Tech Startup Scaling Cases: From Growth Stage to Enterprise

Tech startup scaling cases test whether you can advise a company that has found product-market fit but now faces the harder problem: growing 5–10x without breaking the business. Based on our analysis of 800+ consulting interviews, these cases appear most frequently at McKinsey’s growth-stage practice, BCG’s digital ventures arm, and Bain’s private equity portfolio work.

Why Scaling Cases Are Distinct

Scaling cases sit between two more familiar categories — early-stage growth strategy and mature technology industry cases. The economics are fundamentally different from both:

In our experience coaching candidates, the trap in scaling cases is applying either the startup playbook (move fast, ignore unit economics) or the enterprise playbook (optimize margins, slow down). Interviewers want to see you navigate the tension between speed and sustainability.

Five Recurring Case Archetypes

Scaling cases cluster into five patterns. Recognizing the archetype in the first 60 seconds of a case lets you pull the right mental model immediately.

flowchart TD
    A[Tech Scaling Case] --> B{What's the core tension?}
    B -->|Revenue growing but losses widening| C[Unit Economics at Scale]
    B -->|Domestic success, international ambition| D[Geographic Expansion]
    B -->|Product-led growth hitting ceiling| E[GTM Motion Shift]
    B -->|Hiring can't keep pace with growth| F[Org Design & Talent]
    B -->|Single product, need platform| G[Product Expansion]
    C --> H[Diagnose CAC inflation, cohort decay, or margin compression]
    D --> I[Assess market readiness, localization cost, competitive landscape]
    E --> J[Evaluate sales-led vs. product-led vs. hybrid]
    F --> K[Structure org layers, hiring velocity, culture preservation]
    G --> L[Analyze adjacencies, build vs. buy vs. partner]

Archetype 1: Unit Economics at Scale

The company is growing revenue 80%+ year-over-year but losses are accelerating. The board wants a path to profitability without sacrificing growth momentum.

Framework approach:

1. Decompose unit economics by customer segment — enterprise vs. mid-market vs. SMB often have radically different LTV/CAC profiles
2. Identify where CAC is inflating (channel saturation, increasing competition, declining organic share)
3. Assess whether gross margins improve with scale or face structural ceilings
4. Model the breakeven timeline under different growth/spend scenarios

Key benchmarks to cite:

Archetype 2: Geographic Expansion

The company dominates its home market (typically US) and faces the decision of where and how to expand internationally.

Critical questions to structure:

• Market sizing: What is the total addressable market in target geographies? How does willingness-to-pay differ?
• Competitive landscape: Is the target market served by a local incumbent, or is it greenfield?
• Localization cost: Product localization, regulatory compliance, local payments, customer support in-language
• Go-to-market: Direct sales team vs. channel partners vs. self-serve (depends on ACV)

In our experience, the strongest candidates explicitly address the sequencing question — which market first, and what criteria determine the order. A simple scoring matrix (market size × ease of entry × strategic value) demonstrates structured thinking.

Archetype 3: Go-to-Market Motion Shift

The company grew through product-led growth (PLG) — free trials, self-serve signup, viral loops — but is now hitting a ceiling. Enterprise customers need sales touch, and competitors are winning large deals.

The case question is usually: how do you add enterprise sales without cannibalizing PLG efficiency or bloating the cost structure?

Archetype 4: Org Design and Talent at Hypergrowth

Headcount is doubling annually. The case explores how to maintain velocity, culture, and quality as the organization scales from startup informality to structured execution.

Common diagnostic areas:

• Span of control (are managers overloaded with 15+ direct reports?)
• Decision-making speed (how many approval layers does a product change need?)
• Specialization vs. generalism (when do you split functions that founders held together?)
• Engineering-to-revenue ratio (is R&D spend producing proportional output?)

Archetype 5: Product Expansion and Platform Strategy

A single-product company wants to become a platform. The case tests your ability to evaluate adjacencies, determine build-vs-buy-vs-partner, and sequence multi-product launches.

Connect this to our build vs. buy guide for the tactical framework. The strategic layer here is: which product extension maximizes existing customer wallet share while creating defensible switching costs?

The Scaling Case Framework

Across all five archetypes, a consistent four-part structure works:

flowchart LR
    A[1. Growth Diagnostics] --> B[2. Constraint Identification]
    B --> C[3. Economic Modeling]
    C --> D[4. Sequenced Roadmap]

Step 1 — Growth Diagnostics: Understand current trajectory. Revenue growth rate, customer acquisition rate, retention curves, margin trends. Ask for cohort data if available.

Step 2 — Constraint Identification: What specific bottleneck limits the next stage of growth? Is it demand-side (market saturation, CAC inflation), supply-side (engineering capacity, infrastructure limits), or organizational (hiring, decision speed)?

Step 3 — Economic Modeling: Quantify the trade-offs. If we invest $X in geographic expansion, what’s the payback period? If we add 20 enterprise salespeople at $200K fully loaded each, how many deals do they need to close to justify the investment?

Step 4 — Sequenced Roadmap: Prioritize actions by impact and feasibility. Interviewers want to see you recommend a phased approach — what you do in the next quarter, next year, and next three years.

Practice Scenarios by Difficulty

Common Mistakes in Scaling Cases

1. Applying startup logic at scale — “Just grow faster” ignores that CAC inflates nonlinearly and org complexity grows quadratically with headcount
2. Ignoring unit economics cohort effects — Average LTV/CAC masks that recent cohorts often perform worse as early adopters are exhausted
3. Treating international expansion as copy-paste — Each market has distinct competitive, regulatory, and cultural dynamics
4. Forgetting the org dimension — Recommending aggressive growth without addressing how the organization absorbs it undermines credibility

Key Takeaways

• Scaling cases test the tension between growth speed and operational sustainability — never recommend one without addressing the other
• Recognize which of the five archetypes you face in the first minute and apply the corresponding mental model
• Always decompose by customer segment — aggregate metrics hide critical differences between enterprise, mid-market, and SMB economics
• Quantify trade-offs explicitly — interviewers want to see you model scenarios, not just describe qualitative options
• The Rule of 40 (growth rate + profit margin > 40%) is the single most useful benchmark to anchor your scaling case analysis
• Connect org design to business outcomes — hiring plans and reporting structures are strategic decisions in hypergrowth, not administrative ones

Ready to practice technology scaling cases? Explore our technology case library for real scenarios, or test your skills with AI Mock Interview to get instant feedback on your scaling case structure and quantitative reasoning.