Stripe · Strategy · Senior · 45 to 60 minutes

How should Stripe back a second product?

Stripe builds payments and financial infrastructure tools that businesses use to accept money and run internet commerce. Answer this product management case and get it graded line by line against a weighted rubric.

Strategy
Org design
Goal setting
Portfolio management
Tradeoff analysis

The situation

Stripe leadership has asked you, a senior PM, to recommend how the company should launch and grow a second product line while its core payments business still dominates attention, resources, and operating habits. The new product matters strategically because leadership wants Stripe to become a multi product company, not just deepen the flagship. But there is pressure to move fast by reusing the flagship team's processes, metrics, and distribution playbook. That creates a hard tension. The new bet is earlier and less proven, so it may need different customer selection, success metrics, product cadence, and tolerance for ambiguity. If it is too tightly coupled to the flagship, it may never get the room to find its own fit. If it is too separate, Stripe could miss the advantages of its brand, infrastructure, and existing customer relationships. Leadership wants a recommendation now because early choices about team structure, goals, and sequencing will shape hiring, roadmap tradeoffs, and how success is judged over the next year.

What to produce

A 1 to 2 page strategy memo.

Your answer must

Recommend an operating model for the second product for the next 12 months, including team ownership, decision rights, and how it should interact with the flagship product organization.
Define 3 to 5 success metrics for the new product and explain how they should differ from the flagship product's metrics at this stage.
Explain what Stripe should share across products versus keep separate, covering at least team structure, goals, and go to market approach.
Identify the 3 biggest risks or second order effects of your recommendation, including at least one risk to the core business and one risk to the new bet.
Propose a sequencing plan with near term milestones and clear triggers for revisiting the structure or goals.

Constraints

Do not assume detailed market data, competitor data, or internal financials beyond the prompt.
Your recommendation must preserve customer trust and execution quality in Stripe's core payments business.
Focus on business line strategy and operating model for the next 12 months, not a feature roadmap or engineering implementation plan.

Format

Use headings: recommendation, rationale, operating model, goals and metrics, risks, milestones.

How Stripe actually played it

An early Stripe PM shares nine lessons for launching a second product while the first dominates attention, with examples from Stripe and Watershed. Good for PMs expanding a portfolio.

A new product needs its own team and goals
Do not let the flagship set the rules for the new bet

Built from From Flagship Back to Fledgling: Going Multi-Product, Lessons From an Early Stripe PM by First Round Review.