Scope and priorities
What is in the first release, what is out, and the order we build it in.
Start with the spec. Yours to keep.
A written technical spec comes before any code: scope, architecture, risks and the plan, at a fixed price agreed in writing before we start.
What is in the spec.
One document, written for you and for whoever builds from it. Each part is something you can read, question and check.
User journeys
The flows each kind of user follows, written so you can check them against how your business works.
Architecture and stack
The components, the technology chosen for each, and the alternative we rejected and why.
Data and integrations
The data model, the systems it connects to, and where your data is stored.
Acceptance tests
The checks that decide whether each feature is done, written before any code.
Delivery plan
The sprint-by-sprint plan with the first Friday link named, plus the risks and open questions, each with an owner.
The terms of the spec.
Fixed price
We quote the spec in writing before we start. The price in the quote is the price you pay.
Yours to keep
The spec is yours once paid for. Build with us, build with someone else, or build nothing.
Time stated upfront
The duration is written into the quote, so you know the delivery date before the work begins.
What happens next.
You send the context
Use the project form, however rough your notes are. It takes about two minutes.
We reply within 24 hours, on working days
We confirm what we need to know to scope the spec.
You receive a written quote
The scope of the spec, how long it takes and the fixed price, in writing, before we start.
We write the spec
You receive the finished document, ready to read, share and price.
You decide
Continue with us in two-week sprints with a deployable link every Friday, or take the spec elsewhere.
Start with the spec. Decide after you read it.
Tell us what you are building. We reply within 24 hours, on working days.