The AI Opportunity Blueprint
A short, paid diagnostic that turns recurring work into a decision you can defend — including the decision not to build.
What a Blueprint is
A Blueprint is a short, paid piece of work that answers one question honestly: is this worth building, and if so, what should be built first. It is not a proposal dressed up as research. It ends in a recommendation you can act on, including the recommendation to leave the work alone.
We start from the work itself rather than from a technology. We sit with the people who do it, follow a real case end to end, count how long it takes and how often it goes wrong, and find where the decisions actually happen. Most of what makes a system succeed or fail is visible at this stage, in the exceptions nobody wrote down.
You keep everything it produces whether or not you build with us. The map, the baseline, the ranking and the roadmap are yours, in a form another supplier could quote against. A diagnostic you cannot take elsewhere is a sales document, not a diagnostic.
Choose the depth
Scope and fee are agreed in writing before anything begins. The first conversation costs nothing.
One process, start to finish, when you already know which one hurts.
Best when one process is clearly the problem and you want a decision quickly.
Discuss this depth
A whole department, when you suspect several things are wrong but not which.
Best when the pain is spread across a team and the sequence matters more than any one fix.
Discuss this depthA page from one
The opportunity ranking is the page most arguments end at. Every candidate scored the same way, so the discussion is about order rather than merit.
| Candidate | Hours / month | Readiness | Risk if wrong | Verdict |
|---|---|---|---|---|
| Supplier invoice entry | 132 | Ready | Low — caught at approval | Build first |
| Delivery-note matching | 74 | Needs access | Low | Build second |
| Customer onboarding checks | 58 | Policy unclear | Medium — compliance | After a policy decision |
| Quote preparation | 41 | Changes every time | High — commercial | Do not build |
| Monthly board pack | 22 | Ready | Low | A template fixes this |
Hours come from your volumes and your rates, not an industry benchmark.
A ranking with no rejections in it is a sales document.
Sequence matters more than any single score, because the second build costs less than the first.
Illustrative example built to show the shape of the output. Not a client record.
What you receive
Written so another supplier could quote against them. A diagnostic you cannot take elsewhere is not a diagnostic.
Every step, handoff and waiting point in the real process — not the documented one. Drawn with the people who do the work, so they recognise it, and detailed enough that a developer could build from it.
What the work costs you today in hours and rupees, taken from your own volumes and rates rather than an industry average. This is the number any future claim of improvement gets measured against.
Each candidate scored on value, how often it repeats, how ready your data and systems are, and what could go wrong. Ranked against each other, so the argument is about the order rather than the merits of one idea.
Where the access, the data quality or the process itself would block a build, and what would have to change first. The uncomfortable findings are in here, because they are the ones that sink projects later.
What to automate, what to fix without software, and what to leave alone. Each with the reasoning attached, so someone who was not in the room can follow the argument.
The sequence, who owns each step on your side, what has to be true before each one starts, and the measures you will judge it by. Written to be handed to whoever builds it, including a supplier who is not us.
How the days run
The same six moves whichever depth you choose. Only the number of workflows changes.
You send a representative set of examples and we agree who we need an hour with. Nothing is billed until the scope and fee are agreed in writing.
We watch the process happen and follow real cases, including the ones that went wrong. Most of the value is here: the exceptions, the workarounds and the informal rules nobody documented.
Volumes, time per case, rework rate and the cost of getting it wrong — from your records where they exist, and from a sample we take together where they do not.
We check the awkward examples against what a system could actually read or decide, and confirm whether the systems it must reach offer a usable way in. This is where optimistic plans die cheaply.
Opportunities scored and ordered, the readiness gaps written up, and the recommendation drafted with its reasoning.
A session with your team to challenge it. The plan changes in this meeting more often than not, which is the point of holding it.
Who it is for
Telling you not to buy this is cheaper for both of us than an engagement that was never going to help.
What we need from you
Bring the work as it is. A cleaned-up version hides exactly the exceptions we are looking for.
A recurring process, as it actually runs — not a cleaned-up version of it.
A handful of representative examples, including the awkward ones: the bad scan, the supplier who ignores your format, the case everybody remembers.
An hour each with two or three people who do the work and know the exceptions.
Whatever numbers you already have on volume and time. If there are none, we take a sample together.
A named person who can decide questions of policy while we are working.
The investment
Quoted in writing after a free scoping conversation, and credited against implementation if you build with us.
BYBO publishes no prices, because the honest figure depends on how many workflows are in scope, how many people we need time with, and how much of the measurement has to be built from scratch rather than read from your systems.
The fee is quoted in writing after a free scoping conversation, and it is credited against implementation if you go on to build with us. You are paying for the thinking, and you keep the plan either way.
If you build with us
The Blueprint fee comes off the build. Agreed in the scope, not offered afterwards.
If you do not
You keep every document, and we will answer another supplier’s questions about it.
What happens after
All three are a result. Only one of them is a sale, which is the point of charging for the diagnostic.
We scope the first release from the roadmap and agree a separate fee, with the Blueprint credited against it. The map, the baseline and the evaluation examples all carry straight into the build.
Take the plan to your own team or another supplier. It is written to be quoted against, and we will answer their questions about it. This happens, and it is a fair outcome.
Sometimes the answer is a rule, a template, a form or a conversation with a supplier. If that is what we find, that is what the recommendation says — and you have spent a small amount to avoid spending a large one.
Before you enquire
Including the ones with an uncomfortable answer.
Discuss a BlueprintThen that is the recommendation, in writing, with the reasoning. It is the outcome that saves you the most money, and it is why the diagnostic is paid — nobody can afford to reach that conclusion for free. You still keep the map, the baseline and the ranking.
Yes, and it is written into the scope before the work starts rather than offered afterwards. If you build the recommended first release with us, the Blueprint fee comes off that engagement.
An hour each with two or three people who do the work, plus a session at the end to challenge the findings. We work around your week rather than asking the team to stop.
Often, yes — and if you have someone who can sit with the work and argue with the conclusions, you should. Our guide on choosing the first workflow sets out the method. People bring us in for the outside view and because an internal ranking tends to follow the loudest department.
Usually only read access, and only where a number cannot be established any other way. Anything we look at is agreed in advance with whoever owns it, and the scope says what we may and may not touch.
It stays with you. We do not reuse your process detail, your figures or your documents elsewhere, and the arrangement is written into the scope. Our privacy information sets out the position.
Then bring their work. If it holds up we will say so and build on it rather than repeating it. What we usually add is the measurement and the readiness testing, which strategy work tends to skip.
No. If you know the workflow, have the examples and can name the exceptions, we can scope a build directly. The Blueprint exists for when that is not yet true, or when the choice between candidates is genuinely open.
Read first
Not all repetitive work repays automation. Here is where to look for candidates, what to measure, how to score them without pretending to be precise, and when to walk away.
Read the articleReadiness is not about how modern your company feels. It is about one workflow: whether it can be described, measured, reached, reviewed and owned. Check it honestly.
Read the articleNobody can price your workflow before seeing it. Here is the honest structure of an automation budget, what pushes it up or down, and how to compare two quotes.
Read the articleTell us the process. We will tell you whether a Blueprint is even the right next step.
