Everything decided before the first commit.

Code is the cheapest part to write and the most expensive part to change your mind about. Eleven deliverables that settle the argument on paper: who it's for, what it does, what it looks like and whether anyone can use it, while changing it still costs an afternoon.

0Deliverables
0Weeks typical
0Users interviewed

Eleven notes on one wall

This is the board at the end of week one. Every deliverable written down and the lines showing what feeds what. Hover a note to read what you actually get handed. Pick a phase to watch that part of the board light up.

11 of 11 shown
PRD-01DiscoveryA written map: what you're actually building, who for, and what we agreed not to do.
PRD-02Code AuditsA scored review of the codebase you inherited, with the three fixes that pay for themselves first.
PRD-03Product StrategyOne page saying what ships in v1 and what waits. Initialled by everyone who could later object.
PRD-04UX ResearchRecorded interviews, the quotes pulled out, and the patterns we heard more than twice.
PRD-05User FlowsEvery screen and every dead end as one diagram your engineers can build straight from.
PRD-06WireframesGrey-box layouts for each screen, so structure gets argued before anyone picks a colour.
PRD-07UI DesignPixel-final screens in Figma with every state drawn: empty, loading, error and full.
PRD-08Design SystemsA Figma library plus code tokens your team can use without us in the room.
PRD-09Motion DesignTiming, easing and distance for each transition, specced as values a developer can paste in.
PRD-10Brand IdentityLogo, type scale, palette and the rules for using them, in files your printer accepts.
PRD-11Usability TestingFive users on a clickable prototype, and a ranked list of everything that broke.
DiscoverDefineDesignValidateClick a phase again to clear it

Four steps, and you own every file at the end

01

Listen

Two weeks with your team and your users. Interviews recorded, the old system audited.

02

Frame

One page of strategy: the v1 scope, the cut list, and what success is measured in.

03

Draw

Flows, wireframes, then final screens. Reviewed live every Thursday, never by PDF.

04

Prove

Five users on a clickable prototype before build starts. Findings ranked, then fixed.

Which note is missing from your board?

Most builds go wrong because one of these eleven never got written down. Thirty minutes, and you leave knowing which one it is.

Book a 30-minute call