57 emails · 97 phones
across 71 qualified businesses
Without AutoLeads
5 h 55 of qualifying and writing, €178 in labor
estimated at 5 min per lead, at €30/h
With AutoLeads
0 min of typing: contacts qualified and sequences already written
This sample pulls French companies registered under restaurant NAF codes, then keeps venues where cooking drives the business model, not just the menu label. You get direct contacts and custom enrichment (capacity, service pattern, decision-maker role) that a general hospitality directory never segments.
One lead, up close · picked among 71 businesses
About 80% of revenue from food service; fully equipped professional kitchen on site.
Pitch gas and power against service hours, not footfall alone.
A manual search
2 generic addresses, the front desk on the line.
AutoLeads
People's names are hidden to protect their privacy.
B2B energy broker targeting restaurants and venues with heavy gas and electricity use.
What the audit and enrichment found, in concrete terms.
3 contacts · 0 audit findings
Written from those gaps: each highlighted passage reuses a point from the profile.
Hook on single-site scale (460 m², 218 seats) and dominant kitchen revenue share
3 emails in the sequence
Ask reception for the gérante by title, not « the manager »; associations often route calls to the board.
5 points in the script
Email, LinkedIn and calls run on their own, day after day.
6touches
3channels
25days
Traditional restaurant (56.10A) and fast-service (56.10C) codes both cover businesses where cuisson dominates operations, yet the sales motion diverges. Large single-site lunch rooms live on predictable midday gas peaks; all-day café-clubs stack morning coffee, lunch, and evening tapas on one meter; beachfront brasseries sell visible wok-and-fryer theatre; mall showrooms tagged with a restaurant code are really long-hour retail floors with demo kitchens.
A newcomer filtering « restaurants in France » without enrichment treats Schmidt-style showrooms like Castets Maroli rooms and wastes sequences. Prospection on a local niche explains why broad NAICS-style lists miss these splits; keyword times geography audits help you decide which sub-profile you sell to before you import anything into a CRM.
Many targets list 0 employees in Pappers while service runs daily. Calls hit a host stand, an association switchboard, or a mobile number buried on a PDF menu. Named legal roles (gérante, SAS president, lease-management owner) are the bridge when HR directories are empty.
Scraping only the homepage email yields info@ or a booking widget with no signer. Sellers who need the person who renews gas contracts ask reception for the role title from the registry, not « director » by default. Google Maps scraping limits matter if you supplement with map pins; HubSpot imports punish duplicate generic inboxes if you merge registry and web sources carelessly.
Here enrichment is not generic firmographics: it flags service hours, cover counts, kitchen share of revenue, and single- versus multi-site reality drawn from public positioning. Knowing « open from 9 a.m. with cooking all day » shifts an energy or maintenance opener from « save 20% » to load profiling by hour block.
Knowing « 80% of revenue from food service » tells a equipment seller to lead with line capacity, not Maroli room refurb. A seller without those fields sends the same paragraph to a 400 m² showroom and a 460 m² lunch room. Forty local cold-email runs show how specificity moves reply rates; template openers still fail if the fact behind them is wrong for the sub-type.
Owners ignore « digital transformation » and reply to concrete operational hooks: lunch cover band, terrace season, fryer and ventilation load, contract renewal timing before winter heating. Associations respond when you respect treasurer or board process; SASU founders respond when you acknowledge they still run service themselves.
Do not open with registry incorporation date unless it signals a fresh setup (2025 files). Do lead with geography they claim on the site (Castets, Bordeaux cantine, beach boulevard) so the message reads observed, not blasted. Cold-email deliverability still applies: restaurant domains are often on low-volume Google Workspace inboxes that spike when you batch generic hospitality copy.
Matching on kitchen-heavy public wording pulls edge cases: a kitchen brand showroom can carry a restaurant NAF while selling fitted kitchens, not table service. Registry workforce lags season hires, so « at least one employee » on a new brasserie is a hint, not a full org chart.
Treat NAF as a door, enrichment as the qualification layer, and expect to drop a fraction of rows after a thirty-second site check. Registry coverage gaps discuss what legal data alone cannot tell you; honest trimming beats defending a list that mixes demo halls with dinner service.
Nationwide restaurant prospecting in France looks homogeneous until you split legal form, service rhythm, and who actually signs utilities. Associations running large lunch services, SASU café-bars open from morning, lease-managed brasseries, and Maro showroom-style addresses that share a restaurant code all land in the same NAF bucket. Sellers pitching equipment, maintenance, POS, or energy need that split before the first email: a 218-seat midday kitchen and a 40-cover wine bar do not buy on the same trigger. Registry headcount often reads zero while the floor is busy, so named roles (gérante, president, fund owner) matter more than employee counts on the card.
