BookFast — inquiry responder for independent caterers

1. One-liner

Texts every event inquiry back in 60 seconds, qualifies the lead, and books the caterer who’s still in the kitchen.

2. Trend signal — why now?

Three things collided in the last twelve months.

First, the demand side is loud and on the record. On WeddingWire and WeddingBee, brides describe “messaging and calling about 15 caterers, only three getting back to them,” and complain that caterers are “consistently the least responsive vendors” because “food people generally aren’t great at administrative tasks, organization, and email.” That’s not a caterer whining about software — that’s the paying customer telling you the booking went to whoever answered.

Second, the math is brutal and well-documented. The MIT lead-response study (the one everybody quotes) puts the first responder winning ~78% of the time; HBR’s data says responding within 5 minutes makes you 100× more likely to even reach the lead than waiting 30 minutes. Manual catering proposals average 2.1 hours from inquiry to quote (US Tech Automations 2026 benchmark). A solo caterer is on-site plating a wedding when the next $4,000 inquiry lands — and by the time they wipe their hands, three competitors already replied.

Third, the tech to fix it got cheap and good this year. Low-latency voice/SMS agents (ElevenLabs, Vapi, Cartesia) and reliable structured extraction are now off-the-shelf — the same stack Product Hunt’s “AI voice agents 2026” category is built on. A 60-second, on-brand, qualifying auto-reply was a research project in 2023. In 2026 it’s an API call.

Provenance:

• Signal 1 (demand): Brides report contacting ~15 caterers, only 3 reply; “caterers are the least responsive vendors” — https://www.weddingwire.com/wedding-forums/caterers-not-responding/d6ddf714e8eb25ca.html — observed 2026-06-08
• Signal 2 (feasibility): Low-latency AI voice/SMS agents (ElevenLabs, Vapi, Cartesia) now production-grade and cheap — https://www.producthunt.com/categories/ai-voice-agents — observed 2026-06-08
• Signal 3 (economic): First responder wins ~78% of bookings (MIT); manual catering proposal = 2.1 hrs; incumbents Tripleseat/Curate/Perfect Venue funded and competing — https://www.cendyn.com/blog/why-first-responders-get-70-of-the-business/ , https://ustechautomations.com/resources/blog/restaurant-catering-automation-platform-comparison-2026 — observed 2026-06-08 Category: Tech-unlock

3. The opportunity

The catering software market is full of proposal databases — Tripleseat, Curate ($125–208/mo), Perfect Venue ($119–199/mo), Planning Pod, CaterZen. They are all CRMs: a place to store an inquiry and build a proposal once you sit down at a laptop. None of them solves the actual failure point, which happens before the caterer ever opens the laptop: the 2-hour (or 2-day) silence between “customer hits send” and “caterer replies.”

That silence is where the booking dies. The incumbent’s product literally cannot help, because it’s passive — it waits for the caterer. BookFast is active. It answers for the caterer, instantly, on the channel the customer used (web form, Instagram DM, missed call → SMS), asks the 4–5 qualifying questions a good caterer would ask (date, headcount, venue, budget band, service style), drops the tire-kickers, and hands the caterer a warm, structured, ready-to-quote lead — or books a tasting slot outright.

The incumbents can bolt this on, but it’s not their wedge and it’s not their wallet (they sell up-market to venues and groups). The opening is the long tail of solo and 2–5 person caterers who find Tripleseat “too complex and pricey” and currently use Gmail + a spreadsheet. That’s who’s bleeding bookings, and that’s who nobody is serving with a responder instead of a database.

4. Target market

• Primary customer: Independent caterers and small event-food operators in the US — solo to ~5 staff, $150K–$1.5M annual revenue, doing weddings, corporate lunches, private parties. The owner is also the chef, the salesperson, and the dishwasher. Also fits: food trucks that cater, private chefs, small BBQ/taco/pizza-cart operators.
• Why they buy (their words): “I lose jobs because I’m cooking when the email comes in and by the time I reply they’ve booked someone else.” “Half my inquiries are tire-kickers asking my price for a date I’m already booked.” They feel this every week in season.
• Rough TAM reasoning: The US has ~73,000 catering establishments (Census/IBISWorld range), and that undercounts solo/private-chef/food-truck operators who also cater. Even a serviceable slice of 150,000+ small operators at $100–250/mo is a comfortably-past-$5M business. Don’t need the whole market — need a few thousand.
• Why now for them: Post-2023 event demand rebounded hard; inquiry volume is up but so is competition, and labor is short, so the owner has less admin time than ever. They’ve also now personally used AI assistants and no longer find “an AI texts my leads back” spooky — they find it obvious.

5. Product sketch (MVP)

