A field service CRM demo is built to show you the finished state, not the work required to get there. The software in the demo already has a complete pricebook, clean customer records, and a dispatcher who knows the system. You have none of that on day one. The gap between the demo and your first month is where shops lose money, lose faith, and end up blaming a product that was never wrong for them in the first place.

Six questions surface that gap before you sign. Ask all six of every vendor, and ask them on a call rather than by email — the hesitations are informative.

1. “What does setup actually require from us?”

The honest answer involves your time, not theirs. Ask specifically who builds the pricebook, who enters customer history, and how many hours your office should expect to spend in the first month.

The pricebook is the one that ambushes people. If your shop has never had a written pricebook, you are not doing data entry during setup — you are making hundreds of pricing decisions for the first time, while still running calls. That is a project with its own timeline, and it is the single most common reason a go-live date slips by months.

2. “What happens to my data if I leave?”

Ask what you can export, in what format, and whether it includes job history, attachments and photos — not just a customer list. A vendor confident in their product answers this immediately. A vendor who deflects is telling you the exit cost is part of the business model.

You are not being pessimistic by asking. You are pricing the risk of being wrong, which is the whole job when you are the one signing.

3. “What is the real cost at my size, in year two?”

Per-user pricing is only the visible part. Ask about implementation fees, payment processing rates if their payments product is bundled, SMS and call charges, add-on modules that turn out to be required for the workflow you were shown, and what happens to the price when the introductory term ends.

Then ask what the total looks like if you add two techs. Growth is the point, and some pricing models punish it hard.

4. “Which parts of the demo are add-ons?”

Demos are assembled from the top tier. The dispatch board that impressed you, the automated follow-up, the reporting — ask which tier each one lives in, and re-price against the tier you would actually buy. It is a fair question and a good vendor will answer it plainly.

5. “Who at my company has to change how they work?”

Every platform assumes a way of operating. Some assume a dedicated dispatcher. Some assume techs close out jobs at the truck. Some assume someone owns follow-up on open estimates.

Write down which assumptions the product makes, then look honestly at whether those roles exist in your shop today. If three of them do not, the software is not the next step — defining those roles is. This is the difference between a rollout that sticks and one that quietly reverts inside 90 days.

6. “Can I talk to a shop my size that uses it?”

Not their flagship reference customer with forty trucks. A shop with a crew like yours, in a market like yours. Ask that shop one question: what surprised you in month two?

If a vendor cannot produce a customer at your size, that is real information about who the product is built for.

Matching the platform to the shop

There is no best field service CRM, only a best fit, and the deciding factor is usually how much process discipline already exists rather than headcount.

  • A written pricebook, a dedicated dispatcher, and consistent close-out. The heavier platforms will repay the setup, because you can actually use what you are paying for.
  • Owner still dispatching, pricing partly in someone’s head. Lighter tools tend to win, because the setup burden is survivable and the team will actually adopt it.
  • Neither, and nobody owns the board. Fix that first. Any platform you buy in this state becomes an expensive place to store the same confusion.

The trap to avoid

The expensive mistake is not picking the wrong product. It is buying a product that assumes processes you have not built yet, then concluding that software does not work for a business your size. That conclusion can cost a shop years, because the next good recommendation gets dismissed before it is heard.

One thing to do this week, that costs nothing

Before you take another demo, write down who builds tomorrow’s schedule, where your prices come from, and who chases estimates that did not close. If you cannot answer all three in one sentence each, you have learned more about your next software decision than any demo will tell you.