Resources · Field notes for restaurants
Field notes from real shifts.
Playbooks, operator interviews, and short guides on running a calmer service: written from the floor, not from a content calendar.
Where the field notes stand today
The first field notes are in draft. This page tells you what's on the way and what you can read today.
Six topics. Same shape as the platform.
Each topic maps to a department on the platform. The notes come from the same shifts the software runs on, not generic SEO posts.
What the field notes will cover
- Service
Front of house
Reservations, walk-ins, POS handover, and the branded customer site. The thinking behind the floor screen.
- Floor plan
- Reservations
- Walk-ins
- POS swap
- Branded site
- Kitchen
Back of house
Recipes, prep, KDS, and waste. Field notes from the line.
- Recipes
- Prep sheets
- KDS
- Waste tracking
- Money
Finance & accounting
Daily reconciliation, Xero sync, BAS, and supplier bills. Closing the loop with your accountant.
- Stripe
- Xero
- Recon
- BAS
- Bills
- People
People & HR
Hiring, onboarding, certifications, scheduling, and payroll. From application form to first pay run.
- Hiring
- Onboarding
- Certifications
- Scheduling
- Payroll
- Comms · AI chief-of-staff
Phone, inbox, SMS: answered.
Notes on the AI receptionist, the unified inbox and the daily manager brief: what a small team actually asks of them.
- AI reception
- Unified inbox
- Two-way SMS
- Daily brief
- Tasks
- Compliance
Records an inspector can read.
HACCP, RSA, temperature logs, age verification, and the audit trail. The binder, made live.
- HACCP
- RSA
- Temperature
- Age check
- Recall
- Audit
What you can read today
Five pages already live.
While the field notes are in draft, these pages cover the platform end-to-end, and they're all written in the same voice you'd expect from the notes.
- Product
Product overview
Food-safety records, forecast-driven prep and ordering, and one weekly cost number.
Read - Pricing
What a package includes
Every capability in the platform, and how we scope a package around a venue.
Read - Customers
Pilot customers
The two venues in pilot: what each one has switched on.
Read - Security
Security & isolation
Row-level multi-tenant isolation, encryption, audit trails, and the controls operations should expect.
Read - Changelog
Changelog
Every release in plain language. What changed, when, and why.
Read
What we will publish. What we won't.
We don't run a content team or an SEO machine. Every field note has to earn its place by helping an operator on Monday morning.
Editorial principles · written from the floor
What we'll publish
- Playbooks from real shifts, written with the operator who ran them.
- Setup notes: getting a kitchen off paper diaries and onto a phone.
- Honest postmortems: when something on NexDine broke, what we learned, what shipped.
- Short technical primers: when an operator should care about RLS, STP, or BAS.
- Short interviews with the people who actually run the room: chef, manager, bookkeeper.
What we won't publish
- Ranked-post listicles or AI-generated SEO sludge.
- Vendor-comparison hit pieces written without using the other product.
- Whitepapers gated behind a form.
- "Top 10 restaurant trends" posts disconnected from a real shift.
- Anything we wouldn't read ourselves.
Be the first to read field note 01.
We'll email when the first three notes go live. No drip campaign, no list rental, no other emails. You can reply directly and we'll read it.
We don't have a CRM yet. We reply ourselves, usually within a business day.
Field notes · the long form
When the notes go live, you'll know.
Until then, the platform itself is the best resource, and the pilot programme is the most direct way to use it.
0 published, 6 in draft