How to Find Product-Market Fit Without Funding: The Bootstrapper's Playbook

To find product-market fit without funding, pick a narrow niche with an expensive, recurring problem you can reach without ads, sell a paid pilot before you build much, deliver the smallest paid version by hand if you have to, and watch whether paying users keep coming back. Once enough active users have experienced the product, run the Sean Ellis survey and aim for at least 40% saying they would be very disappointed without it. Scale channels only after retention is real.

Editorial title card reading "How to Find Product-Market Fit Without Funding" beside the orange ZeroRaised mark.

Key takeaways

  • Marc Andreessen defines product/market fit as being in a good market with a product that can satisfy that market. Without it, customers get little value and word of mouth does not spread.
  • Sean Ellis's survey asks how users would feel if they could no longer use the product. After benchmarking nearly a hundred startups, he found the magic number was 40% answering 'very disappointed'.
  • Without funding the order changes: money from customers comes first, retention second, and scaling channels last, because you cannot pay to grow your way out of a weak product.
  • Run the survey only on active users who have used the core feature recently. Under 40% is a signal to tighten your ideal customer and core value, not a grade to hide.
  • Treat paid ads as the last channel, not the first. Founder-led sales, communities and referrals from retained users come before any ad spend.
On this page 53
  1. TL;DR
  2. What is product-market fit, according to Marc Andreessen?
  3. Product-market fit is not a single moment
  4. How do you measure product-market fit? The Sean Ellis 40% test
  5. The question
  6. The 40% threshold
  7. The free tool
  8. Why does having no funding change the sequence?
  9. How is this different from validating an idea or getting your first customers?
  10. Step 1: Pick a narrow niche with an expensive, recurring problem
  11. Write a one-line niche statement
  12. Why narrow is safer, not riskier
  13. Step 2: Run problem interviews about past behaviour
  14. Ask about the past, not the future
  15. Listen for the words they use
  16. Know when to stop
  17. Step 3: Pre-sell or run a paid pilot before the big build
  18. What to offer
  19. First paying customers matter more than waitlist size
  20. Step 4: Ship the smallest paid version and win your first paid users
  21. Deliver manually where you can
  22. Turn pilots into paid users
  23. Write down why each customer bought
  24. Step 5: Prove retention before you scale
  25. What retention means at this stage
  26. Define your core action
  27. Measure retention in a spreadsheet
  28. What good looks like
  29. Why scale has to wait
  30. Step 6: Run the Sean Ellis survey at the right time
  31. When to run it
  32. Who to survey (and who not to)
  33. The questions to ask
  34. How to read the results
  35. What to do if you score under 40%
  36. What if you score over 40%?
  37. Step 7: Sequence your channels: paid ads come last
  38. The bootstrapped channel order
  39. Why paid ads usually come last without funding
  40. One channel at a time
  41. Signs you have (or do not have) product-market fit
  42. A worked example: one bootstrapped path to PMF
  43. What mistakes stop bootstrappers from finding product-market fit?
  44. The 90-day checklist to find product-market fit without funding
  45. Checklist
  46. Where ZeroRaised fits
  47. Frequently asked questions
  48. Can you find product-market fit without funding?
  49. What is the Sean Ellis 40% test?
  50. When should I run a product-market fit survey?
  51. How do I know if I have product-market fit as a bootstrapper?
  52. Should I spend on ads before product-market fit?
  53. Sources

To find product-market fit without funding, pick a narrow niche with an expensive, recurring problem you can reach without ads. Sell a paid pilot before you build much, deliver the smallest paid version (by hand if you have to), and watch whether paying users keep coming back. Once enough active users have experienced the product, run the Sean Ellis survey and aim for at least 40% saying they would be "very disappointed" without it. Scale channels only after retention is real.

That is the short version. The rest of this guide explains why bootstrapping changes the order of the work, what product-market fit actually means, how to run and read the 40% survey, how to measure retention with a spreadsheet, which channels to add and when, the mistakes that waste a year, and a 90-day checklist you can start on Monday. The definitions come from Marc Andreessen and Sean Ellis, checked on 7 Nov 2026. The playbook in between is ours.

TL;DR#

  • Know the definition. Marc Andreessen writes that product/market fit means "being in a good market with a product that can satisfy that market" (pmarchive). When you have it, customers buy, use and tell others. When you do not, they get little value and word of mouth stalls.
  • Know the measurement. Sean Ellis's survey asks: "How would you feel if you could no longer use the product?" After benchmarking nearly a hundred startups, he found "the magic number for product/market fit was 40%" answering "very disappointed" (PMFsurvey).
  • No funding changes the order. A funded startup can buy users and look for fit at the same time. A bootstrapper has to get paid first, prove retention second, and spend on growth last.
  • Retention before scale. Paying users who stay, and keep using the product, are the strongest early evidence. Growth on top of a leaky product just churns faster.
  • Survey at the right time. Ask active users who have used the core of the product more than once. Under 40% means tighten the customer and the core value; it is not a score to hide.
  • Ads come last. Founder-led sales, communities and referrals from retained customers come first. Paid acquisition is the final channel, once you know customers stay.

