CRM Consultant, UK

New business, call-offs, channel orders and renewals

The first job is separating the kinds of revenue a UK firm actually has, because each needs different treatment in a CRM:

• New business. Prospecting, qualification and proposals. This is where classic pipeline stages and forecasting belong.
• Framework call-offs. Winning a place on a framework is one opportunity; each call-off or mini-competition under it is another. The CRM needs to link them, so leadership can see the value actually drawn down against a framework rather than its headline size.
• Channel orders. Sales through merchants, wholesalers or distributors. You may never own the end customer, but you can still track specifier influence, promotions and stockist performance.
• Renewals. Maintenance contracts, managed services, software subscriptions and annual service agreements. They deserve their own pipeline with notice dates and owners.
• Account growth. Additional sites, products or services sold into existing customers by account managers.

Mixing these in one pipeline is the most common reason a UK board stops trusting the forecast. A large framework sits at a high probability for months, renewals inflate new-business numbers, and channel sales do not appear at all. I write a short definition for each type, decide which are forecast and which are only tracked, and design the reports that roll them up honestly. That document becomes part of the requirement set for whichever CRM you choose.

Groups, branches and company registration numbers

British customers are often groups: a holding company, several trading subsidiaries, regional branches and sites, each with its own buyers and sometimes its own credit arrangements. A CRM that holds them as unrelated companies produces duplicate accounts, split histories and confused ownership.

I design the account hierarchy before any data is imported:

• Legal entity versus trading name. Invoices go to the legal entity; salespeople often know the trading name. Both need a place.
• Matching key. The company registration number is the most reliable way to match a business across the CRM, the finance system and credit checks, and it should be captured early for any customer that will be invoiced.
• Branches and sites. Delivery and service locations held under the account, rather than as separate customers.
• Group ownership. One relationship owner for the group, with clear rules for who handles each branch.

Sole traders and partnerships need care too. They are customers like any other, but individuals behind them may be treated differently under data protection and marketing rules, so the record should make that distinction visible.

When migrating from spreadsheets or an older CRM, I run deduplication against these rules and agree merge decisions with sales before loading. The account structure then has to match the customer setup in finance, which is where the handoff design comes in. My UK ERP business analyst page covers the finance-side requirements in more depth.

From accepted quote to the finance system

In many UK firms the CRM and the finance system disagree about customers. Sales creates an account in the CRM, finance creates another in Xero, Sage or the ERP, and the two drift apart. Orders are re-keyed, VAT numbers are missing, and nobody in sales can see that a customer is on stop.

I design the handoff as a written specification:

• The trigger. Usually an accepted quote or signed order, with discount and payment term approvals completed beforehand.
• Required data at that point. Billing entity, registration number, VAT number where relevant, invoice address, purchase order reference and contact for invoices. These become mandatory only at the handoff stage, not at first contact.
• Tax treatment. VAT is determined in the finance system or ERP, not by salespeople. Your accountant confirms the treatments for UK, EU and export customers.
• What comes back. Invoice status, overdue balances and credit stop flags visible on the CRM account.

The connection itself is built by developers, the vendor's services team or a partner; my part is the mapping document and testing with real orders, checking that finance and sales see the same customer. My page on system integration in the UK covers the banking, payroll and channel connections around the ERP, and the sales and ERP integration page explains the general pattern.

UK GDPR, PECR and where CRM data is hosted

Data protection shapes CRM design in the UK, but it is your data protection lead or legal advisor who decides your position. Two sets of rules usually come up: UK GDPR for holding and using personal data, and PECR for marketing by email, text and phone. I do not interpret those rules for you; I make sure the chosen CRM can carry out the decisions you have made, and I treat that as a selection test rather than an afterthought.

During selection I ask each vendor to show, on your scenarios:

• How the lawful basis and source are recorded for a contact or a list.
• How an objection or unsubscribe in one tool suppresses the contact in every other tool, including the email platform, the dialer and any LinkedIn or event integration.
• How a subject access request is answered across the CRM and the connected tools.
• How retention rules archive or remove dormant prospects.

Hosting is the other question. Some buyers want data held in the UK or the EU, or need to understand international transfers to vendor support teams. I collect each vendor's written answers on data location, sub-processors and security reports and pass them to your advisor. Product-level detail on one platform is on my Zoho CRM consultant UK page, and the Odoo CRM UK page covers another option.

Choosing between platforms and reporting the board can trust

With revenue routes, account rules and the finance handoff agreed, platform selection becomes a practical test. The shortlist depends heavily on the wider stack. A firm already running Microsoft Dynamics 365 or Odoo for finance has different integration costs from one running Xero, and that changes the answer. The neutral comparisons of Zoho CRM and HubSpot and Zoho CRM and Salesforce are useful background reading.

Reporting is designed alongside the shortlist, not after launch. For a UK board the useful set is usually small: new-business pipeline by stage, framework value drawn down, renewals due by quarter, account growth by owner and lead response times. Each measure gets a written definition, so the monthly board pack does not depend on someone cleaning exports the night before. Where marketing spend feeds the pipeline, I can connect campaign data to closed revenue as described under B2B lead generation.

The work runs remotely in UK working hours, with video workshops and shared documents; site visits can be arranged if genuinely needed. No vendor pays me for any recommendation. The underlying method is described under CRM consulting; for ERP questions, see the ERP consultant UK page and the UK hub.