No email addresses when you sell to restaurants
Does half of your list have a website but no email address? Here is how people who sell to restaurants fix it.
Does half of your list have a website but no email address?
Directories and scraper exports often give you a company name, a phone number and a website, but no email. Finding an address for each company by hand takes ages.
It hits harder when you sell to restaurants. 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.
Companies without an email address never get your message. Your list looks big but only part of it is usable for outreach.
Role addresses from a website, without credits.
Email from domain takes the website, strips www. and keeps the domain. You tick the prefixes you want, such as info@, hello@ or sales@, and add your own. An existing email column always wins, and derived addresses are clearly guesses based on common patterns.
- Fields that fit restaurants, such as cuisine
- Email prefixes that fit, like info@, bookings@, reservations@ and manager@
- Status, tags and a segment on every record
How to fix it in Riftjaw
- Map the website column. During import, tell Riftjaw which column holds the website.
- Tick your prefixes. Choose info@, hello@, office@ or add a prefix of your own.
- Check and send carefully. Treat derived addresses as guesses and send a small test batch first.
Other walls when prospecting restaurants
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.
Fields worth recording for restaurants
Record these and you can split the list later, write sharper mails and see who fits your offer.
| Field | Why it helps |
|---|---|
| Company name | The key field. Duplicates are checked on it or on the website. |
| Website | Needed to derive an email when the export has none. |
| Cuisine | The type of food shapes which products and suppliers are relevant. |
| Covers | Seating capacity hints at volume and budget. |
| Independent or group | Groups buy centrally, so you need a different contact and approach. |
| Delivery | Restaurants that deliver need packaging and ordering tools. |
| Opening hours | Knowing when they open helps you pick a time to call or visit. |
Questions people ask
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.
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.
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.
Build a database you own
Create your account, import your first list and see it turn into records you can work.
No credit card · cancel any time · your data stays yours