How would you prioritize between making GPT-4 cheaper vs investing in GPT-5 capabilities?
Signal to interviewer
I can turn a high-ambiguity model portfolio choice into testable assumptions and staged capital allocation rather than opinion-driven prioritization.
Clarify
Align on the company objective first: margin expansion, share defense, or frontier leadership. Segment demand into price-sensitive high-volume workloads versus premium high-complexity jobs. Confirm decision horizon and risk tolerance for near-term revenue versus long-term moat.
Approach
Use an assumptions tree with three branches: price elasticity for GPT-4, value capture from GPT-5 capabilities, and competitive substitution risk. Fund both tracks, but sequence by reversibility: run fast pricing/routing experiments first, and gate heavier GPT-5 investment on demonstrated quality deltas in premium tasks.
Metrics & instrumentation
Primary metric: profit-adjusted usage growth by segment. Secondary metrics: premium task success lift, enterprise expansion velocity, and churn risk among high-value accounts. Guardrails: latency, reliability, and support escalations after pricing/routing changes. Instrumentation: request-level tags for workload type, model route, fallback path, segment, and outcome quality.
Tradeoffs
Cheaper GPT-4 improves volume and defensibility but can delay differentiation. GPT-5 investment deepens moat but increases capital risk and longer payback. Mixed strategy reduces regret but raises operational complexity.
Risks & mitigations
Risk: misread elasticity and discount where quality is the bottleneck; mitigate with controlled segment tests and holdouts. Risk: overbuild GPT-5 before premium fit; mitigate with milestone-based funding gates. Risk: packaging confusion; mitigate with job-based plans instead of model-based labels.
Example
Scale optimized GPT-4 for support automation and coding assistance where demand is elastic. Reserve GPT-5 for legal synthesis and complex planning where measurable quality lifts support premium pricing.
90-second version
Treat this as dynamic portfolio allocation. Test elasticity and premium willingness to pay in parallel, learn fast through routing and pricing experiments, and scale investment where evidence is strongest. Keep growth tied to profit-adjusted usage, premium workflow outcomes, and trust guardrails.
- What user segment would you prioritize first for: "How would you prioritize between making GPT-4 cheaper vs investing in GPT-5 capabilities?"?
- What exact success criteria define a strong first release?
- How would you instrument this end to end to detect regressions?
- What rollout guardrails would you apply before scaling broadly?