What Is a Technical Discovery Phase?

Discovery is the part clients most often want to skip, and skipping it is the most reliable predictor of a project going badly. It is a short piece of paid work whose only output is clarity — and clarity is what every subsequent estimate depends on.

What discovery produces

Discovery is not a meeting. It is a bounded engagement, typically one to three weeks, producing concrete artefacts:

A written scope
What is being built, stated precisely enough that two people reading it picture the same thing. Including what is explicitly out of scope, which matters as much as what is in.
User roles and flows
Who uses this and what each can do. Roles drive cost more than features, so this is where the number is really decided.
Data model outline
What information exists, where it lives, and what has to sync. This determines whether you need a backend, which is one of the largest cost forks.
Integration list with risk notes
Every third-party system, with an honest assessment of how well documented and reliable each is.
Technical approach with justification
Platforms, architecture, and why — including options considered and rejected.
Estimate with stated assumptions
A range, and the assumptions it rests on, so that when something changes you can see exactly what it affects.

What actually happens during it

Structured conversations to establish what you are really trying to achieve, as distinct from the solution you arrived with. Often the stated request is one solution to a problem that has cheaper solutions.

Then the awkward questions. What happens when a payment fails midway? What does a brand new user see before any data exists? Who can delete things, and can that be undone? These are business decisions that must be made by you, and answering them during discovery costs a conversation. Answering them during development costs rework.

Where there is genuine technical uncertainty, discovery may include a small prototype — a spike — to establish whether an approach is viable before it is committed to.

Why skipping it costs more

Without discovery, the questions above still get answered — just implicitly, by a developer making a reasonable guess at 4pm on a Thursday. Some guesses are right. The wrong ones surface at review, and changing a decision that other work has been built on top of is far more expensive than making it correctly first.

The second cost is estimate quality. An estimate without discovery is a guess with a risk premium. You pay for that premium whether or not the risk was real. See fixed price vs time and materials.

What it costs, and why paid discovery is better

Discovery is typically a small fraction of total project cost — often in the range of 5–10%. Compared with the cost of building the wrong thing for two months, this is cheap.

Free discovery is really a sales activity, and it is optimised to produce a proposal rather than a plan. Paid discovery aligns incentives: the deliverable is the plan itself, it is yours, and you can take it to another supplier. That last point is the test — if you cannot take the output elsewhere, it was not discovery.

What you should get at the end

A document you could hand to any competent development team, and a decision you can make with confidence: proceed, change direction, or stop. Stopping after discovery is a good outcome — it means you spent a small amount to avoid spending a large one.

How we run it

We run discovery as a fixed-scope paid engagement, usually one to three weeks depending on complexity. You keep everything it produces, including the scope and the estimate assumptions, whether or not you build with us.

Frequently asked questions

What is a technical discovery phase?

A short paid engagement, typically one to three weeks, that turns a vague idea into a written scope with user roles, a data model outline, an integration list, a technical approach, and an estimate with stated assumptions.

How much does a discovery phase cost?

Typically 5-10% of total project cost. Compared to the cost of building the wrong thing for two months, it is inexpensive.

Can I skip discovery to save money?

You can, but the questions discovery answers still get answered, implicitly, by developers guessing. Wrong guesses surface later, and changing a decision other work depends on is far more expensive than making it correctly upfront.

Should discovery be paid or free?

Paid. Free discovery is a sales activity optimised to produce a proposal. Paid discovery produces a plan that belongs to you and that you can take to another supplier, which is the test of whether it was real discovery.

What do I get from a discovery phase?

A document you could hand to any competent development team, and enough clarity to decide whether to proceed, change direction, or stop. Deciding to stop is a legitimate and valuable outcome.

Talk to us about your build

KIDA Studios builds custom software, apps, games, AR and XR across Apple platforms, Windows, Android, web, and embedded. If you have a project in mind, a short discovery call is the fastest way to get a realistic scope and number.

Start a project