A kanban pipeline with first-response tracking — speed wins bookings.
Inquiry to signed, deposited, profitable booking.
Everything an independent private-events program needs — nothing an enterprise venue platform bolts on.
Compare the price
AI drafts the proposal and the BEO. You send them.
From the event record and your catalog, AI drafts the proposal cover in your venue's voice, the line items, and a full BEO — setup, service, kitchen, beverage notes, and the run-of-show timeline. You review, edit, and send. Nothing goes to a client without you.
- Drafted in your voice, from your menu.
- Margin preview before you send — the client never sees it.
- Human reviews and sends — always.
Proposals — versions, engagement, and AI drafting (operator dashboard).
Your client books on their phone. No app, no account.
One link. The client reads the proposal, picks their options, accepts, signs the agreement, and pays the deposit — with the math shown at every step. Then their event page holds the details, timeline, documents, messages, and balance until the night.
- Tokened link — no login, ever.
- Your brand on every client surface.
- A code by email before money or signature.
The chat tab reaching any client on the book, not only tonight’s (captain app).
The whole event in your captain's pocket.
The published BEO, the live run-of-show, the kitchen fire board with dietary counts, the setup checklist with photo proof, the live headcount, and a one-tap close-out that captures the final count and kicks off the invoice.
- Fire cues checked off in real time.
- Dietary counts the line can read.
- A work queue across every event, not one night at a time.
- The staffing handoff — who is captaining, who is on, what they were told.
- Photos of the room as it was set, kept on the event beside the BEO.
- Close-out flows straight into the invoice and P&L.
Kitchen Fire Board — fire cues and dietary counts (captain app).
The staffing handoff — who is captaining, who is on, and their call times, with one tap to create the shifts in SavorCrew. Beside it, the calendar: the week rather than the night (captain app, v1.0.17).
See the profit, not just the revenue.
Every event carries its contribution margin: booked revenue minus the food cost on your catalog minus the labor you planned against the event. Cost the catalog by hand or link an item to its Heard Recipes plate and let the plate keep it current. At proposal time as a preview; after the night as actuals.
- Margin preview at proposal time.
- Food from recipes, labor from real shifts.
- Feeds SavorVitals prime cost.
Profitability — per-event contribution margin with the equation shown (operator dashboard).
The inquiry gets answered before your competitor's phone rings.
Your website form feeds the pipeline directly — no re-typing. The inquiry gets an instant reply, and AI drafts the personal follow-up in your venue's voice for you to review and send. If nobody responds in time, the escalation ladder taps the coordinator, then the manager — a stalled lead never dies quietly. Behind it: the full lifecycle email library — confirmations, reminders, BEO to the chef, thank-yous, the weekly summary — each template on its own per-venue switch, every send in an immutable sent log. And bookings too small for a contract live in the reservations inbox: confirm, hand the chef a headcount, and promote to a full event the day it grows.
- AI drafts the first reply in minutes. A human always sends.
- Two-stage escalation — the SLA clock has teeth.
- A reservations inbox for the twelve-top that isn't a wedding.
Reservations inbox — confirm, transfer, promote (operator dashboard).
Signed, and provable a year later.
The contract goes out from the template stack — your venue default, or the override you keep for weddings — and comes back signed from the client's phone. What it leaves behind is the part that matters when somebody disputes a cancellation in eleven months: an immutable record of who signed, from where, and at what moment, with the exact document they saw. You cannot edit it afterwards, and neither can anyone else.
- A signature queue — what is out, what is back, what is overdue.
- Per-event-type templates over a venue default. Set once.
- An immutable trail: timestamp and IP against the exact document signed.
The count closes. The invoice already knows.
Deposits and installments sit on a schedule with due and overdue rows, and every movement lands in a ledger that only ever appends — a payment is never quietly edited. At the end of the night the captain closes out with the final count, and the invoice reconciles itself the way the contract says it must: it bills the greater of the guaranteed number and what actually walked in. Nobody re-types a headcount into an invoice at midnight.
- Deposit, installments and balance on one schedule, with reminder state.
- An append-only ledger — history you can hand an accountant.
- Final count at close-out, and the invoice bills the greater of guaranteed versus actual.
- Per-event P&L underneath it: revenue, minus food from the recipe snapshot, minus labor from SavorCrew.
Close-out — the final count, the notes, and the number the invoice will use (captain app).
And the rest of the pipeline.
First and second date holds with auto-expiry — no double-booking.
Spaces, packages, and menus with recipe-linked cost.
The book of business: every client with their lifetime events and lifetime value, and a merge that archives rather than deletes.
A work queue across every event — everything waiting on somebody, in one list.
The guarantee countdown — the one date the kitchen is planned against, on the event and on the calendar.
Pipeline value, win rate, revenue by event type — and covers + revenue year over year, CSV export included.
What it isn't.
SavorBanquet is private events and catering for independent restaurants and small groups. Not convention-center software, not a 3D diagramming suite, not a florist ERP, not a staffing platform. That's how it stays $9.99.