Count time because the invoice does not show it
A home robot can shift work as well as perform it. Someone may research the product, prepare the room, create accounts, learn controls, supervise early routines, recover from interruptions, contact support, review settings, and eventually close accounts or return equipment. Those minutes may never appear on an invoice, but they affect affordability, accessibility, adoption, and whether the routine produces net value.
We found no measured household time-saving figure for KOKO in the official overview reviewed on October 2, 2026. That leaves a practical question for an evaluation: how much work does the chosen routine remove, add, or move between people? Track the actual configuration and household. A time estimate for a similarly named Coco or Co Co product does not answer that question.
- Research, demo preparation, purchasing, and scheduling
- Space, network, account, and rule setup
- Learning, training, prompting, and supervision
- Care, charging, or cleaning work required by current instructions; troubleshooting and support
- Review, update, data, relocation, and end-of-use work
Build a baseline before the KOKO evaluation
Choose one routine and observe how it works today. Record who participates, active work time, waiting time, interruptions, coordination, travel, and recovery after an exception. Note the outcome quality and frequency. A baseline prevents a common error: counting all time spent with the robot while treating the existing routine as if it required no effort.
Define the completion rule and observation period before testing. One week may miss infrequent maintenance, while a longer period may blend learning with steady operation. Use separate phases for preparation, learning, routine use, and support. Capture a few representative days rather than demanding perfect timekeeping from every person. Explain the purpose and avoid turning household measurement into surveillance.
- Current routine, people, frequency, and outcome
- Active time, waiting time, and interrupted time
- Exceptions and recovery work
- Observation window and limitations of the sample
Log direct, shared, and displaced time
Direct time requires attention: setup, intervention, cleaning, troubleshooting, or support calls. Shared time happens alongside another activity but still creates a constraint, such as remaining nearby. Displaced time is work the person would otherwise have done. Keep these categories separate. Ten minutes of active troubleshooting and ten minutes of passive waiting do not create the same burden, even though both appear as elapsed time.
Record who did the work because a task can shift from one household member to another without disappearing. Note whether the person could perform it comfortably, whether instructions were usable, and whether the work occurred at an inconvenient time. Add organization time for researchers, developers, caregivers, IT staff, or facilities teams when the evaluation extends beyond a household.
- Date, routine, phase, and configuration
- Person or role performing the work
- Direct minutes, constrained minutes, and elapsed duration
- Reason: planned task, intervention, failure, support, or change
- Outcome and whether the work is likely to recur
Turn the log into a fair value measure
Compare the baseline with the evaluated routine using the same completion rule. Calculate gross time avoided, new time added, and the distribution of work across people. Do not claim savings from a task that was skipped, completed to a lower standard, or moved to someone whose effort was not logged. A meaningful result can be improved predictability, reduced physical strain, easier coordination, or a preferred experience even when minutes do not fall.
A dollar conversion is optional. If the decision requires one, document the rate and why it applies; do not automatically price family time as employee labor or assume every saved minute becomes productive work. GAO recommends sensitivity analysis for cost estimates. Apply it here by checking whether the conclusion survives more frequent routines, longer supervision, or a support incident than occurred during the observed period.
- Gross baseline time for the same acceptable outcome
- KOKO-related preparation, operation, and recovery time
- Net change and which person experiences it
- Non-time benefits and burdens stated separately
- Sensitivity to frequency, failure, and learning assumptions
Use review points instead of defending sunk time
Review after setup, after the learning period, and after enough repeated use to see a pattern. Decide whether to continue, simplify the routine, request support, change household roles, pause, or stop. Time already spent learning should not force a household to continue when recurring burden exceeds value. Likewise, a difficult first week should not be treated as permanent if a documented change removes the cause.
The price is right for the household when the money spent and the work added are justified by the outcome people actually experience. Keep a dated summary of the observation period, configuration, exceptions, and distribution of effort. Revisit it after a change to software, services, the routine, household needs, or support. A new average is useful only when it still represents the people who live with the result.
- Learning time expected to decline and recurring time expected to remain
- Maximum acceptable supervision and administration
- Named change that could improve the result
- Next review date and stop condition
Frequently asked questions
Has Homebot One published how much household time KOKO saves?
The official pages reviewed on October 2, 2026 did not publish a standard verified household time-saving figure. Measure the exact routine, configuration, people, and conditions in your own evaluation.
Should supervision count as a KOKO cost?
Yes. Record active intervention, required presence, interruptions, and recovery separately. Even when supervision has no invoice, it affects household burden and the sustainability of the routine.
Do I need to assign a dollar value to family time?
No. Minutes, timing, distribution, accessibility, and interruption burden can support a decision without a dollar conversion. If money is assigned, document the rate and test other assumptions.
Can time data for a Coco robot be used for KOKO?
Not by name alone. KOKO is Homebot One's official spelling, and time burden depends on the identified product, version, routine, people, environment, and support arrangement.
Sources & further reading
From Homebot One, the team building KOKO in Fremont, California.



