Are we ready for a Pilot?
Useful for
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.
Public purpose
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.
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
Startup playbook: from POC to Production
This is a CTO playbook for augmenting the agentic SDLC with the company work that sits around the software. Most startup writing focuses on building the product. This playbook focuses on the identity, governance, data protection, delivery, cloud and operational decisions that allow a small SaaS company to move from idea to production without creating avoidable risk.
Is the company ready?
The first few months of a software business are not just about building the product. They are about creating the conditions that allow the product to be built, deployed, governed and supported without the company tripping over its own foundations.
Can we start the POC?
Before starting the POC, there is a small amount of governance that should be put in place. This is not about slowing the team down or pretending to be an enterprise. It is about creating enough shape that the first few months do not become a mess of forgotten passwords, inconsistent names, unclear decisions and accidental access.