Guide
Field Service CRM:Definition, Modules, Costs and How to Choose
Field service CRM explained: the modules it covers, three ways to build one, vendor prices checked November 2026, and how to choose one by business size.
A field service CRM is customer relationship management software for a business that works at the customer's address. It holds the customer, the property, the lead, the estimate and every conversation, and links them to the jobs, crews and invoices that deliver the work. One product can hold both halves, or a CRM can be joined to field service software.
The choice of architecture decides how many copies of each customer exist. A plumbing company with a sales pipeline in one system and a job list in another keeps two records per homeowner, and the phone number corrected in one stays wrong in the other. The work side of the category, module by module and with vendor prices, is covered under field service management software. This article covers the customer side and the point where the two meet.
The article defines the term, then sets out the modules, the three architectures a field service CRM can take, and the published prices, checked on November 12, 2026. It closes with selection criteria by business size and the place of FieldRanger, which runs on HubSpot. A CRM records the relationship: who the customer is, how they arrived and what was sold. Field service management (FSM) records the work: jobs, schedules, technicians, photos and invoices. A job is one unit of field work with an address, a crew, an arrival window and a status.
Field Service CRM Modules
A CRM for field service carries the standard CRM modules, shaped by work that happens at an address. The table assigns each module to the half of the system that owns it.
| Module | What it holds | Owner |
|---|---|---|
| Customer and company records | People, businesses, phone numbers, emails, billing details | CRM |
| Property and site records | Each service address, access notes, installed equipment | Either; the FSM side where equipment history matters |
| Lead capture | Web forms, calls and referrals, with their source | CRM |
| Sales pipeline | Each opportunity by stage, from inquiry to won or lost | CRM |
| Estimates and quotes | The price offered, tied to the opportunity | Either |
| Communication history | Emails, calls, meetings and notes on the record | CRM |
| Jobs and scheduling | The job, its crew, its date and its route | FSM |
| Work orders and photos | Checklists, photos and the customer's signature from site | FSM |
| Invoices and payments | The bill for completed work and its payment | FSM, synced to accounting |
| Reporting | Revenue by source, close rates, job margin | Both; joined where the records are shared |
Two modules decide whether the halves fit together. The estimate sits on the seam: it is priced by sales and executed by operations. Reporting depends on the join: revenue by marketing source needs the invoice and the original lead on connected records.
HubSpot's object model shows how a general CRM covers the first half. Its standard objects are contacts, companies, deals and tickets, and a Super Admin can activate appointments, services, listings and projects objects in the data model (How to use objects for business processes, updated October 2, 2026). None of those objects is a scheduling board or a technician app. Jobs can be modeled as custom objects, which require an Enterprise subscription (Create and edit custom objects, updated October 20, 2026).
The pipeline module scales by tier. Every object with pipelines gets one default pipeline, and custom pipelines, shared across objects, number 0 on free tools, 15 on Starter and 100 on Professional for seat-based accounts (Set up and manage object pipelines, updated October 22, 2026). A free account can therefore run one deal pipeline, and a business that wants separate pipelines for installations and service agreements needs Starter.
Field Service CRM Software Compared with Field Service Management Software
The two categories overlap at the customer record and the estimate, and divide after that.
| Dimension | Field service CRM | Field service management software |
|---|---|---|
| Central record | Contact, company, deal | Job and visit |
| Main users | Owner, sales, marketing, office | Office, dispatcher, technicians |
| Starts at | The first inquiry | A won deal or a booked job |
| Ends at | A won deal and repeat business | A completed job and a paid invoice |
| Main screens | Pipeline, inbox, contact timeline, reports | Scheduling board, dispatch queue, technician app |
| Main automation | Follow-ups, reminders, campaigns | Job creation, routing, invoicing |
A business with no sales process beyond answering the phone may need no separate CRM. A business that markets, follows up on estimates and sells maintenance agreements needs the CRM half to be a real pipeline, not a customer list.
Three Architectures for a Field Service CRM
The phrase names three different designs. They differ in where the customer record lives and how many copies of it exist.
FSM Software with a Built-In Customer List
The field service product holds the customer list and sells CRM functions as add-ons. Housecall Pro lists Pipeline for lead follow-up and tracking on its pricing page, with no price shown. Neither pricing page mentions a HubSpot integration. One system means one customer record, and the CRM depth is whatever the add-on provides.
FSM Built on a CRM Platform
The field service product runs on a CRM's own records. Salesforce Field Service requires at least one Service Cloud user license, according to Salesforce's field service pricing page. Dynamics 365 Field Service is a Dynamics 365 product. FieldRanger runs on HubSpot: contacts, companies, deals and activity stay in one CRM, and FieldRanger adds the jobs. There is one customer record, held by the CRM, and the field product depends on the CRM subscription.
A CRM and a Separate FSM App Connected by Sync
Each system keeps its own customer record, and an integration copies changes between them. Zuper describes its HubSpot integration as a two-way sync in which a Closed Won deal or a service ticket creates a Zuper job and field updates flow back to HubSpot (zuper.co/integrations/hubspot, checked November 12, 2026). This design keeps a mature field app, at the cost of two records and a sync to monitor: field mappings, duplicates and the objects each direction carries.
Field Service CRM Costs, November 2026
Every price below comes from the vendor's own page, checked on November 12, 2026. The field service management software page lists the wider set of FSM vendors, several of which publish no price.
| Product | Published price | Basis and notes |
|---|---|---|
| HubSpot free CRM | $0 | Up to 2 users and 1,000 contacts, with no time limit ([hubspot.com/pricing/crm](https://www.hubspot.com/pricing/crm)) |
| HubSpot Starter | $20 per seat per month | New-customer offer of $7 a seat paid annually, or $10 month to month |
| Jobber Core | $29 a month billed annually, $49 without commitment | One user; extra users $29 a month; Pipeline add-on $49 a month |
| Jobber Connect | $149 a month billed annually for 5 users | $199 without commitment |
| Housecall Pro Basic | $59 a month billed annually, $79 monthly | One user; Pipeline listed with no price |
| Housecall Pro Essentials | $149 a month billed annually, $189 monthly | Five users |
| Salesforce Field Service | $175 per user per month for Dispatcher or Technician | Annual contract; at least one Service Cloud license, not priced on that page |
| Dynamics 365 Field Service | $105 per user per month, paid yearly | Contractor license $50 per user per month ([microsoft.com](https://www.microsoft.com/en-us/dynamics-365/products/field-service)) |
| FieldRanger | See [pricing](/pricing) | Runs on the HubSpot subscription the business already has |
Sample data, not a client: a business with one owner who sells, one office manager and three technicians, five people in all. Jobber Connect for 5 users with the Pipeline add-on comes to $198 a month billed annually. Housecall Pro Essentials covers 5 users at $149 a month billed annually, with Pipeline unpriced. Salesforce Field Service for one dispatcher and three technicians is four licenses at $175, or $700 a month, before the Service Cloud license. Dynamics 365 Field Service for the same four users is $420 a month, paid yearly. On HubSpot, two Starter seats for the owner and the office are $40 a month at the normal price, and FieldRanger is priced on the pricing page.
The figures compare subscriptions, not total cost. Two costs appear on no pricing page: the hours spent re-keying customers between two systems, and the cost of a migration if the first choice is outgrown.
Selection Criteria by Business Size
Seven criteria decide the shortlist, and each can be checked in vendor documentation or a demo.
- The customer record: where it lives, and how many copies of it will exist.
- The pipeline: marketing, sequences and reporting, or lead tracking only.
- Multi-visit jobs: one job holding several visits with different dates and crews.
- The technician's phone: what the technician sees, and what is captured on site.
- The hand-off: a won deal becoming a job without anyone re-entering it.
- The accounting sync: which system, and which records move.
- The exit: what data leaves with the business if it changes systems.
The answers shift with headcount. A sole operator with no sales process is served by FSM software with a built-in customer list, and a free or entry plan keeps the cost down. A business of three to ten technicians with an office manager reaches the point where scheduling, a technician app and a real pipeline all matter at once; the deciding question is whether the pipeline already lives in a CRM. A business of ten to twenty-five technicians that already runs sales and marketing in a CRM is the case for FSM built on that CRM: the cost of a second record grows with every customer added.
Two cases favor other products over FieldRanger. A business with no CRM and no plans for one is better served by an all-in-one app such as Jobber or Housecall Pro, which include the customer list. An enterprise already on Salesforce or Dynamics 365 is better served by the field service product built on that platform. The CRM software for small business page covers the CRM decision for smaller teams in more detail.
FieldRanger on HubSpot as a Field Service CRM
FieldRanger is the second architecture on HubSpot: HubSpot is the CRM, and FieldRanger adds the field half to the same records. FieldRanger carries the path from estimate to invoice:
- Estimate: built from the HubSpot deal or contact record without leaving HubSpot, or in FieldRanger and tied to the deal it belongs to; the estimate writes the HubSpot deal's line items and amount.
- Job: a won HubSpot deal becomes a job with its context carried over, and the deal record shows the job's status.
- Schedule: jobs are assigned and rescheduled by dragging them on the calendar, and FieldRanger builds each technician's route for the day automatically.
- Site work: the technician opens a digital work order on the phone, with job details, customer information and instructions, and attaches before and after photos.
- Time: clock-ins and clock-outs record where the technician was, so hours match job sites.
- Invoice: the invoice is generated from the completed work order.
- History: job completions, notes and updates are logged to the HubSpot timeline.
Technicians work in a field service app built for the field, separate from HubSpot's own mobile app. The scheduling side is covered in HubSpot calendar scheduling, and the longer case for running a trades business on one CRM is in the white paper running a trades business on HubSpot.
Three hubs carry the detail. The field service management features hub lists FieldRanger module by module, the HubSpot field service hub covers each task inside HubSpot, and the field service software comparisons hub sets FieldRanger against each rival with the cases where the rival is the better choice.
FieldRanger is not a CRM on its own. It requires a HubSpot subscription, and a business that does not use HubSpot is better served by one of the other two architectures.
Limits of This Comparison
Prices were checked on November 12, 2026 and change without notice; promotional prices are marked as such. Housecall Pro's Pipeline price and Salesforce's Service Cloud license are not stated here because the pages checked do not state them, and FieldRanger's plans are on its pricing page. This article compares architectures and published subscriptions. A demo shows FieldRanger on a real HubSpot portal, and Start free trial runs 14 days with no card.
Frequently asked questions
What is a field service CRM?
A field service CRM is customer relationship management software for businesses that work at customers' homes and sites. It holds contacts, properties, leads, estimates and communication history, and connects them to the jobs, schedules and invoices that deliver the work.
What is the difference between a CRM and field service management software?
A CRM manages the customer and the sale, from first inquiry to won deal. Field service management software manages the work after that: scheduling, dispatch, the technician app and invoicing. A trades business with a sales process needs both, in one product or connected.
Can HubSpot be used as a field service CRM?
For the customer half, yes: HubSpot's standard objects are contacts, companies, deals and tickets, with pipelines, email and reporting. HubSpot's documentation describes no crew scheduling board or field technician app, so field work is added with field service software that runs on HubSpot or syncs with it.
How much does a field service CRM cost?
Published prices checked November 12, 2026 run from HubSpot's free CRM for 2 users, and Jobber Core at $29 a month billed annually for one user, to Salesforce Field Service at $175 per user per month plus a Service Cloud license. The total depends on headcount and on whether the CRM and field software are separate subscriptions.
What is the best CRM for field service?
The one that matches where the sales process lives. A business with no CRM is served by an all-in-one field app with a built-in customer list. A business already selling in HubSpot avoids a second customer record with field service software that runs on HubSpot, such as FieldRanger.
Does FieldRanger replace HubSpot?
No. FieldRanger runs on HubSpot: HubSpot stays the CRM, and FieldRanger adds estimates, jobs, scheduling, work orders and invoices on the same contacts, companies and deals.
A field service CRM is one customer record with the sale and the work attached to it; the architecture decides whether that record exists once or twice. The full module-by-module view of the work side is the field service management software guide.
Run field service on HubSpot with FieldRanger
Estimates with e-signature, scheduling and dispatch, a technician mobile app and invoicing, synced to the HubSpot deals and contacts the business already keeps.
Book a demo