Strategy question

You believe Perplexity’s core agentic experience could unlock value for an enterprise knowledge-work use case, such as competitive research or internal document synthesis. How would you decide whether that opportunity deserves investment now, and what tradeoffs would you make between enterprise-specific requirements and keeping the everyday core product fast, intuitive, and cohesive?

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 deciding whether an enterprise opportunity deserves investment now and what tradeoffs protect the core everyday product's speed and cohesion.

Estimate the opportunity size concretely: how many enterprise accounts or prospects have explicitly asked for this specific use case versus a general interest in 'enterprise features'.
Assess technical reuse: whether the enterprise use case can build on Perplexity's existing agentic core with configuration, or requires a parallel enterprise-only code path.
Weigh the cohesion risk explicitly: features added for enterprise research workflows must not add friction, like extra clicks or setup steps, to the core consumer flow.
If reuse is high and cohesion risk is low, invest now, gated behind an enterprise workspace setting rather than exposed to all users.
If reuse is low or cohesion risk is high, defer and revisit once the core agentic experience has matured enough to absorb it cleanly.
Set a success metric tied to enterprise account value, not general engagement, to justify the investment after launch.

Uses concrete demand evidence, explicit account requests, rather than a general sense that enterprise is a growth opportunity.
Gates the enterprise capability behind a workspace setting specifically to protect the core product's speed and simplicity.
Names a clear decision rule, invest now only if reuse is high and cohesion risk is low, otherwise defer.

Investing in enterprise features based on general market interest rather than specific account demand.
Adding enterprise complexity directly into the core flow instead of gating it behind a workspace setting.

Chapters of the AI PM course that teach what this question tests.