Connected solutions

Technical discovery before a costly commitment

Before you commit to a rebuild, a new platform or another year of fixes, find out what you're really dealing with. Technical discovery gives you a clear answer, a feature list and a cost, so the big decision is an informed one.

Let’s talk

Most expensive projects start with a guess

Two colleagues planning content together on a whiteboard.
Illustrative photography · Walls.io / Unsplash

We meet businesses with apps that have been “almost finished” for years, websites nobody dares to update and integrations that only one former developer understood. Usually the next quote they got was another guess: a big number with no explanation behind it.

Discovery replaces the guess. We look at the code, the data, the hosting and the process around it, and come back with what’s worth keeping, what isn’t and what it will really cost to get where you need to be.

What discovery delivers

  • A code and infrastructure review. What it’s built on, how healthy it is and what’s risky.
  • A process map. How the work actually flows today, from the people who do it.
  • A feature list. Everything the system needs to do, agreed and prioritised.
  • A recommendation. Fix, extend, replace or leave alone, with the reasons.
  • An MVP definition. The smallest useful first release.
  • Costing by feature. Hours per unit of work, so you can see what each part costs.

Where discovery has paid off

How it runs

  1. Agree the question. What decision does this discovery need to support?
  2. Access. Read-only access to the code, hosting and data we need. Never send credentials by email.
  3. Investigate. Code review, interviews and testing.
  4. Report. A written recommendation, feature list and costing, walked through on a call.
  5. Decide. Use it with us, with someone else, or to stop a project that shouldn’t continue.

Questions about discovery

A few useful answers before you decide.

Is discovery just a sales step?
No. It’s paid, bounded work with a written result you own. If the answer is “don’t build this”, that’s the answer you get.
Do we have to use you for the build?
No. The feature list and costing are yours to take anywhere.
What if the code is a mess?
Then we’ll say so, and explain whether rescuing it or rebuilding is cheaper. In our experience a rebuild usually wins, but we’ll show the reasoning.

Get a straight answer

Tell us what you have, what’s going wrong and what decision you need to make.

Book a discovery conversation · Estimate a discovery engagement · Why discovery comes before a rebuild

Let’s move things forward

Start a conversation

Tell us what you are working towards. We’ll help you find a practical next step.

Let’s talk