Tom built his Telecoms business from the ground up. Eight people four years ago. Twenty today. Three carrier wholesale relationships, a growing base of business customers, and a sales pipeline that is finally starting to look the way he always imagined it would.
There is just one thing he has not looked at directly.
The back office runs the way it did when there were eight of them. The provisioning process. The onboarding handoff. The way installation updates get tracked. The billing reconciliation. None of it was ever redesigned for twenty people. It just stretched — quietly, incrementally — to cover the extra load, the extra customers, the extra carriers.
It is still working. Mostly.
This is the position most UK resellers find themselves in after a period of meaningful growth. Nobody redesigns the back office while they are growing. They are too busy growing. The processes that exist keep things moving, people adapt around the edges, and the structural question — does this still make sense at this size — never quite gets a dedicated hour in the calendar.
The result is a business running two versions of itself simultaneously. A front end that reflects where it is now. A back end that reflects where it was.
It works, until it doesn't.
Here is the uncomfortable reality every reseller MD knows but rarely says out loud: the processes that carried the business from eight to twenty people are not the ones that will carry it from twenty to thirty. They will either be redesigned or they will break. The only variable is which one happens first.
This is not pessimism. It is mechanics. A process built around eight people has a certain tolerance. Load it with twenty people's worth of volume, add more carriers, more concurrent installations, more customers going through onboarding simultaneously — and the failure modes that were always there start producing visible outcomes.
The question is not whether the process will break. It is whether you are the one who chooses the timing.
What Outgrowing the Process Actually Looks Like
The signs tend to appear gradually, and they tend to get attributed to the wrong cause.
Provisioning errors start appearing more frequently. Not because the team has become less careful — because the same process that one person managed easily is now shared across three, and the handoffs are unclear.
Onboarding slows down. New customers wait longer than they used to for services to go live. The ops team is stretched, and the informal system that worked at eight people relies on one person knowing where everything is.
Billing queries increase. Small discrepancies that were caught quickly when the finance person knew every account by name are now slipping through, because there are too many accounts to hold in one person's head.
A senior staff member takes a week off, and things that would normally just happen require the MD's input instead. Not because the person was doing anything extraordinary — because the process lived in their head, and without them present, nobody else quite knows how it works.
None of these feel like a back office crisis. They each feel like a bad week. But pattern them across six months of growth and they are not bad weeks. They are a process telling you it has reached its limit.
The Cost of Waiting
There are two ways to redesign a back office. Before the pressure, and under it.
The difference in cost between these two paths is significant — and not just in money.
Before it breaks: The MD has the space to map processes properly, while the people who run them are available and not in crisis mode. Redesign work can run in parallel with live operations. New workflows can be tested without disrupting customers. Staff can contribute to the design rather than just being told what changed. The cost is bounded, the timeline is controlled, and the outcome is a back office built for the next chapter, not patched for the current one.
After it breaks: The timing is no longer the MD's to choose. The trigger is usually a specific, visible failure — a customer affected by a billing error, a missed SLA, a provisioning gap that caused a complaint. The redesign now happens under pressure, with staff in firefighting mode rather than design mode, and with at least one customer already aware that something went wrong. The cost is higher because the urgency is higher, the scope is harder to control, and the disruption to live operations is unavoidable.
Most resellers who fix their back office under pressure spend more, take longer, and end up with a less coherent result than those who did it before the crisis arrived.
The resellers who fix it proactively do not do so because they are more disciplined. They do so because at some point they stopped treating growth as the justification for deferring the conversation, and started treating it as the reason to have it.
What Redesigning Actually Involves
The phrase "redesign the back office" sounds like a large, disruptive project. For most resellers it is not.
The processes that need to change are usually well understood by the people who run them. The provisioning coordinator knows where the tracking breaks down. The finance person knows where the billing reconciliation loses time. The installations manager knows which part of the onboarding handoff produces the most errors. The knowledge exists inside the business already.
What it typically lacks is a structured way to surface it, prioritise it, and address the highest-impact points first without trying to rebuild everything at once.
The starting point is almost never a full process overhaul. It is identifying the two or three workflows that are generating the most friction at current volume — the ones that will produce the most visible failures as the business adds the next five customers per month — and fixing those first.
Done in that order, the back office redesign is not a disruption to growth. It is the thing that makes the next phase of growth possible.
Summary
Getting from eight to twenty people is a genuine achievement. The back office that carried you there deserves some credit.
It is also not the back office that will carry you to thirty. At some point the processes designed for a smaller, simpler version of the business will reach the end of their tolerance — and when they do, the cost of fixing them under pressure will be higher than the cost of fixing them now.
The resellers who grow cleanly through the next phase are not the ones with the most sophisticated systems. They are the ones who looked honestly at what they had built, identified where it was already straining, and addressed it before it became a crisis.
The window between "we've grown" and "something has broken" is not a reason to wait. It is the window to act.
If your business has grown faster than the back office has kept up, the Reseller Ops Roadmap is the right starting point. Fixed scope, fixed fee, and the output is yours — a prioritised map of where the process is straining and what to fix first.
Book a Roadmap conversation: aideal.group
Thanks for reading!