We did not set out to build software.

Four things kept happening

They happened in almost the same order, in almost every brand, from the third store onward — whether the group stopped growing at a dozen locations or kept going toward a thousand. That is the range where a spreadsheet stops being enough, and it does not stop mattering as the estate gets bigger — if anything, the same blind spots just get more expensive to carry.

One. The number always arrived too late.

Close the month. Wait on the accountant. Receive a profit and loss statement somewhere in the third week of the following month. By the time it lands, the labour overrun that ate the margin is forty-five days old. The schedule that caused it has been worked, paid and filed. You are reading a description of a month nobody can change any more.

That gap is not a reporting inconvenience. It is the distance between a decision and its consequence, and at six weeks it is long enough that the two stop feeling related at all.

Two. Nothing was missing. It was just scattered.

Sales sat in the POS. Hours sat in payroll. Invoices arrived as PDFs in somebody's inbox. And every Monday, a person rebuilt a spreadsheet to tie the three together — the same person, the same five to ten hours, every week, forever.

None of the data was actually absent. It simply never existed in one place at one time, which for an operator is the same thing as not having it.

Three. Every store looked fine on its own.

This is the one that decided it. A location can look entirely reasonable in isolation and still be the worst store you own. Without a common denominator across locations — the same definitions, the same period, the same page — the question “which store is the problem this week” quietly turns into “whichever store complained most recently”.

Four. The people closest to the cost could not see it.

The general manager writes the schedule that becomes the labour line. But the labour line lives in a report only head office reads, arriving weeks later. Give somebody responsibility for a number and then hide the number from them, and you have not delegated anything. You have just moved the blame.

So we stopped explaining the problem

We built the answer instead, and we built it in the order the problem actually bites.

First, one number, on time. An estimated profit and loss you can see the same morning — not exact to the cent, but directionally right and available while the period is still open. A rough number today beats a perfect number in six weeks, because only one of them can still be acted on.

Then, the reason behind the number. When labour only covers part of the hours worked, the page says so, in plain language, instead of quietly reporting a flattering percentage. A number you cannot interrogate is a number you will eventually stop believing.

Then, the ability to act. Budgets, schedules, inventory counts and vendor costs in the same place as the reporting — because seeing a labour overrun in one system and fixing it in another is how the fix gets postponed to next week.

Then, the right view for the right person. One login, three altitudes. A store manager sees their store. An area manager sees their region. Only the executive sees everything. Set once on the role, inherited by everyone who holds it.