Disclosure: ZeroRaised publishes this guide and runs a launch site for bootstrapped products. Definitions and survey details are quoted from the linked sources as checked on 7 Nov 2026. ZeroRaised has no commercial relationship with Sean Ellis, GoPractice, PostHog or any other company named here, and no links in this post are affiliate links.

Product-market fit (PMF) is the point at which a product satisfies a strong demand in a good market well enough that customers buy it, keep using it and recommend it, so growth starts to come from the market pulling the product rather than the founder pushing it.

What is product-market fit, according to Marc Andreessen?#

The phrase most founders use comes from Marc Andreessen's essay "The only thing that matters", part of his guide to startups. His definition is short: "Product/market fit means being in a good market with a product that can satisfy that market" (pmarchive).

Two things in that sentence matter for a bootstrapper.

  1. The market comes first. Andreessen's argument is that the market is the most important factor in a startup's success. A good market with real, urgent demand will pull a decent product forward. A weak market will not save a great product.
  2. "Satisfy" is a high bar. It does not mean people say they like it. It means the product does the job well enough that they pay for it, rely on it and would miss it.

Andreessen also describes what the two states feel like from the inside. When you do not have fit, customers are not getting much value from the product and word of mouth is not spreading. When you do have it, customers are buying the product, using it and telling others about it (pmarchive).

Our read: that description was written with venture-backed startups in mind, where meeting demand can mean hiring sales teams and buying servers. For a solo founder or a team of two, the same feeling shows up at a smaller scale. You stop chasing every customer. Some arrive on their own. Your support inbox fills with "can it also do X?" rather than "how do I cancel?". The difference is pull versus push, and you can feel it with ten customers just as well as with ten thousand.

Product-market fit is not a single moment#

Founders often talk about "finding" PMF as if it is a door you walk through once. In practice it is a range. You can have strong fit with one narrow segment and weak fit with everyone else. You can have it for one use case and not for the three features you added later. You can have it and lose it when a competitor ships something better or the market shifts.

That is useful news for bootstrappers. You do not need to find fit with "small businesses". You need to find it with, say, independent physiotherapy clinics that run two to five practitioners and still book appointments by phone. Narrow fit is real fit. You can widen it later from a position of revenue.

How do you measure product-market fit? The Sean Ellis 40% test#

Andreessen's definition tells you what PMF is. It does not give you a number. The most widely used number comes from Sean Ellis, whose product/market fit survey is now available as a free tool at PMFsurvey.

The question#

The survey is built around one question (PMFsurvey):

"How would you feel if you could no longer use the product?"

You then measure the percentage of respondents who answer "very disappointed". That share is the leading indicator. It is a leading indicator because it shows up before revenue curves and growth charts do: people who would be very disappointed to lose a product tend to keep paying for it and tell others about it.

The 40% threshold#

According to PMFsurvey, after benchmarking nearly a hundred startups, "the magic number for product/market fit was 40%." Companies that struggled to find growth almost always had less than 40% of users saying "very disappointed". Companies with strong traction almost always exceeded that threshold (PMFsurvey).

Note what that does and does not say. It is a benchmark from a set of startups, used as a rule of thumb. It is not a law of physics, and the source does not claim that every company above 40% succeeds or that every company below it fails. It says that struggling companies "almost always" scored lower and companies with strong traction "almost always" scored higher.

Our read: treat 40% as a direction, not a finish line. If you score 25%, you have work to do on who the product is for and what it does best. If you score 45% from twelve respondents, you have a good sign, but not enough data to bet your savings on. In both cases, the follow-up questions (covered below) teach you more than the headline number.

The free tool#

PMFsurvey offers a free tool, built by Sean Ellis and GoPractice, to run the survey (PMFsurvey). You can also run the same question in any survey tool you already use. If you have product analytics in place, PostHog's free plan included 1,500 survey responses a month when we checked on 7 Nov 2026 (PostHog pricing), which is more than a bootstrapped product at this stage will need.

The tool matters much less than who you ask and when. We cover that in Step 6.

Why does having no funding change the sequence?#

A venture-backed startup and a bootstrapped one are both searching for the same thing. They search in a different order, because they are paying for the search in different ways.

