A neighbourhood restaurant fills slow weeknights from its own guest list
A neighbourhood restaurant fills slow weeknights from its own guest list
Modelled on a 70-cover restaurant with 2,400 opted-in guest emails and a $46 average cover, running two thin nights a week.
The starting situation
Marketing means posting a photo when someone remembers, and paid reach on social is a rounding error. Tuesday and Wednesday run at half capacity while the guest list — people who already liked the food enough to hand over an email — hears from the restaurant maybe twice a year.
What was installed
- AI Content Engine producing a weekly specials email and matching social copy in the house voice
- Birthday and anniversary club sending automatically, targeted at the slow nights
- 60-day win-back sequence for guests who stopped visiting
- Review request triggered on table turn rather than asked verbally
Before and after
| Measure | Before | After |
|---|---|---|
| Guest emails on file | 2,400 (unused) | 2,400 (worked weekly) |
| Marketing sends / month | 0–1 | 4 + automations |
| Content production time | 2–3 hrs / week | ~20 min / week |
| Incremental covers on slow nights | — | ~70 / month |
| Average cover | $46 | $46 |
The arithmetic
- 2,400 contacts × a 2.9% redemption across the month = about 70 incremental covers.
- 70 × $46 = roughly $3,220 of added revenue on nights that were already staffed.
- Because the labour and rent are fixed on those nights, most of that lands as margin.
The $79 system is covered by two extra tables.
Verdict: The cheapest guests to bring back are the ones who already came. A content engine is what makes contacting them weekly survivable.
What to install to reproduce this
This build runs on AI Content Engine, bundled inside the Restaurants package.
- · AI Content Engine producing a weekly specials email and matching social copy in the house voice
- · Birthday and anniversary club sending automatically, targeted at the slow nights
- · 60-day win-back sequence for guests who stopped visiting
- · Review request triggered on table turn rather than asked verbally
Related pages
More build math
Key terms on this page
- Lead attribution
Lead attribution is the practice of recording where each lead came from — channel, campaign, page, and referrer — so revenue can be traced back to the spend that produced it.
- Conversion rate
Conversion rate is the percentage of people at one stage of your funnel who move to the next — visitors to enquiries, enquiries to bookings, bookings to paying customers.
- Missed-call text-back
Missed-call text-back is an automation that detects an unanswered inbound call and immediately sends the caller a text apologising, naming your business, and offering to book or answer questions.
- Review velocity
Review velocity is how many new public reviews your business earns per month, and how consistently that rate holds over time.
- AI voice agent
An AI voice agent is a system that answers inbound phone calls with a natural-sounding voice, qualifies the caller, answers common questions, and books into your calendar or escalates to a human.
- Webhook
A webhook is a message one application sends to another the moment an event happens, so the receiving system can act immediately instead of checking periodically.
How the numbers on this page are measured
Every metric quoted for this modelled build has a stated definition, a formula, and an assumption you can test against your own books. Last reviewed 2026-08-05.
| Metric | Definition | How it's calculated | Assumption |
|---|---|---|---|
| Cost per booked job | All-in monthly cost of the system divided by the jobs it books. | (system_cost + tool_subscriptions) ÷ booked_jobs_attributable_to_the_system. | Only jobs where the system made first contact are attributed; jobs from referral or repeat customers are excluded. |
Sources
- The Short Life of Online Sales LeadsHarvard Business Review, 2011Response time is the dominant variable in inbound lead conversion; contact odds fall sharply after the first hour.
- Lead Response Management studyMIT / InsideSales, 2007Contacting a web lead within five minutes materially increases qualification rates versus contacting after 30 minutes.
- Local Consumer Review SurveyBrightLocal, 2024Most consumers read reviews before choosing a local service business, and review recency affects trust.
- Local Search Ranking FactorsWhitespark, 2023Review quantity, recency, and response behaviour are recognised local-pack ranking signals.
- Small business phone and messaging behaviour researchGoogle / Ipsos small business studies, 2019Calls are a primary conversion path for local service searches, so unanswered calls are lost revenue rather than deferred revenue.
- Business texting engagement benchmarksTwilio Messaging research, 2023SMS is opened and replied to faster than email for time-sensitive service conversations.
What this is — and isn't
Figures on this page are modelled, not audited client results. Inputs (call volume, ticket size, close rate) are stated next to every number so you can substitute your own. We do not publish named-client outcomes, aggregate ratings, or testimonials we cannot evidence.
Full modelling rules, attribution rules, and the correction policy are on our methodology page.
Guarantees and supported integrations
- 14-day refundInstall it, run it, and if it doesn't fit, get your money back.
- Lifetime updatesEvery revision of a system you own ships to you, free.
- No lock-inBlueprints run on your own accounts. Cancel and they keep working.
- Secure checkoutPayments handled by the processor. We never store card details.
Works with the stack you already pay for
- Zapier
- Make
- HubSpot
- GoHighLevel
- Pipedrive
- Twilio
- Cal.com
- Calendly
- Google Workspace
- Notion
- Airtable
- OpenPhone
Integration partners, not customer logos. We publish client names only with permission — none yet, so none shown.
Plug the same leak in your shop.
Start with the single system that recovers the most revenue, then add the rest of the bundle.