The Price Depends on Which Technician Showed Up

Nobody notices the job that was underpriced, because it closed and it got paid. The margin left at the curb never appears as a line item. It just makes the quarter a little thinner than it should have been.

That's what makes inconsistent pricing one of the quietest ways a field service company loses money. It has two parts that look separate and share a cause. The price a technician quotes doesn't come from the same place as the price the office bills. And the estimate happens somewhere other than the job site, days after the diagnosis, when the moment has passed.

One price book, applied everywhere, and an estimate that's built and approved before the truck leaves the driveway, closes both.

Gap 3: two quotes for one job

The third of the six information gaps is that the price depends on which technician turned up. It happens in three familiar ways.

Two technicians quote the same job and give different numbers, because each is working from memory, habit or a rate sheet that was accurate two years ago. A new hire undercharges because they don't know what's normal and they'd rather lose margin than lose the customer. And the parts price in the field differs from the parts price the office bills, so the customer sees one number on Tuesday and another on the invoice.

You can put a number on it. Take the highest and lowest quote for the same common job last year, take the difference, and multiply by how often the low one was used. It's one of the six formulas in what disconnected field service systems actually cost.

Gap 4: the estimate that arrives days after the diagnosis

The technician sees the problem on Tuesday. The quote reaches the customer on Friday. By then, someone else has been out.

Why do estimates get sent late? Because the person who diagnosed the problem isn't the person who prices it. The technician takes notes, goes to the next call, and the office builds the quote from those notes when it gets to them. Each hand-off adds time, and a customer's sense of urgency fades faster than most offices assume.

The gap is measurable: compare your close rate on estimates approved on site with your close rate on estimates sent later. The difference, multiplied by annual estimate volume and average estimate value, is what waiting costs. We're not going to put a figure on it because the reader's own numbers are the only ones that count.

What a price book is, and what it is not

A price book in field service is the one source that every estimate, invoice and job-cost calculation pulls from. It's not a PDF rate sheet, and it's not a spreadsheet that someone updates when they remember. A rate sheet is something a person looks at. A price book is something the software reads.

A useful price book has four properties.

It's centralized. Parts, labor and service packages live in one list, and every estimate, invoice and job cost calculation pulls from it. Pricing is the same regardless of which technician builds the quote.

It's tiered when it needs to be. Different customers can have different pricing: preferred customers, residential and commercial, members of a maintenance contract.

Updates are one-touch. Change a price once, and every technician's app reflects it on their next estimate. There's no re-issuing of a sheet and no waiting for people to install a new version of a file.

It has a history. You can see what prices were in effect when. That matters for disputes ("what did we charge in March?"), for audits, and for looking at margin trends over time.

The last property is easy to overlook and it's the one you'll wish you'd asked for. The first time a customer disputes a charge from six months ago, "what was the price then?" needs an answer that isn't a guess.

Building the estimate on site

With a price book in place, the estimate can move to where the diagnosis happens.

A technician builds a full estimate from the job site in minutes, powered by the price book, so the pricing is consistent regardless of who builds it. Branded templates make the quote look like it came from a professional operation, and photos and diagnostic notes attach to support the recommendation. It helps a customer to see the corroded fitting rather than being told about it.

Approval happens on the technician's device or in the customer portal. The estimate can offer the customer options to choose between, so the conversation is about which option and not whether. An approved estimate converts to a work order with one click, and nothing is re-keyed.

For the office, there's a pipeline view. Estimate history, versioning and reporting by technician, service type and region show where the pipeline is, and win rate by technician and service type shows where the coaching goes. The numbers come from the same record the estimates were built on.

The work order lifecycle shows where this fits in the six steps, and a day in dispatch shows what it does for the dispatcher's afternoon.

What to put in a price book on day one

A price book doesn't have to be complete to be useful, and trying to make it complete is the usual reason it stalls. Start with what you sell most.

List your twenty most common jobs and price each one as a service package: labor, parts and any standard extras together. Add the parts you use on nearly every truck, with their cost and their price. Decide whether you need tiers on day one. If you have preferred customers or maintenance-contract members who get different rates, set those up early. If you don't, leave them for later.

Then retire the old sheet. A price book that lives alongside the PDF quickly turns into two sources, and two sources is the problem you started with. Once every estimate reads from the same list, you'll start to see the things a rate sheet never showed you: which packages win, which lose, and which technician's estimates convert.

What consistent quotes tell you

Once everyone quotes from the same list, the variation that's left is real information. Win rate by technician and by service type tells you where coaching would help and where a package is priced out of the market. Margin trends by service line show which work is worth chasing. And the history of prices in effect means a customer's question about a charge from March has an answer that doesn't depend on anyone's memory.

None of this needs a data project. It falls out of the fact that the estimates, the invoices and the price list are one record.

Where AI fits

Drafting an estimate is the kind of queue work that AI can do a first pass on. Describe the job, or name the service type, and the assistant drafts an estimate against your price book. The technician reviews it, adjusts it and sends it.

That order matters. The technician stays in charge of what the customer sees, and the price book stays the source of every price. The AI saves the typing and doesn't invent numbers. We cover this, and the other places AI does real work, in where AI actually changes a field service operation.

Agreements price from the same book

Service agreements should price from the same list. Agreement rates, estimates and invoices all draw on it, so the work an agreement covers and the extras that fall outside it are priced consistently, whichever technician is on the job. The way agreements generate their own visits and bill on schedule is the subject of recurring revenue that schedules itself.

A test for any vendor

The demo request is short: change a price, then show me it on a technician's next estimate.

A vendor that can't do it has a rate sheet, not a price book. And if the answer to "when does the technician's app show the new price?" involves a sync window, a re-download or a second list, you'll be quoting the old price for a while. This is question three in how to evaluate a field service platform.

The price book is one piece of a larger argument about putting every fact on one record, and the Field Service Management guide makes that argument end to end. You can also see the Field Service Suite itself.

Frequently asked questions

What is a field service price book?

A price book is the single source of pricing that every estimate, invoice and job-cost calculation reads from. It holds parts, labor and service packages in one place, can carry different pricing for different customer types, and keeps a history of prices over time. It differs from a rate sheet, which a person consults, in that the software applies it automatically.

How do you keep pricing consistent across technicians?

Give every technician the same source for prices and remove the need to remember or look them up. When estimates are built in the technician's app from the price book, the same job gets the same price whoever quotes it. When a price changes, the change appears on every technician's next estimate without anyone reissuing a list.

Can a technician create and get an estimate approved on site?

Yes. The technician builds the estimate on their phone from the price book, with photos and notes attached, and the customer approves on the technician's device or in the customer portal. Approving on site removes the days of delay between diagnosis and quote that lose jobs to competitors.

How does an approved estimate become a work order?

With one click. The approved estimate is converted to a work order and the lines carry over, so no one re-enters what the customer approved. The job then enters the dispatch queue like any other.

Does the price book keep a history of past prices?

It should. A record of which prices were in effect and when is what lets you answer a customer dispute, support an audit and analyze margin trends. When evaluating a vendor, ask to see the history for a price that has changed.