How we quote a build in two weeks
A fixed quote needs a fixed scope. Here is the discovery sprint we run before we name a price, and what you get at the end of it.
(02) — The note
Written by the people who did the work. Numbers come from client analytics, shared with permission.
Most agencies quote from a call and a brief. We think that’s why most projects run over. Before we name a price, we spend ten working days with your team.
Week one: understand
Interviews with five customers and five people on your team, an analytics audit and a teardown of the product you already run. By Friday we can name the one number the build has to move.
Week two: design and cost
Clickable flows for the core journey, a technical plan and an estimate broken into stories. The quote is fixed, and so is the scope it covers.
What if the scope changes?
It will. We price changes as they come, story by story, so you always know what you’re paying for.
(03) — Keep reading
More from the journal
Process
7 min
How we quote a build in two weeks
A fixed quote needs a fixed scope. Here is the discovery sprint we run before we name a price, and what you get at the end of it.
Case notes
6 min
The checkout that paid for itself in a month
Fernloop's new checkout lifted conversion from 3.1% to 4.6%. The design was the easy part. Here is what made the numbers move.
AI
9 min
Evals before features: shipping AI that doesn't guess
We write the test conversations before we write the prompt. It's slower for a week and much faster for a year.