Everything a nine-tool stack does, minus the nine bills

Customers, quotes, invoices, stock, staff, jobs, deliveries and expenses are rows in one schema rather than records in eight products with a sync job between them. There is no sync, because there is nothing to sync.

The cost of the alternative is not the subscriptions. It is that a price typed into four places is right in three of them and nobody can say which three. Margin per job, per customer and per line only exists at all when the catalogue, the invoice and the ledger are the same thing.

The boundary is enforced in code, from each tool's own classification, rather than from what the model says it is about to do. An assistant that reports its own intent is an assistant that can be wrong about it.

Two numbers sit on top of that: the most it may move in one action, and the most in a day. Both are empty when you start, and empty means zero.

Every invoice, payment, expense and stock movement posts on the date it happened. The tax return is a report over records that were already correct, rather than a fortnight spent rebuilding a year from bank statements.

This is the difference between a ledger and a folder of PDFs with a spreadsheet beside it. A document store can tell you what you sent. Only a ledger can tell you what you are owed, what you owe, and what the month actually made.

Type the business name, wait a week, and you are offered a complete copy of every table the workspace owns before anything is removed. A test fails when a new table is added without one, so the copy cannot quietly fall behind the schema.

There is deliberately no one-click export wizard, and this page says so rather than implying otherwise. The retention obligation outlives us either way, so deleting your records on request would not be a kindness.

A pack changes which findings rank first and what each officer says it is watching, in the vocabulary that trade actually uses. And the trades whose work is a register have theirs — a clinic's sealed records, a funeral parlour's cases, a herd register, a pawn book, a guest register — on the same ledger as the money.

The alternative is the configuration project every general-purpose system starts with, where six weeks go on deciding what the fields should be called before anybody has invoiced anything.

Signed quotes, delivery proof, site photos and certificates, each tied to the job and to the person. The point is the timing: evidence gathered after a dispute starts is evidence somebody assembled, and everyone in the room knows it.

What it changes commercially is the discount nobody admits to. A business without proof writes off part of an invoice to keep the relationship and books it as a discount, rather than as the cost of not having a photograph.

Every field action is written to a queue with a key the phone generated, so the same delivery confirmed twice on a bad connection is one delivery. Without that key, working offline means occasionally charging somebody twice and hearing about it from them.

The rep who loses the network between the third shop and the eleventh keeps working. What syncs when the signal returns is the queue, in order, with the keys — not a best-effort replay.

Landmark directions instead of a street address nobody uses. Cash in a rider's bag treated like a till, with a float and a reconciliation. Scheduled power cuts modelled, because where they happen they shape the working day rather than interrupting it.

These are not localisations bolted onto a product designed for one market. A system that assumes a verified street address and an always-on card terminal does not fail loudly where neither is a given. It fails by being worked around, until the spreadsheet comes back.

The commonest fraud against a small business's customers is a copy of its invoice with the bank account changed. Each document carries a code and a short address: anybody holding it opens the document as it was issued, with your official details, and a customer who is unsure asks you to confirm it before paying.

When a customer compares the account they were given and it is not yours, you are told at once — while the scam can still be stopped, rather than when somebody says they paid.

A proof of payment is set against the bank lines you bring in and read for the signs of editing. A refund of an overpayment, from money not yet seen cleared, is held. A buyer calling itself a public body from a free mail address is flagged on the quote.

None of it refuses anything. Each is said, with the facts behind it, at the moment the decision is made — the only moment a warning is worth anything.

Finished jobs with no invoice, notes that read like work beyond the quote, and stages of long jobs reached and not claimed are listed, each one tap from an invoice.

And every quote is read before it goes — the margin against your own floor, the customer's record of paying, the stock on the job date — because the expensive mistakes are made at the quote and found months later.

Assembling the competition costs more than the bill. It costs the person whose job becomes carrying figures across the gaps, usually on a Sunday, and that person is on nobody's quote.

It is also why nobody can benchmark a business like yours, cost a job properly, or tell you what your peers pay. Those answers need the numbers in one place, and in a nine-tool stack they never are.