Strategy question

Anthropic wants product-led growth to work for both individual Claude users and eventual team or enterprise expansion. How would you evaluate whether a consumer growth investment could also support B2B expansion, and what tradeoffs would you consider before prioritizing it?

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 ability to evaluate whether a consumer growth investment also serves a future B2B expansion motion, and the tradeoffs of designing for both.

Define the specific consumer growth investment under consideration, such as a referral or team-sharing feature, since dual-purpose fit depends on the specific mechanic.
Assess whether the feature naturally creates multi-user footprints inside one workspace, such as colleagues inviting each other, which is the pattern that seeds team or enterprise expansion.
Check whether the feature's data model would need significant rework to later support team billing, admin controls, or permissions, since retrofitting is costly.
Weigh the tradeoff of building slightly more structure now, such as basic workspace concepts, against the cost of delaying the consumer-only version's launch.
Decide based on whether the incremental cost of dual-purpose design is small relative to the option value it creates for a future enterprise expansion motion.

Picks a specific candidate feature rather than discussing consumer versus B2B growth in the abstract.
Identifies the exact mechanic, colleagues inviting each other, that would make a consumer feature double as a B2B seed.
Weighs retrofit cost explicitly, recognizing that not building basic workspace structure now could be expensive to add after millions of users exist.
Frames the decision as a real cost-benefit tradeoff, not an assumption that every consumer feature should be built enterprise-ready.

Assuming any consumer growth feature automatically supports future B2B expansion without checking the underlying data model.
Over-engineering every consumer feature for enterprise use cases that may never materialize, slowing consumer launches.

What is the smallest structural change you would make now to preserve B2B optionality?
How would you decide this was not worth the added complexity for a specific feature?