Only 3 of a 15-person UK accountancy firm's last 30 new client matters had a CRM source field filled in, and 22 of the 30 came from referrals: existing clients, professional contacts, the informal "you should speak to my guy" at a networking breakfast. The firm had no referral tracking software and no CRM habit doing the same job, and none of the referring contacts had received a structured acknowledgement within 48 hours. The referrals kept coming because the firm did good work, but the channel was invisible to them.
We ran the same audit on four other UK professional services firms in 2025. The pattern held: referrals generating 60–80% of new revenue, virtually no structured tracking, zero proactive management of the referring relationships. The standard defence was "our contacts refer because they trust us, not because we run a programme." Probably true. Also not a reason to leave the channel unmanaged.
What 30 client matters showed about referral pipeline at a UK professional services firm
Here is what the data actually looks like when you pull 30 deal records from HubSpot at a firm that has never structured its referral tracking. Source field blank on 22 of 30 records. Five attributed to "referral" with no referring contact identified. Three correctly linked to a specific named contact. Of those three, one had a follow-up task logged.
The 22 referral-sourced matters generated an average £18,400 in first-year fees. The firm had no idea which relationships were producing that revenue, no mechanism to reciprocate, and no system to ask again. When one key referring solicitor quietly stopped sending work, after receiving no acknowledgement on two consecutive introductions, the firm identified it six months later when they built the retrospective report.
The audit also revealed a timing problem. The median gap between a referral being made and any acknowledgement reaching the referring contact was 11 days. In three cases, the contact had followed up to ask whether the introduction had been received. That is a relationship management failure.
Research published in the Harvard Business Review found that over-systematising referral programmes can reduce the social goodwill that drives them, a real risk if the programme becomes visible to contacts as transactional. The goal is managed pipeline. Keep the system invisible to contacts; make it visible only to you.
How to track referrals in HubSpot: fields, relationships and a pipeline view
The best way to track referrals in HubSpot takes three things: a source field on the deal, a typed relationship between the referring contact and the referred contact, and a pipeline view that filters on source.
Deal-level fields to create:
referral_source_type(dropdown): Existing Client / Professional Contact / Former Client / Event / Unknownreferral_contact_id: Contact lookup field linking to the specific person who referred
Contact-level calculated properties:
referral_count: count of deals where this contact appears inreferral_contact_idreferral_lifetime_value: sum of deal amounts wherereferral_contact_id= this contact
Association label on Contact-to-Contact:
Use HubSpot's custom association labels to define a "Referred By" relationship type on the Contact-to-Contact association. When a new contact arrives via introduction, associate them to the referring contact with that label. The referring contact's record then shows everyone they have sent you, without custom object overhead.
The pipeline view is a standard HubSpot saved view: filter Deals where referral_source_type is not empty, add columns for deal value and referral_contact_id, sort by value descending. Referral pipeline visible in two clicks. That is client referral tracking without a separate tool, and it makes HubSpot work as a referral management CRM.
See also our work on CRM enrichment and ICP scoring for the broader data model that referral tracking sits inside.
Acknowledging referrals within 24 hours with n8n and a LinkedIn task
When a new deal is created with referral_source_type populated and referral_contact_id filled in, fire an acknowledgement sequence to the referring contact within 24 hours.
Here is the n8n workflow configuration for the trigger and acknowledgement steps (we build this kind of automation under our workflow automation service):
{
"nodes": [
{
"name": "HubSpot Deal Trigger",
"type": "n8n-nodes-base.hubspotTrigger",
"parameters": {
"eventsUi": {
"eventValues": [
{
"name": "deal.propertyChange",
"property": "referral_contact_id"
}
]
}
}
},
{
"name": "Fetch Referring Contact",
"type": "n8n-nodes-base.hubspot",
"parameters": {
"resource": "contact",
"operation": "get",
"contactId": "={{ $json.referral_contact_id }}",
"additionalFields": {
"properties": ["firstname", "lastname", "email", "company"]
}
}
},
{
"name": "Send Acknowledgement",
"type": "n8n-nodes-base.emailSend",
"parameters": {
"subject": "Thank you for introducing {{ $('Deal Trigger').item.json.dealname }}",
"toEmail": "={{ $json.email }}",
"text": "Hi {{ $json.firstname }},\n\nThank you for the introduction to [client name]. We've had an initial conversation — things look promising. We'll keep you posted as it progresses.\n\n[Partner name]"
}
},
{
"name": "Create LinkedIn Task",
"type": "n8n-nodes-base.hubspot",
"parameters": {
"resource": "task",
"operation": "create",
"body": {
"hs_task_subject": "LinkedIn touch — {{ $json.firstname }} {{ $json.lastname }}",
"hs_task_body": "React to or comment on {{ $json.firstname }}'s most recent LinkedIn post. Log interaction.",
"hs_task_type": "TODO",
"hs_timestamp": "={{ $now.plus(1, 'day').toISO() }}"
}
}
}
]
}
The LinkedIn task is deliberately manual. Automating LinkedIn interactions at the account level violates LinkedIn's terms of service, and contacts in professional services networks notice templated comments. The task ensures the touch happens and is logged against the contact record; the partner decides the specific interaction.
Keeping referring contacts warm without a formal programme or referral fee scheme
A referring contact who receives nothing meaningful for 12 months will eventually stop referring, through drift rather than spite. The professional relationship requires maintenance that most firms never systematise.
The approach that has worked across our client builds: tag all referring contacts with a referral_source list in HubSpot, then add them to a quarterly "professional contacts" sequence. Send a 4-point digest relevant to their practice area: HMRC updates that affect mutual clients, regulatory changes they need to know about, one practical insight. The accountancy firm switched from a quarterly firm update to a regulatory digest covering MTD and R&D tax credit changes and saw email open rates move from 14% to 31%.
Alongside the email sequence, set a 6-month recurring task on any referring contact who has not introduced anyone in the previous 12 months. The task prompts a coffee or lunch suggestion from the responsible partner: not a referral ask, just relationship maintenance. The referral ask is separate and specific, covered in the section below.
Our work on meeting transcript CRM automation covers how to get contact interaction data back into HubSpot automatically, which feeds this nurture logic with real engagement signals.
What Law Society, ICAEW and FCA guidance allows on referral fees
UK regulated professionals face hard limits on referral fees. Get these wrong and you are in conduct territory.
Solicitors: The SRA requires disclosure of referral fee arrangements to clients. Financial referral fees from CMCs to solicitors were banned under the Legal Aid, Sentencing and Punishment of Offenders Act 2012. For other introductions, referral fees between law firms and professional contacts are permitted but must be disclosed in the client care letter. The Law Society guidance on referral arrangements sets out the disclosure requirements.
Accountants: The ICAEW Code of Ethics permits referral fees under Section 310 but requires disclosure to clients and prohibits arrangements that compromise independence. An accountant receiving a fee for referring a client to an investment platform creates an independence problem.
FCA-regulated advisers: The FCA prohibits cash referral fees from regulated advisers to third-party introducers under the Retail Distribution Review. Non-cash benefits face inducements rules under COBS 2.3A. The FCA's guidance on introducer arrangements sets the boundary between a permitted appointed representative arrangement and a prohibited fee-for-introduction scheme.
That is also why referral software for a small business, built around rewards and payouts, is a poor fit for a regulated firm. The compliant path for all three types of firm is structured non-financial reciprocity: mutual introductions, joint events, co-authored content. Formal financial referral fees require legal sign-off before implementation regardless of profession.
Finding the 20% of referrers behind 80% of introductions
The HubSpot report to identify top referral sources is a Cross-Object report on Contacts associated to Deals via referral_contact_id. Build it as follows:
Report type: Contacts + Deals (Cross-Object)
Primary object: Contacts
Associated object: Deals
Association filter: Deals.referral_contact_id = Contact.hs_object_id
Display columns:
- Contact.firstname + Contact.lastname
- Contact.company
- COUNT(Deals.hs_deal_id) → label: Referrals sent
- SUM(Deals.amount) → label: Total referred value
- MAX(Deals.createdate) → label: Most recent referral
Sort: SUM(Deals.amount) DESC
Date range: Last 24 months
Run this on two years of data. In the accountancy firm case: six contacts had referred three or more matters each. Two of those six had received no firm communication in the preceding 12 months beyond standard correspondence. One was a solicitor who held no client account with the firm at all, purely a professional contact sending work silently.
The 80/20 pattern holds consistently. Two to four contacts typically account for 50–60% of referral deal value. Identifying them is the first step; building the nurture cadence around those specific relationships, rather than a generic programme, is what turns identification into managed pipeline.
Making the referral request a system rather than a favour: timing, format and trigger
Three parameters determine whether a referral request produces results or awkwardness.
Timing: Ask 30–45 days after a successful project milestone or positive client feedback, not at invoice, not at the start of the relationship. At the moment when the client has just experienced a concrete outcome and has context to describe it to someone else.
Format: Email, not phone. The request must be specific about who you want to meet. "Other accountancy practices transitioning their clients to MTD-compliant systems" or "IFAs with a client base in the £500k–£2M HNW bracket" gives the contact a mental filter to apply. A vague "do you know anyone we should speak to?" produces nothing. For building a systematic target list of ICP profiles worth asking about, see our account-based marketing guide for UK SMEs.
Trigger automation: Set a HubSpot deal workflow that creates a task 30 days after a deal moves to Closed Won, assigned to the account manager, not fired automatically. The task contains a templated request message the manager personalises before sending. The system does not send the ask; it ensures the ask is never missed because a partner was busy or assumed someone else had done it.
Our LinkedIn lead generation build demonstrates the same principle applied to outbound prospecting: automation handles timing and logging, the human handles tone and specificity.
What changed in 2025–2026: HubSpot association records and AI-assisted referral network mapping in Clay
Two developments shifted the standard approach to referral tracking.
HubSpot association labels with custom types (fully stable from 2025): Before this, modelling referral relationships in HubSpot required either custom objects (overkill for most SMEs) or an unqueryable text field containing a contact name. Custom association labels on Contact-to-Contact let you define "Referred By" as a typed, queryable relationship visible in the contact timeline and Cross-Object reports. This is now the standard approach for any HubSpot referral tracking build.
Clay AI-assisted network mapping (2025–2026): Clay's enrichment agents can infer professional relationships from LinkedIn data, shared employer history, and co-published content. For a professional services firm, this means importing your top 200 contacts into a Clay table and receiving a scored list of which contacts are likely connected to your ICP targets before any outreach. The Clay enrichment waterfall approach is documented in Clay's developer docs. Clay tells you where to direct relationship management.
Three referral tracking approaches and what they did to pipeline after 12 months
| Approach | What it is | 12-month outcome |
|---|---|---|
| Good | HubSpot deal source fields + Contact association label + 24hr acknowledgement automation + quarterly nurture sequence | Referral channel fully visible; 3 previously unknown top referrers identified; 2 additional matters directly attributed to re-engagement of lapsed referring contacts |
| Bad | Spreadsheet managed by one partner; referrals logged manually after each matter opens | Incomplete from month 3 onward; partner had a busy quarter and stopped logging; 4 referrals recorded vs estimated 11 received; no nurture triggered because the list was never clean enough |
| Ugly | No tracking, no acknowledgement, no nurture; "it just happens organically" | Channel output flat year-on-year; no ability to defend or grow it; one key referrer, who had sent six matters in two years, stopped after receiving no acknowledgement on two consecutive introductions; identified only retrospectively |
A spreadsheet can hold a referral log, so the Bad outcome is a behaviour failure waiting to happen. The moment the responsible partner goes on leave or has a busy quarter, the log degrades. CRM integration removes the discretionary step.
The Ugly case is the most common. Firms that say "it just happens" are right, until one key relationship drifts. By the time that drift is visible (fewer new matters, a source who stops attending events), the relationship is already cold. Retrospective reports tell you what happened; they do not recover what you lost.
For how to structure the data model that makes referral tracking work alongside inbound and outbound lead sources, see our inbound lead routing post. Once a referred prospect converts, see our client onboarding document pack automation guide for the next step in the pipeline.