Everything ready.Run the whole event from one record — sales to the last plate.
The menu the client approves becomes the prep list, the kitchen sheet, the assignment sheet and the invoice line. No retyping, no missed allergen, no guessing margins until month-end.
Private beta · a few founding teams at a time · your workflow shapes the roadmap
The approved menu writes the prep list, the kitchen sheet and the proposal line by itself. Change the count once; every sheet follows.
A guest's nut allergy is entered once and prints beside the dish, on the prep item, the kitchen sheet and the captain's table list.
Ingredient prices cascade through sub-recipes to a live plate cost on every dish — margins known at the quote, not at month-end.
Ninety seconds, one event.
Follow one gala from the first call to the last plate. Click a step, or let it run.
Nobody re-enters the inquiry: the lead converts to a client and an event in one step, and every stage after is enforced.
Want this on your next event? Request access →- 1Drag a card to the next stage; an out-of-sequence move is blocked, not lost.
- 2Handed off = operations already has everything.
Retyping the same event into four documents.
Lead, tasting, proposal, follow-ups and the client's history live on the event. The proposal pulls the menu, staffing and equipment; prices lock the moment you send it.
Request early accessDoing arithmetic at 6 a.m.
The approved menu becomes the prep list and the kitchen sheet by itself — 207 salmon and 45 risottos from the event, allergens on every line, plate cost on every dish.
Request early accessBuilding the binder the night before.
Event pack, assignment sheet, culinary and room set-up are generated from the event and printed the way supervisors already read them. Change the count on Friday; Saturday's sheets are already right.
Request early accessWhat it replaces.
Most teams run on a spreadsheet, a group text and a Word binder. Here is where each one goes.
| Today | What breaks | In Apuntio |
|---|---|---|
| Pipeline spreadsheet | Stages skipped, deposits missed, nobody knows what's confirmed. | Ten enforced stages; deposits, tastings and handoff on the event. |
| Quotes in Word | Prices retyped from the menu; the version the client signed is anyone's guess. | Proposals pulled from the event, price-locked on send, revisioned. |
| Prep on paper | Counts recomputed by hand; the allergy lives in someone's memory. | Prep list and kitchen sheet generated from the menu; allergens on every line. |
| Staffing by text | Who confirmed? Which agency seat is which? Hours reconciled from photos. | Published shifts, agency seats, punch in and out, hours on the event. |
| The night-before binder | Rebuilt for every change; the floor runs on an out-of-date copy. | Pack, sheets and set-ups regenerated from the event in seconds. |
| Month-end P&L | Margins known six weeks after the event. | Food cost at the quote; event P&L from live totals. |
Shaped inside a working catering operation, not a boardroom.
Every screen was drawn from a real pack, a real tasting, a real prep list and a real night on the floor. We ran the events, then built the system we wished we had.
Founding teams work with us directly during the beta. Your sheets shape the roadmap.
Start with the core, add the rooms you run.
Founding teams set pricing with us during the beta. Every plan includes every seat on the floor.
Pipeline, leads, clients, tastings, proposals, payment plans, tasks, event pack.
Included with every planMenu catalog, recipe costing, prep lists, the Kitchen Builder and day-of ready ticks.
Beta pricingService and Assignment Builders, set-up sheets, staffing, time clock, equipment, logistics.
Beta pricingInvoices from the payment plan, payments, expenses, event P&L and reports.
Beta pricingBefore you ask.
- Who is it for?
- Caterers and event producers running from a few to a few dozen events a month with a kitchen, a floor team and a sales desk. If one person wears all three hats, it still fits — the sheets just have one name on them.
- We run on spreadsheets. How do we move?
- Start with next month's events. Founding teams get their menu catalog, clients and staff loaded with us; past events stay where they are.
- Does it work on the floor?
- The web app runs on any iPad or phone today — the Kitchen Builder's Day-of mode and the staff time clock are built for them. Native iOS apps are in development.
- Who owns the data?
- You do. Every list exports to CSV; your organization is isolated at the database level; deleted records are audited and recoverable.
- What does “private beta” mean?
- The product is live and runs real events. We onboard a few teams at a time so each one gets us directly — and so what you need next is what we build next.
Put your name on the sheet.
Tell us about your operation. We reach out when a founding slot opens.