Service · App development

Field service app development.

Custom field service management for engineers in the field. From dispatch and work orders to offline mode, asset registration and invoicing, built around your own workflow, integrated with your ERP, and reliable even in a basement with no signal.

Dispatch & planningMobile-firstOffline modeERP integrationIoT-ready

Field service is more than a planning app.

Field Service Management (FSM) is the software layer that keeps your service organisation running: scheduling work orders, supporting engineers on site, recording what was done, and feeding it through to invoicing. It touches dispatch, execution, reporting and billing all at once, and it has to work on a phone in a lift shaft with no signal.

We build custom FSM solutions for organisations that are too specific for the big off-the-shelf packages. Often with deep integrations with ERP, customer contact centres and IoT sensors. Sometimes as an addition to an existing system, sometimes as a complete field service app that finally replaces the old paper work order.

What sets it apart from a general planning app is the combination: dispatch based on skills, location and SLA priority; a mobile app that also works without coverage; an asset register that remembers exactly which valve sits at which customer; and a reporting layer that makes first-time-fix rate and SLA compliance measurable. Without that combination, it remains a nicer-looking spreadsheet.

Much of what distinguishes a strong FSM solution lies in the edge cases: how does an engineer handle a part that unexpectedly turns out to be missing, how does an inspection with the customer's signature work, how does a rejected installation automatically become a new work order? We develop those edge cases together with your planners and engineers, rather than from a feature checklist.

Three flavours of field service app.

What fits depends on your operation: one region with ten engineers, a nationwide dealer network, or a mission-critical service organisation with SLAs measured in minutes. In the first conversation, we determine which direction is realistic.

Compact project · fixed sprint budget

Engineer app with central dispatch

The basic variant: a mobile app for your engineers with work order details, customer history, photos, signatures and time recording, plus a simple planning board for the dispatcher. Suited to service organisations still running on email, Excel or an outdated package.

Work ordersPhoto & signatureTime recordingPlanning board
Mid-sized project · fixed sprint budget

FSM platform with asset and contract management

For organisations that do more than handle individual work orders and instead deliver service on assets under contract: lifts, fire safety, refrigeration, climate systems. A complete asset register per client, SLA tracking, a preventive maintenance plan, route optimisation, and integration with a CMMS maintenance management system where one is in place.

Asset registerSLA trackingPreventive maintenanceRoute optimisation
Larger project · fixed sprint budget

IoT-augmented FSM with customer portal

A fully integrated FSM suite: sensor alerts that automatically create tickets, AI-assisted dispatch, a client portal with self-service fault reporting and invoice history, plus deep integration with your ERP, CRM and accounting system. Built for service organisations with hundreds of engineers and thousands of assets under contract.

IoT ticketsAI dispatchClient portalERP & CRM integration

The modules of a complete FSM solution.

No organisation needs everything at once. We take it step by step: starting with the modules that remove the most immediate pain, and building on that foundation once it is in place.

Dispatch

Scheduling by skill and route

Match work orders to the right engineer based on skills, certification, location and SLA deadline. Route optimisation keeps mileage and travel time under control, even when schedules change daily.

Execution

The mobile engineer app

Work order details, customer and asset history, photos, signatures, parts usage, time logging, serial or QR code scanning, and forms with mandatory fields for compliance. Fully usable offline.

Reporting

Reporting and analytics

Service reports that build themselves from what the engineer records on site. First-time-fix rate, mean time to repair, SLA compliance and productivity per team, all measurable without spreadsheets.

Billing

Feed into invoicing

Recorded hours, materials and mileage flow automatically into your accounting or ERP system. Contract hours and time-and-materials hours are split correctly, with the right VAT rates for each type of work.

Assets

Asset and contract register

A register per customer site of installations with serial numbers, warranty status, contract type and maintenance history. Preventive maintenance orders are generated automatically from contract triggers.

Parts

Parts and van stock

Stock management per service van, automatic reordering, and integration with central warehouses and suppliers. A returns flow for parts that go back to the manufacturer under warranty.

Customer portal

Self-service for the end customer

Submit fault reports, track scheduling status, view asset history, and consult contract and invoice history, all under your own brand. Optionally with single sign-on for the customer's organisation.

Integrations

Deeply integrated with your stack

