Enterprise
Several sites, one pipeline, and a number per job.
What it does
Three things that break at more than one site
Everything below ships today. Nothing here is a roadmap item.
One board, every site
Operations are a first-class thing here, not a tag: each truck, kitchen or site carries its own colour, and one pipeline shows every job across all of them without anybody exporting a spreadsheet.
Who can see what, enforced on the server
Roles and permissions are checked where the data is read, not by what a page chooses to render. A crew member opening a job sees the job — not the margin on it.
A P&L per event, not per month
Revenue, food cost, crew, travel and fuel on the event that earned them. A monthly total tells you the business made money; this tells you which jobs did.
The third one, moving
A number per job, not per month
Each inclusion prices itself against what was really paid, and says which rung that number earned. Where a cost cannot be derived the event withholds the margin rather than reporting a zero it cannot stand behind.
- Mon Enquiry logged 80 guests · Sat 26 Sept
- Mon Quote sent $6,200
- Wed Customer accepted deposit paid
- Wed Package chosen Grazing & shared mains
- Thu Recipes priced 34 ingredients, from your invoices
- Fri Crew rostered 4 people · 6h each
- Sat Timesheets approved 23.5h actually worked
- Mon Supplier invoice logged The Pantry · $1,204
- Tue Invoice paid $6,200 cleared
- Revenue invoice $6,200
- Food & goods event-cost −$1,204
- Crew shift-approved −$891
- Overheads allocated −$530
- Fees commission −$112
Start
Talk to us about your operation
Every feature is on every plan. The plans differ on volume, not on capability.