06 · Operations
In developmentHIRO Service
What the house knows, in the hand of whoever is at the table
The Floor
The point where the memory touches the table. Service carries the guest brief to the floor, records what happens during service and returns it to the memory live, with nobody writing it down twice. It consumes the same contract as the rest of the team. In development: the contract with the memory works end to end and the floor app is being built now.
Being built right now. Design-partner programme open.
Data written down twice gets lost once.
The work
What it does, exactly.
Every line carries its own status. If something is in beta, it says so on the line, not in a footnote.
- Carries the guest context to the tableIn development
- Records service consumptionIn development
- Returns to the memory what happened at the tableIn development
- Margin-aware dish suggestionIn development
- Rotation by moment of consumptionIn development
What it does not do yet
It does not replace your current POS if you already have one settled: it coexists with it.
Margin-aware suggestions and moment-of-consumption analysis are in development.
It does not handle payroll, shifts or inventory.
At the table
Guest context where it gets used: in the hand of whoever is serving.
One contract
It consumes the same API as the rest of the team. One single source of truth.
Margin, in development
The food-cost aware suggestion is being built. We do not sell it as done.
No double entry
What happens in service returns to the house memory on its own.
HIRO Service · The Floor
What happens at the table enters the memory live. No double entry.
What it works with
It plugs into what you already have.
TPV · Revo
In integrationReading the closed ticket to know what was actually consumed, not just who booked.
CoverManager
In integrationReal availability, creation, modification and cancellation of the booking. The employee does not leave a note for someone to key in later, the booking is made.
When it goes on duty
The hospitality year is not flat.
The periods where this employee carries the most weight.
July and August, volume
Summer brings no new problems. It brings the same ones, multiplied.
November and December, the house at full load
Six weeks worth a quarter, and the team has nothing left to give.
HIRO Service waitlist
Join the waitlist and we'll notify you before launch.
HIRO Service enters development in 2026 with planned launch in Q3 2026. If you already use HIRO Brain or HIRO Connect, you get private beta priority.
The vacant post
What happens without it
The brief stays in the office and never reaches the table
What happened in service gets written in a notebook and returns nowhere
Sales data trapped in a system that talks to nobody
The same data typed twice, in two different places
What changes
With it on the team
Whoever is at the table knows what the house knows
Service feeds the memory with no extra work
One single source of truth between floor and system
The next visit starts where the last one ended
You cannot hire it yet. You can build it with us.
We are looking for houses that want to define it with us. You come in early, you shape the design and you test it against your real operation.
Join as a design partner