ERP (SAP, Exact, AFAS), CRM (Salesforce, HubSpot, Microsoft Dynamics), accounting, contact centre, IoT monitoring and, where relevant, a fleet management app for your service vehicles.

What you get at the end.

A working FSM environment plus everything needed to manage it yourself. We build an app that your engineers and dispatch team will use every day, not a prototype.

  • Mobile app for engineers (iOS & Android)Work order details, customer and asset history, photos, signatures, parts usage, time logging, serial number or QR scanning, with full offline mode for basements, ships and underground networks.
  • Dispatch web app for the plannerPlanning board, skill-based matching, route optimisation, drag-and-drop rescheduling, real-time status for every engineer and ETA forecasts for the customer.
  • Asset and contract moduleAn asset register per customer with serial and type numbers, location, warranty status, contracts and maintenance history. SLA tracking with automatic ticket creation on contract triggers.
  • Integrations with your existing stackIntegration with ERP (SAP, Exact, AFAS), accounting, CRM, contact centre systems and, where relevant, IoT monitoring or a custom order management system.
  • Reporting and analytics dashboardFirst-time-fix rate, mean time to repair, productivity per engineer, SLA compliance, billable hours, all fed by real field data rather than a manual Excel export.
  • Codebase, documentation and trainingFull source code, build and deployment instructions, architecture overview, an admin guide for your IT team, and training sessions for key users.
  • Management and ongoing development (optional)Monitoring, backups, security patches, app store releases, and ongoing development based on field feedback. A fixed monthly fee with four response-time levels.

When custom is the right choice.

For commodity FSM, such as a general HVAC engineer or an average installation company, ServiceMax, Salesforce Field Service or Microsoft Dynamics 365 Field Service often cover the need perfectly well. Custom becomes interesting as soon as your operation deviates from the standard model somewhere.

Industry-specific

Compliance no package covers

Lifts (NEN-EN 81), fire safety (NEN 2535/2654), medical equipment (MDR), explosion safety (ATEX) or NEN 3140 inspections: each sector has its own certification, inspection logic and liabilities that don't fit a generic FSM package.

IoT integration

Sensor data triggers the ticket

Smart assets report themselves: a heat pump showing an error code, a cold room running outside its range, a lift reaching its maintenance counter. The fault should automatically become a work order with the right skill and parts.

Mid-market

Enterprise package too heavy or too expensive

You are too big for Jobber or Housecall Pro, and too specific to make real use of ServiceMax. Custom gives you exactly the modules you need, without paying licence fees for functionality you never touch.

Customer portal

White-label towards end customers

You deliver service under your own brand, often with an SLA promise. A customer portal in your look and feel, covering fault reporting, scheduling status and invoice history, strengthens the proposition. Standard packages rarely do this well.

Not yet sure about a large project?

Test your idea first: a working prototype in 1 day

With OneDayBuild, we turn your idea into something tangible in one day for €1,150, so you can see whether further development is worth the investment. Decide to go ahead with the full build? Then we credit the full cost.

Explore OneDayBuild →

How an FSM project runs.

1

Introduction and scope

A conversation to understand the workflows running through your field service organisation: how a fault comes in, who plans, which skills are involved, which assets are under contract, and which systems talk to each other.

2

Field research and architecture

Half a day shadowing an engineer and half a day with dispatch. This reveals the real workflow, not the idealised version from the process diagram. Alongside it come an integration inventory, a data schema and the first screen flows.

3

Building in sprints

A working build every two weeks. Your dispatcher tests the planning board, while one or two engineers test the mobile app under real field conditions. A first usable version is ready after a few sprints, and the rest grows from there.

4

Pilot, rollout and management

A pilot with one region or one service team, followed by a phased rollout to the rest. Training for planners and engineers, monitoring from day one, and ongoing development based on field feedback.

Industries where custom FSM makes the difference.

Service organisations differ widely in workflow, compliance and asset complexity. Here are a few contexts where, in practice, we more often end up with custom rather than an off-the-shelf package.

Installation and maintenance

HVAC, electrical, plumbing

Classic installation firms running preventive maintenance contracts, an emergency service and construction projects side by side. NEN 3140 inspections and NEN 1006 requirements call for tight record-keeping.

Lifts and escalators

Statutory inspection cycle

NEN-EN 81 and the inspection obligation for lift owners require asset-specific maintenance history, certificates and liability tracking, data that must be retained for years.

Fire safety

