Decide what to build
before deciding what it costs.
The validation sprint is two to three weeks that saves most of the money a software project usually wastes. It produces a specification precise enough to price against — and it is yours to keep whether or not you build with us.
Two to three weeks,
five deliverables.
Run as a fixed-price engagement of its own. If at the end of it the honest answer is that the product should not be built, you have spent the smallest amount possible to find that out.
Discovery workshops
Who the users are, what they do today, where the money comes from, what “working” means and what the deadline is actually driven by. Held with your team and, where we can get them, two or three real users.
Flows and information architecture
Every path through the product drawn out, including the exception paths that get forgotten until week nine of a build — failed payments, partial data, permissions, empty states.
Clickable prototype
The core journeys built in Figma and clickable end to end. Enough to put in front of a user, a co-founder or an investor and get a real reaction rather than a polite one.
Functional specification
Written, numbered and testable. Each feature has a description, a rule set and an acceptance criterion. This is the document the fixed price is calculated from.
Architecture & feasibility review
Stack recommendation, data model outline, integration inventory, infrastructure plan and an honest note on anything technically risky or expensive to run.
Interface design that
an engineer can build from.
Pretty screens that ignore states, errors and edge cases cost more than they save. Our design output is a system, not a set of pictures.
Component library
Buttons, forms, tables, modals, navigation and states, built as reusable components so the build stays consistent and fast.
Full screen designs
Every screen in the specification, at desktop and mobile breakpoints, including loading, empty, error and permission-denied states.
Style guide
Type scale, colour tokens, spacing, iconography and usage rules — so your next designer inherits a system rather than a guess.
Prototype
Clickable, shareable and testable. Used for user interviews, internal alignment and investor conversations before a line of code exists.
Accessibility baseline
Contrast, focus order, labels and keyboard paths considered at design time rather than retrofitted after a complaint.
Handover file
Figma with layers named, components documented and specs annotated, in your workspace, with edit rights.
The hardest part
is cutting.
Almost every first specification we receive contains twice the product that should be built first. Our job in the sprint is to find the smallest version that still proves the idea — and to argue for it.
Start with a sprint →Bring us the idea. We’ll bring back a scope you can hold us to.
A scoping call costs nothing and takes forty-five minutes. If the product does not need building yet, or needs building by someone else, we would rather say so in that call than three months into a contract.