The diagnosis
Find out what is worth building, before you pay to build it.
Two weeks on your real data. You get what the work costs you today, which jobs are worth taking off your team and in what order, and a fixed quote with the acceptance criteria written down. If we find nothing worth building, we say so and return the fee.
Two weeks
Fixed price
Access
Read access, and two hours from whoever knows the job.
Measure
your dataWhat the work costs you today: hands, hours, delays.
Shortlist
Every candidate ranked by what it gives back.
Quote
One fixed price, and the acceptance criteria in writing.
Your decision
Build it, or take the fee back.
The two weeks, end to end.
Three things you walk away with
All three are yours whether or not we build anything together.
What this work costs you today
Counted, not estimated: how many hands touch it, how long each pass takes, where it waits, and what the delay costs downstream. Most teams have never had this number written down, and it is the number that decides whether anything is worth building.
What a system would take off the team
Every candidate job, ranked by what it gives back against what it takes to build. Including the ones we think you should leave alone for now, and why.
A fixed quote, with the criteria in writing
One price for the build that does not move afterwards, and the list of things the system has to do before it is allowed to ship. You approve that list before anything is built, and it is what we are held to.
If there is nothing worth building, you get the fee back.
Assessments usually come from the people who want the build. That is the conflict, and it is why so many of these projects start on the wrong job. Putting the fee at risk is the only way we know to make the finding worth reading: we would rather return EUR 4,900 than take you into a build that does not pay for itself.
It works the other way too. Go ahead within 90 days and the fee comes off the build, so the honest answer and the paid answer cost you the same.
What we need from you
- Read access to the systems the work runs through
- About two hours from the person who actually does the job, not the person who describes it in a meeting
- A recent example of the output, however messy
- Whatever you already believe the answer is, said out loud
What you stay in control of
- Which systems we are given access to, and for how long
- Whether the criteria we propose are the right ones
- Whether anything gets built at all, and by whom
- The findings themselves: they are yours, including the quote, and any builder can work to them
And if you do build, this is how it works
- Fixed price
- Quoted once after the diagnosis, invoiced once. No day rates and no running meter.
- Criteria in writing
- We agree what the system has to do, and how it will be measured, before anything is built.
- It ships when it passes
- Tested on your data against those criteria. Until it passes, we keep working at no extra cost.
- You own everything
- Code, prompts, data, accounts, documentation. Yours from day one, so there is nothing to be locked into.
- Your team runs it
- Training and a handover built for people who did not write it. If you never speak to us again, it keeps working.
The jobs a diagnosis usually looks at
You do not have to pick one first. Naming the wrong job is the most common way these projects start badly, which is exactly what the two weeks are for.
Lead research and follow-up
The research nobody has time for, and the follow-up that depends on someone remembering.
The document someone is waiting for
The pack your bank, your board or your partner asks for, assembled by hand every time.
The numbers rebuilt by hand
The monthly spreadsheet, and the deck that gets rebuilt from it.
Quotes and orders in the inbox
Requests arriving as email and PDF, retyped into your system by a person.
A website machines can read
What an assistant finds when a buyer asks it about you.
Questions buyers ask
What if you find nothing worth building?
Then we say so and return the fee. That is the whole promise, and it is deliberate: the way this work usually goes wrong is that the person doing the assessment is paid to find a project. We would rather return EUR 4,900 than sell you a build that will not pay for itself.
Is the fee on top of the build?
No. It is credited in full against a build that starts within 90 days. If you go ahead, the diagnosis has cost you nothing extra.
How much of our time does it take?
Read access to the systems the work runs through, and about two hours from the person who actually does the job. Not the person who describes it in a meeting: the person whose afternoon it is.
Do we have to build with you afterwards?
No. You own the findings, the ranking and the quote, and you are free to take them to another builder or to your own team. That is the point of writing the acceptance criteria down: they are a specification anyone can work to.
What if we already know what we want built?
Say so on the call. If the job is clear and the data is in reach, we can sometimes quote directly. The diagnosis exists because most of the time the job people name first is not the one that gives the most back.
Why does this cost anything at all?
Because a free assessment is worth what it costs. Two weeks of measuring your actual work is real effort, and paying for it is what keeps the finding honest rather than a route into a sale.
Bring the job that annoys you most.
Twenty-five minutes is enough to tell whether a diagnosis is worth your money. If it is not, we will say that on the call.