How UK teams can assess prospecting software standards

What to take away

Recent data law changes have pushed service standards for prospecting software from feature promises to documented commitments on data, uptime and support.
The Data (Use and Access) Act 2025 altered how marketing data can be used, so contracts need clauses that track the new rules.
Buyers in England should ask for a named service owner, a first response within four working hours, 99.9% monthly uptime and evidence of how suppression records are kept.
Standards hold only if someone owns them internally, so the operating model matters as much as the tool.
The table below helps teams choose the right level of assurance for their size and risk.

What to assess in a service standard

When assessing prospecting software, contact coverage and ease of use are only part of the decision. Buyers should also ask suppliers to document how they handle consent, suppression and source records.

What a usable standard contains

Named accountable person
Support response time
Process for removing suppressed contacts
Refresh frequency
What happens when target missed

The Data (Use and Access) Act 2025 is part of the UK legal framework relevant to data use, but it does not make the supplier solely responsible for compliance. For an England team, treat each contractual commitment as something to verify at renewal.

What a workable standard should specify

A workable standard sets a first response within four working hours, a fix or workaround within one working day, and 99.9% monthly uptime for core search and export functions. These are typical targets, not quotes. The clause should name the person who owns each one and the remedy if a target is missed.

The internal side matters as much. A supplier can only meet a standard if your own workflow supports it, so review your prospecting software operating workflow before agreeing terms.

Where supplier standards break down in practice

Three gaps recur. Refresh schedules exist only in someone's head. Suppression requests sit with one person who may leave. Response times are promised rather than measured. Each gap shows up in the contract. Ask for the last three months of ticket data and the named owner of the suppression register.

If either answer is verbal, the standard is not yet real.

The compliance side of a service standard

The Information Commissioner's Office publishes a step-by-step guide to direct marketing for small businesses covering consent, the right to object and record keeping. A supplier standard should mirror those expectations rather than paraphrase them loosely. A provider that cannot say how a contact was sourced has a service failure on its hands, not an administrative one.

Compliance points a standard should mirror

Consent
Right to object
Record keeping
How a contact was sourced

To verify provenance, ask for a sample of 20 records from your target segment. For each record, request the source, the collection date and the lawful basis. Check that the supplier can show the same fields in its own system within one working day. If it cannot, mark the source record as unverified.

Checking segment data and price

Segment definitions need a relevant, documented source. For an environmental segment, the Office for National Statistics publishes environmental accounts data, which may be useful; for other segments, ask the supplier to identify a source that fits the definition. The written standard should state how often segment data is refreshed.

Price alone does not show assurance. A self-serve list might cost £99 a month and promise little in writing. A managed standard with a named contact, written refresh and response targets often runs from £400 to £900 a month. Audit rights and source-record evidence sit above that. Treat these as typical ranges, not quotes.

Ownership and exit

Standards should survive the end of the contract. Ask what happens to your suppression list, notes and activity history if you leave.

An example clause reads: 'The supplier shall keep a suppression register and update it within 24 hours of a valid request. On termination it shall return or delete all client suppression records, notes and activity history within 30 days, with written confirmation.'

A supplier that holds your suppression records hostage is a risk you do not need. Include this review in your annual contract cycle, alongside checks on data return, deletion and access.

Choosing the right level of assurance

A ten-person sales function and a two-hundred-seat operation carry different exposures. The table sets out a workable split.

Choose

Small team, low volume, single market: Basic terms with a named contact and a written refresh schedule
Mid-sized team, several segments: Documented standards covering suppression, refresh and response times
Regulated or high-risk sector: Contractual audit rights and evidence of source records
Renewal under budget pressure: Re-test the standard against twelve months of tickets

Avoid

Small team, low volume, single market: Bespoke service-level agreements with penalties you cannot enforce
Mid-sized team, several segments: Verbal assurances from a sales representative
Regulated or high-risk sector: Suppliers who will not disclose data provenance
Renewal under budget pressure: Renewing on price alone

Making the standard stick

Assign one person to own the relationship and one metric to watch each quarter. A single tracked measure beats a page of aspirational language.

Reviewing at renewal

Pull the last twelve months of support tickets and suppression requests. If the supplier met the written standard, renew. If not, the conversation is about remedy, not loyalty.

Common questions

Do these standards apply across the UK?

The data protection framework here applies UK-wide. Operational detail, such as how a supplier staffs its England support desk, may vary, so confirm coverage in the contract.

How often should contact data be refreshed?

There is no single legal figure. What matters is that a frequency is written into the agreement and that you can check it. Monthly is a common working assumption for active segments.

What should happen when a standard is missed?

The contract should set a remedy, such as a service credit or a corrective plan with a deadline. Without a stated consequence, a standard is only a preference.

Can a small business rely on supplier assurances alone?

No. The ICO guidance expects the business running the campaign to keep its own records, so treat supplier assurances as one input.