Stripe · Strategy · Mid · 45 to 60 minutes

Where should Stripe place its next growth bet?

Stripe provides online payments and financial infrastructure that businesses use to accept money and move funds on the internet. Answer this product management case and get it graded line by line against a weighted rubric.

product_strategy
prioritization
market_segmentation
go_to_market_thinking
trade_off_analysis

The situation

It is late 2011, and you are a PM at Stripe preparing an annual planning recommendation for Patrick and John Collison. Stripe's core payments API is gaining strong word of mouth among developers because it makes online payments far easier to implement than older options. At the same time, expectations are rising after a high profile fundraise, and competition is intense, especially from Braintree, which already has momentum in a similar market. Internally, there is disagreement about what the company should do next. One group wants to scale sales and marketing around the current product to grow faster. Another wants to broaden the roadmap toward more traditional payments buyers and enterprise needs. A third group argues that more internet commerce is flowing through platforms and marketplaces, which have more complex money movement problems than a single merchant site. Assume Stripe can only fund one major strategic push over the next 12 months. Your job is to recommend where Stripe should focus its next product and growth investment, and what not to do yet.

What to produce

A 1 to 2 page strategy memo, about 700 to 900 words.

Your answer must

Define the primary customer segment Stripe should focus on for the next 12 months, and explain why the other segments should not be the main focus yet.
Compare at least three options: scale sales and marketing around the current product, expand toward traditional payments buyers and enterprise needs, or invest in a product strategy for platforms and marketplaces.
Recommend one strategy and describe the core user problem, the minimum product capabilities needed first, and how the plan builds on Stripe's developer-first strengths.
Propose a distribution approach for the chosen strategy, with 3 success metrics for the first year, including at least 1 leading indicator and 1 outcome metric.
Identify the top risks and trade-offs, including product simplicity, implementation complexity, and organizational focus, and suggest mitigations.

Constraints

Stripe has only a small sales team and minimal marketing support today.
Engineering capacity can support only one major new initiative over the next two quarters.
Existing developer integrations must remain reliable, and the core API experience cannot become meaningfully harder to use.

Format

Use headings: context, options, recommendation, first year plan, metrics, risks.

How Stripe actually played it

Four lessons from Stripe's product strategy: make a needed task easy, avoid big early marketing, build for platforms and marketplaces, and go deep.

Make a painful task easy for developers
Platforms multiply distribution
Depth in one area beats breadth early

Built from Stripe, A Modern Product Rocket by Aakash Gupta (Product Growth).