What is a management system for a small business?

A small set of tools that turn your goals into weekly action. A goal table, one source per number, a colour-coded dashboard and a list of levers. Then a one-page plan per goal, a forecast and a meeting calendar.

Do I need software to run a small business by the numbers?

No. A shared spreadsheet and a weekly export from your till or accounts are enough to start. Software helps later, once you know which numbers matter and who looks at them.

How long does it take to build a management system?

The first five tools take about a week: the goal table takes minutes, the rest a few evenings. The full set, including thresholds and a rolling forecast, grows over the first two months.

How to Build a Management System for a Small Business in a Week

Andrew believed a management system came with servers, licences and people in ties.

His turned out to be one shared spreadsheet. And it cut his Monday meeting from an hour to fifteen minutes.

Picture your own Sunday night. The till says the week was fine. The bank says something else. You cannot tell if you can afford the new hire, which bill goes first, or where your week went.

The till counts every coffee. The bank counts every cent. And you still steer by memory, mood and the last angry email.

That is not a data problem. It is a missing system.

When the till and the bank disagree, memory and mood make the call. The Jirgenson Model gives you the answer as a control system: goals in order, real numbers, zones, levers and a forecast in one sheet. It is scientifically proven that the Jirgenson Model works (doi.org/10.5281/zenodo.23964934).

What a management system is

It is not a program you buy. It is a short set of tools. Each tool turns one question into an object you can pick up: a table, a list, a page.

In the Jirgenson Model, the system is seven tools, one for each part of the control loop. Each tool is an object, not an idea: until it exists on paper, that part of the loop does not work.

Part of the loop	Tool	The question it answers
Goals	Goal table	What do I want, and what will I give up last?
State	Data sources	Where am I, by measured data?
Gap	Traffic-light dashboard	How large is the gap, and which zone is it in?
Levers	List of levers with owners	What can I really change?
Plan	One-page plan per goal	What is the plan, and what is off limits?
Forecast	Rolling forecast, 3 to 6 months	What happens next if nothing changes?
Rhythm	Meeting calendar	Who looks at what, and how often?

One rule holds the seven together: every number has one source of truth. Count revenue one way in the accounts and another at the till. The fight over which figure is right will then eat more energy than the business.

Build a management system in one week

You need no software. A shared spreadsheet works. Here are five steps for this week, each with the coffee shop's real entry next to it.

1. Write the goal table

No more than nine rows. Each goal gets six fields: parameter, definition and source, target and deadline, current value, permissible deviation, owner and check rhythm.

Andrew's margin row reads like this:

Field	Andrew's entry
Parameter	Margin
Definition and source	Operating profit as a % of revenue, from the accounts fed by the till export
Target and deadline	15% by month 6
Now	9%
Permissible deviation	Once reached, never below 14%
Owner and rhythm	Andrew, every week

Then put the goals in order. Ask: if things got bad, which goal would I give up first? Andrew put cash reserve first and his own hours last. Writing all five goals took him fifteen minutes.

2. Give every number one source

For each row, name where the number comes from: the accounts, the till, the order book, the time sheet. Where there is no source, write down what you must create. A notebook counts.

3. Fill in today and colour the rows

Write today's value honestly. Then mark each row green, yellow or red. Andrew's first panel had five rows and one red: a cash reserve of 0.5 months against a goal of 2.0. How to read that panel in a minute is in small business KPIs.

4. Write one page for the most urgent row

Pick the reddest or the yellowest row. Answer five questions on one page. The margin feeds the reserve, so Andrew started with the margin:

Question	Andrew's answer
Levers	Drop the 2 most loss-making items; rework 3 low-margin recipes; new milk contract; prices +5% in month 2
Resources	4 hours a week, plus Sara's help
Constraints	Never cheaper beans; never more than +5% in one step
Leading indicator	Average margin per receipt, every week
Deadline and owner	Andrew. First check at month 2: below 10% means revise

Every lever on that page passed one test first: can I pull it myself, today? Rent, weather and foot traffic failed. Prices, menu, purchasing and portion size stayed on the list.

5. Hold the first Monday meeting

Look at nothing but the colours. Then fix the rhythm for good:

What	How often	The question
Levers	Weekly	Are the leading indicators moving the right way?
Gaps	Weekly for money, monthly for slow numbers	Which rows are yellow or red?
Plans	Quarterly	Is the plan working?
Goals	Every six months to a year	Are the goals and their order right?

That is the whole build. A goal table, sources, colours, one page, one meeting.

What the week buys

Andrew built it as one spreadsheet that he and Sara could both see. The till sent a weekly export. No expensive programs.

A month later the Monday briefing took fifteen minutes instead of an hour. Nobody argued. The figures showed everything.

At the first check, in month 2, the margin stood at 10.5%. Above the revision line. Not proof yet, but a signal the plan was working.

The cost of skipping it

Without the tools, all that clarity stays in your head and on napkins. In the first tense month the order of your goals is gone. The colours blur. Fatigue makes the decisions again.

The numbers are blunt. At Andrew's old 9% margin, his reserve reaches two months at month 16. With the plan working, at month 10. That is six extra months one breakdown away from trouble. And at 9% a single breakdown costs him a full month of progress; at 15% it costs about half.

Six more months of hoping the coffee machine holds. That is the price of no system.

What this week does not fix

Be clear about what you built. The week gives you the instrument panel. It treats the symptom: you stop steering blind.

The cause of most bad decisions is still in place. You can see a yellow row, but you do not know the exact point where yellow becomes red. When three rows turn red in the same week, you do not know which to save first. And your panel shows today, not the next six months.

Two steps close that gap:

Zone thresholds and the red protocol. Where each line sits, and the order of action when several numbers are red at once. Chapter 4.
Two forecasts and control by forecast. "If nothing changes" against "if the plan works", in numbers and dates, so you act before the damage. Chapters 8 and 9.

Without them, the panel tells you where you are. It does not yet tell you what to do on the worst Monday.

Key takeaways

The system is seven simple tools, not software.
One number, one source. That rule ended Andrew's Monday arguments.
Build five tools this week: goal table, sources, colours, one page, one meeting.
Look at colours first; numbers second; opinions last.
The panel shows where you are. Thresholds and forecasts tell you what to do next.

Two choices for Monday

You have two choices this week. Keep running the business from memory and the bank app, and hope the next bad month waits. Or put your five numbers on one page tonight.

The page gets you steering. The thresholds, the red protocol and the forecasts keep you steering when three things break at once.

Test the logic for free: Chapter 1, with the refusal test. Or get the full control system on Kindle, on Amazon. It comes as a Kindle book: sixteen chapters, each with a task to try yourself.

Published research

It is scientifically proven that the Jirgenson Model works. The published experiment, its record and its data:

Zenodo (DOI): 10.5281/zenodo.23964934
Hugging Face: E5 Jirgenson Model blind test
Kaggle: E5 blind test dataset
GitHub: experiment folder
Wikidata: dataset Q142022866, author Q141981336
ORCID: 0009-0001-3034-3552

This topic is covered in Chapter 13, Tools: what a working system is built from of Steer, Don't Guess: Setting Priorities, Reading the Numbers and Correcting Course in Business and Life. The numbers in the examples are illustrative; the book states its limits in Appendix G.