A common story: a small service business reaches the point where they need operational software, books demos with a couple of well-known enterprise field-service or CRM platforms, receives proposals — and then quietly does nothing. The software works in the demo. The licensing costs, implementation months and annual contract terms are something else. Here's why that gap exists, and what it means for choosing the right operational software for a small team.
Last reviewed:
Per-engineer licensing maths nobody wants to do
Most enterprise field-service platforms are priced per engineer per month, with feature tiers on top. By the time you've added five engineers, two office staff and the integrations you actually need, the monthly cost is a different conversation to the one the website prepares you for.
Worse, the maths punishes growth. Adding a sixth engineer doesn't just add a sixth licence — it often pushes you into the next tier of pricing or unlocks an annual contract minimum. The platform that fits today turns into the platform you're locked into next year.
Office-first software for mobile-first work
Enterprise field-service tools were built around an office-based dispatcher coordinating a fleet of engineers. The mental model is: dispatcher allocates jobs from a desk, engineers receive them, dispatcher monitors progress, dispatcher reports up.
The reality of a small UK service business is different. There's no full-time dispatcher. The office team is two people doing fifteen things. The engineers are running their own day. They need software that's mobile-first and forgiving, not a desktop-first tool with a 'mobile companion app' that loads slowly and forgets the login.
Implementation projects, not month-to-month
Enterprise platforms typically arrive with an implementation project. Three months of configuration, training and 'success management', often through a third-party partner, often for a price that's a multiple of the first year's licences. The pitch is that the implementation pays for itself.
Sometimes it does. Often it doesn't, because the business changes during the three months of implementation — and what you configured at week one doesn't fit any more. The implementation cost is real and up-front; the payoff is forward-looking and uncertain.
Six places enterprise software breaks small teams
Across the engagements we've seen, there's a consistent pattern of where enterprise FSM and CRM platforms break the workflow of a small UK service business. None of these are fatal in isolation, but they compound.
The pattern is recognisable: a tool designed for a different scale of operation, fitted by force to a smaller one. Compromise piles on compromise until the team works around the tool more than through it.
- Engineer-per-seat pricing that punishes growth
- Mobile apps that are an afterthought to a desktop UI
- Onboarding projects measured in months, not weeks
- Annual contracts that assume the business doesn't change
- Dashboards built for executives who don't exist in a small operation
- Customisations that need a paid consultant to alter, not a non-technical admin
Why a flat-feature platform fits better at this scale
Most small operations don't actually need every enterprise feature on day one — but they don't know which ones they'll need by month six. So gated-feature pricing means buying the tier above what you need today, just in case. That's expensive.
A flat-feature platform — full functionality on every plan, priced by staff accounts — sidesteps the gating problem. You pay for staff accounts, not for features. You don't get caught buying the wrong tier and you don't get surprise tier-upgrade conversations when you need a capability that ought to be standard.
When enterprise FSM is the right answer
Enterprise field-service platforms aren't bad software. They're sophisticated tools built for sophisticated operations. If you have hundreds of engineers across multiple countries, complex multi-day project routing, SAP integration requirements and a dedicated operations function, they're often the right answer.
If you don't — if you have 5 to 30 engineers, a small office team, a UK customer base and a desire to spend the evening with your family instead of with a configuration wizard — they're usually the wrong answer. There's no shame in being too small for enterprise software. It's the natural state of most service businesses, and there's better-fitting software in between spreadsheets and ServiceMax.
What 'between spreadsheets and enterprise' looks like
Cushty is built for that middle. Mobile-first, priced by staff accounts rather than by feature tier, opinionated about how a trade job runs so there is less to set up, with a real UK team behind it. If you've evaluated enterprise FSM and walked away, a 30-minute walkthrough will probably feel like the conversation you wanted to have the first time round.
Where to go from here
If any of the above sounded like your week, these are the pages worth reading next.
