Go to market
Pick the dataset. Cut it to your patch.
We publish verified UK business records across a range of datasets. Merchants is the one that feeds an outbound motion. Name the sectors and regions you sell into and we hand over that cut, ready for the team to work on Monday.
The estate
The datasets we publish.
Merchants is the cut that feeds a go to market motion. It is one dataset, not the company, and the one your team should be working may not be merchants at all.
Merchants
Independent operators and chains across the retail, food and service categories. Every record carries trading status, category and location, with the owner named where we can identify it.
View the dataset →Hospitality
Pubs, bars, cafes and restaurants held as their own cut. Category, trading status and location sit on every record, with the review rating where the site is rated.
Hotels
Independent hotels, guest houses and small groups. Records carry trading status and location, with the operator named where identified.
View the dataset →Quick service
Fast food chains, franchises and takeaways. Records carry format alongside trading status, plus the operator contact where we can verify it.
View the dataset →Licensed fleets
Every licensed HGV, coach and bus operator in Great Britain, matched to the licence. Most are owner run SME fleets the big providers skip.
View the dataset →Custom
A sector we have not published, or an attribute the standard dataset does not hold. We scope it with you before anything is built, and we say up front what we cannot source.
View the dataset →New datasets are always in build.
Scope
Cut to your patch.
Sector, region, category, trading status, rating. We cut on the attributes we hold, so the file lines up with the accounts your team is measured on rather than the ones that happened to be in the box.
If your ICP turns on an attribute outside the standard dataset, that is a custom cut and we scope it with you first. If we don't hold a record, we say so.
The record
What a record carries.
Category and TPS status on every record. Owner names where identified. Direct dials where verified. The list is uneven because the data is, and a file that pretends otherwise is the one that wastes a morning.
Whether the site was trading when the cycle ran. Not inferred, and not carried forward from a file we bought last year.
What the business actually does, on every record, so a sector cut is a filter rather than a guess.
On every record. Clean or restricted, screened before delivery and stated rather than assumed.
City and postcode. This is the field a territory is cut on, so a patch is drawn once and holds.
Where identified. We mark the records that carry a name rather than padding the column, so your team knows before it dials.
Where verified. Attached to most records, never generated, and flagged per record when it is not there.
The public review rating where the business is rated. A useful activity signal when a rep is sequencing a patch.
The week
How teams run it.
Pull the territory slice
A head of sales opens the portal and filters the cut down to the patch in play: region, category, trading status. No ticket, no wait on a data team.
Split it and export
Export the slice to CSV and import it into the CRM the team already runs. You move the data on your terms, we don't push into your infrastructure. If the team would rather pull it, the API is there behind auth.
Work the flags, not the patch
The dataset is rebuilt on a rolling cycle. Closures fall out, new openings come in, and the records that changed are flagged on the next cycle, so nobody reworks a territory that only moved at the edges.
FAQ
Frequently asked questions
Can you scope the data to our ICP?
Yes. We cut the dataset by sector, region, category and the other attributes we hold, so the file matches the accounts you sell to rather than the ones that came in the box. Merchants is the usual starting point for a go to market motion, but the estate also holds hospitality, hotels, quick service and licensed fleets, and the right cut is sometimes not merchants at all. If your ICP depends on attributes outside the standard dataset, that is a custom cut and we scope it with you first.
Is the data GDPR and PECR compliant?
Yes. Peach Data is registered with the ICO as a data controller. Phone numbers are screened against the TPS and CTPS registers before delivery and only clean numbers are released for calling, supplied controller to controller under UK GDPR. Customers re-screen on the 28 day cycle PECR requires before any campaign. Full registration and policy detail sits on our compliance page.
How often is the data refreshed?
On a rolling cycle. New openings are added and closures are removed, so your team works a market that reflects today rather than last year.
Do records include the owner and a direct dial?
A verified owner or operator name is attached where we can identify it. A direct dial is attached where verified, rather than a generic enquiries line, so reps reach the operator instead of a front desk.
How is the data delivered?
As a filtered CSV or through the platform. Standard column headers import straight into Salesforce, HubSpot, Pipedrive or any CRM that takes a spreadsheet, with no mapping project.
Can I get a sample before buying?
Yes. A pilot gives you a working sample built around the cities and merchant types you sell into, so you can test the depth and accuracy before committing.
Get started
See the records for the territory you sell into.
Pick the cities you sell into. We'll pull a live sample from the dataset on the call.