Before you run a prospecting software supplier comparison

Test the sample, not the headline

Ask how records are collected and refreshed, and what share of a sample can be verified by hand. Check 50 records rather than trusting a headline coverage figure. Then load 200 of your existing records into a sandbox, count enrichments and duplicates, and measure how long the sync takes.

The ICO's guidance on buying or renting contact data asks who compiled the information and what consent records exist. A sample review can test whether records support the claimed provenance, while data protection checks help frame the wider compliance review before purchase.

Build a weighted score that separates options

Give data provenance the greatest weight and integration the next, followed by contract flexibility, support, compliance and price. Weak CRM integration creates manual work that can erode the business case within a quarter.

Ask what share of records can be checked by hand rather than treating a headline coverage claim as proof.

Keep the rubric short enough that two people scoring independently land in similar places; six criteria is usually enough. Score each criterion out of five, multiply by its written weight and total the result. Put the weights in writing before any demo so the scoring cannot drift around a supplier the team already favours.

Pair each score with a quality checklist so every number rests on a pass-or-fail test. A supplier scoring four for provenance and two for integration will usually lose to one scoring three on both, because integration debt compounds monthly. Price comes last deliberately: cheap licensing on stale data can be the most expensive option.

Treat features as a baseline, not a verdict

Serious suppliers often meet most listed features, flattening the grid and shifting attention to the strongest demo. Yet a tick says neither whether contact data is accurate enough to use nor whether you can leave with your history intact. Those tests require evidence beyond a feature count.

A comparison earns its name only when it produces a ranking you could defend to a finance director, supported by weighted criteria, evidence for each criterion and a record of rejected options. If the requirement is still being framed, What prospecting software tools and providers mean for 2027 buying decisions explains how categories differ before scoring begins.

Keep the winning score and the exit route

Score independently first, then reconcile differences; disagreement is useful because it exposes assumptions nobody has recorded. Keep a one-page decision record listing criteria, weights, scores and the two or three facts that decided the result. That record protects the choice if a new tool appears in six months.

At renewal, read the contract terms for notice periods and data export, and account for the cost of leaving. A supplier unable to state its notice period in one sentence is telling you something. Confirm that your history can be extracted rather than treating exit rights as boilerplate.

Where campaigns rely on contact data, establish how a marketing data incident would be reported. The ICO's personal data breaches guide says a notifiable breach must be reported within 72 hours of becoming aware of it. Ask the supplier to identify that duty in its contract and incident process, including the route for breach reporting.

Where organisational rules set how tools are approved and reviewed, software selection in England can help frame the process alongside scoring. Keep the rejected-options record with your decision note, so the final ranking shows which evidence supported the selection and why alternatives did not proceed.

Complete these checks before signature

Before signing, leave a written trail covering predetermined weights, verified source records, a sandbox result, exit terms and incident handling. Check each item below, then file the decision record. Together, these steps make the supplier ranking easier to explain and support the choice after the selection process is over.

Settle the remaining shortlist questions

The remaining decisions concern shortlist size, price weighting, the usual reason comparisons go wrong and a realistic timetable. These answers use the same evidence rules as the table: keep the supplier pool manageable, score comparable products and include sandbox work before completing the ranking.

How many suppliers should be scored?

Score three to five suppliers. Fewer gives you no real comparison, while scoring more than five rarely changes the ranking. A focused shortlist also lets reviewers apply the same written weights and evidence requests to each option, including checks on provenance and integration.

Should price carry more weight?

Only give price greater weight when the shortlisted suppliers are genuinely comparable on data quality and integration. Otherwise, you are comparing different products. A lower licence price cannot settle the choice if one option relies on stale data or creates manual integration work that erodes the business case.

Why do comparisons go wrong?

The common failure is setting criteria after the demos. The rubric can then bend towards a supplier the team already favours instead of reflecting priorities agreed in advance. Recording criteria and weights before demonstrations limits that drift and gives reviewers a consistent basis for comparing evidence.

What is a realistic timetable?

Four to six weeks is realistic for a mid-market team, including sandbox testing and two rounds of scoring. Allow that period for the evidence review and independent scoring to be completed before the decision record is filed, rather than treating the supplier demonstration as the end of the comparison.