The Owner Who Can't Decide Without the Spreadsheet Wizard

The owner has a decision to make. Whether to take on a second delivery vehicle, whether to give a regular customer longer payment terms, whether the business can afford to hire before the busy season. The information needed to decide exists. It sits inside a workbook that one person built, understands and maintains. So the decision waits until that person is free, or back from leave, or has had time to "run the numbers".

Nobody would describe this as a crisis. The person who built the workbook is usually capable and trusted. And yet something quiet has happened: the person who carries final responsibility for the business cannot form a view on their own business without going through someone else.

This piece is about that quiet thing. Not the spreadsheet itself, which Mellorca has written about as a business-critical system hiding in a file, and not the labour of rebuilding reports, which is the subject of the report someone rebuilds by hand every Friday. It is about what this arrangement takes from the owner, and from the person who has become indispensable.

How a helpful workbook becomes a gatekeeper

Most of these workbooks start well. Someone needs to understand margins by customer, or cash coming in over the next six weeks, and the accounting system does not show it the way they need. They export some data, add a few formulas, and the answer appears. It is useful, so it is used again. Then it is extended. A tab for stock, a lookup, a macro. Over a few years it becomes the place where the business's real picture lives.

Along the way, three things tend to happen without anyone deciding them:

The logic moves into one head. Which tab feeds which, which rows must be deleted after an export, which customer codes are excluded and why. None of it is written down because the builder never needed it written down.
The inputs depend on a manual routine. Someone has to pull the data, paste it in the right place and check it looks sensible. If they do not, the figures are simply old.
The questions route through the builder. Even when the owner can open the file, they cannot be confident they are reading it correctly, so they ask.

That last point is the important one. The constraint is not access to a file. It is confidence in what the file says.

The human tax on both sides

For the owner, the tax is autonomy. They cannot test an idea on a Sunday afternoon, or answer a bank manager's question in the meeting, or think through a supplier's offer while it is still on the table. Their pace of decision-making is set by someone else's diary. Some owners will feel this as frustration; others will hardly notice it until the builder is away. It would be wrong to assume one reaction. What can be said is that the dependency narrows the moments in which the owner is able to act.

For the builder, the tax is different. Being the only person who understands the numbers can bring status, but it can also mean never being fully off duty. A leave request becomes a question of which decisions will be held up. A sick day becomes a phone call. The person can become known for the workbook rather than for their judgement, and their own development may stall because nobody else can take the routine work from them. Mellorca has looked at the wider version of this in the cost of key-person dependency.

There is a confidence tax too, and it is shared. When the figures cannot be checked by anyone else, both people carry a low-level uncertainty: the owner about whether the number is right, the builder about whether they will be blamed if it is not.

What larger organisations learned the hard way

Public bodies have faced a version of this problem at much larger scale. In 2013 HM Treasury published a review of quality assurance of the analytical models that inform government policy, led by its Permanent Secretary, setting out best practice and recommending steps to make sure models are robust and trustworthy. The guidance that followed, the AQuA Book, was updated in July 2025. It describes separate roles for the person who commissions analysis, the analyst who builds it, an assurer who reviews it, and an approver who confirms it has been assured, and it states that the analyst and assurer roles should be separate.

A twelve-person South African business does not need four roles and a governance framework. But the principle travels well: analysis that drives significant decisions should not depend on a single person being both the only builder and the only checker. Separating those roles, even informally, is what lets other people rely on the result.

An illustrative example

Consider an illustrative case: a Pretoria building-supplies distributor with about twenty staff. The bookkeeper has, over six years, built a workbook that combines the accounting export with stock levels and outstanding orders. It produces the only reliable view of cash for the next month. The owner meets the bank every quarter and decides on large stock purchases every few weeks.

In this scenario, the owner has learned to time decisions around the bookkeeper's week. When a supplier offers a discount for an early bulk order, the owner says they will come back the next day, because the bookkeeper is at month-end. By the next day the offer has gone to another customer. Nobody did anything wrong. The business simply has one route to its own numbers, and that route was busy.

What could realistically change

The goal is not to take the workbook away from the person who built it, or to replace it with something larger for the sake of it. It is to make the business's essential picture readable and trustworthy without a single interpreter.

Write down what the key figures mean. A single page explaining where each figure comes from, what is included and what is excluded. This alone lets an owner read the workbook with more confidence.
Move the file somewhere shared and versioned. Microsoft's guidance on co-authoring explains that workbooks stored in OneDrive or SharePoint Online can be opened by several people at once, with version history that lets earlier versions be restored. That does not fix the logic, but it ends the situation where the only current copy lives on one laptop.
Automate the inputs where the source system allows it. Reporting tools can pull data on a schedule. Microsoft's documentation for Power BI, for example, notes that models on shared capacity can be refreshed up to eight times a day on a schedule. The point is not the tool; it is that figures stop depending on someone remembering to paste.
Introduce a second pair of eyes. Ask someone else to check the main outputs once a month against the source system. This is the small-business version of separating the builder from the checker.
Teach the owner to answer three questions alone. Pick the questions that most often wait. Make sure the owner can answer them without help, and confirm they trust the answer.

Mellorca's guidance on when a spreadsheet becomes infrastructure sets out how to judge when a workbook needs this kind of treatment.

What changes first, and what it gives back

The first visible change is small: a question that used to take a day takes ten minutes, and nobody has to be interrupted to answer it. The business outcome follows from that. Decisions that depend on timing, such as supplier offers, credit requests and stock buys, can be taken while they are still available.

The human dividend is autonomy for the owner, and predictability for both people. The owner can think about their business on their own schedule. The builder can take leave knowing that the numbers will still be there and still be understood.

The trade-offs

This change is not neutral, and it should not be presented as if it were.

The builder may feel displaced. Being the only person who understands something can be part of how someone sees their value at work. Opening it up needs to be done with them, not around them, and their expertise should be acknowledged rather than quietly absorbed.
Documentation takes time. Writing down logic that lives in one head is real work, and it competes with everything else.
More access can mean more misreading. An owner who reads figures alone can also misread them alone. A shared definition page and a periodic check reduce, but do not remove, that risk.
New tools add their own dependency. Moving to a reporting platform can simply shift the single point of knowledge from the bookkeeper to whoever configured the platform.

Why it matters

It is easy to treat this as a reporting problem with a reporting solution. The human side is more basic. An owner who cannot see their own business without help has less room to think, and a valued employee who cannot step away has less room to live. Neither condition was chosen. Both grew out of a useful file that nobody ever decided to share properly.

Mellorca's reading is that the most valuable change here is often modest: clear definitions, a shared and versioned file, automated inputs where possible and a second checker. Those steps return the ability to decide to the person responsible for deciding, and the ability to rest to the person who has been carrying the numbers.

Sources and further reading

The AQuA Book (last verified 10 October 2026)
Review of quality assurance of government models (last verified 10 October 2026)
Collaborate on Excel workbooks at the same time with co-authoring - Microsoft Support (last verified 10 October 2026)
Data refresh in Power BI - Power BI (last verified 10 October 2026)