What should an AI platform prioritize next: consumer, enterprise, or developer platform?
### Signal to interviewer
I can make portfolio prioritization choices by evaluating strategic compounding, not surface-level TAM narratives.
### Clarify
I would clarify current traction by segment, monetization maturity, channel strength, and capability gaps.
### Approach
Use a segment sequencing matrix: score consumer, enterprise, and developer paths on distribution, retention depth, monetization speed, and strategic spillover.
### Metrics & instrumentation
Primary metric: growth efficiency by prioritized segment. Secondary metrics: segment retention quality, expansion velocity, and cross-segment pull-through. Guardrails: overconcentration risk and roadmap fragmentation.
### Tradeoffs
Single-segment focus accelerates execution but reduces optionality. Multi-segment pursuit preserves optionality but dilutes team velocity.
### Risks & mitigations
Risk: wrong initial segment bet; mitigate with quarterly re-evaluation. Risk: weak spillover to other segments; mitigate with platform primitives. Risk: execution drag from split focus; mitigate with explicit no-go list.
### Example
Prioritize developer platform first to drive distribution, then scale enterprise packaging once governance and reliability controls are battle tested.
### 90-second version
Pick a lead segment using compounding criteria and sequence the others deliberately. Focus creates momentum; sequencing preserves long-term expansion without diluting execution.
- Which segment currently has the strongest product pull signal?
- What evidence would trigger switching primary segment priority?
- How do you quantify cross-segment spillover benefits?
- What org structure supports staged segment sequencing?