How do you decide when a product is ready to scale?
Model answer
Model answerScaling prematurely is one of the most expensive mistakes a product team can make. Before scaling, I want to see: a retention curve that has flattened (users are staying), a repeatable acquisition channel (growth isn't purely word-of-mouth luck), and unit economics that work at current volume. I'd also want signal that the core value proposition is understood the same way by new users as it was by early adopters. If onboarding completion is dropping as we grow, that's a sign the product isn't ready — the early users self-selected, new users won't.
Framework · CIRCLES
- CComprehend the Situation
What does 'scale' mean here — users, markets, channels? Clarify scope first - IIdentify the Customer
Who are the next users you'd be scaling to? Are they like your current base or different? - RReport Customer Needs
Do new users experience the same core value early adopters did? Check onboarding drop-off - CCut through Prioritization
Flattened retention + repeatable acquisition + working unit economics — all three must be green - LList Solutions
Options: scale now, scale one channel only, run a controlled expansion cohort, or invest in readiness first - EEvaluate Trade-offs
Scaling too early burns budget and dilutes the product; too late cedes market. Weigh both risks - SSummarize Recommendation
Scale when retention is flat, acquisition is repeatable, and unit economics hold — not before all three
Related questions
- How would you define the product vision for an AI assistant in a consumer app?
- How would you manage building a platform product that serves both internal teams and external customers?
- How do you build a product roadmap when company strategy shifts mid-year?
- How do you align multiple product teams around a single company strategy?
- How would you evaluate whether to build, buy, or partner for a new capability?