We settle what is worth building, how big, and which test comes first.
You want to build something with AI and there are several ideas in the air. We sit with the team and come back with the one worth building, a written recommendation and a scope you can approve or decline.
Why a build should not start with the build.
A build that starts before the question is settled answers it at build cost, with a team already committed. The choice of idea and first test decides what the rest of the budget buys.
And if the recommendation is to build nothing yet, you hear it before the build budget is committed.
How it works
We sit with the team
The people who know the workflow, in the room with us.
We sharpen the problem
Which idea comes first, and which risk in it decides the rest.
We write the scope
With a budget and a duration estimate, ready to approve or decline.
What you get
A written recommendation
Which idea, which stage, and the reason.
A scope ready to sign
For the recommended next step.
A budget and duration estimate
So whoever approves it decides on numbers.
A readout
We present it to whoever approves the work.
Frequently asked questions
Can't we just start building?
You can, and some teams should. Choosing first costs less than settling the question at build cost. If the scope is already clear, we say so and skip Discovery.
Couldn't our own team scope this?
Your team knows the workflow better than anyone. What it rarely has is time away from client work to set the ideas side by side. None of the ideas is ours, so the recommendation can go to the one with the most value in it.
How long does Discovery take?
Usually a few days, sometimes a week. It depends on how many ideas are in the air and how many people we need to hear. We agree it before we start.
Our innovation committee wants a business case. Is this it?
It gives the business case its facts: the idea, the test, the scope and the estimate, written to be forwarded.
Wouldn't our platform vendor scope this for us?
They scope what fits their product. Discovery starts from your workflow and may end with the platform, a build alongside it, or nothing.
Isn't this what a strategy house does?
No. A strategy house asks where AI belongs in the organisation. Discovery assumes you know the workflow and asks what to build for it. If where AI belongs is still open, a Practice Assessment is the better start.
More in this track
Tell us what you want to build and who approves it.
Discovery is the answer while the scope is still open. When it is already clear enough to start, we tell you to start.