Every job management platform on the market assumes your work has a shape. A quote becomes a job, the job gets assigned to an engineer, the engineer completes it, an invoice goes out. If that is genuinely your business, buy something off the shelf today and stop reading.
The businesses that end up building their own are the ones where that shape is wrong in a way that cannot be configured away. A commercial cleaning firm where one “job” is a recurring contract with 40 sites and a different scope at each. A plant hire business where the job is really an asset out on loan with a return condition. A maintenance contractor whose work comes from three client portals, each with its own SLA clock and its own reporting format. In each case the off-the-shelf tool can be made to hold the data. It just cannot make the data mean the right thing.
The four signs the shape is wrong
Owners rarely say “our job model does not fit”. They say things that sound like small complaints. These four are the ones worth taking seriously.
1. A job in the system is not a job in real life
The clearest tell. You have jobs in the software that exist purely because the software needs one, or real work that has to be split into four fake jobs because there is no other way to record it. Every report you run afterwards is measuring an artefact of the workaround rather than the business.
2. The important information lives in the notes field
If the answer to “which access equipment does this site need” or “which of the client’s three purchase order numbers applies” is buried in free text, nobody can report on it, nobody can automate against it, and the engineer on site is reading a paragraph on a phone screen in the rain. Fields that matter should be fields.
3. Somebody rekeys the same data every week
The compliance certificate goes into the software and then into a PDF for the client. The timesheet goes into the job system and then into payroll. The purchase order arrives by email and gets typed in. Each individual rekey takes four minutes and nobody counts them, but a two person office doing this loses the better part of a day a week.
4. Your best client wants something the tool cannot do
This is the expensive one. A major client asks for weekly completion data in their format, or access to a portal, or evidence photographs attached in a specific structure. The off-the-shelf answer is “export it and reformat it”, which becomes somebody’s permanent Friday afternoon. Custom software turns that into a scheduled job that runs itself, and it turns a client requirement into a reason they stay.
What custom job management software actually contains
Field service management ↗ is the formal category, and the textbook version of it is enormous. What a UK small business actually needs is usually four pieces, and it is worth being clear that only the first two are essential.
The job model. The data structure that matches how your work is really organised: contracts, sites, visits, assets, whatever the real nouns are in your business. Getting this right is 80 percent of the value and it is the part no off-the-shelf tool can give you.
The field interface. What the person on site uses. This should be ruthlessly small: today’s work, the details that matter, a way to record what was done, and photographs. It has to work with no signal and sync later, because it will be used in basements and on rural sites.
The office view. Scheduling, allocation, and the handful of screens that answer “where is everyone and what is late”. This is where owners want to add features and where restraint pays off most.
The joins. Connections to accounting, payroll and any client portals, so data is entered once. This is usually the piece that pays for the project, and it is often best built second rather than first.
Custom does not have to mean everything is bespoke. The sensible pattern for most businesses is a custom core for the job model and the field app, wired into Xero or QuickBooks for the accounting rather than rebuilding invoicing from scratch. There is nothing distinctive about how your business raises an invoice, and the rules on invoicing ↗ are the same for everyone.
What it costs, honestly
The number that matters is not the build cost, it is the five year cost. A £14,000 build that nobody maintains becomes a liability in year two. Our breakdown of the cost of owning custom software covers the ongoing side in detail, but the short version for a job management system:
| Phase | Typical range | What it covers |
|---|---|---|
| Discovery and job model | £2,000 to £5,000 | Working out the real structure before anyone writes code |
| Core build | £12,000 to £35,000 | Job model, field app, office view, one or two integrations |
| Ongoing | £250 to £900 a month | Hosting, updates, support, small changes as the business shifts |
Compare that against the honest cost of the alternative rather than against zero. A 15 person trade business on a per user platform at £30 a seat is spending £5,400 a year before add-ons, and is still paying somebody to do the rekeying and the client reports by hand. The comparison that decides it is rarely the licence fee. It is the licence fee plus the labour the tool does not remove.
When you should not build
We turn this work down more often than we take it. Three situations where custom job management software is the wrong answer:
- Your process is not settled. If how you run jobs will be different in nine months because the business is changing shape, build the software after the change, not before it. You will pay twice otherwise.
- The off-the-shelf tool fits and you have not configured it. A surprising number of “we need custom” conversations end with a well configured existing tool. If you are using 20 percent of what you already pay for, start there.
- The pain is one report. If everything works except that one client needs one report in one format, you need a custom reporting layer sitting alongside your existing tools, not a replacement for them. That is a much smaller project.
The general test is in signs your business has outgrown its software: the trigger for building is a structural mismatch that recurs, not a single feature you wish you had.
How to start without committing
The mistake is going straight to a full specification. The job model is the risky part, and it can be settled cheaply.
Spend a fortnight documenting what a job actually is in your business. Take the ten most awkward jobs from the last six months, the ones that did not fit the system, and write down what made each one awkward. Patterns emerge fast, and those patterns are the specification. Nine times out of ten the awkward jobs share two or three structural features that no off-the-shelf tool models.
That document is also what makes quotes comparable. Our guide to writing a brief for custom software covers turning it into something a developer can price without guessing, and it is worth doing whether you build with us or not.
If you have a job model that nothing on the market fits, that is exactly the kind of problem managed software is for: built for how you work, then looked after so it keeps working. Get in touch and we will tell you honestly whether you need it.