Cooltra's journey illustrates a principle that many pure-software founders miss: when your product has physical components, the software must be built around the physical operation, not the other way around.
Their first tech versions were heavily influenced by what the operations team actually needed — not what investors expected a "tech company" to look like. The fleet management system was built because mechanics needed it. The damage reporting feature was built because insurance claims without photographic evidence were consistently disputed. The maintenance scheduling feature was built because unplanned downtime was the single biggest cost driver.
Cooltra's expansion across Spain and southern Europe was enabled by this operations-first approach. When they entered a new city, the operational playbook was already embedded in the software. New cities could follow a proven process rather than learning by failure.