A technology scoping service (the industry also says discovery phase, pre-development, or technical due diligence, depending on who is selling) produces the piece of work that comes before the build: what problem is actually being solved, what the current system can support, which options exist, what each would cost, and a phased plan someone could execute. Done properly it is the cheapest work in the whole project, because every error it catches would have cost ten times more to catch in code.
The market for this work has a structural quirk worth naming up front: most scoping is sold by the firms that want to win the build it scopes. That does not make agency discovery worthless, but it shapes every incentive in the engagement, and choosing a scoping service is mostly about deciding how much of that conflict you can live with. Here is the market in 2026.
The market at a glance
| Service | Best for | Timeline | Indicative cost |
|---|---|---|---|
| Counsileum | A neutral scoping report before talking to any builder | About an hour | Lowest on this list |
| Dev-agency discovery phases | Projects where the same firm will likely build | 2–6 weeks | Roughly 5–10% of the build budget |
| Independent architects and fractional CTOs | A senior neutral opinion with no build to sell | 1–4 weeks | Senior day rates |
| Big consultancies | Enterprise programmes needing a defensible process | 4–12 weeks | Six figures |
| Design sprint studios | Product questions where the risk is desirability, not feasibility | 1–2 weeks | Fixed sprint fee |
The best technology scoping services in 2026
Counsileum: best for scoping before you talk to builders
Disclosure first: Counsileum is our product, so read this entry as a position statement rather than a neutral review.
Our Forward-Deployed Engineer and Engineering Planner consultants produce a client-facing technology scoping report as a productised deliverable: problem statement, current-state assessment, requirements split by kind, options with costs, risks and unknowns, and a phased plan. Attach your repository and the analysis is grounded read-only in the code you actually run rather than in what a workshop remembered about it. It arrives in about an hour, at a price that makes "scope first, then shop" the obvious order of operations, and because we do not sell the build, the report has no thumb on the scale. It is the document to hold in your hand while the agencies below pitch you theirs.
Dev-agency discovery phases: the default, with a known conflict
Most software agencies of any size sell a discovery phase: two to six weeks of workshops with a business analyst, a solution architect and a designer, producing requirements, architecture direction and an estimate, typically priced around 5 to 10 percent of the anticipated build (ELEKS, Agilie and Emvigo are representative names in a very large field). The work is often genuinely good, and if you already trust the agency and expect them to build, a paid discovery is a sensible way to start.
Keep the incentive in view: a scoper who profits from the build is structurally rewarded for finding more build. The estimate that comes out of agency discovery is a bid wearing a report's clothing. Two protections work: pay for discovery as a standalone engagement whose outputs you explicitly own and can hand to a competitor, and get a second opinion on the recommendation from someone with nothing to win.
Independent architects and fractional CTOs: best neutral senior judgment
A contracted solution architect or fractional CTO will scope without wanting the build, which removes the conflict and usually shrinks the recommendation. Sourced through networks or word of mouth, at senior day rates for one to four weeks, this is often the best value in the category for a non-technical founder or a team whose own seniors are too close to the system. The variance is the person; there is no brand underwriting the quality, so reference-check the individual, not the label.
Big consultancies: best when the process must survive audit
For an enterprise replatforming with regulatory exposure and a steering committee, the big firms sell scoping as a programme: stakeholder interviews, current-state architecture review, options analysis and a roadmap, delivered with the process weight that procurement and audit expect. You are paying six figures largely for defensibility, and the same question applies as with agencies: the firm usually also sells delivery, so ask what happens to the engagement if the recommendation is "build less" or "buy instead", and watch how the room reacts.
Design sprint studios: best when the risk is the product, not the tech
Some projects fail not because the system could not be built but because nobody wanted it. Studios running one-to-two-week design sprints (prototype plus user testing) answer desirability cheaply before anyone scopes feasibility. This is a complement to technical scoping rather than a substitute: a sprint tells you whether to build the thing, a scoping report tells you what building it involves.
How do you choose a technology scoping service?
Judge the sample deliverable, not the pitch. Ask every candidate for a redacted example of a past scoping report and check it against the eight sections a real one contains: if there is no current-state assessment, no options analysis with a rejected option, no named risks and no phased plan with costs, you are looking at a proposal template. Then ask the incentive question directly: what do you earn if the recommendation is that we build nothing. And for anything touching AI, insist the plan names an evaluation set and a numeric definition of done, because the projects that skip that step are the ones that fail.
On price: agency discovery at 5 to 10 percent of build budget is defensible for a large project where the same team continues. But the wider lesson of 2026 is that the cost of a first, neutral scoping pass has collapsed, and there is no longer a good reason to let the first person who scopes your project be someone bidding to build it.
Frequently asked questions
What is a discovery phase in software development?
A discovery phase, also called scoping or pre-development, is a time-boxed engagement before the build in which the problem, the current system, the requirements and the options are pinned down, producing a scoping document, an architecture direction and a costed, phased plan. Its purpose is economic: every wrong assumption caught in discovery costs a fraction of what the same error costs once it is in code.
How much does a software discovery phase cost?
Agency discovery typically prices at 5 to 10 percent of the anticipated build budget and runs two to six weeks, with the underlying day rates for a business analyst, solution architect and designer each in the mid three to low four figures. Independent architects charge senior day rates for one to four weeks. Consultancy scoping programmes for enterprises start in six figures, and productised scoping reports now cost a small fraction of any of these.
What should a technology scoping report include?
Eight sections: a problem statement, a current-state assessment, requirements split into functional, non-functional and constraints, an options analysis that includes at least one seriously considered rejected option, a recommendation, named risks and unknowns, a phased plan, and costs with resourcing. A deliverable missing the current-state assessment or the rejected option was written to sell a build, not to scope one.
Should the same company do discovery and the build?
It is common and sometimes sensible, because context carries over, but it puts the scoper's incentive on the side of finding more build. If you do combine them, buy discovery as a standalone contract whose outputs you own outright and could hand to a competing builder, and have someone with nothing to win review the recommendation before you sign the build. If the discovery report only makes sense as a preamble to that agency's proposal, it was a proposal.