Skip to content

Healthcare’s back rooms aren’t broken. They’re just overdue.

We run everything around the care.

Robot crews run the floors, laundry, meals, and carts of senior living communities, dispatched against the day’s schedule and documented to the minute.

robot crews

deployed & run

$3,500/mo

standard 3-robot crew

24h

unit swap

every cycle

logged

Community schematicSim feed

Event log

  • 07:42tray run · dining → AL wing
  • 07:48laundry loop · IL wing → laundry
  • 07:55floor cycle · corridor eastlogged
  • 08:03tray carts returned · dock
  • 08:03+38 staff min returned

Simulated feed, fictional community data. Illustrative example. Hours returned vary by community, census, and layout. The two-day study measures yours before we promise anything.

01 ·The staffing problem

There aren’t enough people for the work around the care.

  • The shortage

    63%

    communities short-staffed

    Across senior living, 63% of assisted-living communities report staff shortages and the courier-adjacent roles (dining, personal care, CNAs) turn over at 42–49% a year.

  • The churn

    42–49%

    turnover per year

    The roles that keep a building moving (dining, personal care, aides) turn over fastest and stay hardest to refill. Training walks out the door on a loop.

  • The shift

    OPEN

    back of house

    The posting stays up; the shift stays open. Every care facility is competing for the same shrinking pool, and hiring alone doesn't close the gap.

  • The return

    1:1

    courier hour → care hour

    Every courier hour absorbed is a care hour returned: trained people back on the work only people can do.

The hours aren't lost to the work. They're lost to the walking: trays, linens, supplies, and floors that pull trained people away from the jobs only people can do.

03 ·The crew

Three units run the loops your staff never applied for.

The crew runs floors, laundry, and dining, mapped to your building, wing by wing, and dispatched against your community’s day.

  • F class

    Floors

    Autonomous scrub cycles between the day's events and full corridor cleans overnight. Every cycle logged: where, when, how long.

    scrub deck · between-event + overnight cycles

  • C class

    Transport

    The heavy carry loops: carts, bins, and supplies moved on schedule, exactly on time, so skilled hands stop being couriers.

    tug · heavy payload · scheduled loops

  • L class

    Enclosed delivery

    What must travel contained, travels contained: sealed, badge-secured, cleanable compartments, with soiled and clean never mixed.

    enclosed · badge-secured · sealed modules

  • 24H SWAP

    Service · every unit

    If a unit goes down, we swap it. Target: within 24 hours, and the outage itself is logged and reported like everything else.

04 ·The layer

The hardware is proven. The layer is the product.

Healthcare robots don’t fail for lack of capability. They fail in workflows: the approval that stalls, the schedule nobody integrated, the log nobody kept. That failure mode is what the layer is built against. Dispatch runs against the day’s schedule (meals and cases alike), every cycle logs itself, exceptions are tracked, and the record is built for the people who inspect you: surveys and audits, exportable the moment someone asks.

Every cycle and delivery is logged automatically and exports as a survey-ready record, assembled continuously, not reconstructed the week before an inspection.

operations layer

Sample console · fictional demo data

Staff hours returned · weekly

41h

Wk 1Wk 8 · pilot

Cycles logged · today

47

Floors · deliveries · carry loops

Fleet · dispatch

  • F-1 · floorsScrub cycle · dining corridor
  • C-1 · transportSupply run · dock → wing A
  • L-1 · enclosedDock B · charging

Log · this morning

  • 09:41Dining corridor · floor scrub · 6 minLOGGED
  • 09:47Floor 2 · linen run · delivered sealedLOGGED
  • 09:53Wing A · supply cart deliveredLOGGED

Every record above · exportable on request

See how deployment works

The full console · the product tour

Illustrative example. Hours returned vary by community, census, and layout. The two-day study measures yours before we promise anything. All values above are fictional demonstration data.

05 ·What stays human

The care stays human.

This isn’t a limitation. It’s the operating boundary, written into every deployment plan, resident wing by resident wing. The crew runs the courier and janitorial legs so trained hands stay on the work that requires them.

