The top of your funnel,run likeinfrastructure

We run the market layer under your outbound. The addressable market mapped, every account verified and screened, cut to the territories your team is measured on, and kept true cycle after cycle.

Book a demo
Isolated tenantsIndividual API keysEvery export loggedVersioned datasetsScreened before releaseICO ZC101614
A note on how we work

We sit where the revenue team never had the headcount.

Most sales organisations have someone who owns pipeline. Almost none have someone who owns the market above it: how big it really is, which accounts are live, who signs, and whether the list is still true this quarter.

That is the job we take. We define the market you sell into, keep every record verified and screened, and hand each rep a patch they can work on Monday. You keep the pipeline. We keep the ground under it.

Built and maintained by the team that builds the data. If we cannot source something, we say so before you sign.

What sits behind it

The platform is engineered like a system your security team would sign off, because it is.

Secure by design

Each organisation runs in its own isolated tenant with individual API keys. Every export is logged with who took it and when. Nothing leaves the platform unscreened.

Engineered, not assembled

Datasets are versioned and rebuilt on a rolling cycle. Every record carries the date it was last verified, and what changed between cycles is flagged rather than buried.

Run by operators

The people who built the data have sold into these markets. Scope is agreed with your team before anything is cut, and the numbers you see are the numbers we hold.

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. Trading status, category and location on every record, with the owner named where we can identify it.

Hospitality

Pubs, bars, cafes and restaurants held as their own cut. Category, trading status and location on every record, with the review rating where the site is rated.

Hotels

Independent hotels, guest houses and small groups. Trading status and location, with the operator named where identified.

Quick service

Fast food chains, franchises and takeaways. Format alongside trading status, plus the operator contact where we can verify it.

Fleet operators

Every HGV, coach and bus operator in Great Britain, held as one record per operator. Most are owner run SME fleets the big providers skip.

Custom cut

A sector we have not published, or an attribute the standard dataset does not hold. We scope it with you first, and we say up front what we cannot source.

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 a vendor found easiest to sell.

Your patch
HospitalityMerchantsHotelsQuick serviceFleet
North WestYorkshireMidlandsLondon
TradingRated 4+Owner named
Records in cut[N]
With owner named[N]
TPS clean100%
ExportCSV, portal, API
One patch, drawn on the attributes the dataset already holds. Anything outside them is a custom cut.

What a record carries

Category on every record and TPS status on every UK 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 file that lets you down.

Trading status

Whether the site was trading when the cycle ran. Not inferred, and not carried forward from a file we bought last year.

Category

What the business actually does, on every record, so a sector cut is a filter rather than a guess.

TPS status

On every UK record, clean or restricted, screened against TPS and CTPS before delivery and stated rather than assumed. In other markets the local rules apply before anything is released.

Location

City and postcode. This is the field a territory is cut on, so a patch is drawn once and holds.

Owner name

Where identified. We mark the records that carry a name rather than padding the column, so your team knows before it dials.

Review rating

The public review rating where the business is rated. A useful activity signal when a rep is sequencing a patch.

How teams run it

1
Pull the territory sliceA 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.
2
Split it and exportDivide the slice between reps, export each share as CSV and load it into the CRM they already use.
3
Work the flags, not the patchThe dataset is rebuilt on a rolling cycle. Closures fall out, new openings come in, and the records that changed are flagged, so nobody reworks a territory that only moved at the edges.

See your market before you commit to it

Name the territories your team is measured on. We will map them and pull a live, screened sample on the call.

Book a demo

Frequently asked questions

Yes. Records carry city and postcode, and the portal filters by territory, segment and fit tier. We can also cut a sample to your patch before you commit.