Check the evidence behind any prospecting software review methodology

What to take away

Define the scope before you score anything

Start by writing down the decision the review has to serve. A small team assessing an email tool needs different evidence from an enterprise replacing a large platform. Name the buyer profile, deal size band and sectors in view.

Then fix the boundaries. Say whether the review covers pricing, data sourcing, integration, support and contract exit terms. If a category is excluded, label it as excluded so readers can judge whether the gap matters.

Separate claims, evidence and judgement

Vendor claims are what the supplier publishes: feature lists, uptime figures, accuracy percentages. Record them with the date and page, and treat them as assertions until something independent corroborates them.

Independent evidence means regulator guidance, official statistics, certification records or published standards. Editorial judgement is the reviewer's view on whether that evidence supports the claim. Keep the three apart so a weak claim cannot borrow authority from a strong source.

For user-review evidence, compare the published review and verification information from G2, Capterra and TrustRadius. Record what each platform says about review verification, moderation and incentives. These are review platforms, not regulators, and their ratings do not independently prove a prospecting tool's data quality or compliance.

Where personal data feeds a prospecting workflow, check the ICO's Guide to accountability and governance against the UK GDPR and the Data Protection Act 2018. You can also search the ICO register of fee payers using the supplier's legal name. Registration is not proof of compliance; this is a governance check, not a product feature.

Score against weighted criteria

Build a scoring sheet with criteria, weightings and evidence notes. Typical criteria include data coverage, pricing transparency, integration effort, support terms and exit clauses. Score only what you can evidence.

Set weights for the named buyer profile and explain the rationale for each one. A smaller team might prioritise pricing transparency, while an enterprise buyer might put more weight on integration effort or support terms. Show the weights openly so readers can re-run the scoring for their own needs.

For a fuller comparison structure, use the linked guide to prospecting software reviews and comparison methods to line up criteria across vendors without collapsing them into one flattering number.

What this method does not assess

This method does not include hands-on testing, sandbox trials, mystery shopping or reference calls. It also does not verify security certifications. For ISO/IEC 27001, check the certificate's scope, validity and issuing certification body; where applicable, check IAF CertSearch. SOC 2 Type II is an auditor's report, not a certification, and has no universal public register: request the report and check its auditor, scope and reporting period.

It does not cover every regional pricing variation, and it does not rank suppliers. Where a supplier publishes B2B advertising training, that shows a training offer exists, not that the platform performs well. The LinkedIn Ads certification options are an example of a claim to log as a vendor statement rather than independent proof of outcomes.

Use sector data where it exists

For hospitality, events and entertainment buyers, demand assumptions often rest on leisure spending patterns. The ONS's Overseas travel and tourism bulletin can support a market sizing note. Cite the specific release date and the named data series used, rather than relying on the general statistics page.

Use official data to test a vendor's market claim, not to replace your own pipeline evidence.

Keep an evidence log

Every review should leave a trail: source, date accessed, what it supported and the reviewer's confidence level. Store it with the scoring sheet so you can see which claims have changed at renewal.

A short glossary helps readers use the method consistently:

Use the provider overview as a starting point for identifying suppliers, then apply your own weights. Examples a review might assess include Cognism, Lusha and Apollo.io; their inclusion here is illustrative, not a ranking or endorsement.

Common questions

Does a review methodology prove a tool works?

No. A methodology shows how evidence was gathered and weighed, not how a tool performs in your pipeline.

How do I tell a vendor claim from independent evidence?

Ask who controls the source. If the supplier publishes it, it is a claim. If a regulator or statistics body publishes it, it is evidence you can cite with a date.

Why do weightings change between buyers?

Because deal size, sector and internal capability change what matters. A weighting that suits a small sales team will mislead an enterprise procurement panel.

What should I keep after the review?

The scoring sheet, the weights, the evidence log with dates, and a note of what was excluded.