I want to try to describe something that is usually left vague: what a business actually looks like after twelve months of systematic, proportionate operational improvement. Not the aspiration. Not the projected savings on a spreadsheet. What you would observe, specifically, if you were paying attention to the right things.
The business I am going to use as a frame is a composite archetype. 32 people. Professional services — management consulting, or something adjacent. Good client relationships. A reputation that earns referrals. Revenue growing. Margins not growing at the same rate.
Two operational drags that are identifiable within about 40 minutes of sitting with the team.
The first is the proposal process.
When a new piece of work is scoped, a senior consultant typically spends between six and nine hours building the proposal. This includes finding the relevant previous engagements to reference (distributed across four people’s email histories and a shared drive that follows a filing convention nobody quite agrees on), assembling the fee schedule from the current rate card (updated twice a year, not always the version in the proposal template), and writing the narrative sections that, in practice, are 70 per cent similar to the previous three proposals to clients in the same sector.
The proposal review involves one other senior and the managing director. They add comments in a tracked-changes document. The comments go back to the proposal author. There are usually two or three rounds. The total elapsed time from initial brief to sent proposal is typically eight to twelve working days.
The client is waiting ten days to receive a document that contains, in substance, about two hours of genuinely bespoke thinking.
The second drag is the utilisation reporting.
Every Monday morning, the operations manager — her name, in this telling, is Priya — spends two hours consolidating the previous week’s time entries. This involves downloading from the time-tracking system, cross-referencing against the project management system (which holds the project budgets), and producing a summary for the weekly management meeting. The numbers are not wrong. They are two hours old by the time anyone sees them.
Priya has been doing this Monday routine for three years. She has mentioned twice that she thinks it could be addressed. Both times, the response was broadly supportive and ended with “let’s look at that when things are a bit quieter.”
At the twelve-month mark — after a Map, after the first two improvements have been built and settled in — what does this business look like?
The proposal process looks like this: the senior consultant opens a proposal template that already contains the client context pulled from the CRM, the relevant previous engagement summaries, and the current rate card for this type of work. The narrative sections they wrote for the last three similar proposals are surfaced as drafts. They spend ninety minutes — not six hours — on the genuinely bespoke elements: the specific problem, the specific approach, the specific team. The proposal goes for a single senior review, which takes 40 minutes, because the reviewer does not need to query the rate card or the fee schedule — it is pre-populated and correct. The proposal is sent in four days, not ten.
The client, who has been waiting four days rather than ten, notices that Priya’s firm is unusually responsive. They do not know why. The reason is that the proposal now costs about three hours to produce rather than eight, which means the bottleneck has been removed, which means the managing director is not the approval queue for every pricing decision.
Over twelve months, the firm sends roughly 40 proposals. At three hours each, versus eight hours previously, the recovered time is 200 hours of senior consultant time. At a blended rate of £95 per hour for that seniority level — a reasonable benchmark for a firm of this type — that is £19,000 recovered in one process change.
Priya’s Monday morning looks like this: she arrives, opens the dashboard she was already looking at on Friday, and the utilisation summary is there. It was generated at 11pm Sunday from the time entries that were already in the system. She spends fifteen minutes reviewing it for exceptions — because reviewing for exceptions is what she is good at, and the system does not replace that judgement, it clears the two hours of assembly work that used to precede it. The Monday meeting starts with accurate, current data rather than data that is current as of Friday.
Over twelve months, Priya has recovered approximately 90 hours that were previously spent on compilation. She has spent a significant portion of that time on the analysis work she was hired to do — noticing that one project has had its margins squeezed by scope creep that nobody flagged in the weekly report, noticing that two clients have gradually shifted their project mix towards lower-margin work, noticing things. The business has become better informed, not because of better data tools, but because the person who was supposed to be looking at the data can now actually look at it.
The compound effects at twelve months are harder to put numbers on but no less real.
The business has a clearer picture of its operational costs than it did at the start of the year. The proposal process change has made the relationship between effort and revenue more legible — the managing director can now see, in approximately real time, whether the pipeline covers the next quarter. This was always technically possible. It is now actually happening.
The operations team has recovered roughly 25 per cent of their operational week from compilation and reconciliation tasks. Some of that time has been absorbed by growth — the business took on three new clients in the second half of the year, which would not have been possible without the freed capacity. Some of it has gone into improving the client reporting process, which was the third drag on the list that did not get addressed in year one. It is on the list for year two.
New starters become useful faster. The institutional knowledge about how proposals are scoped is now in the template, not in the memory of the person who trained the last person. A consultant who joined in October was producing independent proposals by month two, rather than requiring supervision into month four.
There is a framing I use at the end of this kind of conversation that tends to land with founders and managing directors in ways the operational numbers do not.
A business that recovers £50,000 to £80,000 per year in genuine operational cost — not projected, not theoretical, but measurable in the time no longer spent and the capacity now available — has not just reduced its cost base. It has created an asset.
If you apply the standard enterprise value multiple for a professional services firm in this revenue bracket — typically 5x to 8x EBITDA, with operational efficiency as one of the primary drivers of where in that range you land — the £50,000 to £80,000 recovered annually represents £250,000 to £640,000 of enterprise value. This is a calculation from standard SME multiples, not a guarantee — but it is the right order of magnitude for a business that has recovered this kind of capacity, provided that capacity is redeployed to billable work or visible cost reduction rather than absorbed silently. Not in year three. Now, embedded in the P&L.
The Map does not cost £50,000. It costs £4,950 and about twelve days of the founder’s attention — mostly in introducing the team to the process and approving the first design before it goes live. The return on that commitment, in a business of 30 people with two or three identifiable operational drags, is not marginal. It is, when described plainly, a reasonably obvious decision.
The reason it is not an obvious decision — the reason it sits on the list next to six other things — is that the destination is hard to see until you name it specifically.
This is what the business looks like in a year. Not transformed. Not unrecognisable. Just noticeably, measurably better — in ways that are visible to the people who do the work, the clients who receive proposals in four days instead of ten, and the finance function that closes the month in two days rather than five.
The businesses that make this change tend to describe it, looking back, not as a significant decision but as an obvious one. The one that is harder to explain is why they waited.