• Drop-in web-form + “text us” widget for the caterer’s site, plus a dedicated booking number that catches missed calls and replies by SMS.
• 60-second AI auto-reply on every inbound inquiry, on-brand (caterer’s name, voice, signature dishes), 24/7 — including 11pm and mid-event.
• Conversational qualifier: collects date, headcount, venue, service style, and budget band; checks the caterer’s calendar for date conflicts before promising anything.
• Tire-kicker filter: flags vague/no-budget/already-booked-date leads as cold so the owner ignores them guilt-free.
• Warm-lead handoff: pushes a clean, structured lead card (or a booked tasting/call slot) to the caterer by SMS + a simple inbox.
• Smart follow-up cadence: auto-nudges unresponsive-but-qualified leads over SMS/email (the data says ~40% of catering bookings close after the 4th touch).
• Lightweight quote starter: pre-fills a templated price range from the caterer’s own menu/per-head numbers so the human just confirms and sends.

6. AI angle — what’s load-bearing

Remove the AI and this is a Calendly form — useless, because the whole value is a human-quality conversation happening in 60 seconds while the owner’s hands are full. The AI does the work a good catering salesperson does: reads a messy free-text inquiry (“hey do you do taco bars for like 60 ppl in August?”), extracts structured fields, asks the right next question, sounds like the brand not a robot, knows when a lead is junk, and writes a reply the owner would be happy to have sent. That’s reasoning + extraction + tone-matching + judgment — squarely load-bearing, not a chatbot sticker on a CRM.

7. Localization angle (if any)

N/A — this is a US-first play. The wedge (English-language event inquiries, US wedding/corporate-catering norms, SMS as the dominant channel) is specific to the US market and that’s where the willingness-to-pay and incumbent pricing ($119–208/mo) are already proven. A later SEA/India cut would need WhatsApp-first plumbing and very different price points; not the launch move.

8. Business model — path to $1M–$5M ARR

• Pricing: $99/mo solo tier (one location, one number, ~150 inquiries/mo) → $199/mo pro tier (multi-staff, integrations, advanced follow-up). Usage overage on heavy inquiry months.
• ACV: ~$1,600/yr blended.
• Rough math to $1M ARR: ~625 caterers × ~$133/mo avg × 12. Against a 150K+ operator base, that’s <0.5% penetration. Believable.
• Rough math to $5M ARR: ~2,600 paying caterers, plus tier mix shifting toward $199 as operators grow and add a deposit-collection / payments take-rate. Needs a working content+partner engine (section 9), not a miracle.
• Expansion path: ACV grows via (a) tier upgrade as they add staff, (b) payments/deposit-collection take-rate on booked events, (c) per-location pricing for the ones who open a second kitchen. The booking flow is the natural on-ramp to “we also process the deposit.”

9. Go-to-market wedge — first 100 customers

• Scrape the unresponsive vendors and prove it to them. Pull caterer listings from WeddingWire, The Knot, and Google Maps in 10 metros, send each a test inquiry, time the response. Most won’t reply for hours/days. Cold email/DM them their own response time + “your competitor 2 miles away replied in 9 minutes — want us to answer for you?” High open, visceral hook, ~100s of named targets per metro.
• Wedding-planner referral loop. Planners HATE chasing unresponsive caterers. Sign 20 planners as referrers (they recommend BookFast caterers because those caterers actually answer); planners are a concentrated, reachable channel on Instagram and local Facebook groups.
• Niche communities. r/Catering, r/PersonalChef, food-truck and catering Facebook groups, and the ICA/local caterer associations. Lead with the “first responder wins 78%” stat and a free response-time audit, not a sales pitch.
• Free response-time audit as the front door. A one-click tool that texts a test inquiry to any caterer and grades them. It’s shareable, it’s a lead magnet, and it converts the exact pain into a number the owner can’t unsee.

10. Build complexity — justification

Low. Everything is off-the-shelf: SMS (Twilio), a voice/text agent layer (Vapi/ElevenLabs), an LLM for extraction + tone, a calendar check, and a thin inbox UI. No custom models, no novel infra, no hardware. The only real engineering discipline is conversation quality (not sounding like a bot, not over-promising on dates) and reliable handoff — solvable with prompt design + a few guardrails. A technical founder ships a credible v1 in 6–8 weeks; a polished multi-channel version in 3–4 months.

11. Gating checklist

Gate	Pass?	Note
Legal in target market	✅	SMS auto-reply to inbound inquiries is consent-by-initiation; honor opt-out (TCPA-compliant).
Ethical — no harm / dark patterns	✅	Disclose “this is an automated assistant”; no deception about the AI.
Market exists (evidence above)	✅	Funded incumbents + loud buyer-side complaints + paid alternatives.
1–5 person team can build this	✅	Off-the-shelf stack, Low complexity.
Launchable with <$50K / ₹40L	✅	API costs + a laptop; well under cap.

