Panko private alpha

You can already see it. Now everyone else can too.

Everyone making an event happen plays a part in realizing the vision: the caterer, the venue, the client. Panko makes sure they’re all working toward the same one. One record of the event sits behind every view of it, so what one person changes is what everyone else sees.

Email us what you run See everyone’s view

Private alpha. A handful of teams, onboarded by the founders.

Tell us about your event Ainsley–Okafor rehearsal dinner
marrowandrye.com · inquiry event 0214 · Marrow & Rye
From the inquiry
Fri 12 Jun · 120 guests · Hollis Barn
Date Fri 12 Jun
Guests 120
Venue Hollis Barn · Lower Field
From Ainsley Okafor
Plated · 3 courses
3 courses · $9,740
Herb-roasted chicken68
Cedar-plank salmon28
Mushroom bourguignon vegan24
Per plate$81.17
Proposal · 120 plates$9,740
Contract
signed 04 Apr
Sent to AinsleyThu 2 Apr
signed 04 Apr
Kitchen sheet · BEO rev. 3
rev. 3 · 120 plates · 15 tables
Plates120
Allergenstree nuts · table 6
Tables · rounds of 815
Seated7:15 pm
Invoices
Deposit paid 06 Apr$4,870
Balance · due 29 May $4,870
QuickBooks Onlinesynced · matches the calendar

Now everyone else can see it too.

The caterer, the venue, and Ainsley each get their own view of the same record. We’re starting with these three; the coordinator, the DJ, and the photographer are next. Try it: change the guest count.

Every view of the same record. Change the guest count.

Guest count
120
every view follows, and so does the rest of the page 120 guests: 68 chicken, 28 salmon, 24 vegan; 15 tables, 120 chairs; deposit $4,870 paid, balance $4,870.
The catererMarrow & Rye · event 0214
Ainsley–Okafor rehearsal dinner Fri 12 Jun
Plated · 3 courses
Herb-roasted chicken68
Cedar-plank salmon28
Mushroom bourguignon vegan24
Kitchen sheet
BEO rev. 3 · allergenstree nuts, table 6
Plates120
Invoices
Deposit paid$4,870
Balance · due 29 May$4,870
The venueHollis Barn
Lower Field · Fri 12 Jun confirmed
Setup
Tables · rounds of 815
Chairs120
Barfull · north wall
Floor planrev. 2
Day of
Load-in2:00 pm
Doors6:30 pm
Seated7:15 pm
Last call9:45 pm
Room
Capacity 160 · one event that night
The clientyour event with Marrow & Rye
Guests120
Documents
Contractsigned 04 Apr
Depositpaid 06 Apr
Balance · due 29 May$4,870
Menu & event orderrev. 3
Messages
Can we move the vegetarian count to 24?
Done. The kitchen sheet and your balance already show it.
Follow one event

From the picture in someone’s head to paid.

The Ainsley–Okafor rehearsal dinner: six stages, one record, and nobody types the guest count twice. Keep scrolling.

Inquiry

Someone already sees it.

Ainsley fills in the form on Marrow & Rye’s site: the date, 120 guests, Hollis Barn. That is the record now. Nobody at the caterer retypes a word of it.

Proposal

Priced from the menus you already keep.

Three courses from the real menu at the real prices. 120 plates, $9,740. Minutes, not an evening rebuilding last year’s quote.

Contract

Signed where they stand.

Your template, their signature, on a phone in a parking lot. The proposal Ainsley read is the contract Ainsley signed. Nothing to print, nothing to scan.

Event order

The kitchen’s copy, without the copying.

The signed contract becomes the BEO. Same numbers, same menu, the tree-nut allergy at table six. The pass works from the sheet the client agreed to.

One record. One motion.

Six stages, and the guest count was typed once. Here is what stops happening when the record is the thing everyone works from.

  • Leads stop dying in a shared inbox.
  • Signatures stop taking three follow-up calls.
  • The headcount stops being typed five times.
  • Deposits get invoiced whether anyone remembers or not.

The rest of the kit

Everything else it takes to realize the vision, on the same record.

Event orders the kitchen can work from

Built from the signed contract, not retyped from it. Order templates open your recurring event types mostly filled in.

One catalog behind every quote

Menus, packages, and add-ons in one place. Raise a price once and every future proposal uses it.

Allergens at the item level

Tag an item once. The tag rides the proposal, the BEO, and the client's view instead of living in one person's memory.

Floor plans on the event

Tables and stations laid out on the actual event. The plan the client approved is the plan the crew sets.

One calendar for the operation

Events, appointments, staff, rooms, and equipment together. You see the double-booking before you confirm the date.

Messages that stay on the event

Threads attach to the booking. When the coordinator is off, the next person opens the event and reads everything.

Every brand, one back office

Several concepts or venues, one operation. Each keeps its own forms, catalog, look, and client view. One login.

QuickBooks Online sync

Invoices and customers flow into the books your accountant already uses. Nobody rekeys deposits at month end.

Permissions per team member

Sales sees the pipeline. The kitchen sees the BEO. You see all of it, across every brand you run.

We’re working with a few of you first.

A handful of catering companies and venues, onboarded by the founders. No signup form, no sales team. The first step is an email.

Panko is built alongside real operations: the deposit rule someone needed on a Tuesday, the BEO field the kitchen kept writing in by hand. Work with us now and yours is one of the operations it gets shaped around.

Two lines is plenty. We reply to every note, even when the answer is “not yet.”

Write to us

Tell us what you run.

hello@panko.events