A scoping phase is a short, paid step before any build, where you and the developer agree what to build, in what order, and for how much, in writing. It saves money because mistakes are cheapest to fix on paper. It also turns a vague estimate into a quote you can hold the supplier to.
Some firms call it discovery. Our version is the Scoping Sprint, from $150₹2,100.
What is a scoping phase, also called discovery?
It is the work you do before anyone writes code. The aim is to understand the problem, decide what to build first, and put a price on it.
The GOV.UK Service Manual is public-sector guidance, so it is not written for small firms. Even so, it makes the point well. It says you need to understand the problem before you commit to building, and that you should not start building in discovery.
It also says stopping at the end of discovery is not a failure if your research shows that is the best thing to do.
The agency CodeStringers (20 July 2026) sells discovery, so weigh its view accordingly. It lists typical outputs:
- Requirements. A document that says what the software must do and for whom.
- Priorities. A ranked feature list, so the first release is small and useful.
- Screens and flows. User flows and rough layouts, so you see the idea before it is built.
- Technical plan. How the software connects to your other systems, and what could go wrong.
- Estimate. A scope, timeline and cost you can compare with other quotes.
Why does a scoping phase save money?
Changing a sentence in a document costs almost nothing. Changing software that is already built costs real time.
CodeStringers puts it this way: “Skipping discovery doesn’t remove the work — it defers it to the most expensive possible moment.” The work of deciding still happens. The only question is when.
A scoping phase helps in three ways.
- Cheaper mistakes. Wrong assumptions show up on paper, before they are built into screens and databases.
- A quote you can hold. The UK back-office software firm InsideData says it only quotes things it has actually understood. A price based on understanding is firmer than a guess.
- A smaller first build. Ranking features means you pay for what matters first and leave the rest for later.
InsideData also gives an illustration of spending £4,500 to avoid a £40,000 mistake. That is an example from one firm, not a standard fee, and your numbers will differ.
There is an honest downside. It feels like paying before you have anything to show, and it adds time before the build starts.
It can also tell you not to proceed. That is a saving too, as long as you learn it before building.
What does a Scoping Sprint with us include and cost?
Start with a free 20-minute call. We tell you honestly what would help, whether that is a Scoping Sprint, a quote, or nothing at all.
| What | Includes | From |
|---|---|---|
| Free call | 20 minutes, honest advice on your next step | Free |
| Scoping Sprint | One working session, a written scope and a tailored quote | $150₹2,100 |
| Experience Design Direction | User flows, key-screen layouts and style direction, 1 to 2 weeks | $200₹3,500 |
| Starter Tool | One data area, logins, one report, one automation, 2 to 4 weeks | $750₹15,000 |
The Sprint fee comes off the project if you go ahead. Experience Design Direction is a separate, deeper design step for when screens matter most.
The written quote lists scope, milestones, dates, assumptions and what is not included. After that, you pay a 30% deposit, then milestone payments. We invoice each milestone after you approve it.
You see and approve screens before the build. You own the code, the domain and your data, and you get 30 days of free fixes after handover.
Custom tools and portals are scoped in a Sprint, then quoted in writing. Workflow automation has no package, so the Sprint is its starting point. See web apps, automation and how we work.
When do you need a scoping phase, and when can you skip it?
Work through these checks in order. The more you answer “no”, the more a Sprint is worth.
- Can you write the scope? If you can list what the software must do in a page or two, you may be ready for a quote.
- Is the first release clear? If you cannot say what comes first, a ranked list is worth paying for.
- Do other systems connect? Links to accounting, email or spreadsheets hide most surprises. Check them before pricing.
- Do several people disagree? A written scope settles who wants what before money is spent.
- Is the budget tight? A short paid step costs less than rebuilding the wrong thing.
You can skip it when the job is small and clear, such as one of our Starter packages. The free call will tell you honestly.
To compare ways of paying, read agreed price vs hourly software development. For what a quote should show, see what a written quote should include. For typical build prices, see how much a custom web app costs.
Start with a free call or a Sprint
Tell us what you want the software to do, who will use it and what worries you. We will say whether a Scoping Sprint makes sense. See our pricing page, then request a quote or book a free 20-minute call.