How we scope a software project in one week
A good scope is the cheapest insurance a project can buy. Here is the five-day process we use to turn an idea into a plan, a prototype and a fixed quote.
By the Anirmo engineering team
Most software projects that go over budget were never really scoped. Someone wrote a feature list, someone else estimated it, and the gaps were discovered in month three. We spend the first week of every engagement closing those gaps before any production code is written.
The goal of the week is simple: by Friday, both sides should be able to describe what will be built, what will not, how long it will take and what it will cost, without hand-waving.
Day 1: Users and outcomes
We start with people, not features. Who will use this, what are they doing today, and what does a good week look like for them after launch? We write these down as a handful of outcomes that the whole project will be measured against.
Day 2: Flows and data
Next we map the key flows end to end: sign-up, the core job the product does, and the edge cases that usually get forgotten, such as permissions, failed payments and imports. In parallel we list every piece of data the system needs and where it comes from.
Day 3: Architecture and risks
With flows and data in hand, the engineers choose the stack and sketch the architecture. Just as importantly, we name the risks: third-party APIs we have not used before, performance targets, compliance requirements. Each risk gets a plan, or a small spike to de-risk it early.
Day 4: Clickable prototype
We build a clickable prototype of the main flows. It is not pretty, but it is real enough to put in front of a few users. This is where most expensive misunderstandings surface, while they still cost an afternoon instead of a sprint.
Day 5: Plan and fixed quote
We finish with a written plan you keep, whether or not you build with us. It contains:
- 01The outcomes and the flows in scope, and what is explicitly out of scope
- 02The architecture, stack and hosting approach
- 03A sprint-by-sprint delivery plan with a live staging link from sprint one
- 04A fixed price for the build and a list of assumptions behind it
Why a week is enough
A week is short enough to keep momentum and long enough to think properly. It forces decisions, and it gives you something concrete to compare, challenge and approve before you commit a large budget.