A funded team has runway it did not earn. It can give the product away, buy users with ads, hire before revenue and run experiments in parallel, accepting that most of them will fail. It is buying time and reach with investor money while it looks for fit.

A bootstrapper pays for every week of the search with savings, a day job or customer revenue. That changes three things:

  1. Revenue is part of the evidence, not a later stage. A funded team can find fit with free users and charge later. A bootstrapper needs customers to pay early, both to survive and because payment is the one signal that is hard to fake.
  2. You cannot run many experiments at once. You have one founder's attention, maybe two. So you narrow the niche hard and test one offer at a time.
  3. You cannot pay your way past a weak product. Ads, sponsored posts and paid acquisition multiply whatever the product already does. If customers churn, spending on growth just loses money faster.

Here is how the two sequences compare.

StageTypical venture-funded orderBootstrapped order (our recommendation)
1Build a broad product for a big marketPick a narrow niche you can reach without ads
2Acquire free users quickly, often with spendInterview about past behaviour, then pre-sell
3Measure engagement, look for fitDeliver the smallest paid version, by hand if needed
4Monetise once usage is strongProve retention and repeat use among payers
5Scale paid channelsRun the Sean Ellis survey on active users
6Hire to growAdd channels one at a time; paid ads last

The funded sequence is not wrong. It is just a strategy that depends on money you do not have. The bootstrapped sequence trades speed for survival: it is slower to reach a large audience, but each step pays for, or at least informs, the next.

Our read: the biggest mistake we see from first-time bootstrappers is copying the funded sequence without the funding. They build a broad free product, launch to a big spike, watch most of it leave, and only then try to charge. By that point they have spent their savings on a product they cannot tell is wanted.

How is this different from validating an idea or getting your first customers?#

ZeroRaised already has two guides that sit next to this one. They answer different questions.

  • How to validate a SaaS idea before building is about the pre-build stage: is this problem real, and will anyone pay to solve it? Its output is a go or no-go decision on building.
  • How to get your first 10 paying customers is about sales tactics: who to contact, what to say and how to close the first handful of deals.
  • This guide is about what comes after and around those steps: once you have, or can get, paying users, how do you tell whether you have product-market fit, how do you measure it, and what do you do until retention and repeat purchase are real?

Put simply, validation tells you the problem is worth solving. First customers tell you someone will pay. Product-market fit tells you they stay, they rely on it, and the market starts pulling. You can have the first two without the third, and many products do. That gap is where most bootstrapped products quietly stall.

Step 1: Pick a narrow niche with an expensive, recurring problem#

The niche is the single biggest lever you control. Get it right and every later step is easier. Get it wrong and no amount of feature work will rescue the numbers.

Look for a niche with four properties:

  1. The problem is expensive. It costs the customer money, staff time, lost revenue or risk. Expensive problems have budgets, and budgets mean people can say yes without a committee.
  2. The problem recurs. It happens every week or every month, not once a year. Recurring problems support recurring revenue, and they give you something to measure: does the customer come back each time the problem appears?
  3. You can reach the buyers without ads. You know where they gather: a forum, a trade association, a Slack group, a subreddit, a newsletter, your own former colleagues. If the only way to reach them is paid search, you have chosen a channel before you have chosen a product.
  4. The buyers are similar to each other. Same job, same tools, same size, same workarounds. Similarity is what lets a small product satisfy them well. A product built for "agencies" serves nobody brilliantly; a product built for two-person Webflow agencies that bill per project can.

Write a one-line niche statement#

Before you move on, write one sentence in this shape:

"[Specific customer] spends [time or money] every [period] on [problem], and today they solve it with [current workaround]."

For example (illustrative): "Two-to-five practitioner physiotherapy clinics spend several hours a week confirming and rescheduling appointments by phone, and today they use a receptionist and a paper diary."

If you cannot fill in the current workaround, you probably have not found a real problem yet. If you cannot name where these people gather, you probably cannot reach them without funding.

Why narrow is safer, not riskier#

Narrow feels risky because the market looks small. For a bootstrapper, it is the opposite. A narrow niche means:

  • Fewer competitors who have bothered to serve it well
  • A shorter list of people to talk to, so you can actually talk to most of them
  • Word of mouth that travels faster, because the buyers know each other
  • A clearer survey signal, because responses are not diluted by people the product was never for

You can widen later. Widening from a base of retained, paying customers is far easier than narrowing from a broad product that nobody loves.

Step 2: Run problem interviews about past behaviour#

Interviews are where you learn whether your niche statement is true, and how customers describe the problem in their own words. They are covered in depth in our guide to running customer discovery interviews. Here is the part that matters for PMF.

