Two products, because two is how many we have implemented.

What this page covers, and what it refuses to

Two products assessed, because two is how many we have built integrations against. There are more in the category — Tradify, AroFlo, Fergus and others — and we have not implemented against them, so they are not ranked here.

That is a shorter page than the affiliate lists and a more useful one. A ranking that includes products the writer has never connected to an accounting package is a ranking of marketing copy — and the questions worth asking any vendor apply to whoever wrote the list as much as to the products on it.

The decision is structural, not featural

Both will schedule a job, hold a quote and raise an invoice. The difference that will actually shape your week is how each is priced and who it was built for.

ServiceM8 meters by jobs per month and states unlimited users on all paid tiers — so adding an apprentice to the system costs nothing, and growth shows up as job volume rather than headcount. Simpro publishes no pricing at all; its pricing page offers a "Request Pricing" action.

Electrical-specific things to test

Electrical work lives and dies on the CoES. If the product cannot generate, attach and retrieve a certificate of electrical safety against the job it was raised on, somebody is keeping a spreadsheet — and that spreadsheet is the leak.

The second is test results and asset data. Where a job involves testing, the results have to attach to the job and survive being looked for two years later by someone who was not there. Most products handle attachment; fewer handle retrieval well.

• CoES generation and retrieval Certificates of electrical safety against the job that produced them. Test finding one from eighteen months ago, not just creating one.
• Test results attached to assets Where the work involves testing, the data has to live with the asset and be findable by someone who was not on site.
• The variation screen On a real phone, in a switchboard cupboard with poor light. If it is awkward it will not get used.
• Progress claims vs invoices If you do any contract work, the two are different documents. Check the product knows that before you commit.
• Offline behaviour Plant rooms, basements, new estates with no coverage. Test what happens when the phone drops out mid-job.

Which we would point a sparky at

One to five vans, jobs rather than projects, and growth that looks like more work rather than more office staff: ServiceM8. The job-volume meter matches how you actually grow, and the free tier means the trial costs nothing but a week.

Multiple entities, staged work with progress claims, heavier inventory or scheduling: Simpro is built for that shape, and the implementation process that comes with it is part of why. Budget for the implementation as well as the licence.

Most of the electricians we talk to are closer to the ServiceM8 shape than they assume, and buy heavier than they need. That is the most common expensive mistake in this category, and it is a version of the same error as building when you should have bought.

The thing that decides it either way

How cleanly it talks to your accounting package. Not "does it integrate" — every product says yes. Ask exactly what syncs, in which direction, and what happens when the sync fails.

Three specifics cover most of the re-typing we are later asked to remove: do customers sync both ways, do part-payments flow back, and do credit notes flow at all. Anyone who knows the product answers all three in a sentence.

That question matters more than any feature on either product, because a weak accounting sync is not a one-off cost — it is somebody re-typing every week for as long as you own the software. The accounting side of the same decision is its own page.

How to actually choose, in about three weeks

A week to write down how a job really moves through your business, then two weeks piloting one real job — a messy one, with a variation and a part-payment — through your preferred pairing.

Agree what would make it a no before you start. Deciding the criteria after two weeks of configuring is how people talk themselves into the wrong product, and it is the single most common failure in this category.

The full version of that process is on the buyer’s checklist, which includes the field test most shortlists skip.