Building product at Stripe: craft, metrics, and customer obsession

Jeff Weinstein, a long-time Stripe product lead who helped scale payments and took Stripe Atlas (company incorporation) from struggling to widely adopted, discusses his approach to craft, customer obsession, metrics, and internal practices. The conversation covers how to find real customer problems, how to choose metrics that reflect customer value, and how to keep teams close to the customer as products scale.

01Key learnings

• Treat a customer who takes time to complain as a rare gift; respond quickly and personally, since speed signals that you care.
• Before investing in craft or polish, confirm the product solves a burning problem customers would pause their day for; polish cannot rescue an unneeded product.
• Discount feedback from friends and casual users; focus on the specific target customer who has the problem and would pay to solve it.
• Test willingness to pay by asking for actual payment or a commitment, since 'ready to pay' is very different from paying and reveals real demand.
• Choose a small number of metrics expressed from the customer's perspective, such as companies with zero support tickets, and name them so people can rally around them.
• Track a 'user having a bad day' metric by logging events whenever customers hit friction, then visualize these reasons to prioritize what to fix.
• Run unnatural, fun exercises like Study Group, where employees pretend to be customers without internal knowledge, to counter the drift of internal lingo and products getting worse over time.
• Balance go-go-go urgency with long-term compounding: invest in durable infrastructure you'll never regret, while still shipping quickly to prove what's possible.

02Frameworks mentioned

Summary and takeaways written by PM Atlas; quotes are short excerpts. © the original author.