A successful pilot is the beginning of a scaling decision, not proof that every site needs the same equipment. Expansion works best when the organisation understands which conditions made the first deployment reliable.
Practical guidance from Desert Horizon. Product examples illustrate a category; capabilities depend on the exact supplied configuration.
Separate repeatable and site-specific work
Document the training, readiness checks and task definitions that can be reused. Then list the features that depended on the pilot site: floor layout, doors, loads, charging or network arrangements. This distinction helps the next site estimate implementation effort without pretending that deployment is only a matter of copying a map.
Review exceptions over time
Look beyond the launch period. Ask how often staff intervene, which consumables are used and whether the service remains reliable when the project champion is absent. Include maintenance and software changes in the record. A fleet decision should reflect sustained operation rather than only the best week of a carefully supported trial.
Expand in manageable groups
Select the next locations with clear process owners and comparable tasks. Use the same acceptance definitions while allowing necessary local changes. Keep service support and spare-part arrangements aligned with the growing fleet. Expansion should increase useful completed work without creating an unmanageable burden for the people responsible for keeping it running.
Three points to take into your project
- Document what made the pilot work.
- Review sustained exception rates.
- Match expansion to support capacity.
