Your business software is a filing cabinet with a login

Almost every piece of business software sold to a small firm is a system of record: a well-organised account of what already happened, kept accurate by people typing things into it. That model works, but it carries a hidden requirement, and the requirement is a person whose job includes the typing.

Companies with two hundred employees have that person. Firms with five do not, and the result is predictable: the system is always a few days behind reality, the spreadsheet becomes the real source of truth, and the owner ends up as the integration layer between four tools that all claim to be the single source.

What the record model assumes

That entry is somebody’s job. Not a task squeezed between calls, but work with time allocated to it.

That the record is worth its own maintenance. True at scale, where reporting drives decisions. Much weaker at five people, where the owner already knows what happened this week without needing to query it.

That accuracy is a discipline problem. So the vendor adds required fields, validation and reminders — all of which increase the cost of entry and therefore make the record less current, not more.

That last one is the trap. Every feature added to protect data quality raises the price of keeping the data, which is why small-firm systems degrade fastest exactly where the vendor tried hardest.

What acting instead of recording means

A system of action starts from the same information and goes the other direction. Instead of waiting for you to enter the invoice, it notices the job closed, drafts the invoice, and asks whether to send it.

Concretely, the difference looks like this:

Record: a form for a new quote, with fields for customer, scope, materials and price. Action: a drafted quote built from the email thread, priced against comparable work you have already done, waiting for you to read and correct.

Record: a report showing three overdue invoices. Action: three drafted follow-ups, in your tone, ready to send.

Record: a field asking which job this supplier PDF belongs to. Action: the PDF already filed against the job, with an easy way to say it guessed wrong.

The work does not disappear. It changes from composition to review, and review is roughly ten times faster and can be done between other things — which is the only kind of time a small firm actually has.

Why this needs approval built in

An acting system is wrong sometimes. It will misread a scope, price something oddly, attach a document to the wrong job.

That is survivable when every outbound action is a draft and a person confirms it. It is not survivable when the system sends on its own, because a wrong quote to a customer costs more than every minute the automation saved that month.

So the design rule is narrow and boring: prepare everything, send nothing. It makes the software less impressive in a demo and considerably safer in a business, and it is the constraint the whole thing is built around rather than a setting you can turn off.

The test

Take the last thing your software asked you to type in. Ask whether it could have known.

Usually it could have — from the email that arrived, the job that closed, the document already uploaded. That gap between what the system knows and what it makes you tell it is the entire opportunity, and it is much larger in a small firm than in a large one.