You've bought the business. Now the operating work starts.
Whether you have completed or you are still in diligence, the thesis is written and the clock has started. The operation you are taking on runs on duplicate systems, manual reconciliation, and processes that lived with the previous owner. We consolidate what you now own and put governed agents on the recurring work — and where access allows, we start before close.
From inherited fragmentation, to one system you control.
- Duplicate tools inherited from the previous owner, each holding part of the picture
- Manual reconciliation between systems that do not agree, absorbing people's time every week
- Recurring admin that was the previous owner's job, and now has no owner at all
- No baseline you can trust, so you cannot tell whether an initiative moved anything
- Operating knowledge that left with the person who sold you the business
- One central data store, written to from day one, holding what the duplicate tools held separately
- Task-specific agents handling the recurring admin, each with a named human approval point
- A documented baseline, so the effect of each initiative is observable rather than argued
- Processes written down rather than remembered, and transferable to whoever runs them next
- A record of what ran, when, and on whose authority
This describes how the operation is structured before and after. It is not a statement of cost saved, time returned or margin gained — no figure appears here, because no figure has been evidenced under conditions that would let us publish one.
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:
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.
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.
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.
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 new owners ask first
Can you start before completion, or only after close?
Before, where the access allows it. The most useful diagnostic work — mapping where the data actually lives, which systems duplicate each other, and what the previous owner was doing by hand — depends on access rather than on ownership. Where diligence access permits it, that work can run before completion so the first thirty days are spent building rather than discovering.
What happens to the previous owner's systems?
They are retired progressively, not switched off. Each inherited tool is either replaced by the new central store or piped into it, in an order agreed up front, so nothing the operation currently depends on disappears before its replacement works. The point is that the data stops living in several places that disagree and starts living somewhere you own.
How fast can this move?
We will not quote you a timeframe, and you should be sceptical of anyone who does before seeing your systems — no engagement of ours has published one, so we have no evidenced basis for a figure. What we can describe is the order: the constraint is identified first, one stage is scoped and priced on its own, and that stage delivers before the next is discussed. Where diligence access allows, the first step can begin before completion.
Is this a headcount-reduction exercise?
It is not sold as one, and we do not promise a cost outcome. What the work does is take the manual reconciliation and recurring admin off people's desks — the tasks that absorb time every week without needing judgement — so that effort moves to exceptions, customers and the decisions that actually require a person. What you then choose to do with that capacity is a decision for you, and it is not a claim we make on your behalf.
How does this fit a value-creation plan we've already written?
Usually underneath it. Most value-creation plans assume operating data that can be trusted and processes that survive a change of owner; the work here is producing both, and producing a documented baseline so the effect of each initiative is observable rather than argued. If your plan already names a specific operational constraint, that is where we would start rather than proposing our own.
Who owns what gets built?
You do. The source repository, a full export of your data, the documentation and the credentials are yours, on terms stated in writing before the work starts. Any ongoing support is separate and optional — you could end it the day after handover and keep everything that was built, in working order.
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.
Where's the fastest defensible cost reduction?
That is the question the first conversation is about. We map what you have actually inherited, where the manual work is concentrated, and which stage to scope first — before any commitment is discussed.