A 10-person UK SME sales team we audited in April was paying for Apollo Pro across all reps, Lusha browser extensions for every seat, and Clay for enrichment. Annual bill: £21,400. Coverage on their ICP — UK professional services firms, 20 to 150 headcount, managing director or operations director — sat at 71%. We rebuilt the stack with Clay as the enrichment layer, Apollo Basic for one prospecting seat, and a single Lusha API licence as fallback. Same coverage, £8,900 per year, with enrichment routing directly into HubSpot without a manual export step in sight.
The problem was not the tools. It was overlap with no waterfall logic behind it. Three platforms doing partially the same job, billing for the same data points on the same contacts.
This post covers what each platform actually does, where each one breaks on UK SME data, and the specific configuration that reaches 80% coverage at the lowest annual cost.
Apollo, Clay, and Lusha: what each one actually does in a UK SME prospecting stack
These are not interchangeable products competing for the same slot. Before comparing price, get clear on what job each one performs.
Apollo is a contact database with a sequencing layer included. You search 275 million contacts by job title, company size, industry, and technology stack, pull a list, and run outbound sequences from inside the same platform. The database is Apollo's core asset. Sequencing is included at every tier. Apollo's strength is search breadth; its weakness is data freshness on contacts outside the US and Western Europe, and particularly on UK SME decision-makers who don't publish content or appear in intent-data feeds.
Clay is an enrichment orchestrator. It does not hold a contact database. You bring a list — from Apollo, from LinkedIn Sales Navigator, from a CSV — and Clay enriches it by calling 50-plus data providers in a waterfall sequence. Clay also supports AI columns: you write a prompt and it runs against every row, calling the model of your choice to score fit, draft a personalised opening line, or flag contacts matching a specific criterion. Clay is where you build your data model; it is not where you find leads.
Lusha is a browser extension plus API that extracts and verifies contact data — primarily personal email addresses and direct phone numbers. It works best as a fallback at the end of a waterfall. When Apollo and your primary enrichment providers miss a contact, Lusha's network, built partly from extension users surfacing LinkedIn profiles in real time, often has the gap covered.
The correct mental model: Apollo or LinkedIn Sales Navigator supplies the initial list, Clay enriches it through a cascading waterfall, and Lusha sits at the tail of the waterfall as a high-recall last resort.
UK data coverage: how each platform performs on SMEs outside the FTSE 500
We ran the April audit against 1,200 contacts matching the client's ICP: UK professional services, 20 to 150 headcount, MD or Ops Director title. Results for verified work email:
| Platform | Overall hit rate | Outside-M25 hit rate | Median data age | Primary source |
|---|---|---|---|---|
| Apollo | 68% | 59% | ~90 days | Proprietary DB + intent feeds |
| Clay waterfall (4 providers) | 81% | 79% | ~35 days | 50+ providers aggregated |
| Lusha | 74% | 78% | ~60 days | Extension network + scraped |
The outside-M25 gap is the number that matters. Apollo's data skews towards companies with strong digital footprints — conference speakers, marketing-active tech firms, companies that show up in B2B intent-data feeds. A regional accountancy firm in Leeds with 40 employees and a managing director who does not publish LinkedIn content simply does not appear in Apollo's database at the same rate as a SaaS company in Shoreditch.
Lusha performs better outside London because its extension user base is geographically distributed across the UK, and those users surface email formats directly from LinkedIn profiles rather than relying on conference records or purchase-intent signals.
Clay's waterfall wins because it aggregates across all of them. It does not beat any single provider on proprietary data quality — it beats them by querying all of them in sequence and taking the first verified result.
UK GDPR compliance: which platforms you can legally prospect from in 2026
All three platforms operate under legitimate interests as their lawful basis and publish Data Processing Addenda covering their role as data processors. Apollo's trust portal includes its DPA, sub-processor list, and ISO 27001 certification. Lusha is registered as a data broker with the ICO. Clay processes data in transit rather than maintaining a persistent contact database, which simplifies its GDPR exposure considerably.
None of that covers your use of the data. The ICO's guidance on legitimate interests makes clear that you must conduct your own Legitimate Interests Assessment before contacting any data subject, regardless of where the contact data came from. Three practical requirements:
- A Legitimate Interests Assessment documented before your first outreach campaign, reviewed each time your ICP changes significantly.
- A suppression list that actually works — contacts who opt out must not receive further email from your domain.
- Honest identification in every email: your registered company name, a UK address in the footer, and an unsubscribe mechanism that processes within 24 hours.
If your ICP touches sole traders or any consumer-adjacent contacts, PECR applies on top of UK GDPR and requires prior consent rather than legitimate interests. For B2B decision-makers at limited companies, legitimate interests is a defensible basis when documented correctly.
Clay enrichment waterfalling: how to get 80% coverage without paying for three full licences
A Clay waterfall is a sequential enrichment table. Clay calls provider one; if it returns nothing, it calls provider two; if that also fails, it moves to provider three. You pay credits only when a provider returns verified data. Failed lookups consume a fraction of a credit.
This is the waterfall configuration we deployed:
{
"waterfall_name": "UK_SME_Email_Enrichment",
"steps": [
{
"provider": "apollo",
"trigger": "always",
"cost_per_hit": 1,
"expected_hit_rate": 0.65
},
{
"provider": "hunter",
"trigger": "if_previous_failed",
"cost_per_hit": 1,
"expected_hit_rate": 0.50
},
{
"provider": "lusha",
"trigger": "if_previous_failed",
"cost_per_hit": 1,
"expected_hit_rate": 0.45
},
{
"provider": "hubspot_insights",
"trigger": "if_previous_failed",
"cost_per_hit": 2,
"expected_hit_rate": 0.30
}
],
"fallback_action": "flag_for_manual_review"
}
At a 65% Apollo hit rate, Hunter catches approximately half of the remaining 35%, and Lusha catches around 45% of what Hunter misses. HubSpot Insights (formerly Clearbit Reveal, rebranded and integrated into HubSpot's enrichment suite following the 2023 acquisition) handles a final slice of company-level enrichment where no personal email is available. The Clay provider key is "hubspot_insights" — the legacy "clearbit_reveal" key was deprecated in 2025. Blended result: 81% coverage. Effective credit cost per enriched contact: 1.4 credits — well below the naïve assumption of four credits per contact. The Clay enrichment waterfall documentation covers credit accounting in detail, including how partial matches are counted and when failed lookups cost zero.
The HubSpot push runs as a Clay table action: when enrichment completes on a row, Clay pushes the full contact record — verified email, direct dial, LinkedIn URL, company headcount, and revenue band — to HubSpot via the native connector. No Zapier, no CSV export. We cover the field mapping and deduplication logic in detail in our CRM enrichment and ICP scoring guide.
Pricing for a 10-person UK team: the real annual bill with all credits included
Published prices shift. These figures are from July 2026, converted at £1 = $1.27:
| Configuration | Annual cost (GBP, approx.) | Coverage (our ICP) | Best fit |
|---|---|---|---|
| Apollo Pro × 10 seats | £9,600 | 68% | US-heavy ICP, high sequencing volume |
| Lusha Teams × 10 seats | £6,000 | 74% | UK-first ICP, reps need browser extension |
| Clay Explorer + Apollo Basic × 1 seat | £5,800 | 73% | Solo SDR, no sequencing requirement |
| Clay Explorer + Apollo Basic × 1 + Lusha API × 1 | £8,900 | 81% | 10-person UK SME team (our recommendation) |
| Apollo Pro × 10 + Lusha × 10 + Clay Explorer | £21,400 | 71% | What the client was paying before |
The before/after gap comes almost entirely from removing per-seat Lusha licences for all reps. Reps do not need a browser extension when Clay runs enrichment centrally and pushes results to HubSpot before a rep ever opens a contact record. One Lusha API seat as a waterfall fallback costs around £600 per year. Ten Lusha browser extension seats on the Teams plan cost £6,000 per year. Same underlying data, nine times the cost.
CRM integration: which platforms push clean data into HubSpot without middleware
Apollo's native HubSpot integration syncs contacts, companies, and sequence activity. It is reliable at the contact level. The failure mode is duplicate company records: Apollo creates a new company object if the domain does not exactly match an existing record. Set company deduplication to domain-based matching in HubSpot before enabling the sync, or you will spend time merging records every month.
Clay's HubSpot integration is more configurable. You define which Clay columns map to which HubSpot properties, and set conditional push logic — only push if email is verified, only update a field if the existing HubSpot value is empty. This precision matters when enriching existing CRM contacts where you want to avoid overwriting manually entered data.
Lusha's HubSpot integration requires the Teams plan or above. On the Starter tier, export is CSV only. If Lusha sits inside a Clay waterfall, this tier restriction is irrelevant — Clay handles the HubSpot push regardless of which enrichment provider supplied the data.
What changed in 2025–2026: AI-assisted lead scoring built into all three platforms
In 2025, all three platforms shipped native AI scoring features. The implementation differences matter for a UK SME stack.
Apollo launched ICP Fit Scoring in Q1 2025, trained on your closed-won deal data to score incoming prospects before they enter a sequence. The model runs inside Apollo without a separate AI subscription. It performs well on firmographic signals — headcount, industry, funding stage — and less reliably on intent signals unless your target accounts are appearing in Apollo's web-activity feeds.
Clay's AI columns are the more flexible option. You write any prompt and run it across every row in your enrichment table, with Clay calling your model of choice — Claude, GPT-4, or Gemini — per row at model API cost plus one credit. This is the mechanism behind our LinkedIn AI SDR build, where personalisation at volume depends on inline AI calls rather than template variables.
Lusha launched its Buyer Intelligence feature in late 2025, surfacing job-change alerts and basic intent signals alongside contact data. It is less configurable than Clay's AI columns but suits reps who want a green/amber/red signal without a prompt engineering step.
LinkedIn argues directly that third-party contact data cannot replicate in-network buying signals — who is researching your company, which job titles are actively evaluating solutions in your category. That argument is strongest for enterprise sales motions. For UK SME outbound at 20 to 150 headcount, where a meaningful share of decision-makers do not maintain active LinkedIn profiles, the case for Sales Navigator alone is weaker, and the data coverage gap with Clay-enriched Apollo lists is not as wide.
Our recommendation by team size and prospecting motion
The good. Clay with a single Apollo Basic seat and one Lusha API fallback is the highest-coverage, lowest-cost configuration for a 10-person UK SME outbound team. You get 80%-plus coverage on regional UK contacts, centralised enrichment that routes clean data to HubSpot before any rep touches a record, and AI columns for personalisation without per-seat premiums.
The bad. Clay has real setup cost. Building a waterfall table, configuring HubSpot field mapping, writing AI column prompts for your specific ICP, and testing credit consumption against a sample list takes three to five days. Teams without a technical ops resource will need outside help — either from an agency or from Clay's own onboarding service.
The ugly. Data decay is the problem none of these platforms solves. A contact enriched in January has a 15 to 20% chance of being stale by July — job title changed, company rebranded, email address deactivated. If you are not re-enriching your prospect list every 90 days, your reply rate will fall and your spam complaint rate will rise. Set a re-enrichment schedule before you argue about which tool to use. Our cold email deliverability guide for UK SMEs covers the bounce and complaint thresholds that decay makes much harder to stay inside.
By team size:
- Under 5 reps: Clay Starter ($149/month) plus one Apollo Basic seat. Skip Lusha unless your waterfall hit rate drops below 65%.
- 5 to 15 reps with a UK-first ICP: Clay Explorer, Apollo Basic, one Lusha API seat. The stack in this post. £8,900/year.
- 15-plus reps with a mixed UK/US ICP: full Apollo Pro for the sequencing volume and US database depth, with Clay layered on top for UK enrichment quality. Do not replace Apollo with Clay — use both for what each does well.
The teams that rebuild this stack and still get poor reply rates almost always skipped the re-enrichment schedule. Set a 90-day re-enrichment cadence before the first sequence fires — every month of delay after enrichment erodes coverage faster than any waterfall configuration can compensate for.
If your ICP, headcount band, and HubSpot workflow need a prospecting stack built without the tool overlap, we scope and build the Clay waterfall, HubSpot field mapping, and enrichment schedule as a fixed engagement. Book a 30-minute audit to walk through your current stack — we will not recommend a change unless the coverage or cost numbers make the case plainly.