Executive Summary
Decide first which system field service sits closest to: the CRM that holds the customer, the ERP that holds the parts and the money, or neither.
Field service management (FSM) software plans and schedules work at customer sites, dispatches technicians with the right skills and parts, gives them a mobile app for the job, and sends labor, parts and completion data on for billing. ServiceNow defines field service management as the coordination of field service operations, including scheduling, dispatching, labor tracking, and invoicing. Choose it in two steps. First decide which system it must sit closest to: the CRM that holds customers and cases, the ERP that holds inventory and finance, or neither. Then test scheduling, the offline mobile app and contractor handling on your own jobs.
Field service is sold both as part of CRM suites and alongside ERP suites. Praxedo states that a CRM manages sales, marketing, and customer relationships, an ERP manages company-wide resources like finance, inventory, and HR, and field service management software is built to schedule, dispatch, and track technicians doing on-site work, then feed that activity back into the CRM or ERP. Salesforce states that Field Service and Operations requires at least one Service Cloud user license. SAP states that SAP Field Service and Asset Management works independently of SAP Cloud ERP and supports other ERP environments, and that for SAP Cloud ERP customers, native integration synchronizes field activity with ERP financials, supply chain, and asset records in real time.
The vendors divide by what the field service product is attached to: a CRM platform, an ERP suite, one platform that combines ERP, asset management and field service, an enterprise service platform, an asset-centric service suite, or nothing at all. Start from the approach that matches where your customer, asset and inventory records already live.
Field Service Planning: Who Goes Where, With What
Field service planning turns a list of jobs into each technician’s day: which jobs, in what order, with which parts, and with room for the emergency that arrives at noon. BLS states that technicians may be assigned to a single jobsite or to several locations at the beginning of the day, and then travel to each site, making service calls. A visit that fails for want of a skill, a part or the customer’s history means a second trip.
Demand for technicians is growing, so the schedule has to use them well. The Bureau of Labor Statistics projects that employment in installation, maintenance, and repair occupations will grow faster than the average for all occupations from 2025 to 2035, with about 569,000 openings projected each year, on average. Better matching of skills, travel and priority adds completed jobs without adding technicians.
Some skills are legal requirements. BLS states that the Environmental Protection Agency (EPA) requires nearly all HVAC technicians to be certified in proper refrigerant handling. BLS states that some states and localities require HVAC technicians to be licensed. The scheduling engine needs certifications and licenses as hard constraints with expiry dates, so it never sends an unqualified person to a job.
Offline operation decides adoption. Technicians work in basements, plant rooms and rural areas with no signal. Ask each vendor what the mobile app can do with no connection: open the job, see asset history, record parts and time, capture a signature and close the work order. Then ask how it resolves a conflict when two people changed the same record while offline.
Contractors change the design. A contractor needs assigned work, the forms for the job and a way to report completion, without a full employee license or access to everything else. Decide early whether contractors use the same app, a portal or their own system, because licensing and data access follow from that choice.
Asset history tells the technician what to bring. A technician who can see what was installed, what failed before, the warranty and the contract terms arrives with the right parts. That history lives in the CRM, the ERP or an asset management system, and the field service product has to read it before the technician sets out.
Field Service in the CRM, Beside the ERP, or Standalone?
The first decision is where field service lives. The product has to read customers, contracts and assets, consume parts from inventory, and send labor and materials to billing. The system that already holds most of that data is the natural home, and the others get an integration.
In a CRM-based product, the customer, the case and the entitlement are already there when the work order is created. Salesforce states that Field Service and Operations is built on Salesforce and combines scheduling, dispatching, mobile tools, and intelligent automation. The work left to do is on the ERP side: inventory, costing and invoicing have to reach the finance system.
In an ERP-connected product, parts, inventory and cost can reach finance through the vendor’s own integration. Microsoft states that when the finance and operations integration is enabled, Dynamics 365 Supply Chain Management becomes the system of record for inventory. Oracle states that it connects field workers with Oracle Fusion Cloud Inventory Management and Supply Chain and Manufacturing (SCM) to coordinate parts and logistics. The work left to do is on the customer side: cases, entitlements and customer messages have to reach the field.
A standalone product sits between the two and connects to both. Praxedo states that it is designed to run alongside the systems you already use, not replace them. That means two integrations to maintain, one to the CRM and one to the ERP.
Building your own scheduling optimizer and offline mobile app is rarely sensible. Spend custom work on the integrations and on the forms technicians fill in.
| If most of your service data lives in | Start with | What you still have to integrate |
|---|---|---|
| A CRM, with cases and contracts managed there | Field service on that CRM platform | Inventory, costing and invoicing in the ERP |
| An ERP, with parts, inventory and finance managed there | Field service from the ERP vendor or connected to it | Customer cases, entitlements and notifications |
| An asset or maintenance system, for long-lived equipment | Asset-centric field service, or a combined ERP and asset platform | Customer records and sales leads from the field |
| An IT or customer service platform | Field service on that platform | Parts and finance in the ERP |
| Several systems, none dominant | Standalone field service software | Both the CRM and the ERP |
How do you evaluate Field Service Management (FSM) Software?
Scheduling and dispatch come first. Test whether the engine assigns work by skill, certification, location, priority and SLA, and whether it re-plans during the day when a job overruns or a technician calls in sick. Oracle states that Oracle Field Service combines automation and embedded AI to help plan, schedule, and execute field work. Oracle states that its scheduling can automatically reoptimize schedules throughout the day in response to delays, cancellations, urgent work, and changing field conditions. ServiceNow lists among the benefits of FSM automated work planning and dispatch that matches each job to the best-fit technician, crew, or contractor. Microsoft lists Dynamics 365 Field Service - Resource Scheduling Optimization, which automatically creates optimized schedules, at $30.00 per resource per month, paid yearly. Ask each vendor which optimization features come with the base license and which are add-ons.
Technicians judge the product by the mobile app. Salesforce states that its Field Service and Operations mobile app, available for Android and iOS, is designed as an offline-first application that lets teams access thousands of records even without an internet connection. Microsoft states that when an administrator configures offline capabilities, technicians using the Dynamics 365 Field Service mobile app can continue to access and update work data without an internet connection. Microsoft states that the refreshed mobile experience doesn't currently support working offline. SAP states that SAP Field Service and Asset Management includes a cloud-native mobile app with which technicians receive assignments, access asset history, record time and materials, and close work orders online or fully offline. Oracle lists automatic offline access and synchronization to keep field work moving regardless of connectivity. PTC lists a mobile app for technicians with access to work orders, customer info, service procedures, checklists, and forms that all work online or offline. Ask which screens and actions work offline in the version you will deploy, and test it with the phone in airplane mode.
Asset and contract data tells the technician what to bring. IFS states that with IFS FSM, service teams gain real-time visibility into asset history, warranty information, and SLA commitments. ServiceNow states that its FSM surfaces asset data, service history, and the fix, giving technicians what they need to stay ahead of SLAs. Check where that data is mastered and how quickly a change in the CRM or ERP reaches the phone.
Contractor handling differs between products. SAP states that SAP Field Service and Asset Management extends scheduling and dispatch to contractors and subcontractors, who access assigned work through dedicated portals. IFS lists managing contractors alongside employees, with automated onboarding and billing. Ask how contractors are licensed, what they can see, and how their completed work reaches your invoices and their payments.
Billing is the last test. Oracle lists connecting field operations to financial outcomes by carrying labor, parts, and completion data into costing, billing, revenue, and profitability processes. Trace one completed work order from the technician’s phone to the customer invoice and the parts consumed from inventory, and count the systems it passes through.
| Capability | What it does | Buyer translation |
|---|---|---|
| Scheduling and dispatch | Assigns jobs by skill, location, priority and SLA | Does it re-plan during the day, and is optimization included or an add-on? |
| Offline mobile app | Lets technicians open, update and close work with no signal | Which screens work offline in the version you will deploy? |
| Asset and service history | Shows installed equipment, past work, warranty and contract | Where is it mastered, and how fast do changes reach the phone? |
| Contractor management | Assigns work to external crews and records their completion | How are contractors licensed, and how are they paid? |
| Parts and inventory | Shows truck stock and nearby stock, and records parts used | Which system is the inventory system of record? |
| Customer communication | Booking, reminders, arrival times and job status | Can customers book and reschedule on their own? |
| Billing and costing | Sends labor, parts and expenses to invoicing and job costing | How many systems does one work order pass through to reach an invoice? |
Vendors in Field Service Management (FSM) Software
Representative vendors include IFS, Microsoft Dynamics 365 Field Service, Oracle Field Service, Praxedo, Salesforce Field Service, SAP Field Service Management (now SAP Field Service and Asset Management), ServiceMax and ServiceNow Field Service Management. The list is alphabetical, is not a ranking, and is not for sale. How we choose vendors
The approaches below follow one question: what is the field service product attached to? That decides which records it already has and which it needs an integration for.
Two vendors build field service on a CRM platform. For one of them, the ERP integration path is changing. Microsoft states that the Field Service integration with finance and operations applications won't be available after February 28, 2027, and that the capability is transitioning to the Field Service and Project Operations integration. If you plan that integration, confirm which path will be supported on your go-live date.
Two vendors sell field service beside their own ERP and supply chain applications. SAP states that with the 2605 release, SAP Field Service Management has been relaunched as SAP Field Service and Asset Management with new asset maintenance capabilities. SAP describes SAP Field Service and Asset Management as an SAP Supply Chain Management solution.
One vendor combines ERP, asset management and field service on one platform. IFS states that IFS Cloud is a single, unified platform that, built on a composable architecture, integrates ERP, EAM and FSM. IFS stated when it launched IFS Cloud in 2021 that customers can deploy best-of-breed or connect capabilities such as enterprise resource planning (ERP), customer relationship management (CRM), human capital management (HCM), asset management (EAM) and field service (FSM). IFS states that IFS Cloud was engineered for the cloud but can be deployed on-premises with a choice of residency.
Field service also runs on enterprise service platforms. ServiceNow states that the ServiceNow AI Platform unites AI agents, data, and workflows on one enterprise-grade platform.
Asset-centric service is built around installed equipment rather than the appointment. PTC announced in 2023 that it had completed its acquisition of ServiceMax from an entity majority owned by Silver Lake. PTC states that the acquisition adds field service management (FSM) capabilities to PTC's closed-loop product lifecycle management (PLM) and digital thread offerings. PTC describes ServiceMax as purpose-built for asset-centric industries. PTC states that ServiceMax enables service delivery with work management, automation, preventive maintenance, contract management, mobile tools, and customer self-service on one platform.
Standalone software suits teams that will keep their CRM and ERP. Praxedo describes itself as cloud-based FSM software for companies running 5 to 500+ technicians, with a mobile app that works offline.
| Vendor | Approach | Where it fits |
|---|---|---|
| ServiceMax | Asset-centric service | Service for complex equipment, from PTC |
| IFS | ERP, assets and field service on one platform | Asset-intensive service on the same platform as ERP and asset management |
| Oracle Field Service | Field service beside an ERP suite | Scheduling and field work connected to Oracle Fusion inventory, supply chain and costing |
| SAP Field Service Management (now SAP Field Service and Asset Management) | Field service beside an ERP suite | Customer service and maintenance work, with SAP Cloud ERP or another ERP |
| Microsoft Dynamics 365 Field Service | Field service on a CRM platform | Field service in Dynamics 365, connected to Microsoft’s finance and supply chain applications |
| Salesforce Field Service | Field service on a CRM platform | Field service for organizations running Service Cloud |
| ServiceNow Field Service Management | Field service on an enterprise service platform | Field work for organizations already running service workflows on ServiceNow |
| Praxedo | Standalone field service software | Teams of 5 to 500+ technicians, alongside an existing CRM or ERP |
The seven vendors from the previous edition of this guide stay, grouped by approach, and Praxedo was selected to represent standalone software. A row in this table cannot be bought. The roster check for this edition covered 16 field service vendors, from CRM and ERP suites to software for trades businesses, and any of them can describe its own product in the Spotlight below.
How much should you budget for Field Service Management (FSM) Software?
Field service software is priced per user per month, with different prices for dispatchers, technicians and contractors, and add-ons for optimization and AI. Salesforce lists Dispatcher, an Intelligent Dispatch Console built directly in CRM, at $175 per user per month, billed annually. Salesforce lists Field Service Plus, which combines Dispatcher, Technician, Service Cloud and Sales Cloud, at $230 per user per month, billed annually. Microsoft lists Dynamics 365 Field Service at $105.00 per user per month, paid yearly.
Contractors are priced differently. Salesforce lists Contractor Plus at $80 per user per month or $32 per login. Count how many contractors work in a typical month, and how often each one logs in, before choosing between the two.
Minimums and one-time fees matter more to smaller teams. Praxedo states that its plans are available for businesses with a minimum of 5 users per month. Praxedo states that its listed rates exclude one-time implementation and setup fees. Where no list price is published, ask for a written quote by role: dispatcher, technician, contractor and back office.
Check the prerequisites too. A field service license can require a license in the underlying CRM platform, and the optimizer can be a separate meter counted per scheduled resource. Ask for both in the first quote.
| Meter | You are charged for | Grows with | Where it goes wrong |
|---|---|---|---|
| Per dispatcher | Each scheduler or dispatcher | Size of the planning team | Full seats for supervisors who only view the board |
| Per technician | Each employee using the mobile app | Field headcount | Seasonal staff licensed all year |
| Per contractor | Each contractor, or each login | Contractor volume | Per-user prices paid for occasional contractors |
| Optimization | Each resource the optimizer schedules | Resources in scope | Crews planned by hand included in the count |
| Platform prerequisite | A required license in the underlying CRM or ERP | Platform footprint | Left out of the first quote |
| AI usage | Credits, or a higher edition | Use of agents and assistants | Use beyond the included allowance |
How long does implementation take for Field Service Management (FSM) Software?
A field service rollout changes how dispatchers plan and how technicians work every day. Prove scheduling and the mobile app in one region before you scale.
List job types, durations, skills and certifications, SLAs and territories. Mark which data comes from the CRM, the ERP and any asset system, and which system owns inventory.
Load skills and certifications as scheduling constraints. Configure the mobile app, its offline settings and the forms for each job type. Test in the places with the worst coverage.
Run one region or service line live. Compare completed jobs per technician, repeat visits and the time from job completion to invoice against the months before.
Add regions in waves. Bring contractors on once employee workflows are stable, with their own access and billing rules.
What should you ask vendors about Field Service Management (FSM) Software?
Ask each vendor to answer in writing and to demonstrate on your own jobs.
-
Do your customer cases, contracts and entitlements live in one CRM?Yes Shortlist that CRM’s field service product, and price the integration to your ERP for inventory and invoicing.No Look at ERP-connected, platform and standalone products.
-
Do parts, inventory and job costing drive your service margin?Yes Shortlist products from your ERP vendor or tightly connected to it, and test the inventory flow end to end.No Weight scheduling and the mobile app above back-office integration.
-
Do you service complex, long-lived equipment under contract?Yes Add an asset-centric product or a combined ERP and asset platform to the shortlist.No Concentrate on scheduling, travel and customer communication.