Team works in separate lists when you sell to restaurants
Does your colleague know you already called that company? Here is how people who sell to restaurants fix it.
Does your colleague know you already called that company?
Each person on the team keeps a private list or sheet. Nobody sees the full picture of who was contacted and what they said.
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.
Two people approach the same company and prospects notice. Knowledge walks out the door when someone leaves.
One shared database, unlimited users.
Riftjaw gives the team one shared lead database with unlimited users on an account. Everyone sees the same statuses, notes and mail history. The activities feed shows what happened recently.
- 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
The fix, step by step
- Bring the lists together. Import each team member's list into the shared database.
- Invite the team. Add colleagues to the account at no extra cost per user.
- Work from one status. Update statuses and notes so everyone sees the latest step.
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
Add these as fields in your lead file. Any column in your import can become a field.
| 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