Strategy question

How would you price across creators, developers (API), and enterprises?

Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.

What this question tests

Tests pricing strategy across three distinct buyer segments with very different usage patterns and budgets.

Segment clearly: individual creators are price sensitive and usage light, developers integrate via API and scale with volume, enterprises need custom terms, support, and compliance.
Match pricing models to segment behavior: creators likely prefer simple flat tiers, developers prefer usage based API pricing, enterprises prefer negotiated contracts with volume discounts.
Design the creator tier to lower the barrier to trying the product, since creators are the top of funnel that often become advocates or later upgrade to higher usage.
Design developer pricing around predictable unit economics, since API customers build businesses on top and need to forecast their own costs reliably.
Design enterprise pricing around value delivered and required guarantees, like uptime SLAs and dedicated support, not just raw usage volume.
Confirm with the interviewer whether the immediate priority is growing creator volume, developer API revenue, or landing enterprise logos, since that shapes where to invest pricing simplicity.

Explicitly matches pricing structure to how each segment actually consumes the product, rather than forcing one pricing model across all three.
Positions the creator tier as a funnel into developer and enterprise usage, not just a standalone revenue line, recognizing creators often become advocates.
Prioritizes predictability for developers, since unpredictable usage based costs are a common complaint that drives churn to competitors.
Notes enterprise pricing needs to bundle in things beyond raw usage, like support and compliance guarantees, which matter more to that buyer than unit price alone.

Applying one pricing model, like pure usage based, across all three segments despite very different needs.
Ignoring the funnel relationship between creator adoption and later developer or enterprise revenue.
Treating enterprise pricing as just a volume discount rather than a different value proposition entirely.

How would you handle a creator who becomes a heavy API user, causing a mismatch in tier?
What would you include in an enterprise contract beyond usage volume?
How would you test whether developer pricing is actually predictable enough for customers?