Reviews
3 questions Bristol buyers ask before choosing prospecting software
Bristol buyers weigh prospecting tools on data provenance, CRM integration and ICO compliance. Here are the three questions vendors must answer.
What to take away
- Bristol buyers assess prospecting tools on three thingsdata provenance, CRM integration and compliance duties.
- Data source checks mean asking for the lawful basis, the collection method and the refresh cycle behind every record.
- CRM integration questions cover field mapping, deduplication, sync direction and what happens when a contact is deleted.
- Compliance sits with you, not the vendorUK GDPR, PECR and ICO guidance govern bought lists and shared leads.
- The city's B2B services cluster expects named references, a Bristol-aware contract and a security answer before a pilot.
- A short paid pilot on your own CRM data settles more than a feature demo ever will.
Why Bristol buyers ask different prospecting questions
Bristol is not a satellite sales office. The city has a dense B2B services cluster: marketing agencies, consultancies, accountancy practices, legal firms and a growing software sector, all selling to each other as much as to London.
That mix changes what buyers ask. A Bristol agency buying prospecting tools is usually buying on behalf of clients as well as itself. The list it builds may sit inside a client's CRM, under a client's privacy notice, within a client's retention schedule.
The ONS business services data tracks output and turnover across this sector, and it has been the quiet engine of UK growth. Bristol's share is small but concentrated, which means word travels. A vendor that mishandles one agency's data will hear about it across the city's sales-tech meetups within a quarter.
Buyers here also sit close to the South West's public sector and university base. University of Bristol and UWE spinouts buy B2B services locally. Those buyers tend to have procurement habits formed in regulated environments, and they ask for paperwork early.
The practical result: price and feature lists settle nothing. Three questions decide most deals.
Bristol buyers can put these questions to named prospecting platforms such as Cognism, Apollo.io, Lusha and ZoomInfo; assess each against the same evidence requests rather than relying on brand recognition.
Question one: where does the data come from?
This is the first question in almost every serious conversation, and it is the one vendors most often fudge.
Vendor A vs Vendor B data provenance
Vendor A
- Source
- Scraped directory
- Consent record
- None
- Lawful basis
- Unstated
- Balancing test
- Absent
- Suppression file
- None
Vendor B
- Source
- Licensed broker
- Consent record
- Documented
- Lawful basis
- Legitimate interests
- Balancing test
- Documented
- Suppression file
- Updated monthly
"We have millions of contacts" is not an answer. Bristol buyers want provenance: where each record was collected, when, under what lawful basis, and whether the person was told their details would be used for marketing.
Data source provenance checks
Ask for these seven things in writing before a trial:
- The original source of the data and any brokers or intermediaries in the chain.
- How and when each record was collected.
- The lawful basis for using the data for your intended marketing purpose, including the legitimate-interests assessment where relevant.
- What privacy information people received about the use of their data.
- When records were last checked and how often they are refreshed.
- How objections, opt-outs and suppression requests are checked and applied.
- What uses the supplier’s licence permits, and what evidence it can provide for these checks.
Data provenance checks to request
- Named source for each data category
- Lawful basis for B2B marketing contact
- Date of last email/phone verification
- Consent collected and exact wording used
- Suppression and opt-out process speed
- Vendor is controller or processor
- Audit trail if ICO asks questions
A vendor that cannot produce the first two items is not worth a pilot. A vendor that produces all seven is worth a premium.
A worked example
A Bristol marketing agency wants 2,000 contacts at professional services firms across the South West. Vendor A supplies a list from a scraped directory with no consent record. Vendor B supplies records sourced from a licensed broker, with the lawful basis stated as legitimate interests, a documented balancing test and a suppression file updated monthly.
On price, Vendor A wins. On risk, the agency is now the controller for a list it cannot defend. If a recipient complains, the agency answers the ICO, not the vendor.
That asymmetry is why provenance questions come first here. Buyers in Bristol's B2B services cluster often carry professional indemnity cover and client contracts that assume they can evidence their data sources. For a wider look at how these evaluations are run, see prospecting software reviews explained.
Question two: how does it integrate with our CRM?
Bristol agencies rarely run one CRM. They run their own, plus whatever the client uses. HubSpot, Pipedrive, Salesforce and Zoho all appear in the same pitch deck.
CRM integration requirements to verify
- Field mapping and remapping options
- Sync direction and trigger
- Deduplication match keys and merge behaviour
- CRM deletion propagation
- Rate limits on your plan
- Error handling visibility
So the CRM integration question is not "do you connect to HubSpot?" It is "what exactly crosses the boundary, in which direction, and what happens when it goes wrong?"
CRM integration requirements
| Requirement | What to ask | Why it matters |
|---|---|---|
| Field mapping | Which fields map to which, and can we remap? | Custom fields break silently |
| Sync direction | One-way or two-way, and on what trigger? | Two-way sync overwrites human edits |
| Deduplication | Match keys used, and merge behaviour | Duplicate contacts inflate reporting |
| Deletion | Does a CRM deletion propagate back? | Retention duties follow the record |
| Rate limits | Requests per hour on our plan | Bulk imports stall mid-run |
| Error handling | What we see when a sync fails | Silent failure costs pipeline |
Two-way sync sounds better than it is. If a salesperson corrects a job title in the CRM and the tool overwrites it overnight, trust in the data collapses.
Ask for a sandbox and run your own records through it. A vendor that will not give you a sandbox is telling you something. For a structured way to compare options, see prospecting software product comparison.
Question three: what compliance duties apply to us?
This is where Bristol buyers separate from the national average. The city has a high concentration of agencies handling personal data for clients, so the compliance conversation starts earlier and goes deeper.
Compliance duties when buying prospect data
- Buy prospect data from broker
- You become controller for that use
- Do your own due diligence on broker
- Keep records of your decisions
- Apply PECR to email, calls, texts
- Soft opt-in does not cover bought lists
Compliance duties for Bristol buyers
The short version: buying data does not transfer responsibility. If you use bought prospect data for direct marketing, you are a controller for that use, and the ICO expects you to have done your own checks.
The ICO's Direct marketing guidance, including its advice on buying and using marketing lists, sets out what this means in practice, including due diligence on the broker and records of your decisions.
PECR sits alongside UK GDPR. It governs electronic marketing: email, calls and texts. Soft opt-in applies to your own customers and enquirers, not to bought lists. Corporate subscribers have some latitude on email, but sole traders and partnerships count as individuals, and Bristol's agency sector sells to a lot of both.
If you share leads with a partner, a common arrangement between complementary Bristol agencies, the ICO's Data sharing: a code of practice covers the controller-to-controller and controller-to-processor distinctions, plus what belongs in a written agreement.
And if you hold prospect data in a CRM, security is part of the duty. The ICO's A practical guide to IT security offers practical advice for small organisations, while UK GDPR Article 32 sets the security-of-processing requirement. A vendor that cannot describe its encryption at rest and in transit, its access model and its breach notification timeline has not finished its homework.
None of this is exotic. It is the standard set of questions a competent buyer asks, and it is cheaper to ask them before signing than after a complaint.
What Bristol's B2B services cluster expects from vendors
Vendor expectations in the city are shaped by the buyer mix: agencies, consultancies and scale-ups, often selling to each other, often with clients watching.
Expect these in a Bristol pitch:
- Named customer references relevant to your type of work.
- A written account of data sources, lawful bases and due-diligence evidence.
- A contract that clearly sets out client and supplier responsibilities for data.
- A clear explanation of the vendor’s security controls and breach-notification process.
- A demonstration of CRM field mapping, sync behaviour and deletion handling.
- A named support contact and an explanation of how urgent problems are escalated.
- A pilot using your own CRM and sample records, with the scope and success criteria agreed in advance.
What Bristol buyers expect in a pitch
- Named South West reference you can call
- Written data provenance answer, not a slide
- Sandbox using buyer's CRM and records
- Clear pricing in pounds with limits
- Security summaryhosting, encryption, breach
- Contract naming controller and processor
- Exit plandata out, format, deletion
Bristol buyers also compare suppliers on support responsiveness, because a stalled sync during a client campaign is a commercial problem, not a technical one. A structured approach helps here: see prospecting software supplier comparison.
Once a tool is chosen, the work shifts to rollout. Plan that phase properly with this guide to prospecting software tool implementation, because a tool that never reaches the sales floor returns nothing.
One last local point. Bristol's sales-tech meetups and the wider South West network mean vendor behaviour is visible. Deliver a clean pilot, answer the three questions straight, and referrals follow. Bluff on provenance and the city will know.
