Job Management Software vs Custom Automation for UK Trades
Job management software vs custom automation is, for most UK trades businesses under about ten users, not a close contest: buy the platform. Published UK pricing runs roughly £28 to £45 per user per month, so a five-person firm pays £1,680 to £2,700 a year for quoting, scheduling, job records and invoicing that already work — and a bespoke build only earns its place when the way you price, schedule or evidence work genuinely does not fit that shape.
That is not the way the question is usually framed. Search it and you get two kinds of page: software listicles that all conclude you should buy the product the publisher sells or earns a commission on, and software-development explainers costing a custom platform at £20,000 to £80,000 as though a ten-van electrical contractor were commissioning an enterprise system. Neither answers the question a UK trades owner is actually asking, which is narrower and more useful: I already pay for software; is the thing I am still doing by hand a reason to replace it, or a reason to bolt something onto it?
Job management software vs custom automation: what does each actually buy?
Job-management software is an off-the-shelf subscription product that holds the standard trades workflow — enquiry, quote, scheduled job, job sheet, invoice — in one place, billed per user per month. You get a maintained mobile app, a support line, accounting integrations and a product roadmap. What you do not get is your process; you get the vendor's, and you fit to it.
Custom automation is software built around the way you already work. In practice, for a firm of this size, it is rarely a whole platform. It is one or two workflows — a chased certificate, a supplier invoice matched to a job, an enquiry turned into a priced quote — running between the systems you keep. It is bought once and then maintained, and at Ihsan Ops a single well-scoped workflow runs £2,000 to £5,000 over two to four weeks.
The honest distinction is not bespoke versus generic. It is that the platform replaces your admin system, and good custom automation usually does not replace anything — it fills the gap the platform left.
What does job-management software cost at 1, 5 and 10 users?
Per-user pricing is the whole story, because the bill is driven by how many people need a login rather than how much work goes through it. Three UK platforms publish their prices. Tradify lists Lite at £34, Pro at £37 and Plus at £44 per user per month (Tradify UK pricing, checked 29 September 2026). Powered Now lists £28, £32 and £40 per user per month across its three plans, with two months free on annual billing (Powered Now pricing, checked 29 September 2026). Joblogic lists Standard from £45 per user per month billed annually, with its Premium and Enterprise tiers quote-based (Joblogic pricing, checked 29 September 2026). Several of the larger field-service platforms publish no full price list at all, which is a budgeting fact worth knowing before you book the demo.
Annualised, ex VAT, at the bottom and top of that published band:
| Users needing a login | At £28 per user/month | At £45 per user/month |
|---|---|---|
| 1 | £336 a year | £540 a year |
| 3 | £1,008 a year | £1,620 a year |
| 5 | £1,680 a year | £2,700 a year |
| 10 | £3,360 a year | £5,400 a year |
Two things follow. At one to five users the platform is cheap enough that replacing it is almost never the highest-value thing you could spend on. At ten users and up the annual figure is large enough to be worth examining — but examining does not mean replacing, because most of that bill is buying something a build does not give you.
Why the per-seat versus one-off comparison is usually wrong
The argument circulating in this category goes: eight users at £40 a month is £3,840 every year, against a custom build bought once. As arithmetic it is correct. As a purchase decision it leaves out three costs, and all three land on the buyer.
A build has recurring costs too. Hosting, a workflow platform, and model usage if there is AI in it. Ihsan Ops publishes these openly at £100 to £600 per workflow per month at production volume, which is £1,200 to £7,200 a year for one workflow. A bespoke build is not the end of your subscriptions; it is a different subscription with fewer features in it.
Somebody has to maintain it. An integration breaks when a vendor changes an API. A platform subscription includes the vendor absorbing that; a build does not, and the cost of a supplier retainer or your own time belongs in the comparison. What a fair retainer should include is its own question, and a fair one is not zero.
You are not buying the same thing. £40 per user per month also buys a mobile app maintained for two app stores, offline sync on a site with no signal, payment processing, accounting integrations and someone to ring. Quote a build that matches all of it and you are back at the £20,000 to £80,000 figures the development agencies publish — which is exactly why, for a trades firm of this size, the sensible build is narrow.
So what is the third option?
Keep the platform. Automate the specific place it does not reach. This is the answer for most of the firms we speak to, and it is the option the two dominant kinds of article on this topic never offer, because neither side sells it.
The three routes, side by side:
| Buy the platform | Keep it, automate the gaps | Build custom | |
|---|---|---|---|
| Typical first-year cost | £336 to £5,400 depending on users | Platform cost plus £2,000 to £5,000 per workflow | £2,000 to £5,000 per workflow, or £15,000 to £40,000 for a multi-process programme |
| Recurring after year one | The per-user subscription | Subscription plus £100 to £600 per workflow per month | £100 to £600 per workflow per month, plus maintenance |
| Time to working | Days to a few weeks of setup | Two to four weeks per workflow | Two to four weeks per workflow; 8 to 14 weeks for a programme |
| Who fixes it when it breaks | The vendor | Your supplier, under a retainer | Your supplier, under a retainer |
| Fits how you actually work | Mostly, if your work is standard | Exactly, at the joins that matter | Exactly, everywhere |
| Right when | Your work fits a standard shape, which is most of the time | The platform holds the jobs but the admin still happens in WhatsApp, email and a spreadsheet | Pricing, scheduling or evidencing work is genuinely non-standard |
Ihsan Ops build figures above are our own published pricing: £2,000 to £5,000 per workflow over two to four weeks, £15,000 to £40,000 over 8 to 14 weeks for a multi-process programme, and £100 to £600 per workflow per month in platform and model costs at production volume. Platform costs are the published UK per-user prices cited above. Nothing here is a quote for your firm, because neither a build nor a programme can be priced before it is scoped.
What changes when you own the software
Two obligations move onto you, and both are cheaper to settle before a build than after.
Data protection. If a supplier builds and runs a workflow touching customer records, they are processing personal data on your behalf and you remain the controller. The ICO is explicit that the controller is ultimately responsible for ensuring personal data is processed in accordance with the UK GDPR regardless of whether a processor is used, and that the arrangement needs a written contract setting out the subject matter and duration of the processing, its nature and purpose, the types of personal data and categories of data subject, and the obligations and rights of the controller (ICO, Contracts, checked 29 September 2026). A platform vendor hands you that document as a matter of course. Ask a builder for it at the quote stage. This is a description of the obligation, not legal advice; how it applies to your firm is for your own adviser.
Continuity. Ask who holds the credentials, where the workflow runs, whether you could hand it to a different supplier, and what happens if you stop paying the retainer. A platform answers all four in its terms. A build answers them in a contract you have to ask for.
Four questions that settle it
- Count the logins you would actually pay for. Not staff — logins. Two office users and four engineers who need a job sheet on a phone is a different bill from six full seats, and some platforms price those differently.
- Find where the hours go, by watching one week. If the time disappears inside the platform, you have a configuration problem. If it disappears between the platform and your inbox, your merchant's paperwork and a spreadsheet, you have an automation problem. These have different answers and the same symptom.
- Write down how you price three typical jobs. If you cannot, a build has nothing to encode yet, and that is a finding rather than a failure.
- Name who will notice when it stops working. In a firm where everyone is on the tools, this is the constraint that decides more builds than budget does.
If the answers point at a build, the sequence is an audit first. Ihsan Ops prices an AI Opportunity Audit from £1,000 — a structured review that decides which workflow is worth building and whether any of them is, before a build is quoted. Details of what gets built are on our process automation and custom AI development pages, and if you have not yet worked out which admin job comes first, what to automate first in a UK trades business ranks them by payback.
Frequently asked questions
Is job management software or custom automation better for a small UK trades business? For most firms under about ten users, the platform. Published UK pricing runs roughly £28 to £45 per user per month, which buys quoting, scheduling, job records, invoicing and a maintained mobile app. A custom build has to beat all of that, not just the monthly figure, and below ten users it usually cannot.
When is a custom build actually worth it for a trades business? When the way you price, schedule or evidence work does not fit a standard quote-to-invoice shape, when the hours go missing between systems rather than inside one, or when you are paying full seats for people who need a single function. Those are the three cases where a build pays back rather than duplicating what you already own.
Does a custom build remove the monthly subscription? No, and any comparison that says it does is incomplete. A bespoke workflow still needs hosting, a workflow platform and, if it uses AI, model usage. At Ihsan Ops those recurring costs run £100 to £600 per workflow per month at production volume, which is £1,200 to £7,200 a year before anyone maintains it.
How much does custom automation cost for a UK trades business? Ihsan Ops prices a single well-scoped workflow at £2,000 to £5,000 over two to four weeks, with recurring platform and model costs of £100 to £600 per workflow per month. Multi-process programmes run £15,000 to £40,000 over 8 to 14 weeks. Every engagement starts with an AI Opportunity Audit from £1,000, which is where scope and price get settled.
Who is responsible for customer data if a supplier builds and runs the automation? You are. The ICO is clear that a controller remains responsible for how personal data is processed regardless of using a processor, and that the arrangement needs a written contract setting out the subject matter, duration, nature and purpose of the processing. Ask for that contract before a build starts, not after.
Where to start
Do question two before anything else. Watch one week and mark where each admin task actually happens — inside the platform, or in the space between the platform and everything else. If it is inside, the fix costs nothing but configuration time. If it is in the gaps, you have found the workflow worth costing, and it is almost certainly narrower than the software you were about to replace.
Ihsan Ops is a UK AI automation agency based in Bedford, working with trades and local services, accounting practices, professional and B2B services firms, and appointment-based businesses. To work through your own login count and your own week of admin with someone who will tell you if the honest answer is to keep what you have, book a 30-minute call.