All five pass.

12. Feasibility score

Axis	Weight	Score	Notes
Problem intensity	20	16/20	Felt weekly in season, costs real money, buyers complain unprompted. Not quite hair-on-fire daily-compliance, but close.
Demand evidence	15	13/15	Buyer-side complaints, MIT/HBR response stats, multiple funded incumbents, benchmarked pricing. Skeptic nods.
Build feasibility	15	13/15	Off-the-shelf APIs, solo-buildable in 6–8 wks; conversation quality is the only real risk.
Distribution clarity	15	11/15	Named lists (WeddingWire/Knot/Maps), planner loop, niche communities, audit lead magnet. Conversion still to prove.
Revenue mechanics	15	11/15	Pricing benchmarked to incumbents; ACV reasonable; churn in a seasonal, low-tech-savvy SMB base is the open question.
Time to first revenue	10	8/10	The “we test-messaged you and you failed” pitch can close in days; short trial-to-paid.
Defensibility	10	3/10	Thin moat — incumbents or a clone can copy the responder. Race is execution + niche brand + workflow lock-in.
Total	100	75/100

13. Qualitative modifiers

Founder-fit tags

technical-heavy (conversation quality, integrations) · sales-heavy (cold outreach + planner relationships are the GTM engine).

Key assumptions to validate (3–5)

1. Assumption: Caterers will pay ~$99–199/mo for faster response, not just nod that it’s a problem. How to test: Run the response-time audit on 50 caterers, pitch 30, pre-sell 5 at a launch price.
2. Assumption: A 60-second AI reply books more than it scares off; customers don’t bounce on “this is an assistant.” How to test: A/B the auto-reply on 3 pilot caterers’ live inquiries; measure reply-back and book rate vs. their old baseline.
3. Assumption: Churn is survivable despite seasonality (caterers may pause in off-season). How to test: Watch the first 20 paid accounts through one slow month; offer a seasonal pause instead of cancel.
4. Assumption: Wedding planners will actually refer. How to test: Sign 5 planners, track referred signups over 60 days.

Risk flags

1. Platform dependency: Relies on Twilio/SMS deliverability and an LLM API; pricing or policy shifts hit margins. Mitigate by keeping the agent layer swappable.
2. Incumbent fast-follow: Tripleseat/Perfect Venue could ship “instant reply” as a feature. Counter with niche focus, brand, and the deposit/payments expansion they’re slower to localize for solo operators.
3. Trust/quality risk: One bad AI reply that over-promises a booked date burns the caterer’s reputation. Guardrails on calendar/availability are non-negotiable.
4. Seasonality churn: Off-season pauses can spike churn; seasonal pricing needed.

14. Structured verdict

Score:                  75/100
Verdict:                GO
Confidence:             Medium
Best-fit builder:       Technical founder who can also run cold outreach (or a 2-person tech+sales pair)
Time to revenue:        4–8 weeks (audit-to-pitch closes fast)
Capital to launch:      $5–10K (API credits, number provisioning, landing page)
Top 3 assumptions to validate first:
  1. Caterers pay $99–199/mo for speed — pre-sell 5 of 30 pitched.
  2. AI reply lifts book rate vs. baseline — A/B on 3 pilots.
  3. Off-season churn is manageable — track first 20 accounts through a slow month.
Kill criteria:
  - Abandon if <5 of 30 audited+pitched caterers pre-pay at launch price.
  - Abandon if pilot caterers see no measurable lift in book rate over their manual baseline after 4 weeks.
  - Abandon if a major incumbent ships an equivalent instant-responder at SMB pricing before your v1 lands.

15. Next step — 1-week validation sprint

• Day 1–2: Build the “response-time audit” — a script that texts a standard test inquiry to a caterer and grades the reply speed. Run it on 50 independent caterers across 3 metros (WeddingWire + Google Maps lists).
• Day 3–4: Cold email/DM the 50 their own grade + “want us to answer in 60 seconds for you?” Book calls with anyone who bites. Manually role-play the AI responder over SMS for 3 willing caterers’ real inquiries (concierge MVP — you behind the curtain).
• Day 5: Decide. Go if ≥5 caterers ask to pay and ≥1 manual-pilot inquiry converts to a booked tasting that the caterer credits to the fast reply. No-go if the audit shows caterers actually respond fast (no pain), or nobody will pay for the fix.

The falsifiable result: a signed pre-pay (or a refusal) from caterers who just watched themselves fail their own response-time test.