Startup playbook
Are we ready for a Pilot?
Defines the public shape of the "Are we ready for a Pilot?" stage. The website should explain the decision, the intent and the related guidance without publishing the full assessment method.
Useful for
Public purpose
Curation guidance
Open with the distinction between technical governance and data governance. Pilot means external users may enter real data, even if the product is not yet Production.
Use the control introductions to explain data obligations, Pilot infrastructure, and architecture risks such as tenant isolation and AI model use.
Summary intent
The company should understand what data may appear, where it goes, what users have been told, how Pilot resources can be recreated, and which architecture decisions affect customer risk.
How Brokenhouse helps
Turn this into a practical plan.
I help technology teams turn this guidance into decisions, implementation plans, governance evidence and production-ready operating models.
Talk through your situationNext guidance
Related decisions to work through
Use containers as the default packaging stance. They give the product a flexible route from POC to Pilot to Production without forcing the final hosting decision too early.
Pilot data should not accidentally become Production data. The transition needs an explicit decision.
Stage gates are decision points. They help a company decide whether it is ready to move to the next level of customer exposure, operational risk and commercial promise. They are not ceremonies and they are not a replacement for judgement.