Ask about the past, not the future#

People are poor predictors of their own future behaviour and generous with compliments. So skip the hypotheticals:

  • Avoid: "Would you use a tool that did X?" and "How much would you pay for Y?"
  • Ask instead: "Tell me about the last time this happened." "What did you do?" "How long did it take?" "What did it cost?" "What have you tried to fix it?" "What did you stop using, and why?"

Past behaviour shows you three things a pitch never will: how often the problem really occurs, how much they already spend on it, and whether they have tried to solve it before. Someone who has tried three tools and a spreadsheet is a much stronger prospect than someone who says the idea "sounds great".

Listen for the words they use#

Write down exact phrases. The way customers describe the problem becomes your landing page headline, your onboarding copy and, later, the answer options you read in survey responses. When the language in your survey's open answers matches the language in your early interviews, you are probably talking to the right people.

Know when to stop#

Stop interviewing a segment when you stop hearing new things. If the same three pains come up again and again, you have enough to write an offer. If every interview surfaces a different problem, your niche is too broad, or the problem is not as shared as you thought. Narrow and try again.

Step 3: Pre-sell or run a paid pilot before the big build#

This is where bootstrapping diverges most sharply from the funded playbook. Instead of building and hoping, you ask for money while the product is still small or not yet built.

A pre-sale or paid pilot is the cheapest strong signal you can buy. A waitlist sign-up costs the customer nothing. A deposit, a pre-order or a paid pilot costs them something real, which is exactly why it tells you something real.

What to offer#

Write a one-page offer:

  • Who it is for. Your niche statement, in their words.
  • The outcome. What changes for them, stated as a result, not a feature list.
  • What version one includes. Be specific and modest.
  • The price. A founding price is fine; free is not.
  • The delivery date. And what happens if you miss it (a refund is the honest answer).

Then ask the people you interviewed, starting with those who described the problem most painfully. Our guide on how to bootstrap a SaaS covers payment links, merchants of record and setting a validation threshold before you start.

First paying customers matter more than waitlist size#

A waitlist of 2,000 people is a marketing asset. It is not evidence of product-market fit. Five customers who paid before the product existed are worth more to a bootstrapper than that list, because:

  • They have already crossed the hardest line: deciding to pay
  • They will use the product, so you learn from real behaviour
  • They have a stake in it working, so they give honest feedback
  • Their money funds the next weeks of building

Our read: if nobody will pay a deposit or a pilot fee, do not build the full product to "see if it works". Change the customer, the problem, the offer or the price and ask again. Building the full product is the most expensive possible way to learn the same lesson.

Step 4: Ship the smallest paid version and win your first paid users#

Once a few people have paid, build the smallest thing that delivers the outcome you sold. Not the roadmap. Not version two. The outcome.

Deliver manually where you can#

At this stage, a lot of what looks like "product" can be you. Onboarding can be a call. Data imports can be you with a spreadsheet. Reports can be generated by a script you run on Monday mornings. This is not cheating; it is how you learn which parts of the job matter enough to automate.

Doing the work by hand has a second benefit for PMF: you see exactly where customers get value and where they get stuck. You cannot get that from a dashboard with ten users.

Turn pilots into paid users#

The first paid users usually come from three places, in this order:

  1. People who paid a deposit or pilot fee in Step 3
  2. Interviewees who did not pay before, but see a working product now
  3. Warm introductions from those first users to people with the same problem

Our guide to getting your first 10 paying customers covers outreach messages, follow-ups and closing. For PMF purposes, what matters is that these first users are inside your niche. Ten paying customers from ten different industries tell you much less than ten from the same one.

Write down why each customer bought#

For every paying customer, record three things in a simple sheet:

  • What problem they said they were solving
  • What nearly stopped them from buying
  • Where they came from

After ten customers, patterns appear. If most bought for the same reason, that reason is your core value. If they bought for ten different reasons, you have ten small markets and no fit with any of them yet.

Step 5: Prove retention before you scale#

This is the step most guides skip and most bootstrappers rush. Getting paid once proves a customer was willing to try. Getting paid again, and seeing the product used again, is what starts to prove fit.

What retention means at this stage#

Retention has two parts. Track both.

  • Revenue retention: do paying customers keep paying? For a monthly subscription, that means renewals. For a usage-based or one-off product, it means repeat purchases.
  • Usage retention: do customers keep doing the core job in the product? A customer who pays but never logs in is about to churn; they just have not noticed the charge yet.

Usage often moves first. A customer who stops using the core feature in month two will usually cancel in month three or four. Watching usage gives you time to call them before the cancellation arrives.

