Key takeaways
- The $200,000 to $400,000 a year per hospital figure is a vendor projection, not an audited result.
- Split any per-site claim into deliveries, staff minutes and cost per move before you believe the total.
- Minutes saved only count as money when the hospital redeploys them, shortens shifts or avoids overtime.
- Two weeks of your own runner logs is the baseline a vendor cannot argue with.
- Compare a fixed monthly payment against measured recovered minutes, never against the headline number.
Is the $200,000 a year per hospital figure proven?
A vendor says each hospital running its robot could bring in $200,000 to $400,000 a year. That is a projection, and nothing we found in public sources audits it. Serve Robotics stated the range in its January 20, 2026 release on the Diligent Robotics acquisition, describing it as the expected annual sales from each hospital facility deploying Moxi robots.
Treat the figure as a hypothesis to test, not a budget line. It tells you what the vendor hopes to book from a site. It does not tell you how many runner minutes a hospital recovers, how many moves a robot completes, or what those minutes cost. Those three quantities are what a facility team can measure, and they decide whether a fixed monthly payment is worth signing.
How the public record counts Moxi work
Vendor counts are the closest thing to hard data available. Serve's release reports that Diligent's Moxi fleet has completed over 1.25 million autonomous deliveries, with nearly 100 robots deployed across more than 25 hospitals. Proof News, citing Diligent, reports over 1.3 million tasks and nearly 100 robots at more than 25 hospital systems. Deliveries and tasks are not the same unit, so ask which one a vendor means before you multiply anything.
Independent checks are thinner. Proof News says it reached out to 14 hospitals that deployed Moxi, and five of them confirmed they are still running the program. That is Proof News's own reporting, not vendor data, and the sample is small. One hospital's own release, quoted by PYMNTS, reported more than 40,000 deliveries representing more than 16,000 hours of work. That is useful, but it covers one site and does not show a cost.
We did not find audited hospital revenue figures, a per-delivery cost, or a published staff-minute baseline for Moxi. Your worksheet has to fill those gaps with your own data.
Split the claim into three measurable numbers
The last line is where most claims quietly inflate. A minute freed from a runner is worth money only if the shift gets shorter, overtime drops, or the time moves to work someone is already paid to do. A minute lost to hallway idling is not a saving.
- Annual moves: robots at the site, times completed moves per robot per operating day, times operating days per year. Count only moves that replace a human task.
- Staff minutes recovered: baseline minutes per move from your logs, minus the minutes a person still spends loading, unloading, waiting for elevators or clearing exceptions.
- Cost per move: total annual fee plus your own support time, divided by annual moves.
- Value: recovered minutes divided by 60, times the loaded hourly labor cost you can actually redeploy.
Test the split against your own runner logs
Pull two weeks of runner records before any vendor demo. Note the task type, pickup and drop times, the route, and every interruption, such as a locked door, an elevator wait or a missing specimen. Two weeks covers a weekday and weekend pattern for most units, and it gives you a baseline that is yours.
Then run the vendor's numbers against yours. If the claimed delivery count per robot is high but your runners complete far fewer moves per hour on the same routes, the gap is either a route mismatch or an overstated task count. Ask the vendor which tasks count, and whether a delivery that needed a person at the elevator is logged as a robot delivery.
Where per-hospital claims usually break
Three places cause most of the gap. Redeployment comes first, because freed time rarely shows up on a spreadsheet unless someone assigns it to other work. Exceptions come second. A robot that completes most runs still leaves a person handling the rest, and that person's time belongs in the cost per move.
Routing is the third failure point. A corridor layout that suits a demonstration can slow a fleet in a real building during shift change. Hospitals also differ by run type. A medication run, a lab specimen run and a meal tray run carry different handling rules and time windows, so one per-site average can hide the routes where a robot pays and the ones where it does not.
What the Serve and Diligent deal numbers do and do not tell you
Serve closed its acquisition of Diligent Robotics on January 27, 2026, according to TipRanks. The headline value in the January announcement was $29 million in Serve common stock, subject to adjustments, with a potential earn-out of up to $5.3 million tied to performance milestones, according to Robotics and Automation News. A Serve SEC 8-K pro forma filing gives a preliminary purchase price of approximately $25.7 million, including $3.1 million of contingent earnout fair value, and states that final acquisition accounting may be materially different.
Those are deal numbers, not hospital results. AI Business reported that Serve did not disclose the financial terms, so outlets disagree about what was public, which is one more reason to cite the filing directly. The same filing's unaudited pro forma figures for the first quarter show combined revenue of $3.483 million and a net loss of $51.032 million. A hospital buyer should weigh the vendor's financial position alongside its per-site projection, and should ask who supports the robots if ownership of the business changes again.
How to read a fixed monthly payment after the worksheet
A fixed monthly payment only means something after the worksheet is done. Divide the payment by the recovered minutes you can redeploy each month, then compare that cost per recovered minute with the loaded labor you already pay. A payment that looks modest next to a vendor headline can still be expensive per move if the robot runs few routes.
PYMNTS reported in 2026 that NEURA leases its bed robot for a fixed monthly fee. Our research did not find NEURA's pricing details, so we cannot compare them. A fixed fee makes budgeting predictable, but it does not fix the cost per move, which depends on routes, exception rates and what the freed time is used for.
Service Robot Co. is a full-service, OEM-neutral integrator. We pick the right robots across manufacturers, and we lease robots only, through financing on a 3-year lease with one fixed payment quoted after a site assessment. Our assessment maps the runner routes and measures baseline minutes first, so the worksheet is filled with your numbers before any payment is quoted. We start from your logs, not from the vendor's headline.
Frequently asked questions
Want a robot working for you?
Tell us the job and the site. We will recommend the robot, quote the lease, and keep it serviced.
Sources
- Serve Robotics investor release on the Diligent Robotics acquisition (January 20, 2026)
- Robotics and Automation News: Serve Robotics to acquire Diligent Robotics
- PYMNTS: Robots give hospitals more capacity without adding beds (2026)
- Proof News: Moxi hospital robots reporting
- StockTitan: Serve Robotics release on Diligent Robotics acquisition
- StockTitan: Serve Robotics SEC 8-K filing
- AI Business: Serve Robotics acquires hospital robot company
- TipRanks: Serve Robotics completes acquisition of Diligent Robotics
