We built a catering email outbound system for a 30-year Lebanese restaurant. Here's what worked.
Greater Boston is full of corporate offices, law firms, and event planners who order catering every month. They don't know your restaurant exists. Here's the outbound system we built for Byblos to fix that.
Byblos Restaurant in Norwood has been serving Lebanese fine dining since 1996. Live music every Friday and Saturday. Mezze that people drive 45 minutes for. And a catering side that was running entirely on word of mouth.
We built them a Boston-area catering outbound program. Here's the system.
The list, where most outbound dies
Outbound is 70% list quality and 30% everything else. We segmented the Greater Boston market into five buyer pools: corporate offices, law firms, hospitals, universities, and event planners. Each pool got its own dataset built from a combination of LinkedIn, ZoomInfo, and public records (Massachusetts is unusually generous with business registry data).
- Corporate offices got CTOs, ops managers, and office managers at companies 50 to 500 headcount inside a 20-mile radius.
- Law firms got managing partners and office administrators at 5 to 100 attorney firms.
- Hospitals and universities got event coordinators and food service directors.
- Event planners got the actual planners, named, not the firm.
The sequences, one per segment
We didn't run one email blast. We ran five, because corporate lunch drops read different than wedding rehearsals.
- Corporate lunch sequence: Lead with 'authentic Lebanese for your monthly team lunch,' price per head, lead time. Three emails over ten days.
- Law firm sequence: Lead with 'we cater client closings and partner retreats,' confidentiality, dietary restrictions handled. Four emails over two weeks.
- Event planner sequence: Lead with 'add live music and Levantine mezze to your client's wedding.' Different angle, longer cycle.
- Every sequence ends with a soft ask, a single meeting slot, or a 'reply with your venue and date.'
The deliverability work nobody sees
We set up a dedicated sending domain (not the restaurant's main one), warmed it for two weeks, and configured SPF, DKIM, and DMARC properly. We never sent more than 50 cold emails per day per inbox. Greater Boston law firms in particular are aggressive about marking unfamiliar senders as spam, and an unwarmed domain dies in the first week.
The handoff to the kitchen
The hardest part of running outbound for a restaurant isn't getting the reply. It's making sure the inbound interest doesn't blindside the host stand. We routed replies into a dedicated catering inbox, with a daily summary email to the owner so nothing got lost between dinner service and the next morning.
Full case study with the architecture and the categories of replies we saw on the Byblos work page. If you run an SMB restaurant or food service business in Greater Boston and you want to talk through what an outbound program would look like for you, book a free growth audit.
Frequently asked questions
- How big does my restaurant need to be to run B2B catering outbound?
- Big enough to handle a 30 to 50 person order without disrupting dinner service. That's the realistic minimum. Smaller than that and the outbound generates pipeline you can't fulfill, which damages the brand and the relationships.
- How many emails per day is safe for cold outbound?
- From a single inbox on a warmed domain, 30 to 50 per day. From multiple inboxes (which is the standard professional setup), you can scale to several hundred per day across the program. Faster than that and Greater Boston email filters will catch you inside two weeks.
- Do I need a dedicated sales hire to run B2B catering outbound?
- No, but you need somebody to handle the replies. Most of our restaurant clients route inbounds to an existing manager and grow into a dedicated role only when reply volume is above 15 per week.
