What a Spec Sprint is
A Spec Sprint is a short, fixed-shape engagement in which we write the spec for your frontend with you. In one to two weeks you get every rule your product must follow written down and agreed, each one testable, together with the plan to build it. Nothing is built yet. You decide what happens next with the spec in hand.
Most frontend projects start from a ticket list and a promise to work out the details later. The details then arrive late, as rework, missed dates and failed reviews. The sprint moves that work to the start, where it is cheapest.
What you receive
You receive a spec pack: a set of versioned documents that together describe what will be built and how anyone can check it was built correctly. You own it on payment, and you can build it with us, with another team or in-house.
| Deliverable | What it contains | Why it matters to you |
|---|---|---|
| Product constitution | The non-negotiables: accessibility level (WCAG 2.2 AA), performance budget, privacy stance, supported browsers and devices, brand rules, and the rules for each market you operate in | Settles the questions that otherwise get argued feature by feature |
| Feature specs | User stories, acceptance criteria in Given/When/Then, states and edge cases, and every piece of data collected with the reason for it | Each criterion becomes an automated test, so “done” is no longer a matter of opinion |
| Rules matrix | Markets × rules → the UI requirement each rule creates | Shows where one rule changes the interface, before anyone builds it twice |
| Risk register | What could go wrong, how likely it is, and what the spec does about it | Lets you see the risks you are accepting |
| Architecture outline | Structure, rendering approach, integrations, tokens, test strategy | Shows the build is feasible and how it will hold up as the product grows |
| Delivery plan | The work broken into small tasks, each linked to the criteria it satisfies, grouped into milestones | The basis for a fixed quote and a dated plan |
You can see the shape of these documents in our feature spec template and constitution template.
How the sprint runs
The sprint is a structured sequence of short sessions and written drafts, not a series of workshops. Most of the work happens asynchronously in writing, so your team spends a few focused hours on it, not whole days.
- Kickoff. We agree the scope of the sprint, the decision-maker on your side and the material we need: existing designs, repositories, vendor documentation, current pain points.
- Constitution draft. By the end of the first days you have the non-negotiables in writing. This is where most hidden disagreements surface.
- Feature specs. We write the specs for the features in scope, with acceptance criteria you can read without technical training. Your team comments; we revise.
- Rules and risks. Your compliance or legal team confirms the rules for each market. We record that confirmation in the spec. We implement rules precisely, but we don’t give legal advice.
- Plan and handover. We break the work into tasks and milestones and walk you through the whole pack in plain terms.
Who it is for
The Spec Sprint fits a team that knows what it wants to build but has not yet written down every rule the interface must follow. It suits a founder about to commit budget to a build, or a team that has been burned by an agency that “figured it out in sprint 3”.
It also works when you plan to build in-house. A spec written by an outside team you can check is often the fastest way to get your own engineers and agents building from the same source.
What it costs and how it is credited
The sprint is paid, at a fixed fee quoted after a first conversation once we understand the scope. We don’t publish prices because the scope varies too much for a list to be honest.
If you start a Build with us within 60 days of accepting the sprint, the full sprint fee is credited against the Build. If you don’t, you keep the spec pack and owe nothing more.
What happens after the sprint
After the sprint you hold a spec, a plan and a fixed quote for the Build. There are three common next steps, and all of them are fine with us.
- Build with us. The spec becomes the scope of a Statement of Work, milestones map to spec sections, and every release ships with a trace report.
- Build with another team. The spec pack is yours. It is written so any competent team can build and verify against it.
- Build in-house. Your engineers and coding agents work from the same tasks and criteria we would have used.
How we work during the sprint
We work under a mutual NDA from the first detail you share. Communication runs over a company messenger (Signal, Telegram or Session), with a written update at the end of each working week and replies within one business day. We name no client, publicly or privately, unless you approve the exact wording in writing.
Common questions
Do we need designs first? No. Designs help, but the spec defines behaviour, states and rules, which designs rarely cover in full. Where designs exist, the spec references them.
Can the spec change later? Yes. Changes are written as spec deltas, marked ADDED, MODIFIED or REMOVED, and priced before any work starts. See Spec Kit and OpenSpec for how we handle changes in an existing codebase.
Is the sprint useful if we don’t build with you? That is the point of it. You own a spec that any team can build and test against.