The brief
A recruitment agency in the South East. Twenty years in business. Good reputation. Solid client base. Growing steadily. But the founder was still involved in almost everything.
They did not need more clients. They needed the business to function without the founder being the glue that held it together.
The mapping exercise
We sat down with the founder and two senior team members for half a day. The goal was simple: document every step of the customer journey from first contact to placement fee being paid.
It took longer than expected. Not because the process was complicated, but because nobody had ever written it down. Each person had a slightly different version of how things worked. Steps that one person thought were critical, another had never heard of.
The final document was 23 pages long.
That alone was worth the exercise. For the first time in 20 years, everyone in the room could see the entire business laid out in front of them. Every handoff, every decision point, every place where something could go wrong.
What we found
Three things stood out immediately.
First, there were 14 steps that existed purely because two systems did not talk to each other. Data was being copied from one tool to another by hand. Every day. This was not complex data transformation. It was literally copying a name and email from one screen to another. The kind of thing that takes 30 seconds each time but adds up to hours every week.
Second, follow-up timing was entirely based on memory. Candidates were falling through cracks not because nobody cared, but because nobody had a system telling them when to follow up. A good candidate could sit in the pipeline for two weeks without contact, not through neglect but because the consultant was busy with 40 other candidates and no automated reminder.
Third, the founder was the single point of failure for client communication. Not because the team was not capable, but because there was no documented process for how to handle each scenario. So everything got escalated. The founder was spending three hours a day on emails that the team could have handled with the right playbook.
What happened next
We did not automate everything on day one. We started with the 14 data-copying steps. Those were pure waste. Connecting their CRM to their ATS eliminated all of them in the first week.
Then we built the follow-up sequences. Automated reminders at the right intervals based on where each candidate sat in the pipeline. The team stopped missing follow-ups overnight.
The founder delegation piece took longer. We built process documents for the five most common client scenarios and set up a system where the team could handle them independently, with the founder only being pulled in for genuine exceptions.
The result
Three months later, the founder took a two-week holiday. First one in four years. Nothing broke.
The team made decisions using the documented processes. The automations kept candidates moving through the pipeline. Client communication continued without interruption.
Revenue actually increased that month because the team had more time to focus on placements instead of admin.
What you can take from this
You do not need 20 years of accumulated process debt for this to be relevant. If you are the person everyone comes to with questions, if your team cannot function when you are out of the office, if you have never documented how your business actually works, then this story is about you too.
The mapping exercise takes half a day. The document it produces will show you exactly where your time is going, where things are falling through the cracks, and where the quickest wins are. Every business we have mapped has found at least one thing that could be fixed in the first week.
Common questions
How long does a process mapping exercise take?
Half a day for most businesses. You need the founder and one or two senior team members in the room. The output is a complete document of how the business works, from first customer contact to final invoice.
What if our business is smaller than a 20-year-old recruitment agency?
Size does not matter. We have mapped businesses with three people and found the same patterns: disconnected systems, follow-ups based on memory, and the founder as the single point of failure. The document is shorter. The problems are the same.
Do we need to fix everything the mapping reveals?
No. The mapping shows you everything, but you fix things in order of impact. Start with the quickest wins. For this client, that was the 14 data-copying steps. For your business, it might be something completely different. The mapping tells you where to look.
