How to choose a CRM

Check what you already have

Before shopping, look at the systems you already pay for. Many industry platforms include client and pipeline features. Field service tools such as ServiceTitan, Housecall Pro and Jobber track leads, estimates and customer history. Legal platforms like Clio and MyCase handle intake and matters, and Clio offers a separate intake and CRM product. Accounting practice tools like Karbon and Canopy manage client relationships and work. If your core system already covers most of your sales process, a separate CRM may add a second place for data to go stale.

A standalone CRM such as HubSpot, Pipedrive, Zoho CRM or Salesforce makes more sense when your sales cycle is long, involves several contacts per client, or spans services your operational system does not handle, as in a consulting firm, a marketing agency or a commercial cleaning company bidding on contracts.

A quick test helps. List the five things your team most needs to track about a prospect or client, such as source, stage, next step, owner and value, and check whether your existing system handles each one cleanly. If it handles four of the five, better configuration may beat a new product.

Map your pipeline first

Write down, in plain steps, how an enquiry becomes a paying client in your business. For an architecture firm it might be: enquiry from website or referral, introductory call, site visit, fee proposal, revision, signed agreement, project kickoff. For each step, note who does it, what information they need and where it lives today.

This map becomes your requirements. It tells you which pipeline stages the CRM must support, which fields matter, which handoffs need automation, and which reports the owner wants each Monday. It also shows where things fall through today, such as proposals that are never followed up or referral sources that are never recorded.

Pay particular attention to the handoff from sales to delivery. In many service businesses the CRM records the win, then someone retypes everything into the job or matter system. Knowing exactly what moves at that point tells you which integration matters most.

List a short set of must-haves

Most CRMs do the basics well. The differences that matter are usually in a handful of areas, so keep your list short and specific.

• Email and calendar sync with Microsoft 365 or Google Workspace.
• Integration with your core system, such as QuickBooks Online, Clio or your field service platform.
• Web form capture so enquiries arrive as records automatically.
• Simple automation for follow-up tasks and reminders.
• Reports your owner will actually read, such as pipeline by stage and win rate by source.
• Mobile access for staff who sell in the field.
• Permissions that keep sensitive client data visible only to the right people.
• Data export, so you can leave if you need to.

Test with your own data

Vendor demos use clean, invented data and a perfect process. Ask for a trial and load a realistic sample: 100 to 200 of your own contacts, a dozen open opportunities and a few closed ones. Then ask two or three people who will use it daily to run through a normal week: log a new enquiry, schedule a follow-up, move a deal forward, find a past client's history and pull the weekly pipeline report.

Time those tasks and note where people get stuck. A CRM that takes four clicks to log a call will not get calls logged. Compare finalists on these real tasks rather than on feature lists, and include the person who will run reports, often the office manager or owner.

Ask each vendor to load your sample data, or do it yourself with their import tool. How easily your data goes in is a preview of the migration. If a trial import produces duplicates, broken fields or lost notes, expect the same at full scale.

Count the total cost

CRM pricing usually depends on the number of users and the feature tier, and prices change often, so check each vendor's current pricing page. Look past the entry price. Features such as automation, custom reports or more contacts may sit on higher tiers, and some vendors charge for onboarding or require annual contracts.

Add the costs outside the subscription: data cleanup and migration, integration work, training time, and the hours someone will spend each month keeping data clean. A cheaper CRM that needs a separate integration subscription and manual workarounds can cost more than a pricier one that connects natively.

Also consider who will administer the CRM. Some products need regular attention from someone comfortable with fields, workflows and permissions. If nobody on staff has that time, favor a simpler tool, or budget for outside help with admin each month.

Plan the migration and cleanup

Do not move a mess into a new system. Before migrating, export your contacts from every source: the old CRM, email, spreadsheets, your accounting system. Merge duplicates, remove contacts with no activity in several years, standardize company names and fill in key fields such as referral source where you can. This is tedious and worth it.

Migrate active clients, open opportunities and the history people actually use. Archive the rest in a read-only export. Set up the integrations, then run a short pilot with one team before everyone switches. Name one owner for data quality who reviews duplicates and incomplete records each month.

Make sure people use it

A CRM only works if it is the single place people record sales activity. Configure it so the most common tasks are fast, connect it to email so logging happens automatically where possible, and retire the old spreadsheet on a set date. Review usage weekly at first: share of new enquiries logged, share of opportunities with a next step and a date, and accuracy of the pipeline report.

Measure results against a baseline too, such as time to first response, proposal follow-up rate and win rate by source. If those numbers do not improve within a few months, look at whether the process or the configuration needs to change. A technology lead, whether internal or an outside one like InTheory, can help run the selection and setup, but the choice should rest with the people who will use it.