How It Works
Three steps.
You approve every one.
Bodie is designed to feel boring in the best way: it connects, it learns, it proposes, you approve. No new system to live in, no chatbot to manage, no guest experience to rethink.
Connect what you
already use.
We start with the systems you already run. Toast POS is supported at launch; scheduling integrations (7shifts, Homebase, and others) are rolling out based on what beta partners actually use. On day one, we enable secure Toast data exports to a private landing zone — real sales, menu, and labor data flowing this week, while the full API integration is provisioned in parallel. You authorize access; we handle the plumbing.
- Toast POS — menu, checks, payments, stock status
- Scheduling — availability, time-clock, published schedules (tell us your tool when you apply)
- Vendor invoices — PDFs become structured lines for price tracking
- No customer data on the edge — everything canonical lives in your private cloud database
Credentials are referenced by secure vault — never stored in the database or in logs.
Connections
Toast
Connected · read-only exports
7shifts / Homebase
You tell us → we prioritize
Vendor invoices
PDF → structured lines
Secure vault
No secrets in DB/logs
Private landing zone · encrypted in transit
Bodie learns, then proposes — quietly
Before ordering day
Draft purchase order with per-line rationale, price flags, and forecast context
Before the schedule is due
Draft schedule with availability, skills, pairings, and labor-rules evaluation
Every morning at 6am
Your one-page brief: yesterday, today, and what’s coming
In real time
Depletion alerts and 86 proposals when you’re about to run out
Every proposal shows its work: what data it read, why it recommends what it does, and what it estimates the impact to be. Correlation trace links every action back to its source.
Bodie learns your
restaurant, then gets
to work quietly.
Bodie builds a canonical picture of your restaurant: menu items mapped to vendor items and recipes, guest identity handled with confidence-aware care (and never storing card numbers), events and sports fixtures turned into demand signals, and manager pairings respected as you entered them.
Canonical picture
You review.
One tap to approve.
Nothing Bodie proposes happens until you say so. Open the proposal, scan the rationale and evidence, edit if you want, then approve. Bodie’s approval service — separate from the AI, with its own permissions — validates the proposal is still fresh, executes the approved action, and writes a full audit trail. If the box at the store is offline, the same approval runs through the cloud.
- Proposals expire — stale approvals don’t execute against changed reality
- Re-validation is synchronous — inventory, pricing, and policy checked at approve time
- Irreversible actions always require human approval — hard-coded floor, not a setting
- Every action is audited — who approved, what executed, when, with what result
Approval flow · deterministic
Propose
Approve
Execute
Audit
If box offline, same approval runs via cloud. You get SMS: “switched to cloud processing, nothing interrupted.”
What Bodie never does.
It’s as important to say what Bodie won’t do.
- Never talks to guests. No chatbots, no automated guest outreach without your explicit approval and guest consent.
- Never places an order, 86s an item, publishes a schedule, or sends a message without your approval.
- Never stores a card number. Guest identity uses hashed, confidence-scored aliases — or stays anonymous.
- Never exposes sensitive notes to AI. Manager pairing notes are excluded from every AI context window by design.
- Never replaces the manager’s judgment. Bodie drafts; you decide.
Trust is the feature.
Bodie’s authorization is enforced by database policy, not by prompt instructions. Each helper can only see and do what its role allows.
- Role-based access at the database layer — not just in the prompt
- Per-table read/write controls and redacted columns on every AI-facing surface
- Raw POS payloads preserved immutably for audit and recovery
- Cost and usage metered per restaurant from day one — no surprise bills
Consent is recorded with the exact language shown and timestamp, and opt-out is checked at send time — every time.
What beta actually looks like.
We’re keeping the beta small so we can be hands-on and listen well. Here’s the rhythm:
-
Apply (3 minutes)
Tell us about your restaurant, POS, and scheduling tool.
-
Intro call (30 minutes)
We learn your biggest time sink and confirm fit.
-
Connect (this week)
Toast exports live; your data mirrored securely. No disruption to service.
-
First win (within ~10 days)
Your morning brief live, or the feature that saves you the most time first.
-
Weekly check-in (~15 minutes)
What’s helping, what’s not, what to build next. Your feedback sets the roadmap.
If at any point Bodie isn’t helping, say so. We’ll adjust or you step back — no hard feelings, no lock-in for the beta.
See what Bodie would do
with your restaurant.
Apply for the beta and we’ll map your actual workflow — no sales pitch, just a plain-English walkthrough of where Bodie helps and where it doesn’t (yet).