Before you choose a CRM

Start with one real enquiry

Think about a recent customer who called, received a quote and either booked or went quiet. Write down where their details lived, who was responsible and what happened next. A CRM should make that journey clearer. It will not fix a missing follow-up process just because it has more features.

Give the CRM and job system different jobs

A CRM is often the place for contacts, opportunities and sales follow-up. A field-service system may already manage scheduling, technicians and job completion. Before adding another tool, decide which system owns each record and when information should move. If both systems can edit the same field, agree how conflicting changes are handled.

• Where is the authoritative customer contact record?
• What event turns an enquiry into a job?
• Who handles a change of address or duplicate contact?
• Which system owns quote, job and invoice status?

Keep the first pipeline simple

Use stages that reflect a real next action, such as new enquiry, qualified, site visit required, quote sent, accepted and not proceeding. Every open opportunity needs an owner and a next action. Avoid collecting dozens of compulsory fields that staff cannot reliably maintain. Add a field only when it supports an agreed decision or workflow.

Test the difficult handoffs

Ask for a demonstration using a small set of representative test records, not your complete customer list. Check a normal enquiry and the exceptions: an existing customer calling about another property, a revised quote, a duplicate form submission and a customer who has opted out of marketing. Watch what the field team and office each need to do.

• Can a missed call become an assigned follow-up task?
• Can quote reminders stop when the customer replies or accepts?
• Does a failed integration create a visible exception?
• Can staff export their business records in a usable format?

Compare the full commitment

The subscription price is only part of the decision. Check which plan includes the required integrations, the number of paid users, migration work, training, message or call usage and ongoing administration. Ask about cancellation, exports and account ownership. Treat a feature as unconfirmed until its availability has been checked for the specific product and plan.

Pilot, then migrate

Start with one team or enquiry source, agree what success looks like and test the handover into operations. Useful checks include whether enquiries have an owner, whether follow-ups happen and whether duplicate entry has reduced. Clean and migrate the remaining data only after the process works. Preserve consent and suppression records; a CRM import is not permission to start marketing.

A useful first decision

Write a one-page brief covering the problem, the workflow, the systems staying in place, the required integrations, the owner and the budget constraints. That brief gives a vendor something concrete to prove and gives your team a shared basis for comparing options. You may discover that improving the existing tool is enough.

Keep exploring

Use these guides to prepare a practical conversation about your business systems. They provide general technology information, not regulated professional advice.