❝Story16:30
Craft Is the Dessert You Get After Product-Market Fit
Jeff tells the story of his SQL analytics startup, which briefly bricked its service for 10-20 minutes. Customers barely reacted, and a year later he realized that calm was the signal they didn't have product-market fit. His lesson: no amount of craft, beauty, or delight can rescue a product people don't actually need.
- The startup accidentally shut down for 10-20 minutes and customers weren't furious, just a murmur
- Low customer anger during an outage was the tell that the product wasn't solving a burning problem
- People get out of bed for their first problem, not their second
- Craft comes only after you've confirmed people will pause their day to solve the problem
- The biggest error is polishing something that maybe shouldn't exist
“during those 20 minutes our customers weren't Furious they weren't emailing us like crazy”
“craft is kind of a dessert that you get after the meal of does your thing solve a real problem in the world”
#product-market-fit#craft#startups#customer-signal
❝Story29:30
A Customer Reaching Out Is a P0 Alert
Jeff treats the moment a busy customer bothers to report a problem as an unbelievable gift and near-emergency-level priority, dropping meetings to reply fast. He recounts an Atlas bug that handed out '25 shares' instead of '25%' of shares; a gracious founder who tweeted it became a lasting friend, ally, and document reviewer for the team.
- Reducing time-to-response turns customers into promoters and builds a secret-portal feeling
- Even a quick 'got this, hit you up tomorrow' reply delights people who didn't expect any reply
- An Atlas legal-doc bug dropped a percentage sign, granting shares instead of a share percentage
- The team fixed and regenerated docs fast; the founder offered to review docs going forward
- Fast, human handling of a serious issue can convert a potential detractor into a promoter
“that's a unbelievable gift that should be you know p0o alert level intensity”
“I will leave a meeting I will CH change what I'm doing to just get one message back to them”
#customer-support#speed#atlas#stripe
❝Story48:00
The Zero-Support-Tickets Metric That Flipped Atlas
Jeff explains how Atlas moved from unhappy support tickets to a single guiding metric: the percentage of founders who complete incorporation with zero support tickets (including a two-week buffer). Only 15% qualified at the start; over 18 months the team drove it to 85%, and market share tracked the same curve. The metric turned engineers into PMs solving one ticket at a time.
- A good metric is a numerical representation of the value delivered from the customer's perspective
- Atlas measured the percentage of founders finishing with zero support tickets, not an average
- Only 15% got through cleanly at first; 18 months later it was 85%, and market share matched
- Engineers were each assigned support-ticket topics, becoming PMs who scoped their own fixes
- A metric a customer would be thrilled to see on your dashboard is the right kind of metric
“over about 18 months we took that number from 15% to 85 uh we basically just flipped it”
“that if you by accidentally leaked your dashboard to them your customer would be ecstatic to learn that that's what you were measuring the whole…”
#metrics#atlas#product-management#stripe
❝Story1:16:30
Stripe Study Groups: Pretend You Don't Work Here
Jeff describes 'study groups', a program he started at Stripe where 4-8 random employees role-play being a made-up company (e.g. Dolphin Aquarium Industries) trying to accomplish a goal using Stripe. Two rules govern it: you no longer work at Stripe (no internal knowledge allowed), and you're not there to solve or critique, just to embody the customer. Over 250 people have joined 25+ sessions, and teams have franchised it internally.
- 4-8 employees from any role pretend to be a fictional company with a real outcome to achieve
- Rule one: you don't work at Stripe, and using any internal knowledge means redoing the step
- Rule two: no solving, critiquing, or filing bugs, just practicing customer empathy
- It's done slowly over an hour-plus so participants genuinely inhabit the customer's frustration
- 250+ people across 25+ sessions; teams adopted and franchised it with 'study group captains'
“rule one is you do no longer work at stripe you you're not you're not you do not work at stripe”
“Rule two is we're not here to solve any problems we're not here to critique we're not here to solution or suggest”
#customer-empathy#culture#stripe#product-quality
❝Story2:09:30
When AngelList Handed Atlas Its Competitor
Jeff recounts starting on Atlas the same month AngelList announced the exact same incorporation, banking, and cap-table product he wanted to build. Rather than treating them as enemies, Stripe kept an open relationship (shared Slack, discussing 83b openly). About two years later AngelList's Dan called on Jeff's wife's birthday to hand over the business and route their users to Atlas.
- AngelList launched incorporation, banking, and cap table the same month Jeff started Atlas
- Instead of guarding, Stripe kept an open relationship, even a shared Slack channel, with AngelList
- Stripe committed to the long-term compounding bet on 83b and kept building through the doubt
- AngelList later chose to exit incorporation and pointed its users to Atlas
- Lesson: alternatives aren't enemies; caring about your customer means caring about their alternatives
“he said hey we're going to get out of Incorporation this is not going to be our Focus going forward do you want the business”
“if you care about your customer you care about their Alternatives and if you care about the mission you you need to all work together”
#competition#partnerships#atlas#strategy
❝Story2:30:30
The Collison Feedback That Changed How Jeff Works
Jeff shares two pieces of formative feedback from Stripe's founders. Patrick pushed him, in his first month, to write the quarterly business review himself and rejected the first draft with 'this doesn't sound like you yet.' John delivered a gut punch: Jeff was among the best at solving problems three through 100, but needed to stay stuck on problems one and two, the hardest ones.
- Patrick made a one-month employee write the quarterly business review to force whole-business understanding
- Patrick rejected the first draft with 'this doesn't sound like you yet,' entrusting Jeff's own perspective
- John told Jeff he was great at problems 3-100 but needed to be stuck on problems 1 and 2
- Jeff had been unintentionally masking the hardest problems by being productive on everything else
- Afterward Jeff showed up only with problems one and two, which he calls phenomenal advice
“he wrote back this doesn't sound like you yet”
“you are one of the best people I've ever worked with at solving problems three through 100 but I need you stuck on problem S…”
#leadership#feedback#stripe#career