ERP Systems

Nothing breaks at two branches. Everything breaks at four.

The second branch is easy and teaches you the wrong lesson. What carried you through two was you walking between them, and there is no four-branch version of that. The arithmetic underneath is old, and it is not about your staff.

What you produce grows in a straight line. What it takes to keep everyone in step grows as pairs.

n(n−1)/2

MeasuredBrooks’ counting of communication paths. Four sites is six pairs; eight sites is twenty-eight. Arithmetic, and the count of sites is yours.

Informal coordination has a hard ceiling, and walking between branches is informal coordination.

a ceiling

MeasuredDunbar’s argument that the size of a group held together without structure is bounded. The mechanism transfers; the specific number is about primates, not shops.

Which system gives way first, and at exactly which branch count.

not measured

Not measuredWe have not tracked a set of multi-site businesses and recorded the order things failed in. The ordering suggested below is reasoning, and it is labelled where it appears.

The second branch goes well. That is the problem.

It goes well because you can hold both of them. You walk in, you look at the shelf, you know the number is wrong before anyone tells you, you fix it in the corridor. Nothing is written down because nothing needs to be. The system is you, and at two sites you are an excellent system.

So you open a third, and it is harder but manageable. Then a fourth, and inside about two months everything is on fire at once: the cash does not reconcile, two branches are quoting different prices, stock says one thing and the shelf says another, and nobody can tell you which day it started.

Nothing about your staff changed. The arithmetic did.

Output adds. Coordination multiplies.

Fred Brooks worked this out about software teams, and it is one of those results that turns out not to be about software at all.1 If you have n things that must stay in agreement, the number of pairs that must be kept in agreement is n times n minus one, over two.

Two branches: one pair. Three: three pairs. Four: six pairs. Six: fifteen. Eight: twenty-eight.

Your revenue went up four times when you went from two to eight. The coordination went up twenty-eight times. Nobody planned for the second number because nobody was ever shown it.

branchesWHAT YOU PRODUCEWHAT MUST BE KEPT IN STEP21 pair33 pairs46 pairs615 pairs828 pairsit stops being carryablearound here
Both lines start together, which is exactly why the second branch teaches the wrong lesson. The gap between them is everything that feels like chaos at four.

Why walking between them stops working

What you had at two branches was not a small system. It was no system, and it worked because informal coordination is genuinely excellent up to a point and genuinely impossible past it.2 The way a group stays aligned by everyone roughly knowing everything has a ceiling, and the ceiling does not announce itself. You do not get a warning that you have crossed it. You get a Tuesday where nothing adds up.

You did not lose control at four branches. You ran out of a mechanism that had no four-branch version, and nobody told you it had a limit because it never looked like a mechanism.

What gives way first

This ordering is reasoning, not measurement, and I want that clear before you plan around it. We have not followed a set of businesses and recorded the sequence. What follows is an argument from how often each thing is touched and how fast a mistake in it becomes permanent.

  1. Cash goes first. It is touched every day, by the most junior people, at the busiest moment, and a discrepancy from Tuesday is effectively unrecoverable by Friday. There is no shelf you can go and look at.
  2. Price and promise go second. Two branches start quoting differently, or one honours something the other does not. Customers find this out before you do, and they compare.
  3. Stock goes third. It breaks loudly but it is recoverable, because the truth is physically present and can be counted.
  4. People and rosters go last.Painful, visible, and the one everybody blames first — usually while the cash problem that started three months earlier goes unnoticed.

If that ordering is right, it has an awkward consequence: the thing to fix first is the one with the least drama attached to it.

The bill for waiting

Almost everybody builds this at four branches, and almost everybody should have built it at two. The reason is not stupidity, it is that at two branches the payoff is distant and uncertain while the pain is immediate, which is the exact shape of a decision that gets deferred.3

The difference in price is large and it is not the software. At two branches you are writing down how things already work, calmly, with one person’s help, in a quiet month. At four you are doing the same work during an emergency, with staff who have lost confidence, while somebody is chasing a cash difference from six weeks ago. Same project. Completely different month.

What to do at two, if you are at two

  1. Write down the one that would be worst to get wrong. Usually the daily cash close. Not a system — a page. What gets counted, by whom, by when, and where the number goes.
  2. Give every figure one home. For each number that matters, name the place that wins when two places disagree. Say it out loud to staff. Most branch chaos is two sources and no rule.
  3. Count your pairs before you sign the next lease. Work out n times n minus one over two for the branch count you are about to have. That number is the coordination you are buying along with the rent.
  4. Test it by leaving. Take a week off. Whatever breaks is the thing that was living in your head, and now you have a list instead of a feeling.

If you are already at four, the order above is your order. Cash first, and do it before the roster, however loudly the roster is complaining.

How this paper was made

This paper is arithmetic and mechanism. The pair-counting is Brooks’ and is cited; the ceiling argument is Dunbar’s and is cited, with the caveat that his number concerns social groups and is used here only for its shape.

The suggested order in which systems fail — cash before stock, stock before roster — is reasoning from how often each is touched and how quickly an error in it becomes irreversible. It is not a measured sequence across businesses. We have not run that study, and pillar three says so.

No client is named or described. Nothing here reports a specific business’s failure.

On the date at the top of this page. This paper is dated 17 August 2026 because that is its slot in the series. The writing and the working were done on 26 August 2026, when the series was compiled and released together. We would rather say that here than have you find it in the page history.

References

  1. Brooks, F. P. (1975). The Mythical Man-Month: Essays on Software Engineering. Addison-Wesley. Communication paths grow as n(n−1)/2 while output grows in a line. No DOI is registered, so no link is given rather than a guessed one.
  2. Dunbar, R. I. M. (1992). Neocortex size as a constraint on group size in primates. Journal of Human Evolution, 22(6), 469–493. The argument that a group held together informally has an upper bound. Used here for the shape, not the number.
  3. Steel, P. (2007). The nature of procrastination: A meta-analytic and theoretical review of quintessential self-regulatory failure. Psychological Bulletin, 133(1), 65–94. Why the system that should have been built at branch two gets built at branch four, at the worst possible moment.