Missed appointments. Schedules that fall apart by mid-morning. Engineers turning up without the right parts because nobody could see van stock. Most field service businesses outgrow spreadsheets and WhatsApp somewhere around five or ten technicians, and that is usually the point a double-booking or a missed maintenance visit forces the issue. The instinct is to buy an off-the-shelf platform. Often that is the right call. But for businesses with awkward pricing rules, multi-trade operations, or a large field team facing per-seat pricing, generic FSM tools quietly cost more and fit worse than they should.
At ByteGears we build field service management software for UK businesses that fits how your engineers and dispatchers already work. You own it outright, so there is no per-user subscription climbing every time you hire. We are a UK consultancy, so we know the regulations your trade has to meet, and we design the software around your actual process rather than a generic template.
Where off-the-shelf field service software lets you down
Mainstream FSM platforms are genuinely good at the common case. The problems show up at the edges, and they tend to be the same edges:
- Per-user pricing punishes growth. Subscription FSM runs from roughly £25 a user a month at the simple end up to £300-plus for enterprise platforms. For a 20- or 50-strong field team that becomes a serious annual line item, and it grows every time you take on an engineer.
- Rigid workflows don’t match the trade. Service-call fee plus parts plus labour, multi-level sign-off on high-value jobs, commission splits, recurring maintenance contracts with visit entitlements. If your process doesn’t fit the vendor’s data model, your team works around the software instead of with it.
- Integrations stop at the obvious ones. Most tools sync neatly with QuickBooks and little else. If you run Sage, a bespoke ERP, a parts supplier feed or asset systems, you are back to manual re-keying and CSV exports.
- Mobile apps lag in the field. Enterprise apps can be slow or clunky at scale, and several popular SMB tools have weak or no offline mode. Engineers in basements, plant rooms and rural sites need the app to work with no signal.
- Vendor lock-in. Custom pricing with no transparency, awkward data export and multi-year contract minimums make it hard to forecast cost or change your mind later.
These problems compound. Engineers arrive without the right information, dispatchers rebuild the day by hand, and managers cannot see job status until a customer rings up annoyed. You lose first-time fixes, burn fuel on repeat truck rolls, and watch admin headcount grow faster than revenue.
When SaaS is genuinely the better choice
We will say this plainly: if you run a small team with straightforward, repeatable jobs, stick to standard accounting like Xero or QuickBooks, and an off-the-shelf product covers most of what you need, buy the subscription. It is cheaper and faster to live with. Custom software earns its place when per-seat pricing has become punishing, when your workflows or compliance needs genuinely don’t fit standard products, when you need integrations the market doesn’t offer, or when owning the system and your data matters for the long term.
What ByteGears builds instead
Software shaped around your process
We map how your team actually works before anyone writes code: how a job moves from enquiry to dispatch to completion to invoice, where the approvals sit, how you price. The system supports that routine rather than forcing a generic one on you. Dispatchers and engineers keep workflows they recognise, just faster and visible.
One fixed cost, no per-seat fees
You pay a defined project cost and own the result, including the code and your data. Adding your tenth engineer or your fiftieth costs nothing in licensing. There is no vendor lock-in, no surprise renewal increase and no forced upgrade.
An offline-first mobile app
The technician app is built to work with no signal, because plant rooms, basements and rural callouts are where field teams actually spend their time. Job details, history, photos, checklists and customer signatures all work offline and sync cleanly when the phone reconnects, with conflict handling so concurrent edits don’t clash.
Integrations that reach your real stack
We build the connections that matter to you: Xero, Sage or QuickBooks for invoice and payment sync, your CRM, Google Maps or Mapbox for routing, Stripe for card payments, SMS and email gateways for customer updates. Where you run legacy or proprietary systems, we bridge to those too rather than telling you to replace them.
UK compliance built in
UK GDPR handling, role-based access and an immutable audit trail are designed in from the first session. For safety-critical trades we build certification tracking (Gas Safe, NICEIC, NAPIT) and the service documentation an inspection or an ISO 9001 audit would expect, with retention rules that respect the six-year HMRC and customer-record norms.
Start with an MVP, grow in phases
We deliberately ship a focused first version: work orders, the mobile app, scheduling and dispatch, basic invoicing and customer notifications. Route optimisation, asset management, service contracts, a customer portal and predictive maintenance come in later phases once the core is bedded in. Modular architecture means growth is an addition, not a rebuild.
A team in your timezone
Our team is in London. You get same-day responses, on-site training and regulatory updates without waiting for someone overseas to wake up.
Features we typically build
We tailor the feature set to your operation. A first release usually covers the core; later phases add the rest.
Core (the MVP we usually ship first)
- Work order management: create, assign, schedule and track jobs through to completion
- Scheduling and dispatch with a drag-to-assign calendar, matched on engineer skill, location and availability
- The offline-first mobile app: job details, customer history, status updates, photos and digital signatures
- Automated customer messages: appointment confirmations, engineer-on-the-way alerts and completion reports
- Invoicing generated from completed jobs, capturing labour and parts, with payment tracking
Later phases, when you need them
- Route optimisation that cuts travel time and repeat truck rolls across the day’s jobs
- Parts and inventory tracking that logs usage per job and flags van stock for reorder
- Asset and equipment records: serial numbers, warranty, service history and maintenance schedules
- Service contracts with recurring billing and visit entitlements (for example, four visits a year)
- Dashboards for first-time fix rate, travel time, revenue per job and engineer utilisation
- A self-service customer portal for booking and status tracking
- Role-based access, an immutable audit trail and UK-hosted, encrypted storage
How a project runs
Discovery and planning, 2 to 4 weeks
We document your current process, agree the integration list, plan the data migration and define the MVP. The discipline here matters: scope creep and “golden features” that take weeks to build and rarely get used are a common reason FSM projects overrun.
Build and integration, 12 to 16 weeks for the core
Developers build the system in regular cycles, with sessions where you see working software and give feedback. Integrations to accounting and CRM are tested properly rather than assumed, because broken sync is one of the most common post-launch complaints.
Testing and pilot, 2 to 4 weeks
Your team runs acceptance testing, then we pilot with one or two engineers or a single branch before the wider rollout. Running the old and new systems in parallel for a short window protects you if migrated data turns out messy.
Training, rollout and support
Engineers typically need two to four hours on the mobile app; dispatch and admin staff a little more. We provide hands-on training and post-launch support, then later phases proceed at your pace.
A core build is usually 12 to 16 weeks; a full-featured solution with integrations and advanced modules is more like six to nine months across phases. We send progress updates every week so you always know where things stand.
What it costs and what you own
A custom build is a larger upfront cost than a subscription, but the shape of the spend is different:
- The development cost is fixed and defined, not a per-seat fee that grows with headcount
- You own the code and the data: no lock-in, no contract minimums, no early-exit fees
- Add-ons that SaaS vendors bill separately (route optimisation, advanced reporting, premium support) are simply part of your system
- You add features when the business needs them rather than migrating to a new platform
- No recurring licence fees, only the hosting and any support package you choose
For a mid-market field team, a core build typically lands in the low-to-mid five figures, with later integration and advanced-feature phases adding to that depending on scope. The honest comparison is total cost of ownership over five years against subscription fees plus setup, add-ons and support for a team your size. We will work that through with you during the free consultation rather than quote a number blind.
Industries we build for
Each build picks up the workflows and compliance rules specific to the trade:
- HVAC and plumbing: emergency callout dispatch, maintenance contracts, service-call-plus-parts-plus-labour pricing and Gas Safe certification tracking
- Electrical and building services: NICEIC or NAPIT certification, safety paperwork, subcontractor scheduling and audit trails for safety-critical work
- Facilities management: preventive maintenance across multiple buildings, asset health tracking and cost allocation by site or tenant
- Utilities: emergency-priority dispatch, field data capture for regulatory submissions and asset records for pipes, cables and meters
- IT and telecoms support: SLA enforcement on response and resolution times, engineer routing for installs and integration with ticketing systems
- Industrial and medical equipment repair: warranty status, engineer certifications and full service histories
- Renewable energy: solar and heat-pump maintenance across scattered sites
- Catering equipment repair: parts inventory tracked across service vans
If your trade isn’t listed, the same principles apply. The point of a custom build is that the workflow and compliance specifics are designed in, not approximated.
Common Questions About Custom Field Service Management Software | UK Solutions
How does a custom build compare on cost to FSM subscriptions?
Per-user SaaS pricing runs anywhere from roughly £25 to £300 per user per month, and for a 20- to 50-strong field team that compounds fast across a five-year horizon once you add setup fees, premium support and paid add-ons like route optimisation. A custom build is a larger upfront cost but a fixed one. You own the result, so there are no per-seat fees climbing as you hire. We give you a proper estimate against your team size and feature list during discovery.
What's the typical development timeline?
A core build covering work orders, a mobile app, scheduling and basic invoicing usually runs 12 to 16 weeks. Integrations, automation and advanced features like route optimisation, asset management or a customer portal are normally a second phase. We scope a phased plan in discovery so you get a working system in production sooner rather than waiting on everything at once.
How do you handle updates and changes?
You decide when changes happen. There are no forced migrations or feature removals on a vendor's schedule. We offer support packages for enhancements, new integrations and regulatory updates, and because you own the code you are never locked into us to make them.
Can you integrate with our existing accounting and other systems?
Yes. Common connections include Xero, Sage and QuickBooks for invoice and payment sync, CRM systems, Google Maps or Mapbox for routing, payment processors like Stripe, and SMS or email gateways for customer updates. We also bridge to legacy or proprietary systems that mainstream FSM tools simply do not support.
How do you handle offline working for engineers?
We build the mobile app offline-first. Engineers can open job details, log work, capture photos and take signatures with no signal, and the app syncs when connectivity returns. Sync conflict handling is built in so two updates to the same job do not overwrite each other.
What about data security, GDPR and trade compliance?
Builds include UK-based hosting options, encrypted data, role-based access and an immutable audit trail of who changed what and when. We handle UK GDPR obligations like subject access requests and retention rules, and for safety-critical trades we can track engineer certifications such as Gas Safe or NICEIC and hold the documentation an inspection would ask for.