CRM setup and integration

If your enquiries land in three or four inboxes, a shared spreadsheet and somebody’s mobile, the problem is rarely the lack of software. It is that nothing moves leads from where they arrive to one place your team works from. CRM setup and integration fixes that: a CRM chosen or repaired to fit how you sell, with every lead source feeding it automatically.

A CRM (customer relationship management system) is only as useful as the data that reaches it without anyone retyping it. Most of this work is plumbing and decisions, not the choice of software.

What changes when leads go straight into a CRM

When enquiries live in inboxes, the same things keep going wrong. Leads are answered late, or twice by two people. Nobody can say which channel produced last month’s customers. And when someone leaves the business, their contacts and history leave with their mailbox.

Once the setup is done, each enquiry creates or updates a contact, opens a deal at the right stage and assigns an owner as soon as the form is sent. You can see what is waiting, what was won and where each lead came from. Ad spend can then be judged against sales rather than form fills, which is often the first time an owner sees that one channel brings plenty of enquiries and very few customers.

Who it suits, and who it does not

It suits businesses with a steady flow of enquiries from more than one place, where two or more people handle follow-up and a sale takes more than one conversation. Trades quoting jobs, B2B suppliers, private clinics, training providers, letting agents and consultancies are common examples.

It is the wrong fit if you take a few enquiries a month and one person answers them all; a well-kept inbox and a calendar will serve you better. It is also not the answer when leads are lost because nobody has time to ring them back. A CRM will show that problem very clearly, but it will not solve a staffing gap.

Choosing the CRM

If you already pay for a CRM, I start by checking whether it can do the job once it is set up properly. Replacing a system people only half use rarely helps, because the habits move across with them. When a new one is needed, I compare a short list against what your business actually does:

• Pipeline shape. One sales process or several, and how many stages a deal genuinely passes through.
• Who uses it. The number of seats, whether staff out on site need a phone app that works, and how much admin anyone will put up with.
• Connections. Built-in integrations with your website, booking tool, accounting software and ad platforms, plus an open API for anything else.
• Data location and contract. Where the vendor stores data, and whether its processing terms meet UK GDPR.
• Full cost. Per-seat pricing (often quoted in US dollars), the plan tier you need before automation features appear, and how hard it is to export everything and leave.

HubSpot, Pipedrive, Zoho CRM and GoHighLevel all turn up often in UK small businesses, and each suits a different shape of business. Platform-specific builds are separate pieces of work; everything below applies to whichever CRM you end up with.

What gets connected

How a CRM project runs

1. Map the current journey. A call with whoever handles enquiries, tracing where leads arrive, who touches them and where they stall.
2. Design the record. Contact and company fields, deal stages with plain-English definitions, owners, and the lifecycle stages a contact moves through. Expect fewer fields than you would guess, because every field is one more thing for someone to fill in.
3. Set up and import. Configure the CRM, clean the existing data and import a small test batch before the full load.
4. Connect the sources. One source at a time, each tested with real submissions before moving to the next.
5. Test end to end. Test leads from every source, checked for the correct owner, stage, source and consent fields, using the same approach as my guide to checking that conversion tracking records real enquiries.
6. Hand over. A training session and written notes. Any support after handover, and how long it lasts, is agreed before work starts.

Data protection: settle this before data flows

A CRM holds personal data about every lead, so UK GDPR applies from the first import. Your business is the controller. The CRM vendor, and any connector tool such as Zapier or Make, act as processors, and Article 28 of UK GDPR requires a written contract with each of them. That is normally the vendor’s data processing agreement, which you accept and keep on file.

Each feed also needs its own lawful basis. A quote request is usually handled as a step towards a contract or under legitimate interests. Adding that person to marketing emails is a separate question governed by PECR, which generally needs consent for individuals, with a soft opt-in for people who have bought or asked to buy from you. I store source and consent status as fields, so your team can see what each contact agreed to. If the vendor stores data outside the UK, check which transfer safeguard it relies on before you sign.

I build the fields, flows and retention settings; the wording of your privacy notice belongs to you or your adviser. Health details on clinic enquiries count as special category data, so I keep them out of free-text fields that sync to other tools.

What breaks, and how I prevent it

• Duplicates. One person sends two forms and appears twice with different owners. Matching on email and phone with clear deduplication rules stops most of it.
• Silent failures. A form plugin update renames a field and leads stop arriving, unnoticed for weeks. Every connection gets a failure alert to a named person, and a weekly count of new records by source makes a sudden drop obvious.
• Lost source data. UTM values disappear when a visitor browses several pages before enquiring. Where your cookie consent allows, I hold them from the first landing page until the form is sent.
• Stages nobody updates. If moving a deal takes six clicks, it will not happen. I keep stages few, and some move automatically, for example when a quote is sent.
• Connector sprawl. A dozen small automations built by different people with no record of what each does. Everything I build is listed in one document with its purpose and an owner.

What you receive

• A configured CRM in an account you own, with pipelines, fields and user permissions set.
• Your existing contacts cleaned, de-duplicated and imported.
• Each lead source connected and tested, with failure alerts switched on.
• A data map showing what each feed collects, where it goes, its lawful basis and how long it is kept.
• Written notes your team can follow without me.

What it costs

The price depends on how many lead sources there are, how untidy the existing data is, and whether the CRM is new or being repaired. The CRM subscription and any connector tool are billed to your own accounts, so you keep them if we stop working together. Each quote is written after a free first call, in GBP, and agreed in writing before work starts.