How to choose and set up a CRM or operations platform for a service business

Start with the problem, not the software

Before you look at any product, write down where work currently falls through. Common answers: calls go to someone's mobile and never get logged, estimates are sent and forgotten, the schedule lives on a whiteboard, and nobody can say which marketing brings in paying jobs. That list is your real requirements document.

A quick way to build it: take the last ten inquiries you received and trace each one from first contact to today. Where did it arrive, who handled it, how long did the first reply take, was an estimate sent, was there any follow-up, and what happened in the end? Most owners find two or three repeated gaps. Those gaps, not a vendor's feature page, are what the new system must fix.

It also helps to know the categories. A CRM (customer relationship management system) keeps track of customers, leads and follow-ups. Field service software focuses on scheduling, dispatching crews, job details and invoicing. Operations platforms try to cover both, plus automation and reporting. Many products overlap, so judge them by whether they fix your list, not by the label.

A requirements checklist

Mark each item as must-have, nice-to-have or not needed before you talk to vendors. Most small service businesses need the first six.

• Every inquiry in one place: calls, web forms, texts, email and any lead services you use.
• One owner and a next step on every lead and open estimate.
• Follow-up reminders, and automated messages you can review and switch off.
• A shared schedule or calendar that the office and the field both see.
• A mobile app that works for people in trucks and on roofs, not only at a desk.
• Reports by lead source: how many inquiries, appointments and won jobs each one produced.
• Texting that records consent and handles opt-outs automatically.
• Connections to the tools you keep, such as accounting, estimating or your phone system.
• User roles, so staff see what they need and no more.
• A complete export of your data in a standard format, whenever you want it.

Questions to ask every vendor

Sales demos are designed to look effortless. These questions get you closer to what owning the product will be like.

• Can you show me my workflow, using a lead and an estimate like mine, rather than your standard demo?
• Which features in this demo are live for customers today, and which are planned? Can I speak to a customer using the ones I care about?
• What will I pay in total for the first year: setup or implementation, per-user fees, texting and phone charges, add-ons and contract length?
• Who sets it up, how long does it usually take, and what do you need from my team?
• How do I get all my data out if I leave, and in what format?
• How is texting registration and consent handled, and who is responsible for it?
• What security do you offer: two-step sign-in, user roles, and security commitments written into the contract?
• What support is included, during which hours, and how do I reach a person?

Setting it up in the first 30 days

Most new systems fail in the first month, when people quietly go back to the old way. A short, focused plan prevents that.

1. 1

   Week 1: clean up and import

   Remove duplicates and dead contacts before importing, not after. Agree on a small number of lead stages, for example new, contacted, estimate sent, won and lost, and define each one in a sentence.

2. 2

   Week 2: connect your lead sources and set the rules

   Route your website form, phone and lead services into the system. Decide who owns new leads at each time of day, and write your first-reply and follow-up messages.

3. 3

   Week 3: train and switch over

   Train everyone on the few tasks they do daily, not every feature. Pick a switch-over date and stop using the old spreadsheet or tool on that day, so there is only one place to look.

4. 4

   Week 4: review and adjust

   Check which leads have no owner or no next step, which reports people actually read, and where staff are working around the system. Fix those before adding anything new.

Mistakes to avoid

Most failed rollouts come from the same handful of decisions.

• Buying for features you might use one day instead of the problems you have now.
• Importing years of messy contacts and expecting the system to tidy them.
• Creating so many stages and custom fields that nobody fills them in.
• Having no one inside the business who owns the system and keeps it tidy.
• Automating messages before the manual process works, which only sends mistakes faster.
• Never checking whether people use it. Look at how many leads have an owner and a next step each week.

Count the real cost

The monthly subscription is only part of the price. Add any setup or implementation fee, per-user charges as your team grows, phone and texting charges, paid add-ons, and the hours your team will spend learning and moving data. Ask whether the price is fixed for the contract term and what it rises to afterwards.

Then set that against what the current gaps cost you. If you can estimate how many jobs a month are lost to slow replies or missed follow-up, and what an average job is worth, you have a rough ceiling on what solving the problem is worth. This keeps the decision about results rather than about which product has the longest feature list.

Run a real trial

If a vendor offers a trial or a pilot, use it on real work rather than clicking around. Pick one lead source, such as your website form, and run every inquiry from it through the new system for two weeks. Have the people who will use it daily do the work, and write down every point where they had to stop and ask how to do something.

At the end, check three things: did every inquiry get an owner and a next step, did the follow-ups happen on time, and would your team choose to keep using it. If the answer to the last question is no, the other two will not last.

How to make the final decision

Narrow the field to two or three products, then score each one against your must-haves using your own examples. Ask the person who will use it most, often the office manager, to sit in on the demos and score them too. The system they will actually open every morning is worth more than a longer feature list.

Hypothetical example: a four-truck HVAC company lists its must-haves as one inbox for calls and forms, follow-up reminders on open estimates, and a shared schedule. One product scores well on scheduling but cannot pull in its lead service. Another handles all three but costs more to set up. Weighing the setup cost against the jobs currently lost to missed follow-up makes the choice much clearer than comparing feature pages.

Finally, read the contract before you sign. Check the term length, cancellation terms, what happens to your data when you leave, and any security commitments, which the Federal Trade Commission recommends putting in writing with service providers.