( Service 02 )
Product design
Interfaces and flows shaped for clarity — tokens and patterns that stay honest as the product ships.
( Cadence )
8–12 weeks
( File )
Flows + Figma kit
( Studio )
Toronto
( Team )
Two designers
( Scope )
Flows, UI, tokens
( Handoff )
Live library
( What we hold )
A product surface that only works in the pitch file will not survive the weekly build. We design the flows and the kit the team actually ships.
02
(Product design)
What ships in the product file.
Not a screen dump. Flows, a component kit, and tokens a build can keep.
- Flows for the jobs the product already does
- UI for product, empty, and error states
- Tokens for type, color, and space
- Component kit in Figma
- Prototype for the decisions that need a click
- Handoff notes the build can follow
03
(Cadence)
01 · Brief
The surfaces you ship, who uses them, and the deadline. A short brief is enough to start.
02 · Flows
The path through the product, including the states a happy-path mock hides.
03 · Kit
Components and tokens sized for the weekly build, not a one-off screen.
04 · Handoff
A live library and a short rule sheet so the next designer can ship without a call.
04
(How it holds)
( 01 )
Flows before frames
A beautiful screen that skips the empty state is not a product.
( 02 )
Tokens with jobs
Type, color, and space each have a job. Decoration does not get a token.
( 03 )
One kit
Campaign art does not get a second component library. The product file stays the source.
05
(Questions)
Flows, UI for the real states, tokens, a Figma kit, and handoff notes.
Yes. We map the system onto the surfaces you already ship, then harden the kit so the next release does not invent a second UI.
New work uses the same tokens and components. If a feature needs a new pattern, it is written back into the kit.
Send the product you already ship.
A live screen, a Figma file, a backlog. We will tell you if a product system is the next file — or if the flows still need a strategy pass.
Start a brief