Service Design

GridOne

A tailored building-maintenance and consulting firm, where one phone scan carries all the way through to a signed contract.

Year
2026 / Jun
Type
Service Design
Scope
Six-step service pipeline
Status
In progress
Overview
Scan to contract, in one continuous flow

GridOne turns a smartphone scan of a room into a measured scope, a transparent estimate, a code check, an instrument-verified inspection, and a signed contract, without the owner re-entering anything or chasing a different person at every step.

Renovation is one of the largest purchases a household makes and one of the least legible. I designed the service around continuity rather than around features, because the thing that breaks trust is the handoff between steps, not any single step on its own.

Snapshot

Every price the owner sees traces back to a measurement somebody actually took.

Problem Definition

Owners approach renovation with almost no leverage. I narrowed that into three structural frictions, because each one needs a different mechanism to dissolve.

Three frictions that make renovation a black box

These are not three separate products. Each one is the reason the next is hard to fix, so I treated continuity as the design problem and built the pipeline to carry evidence forward rather than to add features at each stage.

Discovery

Toronto's housing stock is old and getting older, which makes the demand durable rather than cyclical. That is what made a single-city beachhead defensible.

The context that makes demand durable
One pipeline, three sides of the market

The service only works if all three sides show up, so I mapped what each one gets before designing anything.

From a $105B sector to a Toronto beachhead

Renovation is now the majority of Canadian residential investment, yet nobody owns the transparent, code-verified estimate. Narrowing to one wedge is what makes the entry credible.

Three horizons

I sequenced it so the compliance backbone is in place before the marketplace opens, since a trust product that launches without an audit trail has nothing to defend.

Prototyping
Four layers, one continuous data handoff

Each layer transforms the one below it and passes structured data up. Nothing is re-entered, so the scan captured in the first layer is still doing work at the contract in the fourth.

System layers
Six steps, one pipeline

Capture, auto-analysis, estimate, code check, measurement, contract. Each step inherits what the previous one produced, which is the whole mechanism.

Conclusion
Resolve asymmetry, trust, and complexity with continuity

When capture, analysis, estimate, code check, measurement, and contract all live in one flow, the owner stops chasing a different person at every step, and every price becomes a measured, auditable claim.

The lesson I take from this one is that the trust problem in renovation is a continuity problem wearing a different name. Nobody is lying at any single step. The evidence simply stops travelling between them, and once it stops the owner has no way to check anything, which is the condition a scam needs to work.

The case study is still in progress. The walkthrough videos for each stage are in production, and the open question I want to answer next is calibration: an instrument reading is only auditable if the instrument itself is provably in spec, which is why calibration standards sit in the second horizon rather than the third.

Sources: City of Toronto Housing Data, Woodsmith, IBISWorld, Mordor Intelligence, Newswire, City of Toronto Building Permits.