
Reviews
Reviewing lead networks starts with finding out who actually offers the service
Lead generation network reviews need verified identities, common buyer tests, evidence limits, declared conflicts and a publication-day recheck.
A useful review does not reward the provider with the longest feature page. It tells an England buyer what was examined, what remains unknown and what evidence justifies a limited trial.
That distinction matters. A marketplace, a data supplier and a managed agency can all be called a lead network, yet each allocates risk and work differently.
This guide rests on desk research completed on 5 September 2026. The byline and fact checker are not yet assigned.
No supplier funded the research, supplied an account or has an affiliate relationship with this site. No live lead, payment, integration, deletion request or complaint journey was tested. The current verdict is therefore a method for selection, not an endorsement or performance finding.
What to take away
- Registry records confirm legal identity and filing status only, not service quality or regulatory approval.
- Privacy provenance, security and a usable exit cannot be offset by a lower fee.
- Reviews and case studies can suggest questions to investigate but do not establish representative rates or outcomes.
Start with the buying configuration
The same service may suit a sole trader seeking nearby project enquiries and fail a regulated business that needs documented onward-sharing permission. Before building a longlist, record:
- the service categories and English areas required;
- whether the buyer wants introductions, contact data, directory visibility or managed acquisition;
- whether people or corporate subscribers will be contacted, by which channel and by whom;
- the buyer's acceptance states, complaint route, suppression process and fulfilment capacity;
- the billing unit, renewal route, credit rules and exit evidence required.
Do not turn these entries into weights too early. Privacy provenance, security or an unusable exit cannot be compensated for by a lower fee. The ICO's lead collection guidance expects organisations that buy or rent marketing information to make proportionate checks, rather than accepting assurances at face value. That is a UK regulatory boundary, not an England-only market statistic.
Establish who is actually offering the service
A trading name is not enough for contracting. Record the legal entity named in the terms, its company number, registered address, and the entity that will invoice or process data.
Trading names vs legal entities
Bark
- Trading name
- Bark
- Legal entity
- Bark.com Global Ltd
- Company number
- 10614196
- Registry status
- Active English
Checkatrade
- Trading name
- Checkatrade
- Legal entity
- Vetted Limited
- Company number
- 04285394
- Registry status
- Relevant record
MyBuilder
- Trading name
- MyBuilder
- Legal entity
- MyBuilder Limited
- Company number
- 05272398
- Registry status
- Filed record
Companies House can confirm filed identity and status. It warns that it does not check the accuracy of filed information. Registration proves neither service quality nor regulatory approval.
Three current public records illustrate the exercise. Bark's customer terms name Bark.com Global Limited; the Companies House record for company 10614196 shows an active English company. Checkatrade's platform terms identify Vetted Limited as the operator trading under that name, and company 04285394 is the relevant record, not a similarly named dormant company.
MyBuilder's terms identify MyBuilder Limited, appearing as company 05272398.
A worked example: the trading name MyBuilder in the terms leads to MyBuilder Limited, and company number 05272398 finds the filing record on Companies House.
Those matches establish legal identity only. They say nothing about whether a particular buyer should join, whether enquiries are suitable or whether contract terms are acceptable.
Use an evidence hierarchy
Build the dossier from materials that answer different questions:
Evidence hierarchy for supplier dossiers
- Law and regulator guidancelegal boundaries only
- Registry recordsidentity and filing status
- Signed terms and schedulesobligations and remedies
- First-party service documentssupplier claims only
- Controlled buyer testsrouting, export, suppression
- Customer reviews and case studiesquestions, not rates
- Law and regulator guidance.Use these for legal boundaries, not product scoring. The ICO separates controller and processor status according to actual decisions and activities in its roles guidance.
- Registry records.These help resolve identity and filing status. They are not certification.
- Signed terms and schedules.These allocate service obligations, billing and remedies, but cannot create a lawful marketing permission that the underlying facts do not support.
- First-party service documents.They show how the supplier describes its offer. Treat every feature or process description as a supplier claim until demonstrated in the buyer's configuration.
- Controlled buyer tests.Synthetic or properly authorised fixtures can inspect routing, evidence export, suppression and deletion. A test result applies to the tested version and settings.
- Customer reviews and case studies.These can reveal questions to investigate. They do not establish a representative rate, outcome or England-wide quality level.
The CMA's work on online consumer reviews is a reason to examine how reviews are collected and presented, not to assume that a prominent rating is true or false. Badges, directory positions and absence of an adverse ruling are likewise not endorsements.
Current ICO and CMA guidance is published on ico.org.uk and gov.uk; the links in this article point to the pages reviewed.
Apply the same comparison gates
Every candidate should face one common question set. Leave a cell as unknown when the public record does not answer it.
Common comparison gates
- Intended user and territoryremove if out of scope
- Source and recipient modelstop if unreconstructable
- Workflow stateshold integration if unreconciled
- Billing unitdo not model undefined chargeable event
- Privacy and PECR rolessend to named reviewers
- Securitypause if critical evidence missing
- Accessibilityreject inaccessible essential path
- Complaints and creditsescalate unresolved cases
| Gate | Evidence to request | Failure response |
|---|---|---|
| Intended user and territory | Service definition, supported categories and postcode rules | Remove if the buyer configuration is outside scope |
| Source and recipient model | Collection journey, named recipient wording and provenance record | Stop if the recipient or source cannot be reconstructed |
| Workflow states | Definitions for submitted, checked, shared, accepted, rejected and credited | Hold integration when events cannot be reconciled |
| Billing unit | Executed order form, VAT treatment and credit mechanism | Do not model cost from an undefined chargeable event |
| Privacy and PECR roles | Data-flow map, purpose decisions and channel-specific assessment | Send to named privacy and PECR reviewers |
| Security | Architecture evidence, access controls and incident duties | Pause if critical evidence is missing or stale |
| Accessibility | User journeys, current conformance evidence and remediation owner | Reject an inaccessible essential path |
| Complaints and credits | Ownership, evidence clock, escalation and remedy terms | Escalate an unresolved wrong-recipient or billing case |
| Renewal and change | Notice route, version control and material-change rights | Block auto-renewal without an approved recheck |
| Portability and exit | Export format, deletion evidence, retention and assistance | Keep the incumbent until a safe rollback is proven |
Security assurance should be evidence-led. The NCSC's supplier assurance questions cover governance, incidents, data, testing and contractual controls, but they do not certify a vendor. Accessibility and security remain separate gates: strength in one cannot repair failure in the other.
Compare public supplier models without inferring results
Bark's service explanation describes matching a customer's request with professionals, who can decide whether to use credits to contact that customer. Checkatrade's platform terms describe a platform through which customers can find and contact approved tradespeople, and Vetted Limited's use of the Checkatrade trading name is explicit there.
MyBuilder's current terms describe a marketplace connecting customers and tradespeople and set out a shortlist concept; they identify MyBuilder Limited and were updated in March 2026.
These public documents describe mechanisms, not England conversion rates, vetting scope, job values, response quality or buyer suitability. They are not three interchangeable products.
A buyer should compare the precise journey it intends to use, including when contact details become visible, what event is chargeable and how a disputed introduction is evidenced. No prices were compared, because editions, applicability and billing units were not established on a common current basis.
Distinguish a platform review from an agency review
An agency may operate several channels, select data sources and make targeting decisions. Its review therefore needs evidence of people, subcontractors, campaign controls, creative approval, complaint handling and the client's ability to audit. A platform review concentrates more heavily on the configured workflow, account permissions, event definitions and product terms.
Ask the agency to map who determines the purpose and essential means of each processing activity. A contract label cannot settle the point. Where sharing occurs, the ICO's data-sharing agreement guidance offers a practical structure for recording parties, purposes, roles, datasets, standards and review arrangements. It does not make every sharing arrangement lawful by itself.
Agency references should be verified with the referee's consent and limited to questions the referee can actually answer. A case study chosen by the agency remains selected evidence. No adverse inference should be drawn from a provider declining to reveal another client's confidential information.
Run a bounded acceptance test
A document review can narrow a field, but it cannot validate a configured service. Before real personal data or spend is released, create a test plan with synthetic records or properly authorised fixtures. Assign an owner and expected evidence to each step:
Bounded acceptance test steps
- Accept and quarantine a test submission
- Reject ineligible category without leaking data
- Show recipient disclosure before sharing
- Route objection and confirm suppression
- Send wrong-recipient report to investigation queue
- Reconcile accepted, rejected and credited events
- Exercise keyboard and error-recovery paths
- Export record and request deletion
- accept and quarantine a test submission with its source record;
- reject an ineligible category without leaking contact data;
- show the actual recipient disclosure before sharing;
- route an objection and confirm suppression across relevant destinations;
- send a wrong-recipient report into a controlled investigation queue;
- reconcile accepted, rejected and credited events against the billing export;
- exercise accessible keyboard and error-recovery paths;
- export the agreed record and request deletion under the test procedure;
- restore the pre-test state if any high-risk gate fails.
The ICO explains that an objection to direct marketing requires that processing to stop in its right-to-object guidance. A test of suppression plumbing does not decide the lawful basis for earlier collection, nor does it grant permission for another channel.
Record exactly what passed, failed or remained untested. A partial run must not be presented as an end-to-end result. The proceed decision should be bounded by category, territory, volume, account configuration and time, with named rollback authority.
Make conflicts and scoring visible
This research is non-ranked. A numerical total would imply that missing legal, provenance or security evidence can be traded against convenience. If a buyer later scores operational preferences, publish the formula before viewing results and keep the non-compensating gates outside it.
Disclose supplier payments, affiliate links, free access, gifts, ownership connections and previous client work. A declaration of no known conflict is still time-bound. The reviewer should also identify who performed each test and retain the evidence, rather than using the byline as a substitute for method.
Recheck before publication and renewal
Terms, legal entities, service journeys and regulator guidance can change. On publication day, reopen every linked record, confirm the trading entity, note the terms version and retest any material claim. Withdraw a named entry when identity or first-party evidence no longer matches. At renewal, repeat the checks for price unit, data flow, subcontractors, complaints, export and deletion.
A named fact checker and qualified UK privacy, PECR, security, accessibility, consumer, advertising, commercial and procurement reviewers must examine the eventual buyer configuration. Their work can define a safe decision boundary; it cannot guarantee legality, service quality or commercial results.
Before you act
- Record service categories, English areas and contact channels required.
- Match the legal entity in the terms to its Companies House record.
- Leave a comparison cell unknown when the public record does not answer it.
- Request evidence for each gate before integrating or paying.
- Keep the incumbent until a safe rollback is proven.
- Send privacy and PECR questions to named reviewers.
Common questions
What does this guide's current verdict actually amount to?
It is a method for selection, not an endorsement or performance finding. It sets out the questions to ask; it does not confirm how any service performs.
Why is a trading name not enough for contracting?
A trading name does not identify who is legally bound. Record the legal entity named in the terms, its company number, registered address and the entity that will invoice or process data. Companies House confirms filed identity and status, but warns it does not check the accuracy of filed information.
How should a platform review differ from an agency review?
An agency may run several channels, choose data sources and make targeting decisions, so its review needs evidence of people, subcontractors, campaign controls, creative approval, complaint handling and client audit rights. A platform review concentrates more on the configured workflow, account permissions, event definitions and product terms.
In this guide
- Three lead marketplaces compared on one buyer framework, no scores inventedCompare three lead marketplaces by one buyer framework, with verified operators, documented service models, explicit unknowns and no invented scores.
- Reviewing a lead generation agency before any live engagementA defensible agency review for England verifies identity, scope, channel controls, provenance and exit evidence before any bounded live engagement.
- Selecting a lead network with recovery and exit proven before signatureUse this lead network selection checklist to verify identity, provenance, configured tests, non-compensating gates, rollback and exit evidence.



