· Process, Clients
How we scope a web project in one week
Vague estimates kill projects before they start. Our one-week scoping process turns an idea into a fixed plan: screens, milestones, price.
Most software projects don't fail in development. They fail at the estimate, when neither side really knows what's being built. We spend one week fixing that before any contract is signed.
Day 1–2: the problem, not the feature list
A call where you talk and we ask questions. What does the business do, who uses the software, what breaks today. Feature lists come later; first we need to know what "done" changes for you.
Day 3–4: the walking skeleton
We sketch the key screens, usually five to eight, and put them in front of you as a clickable flow. This is where "oh, actually…" happens, and it's the cheapest place for it to happen.
Day 5: the plan
You get a short written document:
- The screens and features in scope, by name
- Milestones with dates. The first demo is always within two weeks
- A fixed price, and what would change it
- What we deliberately left out, and why
What this costs
Nothing. If the plan is useful and you build with someone else, keep it. A scope document that only works as a sales trap isn't a scope document.
Have something half-formed? Send us two sentences about it. That's genuinely enough to start.