Get more from your CRM: A practical guide for UK SMEs.

Start with the enquiry, not the software.

So, what happens when somebody fills in a form on your website? Where does the enquiry land, who sees it, and how does that person know what to do next? I would start there, even if you already have a CRM in place.

You can have plenty of features and still find that the day-to-day work is awkward. Perhaps the lead arrives in an inbox while sales works from a spreadsheet. The CRM creates a record, but nobody owns it. Then the customer agrees a deal and keeps getting prospect emails. At that point, I'd want to know where the process and the setup have drifted apart.

Take one recent enquiry and walk through what actually happened. Where did somebody copy information, open another system or make a decision from memory? You might find that a small change to the CRM solves it. You might also find a genuine reason to change platform.

If several tools are involved, our marketing technology strategy guide gives you a way to look at the wider stack. Here, I am focusing on the CRM and the journey into it.

Make a requirements checklist you can actually use.

I would keep the first version short enough to take into a demonstration or trial. For each requirement, write down who needs it and what a working result would look like. Otherwise you can end up ticking off features without knowing whether they help anybody.

• Enquiry capture: Which forms, calls and other sources need a record? Which fields are essential, and where should the source be recorded?
• Consent and preferences: What information is collected when someone opts in, where is it stored, and can the team see and honour a later change?
• Records and duplicates: How will you spot an existing contact or company before adding another one? Who can merge records, and what information must survive a merge?
• Ownership: Who receives a new enquiry, what happens when they are unavailable, and who checks unassigned records?
• Follow-up: What is the next action, when is it due, and what stops an inappropriate sequence when the person's status changes?
• Visibility: What does the team need to see to understand open enquiries and overdue actions? Which fields must be reliable for that view to mean anything?
• Access and upkeep: Who can change fields, automations and permissions? Who will maintain the setup when the process changes?

Mark each item as essential now, useful later or unnecessary for the work in front of you. That's a useful way to keep the scope under control. Begin with the steps people already need to complete; add complexity when you can explain what it will improve.

Compare CRM options against the same work.

I wouldn't choose a CRM because it came first in a “best for small business” list. A team with one shared inbox works differently from one with several sales owners and an existing email platform. Product features, limits and prices change, so check the current vendor documentation and terms for anything you shortlist.

I would compare two or three plausible options, including the one you already use if it might still fit. Give each the same sample enquiry and ask someone who will use the system day to day to try it. Score each option against these questions:

1. Can it do the essentials? Check the requirements above in a trial or demonstration. Record what worked, what needed another tool and what was only promised.
2. Can the team live with the workflow? Count the manual steps and look at how easy it is to find an enquiry, update it and hand it over.
3. Does it fit your existing stack? Check the actual form, email and reporting connections you need, including how errors become visible. An integration label on a sales page is only a starting point.
4. Can you own the setup? Consider permissions, training, support, data export and who can maintain the system after launch.
5. What is the full cost for your use? Check the current plan limits, users, required add-ons, implementation work and ongoing maintenance, rather than comparing headline subscription prices alone.

Write the trade-offs down. If your team leaves a demo and immediately opens a spreadsheet to work around it, that matters as much as a long feature list. Choose the compromises they can live with on a normal Tuesday, not just in the demonstration.

HubSpot, Pipedrive and Capsule: a dated starting point.

I checked the vendors' own documentation on 30 September 2026. This is a shortlist to test, not a league table. Features and plan limits change, so check your proposed subscription before making a decision.

HubSpot keeps contacts, companies and deals together, with deal pipelines and website forms that write into the CRM. I'd test it when marketing and sales need to work from shared records. Watch the subscription boundary: full workflows require Professional or Enterprise, while simpler follow-up options have their own limits.

Pipedrive separates unqualified leads from deals moving through a sales pipeline. That may be useful if the team's immediate problem is keeping deal follow-up visible. Its Web Forms need LeadBooster, which is included on Premium and Ultimate or added to Lite and Growth. Automations start on Growth.

Capsule links opportunities to contacts and has a visual sales pipeline. It is another option to trial for straightforward contact and opportunity tracking. Website forms can feed contacts through Transpond, a separate connected product, and Capsule's workflow automation starts on Growth.

Before migrating, export a real sample and check contacts, deals, owners, notes and attachments. HubSpot, Pipedrive and Capsule package related history differently. Pipedrive exports activities, notes and files separately; Capsule's full export excludes attachments. A CSV import alone won't tell you whether the relationships or history survived.

Set up one dependable path first.

Once you have chosen a direction, describe the path of one enquiry in plain language. Here's a hypothetical version: a website form creates or updates a contact, records where the enquiry came from and the person's stated preference, and gives the lead to a named owner. A follow-up task appears. The owner reviews it and changes its status. Any later email depends on that status and the communication preference.

Now decide which system owns each bit of information. Keep the fields and stages simple. When does “new” become “contacted”? What counts as closed? Who can change those definitions? Import the data needed for this first process, check its quality and decide what to do with duplicates before bringing in more. Then walk the team through the same steps they'll use on a normal day.

I'd hold off on automating every response. If ownership, status or consent is unclear, an automated email can make the confusion visible to the person receiving it. Get the basic handover working, then add one rule and test it before adding the next.

Test it with a sample enquiry.

Use a clearly labelled internal test contact in a safe test environment where possible. Follow the whole path rather than stopping when the form shows a success message:

1. Submit the enquiry and check whether the right contact and company records were created or updated. Repeat it with the same details to see how duplicates are handled.
2. Check that the source and the consent choice were captured accurately. Change the preference and see whether later communications respect the change.
3. Confirm that the right person owns the enquiry and receives the task or notification. Try an unavailable owner or an unassigned case.
4. Complete the follow-up, change the enquiry status and check that the next action makes sense. Close it and make sure prospect follow-ups stop where they should.
5. Deliberately break one step, such as a missing required field or a failed connection, and find out who notices and how the issue is recovered.

Write down what happened, what you expected and who will fix the gap. Run it again after the change. Then keep an eye on real enquiries. Are any sitting without an owner? Are follow-ups overdue? Are duplicates creeping back in? I would also ask what people are still doing outside the CRM, because that's often where the next useful improvement becomes clear.

If you want a second pair of eyes on the workflow, we can review your CRM and marketing automation setup. Bring the requirements and the path of one enquiry. That gives us something concrete to work through together.