Shipping 0-to-1 Inside a Big Company
Make it the customer's idea, storyboard it in Sharpie, prove it once, and show the economics
- Difficulty
- Advanced
- Time to result
- ~months to results
- Steps
- 6
- Confidence
- 92%
Weinstein's playbook for getting a new bet funded and shipped inside a large organisation, derived from taking Stripe Atlas from a modest side product to one-in-six new Delaware corporations. The core insight is that the default outcome is not rejection — it's inaction. So you remove every reason for inaction: make the idea belong to customers, make the vision cheap and vivid, make progress tangible immediately, make status self-serve via a shared metric, and make the business case explicit.
Origin
Jeff Weinstein's approach at Stripe, described in response to a former colleague's assessment that 'Jeff is really good at cutting through the BS — you hear so much about frameworks and complicated stuff in PM circles when the most straightforward obvious thing is probably right.' It converges with Mihika Kapoor's 0-to-1 advice from Figma; Weinstein's distinctive additions are 'not having things be your idea', the Sharpie constraint, and proof of existence.
Core principles
- 01The majority failure mode is that we do nothing — not that we do the wrong thing.
- 02Not having it be your idea is the most powerful position: 50 customers yelling the same thing, in their own words, is unarguable.
- 03Sharpie, not Figma. The tool's crudeness forces you to draw the unconstrained perfect solution rather than negotiate with fidelity.
- 04Proof of existence beats proof by theory or proof by debate.
- 05Ask for less permission and make each step not such a big deal; trust accrues from small shipped steps and buys you bigger bets.
- 06If everyone can see the same live metric, you don't need internal update decks and night-before scrambles — and the absence of theatre generates trust.
- 07Product quality and customer love are only half the story; you must also carry the economic argument.
How to run it
- 1
Make it the customers' idea
Arrive with the raw material: I just talked to 50 customers and they all yell the same thing — here they are in their own varieties of quotes and forms. Add three bullet points of strategy on why it matters and how it wins market share. Then it isn't your opinion to argue with.
Pro tip Bring the earliest customers physically into the room. Invite a founder to the team meeting; pipe all their feedback into a Slack channel automatically; route every NPS score to a channel and follow up directly on anything below a 10.
- 2
Storyboard the unconstrained solution in Sharpie
Draw the perfect solution to the burning problem, Pixar-style, with a Sharpie on paper — stick figures are fine. Deliberately not Figma, deliberately not high fidelity. The question is: what is the unconstrained perfect solution to this burning problem?
Pro tip You don't need to be a designer. The point is a visual that aligns people around an outcome, not a spec.
- 3
Get one thing working, once
Make tangible forward progress against the stick-figure vision immediately, with something in a browser or one crude version of one step. Do not ask for the sun and the moon in headcount to make forward progress — if you're not asking for much, who could stop you?
Pro tip Physical, undeniable artefacts are best. The blank piece of paper Stripe mailed to itself proved the entire 83(b) mechanism existed.
- 4
Make status self-serve on a live metric page
Put the shared metric somewhere everyone can look. No big internal updates, no long-winded PowerPoints, no night-before scrambles — anyone can go to the metric page and see how you're doing.
Pro tip This is what flipped internal sentiment on Atlas from 'why do we have this thing that charges companies with no money?' to people rooting for it — they could see the curves and the mission progress themselves.
- 5
Carry the economic argument
Make it explicit why the product will run in an economically viable way. If it's a customer-acquisition product, show why it's the best acquisition per dollar for the company. If it's margin/moat/ecosystem-generating, your metrics have to show that. You cannot have half the story — product quality and tweets — without the economics.
Pro tip The economic case is also what convinces the org to keep investing over the long term, which is where competitors fall away.
Watch out Skipping this is what makes 0-to-1 bets inside big companies get quietly deprioritised even when customers love them.
- 6
Only pick up work you can automate
Choose scope where you can be the only, not the best. Atlas is ten people; they deliberately do not pick up work they can't automate, because they need the leverage — so they avoid situations where they'd have to compete on effort.
In the wild
Weinstein put 83(b) elections on the team's to-do list after hearing founders terrified about it repeatedly (and having experienced it himself). There were many good reasons not to do it: huge liability, snail mail, no obvious monetisation, questionable competitive advantage. The team started with one piece of paper mailed to their own office and systematically automated each internal step over three years.
→ By the episode's launch date, starting a company on Atlas is a single click, ready for business in a day or two, with 10,000+ 83(b) elections filed 100% on time. Atlas has NPS above 80 (Apple is in the low 60s), 55,000 companies formed, and one in six new Delaware corporations.
Rather than running UXR on what should come after incorporation, the Atlas team invited founders into a Whimsical board and asked what they'd hope the dashboard would have. Founders started drawing it themselves.
→ Weinstein saw a diagram of an in-progress surface, assumed design had made it, and was told the customer drew it: 'why were we guessing?' He now argues for giving customers write access, not just read access.
Common mistakes
Presenting it as your idea
Your opinion is contestable; fifty customers saying the same thing in their own words is not. Making it your idea invites a debate you have to win, which increases the odds of the default outcome — nothing happens.
Starting in high fidelity
Going straight to Figma anchors the conversation on constraints and craft before anyone agrees on the outcome. The Sharpie is a forcing function for the unconstrained vision.
Winning on quality alone
Product quality and customer tweets are half the story. Without the economic case — why this is the best acquisition per dollar, or where the margin comes from — internal support erodes and the bet doesn't survive the long term where the compounding pays off.
Asking for a big commitment up front
The bigger the ask, the more permission is needed and the more people can stop you. Making each step small keeps momentum and earns the trust that gets you bigger bets later.
Is it for you?
Best for
A PM or product lead trying to start or scale a 0-to-1 product inside a large company with a thousand competing priorities
Not ideal for
Standalone startups with no internal politics to navigate — though the customer-idea, Sharpie and proof-of-existence steps still transfer
From the transcript
“not having things be your idea I think is really powerful like I just talked to 50 customers who all yell the same thing”
“the majority failure mode is we do nothing that's the majority failure mode”
“what is the unconstrained perfect solution to this Burning problem and that's you know Pixar style storyboard”
“existence to be an incredibly powerful proof rather than proof by Theory or proof by debate it's just like look we did it one time”
“about momentum and making each step not such a big deal and asking for Less permission”
“we don't need to do big internal updates with long- winded PowerPoint presentations and scrambles the night before you can just go to the metric…”
“you can't just have half the story of just the product quality and the tweets you have to have the economics”
From the episode
Building product at Stripe: craft, metrics, and customer obsession
Jeff Weinstein (Product lead)