In the 1780s, a weaver working at home could look at a mill and not see the danger. The mill had to pay for a building, for coal, for a machine, for the men who kept it running. The weaver paid for none of that. What the weaver did not count was their own labour, because it never arrived as a bill. By the time the sums were obvious the decision had already been made by someone else.
That is not a story about looms. People hold on to the way things are for a reason that has been measured in the lab: the current arrangement gets extra credit purely for being the current one, and the cost of staying put is almost never priced against the cost of moving.1 Your spreadsheet has never quoted you. The software company did. Only one of them looks expensive.
The work is not the work
Ask an owner where the day goes and you get an answer about the work: orders, deliveries, customers, staff. Watch the day instead and a different thing shows up, over and over. Somebody is typing a number into a second place.
Here is what that actually looks like in a business with a few systems:
- Yesterday’s sales, off the billing machine, into a sheet.
- A booking from WhatsApp, into the diary.
- The diary, into the roster, so the right people turn up.
- A supplier bill, into the sheet, and again into the accountant’s folder.
- The stock count, from a paper pad, into the sheet.
- The sheet, into a message, because somebody asked how the week went.
Nobody put “retype yesterday’s sales” on anyone’s job description. It is not a task. It is what falls out of having the same figure live in six places, and it is the largest single thing standing between your staff and the work you hired them for.
Your team is not slow. They are doing a second job that nobody named, nobody scheduled, and nobody is paying attention to.
The sum nobody does
Let us do it. I am going to pick numbers. They are made up, they are labelled as made up, and you should throw them away and use yours.
Say six people touch the numbers in some way. Say each one loses forty minutes a day to moving them around: a few minutes here, a retype there, two minutes finding which version is the real one. Forty minutes is a small number. Most people guess higher once they have watched a day properly.
Six people, forty minutes, is four hours a day. Twenty-two working days makes eighty-eight hours a month. Put a fully loaded cost of two hundred and fifty rupees an hour against it and you get twenty-two thousand rupees a month. Two lakh sixty-four thousand a year.
That is the number that competes with the software quote. Not zero. It was never zero. It just never turned up as a bill, so it never turned up in the decision either.
It grows with places, not with people
Here is the part that catches owners out, and it is arithmetic rather than opinion. The effort does not go up with how many staff you have. It goes up with how many places the same figure has to live.
Two places, one pair to keep in agreement. Three places, three pairs. Four places, six. Six places, fifteen. The count is n times n minus one, over two — the same counting Fred Brooks used to explain why adding people to a late project makes it later.2 Staff numbers add. Places multiply.
This is why nothing feels broken at one location and everything feels broken at three. You did not triple the business. You tripled the places a number has to live, and the checking went up by a good deal more than three.
The gap: bills you get, bills you don’t
Every business runs two ledgers. Only one of them is written down.
The first has due dates. Rent, stock, salaries, the software quote. You watch it closely, because somebody has to hand over money and somebody will chase you if you do not.
The second never turns up. The hours. The order that went out wrong because two sheets disagreed. The customer who waited while somebody looked for the right version. The decision you made on a number that was four days old. Nothing is refused, nothing is paid, the month ends, and it looks like a normal month.
The gap between those two columns is the whole of this paper. It is not that owners make bad decisions. It is that they make correct decisions using one column.
Why it stays unfixed for three years
Owners who have “been meaning to sort the stock system out” for three years are not lazy and they are not too busy. Both of those explanations are wrong in a way that matters, because they suggest the fix is discipline.
What actually happens is that motivation falls away sharply as the payoff moves further off and gets less certain.3 A system decision is the worst possible shape for a human being: the pain is now, the benefit is a year out, and nobody can promise it will work. Against that, an unpleasant task with a reward next month wins every single time, forever.
Which means the way out is not resolve. It is making the payoff nearer and more certain. That is the whole reason we start with one small thing that pays back inside a month, rather than a system that pays back after the monsoon.
Four things you can do this week, without us
- Count the places.Write down every place one figure lives — say yesterday’s takings. Count them. Then work out the pairs: n times n minus one, over two. That number is your real problem, and you now have it.
- Watch one person for one day. Not a survey, not a form. Sit with one person and mark every time they type something that already exists somewhere else. One day is enough to end the argument.
- Put a cost on it. Hours times a fully loaded hourly cost. Write the yearly figure on the same page as the software quote you have been putting off. Look at both.
- Fix the worst pair, not the whole system. Of all the pairs, one is retyped daily and gets it wrong most often. Just that one. A payoff you can see this month is what makes the next one possible.
If, after doing that, the honest figure is small — and for a business one person can hold in their head, it often is — then you do not have this problem and nobody should sell you a system. That is a real answer and it is the right one more often than our industry admits.
How this paper was made
This paper is built on arithmetic, not on a survey. Every figure in it is one we chose to show the shape of a cost, and each one is labelled where it appears. Put your own numbers in and the shape does not change.
The history and the three findings about how people judge a change are drawn from published work, cited below. We have not run a study of Indian owner-led businesses on this question. When we have, this paper gets a second edition and the numbers stop being ours.
Nothing here comes from a client. No business is described, named or implied.
On the date at the top of this page. This paper is dated 22 June 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
- Samuelson, W. and Zeckhauser, R. (1988). Status quo bias in decision making. Journal of Risk and Uncertainty, 1(1), 7–59. The experiments behind the claim that the current arrangement is over-valued simply for being current.↩
- Brooks, F. P. (1975). The Mythical Man-Month: Essays on Software Engineering. Addison-Wesley. Where the n(n−1)/2 counting of communication paths comes from.↩
- Steel, P. (2007). The nature of procrastination: A meta-analytic and theoretical review of quintessential self-regulatory failure. Psychological Bulletin, 133(1), 65–94. Motivation falls away as the payoff gets further off and less certain, which describes every system decision ever deferred.↩