Make the business easier to buy before you sell it.
You are planning an exit in the next one to five years. The problem is not that the business does not work — it is that it works because of you. We consolidate the data, systemise the work that only happens when you chase it, and put governed agents on the defined tasks, so what an adviser inspects is a system rather than your memory.
From a business that runs on you, to one that runs without you.
- The operating picture of cash, delivery and customers lives in your head, not in a system
- Several tools hold different versions of the same information, and only you can reconcile them
- The processes that matter are the ones you explain in person, not the ones written down
- Answering a question about the business means you personally going and finding out
- An adviser has to take your word for how the operation runs
- One consolidated data store holds the operating picture, rather than a person
- Repeatable work handled by task-specific agents, each with a named human approval point
- Documented processes a new operator can be handed without you in the room
- Questions answered from the system, and answered the same way twice
- A record of what ran, when, and on whose authority — evidence rather than assurance
This describes how the operation is structured, not what it is worth. We build the operating evidence that supports a buyer's conversation; we do not promise what that conversation concludes.
We find the constraint before we propose anything.
We start with a discovery call — not a sales pitch, a genuine attempt to understand your business. Everything after it depends on getting the first question right.
- A discovery callHow the business actually runs, who holds what in their head, and what it costs when the person holding it is unavailable. No pitch, and nothing to sign.
- Find the real constraintWe look for the single bottleneck actually limiting the business — the one thing that, if fixed, moves every number that matters. (This follows Theory of Constraints, the same discovery method now used by private equity firms applying it across portfolio operations.)
- Test whether an agent is the answerOnly then do we explore whether an AI agent is the right way to address it. Sometimes it is. Sometimes the constraint is not something an agent can touch, and we will tell you that too.
- Scope one stage, not threeYou see the first stage scoped and priced on its own terms before anything else is discussed. Nobody commits to a programme they have not seen the shape of.
A diagnosis that ends in a slide deck and a sales pitch is not a diagnosis. If the constraint is not something we can help with, that is what you will hear.
What a governed agent actually does.
Every agent is scoped to a named task, against your own data, with a defined human approval point. Some examples:
Top of funnel & sales
- An agent with full context on your pricing, past jobs and capacity produces a quote on demand for a prospect; a person reviews it before it is sent.
- An agent triages and drafts responses to prospect enquiries, pulling from your own documentation and past answers; a person approves before it goes out.
- An agent tracks a lead through follow-up on a schedule you set.
Reporting & financial visibility
- An agent consolidates cash, sales and delivery data into one weekly view.
- An agent drafts the month-end reconciliation; a person signs it off.
- An agent flags a number that does not reconcile before it reaches a report.
Delivery & fulfilment
- An agent runs the onboarding checklist for a new client and flags what is outstanding.
- An agent tracks capacity against demand and surfaces the exceptions.
- An agent drafts a status update from job data; a person reviews it before it goes out.
Post-acquisition cost reduction
- An agent consolidates duplicate systems inherited from a previous owner into one data store.
- An agent takes on the manual reconciliation work that currently occupies people full-time, moving that effort to exceptions and judgement.
- An agent takes on the recurring admin that used to be the previous owner's job, so the work survives the change of ownership rather than depending on the person who left.
Every one of these has a name, a defined scope, and a person accountable for the output — which is what makes it something a buyer's adviser can be shown, rather than a black box somebody has to explain away.
What founders ask first
Does this replace me, or my team?
No. Every agent is scoped to a named task and has a person who approves its output before anything leaves the business — an agent drafts, a person sends. The work that gets handed over is the repeatable part: the chasing, the re-keying, the reconciling between systems that do not agree. What it changes is that the business stops depending on you personally holding the picture, which is a different thing from replacing you.
We already pay for tools that work — does this mean ripping them out?
No. Stage 1 is deliberately not a big-bang migration. A custom app becomes where the work happens and writes into one central store from day one, and each existing tool is replaced or piped in as its turn comes. Anything genuinely working can stay until there is a reason for it not to. The business never stops running to accommodate the project.
What if our data is a mess?
That is the normal starting point, and it is what Stage 2 exists to do. Reconciling what several systems each believe to be true, resolving it into one structured record, and documenting where each number comes from is the unglamorous 80% of this work — and it is the part a diligence process actually tests. A business with clean data and no agents is in better shape than the reverse.
How long before this shows up in a data room?
It shows up in the order the work is done, not on a fixed timetable — and we will not quote you one, because we have no published engagement to base it on. What we can say is the sequence: Stage 1 produces a system a new operator can be shown, Stage 2 produces data that reconciles when somebody checks it, and Stage 3 produces a record of what ran and on whose authority. Each stage is scoped and priced on its own, so you see the shape of the first before committing to the next.
What do we actually keep at the end?
The source repository, a full export of your data, the documentation and the credentials — itemised in writing before the work starts, not described afterwards. All of it is yours whether or not you continue working with us. Ongoing support is a separate, optional service; it is not access to what was built.
Do you work with businesses in our industry?
Almost certainly. Fragmented data, tools that disagree and no single view of cash or delivery look much the same in manufacturing as in professional services, and the method does not depend on sector knowledge — it depends on how the work is currently arranged. If the constraint turns out to be something specific to your industry that we cannot help with, we will tell you that in the first conversation.
The method in full
The three stages, why they run in that order, and what you end up holding at the end of each are set out on the method page.
Can this business run without you?
That is the question the first conversation is about. We map where the data actually lives, what is creating dependency on you, and which stage the business is genuinely ready for — before any commitment is discussed.