Thirty People, Five-Person Processes: The Cost of Systems That Did Not Grow

The tolerated pain

When the business had five people, everything worked. Everyone sat within earshot. Orders were discussed over coffee. The owner approved every quote, knew every client and remembered which supplier was late last time. Leave was tracked on a wall calendar. Stock was "whatever is in the storeroom". There was no need for written processes because everybody could see everything.

Now the business has thirty people, two sites and a sales team on the road. The processes are the same. Orders still depend on someone mentioning them. The owner still approves every quote, now from a phone at 10 p.m. Information still lives in heads, WhatsApp groups and a few spreadsheets. The business has grown; its operating system has not.

This is related to, but different from, the problem described in when every rise in workload needs another hire. That article is about repeatable work that grows in proportion to volume. This one is about coordination: the informal ways of knowing, deciding and handing over that only work at small scale.

Why informal processes stop working

The arithmetic of coordination is unforgiving. Five people have 10 possible one-to-one communication paths. Thirty people have 435. Informal processes depend on those paths carrying the right information at the right time, and the number of paths grows far faster than headcount.

At the same time, growth brings formal obligations. SARS's VAT registration page states that registration is compulsory once taxable supplies exceed R2.3 million in any consecutive 12-month period. Employing people brings PAYE duties: SARS's PAYE page describes monthly EMP201 declarations, payment within seven days after month-end, and annual EMP501 reconciliations, with penalties for late reconciliation. Processes designed when none of this applied struggle to produce accurate, timely records once it does.

Why businesses tolerate it

• The old way still mostly works. Failures are occasional, so each one looks like bad luck rather than a design problem.
• The owner is the safety net. When something slips, the founder catches it, which hides how much depends on them.
• Formal process feels corporate. Owners fear that writing things down will slow the business and lose its culture.
• Nobody has time to redesign. The people who understand the processes are the busiest people in the business.
• Growth is the priority. Every rand and hour goes to sales and delivery, not to how work moves.

Operational symptoms

• the owner as the approval point for quotes, discounts, purchases and exceptions;
• staff asking "who handles this?" because responsibilities were never written down;
• WhatsApp groups doing the job of a job board, an order system and a customer record;
• the same mistakes recurring, such as wrong prices, missed deliveries or duplicate orders;
• new employees taking months to become effective because nothing is documented;
• month-end and payroll depending on one person's spreadsheet.

How the pain becomes money

• Coordination cost: paid hours spent asking, checking, chasing and re-explaining.
• Error and rework cost: mistakes from information that was not passed on or was passed on wrongly.
• Owner bottleneck: decisions queue behind one person, slowing sales and delivery and limiting how much the business can take on.
• Scaling cost: each new hire adds more coordination load than capacity.
• Compliance risk: VAT, payroll and employment records that depend on informal processes are more likely to be late or wrong.

Secondary consequences

Some costs are harder to put a number on but matter just as much. Capable employees leave when they spend their days chasing information instead of doing skilled work. Customers notice when they have to repeat themselves or receive conflicting answers from different people. The owner loses the time needed to think about pricing, new markets or key clients, because the day is consumed by routine approvals. And the business becomes harder to sell or finance, because a buyer or lender sees an operation that depends on a few individuals rather than on repeatable processes.

An illustrative cost model

This example is illustrative. Every figure is an assumption for a hypothetical business. Picture an East Rand fabrication business that has grown from six to 32 employees in four years.

• Coordination time: 25 × 2 × R220 × 46 = R506,000
• Rework: R12,000 × 12 = R144,000
• Owner time on routine approvals: 8 × R1,000 × 46 = R368,000
• Illustrative total: about R1.02 million a year

Some coordination is necessary, so the full amount is not recoverable. The more important point is direction: on informal processes, these figures rise faster than headcount. Measure your own version by asking staff to log, for two weeks, the time they spend finding out what to do next.

When it becomes commercially urgent

• the owner is the limiting factor on how much work the business can accept;
• a second site, a large contract or a new product line is planned;
• the business crosses the compulsory VAT threshold or adds significant payroll;
• a key early employee leaves and takes the process knowledge with them;
• errors start reaching customers regularly.

What better looks like

The answer is not to formalise everything. It is to redesign the few processes that carry the most money and risk.

1. Identify the core flows. Usually quote to order, order to delivery, delivery to invoice, and hire to payroll.
2. Give each flow an owner. Someone other than the founder, with authority to change it.
3. Write down the steps and handoffs. One page per flow is often enough.
4. Move the flow into a shared system. Work should be visible in a record, not in a WhatsApp thread.
5. Delegate approvals with limits. Discounts up to a threshold, purchases up to an amount, without the owner.
6. Use data to see the real process. Once work runs through systems, tools such as process mining can use event data to show how processes actually run and where bottlenecks sit.

The Insights article why growth breaks systems that worked when the business was smaller explains the pattern, and how to map a business workflow without making it complicated is a practical starting point.

Practical next actions

1. List every decision the owner made last week and mark which could be delegated with a simple rule.
2. Pick the one process that causes the most customer-facing errors and map it on a single page.
3. Name an owner for each core flow and agree what they can change without permission.
4. Move one WhatsApp-run process into a shared system with clear stages.
5. Check that VAT and payroll records come from systems, not one person's spreadsheet.
6. Repeat for the next process every quarter.

Bottom line

Informal processes are an asset when a business is small and a liability when it is not. The cost arrives gradually, as hours spent asking and checking, as recurring mistakes, as compliance pressure and as an owner who has become the bottleneck. Redesigning a handful of core processes for the business you are now, rather than the one you were, is how growth stops making the business harder to run.

Sources and further reading

• Register for VAT - South African Revenue Service (last verified 10 October 2026)
• Pay As You Earn - South African Revenue Service (last verified 10 October 2026)
• Overview of process mining in Power Automate - Power Automate (last verified 10 October 2026)

Related Mellorca reading

• The Human Dispatcher: The Cost of Manually Routing Every Incoming Request
• When Every Decision Waits for One Person: The Cost of a Decision Bottleneck
• "That's Just Admin": The Payroll Cost of Processes Nobody Ever Redesigned