Product Maturity Framework

A city-building metaphor for engineering decisions. Seven stages from Outpost to Keystone guide how teams should think about product, technology, infrastructure, and dependencies.

Product Maturity Framework

Every product is a city being built. The decisions that make sense for an outpost don't make sense for a metropolis, and vice versa.

The Core Insight

The problem isn't making "bad" decisions. It's making decisions that don't match your stage.

Building enterprise-grade infrastructure for an MVP wastes months you don't have. Shipping duct-tape solutions when you have millions of users creates technical debt that compounds.

SageOx helps teams make stage-appropriate decisions by making context explicit and keeping engineering mindsets aligned.


The Seven Stages

1. Outpost

Core Theme: Exploration and validation

You're scouting new territory. Everything is an experiment. Speed of learning matters more than durability.

| Aspect | Guidance | |--------|----------| | Engineering Mindset | "Will this help us learn faster?" | | Success Criteria | Validated problem-solution fit | | Typical Duration | 1-3 months | | Team Size | 1-3 people | | Infrastructure | Local dev, maybe a shared staging server | | Dependencies | Use whatever's fastest to integrate |

Common Mistake: Over-engineering. Building a castle when you need a tent.


2. Camp

Core Theme: Establishing a foothold

You've validated something. Now you're committing resources. Still scrappy, but with intention.

| Aspect | Guidance | |--------|----------| | Engineering Mindset | "Can we sustain this for 6 months?" | | Success Criteria | First paying customers or committed users | | Typical Duration | 3-6 months | | Team Size | 3-7 people | | Infrastructure | Cloud provider, basic CI/CD | | Dependencies | Evaluate build vs. buy more carefully |

Common Mistake: Premature scaling. Adding Kubernetes when you have 100 users.


3. Settlement

Core Theme: Building foundations

Real users depend on you. Reliability starts to matter. Technical debt becomes visible.

| Aspect | Guidance | |--------|----------| | Engineering Mindset | "What patterns should we establish?" | | Success Criteria | Sustainable growth, repeatable processes | | Typical Duration | 6-12 months | | Team Size | 7-15 people | | Infrastructure | Monitoring, alerting, incident response | | Dependencies | Audit critical path dependencies |

Common Mistake: Ignoring patterns. Letting each developer reinvent the wheel.


4. Village

Core Theme: Community and governance

Multiple teams coordinate. Conventions emerge. You need rules that scale beyond "ask Bob."

| Aspect | Guidance | |--------|----------| | Engineering Mindset | "How do we make good decisions easy?" | | Success Criteria | New team members productive in days, not months | | Typical Duration | 1-2 years | | Team Size | 15-50 people | | Infrastructure | Internal platforms, shared services | | Dependencies | Formal vendor evaluation, SLAs matter |

Common Mistake: Under-governing. "We're small, we don't need process." (You're not that small anymore.)


5. Town

Core Theme: Specialization and efficiency

Dedicated teams own distinct domains. Efficiency gains compound. Technical excellence becomes competitive advantage.

| Aspect | Guidance | |--------|----------| | Engineering Mindset | "How do we do this 10x better?" | | Success Criteria | Industry-leading practices in core areas | | Typical Duration | 2-5 years | | Team Size | 50-200 people | | Infrastructure | Platform teams, internal tools, observability | | Dependencies | Strategic partnerships, not just vendors |

Common Mistake: Over-specializing. Creating silos that can't collaborate.


6. City

Core Theme: Mature operations

You're a known entity. Stability and predictability matter. Innovation happens within established frameworks.

| Aspect | Guidance | |--------|----------| | Engineering Mindset | "How do we evolve without breaking?" | | Success Criteria | Consistent delivery, manageable tech debt | | Typical Duration | 5+ years | | Team Size | 200-1000 people | | Infrastructure | Enterprise-grade, multi-region, DR tested | | Dependencies | Long-term contracts, deep integrations |

Common Mistake: Stagnation. "This is how we've always done it."


7. Keystone

Core Theme: Critical infrastructure

Others build on top of you. Backward compatibility is sacred. You're responsible for ecosystems.

| Aspect | Guidance | |--------|----------| | Engineering Mindset | "What's the 10-year impact of this decision?" | | Success Criteria | Trusted by enterprises, platforms, governments | | Typical Duration | Ongoing | | Team Size | 1000+ people | | Infrastructure | Global, redundant, formally verified | | Dependencies | You ARE the dependency for others |

Common Mistake: Moving too fast. Breaking changes that cascade through dependent systems.


How SageOx Helps

The framework is simple. Applying it is hard.

Stage Detection: We help teams honestly assess where they are, not where they want to be or where they were six months ago.

Decision Context: When AI agents make engineering decisions, they know your stage. An agent helping a Settlement team suggests different patterns than one helping a City team.

Mismatch Alerts: We surface when decisions don't match your stage. Building enterprise auth for an Outpost. Shipping quick hacks in a Keystone.

Team Alignment: Everyone sees the same context. "We're a Settlement now" means something concrete.


The Mismatch Problem

Most engineering pain comes from mismatch:

  • Under-building: Settlement-stage decisions in a Town-stage company. Quick hacks that become load-bearing walls.

  • Over-building: City-stage decisions in an Outpost-stage company. Six months to ship a feature nobody wants.

  • Denial: Believing you're still an Outpost when you're clearly a Village. "We're still small" while onboarding fails.

  • Aspiration: Acting like a City when you're a Camp. Bureaucracy that strangles velocity.

The goal isn't to rush to Keystone. The goal is to build appropriately for where you are right now.


Getting Started

The Product Maturity Framework is how SageOx thinks about engineering decisions. It's embedded in how our platform works.

Ready to get your team aligned on your current stage?