Sprinklers and fire alarm control panels

NEN 2535, NEN 2654 and REOB procedures require records per installation, signed reports and automatic alerts when maintenance dates are exceeded. A mistake here directly affects the customer's insurability.

Medical equipment

Service under MDR

UDI registration, traceability per service action, validation protocols and retention periods. A standard FSM package rarely covers this well on its own.

Energy and utilities

Smart meters and grid operations

Large work order volumes, tight scheduling windows per customer appointment, integration with grid management systems, and certification per type of work (gas, electricity, water).

Industrial service

Machine aftersales

Manufacturers with service contracts on the machines they supply: spare parts, retrofits, remote diagnostics. Often with their own client portal for OEM customers and integration with production data.

White goods and office equipment

Dealer network maintenance

Servicing of household appliances and office printers through a dealer or partner network. Service downtime, parts management and billable hours across multiple entities.

Solar, heat pumps, EV

Fast-growing installation markets

Hybrid work: installation and service within one organisation, subsidy administration, warranty claims to the manufacturer, and growth in volume that standard packages struggle to keep pace with.

Frequently asked questions.

What clients usually want to know before we start.

What is the difference between a field service app and a buitendienst app?
In practice, they are the same thing. "Field service" is the international term and "buitendienst" the Dutch one. Sometimes "buitendienst" is used more broadly (also covering account managers and inspectors), whereas "field service" tends to refer more specifically to service engineers and work orders. Our field service app page covers much of the same ground from a Dutch perspective.
Doesn't this belong to CMMS or fleet management now?
There is some overlap, but the focus differs. A CMMS looks at the asset: which installation needs which maintenance. FSM looks at the workforce: which engineer resolves which ticket. Fleet management focuses on the vehicles themselves: tracking, fuel, and servicing the vans. In large service organisations these three systems often run side by side, connected through an integration layer.
Do you replace ServiceMax, Salesforce Field Service or Dynamics 365?
For commodity FSM, rarely. Those packages cover the standard 80% well, and rebuilding that seldom adds value. We come into the picture when you have a specific industry, compliance requirement or depth of integration that an off-the-shelf package can't handle, or when licence costs and customisations on those packages climb so high that custom suddenly becomes more realistic. Sometimes we build a layer on top of such a package instead.
How does offline mode work in practice?
The app has a local data store preloaded with that day's work orders, customer details and asset history. Photos, signatures, materials used and form fields are stored locally and synchronised as soon as connectivity returns. For service in lift shafts, underground networks or on ships, this is not a luxury but a requirement.
Which industries typically suit custom FSM?
Installation and maintenance (HVAC, electrical, plumbing, installation companies more broadly), lift and escalator maintenance, fire safety, alarm and camera systems, telecom and fibre installation, energy and utilities (smart meters, gas networks), medical equipment, industrial machine service, white goods, copier and printer service, solar, heat pumps, EV charging points, pest control, cleaning chains and vending. Sectors with assets under contract, SLA obligations or certification requirements are almost always candidates.
How do you handle compliance: GDPR, MDR, Arbo, NEN?
For each project we carry out a DPIA where location or customer data is sensitive. GDPR and the Dutch Working Conditions Act (Arbo) requirements are built into our standard workflow. For medical equipment we align with MDR requirements around UDI and service logging. For fire safety (NEN 2535/2654), lifts (NEN-EN 81), electrical installations (NEN 3140) or explosion safety (ATEX) we build the inspection logic and certificate administration in. VCA-compliant reporting where relevant.
Can the client portal be white-label?
Yes, and that is one of the reasons organisations opt for custom development. The portal carries your brand, your domain name and your SLA promise to the end customer. Fault reporting, scheduling status, asset history, contract information and invoice history, all in your own look and feel. Single sign-on towards the client organisation where that fits.
What determines the cost of an FSM project?
The three biggest variables are: the number of modules (just the engineers' app, or also asset and contract management, a customer portal, an IoT layer), the depth of integration with your ERP/CRM/IoT stack, and industry-specific compliance. In the first conversation we give a sense of the range; after the scoping phase, a fixed sprint budget per phase follows.

Talk to us about your field service app.

A half-hour introductory call, with no obligation. We listen to your operation, ask questions about your stack and compliance requirements, and give direction that is useful to you, even if the outcome is that a standard package is a better fit.

Edit content