For restaurants, bars, cafes and event venues
Your bookings and your staff schedule live in one system, so the wage bill for a service sits beside the covers it served. Menus, events, guest records and the follow-ups after come with it.
EU-hosted · No per-cover fees · Set up with you on a call
What is on the books tonight, and what still needs you.
Built for
Cost per cover
The schedule is priced from the shifts you published, at each person’s own rate. The covers are counted from the party sizes in the book. Reports divides one by the other, day by day and across the period, one venue at a time.
Where it lives
Reports, on the Labour cost tab, next to the rostered hours for the same days. The Bookings tab carries the same figure beside revenue per cover, over any window from today to the last ninety days. Wage numbers only open for the people you have given the wage permission to; everyone else sees the schedule and the hours.
How the number is worked out
01
Every published shift in the window, priced at that person’s own rate: by the hour, by the shift, or unpaid. Planned breaks come off the paid minutes, and a shift that runs past midnight is measured on the real clock rather than the wall one.
02
Party sizes added up from the bookings on those dates, split by day and by service. A table booked without a headcount counts as one cover, not as none.
03
Per day and for the whole period, shown beside the no-show rate for the same window. That rate is measured only against covers whose outcome is already known, so next Friday cannot flatter it.
What it refuses to guess
01
Salaried people are counted in hours, not in money
Splitting a monthly wage across a month of shifts needs an assumption about how many shifts the month holds. The report says how many people it left out instead of inventing one.
02
Nobody without a rate on file reads as free
A shift with no rate contributes hours and no money. It stays out of the total rather than landing in it as a zero.
03
Two currencies stay two figures
A schedule that mixes currencies is shown as two subtotals. Adding them needs an exchange rate, and an exchange rate needs a date and a source. That is a finance decision, not a rounding one.
04
Profit per person is an estimate, and says so
Nothing records which booking a shift served, so setting someone’s scheduled cost against the bookings assigned to them is a considered estimate. That sentence is printed on the screen it appears on.
A peek under the hood
Bookings and the staff schedule sit in one database. So do menus, events, outreach, loyalty, the guest record, and the pages your guests use without an account.
The day as a list, a time grid, or a timeline by table. Guests book from one simple form, and every reminder carries a link they can cancel or move it from.
Plus QR capture, and one reporting tab for every module you switch on.
Print a QR code, stick it on a table or a receipt, and every guest who scans it lands on a branded join page. They leave their email, confirm it, and become a contact on your list - tagged with the property and the touchpoint they came from, so you always know where each person came in.
One code per table, per receipt, or per door
A week with Guestavo
No abstract benefits. Four moments from a normal week, and how the same system fills the gap.
Before
You text the contact yourself, hope they reply, and the table sits empty for the rest of service. Nobody remembers it was the third time.
After
You mark it once, and it lands on that guest’s twelve-month record alongside their late cancellations. Once they pass the threshold you set, their next booking arrives as pending instead of holding a table, and they have already read your policy on the booking form.
Before
You build the schedule in a spreadsheet, against a memory of how busy last Saturday felt. Whether it was the right number of people is a conversation you have after payroll.
After
The week grid sits in the same system as the covers already booked. Draft it, publish it when it is ready, and the labour tab prices it against those covers before anybody works the shift.
Before
You hand them a card. You forget. They forget. A great guest never comes back.
After
They scan the QR on the receipt, land on a branded join page, and by morning they are tagged with the property and the touchpoint they walked in from.
Before
You open Mailchimp, your phone, a guest spreadsheet, and an old WhatsApp Web tab. Three hours later you have sent a half-broken email.
After
One composer. Segments live. Email goes out, SMS to regulars, WhatsApp to VIPs. Done before the espresso machine warms up.
Pricing, in one breath
Early access is on the house — no card on file, no clock counting down. When public pricing opens, you keep a permanent discount and we tell you exactly what you will pay.
“I have worked the floor. The last thing you need on a Saturday is a SaaS tab tax.”
Here is the short version
Founding partners
We are onboarding a small group of venues one by one. Leave your details, take a twenty-minute call, and we set the first property up together on a screenshare.
Who we are looking for
How it goes
We review every signup by hand. No automated drip sequence follows.
Within one working day. We learn about the venue, you ask anything you want.
If it is a fit, we build the first property and the first campaign with you on a screenshare.
Or write to us directly info@guestavo.com
Drop your email below. We review every signup by hand and reach out within one working day to set up a 20-minute call.
What you get for going first
Honest answers
No filler, no sales pitch. If something is missing here, drop us an email and we will answer it personally.
Yes. Early access partners pay nothing while we onboard them, period. No card on file, no surprise charges, no "free for 14 days" trick.
Until we are confident the product is solid for everyone. Realistically, a few months. Early partners get plenty of notice before anything changes.
Early access partners keep using Guestavo on a permanent discounted plan. You will not be forced into a higher tier or quietly kicked off.
A small group. Small enough that we can actually answer every message and run setup calls personally without dropping the ball.
Guestavo is built for restaurants, bars, cafes, bakeries, and event-led venues. If your main goal is better guest capture, direct follow-up, and more repeat visits, you are in the right place.
All core modules are available: bookings and reservations, team and scheduling, digital menus, events and RSVPs, outreach, loyalty, and the guest portal. We scope the rollout with you instead of pushing every feature or channel on day one.
Yes. CSV import is ready, and we help you map and clean the first migration during onboarding so nothing falls through the cracks.
Guestavo runs in the browser on desktop and mobile. The guest portal is built to work cleanly on phones, and where supported it can be saved to the home screen without a separate app-store rollout.
In the EU, on infrastructure we control. GDPR-compliant by default. You stay in charge of consent and retention.
Of course. Export your guests, reservations, and content whenever you want. No lock-in, no exit fee, no awkward email exchange.
No. Your guests, your menus, your reservations, none of that gets used to train models. Period.