What does a CRM actually do for a trade business?
It holds one record of a job from the first phone call to the money landing, so nothing is retyped and nothing falls between tools. The value is not the contact list. It is that the quote becomes the job, the job's hours and materials become the invoice, and the certificate the law requires comes out of the same record rather than a separate folder.
Every state below produces something the next one needs. That is the part a generic CRM cannot model, and the reason the workaround is usually a spreadsheet nobody else can read.
Four places off-the-shelf software runs out
None of this is a criticism of those products. They are built for a general case, and a trade business is a specific one.
Compliance with a statutory deadline
An electrical certificate has to reach the customer inside 20 days and be kept for 7 years, and it has to carry the issuing worker's registration and licence class as at the moment it was issued. A notes field does not do that. A calculated deadline on a dashboard does.
A job that carries its own margin
Labour and materials booked as they happen, at cost and at charge-out, so the job shows revenue, cost and margin without anyone reconciling anything afterwards. Most tools can tell you what you invoiced. Far fewer can tell you what it cost you.
A price list a supplier increase flows through
Lines priced from the current sell price at the moment they are inserted, so a price rise reaches new quotes without editing every product, and never rewrites a quote already sent.
What the customer is allowed to see
Your internal breakdown and the customer's copy are different documents built from the same record. Handling that with two spreadsheets is how a cost price ends up in front of a client.
One setting, two documents.
Customisable is the emptiest word in software sales, so here is a real setting changing a real document rather than a claim that it could.
The total and the GST are always shown, because a tax invoice has to state them. The choice is saved onto the document when it is raised, so changing the setting later never rewrites an invoice you have already sent.
What it looks like in use.
Drawn rather than screenshotted, because no client has cleared their data for publication and a drawing stays accurate when an interface changes.
Six decisions that decide whether you can trust it in three years
These are not features. They are the things that stop a system quietly corrupting its own records, and they are chosen before a line of the interface is drawn.
Money is never a floating point number
Amounts are held as whole cents, quantities as thousandths, tax rates as basis points. A rounding error in an invoice total cannot happen, because there is nothing to round. A document discount spreads across lines and the remainder lands on the last taxable line, so line tax always sums to header tax.
An issued document cannot be quietly edited
Only drafts change. A sent invoice is corrected with a credit note or voided, and voiding releases that job's labour and materials so they can be billed again. Your records stay defensible because history is not rewritten.
An invoice cannot be orphaned
Every invoice is tied to a client at the database level, and a client with invoices, jobs, quotes or certificates cannot be deleted. Deactivate them instead. There is no path that leaves money attached to nobody.
A template stops being a link once used
Inserting a product copies its lines into the document. Editing that product next month leaves every quote and invoice already raised exactly as it was, which is the opposite of what most systems do and the reason old documents stop matching what was agreed.
Customer links are unguessable and scoped
Portal links are 24-byte tokens, so a client can open an invoice or accept a quote without an account. Drafts and voided documents are never reachable through them.
Authorisation is enforced on the server
Every action checks the user's role before it does anything, not just the button that triggered it. Hiding a control in the interface is not security, and a system handling compliance records should not pretend otherwise.
Not sure whether your work needs this or whether an off-the-shelf tool already covers it? That is a fifteen minute conversation, and we will tell you either way.
Build, or buy?
The honest version. There are more reasons to buy than to build, and we would rather say so now than three months into a project.
| Buy off the shelf | Build it | |
|---|---|---|
| Your work fits the standard model | Yes, do this | No reason to |
| You need it working this month | Yes | No |
| Compliance artefacts with deadlines | Usually a notes field | Modelled, calculated, watched |
| Running three tools plus a spreadsheet | The spreadsheet is the tell | This is the case for building |
| The workaround is now the process | Costly and invisible | The thing worth fixing |
| The work is worth less than the build | Yes, stay put | Worth talking about |
Questions, answered.
Tell us what your current workaround is.
That is usually the whole brief. Fifteen minutes, and we will tell you honestly whether this is worth building or whether something off the shelf already does it.
Book a 15-minute demoNo commitment. No pitch deck. Just 15 minutes.