Define your core action#

Pick the one action that means the customer got value. Not "logged in". Something closer to the outcome:

  • An invoicing tool: an invoice sent
  • A scheduling tool: an appointment booked through it
  • An analytics tool: a report viewed, or a weekly email opened
  • A content tool: a piece published

Then define how often that action should happen for a healthy customer, based on how often the problem recurs. A weekly problem should produce weekly use. A monthly problem should produce monthly use.

Measure retention in a spreadsheet#

You do not need a product analytics platform for your first twenty customers. A sheet is enough:

CustomerStartedMonth 1Month 2Month 3Month 4Notes
Customer AJulPaid, activePaid, activePaid, activePaid, activeUses weekly report every Monday
Customer BJulPaid, activePaid, low useCancelled-Said the import was too slow
Customer CAugPaid, activePaid, activePaid, active-Referred Customer F

Illustrative example. Not real customers.

Group customers by the month they started (a "cohort") and look at each cohort over time. Once you have more customers, a product analytics tool can do this automatically, and our guide on reducing SaaS churn covers collecting cancellation reasons and fixing the common causes.

What good looks like#

We are not going to give you a retention percentage to hit, because we have not found a primary source for a universal benchmark that we would trust across niches, price points and billing models. What you can look for is shape:

  • A curve that flattens. Every cohort loses some customers early. The question is whether the line levels off. If a group of customers is still paying and using the product after several months, you have found people the product genuinely satisfies.
  • Later cohorts that do as well or better. If customers who started in September stay longer than those who started in July, your product and onboarding are improving.
  • Cancellation reasons that cluster outside your niche. If the customers who leave are mostly ones you would not target again, that is a niche problem you can fix by being stricter about who you sell to.

A curve that keeps falling towards zero, cohort after cohort, means you do not yet have fit, however good the sign-up numbers look.

Why scale has to wait#

Every growth channel you add after this point pours more people into the top of your funnel. If the bottom leaks, you pay (in time or money) for every person who falls through. Funded companies can sometimes afford to grow and fix retention at the same time. Bootstrappers usually cannot.

Our read: if you are tempted to launch everywhere before retention is clear, ask what you will learn from it. A launch is excellent for getting a burst of new users to test retention on. It is a poor substitute for retention itself.

Step 6: Run the Sean Ellis survey at the right time#

The survey is most useful once you have users who can answer it honestly. Ask too early, or ask the wrong people, and the number will mislead you.

When to run it#

Run the survey when all of these are true:

  1. You have active users who have used the core of the product recently, not just people who signed up.
  2. They have experienced the core value more than once. One use is a trial. Several uses, over at least a few cycles of the problem, is an experience they can judge.
  3. You have enough of them to see a pattern. With a handful of respondents, one person changes the percentage dramatically. Treat small samples as qualitative feedback and keep collecting.

For a bootstrapped SaaS, that usually means after you have paying users who have been through a few renewal periods or a few dozen uses of the core feature. For a consumer app with a free tier, it means users who have come back on several separate days.

Who to survey (and who not to)#

  • Include: active users inside your target niche who have used the core feature recently.
  • Exclude: people who signed up and never activated, people outside your niche, your friends and family, and anyone you onboarded as a favour.
  • Segment, do not discard: if you have multiple customer types, tag responses so you can see each group's score separately.

Surveying everyone who ever signed up drags the score down with people who never experienced the product. Surveying only your biggest fans inflates it. Neither tells you anything useful.

The questions to ask#

The core question comes from PMFsurvey: "How would you feel if you could no longer use the product?" with "very disappointed" as the answer you measure (PMFsurvey). Keep the headline question exactly as written, so your results are comparable over time.

Then add a few short, open follow-ups. These are our suggestions, and they are where most of the learning comes from:

  • "What type of person do you think would benefit most from this product?"
  • "What is the main benefit you get from it?"
  • "What would you use instead if this product were no longer available?"
  • "How could we improve it for you?"

How to read the results#

  1. Calculate the headline. Very disappointed responses divided by total responses from your filtered group.
  2. Read the "very disappointed" group closely. Who are they? What do they say the main benefit is? This group is your real ideal customer, and their words describe your real core value.
  3. Compare with the "somewhat disappointed" group. These are people who like the product but could live without it. What stops them loving it? Often it is one missing piece, or a benefit they have not discovered.
  4. Look at the alternatives. If "very disappointed" users name a spreadsheet or "nothing", you are solving a problem nobody else is. If they name a strong competitor, your fit may be narrower than it looks.
  5. Re-run it. One survey is a snapshot. Running it every quarter, on the same type of active users, shows whether you are getting closer.

