← The journalVISION / OPERATIONS

One system of record: why spreadsheets break at 20 people

Spreadsheets carry a small company a long way. Here is where they start to fail, and how to move to one system of record without a big-bang project.

Glass facade and people with directional camera-motion blur.VISION / SUNDIAL
Photography: Vincent Tint / Unsplash ↗ · Sundial motion treatment
THE PRACTICAL TAKEAWAY

When more than one person needs the same number to make a decision, that number belongs in a system of record, not in a file someone emailed last Tuesday.

How the spreadsheet stack forms

Almost every company begins with spreadsheets, and that is sensible. A founder tracks orders in one sheet, stock in another, and hands invoices to an accountant who keeps the books in a desktop package. Each file is simple, fast and owned by one person.

As the team grows, the files multiply. Sales keeps its own customer list. The warehouse keeps a stock sheet that it updates when it remembers. Purchasing keeps a supplier tracker. Somebody builds a master sheet that pulls from the others, and it works until the day a column is inserted in the wrong place.

Where it breaks

The first failure is disagreement. Sales promises stock that the warehouse shipped yesterday. Two people answer the same customer question with different numbers. Meetings start with a reconciliation of whose file is right.

The second failure is the missing link between documents. In a spreadsheet, an order, a delivery and an invoice are separate rows in separate files. Nothing guarantees that every delivery was invoiced, or that every invoice matches what was actually shipped. Leakage is quiet: an unbilled delivery here, a duplicate payment there.

The third failure is history. A spreadsheet shows the current value of a cell, not who changed it, when, or why. When a stock count is wrong, there is no trail to follow.

Why it happens around twenty people

There is nothing magic about the number twenty; it is a rule of thumb. The real threshold is when the people who enter information and the people who rely on it are no longer the same people, and no longer sit within earshot of each other. Below that point, conversation fills the gaps between files. Above it, the gaps become errors.

Other signals arrive around the same time: a second warehouse or location, a first production run, a customer who asks for statements, an auditor who asks for a trail, or a lender who asks for monthly accounts on a deadline.

What a system of record actually means

A system of record is the place where a fact is created once and everyone else reads it from there. A sales order is entered once; the warehouse picks from it, the invoice is made from it, and the accounts are updated by it. Stock moves only through documents, so the stock figure is always the sum of real transactions.

It also means every change has an owner and a timestamp, permissions decide who can see and change what, and reports are views of the same records rather than separate copies. Spreadsheets remain useful for analysis; they stop being the source.

What to expect in the first months

The first weeks feel slower. People who could update a cell in seconds now fill in a document with required fields and links to other records. That friction is the point: it is the system refusing to accept a stock movement without a reason, or an invoice without a customer. Keep the required fields to what genuinely matters so the friction stays small.

Expect old disagreements to surface. When stock moves only through documents, the first proper count will show differences that the spreadsheet had been quietly absorbing. Treat that as the system doing its job, adjust once with a clear note, and watch the differences shrink as people learn that every movement now has to be recorded.

The payoff shows up in meetings. When everyone reads the same numbers, the conversation moves from whose figure is right to what to do about it.

Moving off spreadsheets in stages

Start with the records everyone argues about: customers, suppliers, items and opening stock. Clean them once, import them, and make the system the only place they are edited.

Then move the flows that touch money and stock, usually sales orders through invoicing, and purchase orders through supplier bills. Run the old sheet in parallel for one cycle if it helps confidence, then retire it. Add manufacturing, projects or support once the core is settled.

Sundial is built for this path. The modules share one database, so a customer created in Sales and CRM is the same customer in Finance and Support. Each company runs on its own dedicated instance, and because Sundial is built on open-source Frappe and ERPNext, your records remain exportable if you ever choose to leave.