Discovery before you build: why a short first step saves money

The most expensive changes are the ones you make after something is built. A short, time-boxed discovery finds them while they still cost an afternoon instead of a month.

  • Planning
  • 2 minute read
  • Updated 19 October 2026

Every project has surprises. An old system that will not talk to the new one. Data that is messier than anyone thought. A user who works in a way nobody asked about. The only question is when you find them.

The later you find a problem, the more it costs to change course.

Discovery is the step where you go looking for those surprises on purpose, before the budget is committed. It is short, it has an end date, and it produces things you can hold.

What discovery should answer

By the end, you should be able to answer four questions in plain words, without anyone reaching for a slide.

  1. What is the problem, and for whom?
    In the words of the people who have it, not the people who will fix it.
  2. What would success look like?
    Written down before anyone estimates the build.
  3. What must it connect to?
    Every system, every data source, every sign-off it depends on.
  4. What could go wrong?
    The risks, ranked, each with what would reduce it.

Easy to forget

Include the constraints you cannot wish away: old systems, messy data, busy periods, and who has to say yes.

What you leave with

Talk is cheap to forget. Good discovery ends in documents you can share with your team, your board or another supplier. These are the ones we hand over.

What a discovery leaves in your hands.

What "done enough" looks like

Discovery is not about knowing everything. It is about knowing enough to start well. You are ready when you have a first slice worth shipping, a short list of open risks, and a clear list of what is out for now.

If the brief still says "platform" with no path a real person takes through it, keep going. Building starts when the first path is specific enough to build and test.

Where discovery sits

Discovery is the first step of a longer route. Each step after it is shorter and safer because of what discovery found.

The order we work in, and the loop that keeps a product improving.

Sometimes the answer is not yet

A good discovery can end with "do not build this yet". Maybe the problem is smaller than it looked, or a tool you already pay for can solve it. That is a good outcome. It cost you a short, fixed amount instead of a long project.

Our promise

Our discovery is time-boxed, and it can end in "do not build that yet".

Tell us what you need

Know what you need

Five short questions. We reply with questions or a written quote.

Hire us
or

Not ready to commit

A small piece of real work, written up and yours to keep.

Get a free first look

Questions first? Email [email protected]