What to do if you score under 40%#

Under 40% is common, and it is a signal to act on, not a vanity score to bury. Our recommended responses, in order:

  1. Recalculate for your best segment. Filter responses down to the customer type that matches the "very disappointed" group. If that segment is above 40%, you may already have fit with a narrower market. Focus on it.
  2. Tighten your ideal customer profile. Stop selling to segments that score low. Rewrite your landing page and outreach for the segment that scores highest.
  3. Double down on the main benefit. Take the benefit that "very disappointed" users name most often and make it faster, clearer and more central in onboarding.
  4. Fix what holds back "somewhat disappointed" users who match your best segment. Ignore requests from people outside it.
  5. Survey again after the changes have had time to reach users.

What not to do: add a long list of features in the hope that something sticks. That usually spreads the product thinner and lowers the score further.

What if you score over 40%?#

Good. Check that the number is not flattered by a tiny sample or a biased group, then check that retention agrees with it. If people say they would be very disappointed but your cohort curves keep falling, trust the behaviour over the survey. If both point the same way, you have earned the right to start scaling channels.

Step 7: Sequence your channels: paid ads come last#

Once retention is real and the survey supports it, growth becomes the job. Without funding, the order in which you add channels matters as much as the channels themselves.

The bootstrapped channel order#

OrderChannelWhy it comes hereWhat it costs
1Founder-led sales and direct outreachYou learn the most per conversation, and it works with a tiny audienceYour time
2Communities where your niche gathersNarrow niches cluster; helpful answers compoundYour time, plus patience with each space's rules
3Referrals and word of mouth from retained customersOnly works once people love the product; a strong PMF signal in itselfAccount credit or thank-yous
4Launches on directories and launch sitesA burst of new users to test onboarding and retention onA day or two of preparation
5Content and SEOCompounds over months if your buyers search for the problem by nameSteady writing time
6Partnerships and integrationsPuts you inside tools your niche already usesBuild time, then upkeep
7Paid adsMultiplies a product that already retains; only affordable once you know customer valueCash, plus your time to manage it

This is our recommendation, not a fixed law. A product for developers might get more from content or a launch earlier. A high-priced B2B tool might stay on founder-led sales for a long time. The principle holds: channels that cost time and teach you something come before channels that cost cash and teach you less.

Why paid ads usually come last without funding#

Paid acquisition is not bad. It is just the channel that punishes weak product-market fit hardest. You pay for every click whether or not the person stays. Until you know how long a customer stays and how much they pay over that time, you cannot know what you can afford to spend to get one.

Before you test ads, you should be able to answer:

  • What share of new paying customers are still paying after a few months?
  • What does an average customer pay you over their lifetime, roughly?
  • Which customer segment retains best, so you can target it?

If you cannot answer those, the ad spend is a guess. Bootstrappers cannot afford many expensive guesses.

One channel at a time#

Add channels one at a time, and give each one enough weeks to show a result before you judge it. Splitting a few hours a week across six channels usually produces nothing measurable in any of them. Track where every new paying customer came from, so you know which channel actually works rather than which one feels busy.

When you are ready to launch, our product launch checklist for bootstrapped makers covers preparation, listings and follow-up.

Signs you have (or do not have) product-market fit#

Andreessen's description of the two states is the best quick test we know (pmarchive). Here is how it translates for a small, self-funded product, using our own interpretation.

Signals you are getting close:

  • Customers pay without heavy discounting or long persuasion
  • Paying customers keep paying, and your cohort curves flatten
  • Customers use the core feature as often as the problem recurs
  • New customers mention a friend, colleague or community post you did not create
  • Support requests shift from "how do I" and "why did this break" to "can it also"
  • At least 40% of active, in-niche users say they would be very disappointed without the product
  • You have to choose which customer requests to say no to, because there are more than you can build

Signals you are not there yet:

  • Each sale needs a long call, a discount and several follow-ups
  • Customers churn after the first or second billing period
  • Usage drops after the first week, even among people who pay
  • Every new customer comes from your own outreach; nobody arrives on their own
  • Survey respondents describe the main benefit in many different ways
  • Launch days bring spikes that fade back to the same baseline

No single signal is enough. A big launch can look like pull for a week. A few loyal customers can hide a niche that is too small to support you. Look for several signals pointing the same way.

A worked example: one bootstrapped path to PMF#

Illustrative example. This is a hypothetical product, built to show how the steps fit together. The numbers are invented for the example and are not benchmarks.

