Stripe · Go-to-market · Senior · 45 to 60 minutes

How should Stripe launch its payments API?

Stripe provides software and APIs that let businesses accept payments and move money online. Answer this product management case and get it graded line by line against a weighted rubric.

Segmentation
GTM strategy
MVP scoping
Pricing judgment
Experiment design

The situation

In fall 2010, Patrick and John Collison have a working prototype for online payments, a very simple API that lets a website or app start accepting card payments far faster than bank gateways or PayPal style setups. A few friendly developers think the idea is promising, but Stripe is still fragile. Some of the product experience is manual behind the scenes, the team is small, and big unanswered questions remain around fraud, onboarding, non US use cases, and whether customers will trust a new payments company with mission critical money movement. The founders ask you, acting as Stripe's first product lead, to recommend how to bring the product to market over the next several months. Stripe cannot pursue every buyer at once. The obvious economic buyers at many companies are finance teams, but the people who feel the implementation pain most sharply are developers. The team also needs a way to get feedback that is stronger than polite interest. Your job is to define who to target first, what to launch, how to acquire early customers, and how to learn fast without overbuilding.

What to produce

Write a 1 to 2 page go to market brief.

Your answer must

Recommend the initial target segment, user, and buyer, and explain why other segments should wait.
Define the launch MVP, including which parts must be productized for customers and which operations can remain manual temporarily.
Propose an early customer acquisition plan for the first cohort, including founder led actions and likely distribution sources.
Recommend a pricing approach and explain how it will be used to separate real demand from weak or polite feedback.
Define the key success metrics, major risks, and decision points for expanding beyond the initial wedge.

Constraints

Stripe must earn trust in a regulated, mission critical category where failures can block customer revenue.
The team is small and cannot build a full payments platform for multiple segments at once.
Some core capabilities are still immature, so a fully automated backend is not realistic at launch.
Incumbents already exist, even if their products are painful to use.

Format

Use short sections: target wedge, MVP and operations, customer acquisition, pricing and learning, risks and expansion triggers.

How Stripe actually played it

Covers Stripe solving a hard problem others ignored, early customers, MVP, pricing as a feedback tool and an ecosystem.

Solve a hard problem others ignore
Use pricing to find strong feedback
Build an ecosystem

Built from How Stripe Grows by Jaryd Hermann (How They Grow).