FAQ
Fair questions, straight answers.
13 questions on file
01 ·Residents first
Do the robots go anywhere near residents or resident care?
Never as caregivers. Nothing our robots do involves resident care. They carry trays, linens, and supplies, so caregivers spend their hours on people, not hallways. That line isn't a launch posture we quietly relax later. It's the design, and it's written into the resident-safety protocol your team signs before a single robot rolls.
What about falls? How do the robots behave around walkers and wheelchairs?
Robots run slower in resident areas, announce themselves softly, yield to people, and do not operate in memory-care neighborhoods. Speeds and routes are set with your team, hallway by hallway. Walkers, wheelchairs, and unhurried hallways are the operating environment, not an edge case. The crew is configured for your building, with your people, before it runs its first loop.
Do they work in memory care?
No. Memory-care neighborhoods are excluded by policy: the routes are drawn so the crew never enters them, and that exclusion is part of the resident-safety protocol your team signs before deployment. Where a robot doesn't belong, our answer is that it doesn't go, not that it goes carefully.
Can they carry medications?
Never. Our robots deliver trays and supplies, never medications, and nothing they carry involves resident health information. That's a deliberate exclusion, not a gap in the roadmap: the crew carries the hallway work, and everything that touches a resident's care, medications included, stays with your staff.
Do the robots go anywhere near residents or resident care?
Never as caregivers. Nothing our robots do involves resident care. They carry trays, linens, and supplies, so caregivers spend their hours on people, not hallways. That line isn't a launch posture we quietly relax later. It's the design, and it's written into the resident-safety protocol your team signs before a single robot rolls.
What about falls? How do the robots behave around walkers and wheelchairs?
Robots run slower in resident areas, announce themselves softly, yield to people, and do not operate in memory-care neighborhoods. Speeds and routes are set with your team, hallway by hallway. Walkers, wheelchairs, and unhurried hallways are the operating environment, not an edge case. The crew is configured for your building, with your people, before it runs its first loop.
Do they work in memory care?
No. Memory-care neighborhoods are excluded by policy: the routes are drawn so the crew never enters them, and that exclusion is part of the resident-safety protocol your team signs before deployment. Where a robot doesn't belong, our answer is that it doesn't go, not that it goes carefully.
Can they carry medications?
Never. Our robots deliver trays and supplies, never medications, and nothing they carry involves resident health information. That's a deliberate exclusion, not a gap in the roadmap: the crew carries the hallway work, and everything that touches a resident's care, medications included, stays with your staff.
02 ·Day to day
How is soiled laundry kept separate from clean?
In sealed, separated soiled and clean bins that are never mixed. The laundry unit runs soiled linen out and clean linen back as two contained loads on a schedule (the loop your caregivers walk a dozen times a shift), and every run is logged like everything else the crew does.
What do residents and families actually think?
We measure it rather than assert it. The 60-day pilot reports weekly on hours returned, uptime, and what your staff actually think. Your community's read on residents and families is part of that conversation. The design principle is plain: robots deliver trays; your people deliver care.
Are you replacing our staff?
No. We fill the shifts you can't hire for. Deployment plans are built with your team, and the roles that require judgment stay human. The hours aren't lost to the work. They're lost to the walking: trays, linens, and supplies that pull trained people away from the jobs only people can do. What changes is what a shift looks like: the crew absorbs the walking, and the caregivers you fought to hire spend their hours on residents.
How is soiled laundry kept separate from clean?
In sealed, separated soiled and clean bins that are never mixed. The laundry unit runs soiled linen out and clean linen back as two contained loads on a schedule (the loop your caregivers walk a dozen times a shift), and every run is logged like everything else the crew does.
What do residents and families actually think?
We measure it rather than assert it. The 60-day pilot reports weekly on hours returned, uptime, and what your staff actually think. Your community's read on residents and families is part of that conversation. The design principle is plain: robots deliver trays; your people deliver care.
Are you replacing our staff?
No. We fill the shifts you can't hire for. Deployment plans are built with your team, and the roles that require judgment stay human. The hours aren't lost to the work. They're lost to the walking: trays, linens, and supplies that pull trained people away from the jobs only people can do. What changes is what a shift looks like: the crew absorbs the walking, and the caregivers you fought to hire spend their hours on residents.
03 ·Money & the pilot
What does it cost?
$3,500 per month, per community, plus a one-time $3,000 setup itemized up front: freight, mapping, staff orientation, and your documented resident-safety protocol. The monthly rate covers the standard three-robot crew deployed and mapped to your building, service with 24-hour unit swap, survey-ready documentation, and workflow reviews as your building's day changes. It's published on our pricing page, because a company that promises documentation shouldn't make you request a quote to learn the price.
Why per community instead of per robot?
Because you're not buying robots. You're buying hours back from the hallways. The rate covers the standard three-robot crew. Larger communities run larger crews, scoped during the stopwatch study. Then the rate is flat. Per-robot pricing rewards a vendor for selling you hardware. Per-community pricing rewards us for making your whole building run.
How does the pilot work, and what if we want out?
Two steps, and the first costs nothing. The stopwatch study comes first: 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. Then the 60-day instrumented pilot: The crew runs your building's loops while we measure hours returned, uptime, and what your staff actually think, reported weekly. 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. And if you convert and later change your mind, either of us can end the agreement any time after day 90 with 30 days' notice. No termination fees, no exit interviews.
What does it cost?
$3,500 per month, per community, plus a one-time $3,000 setup itemized up front: freight, mapping, staff orientation, and your documented resident-safety protocol. The monthly rate covers the standard three-robot crew deployed and mapped to your building, service with 24-hour unit swap, survey-ready documentation, and workflow reviews as your building's day changes. It's published on our pricing page, because a company that promises documentation shouldn't make you request a quote to learn the price.
Why per community instead of per robot?
Because you're not buying robots. You're buying hours back from the hallways. The rate covers the standard three-robot crew. Larger communities run larger crews, scoped during the stopwatch study. Then the rate is flat. Per-robot pricing rewards a vendor for selling you hardware. Per-community pricing rewards us for making your whole building run.
How does the pilot work, and what if we want out?
Two steps, and the first costs nothing. The stopwatch study comes first: 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. Then the 60-day instrumented pilot: The crew runs your building's loops while we measure hours returned, uptime, and what your staff actually think, reported weekly. 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. And if you convert and later change your mind, either of us can end the agreement any time after day 90 with 30 days' notice. No termination fees, no exit interviews.
04 ·Service & data
What happens when a unit goes down?
If a unit goes down, we swap it. Target: within 24 hours, and the outage itself is logged and reported like everything else. You never inherit the repair problem: no parts on order, no technician window, no robot parked in a closet for three weeks. A down unit is our pager, not yours.
What data do you collect about residents?
Our robots navigate with sensors, not surveillance. Any camera views are masked by design, we store no patient information, and facility data stays the facility's. What the crew logs is room-level and operational (where a cycle ran, when a tray moved, which runs needed a human), and none of it is resident health information. The record describes the building's work, not the people who live there.
What does the survey documentation look like?
Every cycle and delivery is logged automatically and exports as a survey-ready record, assembled continuously, not reconstructed the week before an inspection. Cleaning cycles, laundry runs, tray deliveries, exceptions, and human interventions, each entry time-stamped as it happens, so your team exports the record instead of rebuilding it the week before a survey.
What happens when a unit goes down?
If a unit goes down, we swap it. Target: within 24 hours, and the outage itself is logged and reported like everything else. You never inherit the repair problem: no parts on order, no technician window, no robot parked in a closet for three weeks. A down unit is our pager, not yours.
What data do you collect about residents?
Our robots navigate with sensors, not surveillance. Any camera views are masked by design, we store no patient information, and facility data stays the facility's. What the crew logs is room-level and operational (where a cycle ran, when a tray moved, which runs needed a human), and none of it is resident health information. The record describes the building's work, not the people who live there.
What does the survey documentation look like?
Every cycle and delivery is logged automatically and exports as a survey-ready record, assembled continuously, not reconstructed the week before an inspection. Cleaning cycles, laundry runs, tray deliveries, exceptions, and human interventions, each entry time-stamped as it happens, so your team exports the record instead of rebuilding it the week before a survey.
Question not on the list?
Ask a person. Write to us and one of the humans building this answers.