Strategy question
Harvey can only fund 2-3 ecosystem bets in the next 12 months. How would you identify and prioritize the first 0→1 integrations or data partnerships to build across the core app, Word Add-In, and Outlook plugin for enterprise legal teams? Walk through your framework and how you would balance customer pull, workflow frequency, implementation cost, and strategic defensibility.
- Harvey
- Strategy
- Hard
Practice this question out loud. An AI interviewer asks it, follows up like a real interviewer would, and scores your answer. Type or speak.
Start a mock interview on this question · Mock interview from a job description
What this question tests
Tests prioritization under real constraint: choosing 2 to 3 ecosystem bets across surfaces using a repeatable framework, not gut feel.
How to approach it
- Gather customer pull data: which integrations or partnerships are most requested across the core app, Word Add In, and Outlook plugin.
- Score each candidate on customer pull, workflow frequency, implementation cost, and strategic defensibility, such as data exclusivity or switching cost created.
- Weight workflow frequency heavily, since a daily used integration compounds value faster than a rarely used but flashy one.
- Check for dependencies, for example if one integration needs infrastructure the others would also reuse, prioritize that one first to unlock the rest.
- Pick 2 to 3 bets that span different surfaces rather than clustering all investment in one, to spread risk and prove the platform works broadly.
- Set a checkpoint at 90 days to confirm adoption before committing further engineering time to a bet.
What a strong answer includes
- Uses a scoring framework with named criteria rather than an intuitive ranked list, showing repeatability under future similar decisions.
- Explicitly weighs strategic defensibility, for example an exclusive data partnership competitors cannot replicate, not just short term revenue.
- Identifies shared infrastructure dependencies across candidate bets to sequence work efficiently instead of treating each in isolation.
Common mistakes
- Prioritizing purely by loudest customer request without checking implementation cost or strategic value.
- Spreading investment across too many small integrations instead of committing fully to 2 to 3 defensible bets.
Likely follow-up questions
- How would you handle a top enterprise customer who demands an integration that scores low on your framework?
- What would make you kill one of the three bets mid quarter?
More strategy questions
- How should Harvey price for law firms vs. in-house legal teams?Harvey · Strategy · Hard
- How would you grow Harvey adoption among conservative, risk-averse law firms?Harvey · Strategy · Hard
- You inherit Vault with strong customer interest but limited engineering capacity. How would you set Vault’s product vision and a 12-month roadmap across file management, AI search/Q&A, document extraction, secure sharing, and platform investments like permissions, indexing, and integrations? Walk through your prioritization framework, major bets, and what you would explicitly defer.Harvey · Strategy · Hard
- Harvey can fund only one major integration track next: deeper iManage support, broader SharePoint coverage, or cross-platform capabilities like sync, permissions mapping, and admin controls. How would you decide what to build first, and what tradeoffs would you make across customer demand, implementation effort, security risk, and strategic leverage?Harvey · Strategy · Hard
- Harvey’s Command Center needs to serve three jobs for enterprise admins: understanding adoption, managing users and access, and enforcing governance. How would you define the product strategy and first 12-month roadmap for Command Center, and what framework would you use to make trade-offs across those three areas for Harvey’s largest legal customers?Harvey · Strategy · Hard
- You inherit a platform where teams lack visibility into request failures, latency regressions, customer-impacting incidents, and model-quality degradation. How would you define the product scope for observability, decide what to ship first, and ensure the work improves customer outcomes rather than just adding internal tooling?Harvey · Strategy · Hard
More questions from Harvey
Learn the skill behind it
Chapters of the AI PM course that teach what this question tests.
- Chapter 4: Discovery and strategy for AI products
- Chapter 9: Prove it paid off: outcomes, economics, and pricing
- Chapter 14: Get the job: the AI PM interview loop