Skip to content

Restaurant leads in Derby

Collect restaurants in Derby from public sources, turn them into records you own and start conversations that lead somewhere.

  • Public sources for restaurants in Derby
  • Missing emails derived from websites
  • No credits, no rented data
Database in Riftjaw with active contacts, segment, lead file and source

Reaching restaurants in Derby

Restaurants run on thin margins and long hours, and the owner or general manager decides on suppliers, software and marketing. Groups have a head office buyer, but independents choose on price, reliability and how little extra work a change brings.

Start with Derby itself and keep Nottingham, Leicester and Stoke-on-Trent as separate segments. That way a campaign never reaches the same restaurant twice, and you can see at a glance how much of Derbyshire is done.

Your competitors are already emailing restaurants in Derby. With your own list you reach them in a planned way instead of hoping they find you.

Build your Derby list of restaurants in four steps

Every import waits as a concept until you publish it, so nothing lands in your database by accident.

Collect restaurants in Derby

Export restaurants in Derby from Google Maps listings or restaurant review sites as CSV, or paste the results page into paste and collect.

List of imports and scrapes in Riftjaw
Imports and scrapes in Riftjaw, each with its source, lead file, date and number of rows.

Import into one lead file

Drop the file into a lead file called Restaurants Derby. Columns are matched for you and duplicates are flagged before anything is saved.

Import in Riftjaw: every column matched to a profile field, with all rows previewed
Columns from a maps export matched to profile fields such as company, phone, website and city.

Fill in the missing emails

No email in the export? Tick info@, bookings@, reservations@ and manager@ and addresses are derived from each website.

Contact panel in Riftjaw with pipeline status, tags, details and campaign history
One record per company: New, Contacted, Replied or Customer, with tags and every campaign it got.

Reach them in small batches

Pick the segment, keep only status New, write one mail with placeholders like {company|your team} and send it in small batches.

Segments in Riftjaw, each with its own name and number of contacts
Segments in Riftjaw, each with its own name and number of contacts.

Fields worth recording for restaurants in Derby

Add these as fields in your lead file. Any column in your import can become a field.

FieldWhy it helps
Company nameThe key field. Duplicates are checked on it or on the website.
WebsiteNeeded to derive an email when the export has none.
CuisineThe type of food shapes which products and suppliers are relevant.
CoversSeating capacity hints at volume and budget.
Independent or groupGroups buy centrally, so you need a different contact and approach.
DeliveryRestaurants that deliver need packaging and ordering tools.
Opening hoursKnowing when they open helps you pick a time to call or visit.

What slows down prospecting restaurants, and the fix

Restaurant lists change fast as places open, close and change owners.

Each record keeps its source and date, and you can archive closed places so your active list stays current.

The bookings@ address reaches a host, not the owner.

Tick several prefixes in email from domain, such as info@ and manager@, and note on the contact who replied.

You cannot tell which restaurants you already visited in person.

Set the status to Contacted and add a note after each visit, so the whole team sees it.

Openings that work with restaurants

Use one angle per campaign, so the results show which one gets restaurants to click.

  • Show how your offer protects margin, because food and labour costs are always on their mind.
  • Mention something specific from their menu so the owner knows you looked.
  • Offer a simple switch with no disruption to service, as that is what owners fear most.
Campaign editor in Riftjaw: pick a segment, write the mail and set the button
The campaign editor in Riftjaw: pick a segment, write the mail and check the preview.

Emailing restaurants in the UK

In the UK, B2B cold email is covered by the Privacy and Electronic Communications Regulations (PECR) and UK GDPR. PECR generally allows marketing email to corporate subscribers such as limited companies without prior consent, but sole traders and some partnerships are treated like individuals and usually need consent, and every message must identify you and offer a simple way to opt out. Under UK GDPR you also need a lawful basis, often legitimate interests, to use the details of named contacts. This is general information, not legal advice.

Mid afternoon between lunch and dinner service, early in the week, is usually the calmest time, while Friday and Saturday evenings are best avoided. Read the deliverability guide before your first send.

Questions people ask

Yes. The Free plan runs the whole pipeline on one list with small campaigns, and you do not need a credit card. Move to Pro when you want more lists, segments and bigger campaigns.

Yes. Put Derby in its own segment, or keep a City field and save a filter such as city contains Derby. You always see which part of the market you already worked.

If your file has an email column, that wins. If it only has websites, tick the prefixes you want, such as info@, bookings@, reservations@ and manager@, and Riftjaw derives addresses from each domain. Derived addresses are good guesses, not verified, so start with small batches.

Collect restaurants from public listings such as Google Maps or review sites with a scraper, then import the CSV or Excel file. Riftjaw flags duplicates and lets you add a field for cuisine or area.

Many teams do both. Riftjaw keeps phone numbers as fields and email history per contact, so you can tag who to call and send a short campaign to the rest.

Start your Derby list today

Create your account, import your first file of restaurants and see them as records you can work in a few minutes.

No credit card · cancel any time · your data stays yours