The exit plan belongs in the buying plan
A buyer usually focuses on getting started, yet the cost of stopping can determine whether an offer is acceptable. Before paying a deposit or beginning a pilot, ask how cancellation works, what can be returned, who pays transport, how accounts close, and what happens to data. These questions are useful even when everyone expects the project to succeed.
Homebot One’s reviewed public pages provide waitlist, demo, pilot, research, and developer contact paths but do not publish standard return or cancellation terms. The applicable rules may differ among a consumer purchase, organizational pilot, research arrangement, developer access, lease, or custom agreement. Use only the written terms for the actual transaction. An exit checklist should be reviewed by the same operational, privacy, security, and finance owners who approve the start of the engagement.
Trace every payment milestone
Create a payment timeline showing deposit, order acceptance, configuration, shipment, installation, pilot start, acceptance testing, recurring-service activation, renewal, and final payment. For each milestone, note whether the amount is refundable, creditable, earned, or contingent. Ask what happens if Homebot One, a partner, or the buyer causes delay.
Distinguish cancellation before shipment from return after delivery and termination after service begins. A cancellation fee, restocking charge, custom-work charge, subscription commitment, and return freight can stack. If an early-access configuration changes before delivery, determine who may cancel and what remedy applies. Avoid relying on a general email if the signed agreement says something else. If acceptance depends on a test, define the procedure, deadline, evidence, cure opportunity, and consequence of failure before equipment arrives.
- Deposit amount and refund conditions
- Cancellation deadlines and milestone charges
- Return window, authorization, condition, and packaging
- Restocking, inspection, shipping, removal, and restoration
- Subscription termination, renewal notice, and final billing
Budget physical return and site restoration
A mobile robot and its accessories may require more return planning than a small consumer device. Ask who disconnects, powers down, packages, insures, and transports the equipment. Confirm whether original packaging must be stored and whether damage in transit is assigned to the buyer, carrier, or vendor. Include chargers, accessories, documentation, and loaned components in the inventory.
Organizations should also budget facilities and staff time. Network credentials may need removal, room layouts may need restoration, and a research or care site may need participant communication. Photograph condition at arrival and departure and use a signed checklist. These steps reduce later disputes without assuming any specific Homebot One process. Record tracking, custody, and receipt confirmation during return, especially when the arrangement includes prototypes or loaned research hardware.
Close accounts and handle data deliberately
Exit is incomplete while accounts, remote access, integrations, stored credentials, logs, maps, media, or research files remain active. Ask what data can be exported, in which format, who initiates deletion, how long backups remain, and what records Homebot One must retain. NIST’s Privacy Framework encourages organizations to map data processing and manage privacy risk across the lifecycle.
For a shared household or care setting, decide whose permission is needed before export or deletion. For research, follow the approved protocol, consent, and institutional data plan. Verify that third-party integrations are separately disconnected. Do not claim a KOKO deletion or portability function until the current agreement or product documentation confirms it. Ask how deletion completion is confirmed and whether the buyer receives a record suitable for its own privacy, security, or research files.
Use exit cost in the go/no-go decision
Add expected exit cost to the ownership model, then test a difficult case: early cancellation, failed acceptance, long downtime, organizational change, or end of support. The result may justify a smaller pilot, milestone payment, acceptance test, cap on charges, or clearer data and removal obligations. Risk allocation is part of price, even when it does not appear on the first invoice.
When terms are incomplete, keep the issue open rather than assuming the most favorable outcome. FTC consumer guidance recommends checking return policies and keeping the contract, receipts, warranties, and other purchase records. Exact rights still depend on the transaction and jurisdiction, so obtain qualified advice where appropriate. A maximum exit exposure can be compared with the value at risk and used as a practical approval threshold before the agreement begins.
Frequently asked questions
What is Homebot One’s KOKO return policy?
The reviewed public pages do not publish a standard return policy. Ask for the current written terms that apply to the specific purchase, pilot, lease, research, or developer arrangement.
Should data deletion be part of a return checklist?
Yes. Ask about export, deletion, backup retention, account closure, integrations, and records that must legally or contractually remain.
Are deposits always refundable?
No general assumption is safe. Refundability depends on the written offer and the event causing cancellation.
When should exit cost block a KOKO pilot or purchase?
Treat exit cost as a stop condition when the maximum credible exposure, data obligation, removal work, or unresolved cancellation term exceeds the limit approved before the agreement.
Sources & further reading
From Homebot One, the team building KOKO in Fremont, California.
