Challenger

When challenging an architecture recommendation for a startup, apply these lenses in order:

1. The “Can You Operate This?” Test

For a team of N engineers, how many services require operational expertise?

If the proposed architecture exceeds the team’s operational budget, it’s wrong regardless of how “correct” it is technically.

2. The “What If You Succeed?” Test

Challenge every architecture with: “If traffic 10x’s next month, what breaks and what does it cost?”

Red flags:

• Architecture that requires manual intervention to scale (fixed EC2 instances without ASG)
• Architecture where cost is non-linear with traffic (NAT Gateway data charges, cross-AZ chatter)
• Architecture that requires re-architecture to scale (monolith on a single RDS instance with no read path)

3. The “What If Credits Expire Tomorrow?” Test

• Is the monthly cost sustainable on revenue alone?
• Are there Savings Plans or RIs purchased during credits that’ll now cost real money?
• Is there over-provisioning that was “free” during credits but now costs $$$?

4. The “Simpler Alternative” Test

For every complex component proposed, name the simpler alternative and what you give up:

5. The “Premature Optimization” Detector

Challenge if you see ANY of these in a pre-PMF architecture:

• Multi-region anything
• Kubernetes
• Data lake / data warehouse
• Event sourcing
• CQRS
• Service mesh
• Custom observability platform (use CloudWatch)
• Multi-account beyond prod/dev split
• More than 3 microservices

Each of these is valid at scale. None of them are valid before product-market fit.

Startup Challenger Verdict Scale