A solo founder who used to work in a physiotherapy clinic notices that small clinics lose hours each week to phone-based rescheduling.

  1. Niche. They write: "Independent physio clinics with two to five practitioners spend hours a week rescheduling by phone, and today they use a receptionist and a paper diary." They know three local clinic owners and a regional association newsletter.
  2. Interviews. They interview twelve clinic owners about the last week of rescheduling. Most describe the same pain: late-night cancellations that leave empty slots. Several have tried a general booking tool and dropped it because patients found it confusing.
  3. Pre-sell. They offer a three-month paid pilot at a founding price for an SMS-based rebooking service, delivered partly by hand. Four clinics pay.
  4. First paid users. The founder sends rebooking messages using a simple script and a shared inbox, and fills cancelled slots manually for the first weeks. Two more clinics join through referrals from the first four.
  5. Retention. After three months, five of the six clinics renew. The one that leaves is a larger clinic with its own front desk team, outside the niche. All five remaining clinics use the service every week.
  6. Survey. With only six customers, the founder surveys each practitioner and receptionist who uses it, not just the owners. Most say they would be very disappointed without it, and nearly all name "filling cancelled slots" as the main benefit. The sample is too small to trust the percentage, but the language is consistent.
  7. Channels. The founder writes a short case study for the association newsletter, asks happy clinics for one introduction each, and only then lists the product on launch sites. Paid ads stay off the plan until a few more cohorts have renewed.

Notice what the founder did not do: build a general booking platform, launch it to the world, offer it free, or buy ads. Each step was small, paid for itself or nearly did, and produced evidence for the next decision.

What mistakes stop bootstrappers from finding product-market fit?#

  1. Copying the funded playbook without the funding. A broad free product with a big launch and monetisation "later" depends on runway you do not have.
  2. Treating a waitlist as proof. Sign-ups cost nothing. Payments and repeat use are the evidence.
  3. Choosing a niche you cannot reach. If the only route to customers is paid search, you have made ads your first channel by accident.
  4. Asking hypothetical questions. "Would you use this?" invites polite yeses. Ask what people did last time.
  5. Building the full product before anyone pays. Pre-sell or pilot first. Change the offer if nobody pays.
  6. Selling to everyone who will say yes. Early revenue from outside your niche feels good and muddies every signal, from retention to survey scores.
  7. Measuring sign-ups instead of retention. Sign-ups tell you about marketing. Retention tells you about the product.
  8. Running the survey too early, or on the wrong people. Ask active, in-niche users who have experienced the core value. Exclude people who never activated.
  9. Hiding a low survey score. Under 40% is information. Use the follow-up answers to find the segment and benefit to focus on.
  10. Adding features to fix weak fit. More features usually spread a product thinner. Tighten the customer and the core value first.
  11. Scaling channels before retention is real. More users into a leaky product is a faster way to burn savings.
  12. Starting with paid ads. Ads come last for bootstrappers, once you know how long customers stay and what they are worth.
  13. Confusing a launch spike with pull. Watch the baseline in the weeks after a launch, not the peak on the day.
  14. Quitting the day job on hope. Wait until revenue or a written runway plan supports it. Our bootstrapping guide covers the ramen profitability test.

The 90-day checklist to find product-market fit without funding#

This plan assumes a solo founder or a pair with roughly 10 to 15 hours a week. If you already have paying users, start at the week that matches where you are. If you have more time, compress it; do not skip the payment and retention steps.

WeeksFocusOutputDone when
1 to 2Niche and reachOne-line niche statement; list of 30 to 50 reachable target customers; 3 places they gatherYou can name the workaround they use today and where to find them
3 to 4Problem interviews10 to 20 interviews about past behaviour; exact phrases recordedThe same few pains keep coming up
5 to 6Pre-sellOne-page offer with price and date; deposits or paid pilots requestedAt least a few customers have paid, or you have changed the offer and are asking again
7 to 9Smallest paid versionCore job delivered, manually where needed; first paid users onboarded personallyPaying users are doing the core action as often as the problem recurs
10 to 11Retention trackingCohort sheet with payment and core-action columns; reasons for buying and cancelling loggedYou can see whether early cohorts are still paying and using it
12Sean Ellis survey (if enough active users)Survey sent to active, in-niche users with follow-up questionsYou have a headline score and a description of the "very disappointed" group
13Decide and sequenceWritten keep, narrow or change decision; first channel chosenOne channel has a weekly target, and paid ads are explicitly parked

Checklist#

Niche and problem

  • One-line niche statement with the current workaround
  • At least three places where the niche gathers, reachable without ads
  • 10 to 20 problem interviews about past behaviour, with notes saved
  • Customers' exact phrases collected for copy and survey analysis

