Restaurant prospect data

What we can find out
before anyone calls

Short version of what's gettable on a restaurant, roughly how we get it, and how deep you'd want us to go. Tell us which parts matter and we'll build to that.

What we can pull per restaurant

Proven already built and in the sample files   Short build known route, days not weeks

The business

  • Name, full address, category
  • Main phone line
  • Website
  • Rating, review count, price tier
  • Single site or multi-location
  • Size band (from review volume)

Who runs it

  • Owner or GM by name
  • Their actual title
  • The source that proves it
  • LinkedIn profile where they have one
  • Legally filed owner and officers Short build

What they run today

  • Current POS and online ordering
  • Delivery platforms they use
  • Reservation platform
  • Which POS vendor to displace

Reasons to call now

  • Currently hiring, and for what
  • Health inspection dates Short build
  • New or renewed licences Short build
  • Review velocity, growing or slipping

Roughly how we do it

Same five steps whichever campaign it is. Only step 1 changes.

  1. Start from the qualifying signal, not from a list. For a POS pitch that's which system they run today. For payroll it's size. For Aloha it's proof they're on Aloha.
  2. Pull the public record. State business registries, liquor licences, health permits. These name the legal owner and are free in a lot of states.
  3. Cross-check against the open web. Their own site, local press, job adverts, review platforms. Different sources, same person, is a much stronger answer.
  4. Throw away anything we can't prove. A name only survives if a real source states their role. Guesses get deleted rather than shipped.
  5. Hand it over with the evidence attached. Every named person comes with the quote and where it came from, so any row can be spot-checked in seconds.

Why step 4 matters more than it sounds. On the Arizona sample we found a candidate name for roughly 8 in 10 restaurants and kept 7. The ones we dropped came from customer reviews, which is where a reviewer's own name gets mistaken for the owner. A caller asking for the wrong person has burned that account. A blank hasn't.

How deep do you want to go

Three levels. They stack, so you can start light and add later.

1. What's already built

ready now

Business, phone, website, current POS, size, plus a verified owner or GM where the open web names one. This is what's in the sample files.

2. Add the public record

days

Pull state business registries and licence records so the owner comes from a legal filing rather than an article. Much higher coverage, and it's the difference between "we found a name" and "this is the registered owner." Free in a good number of states.

3. Add timing and direct contact

longer

Inspection dates, licence renewals and hiring activity, so your team calls when something just changed rather than at random. Plus direct-dial enrichment where it's available and you're comfortable with it.

Two things we'd rather flag now

Personal mobiles are the hard one

Independent restaurant owners barely exist in the databases most vendors resell. It's doable through other routes, but there are rules around calling mobiles, so it's worth a conversation rather than an assumption.

Payroll and processing incumbents

POS leaves a public trace. Who does their payroll or card processing generally doesn't. We can get at it in some cases, but not as a reliable column across a whole list.

What would help us most from you:

  • Which of the data points above actually change whether a call happens?
  • Anything on the list you'd never use, so we don't build it?
  • What disqualifies a restaurant, so we filter before you spend calls on it?
  • How many records a week does the team actually want?