Article
How many robots does a restaurant need?
Fleet size depends on how long a trip takes and how often trips happen, not on the size of the venue. A large room with a short run to the tables may need fewer robots than a small one with a long run. Measure trips per shift and minutes per trip before accepting any recommended number.
Written by Hybot operations lead, Deployment and operations lead, Hyrcan-Tech · · 5 min read
Floor area is the wrong question
The intuitive approach is to scale with the room: big venue, more robots. It is wrong often enough to be worth correcting properly.
A robot's work is measured in trips. A large open dining room with the pass in the middle produces short runs. A small venue with the kitchen at the far end of a corridor produces long ones. The small venue needs more robot-minutes per delivery than the large one, and sizing by area gets it exactly backwards.
The calculation
Required robot-minutes per shift = trips per shift × minutes per trip.
Both numbers come from your own venue. The ROI method explains how to take them, and it is the same measurement exercise, so do it once.
Then the other side: available minutes per robot per shift. This is shift length minus the time not spent working, which is not nothing:
- Travel to and from charging, and charging itself. A robot below its threshold takes itself to charge and stops receiving work — placement of chargers matters here.
- Waiting at handovers. Many tasks wait for a person to confirm, and that wait is real robot-minutes consumed by staff behaviour.
- Waiting for people in the path, which is correct behaviour and still counts.
Divide required by available. That ratio is your indication.
Why the handover wait deserves attention
It is the line venues consistently underestimate.
If a robot waits ninety seconds at a table because nobody acknowledges it, that is ninety seconds removed from the fleet, repeated all evening. Two venues with identical trips and identical distances can need different numbers of robots purely because one has staff who confirm promptly.
This is an operations problem with a hardware price attached, and it is usually cheaper to fix the workflow than to buy another unit.
The case for starting with one
A single robot answers questions no spreadsheet can:
- Are the trips as frequent as you assumed?
- Do staff actually complete handovers?
- Which routes turn out to be blocked at service time?
Hybot allows robots to be added, removed and reloaded without restarting the system, so scaling after you have learned is straightforward.
One caveat worth knowing: the second robot introduces genuinely new problems — allocation, shared chargers, two machines in one corridor — which is its own subject. A one-unit trial will not surface them.
What we will not tell you
A number of units, from a web page, for a venue we have not seen. Anyone offering that is guessing. Describe the venue and we will work through the sizing with your numbers.
Where to go next
- A method for calculating ROI
- What drives the cost of a service robot?
- Multi-robot coordination, explained
Cluster hub: Smart robotic solutions.
Frequently asked questions
Why isn't floor area the right measure?
- Because the robot's work is trips, not square metres. A large open room where the pass sits centrally produces short runs; a small venue with the kitchen at the far end produces long ones. The second needs more robot time per delivery despite being smaller.
What is the sizing calculation?
- Trips per shift multiplied by minutes per trip gives required robot-minutes. Compare that against the minutes actually available per unit after charging and waiting for handovers. That ratio, rather than any rule of thumb about venue size, indicates how many units the venue needs.
Should I start with one robot?
- Often yes, and it is a genuinely informative experiment. One unit reveals whether trips are as frequent as assumed and whether staff complete handovers promptly. Hybot allows robots to be added without restarting the system, so growing after learning is straightforward.
Where this fits
This page is part of Smart robotic solutions: choosing and buying. If you are working through the topic in order, these are the neighbouring pages.
A method for calculating service robot ROI
Take the baseline before you buy. A practical method for measuring what a service robot actually changes, using your own numbers instead of a vendor's model.
What drives the cost of a service robot?
The robot is one line of several. Site survey, mapping, integration, training and support all vary by venue — what to ask before comparing quotes.
Multi-robot coordination, explained
Two robots are more than twice the problem of one. The failure modes that appear at the second unit, and what a coordination layer has to do about them.
Take it further
If a question here applies to a venue you actually run, the specifics matter more than the general case.