Home › Guides

Choosing job management software: the questions that matter

Every job management system does quotes, jobs, job sheets and invoices. Compare the feature lists and you will find they agree with each other almost completely, which tells you the feature list is not where the differences are.

Start with the week you actually have

Before looking at anything, write down what goes wrong in a normal week. Invoices going out late. Variations never billed. Two versions of the schedule. Certificates nobody can find. That list is your specification, and it is more useful than any comparison table, because it is about your firm rather than about software.

The questions worth asking

• How does it charge — per user or per business? Per-user pricing turns every new engineer into a decision.
• What happens on site with no signal? Half the trade works in cellars, plant rooms and new builds.
• How do we get our data out if we leave? Ask before signing, not after.
• How does our existing data get in — customers, price lists, jobs in progress?
• What does it do about the parts specific to here: CIS, the reverse charge, VAT rates that sit on the line rather than the document?
• What does setup cost, and is it optional?

The engineer decides whether it works

Office software gets used because it has to be. Field software gets used if it is faster than the pad and ignored if it is not. So the demo that matters is not the one on the office screen — it is one engineer, on their own phone, on a real job, on a bad signal. If that is awkward, nothing else about the system matters, because the data will not arrive.

Per user or per business

This is the difference that compounds. Per-user pricing is often cheaper at two people and considerably more expensive at ten, and it quietly discourages putting everyone on it — which is exactly the thing that makes the system work. A flat price per business is easier to plan against, and it means the answer to "should the new lad have a login" is always yes.

Try it on a real job

Not a demo dataset. Take one live job from quote to invoice, with a real customer and a real engineer, and see where it sticks. A fortnight of that tells you more than a month of evaluation, and it also tells you how much of the trouble was the software and how much was the way you work — see moving off spreadsheets.