A worked example
Watch a business
rewire itself.
One enquiry, from the moment it arrives to the moment the work is delivered and invoiced. This is the engine most businesses run on, what the read finds inside it, and what it looks like rebuilt.
A professional services business, around forty people. Not named, at their request.
The engine
Sales to delivery.
Nine handovers.
Every business has this engine. Very few have ever seen it drawn. Press play and follow one job through it.
Each one holds a different answer. The orange stages are where a person is doing work a system should carry.
What the read found
The problem was never
the people.
Nobody was slow. Every stage worked. The loss was in the joins between them, and no single function owned a join.
The same job, typed four times
Enquiry, proposal, project record, invoice. Four systems, one set of facts, retyped at every boundary. Every retype is a chance to be wrong, and every correction costs more than the typing did.
Waiting is invisible
The work took hours. The job took weeks. The difference was sitting in inboxes waiting for somebody to notice, and nobody was measuring the waiting because nobody owned it.
Everyone invented their own way
Three project managers, three methods, three spreadsheets. All of them sensible. None of them the same, so nothing could be automated and nothing could be compared.
The rebuild
One spine.
Judgement where it counts.
Not a restructure. Nobody left. The work was rearchitected around the people who were already doing it.
As it was
- Enquiry logged by hand in a shared inbox
- Proposal rebuilt from scratch each time
- Won work retyped into the project tool
- Status chased in meetings, weekly
- Resourcing decided from memory
- Invoice raised from a spreadsheet at month end
- Margin known a month after the job closed
Rebuilt
- Enquiry captured once, structured on arrival
- Proposal assembled from the same record
- Won work becomes the project, no retyping
- Status is a state the system already knows
- Resourcing shown against real capacity
- Invoice raised from the delivered work itself
- Margin visible while the job is still running
What the system took
Copying, chasing, reconciling and reporting. Everything that had one right answer and no judgement in it. None of that work was anybody's job description, and none of it was missed.
What the people kept
Scoping the work. Pricing risk. Reading a client. Deciding what to do when a project turns. The parts that were always the reason to hire them, and never the parts that filled their week.
What it moved
The week changed
before the numbers did.
The range across the processes we have rebuilt. Where it lands depends on how much of the work was manual before we started.
Once the engine can carry the volume, the commercial side is the constraint. This is the range when both are rebuilt together.
These are ranges, not averages, and we do not print a midpoint. Where a specific business lands is the honest answer only after the read.
How it ran
Four steps.
One conversation to start.
A bird's-eye view of the business, the future vision, and what is actually possible. No obligation, and no methodology talk.
One connected read of the whole business, or of a single function. Collection is light, because one agent sits with everyone at once.
The right seats read it together and connect the dots. Aneal chairs it and stays accountable.
The next step
Let's talk about
your engine.
What is possible. What is not. What we can build. Then you decide if the MAP is the right next step. One conversation, and you will know more about your own business than you did an hour before.