Hotel Robot for a 100-Room Hotel: Sizing the First Pilot

A 100-room hotel is the most common starting point for a robot pilot. It is large enough to have a real delivery load, small enough that one unit can make a visible difference, and usually has a service lift that can be integrated.

But the pilot still fails if it is sized from a brochure instead of the property’s own request log. This guide walks through the numbers and the operating rules for a 100-room property.

What does a 100-room hotel need from a robot?

Three things, in order:

1. A reliable delivery leg from the service core to the guest floor.
2. A clear guest hand-off that does not require a staff member at the door.
3. An exception path that returns the task to the front desk when something goes wrong.

Everything else — the screen, the language pack, the branding — is secondary to those three. A pilot that gets the delivery leg right but the exception path wrong will be bypassed during the first busy shift. The hotel delivery robot page shows the platform inputs; the room service robot page shows the guest-triggered flow.

How many robots does a 100-room hotel need?

Start with the daily request volume, not the room count.

One unit covers the pilot with spare capacity. The spare capacity is useful: it absorbs peaks and allows the robot to charge without stopping the service.

A second unit is justified when the property needs two-shift coverage, when the lift wait is long, or when the robot must charge during the service window. Redundancy is part of capacity, not a luxury. Run your own numbers with the ROI calculator; the ROI guide explains the cost lines behind the result.

Which tasks should the first robot take?

Amenity and towel delivery. It is the best first task because it is frequent, light, predictable and easy to measure.

A typical first-task list:

• Extra towels, pillows and bedding.
• Toothbrush, slippers, adapters and baby kits.
• Water and minibar restock.
• Late-night F&B after the route is stable.
• Parcels after the compartment and chain-of-custody rules are agreed.

Do not start with hot food or luggage. Hot food adds temperature and spill constraints; luggage adds weight and a different hand-off. Prove the route first. The delivery workflow guide explains the six steps from request to hand-off.

What lift rule works for a 100-room hotel?

Four options, in order of preference:

1. Dedicated service lift with robot priority and a manual override.
2. Shared service lift with a peak-hour exclusion window.
3. Guest lift at off-peak times with a staff escort.
4. Manual staff-assisted lift if no automatic method is viable.

The rule should be written down and included in the front-desk training. “The robot uses the service lift unless a guest needs it” is not a rule; “the robot waits 90 seconds, then requeues” is. The elevator integration guide explains the controller methods and the fire-mode test.

What does a 100-room pilot cost?

The unit price is quoted per configuration. The project total usually adds lift integration, PMS/PABX work, freight, duties and a spare-parts kit.

A single-unit pilot is the lowest-cost way to test demand. If the building integration is uncertain, rent or negotiate a pilot unit with a return option. The price guide explains the landed-cost lines; the hotel robot price page shows the current listing.

How do you measure success in 30 days?

Use four numbers:

• Tasks completed per day — is the robot doing the volume?
• Average round-trip time — is the lift rule working?
• Exception rate — how often does a human have to rescue it?
• Staff time released — is the front desk feeling relief?

Set the baseline before the pilot. If the front desk does not track delivery time today, spend a week logging it manually. A pilot without a baseline cannot prove anything. The deployment guide covers the site preparation; the deployment checklist lists the tests.

What is the expansion path?

If the pilot works, expand in this order:

1. Add the second shift, not the second robot, if one unit can cover it.
2. Add a second unit for redundancy and peak coverage.
3. Add late-night F&B and parcels to the task mix.
4. Add a reception unit only if the lobby has a separate guest-flow problem.

Do not expand to a second building or a second lift bank until the first route is stable. Each new integration repeats the survey and test work. The hotel service robot overview shows the types; the comparison guide explains how to choose the next one.

What are the common mistakes?

Five mistakes account for most disappointing pilots:

1. Buying for the brochure, not the request log. The robot ends up oversized or underused.
2. Skipping the lift exception tests. The normal call works; the busy lift does not.
3. No named owner. The task queue is nobody’s job.
4. No baseline. The property cannot show what changed.
5. Expanding too early. A second unit is added before the first route is stable, doubling the exceptions.

The pilot is a learning exercise with a commercial purpose. Give it a baseline, a scorecard and an owner, and the decision to expand becomes evidence-based rather than emotional. The case studies page shows reference deployment patterns for the same size of property.

Where to go next

• Review the hotel delivery robot and room service robot configurations.
• Check the price guide and ROI guide.
• Run the pilot numbers with the ROI calculator.
• Prepare the site with the deployment checklist.
• Read the delivery workflow guide.
• See the city hotel solution for a 100–180 room layout.
• Browse the product range and factory catalogue.
• Send the room count and lift type through the contact page.
• Message the factory on WhatsApp.

The room count sets the context; the delivery log sets the fleet size. Start with the log, and the pilot has a number to beat.