A crossover autonomy team
2023 – 2026- Setup
- Strong consumer-grade engineering, a genuinely impressive prototype, and an early sole-source contract that read to investors like validation of a programme relationship. The team's plan was to win on capability and deal with accreditation later, on the theory that the capability gap would force accommodation.
- What happened
- It did not. Retrofitting the security boundary, supply-chain provenance and airworthiness evidence took eighteen months and forced a hardware redesign to remove components with unacceptable origin. The prototype contract expired without converting to a programme of record, and the relationship it represented turned out to belong to an office with no procurement authority.
- Where it stands
- The competitor that designed for the accreditation boundary from the first schematic shipped visibly less capability and won the re-compete, because it could deliver into the environment on the customer's timeline. It is now iterating capability inside a boundary it already holds, which is the cheap direction to travel.
- Retrofit cost
- 18 months + redesign
- Prototype-to-programme conversion
- 0
- Winner's differentiator
- boundary-first design
Build for the boundary, then add capability inside it. Track conversions from prototype to programme of record; contract announcements are marketing.
