What Is Field Service Management? A Plain-English Guide for Trade Owners

Field service management is the coordination of work your business performs away from its own premises. It covers the whole loop of a job: the call or booking that starts it, the schedule and the dispatcher who assigns it, the work order the technician carries onto the site, the invoice raised before the van leaves the street, and the numbers that come back to tell you whether the job made money.

Trade business owners usually meet the term in one of two places. One is a software vendor’s website, where “field service management” is the label on the product being sold. The other is a search box, typed at the end of a long week by somebody who has just double-booked two jobs and cannot say what last month’s big install cost to deliver. This page is written for the second reader. It explains the category in plain English, walks through a normal Tuesday at a five-person trade business, and only reaches the software and its prices at the end.

There is no product talk in the first half of this page and no hard sell in the second. We read the vendors’ published pricing pages on 11 September 2026 for the cost section. We have not used these products on customer jobs and we do not claim to have. If you have not bought anything yet, that is a perfectly good place to be, and the goal here is simply that you recognise your own week in the description.

The five parts of field service management

Strip away the brand names and field service management is five jobs done in order. Every platform on the market is some arrangement of these five, priced and packaged differently.

1. Intake - catching the work. A call at 7:40am, a form on your website at lunchtime, a text from a regular client, a lead from a directory, a request a technician picks up while standing in a driveway. Intake is everything that has to land somewhere it will not be forgotten. The failure mode is a message living on one person’s phone with nothing to prompt it.

2. Scheduling and dispatch - deciding who and when. Scheduling answers when the job happens; dispatch answers who goes. On a small crew one person does both, usually the owner, usually at the kitchen table. The work is matching three things: the technician’s location, their skill, and the window the customer agreed to. Most of the hidden cost in a service business sits here, in drive time and in drive time’s cousin, the second visit.

3. Work orders and mobile execution - doing the job and recording it. A work order is the instruction that travels with the job: the address, the complaint, the history, the parts and the price. On paper it is a carbon-copy pad. In software it is a screen on the technician’s phone, ticked through on site with photos, notes and a customer signature. This part decides whether you can bill the same day.

4. Invoicing and payment - turning the job into money. Everything above is cost until this happens. The measure of a good setup is how short the gap is between “job done” and “money received”: a card charged in the driveway, or an invoice that fires automatically when the work order closes instead of being typed up on Friday.

5. Reporting - the feedback loop. Job costing per job, revenue per technician, which marketing source produced the call, how often you had to go back. Without this part, the other four run on memory, and memory flatters a business.

Two of the five - intake and payment - are where a small trade business usually loses the easiest money. The middle three are where it loses the most time.

A normal Tuesday, step by step

Here is a five-person trade business getting through a Tuesday: three vans, an owner who quotes and runs the office, and a part-time admin. Nothing in this story is unusual, which is the point of telling it.

7:40am. The phone rings. A property manager has a water heater leaking into a closet at a rental unit. The owner writes the address on the pad beside the phone.

7:55am. The office checks the day’s board. Two vans are already out; the third has a gap between 11am and 1pm. The owner calls back, agrees a noon window, and texts the technician the address, the access code and the history from the last visit to that unit.

8:30am. The technician opens the job on their phone and sees the same unit had a valve replaced eight months ago. That detail alone can justify a subscription, because it changes what gets loaded onto the van.

12:10pm. On site. The technician diagnoses a failed expansion tank, photographs it, checks the price book on the phone, and shows the property manager a flat-rate price before touching anything. Approved. The repair takes an hour.

1:20pm. The work order closes on the phone with photos, parts used and the customer’s signature. That last step is what makes the next one possible.

1:25pm. The invoice is generated from the closed work order rather than typed up later, and the card on file is charged in the driveway. The job is paid before the technician has left the street.

1:30pm. A review request goes out automatically. The board shows the van is now free, and the office books a non-urgent call into the gap.

Now run the same Tuesday without any of it. The address goes onto a notepad. Nobody remembers the valve from eight months ago. The price is quoted from memory, which either leaves money on the table or starts an argument. The invoice is typed up on Friday from a paper docket, if the docket survived the van. The card gets charged whenever somebody remembers to call. The review request never happens. None of those failures is dramatic on its own. Together they are the difference between a business that grows and one that plateaus at the same revenue with more work.

Field service management vs mobile workforce management

These two terms get used as though they were interchangeable, and the difference matters when you are reading a vendor’s page.

Field service management is organised around the job and the customer. The unit of work is a work order at a specific address for a specific client, with a price, a history and an invoice attached. The questions it answers are: is this job booked, who is going, what did it cost, and has it been paid.

Mobile workforce management is organised around the worker and the shift. The unit is a person’s day: where they clocked in, how many hours, which site, which task on a list, often many tasks at a single location. It is the language of facilities management, janitorial contractors and utilities, where attendance, rostering and compliance sit at the centre of a large mobile workforce.

