Build for best-case scalability from day zero to avoid technical debt crises
Design your pricing model, infrastructure, and technical architecture assuming massive success from launch. If 100,000 users signed up tomorrow, your system should handle it without requiring a complete rebuild. This prevents the painful scenario where sudden growth forces you to rethink core decisions under pressure, creating technical debt that becomes expensive to fix later.
When to use
When architecting any product with potential for viral growth or network effects. Especially critical for B2C products where growth can spike unpredictably, and for bootstrapped founders who can't afford expensive rebuilds after launch.
Don't do this
Building the absolute minimum to 'just get it working' and assuming you'll have time to refactor later. Growth often happens faster than expected, and scrambling to handle scale under pressure leads to poor architectural decisions and potential downtime.
1 Founder Who Did This
Advised building from day zero optimizing for best case scenario - if 100K people signed up today, could your app handle it? Designed pricing and infrastructure for scale before needing it