Nothing our robots do involves resident care. They carry trays, linens, and supplies, and they clean floors, so caregivers spend their hours on people, not hallways.

Off your staff’s day

  • Caregivers as couriersretired
  • Skilled hands hauling linenretired
  • Staff pushing cartsretired

Yours, permanently

  • Resident care, all of ithuman
  • Medication handlinghuman
  • Final cleaning sign-offhuman

Before anything deploys

Infection control signs off first.

Nothing deploys until your infection-control lead signs off. We arrive with a written protocol: how the robots are cleaned, where they may travel, and how dirty-to-clean boundaries are respected.

We fill the shifts you can't hire for. Deployment plans are built with your team, and the roles that require judgment stay human.

06 ·The pilot path

Two days of stopwatch. Sixty days of proof. Then one number.

  1. Days 1–2

    The stopwatch study.

    Free

    Two days in your building with a stopwatch, mapping where the hours actually go: which minutes are the work, which are the walking. You keep the report either way.

  2. 60 days

    The instrumented pilot.

    The crew runs your building's loops while we measure hours returned, uptime, and what your staff actually think, reported weekly.

  3. Then

    Convert on measured results.

    If the measurements justify it, the crew stays, at one number set before the pilot started. If they don’t, the crew rolls out and the data stays yours.

The stopwatch study is free and yours to keep. The 60-day pilot converts only if the measured minutes justify it, and you'll have the same numbers we do.

The number it resolves to

$3,500/ month

standard three-robot crew · never metered per robot

+ $3,000 one-time setup

One number for the whole crew, the service behind it, and the documentation that proves it ran. Larger facilities run larger crews, scoped in the stopwatch study; then the rate is flat. The setup fee is itemized, not vague.

Full pricing detail

What $3,500/month covers

  1. 01The three-robot crew, deployed and mapped to your building
  2. 02Service with 24-hour unit swap. A robot down never becomes your problem
  3. 03Survey-ready cleaning, laundry, dining, and exception documentation
  4. 04Workflow reviews with your team as your building's day changes

What the $3,000 setup covers

  • Freight and unit staging
  • Facility mapping and route configuration
  • Three staff orientation sessions
  • Your resident-safety protocol, documented and signed

Legacy hospital logistics robots have leased for $1,500–2,000 per month, per robot. Our pricing covers a three-robot crew, service, and documentation for the whole facility.

The First Five

Not discounted guinea pigs. The five facilities that shape the platform.

5 founding facilities run the pilot path above free, lock founding pricing, and set direction on what the platform builds next. In exchange: five teams reporting which loops earn their keep.

What founding means

  • The stopwatch study and 60-day pilot, free
  • Founding facility pricing, locked while your agreement stays active
  • A direct line to the founder, not a ticket queue
  • First access to every capability the platform adds
  • A real voice in what gets built next

07 ·Questions, answered

The questions every facility asks first.

Do the robots go near residents or resident care?

Never as caregivers. Nothing our robots do involves resident care. They carry trays, linens, and supplies, and they clean floors, so caregivers spend their hours on people, not hallways.

Can they carry medications?

Never. Our robots deliver trays and supplies, never medications, and nothing they carry involves resident health information.

What if a robot breaks?

If a unit goes down, we swap it. Target: within 24 hours, and the outage itself is logged and reported like everything else.

What does it cost?

$3,500 a month, per community, never per robot, plus a $3,000 one-time, itemized setup. Covers the three-robot crew, service with 24h unit swap, and audit-ready documentation of every cycle. No per-task charges, no tiers with asterisks.

08 ·Start here

Your back rooms have waited long enough.

Book the stopwatch study. Two days. Free. You keep the report.

free 2-day stopwatch study · 60-day instrumented pilot · $3,500/month per facility

The stopwatch study is free and yours to keep. The 60-day pilot converts only if the measured minutes justify it, and you'll have the same numbers we do.