A trade business almost always wants the first one, and the test is the questions you ask the system. If your questions are about jobs, customers and money, you want field service management. If they are about shifts, hours and attendance across a large part-time workforce, you want workforce management, and platforms built for trades will fight you on it. That gap is real, and it is why a cleaning company with a rotating part-time crew often finds that nothing here fits exactly.

The words vendors use, translated

Sales pages are written in a shorthand that assumes you have bought software before. Here it is in plain English.

Two of these deserve a second look. A price book is not a price list you print and pin to the wall; it is the thing that stops your best technician and your newest hire quoting differently for the same job. And job costing is the only one of the ten that tells you whether the business is genuinely profitable job by job. Most owners who cannot answer “what did that install make me” are missing exactly this, and it usually sits a tier or two above the entry plan rather than on it.

Do you need software yet?

Not necessarily. Software is not a rite of passage, and a well-built spreadsheet is a respectable answer below a certain size. Here are three checkpoints. If none of them is true, keep your money.

1. You are double-booking. Two jobs, one van, one address you cannot be in twice. It happens once a month and somebody has to apologise. A shared calendar fixes the immediate problem; a shared calendar plus a job history fixes the next two checkpoints as well, and that is the honest reason to look past a calendar app.

2. You cannot say what a job cost you. You know what you charged. You do not know what the labour, the parts and the two trips to the supplier cost you. If a four-figure install was profitable last month and you cannot prove it, you are pricing on instinct.

3. You are the bottleneck on every schedule change. Every move, every sick day and every emergency call passes through your phone. That is not a discipline problem, it is a capacity problem, and it caps the business at the size of your attention.

Below that line, be straight with yourself. One person doing under roughly ten to fifteen jobs a month, with none of the three symptoms above, does not need to buy anything. A calendar, a folder of invoices and a spreadsheet of prices will run that business well. The point of field service management software is not to modernise you; it is to remove one specific bottleneck, and it is worth the money only once that bottleneck exists.

What it costs at each size

When you do reach for software, the figures below are the ones vendors publish themselves. We read each vendor’s own pricing page on 11 September 2026 and used the list price printed there. Vendors that publish nothing are marked “request pricing”, and we do not fill that gap with a guess.

The written ranges by size, using list prices only and excluding payment processing and add-ons:

One person. Jobber Core at $29/mo billed annually, or ServiceM8’s free plan while you stay under 30 jobs a month. Nothing at this size costs more than a job or two a year.

Two to five people. Jobber Connect at $149/mo billed annually covers five users, and Housecall Pro Essentials is the same $149/mo for five. Both add what matters at this size - reminders, automatic payment collection, job notes and photos - rather than dispatch depth. ServiceM8 Growing at $79/mo with unlimited users wins if volume stays under 150 jobs a month, and Kickserv Start at $60/mo for five users is the budget route. This is the band where a trade business first meets the field service software category properly, because it is the point at which a calendar stops being enough.

Six to fifteen people. Jobber Connect at $229/mo billed annually for ten users, or $299/mo for fifteen. Housecall Pro MAX at $299/mo billed annually covers eight users, with extra seats at $75/mo, and route optimization sits at this tier rather than the entry one. Kickserv Scale is $199/mo for twenty users, and Service Fusion Starter at $208/mo billed annually removes the seat question entirely, because users are unlimited on every plan. Towards the top of this band dispatch depth starts to matter more than price, which is what our dispatch software breakdown covers.

Where per-technician pricing begins to make sense. Above roughly ten to fifteen technicians, with one or two dispatchers in the office, the question stops being what the software costs and becomes what a missed visit costs. That is where the enterprise platforms enter. ServiceTitan is quote-only on a per-technician model, publishes no list price and offers no free trial, and Simpro and FieldPulse likewise run on demos, though FieldPulse’s own pricing tool publishes a platform rate of $99 per user (checked 11 September 2026). None of the three belongs in a first purchase. They are the benchmark once somebody’s whole job is dispatch, not a starting point.

If you want all nine compared on the same criteria, that is what the best field service software round-up and the Jobber pricing page do in more detail. And to be straight with you: we may earn a commission if you sign up through a link on this page - that never changes what we recommend; here is our affiliate disclosure.

How this page was built

Every price and every vendor claim on this page was read from the vendor’s own pricing page on 11 September 2026, and the date at the top moves whenever we re-check them. Where a vendor publishes no price, we write “request pricing” instead of filling the gap with a figure, and where a third-party estimate circulates for a vendor that publishes nothing, we label it as an estimate and name the source.

We have not used these products on customer jobs and we do not claim to have. What this page does instead is describe the category from the outside: what the five parts of field service management are, what a normal Tuesday looks like when they work and when they do not, and what the platforms that publish prices actually charge. The five-person business in the walkthrough is a composite illustration of the pattern, not a case study of a named customer.

If you take one thing from this page, take the order of the sections. Work out which of the five parts is failing before you look at a product name. Double-bookings are a scheduling problem, invoices that go out on Friday are a work-order problem, and not knowing what a job cost you is a reporting problem. Match the fix to the failure, and the feature list sorts itself out.