How to go from idea to your first 100 users when you are the only product manager on the team. Opinionated, direct, and framework-heavy.
7 Mental Models to Master
Everyone has ideas. Founders win by finding problems so painful that people will use a broken, ugly product just to get relief.
When you're the only PM, building the wrong thing is fatal. You don't have the runway to ship a feature, see it fail, and try again next quarter. Your first job isn't to build a solution; it's to validate that a problem actually exists.
Most early-stage founders fall in love with their idea. But as Rob Fitzpatrick writes in *The Mom Test*, you shouldn't ask people if they think your idea is good. Instead, ask them how they currently solve the problem and how much money or time they spend doing it. If they aren't actively trying to solve it today, your product won't magically make them start tomorrow.
To rigorously filter ideas, use the Problem Triage Triangle. A truly 0-to-1 worthy problem must hit all three points: it must happen frequently, it must cause significant pain, and the need to solve it must be urgent. For example, when we built Flatr, the pain of apartment hunting was high, but the urgency (leases ending) forced users to act.
Frequency × Pain × Urgency
Does this problem happen every day, week, or just once a year? Daily problems build habits.
Is it a minor annoyance or a bleeding neck? Are they actively complaining about it?
Do they need a solution today? If they can wait 6 months, you will run out of cash before they buy.
If your thesis is obvious, someone with more funding is already building it. You need a secret.
In *Zero to One*, Peter Thiel asks: 'What important truth do very few people agree with you on?' In product management terms, this is your Secret. If you're building a 0-to-1 product, you must hold a non-obvious belief about the market that incumbents have missed.
Kevin Systrom didn't just build a photo app; his secret was that people wanted their bad mobile photos to look professional instantly (hence filters). Without a secret, you are just competing on features, which is a losing game for a solo founder without a team.
Before writing a single line of code, articulate the gap between what the market believes and what you know to be true. Shreyas Doshi often points out that most products fail to carve out new space because they operate on consensus. If everyone agrees your idea is good, it's probably too late.
"Most people think X but actually Y — that gap is where our product lives"
What is the prevailing wisdom in your industry that everyone accepts as true?
What unique insight have you discovered through deep user observation that contradicts X?
How does your product exploit this gap to acquire its first hyper-passionate users?
You cannot win a 0-to-1 market by being right about something everyone else already agrees on.
Everyone knows it's true. Big tech wins here.
You know a secret the market hasn't realized yet.
Everyone believes it, but everyone is wrong.
You think you have a secret, but you're just wrong.
The biggest lie in startups is that you need an MVP. You don't. You need a hypothesis.
Founders often mistake a 'Minimum Viable Product' for a smaller, shittier version of their grand vision. But as Marty Cagan emphasizes in *INSPIRED*, your goal at this stage isn't to deliver a product; it's to discover if a product is worth delivering. Every feature you build without validation is a gamble.
Instead of a feature roadmap, operate on a risk roadmap. What is the single biggest assumption that, if false, kills your business? Test that first. Often, the smallest thing you can build to test an assumption isn't code at all—it's a landing page, a Figma prototype, or a manual concierge service.
By framing your build as a hypothesis, you separate your ego from the outcome. When Mailhub launched, they realized that getting 100 signups didn't mean 100 active users. Their acquisition hypothesis was correct, but their engagement hypothesis failed. Test the hypothesis before building the system.
Belief → Proof → Smallest Test
State your riskiest assumption clearly. (e.g., 'PMs will pay $10/mo for an AI writing tool')
Define the exact metric that validates the belief. ('10% of waitlist signs up for paid plan')
How can I test this today without coding? ('Add a Stripe checkout link to the waitlist page')
Why building "expected" features doesn't win markets. 0-to-1 products must focus on the delighters.
Users will lie to your face to be polite. Your job is to ignore what they say and watch what they do.
Product intuition isn't magic; it's calibrated observation. Early-stage founders without data science teams must rely on qualitative signals. But not all signals are created equal. Rob Fitzpatrick's core rule in *The Mom Test* is that opinions are worthless—only past behavior and actual commitment count.
When a user says, 'I would definitely use this,' that is a Level 1 signal. It feels good, but it's dangerous. You must force users up the Signal Ladder. Will they give you their email? Will they pay you today for a product that doesn't exist? Will they actually log in on day 7?
Des Traynor of Intercom notes that product instinct comes from observing the gap between intent and action. For example, at Orlog, users said they wanted comprehensive career guides, but the data showed they only ever engaged with the immediate, personality-driven test results. We built for the action, not the statement.
From polite lies to undeniable truth
Opinions, compliments, and hypothetical 'I would use this'. Dangerously misleading. Ignore.
Actual usage data. Where do they click? Where do they drop off? Actions reveal true intent.
The ultimate validation of value. A $1 transaction is worth more than 1,000 waitlist emails.
Retention. They paid, used it, and returned next week. You have found something real.
Words are cheap. Move your validation up the pyramid as quickly as possible.
RICE scoring is for PMs at Google. When you're a founder, prioritize by survival.
Complex prioritization frameworks are designed to align large teams and allocate massive budgets. When you are the only PM, they are a distraction. As Andrea Albuquerque notes in her principles of 0-to-1 PM, you shouldn't rely on spreadsheets at this stage; operate on feel and the smallest possible version of a feature.
Jason Fried and DHH argue in *Rework* that you should 'make it tiny' and 'throw less at the problem'. If a feature takes a month to build, it's too big. You are optimizing for learning speed, not feature completeness. Every week spent building in the dark increases the chance of building the wrong thing.
When evaluating what to do next, run it through a brutal, simple filter. If a task doesn't get you closer to a paying user, answer an existential question about your business, or ship within a week—drop it.
Survival-mode prioritization
Does this get us closer to one paying user? If not, why are we building it now?
Does this answer our biggest open question or validate a core assumption?
Does this take less than a week? If not, how do we cut the scope in half?
Prioritization by survival. If an idea fails any of these branches, it drops off the spine.
Gets us closer to a paying user?
Answers a core assumption?
Ships in less than a week?
Do things that don't scale. Your first 100 users must be hand-to-hand combat.
Paul Graham's legendary essay 'Do Things That Don't Scale' is the definitive guide to early distribution. You cannot rely on SEO, ads, or viral loops at day zero. As indie hackers have shared across hundreds of case studies, the consistent finding is that manual, unscalable tactics work first.
A common trap is to rely solely on a Product Hunt launch. While PH can give you a spike, data shows that community-led distribution converts significantly higher. A successful launch isn't a single event; it's chaining your wins. As one founder noted: 'When you have nothing, post on PH. When PH works, post about that on Reddit. When Reddit works, post about that on Twitter.'
Adopt a phased strategy. Phase 1 is educating your immediate network and niche communities (0-20 users). Phase 2 is agitating the problem through direct outreach and targeted content (21-50 users). Phase 3 is architecting systems that encourage word-of-mouth (51-100 users).
Chaining your wins from 0 to 100
Tap your immediate network, niche subreddits, and Slack groups. Offer white-glove onboarding.
Cold DMs, targeted emails. Find where your exact persona complains about their problem.
Share your building journey. Chain your early wins into case studies to drive organic interest.
When you have Product-Market Fit, you don't have to ask if you have it. The market pulls it out of you.
Product-Market Fit (PMF) is the only thing that matters. Marc Andreessen famously said you can always feel when PMF is happening—servers break, support queues overflow, and customers demand the product. But before the servers break, there are quantitative and qualitative signals you can measure.
Sean Ellis popularized the '40% rule': ask your users how they would feel if they could no longer use your product. If over 40% say 'very disappointed', you have PMF. Furthermore, as Lenny Rachitsky found when surveying 40+ founders, the most reliable early signal is repeating requests from users—they care enough to tell you what's missing.
The ultimate test, coined by Don Valentine of Sequoia Capital, is: 'When customers want your product so badly that you can screw everything up and still succeed.' Until you hit that point, your only job is to iterate.
5 weekly questions a founder should ask
Would 40%+ of our users be 'very disappointed' if our product disappeared tomorrow?
Is our retention curve flattening out at a healthy number, or is it trending to zero?
Are we acquiring new users through word-of-mouth without spending money on ads?
Are users demanding features faster than we can build them? Are they dragging the product out of us?
Can we acquire a user for less than the lifetime value they bring to the business?
Answers to the hardest 0-to-1 questions for early-stage founders.
0 to 1 refers to the phase of building a product from scratch—going from nothing (zero) to a functional product with its first real users (one). It requires a completely different mindset than scaling an existing product (1 to N). In 0 to 1, the focus is entirely on validating the problem, finding a wedge, and achieving product-market fit, rather than optimization or process.
Validate the problem, not the idea. Use frameworks like The Mom Test to interview potential users about their past behavior, not their future intent. Ask them how they currently solve the problem and how much money or time they spend on it. If they aren't actively trying to solve it today with a makeshift solution, they won't use your software.
A prototype is a low-fidelity mock-up (like a Figma file or a wireframe) designed to test usability and basic concepts with users quickly and cheaply. An MVP (Minimum Viable Product) is the smallest actual version of the product that delivers the core value proposition and can be used to test your riskiest business assumptions in the real world.
The first 100 users are almost always acquired through unscalable, manual methods. Founders should tap their immediate network, engage authentically in niche communities (like Reddit or Indie Hackers), and conduct direct cold outreach (DMs and emails). Relying entirely on a launch platform like Product Hunt is risky; community-led distribution and 'hand-to-hand combat' build the strongest early foundation.
Qualitatively, you can feel Product-Market Fit when the market is pulling the product out of you—users are demanding features, servers are strained, and growth happens via word-of-mouth. Quantitatively, you can measure it using the Sean Ellis test (if 40%+ of users would be 'very disappointed' without your product) and by observing a retention curve that flattens at a healthy percentage.
Created by Pranay Wankhede
Synthesized from Paul Graham, Lenny Rachitsky, Indie Hackers, and 120+ early-stage case studies.
Take the Orlog PM personality test — discover if you're The Strategy PM, The Builder PM, The Discovery PM, The Growth PM, The Operational PM, or The Founder PM.
No login required · 10–15 minutes · Free, always
Start The Experience →