LinkedIn Recruiter India-Only Tier: Product Design, Cannibalization Model and Go/No-Go

LinkedIn earns a large part of its revenue from Recruiter, the product that lets recruiters search for LinkedIn members and reach out to them, for example through InMail messages. LinkedIn is considering a cheaper, reduced version of Recruiter for India, in which recruiters can find and contact only members who are located in India. You are the product manager for this idea. ### Clarifying Questions - Is the only restriction the member's location, or do other parts of the product (InMail allowance, search filters, seats per account) also shrink in the cheaper version? - Who may buy it: any recruiter in India, only organizations contracting and billed in India, or also global companies for their Indian hiring teams? - Are the prices given in Part 2 per recruiter seat per year, and would the cheaper version replace anything LinkedIn currently sells in India? - What is the main objective: incremental revenue, market share against other hiring platforms in India, or more hiring activity for members in India? ### Part 1 — Design the India-only product Explain how you would build this product: which recruiters it is for, what it includes and leaves out, how the restriction to members in India works, and how it sits next to the existing Recruiter product. ```hint Design the fence A cheaper edition is only worth launching if its restriction separates buyers who would never pay the full price from buyers who would. Ask which current Recruiter customers could switch, and what would stop them. ``` #### What This Part Should Cover - Buyer segments in India and how each relates to the full Recruiter product. - Product scope, including how "located in India" is defined and how eligibility to buy is checked. - Protections against cannibalization and misuse, and the effect on members who would receive more messages. ### Part 2 — Operationalize the pricing and recommend go or no-go Assume the full Recruiter product costs \$9,000 per year and the India version \$6,000 per year. Explain how you would put the launch into operation and how you would present it to a VP who must decide whether to go ahead. ```hint Compare a downgrade with a new sale Before sizing the market, work out what LinkedIn loses each time an existing customer moves to the cheaper version and what it gains from each customer who would not have bought before. That ratio frames the decision. ``` #### What This Part Should Cover - A revenue model that weighs new purchases against downgrades, with labeled assumptions and a sensitivity range. - A rollout plan, such as a pilot or staged launch, with success and stop criteria. - A concise VP presentation: the decision requested, the evidence, the risks, and what would change the recommendation. ### What a Strong Answer Covers - One clear objective, such as incremental revenue or market share, that links the product design to the financial case. - Fences in Part 1 that are consistent with the assumptions in the Part 2 model. - Member-side guardrails, since more recruiters would be contacting members in India. - Likely reactions from competing hiring platforms in India and from existing global customers. - A recommendation with explicit conditions attached, not a list of considerations. ### Follow-up Questions - The pilot shows that most buyers are existing customers moving down rather than new ones. What do you tell the VP? - How would you stop a multinational from buying the India version for a team that actually recruits candidates outside India? - If the India launch succeeds, how would you decide whether to offer similar editions in other countries?