Signs You've Found Product-Market Fit as an Indie Hacker

Product-market fit is one of the most overused phrases in startup culture and one of the least explained. Founders either claim to have it before they have any revenue, or they doubt they have it even after customers are reordering and referring friends. Neither posture helps you build a better product.

At the indie hacker scale, PMF is not a moment — it is a pattern. Here is what that pattern actually looks like, and how to tell whether you are seeing it or imagining it.

What PMF Actually Means at the Indie Scale

The classic definition — “when the product satisfies a strong market demand” — is not wrong, it is just not actionable. At the venture scale, PMF often shows up as explosive growth that founders cannot fully explain. At the indie scale, it looks quieter and more specific.

For a solo founder running a micro SaaS, PMF means three things are simultaneously true. First, customers who activate keep using the product without being pushed. Second, the reasons people pay for it and the reasons you built it are the same. Third, some percentage of your customers are bothered when they imagine not having the product.

That third point is the core of Sean Ellis’s famous “40% test” — survey your users and ask what they would feel if they could no longer use your product. If more than 40% say “very disappointed,” you likely have fit. At the indie stage, you may not have enough customers to run this survey statistically. But the qualitative version — a customer who emails you unprompted to say they rely on your product — is the same signal at a smaller scale.

Notice what is not on this list: high traffic, press mentions, a big free user base, or a product that “feels” ready. Those are all easy to confuse with traction. They are not PMF.

The Real Signals You’ve Hit PMF

When genuine PMF exists, you will notice specific behaviors — not just positive feelings.

The clearest signal is pull. Customers start coming to you through channels you did not set up. Word-of-mouth referrals. Mentions in communities you are not active in. Forum posts recommending your tool that you discover by accident. You cannot manufacture this early. When it starts happening, even at a trickle — two or three referral signups per month — it means customers believe strongly enough in the product to stake their reputation on recommending it.

The second signal is retention without effort. In the early days of most indie SaaS products, founders stay engaged with free users through personal emails, Slack messages, and check-ins. When you step back and users still keep logging in, still use the product weekly, still renew — that is PMF behavior. Churn below 3% per month for a product with more than 30 paying customers is a strong indicator.

Third: customers push back on price increases less than you expect. If you raise your price from $29/month to $49/month and fewer than 15% of existing customers churn as a result, you have built something people value beyond the minimum viable alternative. Price resistance dropping is a real PMF signal.

Fourth: feature requests start clustering around depth, not breadth. Early-stage products get requests for more integrations, more use cases, more types of users. When customers who have been with you for 6 months start asking for deeper functionality within the same workflow — better reporting, more customization, advanced automation — they are telling you they are committed to the product. Breadth requests come from people trying to evaluate whether to stay. Depth requests come from people who have already decided.

False PMF Signals That Fool Founders

The signals that most reliably fool solo founders fall into three categories.

High free signups with low conversion. If 500 people signed up for your free tier last month but only 8 are paying, you do not have PMF — you have an interesting landing page and an unresolved conversion problem. Free users who do not convert are telling you either the product does not deliver on its promise or the people signing up are not your actual target customer. Both are useful information. Neither is PMF.

Enthusiastic early adopters who do not represent the mainstream. Early adopters will try almost anything, forgive rough edges, and give you glowing feedback. They are invaluable for validating the core concept. But if your paying customers are all personal connections, fellow indie hackers, or people who found you via your personal Twitter, you have not proven that a broader market wants what you built. The real test is whether strangers — people with no relationship to you — pay and stay.

Press and ProductHunt traffic spikes. A feature on a popular newsletter or a top-5 finish on Product Hunt will give you hundreds of signups and dozens of trials in a 48-hour window. This feels like validation. It is usually a sugar spike. Watch what happens to those trial users 30 days later. If conversion is below 5% and those who converted churn within 60 days, the launch event was not a PMF signal — it was exposure to the wrong audience at scale.

If you are still in the stage of trying to get people to pay at all, the article on why no one is paying for your app covers the most common reasons the first conversion never happens.

What to Do Once You Have PMF Evidence

If you are seeing two or three of the real signals described above, the right move is to stop experimenting with the core product and start compounding what is working.

Double down on the customer segment that is showing pull. Look at your last 10 referrals. Who sent them? What industry are they in? What job title? That cluster is your beachhead. Write content for them specifically, reach out to communities they are in, and price and position for them rather than for a hypothetical broader market.

Make the onboarding path match the activation behavior of your best customers. If your highest-retention customers all completed a specific workflow in the first 48 hours, your onboarding should guide every new user toward that workflow immediately. Remove steps, remove choices, and remove anything that does not lead directly to that moment.

Start collecting evidence systematically. Screenshot customer emails, save Slack messages, record which customers have been with you for 6+ months. This evidence will help you when you need to write copy, pitch partnerships, or convince a skeptical potential customer that the product is worth trying.

Understanding how to validate your app idea before building gives you a framework for catching these signals earlier in the cycle — before you have spent months building in the wrong direction.

PMF is not a finish line. It is a signal that you have found the right direction. The founders who build lasting businesses are the ones who recognize it clearly and then move fast once they see it.