Deployment-ready is not production: an honest maturity model

“Production-ready” is one of the most abused phrases in enterprise software. It usually means “the demo worked.” We avoid it on purpose.

We describe every application in one of three stages. Each stage describes what has actually happened, not what we hope will happen.

1. Deployment-Ready Application Foundation

This is where every application in our inventory starts. A foundation has:

• been generated and scaffolded on the factory architecture
• a runnable core with domain services and adapters
• an API structure defined by contracts
• a web application
• identity and authorization patterns
• automated tests
• a deployment baseline
• a known, consistent architectural structure

A foundation is real software, not a mock-up. But it hasn't met your data, your identity provider, your integrations or your policies. Calling it “production” would be misleading.

2. Customer-Configured Application

The foundation has been adapted to one organization:

• the customer's requirements and business workflows
• their data and data platforms
• integrations with their systems of record
• AI and model choices, including providers, hosting and evaluation criteria
• their identity environment
• their cloud platform and regional constraints
• their policies and approval rules
• their operating environment

This is what an AI Production Sprint delivers. It is a working application on a production path, but it isn't in production yet.

3. Production Deployment

The application has completed the customer-specific work that production actually requires:

• integration testing against live systems
• security hardening and review
• cloud deployment in the customer's environment
• operational testing
• customer acceptance
• observability and alerting
• a support design
• production controls

Only then do we call it production.

Why the distinction matters

For buyers, it sets honest expectations. A foundation shortens the path to production. It doesn't remove the path. Integration, hardening and acceptance still take real effort, and a vendor who claims otherwise is either underestimating your environment or overestimating their template.

For risk and security teams, it gives a shared vocabulary. A deployment-ready foundation can be reviewed architecturally. A customer-configured application can be reviewed against your policies. A production deployment has passed your gates.

For partners, it prevents over-selling. A systems integrator who promises a “production-ready AI app in two weeks” is setting up the relationship to fail.

How the stages map to engagements

Stage	How you get there
Deployment-ready foundation	Already in the inventory, or generated by the factory
Customer-configured	Solution Definition Sprint, then AI Production Sprint
Production deployment	Completion of the production roadmap, often inside an Application Family Program

What we won't do

We won't label a listing “production” because it runs. We won't describe a customer-configured application as a production deployment before acceptance. And we won't publish customer names, metrics or badges we can't evidence.

It's a small discipline. It also happens to be the one enterprise buyers trust most.

Read more about the factory, or bring us a use case.