Well Architected

AWS Well-Architected assumes you optimize all 6 pillars simultaneously. Startups can’t. Here’s the priority order by stage:

Pre-Seed Priority Stack

1. Cost Optimization — you die if you run out of money
2. Security — but ONLY: no public data exposure, no hardcoded creds, basic IAM
3. Performance — just “fast enough” for the user experience
4. Operational Excellence — you ARE the operations team
5. Reliability — single-AZ is fine, manual recovery is fine
6. Sustainability — irrelevant at this stage

Seed Priority Stack

1. Security — first customer data means you can’t leak it
2. Cost Optimization — credits are running out or gone
3. Reliability — first SLA commitments need basic redundancy
4. Performance — user expectations rise with a real product
5. Operational Excellence — basic CI/CD, basic monitoring
6. Sustainability — still not the priority

Series A+ Priority Stack

All 6 pillars matter. Use the standard Well-Architected framework. But still weight Cost and Security highest — board reporting requires cost visibility, and enterprise customers require security posture.

Startup-Specific “High Risk” Redefinitions

Standard WA rates these as HRI (High Risk Issue). For pre-seed startups, they’re actually acceptable:

Startup-Specific ACTUAL High Risk Issues (any stage)

These are genuinely dangerous regardless of stage:

Minimum Viable Well-Architected (Pre-Seed Checklist)

Instead of 50+ WA review questions, pre-seed startups need exactly these:

That’s it. Seven items. Everything else can wait.

“When to Do a Full WA Review” Triggers

• Preparing for SOC2 audit
• First enterprise customer with security questionnaire
• Monthly spend > $10K (optimization has real ROI)
• Series A due diligence
• Post-incident (something broke in production affecting customers)
• Annual cadence once you’re past Series A