Paying users

  • One-page offer with outcome, scope, price and delivery date
  • Deposits, pre-orders or paid pilots requested from interviewees
  • Smallest paid version shipped, with manual delivery where it helps
  • For each customer: problem, what nearly stopped them, source

Retention

  • Core action defined, with the expected frequency
  • Cohort sheet tracking payment and core-action use each month
  • Cancellation reasons collected from everyone who leaves
  • Customers outside the niche identified and not targeted again

Measurement

  • Sean Ellis question asked exactly as written, to active in-niche users only
  • Follow-up questions on ideal user, main benefit and alternatives
  • Results segmented by customer type
  • Repeat survey scheduled for next quarter

Channels

  • Founder-led outreach and community presence running weekly
  • Retained customers asked for one introduction each
  • Launch planned only once onboarding and retention are tested
  • Paid ads parked until customer lifetime value is understood

At day 90 you should be in one of three places. You have paying users who stay and a survey that agrees, so you keep going and add a channel. You have paying users who leave, so you narrow the niche or sharpen the core value and run the cycle again. Or nobody would pay, so you pick a different problem with everything you learned. All three are progress, and none of them needed an investor.

Where ZeroRaised fits#

ZeroRaised is a launch directory for products built without institutional VC or accelerator equity. Once your retention looks real and you are adding channels, a listing is one of the free launches you can use to bring new users in to test your onboarding on. You can submit your product for free. For more guides on pricing, launching and growing without investors, join the ZeroRaised newsletter.

We do not promise traffic, sign-ups or revenue from a listing. Product-market fit comes from the work above, not from any launch site, including ours.

Frequently asked questions#

Can you find product-market fit without funding?#

Yes. Funding buys time and reach, but product-market fit comes from a product that satisfies a good market, which customers decide, not investors. Without funding you run the same search in a different order: narrow niche, paid pilots, first paying users, proof of retention, then the Sean Ellis survey, and only then broader channels.

What is the Sean Ellis 40% test?#

It is a one-question survey: "How would you feel if you could no longer use the product?" You measure the share of respondents who answer "very disappointed". Sean Ellis says that after benchmarking nearly a hundred startups, the magic number for product/market fit was 40%. Companies that struggled to grow almost always scored below it, and those with strong traction almost always scored above it. He offers a free tool with GoPractice at pmfsurvey.com.

When should I run a product-market fit survey?#

Run it once you have a group of active users who have used the core of the product recently and more than once, not on everyone who ever signed up. In a bootstrapped product that usually means after you have paying users who have been through at least a few full use cycles, such as several weekly reports or a couple of billing periods.

How do I know if I have product-market fit as a bootstrapper?#

Look for several signals together: customers pay without heavy discounts, they keep using and paying after the first few months, new customers arrive through referrals or word of mouth you did not prompt, and at least 40% of active users say they would be very disappointed without the product. One signal on its own, especially a big launch day, is not enough.

Should I spend on ads before product-market fit?#

Usually not. Ads bring people to a product, but if it does not retain them you pay to watch them leave. Without funding, put your time into founder-led sales, communities and asking retained customers for referrals first. Test ads only once retention is stable and you know what a customer is worth to you.

Sources#

Frequently asked questions

Can you find product-market fit without funding?

Yes. Funding buys time and reach, but product-market fit comes from a product that satisfies a good market, which customers decide, not investors. Without funding you run the same search in a different order: narrow niche, paid pilots, first paying users, proof of retention, then the Sean Ellis survey, and only then broader channels.

What is the Sean Ellis 40% test?

It is a one-question survey: 'How would you feel if you could no longer use the product?' You measure the share of respondents who answer 'very disappointed'. Sean Ellis says that after benchmarking nearly a hundred startups, the magic number for product/market fit was 40%. Companies that struggled to grow almost always scored below it, and those with strong traction almost always scored above it. He offers a free tool with GoPractice at pmfsurvey.com.

When should I run a product-market fit survey?

Run it once you have a group of active users who have used the core of the product recently and more than once, not on everyone who ever signed up. In a bootstrapped product that usually means after you have paying users who have been through at least a few full use cycles, such as several weekly reports or a couple of billing periods.

How do I know if I have product-market fit as a bootstrapper?

Look for several signals together: customers pay without heavy discounts, they keep using and paying after the first few months, new customers arrive through referrals or word of mouth you did not prompt, and at least 40% of active users say they would be very disappointed without the product. One signal on its own, especially a big launch day, is not enough.

Should I spend on ads before product-market fit?

Usually not. Ads bring people to a product, but if it does not retain them you pay to watch them leave. Without funding, put your time into founder-led sales, communities and asking retained customers for referrals first. Test ads only once retention is stable and you know what a customer is worth to you.