Four weeks from “I have an idea” to a prototype real users have handled in front of you.
Who it's for.
- The founder who has validated a pain, not yet a market
- The SMB turning a manual service into a product
- The team that already burned a development budget for lack of scope
The problem we solve.
Most products don't die of bad code. They die of bad scope — decided too early, never written down, never put in front of a user. We fix it on the mockup, where it costs an hour, not in sprint 12, where it costs a quarter.
What you get.
- Scoping memo: problem, target user, competition, regulatory constraint
- v1 scope — and an explicit list of what is not in it
- EN and FR user journeys
- High-fidelity clickable prototype
- Five user tests, with verbatims
- Base design system: colours, typography, components
- Estimated backlog, ready to be built by any team
How it runs.
What we don't do.
- No cosmetic redesign without an identified usability problem
- We don't start without access to five target users — a condition, not a preference
- No “brochure site in five days”
Starting point.
Fixed-price four-week engagement. Kickoff within two to three weeks depending on studio load. The figure comes out of the Diagnostic — one paid scoping week, credited if you continue. And the file is yours: build it with us, with your team, or with anyone else. It works in all three cases.
Bilingual by default. Compliance scoped from day one.
Law 25, PIPEDA and GDPR enter the scope, not the change order: consent records, data minimization, data residency in Canada or the EU, incident procedure. It isn't a line item — it's a design constraint.
How we handle compliance