Finding Product-Market Fit as a Solo Developer

Product-market fit. The term gets thrown around constantly, but most advice assumes you have a team of 10, a runway of 18 months, and a data science person to crunch numbers. What if you're one developer with a side project and a dream?

The principles of PMF still apply. The tactics need to be adapted. Here's how.

What PMF Actually Means for Solo Devs

Andy Rachleff, who coined the term, defined it simply: "being in a good market with a product that can satisfy that market." For a solo developer, this translates to:

• A specific group of people with a painful problem (the market)
• Your product solves that problem well enough that they'd be upset to lose it (the fit)

You don't need hockey-stick growth or VC-scale metrics. You need a core group of users who genuinely depend on your product.

The Sean Ellis Test (Adapted)

Sean Ellis popularized the benchmark: if 40% or more of your users say they'd be "very disappointed" if your product went away, you have PMF.

For a solo dev, here's how to apply this:

1. Wait until you have at least 20 active users
2. Email them: "How would you feel if [product] no longer existed? Very disappointed / Somewhat disappointed / Not disappointed / I no longer use it"
3. If fewer than 40% say "very disappointed," focus on deepening value for the users who are closest to that answer

With small numbers, the exact percentage matters less than the pattern. If even 5 out of 20 users would be very disappointed, you have a seed of PMF. Double down on what those 5 love.

The Superhuman Playbook (Solo Edition)

Rahul Vohra at Superhuman built a systematic PMF engine. Here's a simplified version for solo devs:

Step 1: Segment Your Users

Not all users are equal. Some love your product, some are lukewarm, some signed up and never came back. Focus exclusively on the ones who love it — they're your signal.

Step 2: Understand the "Very Disappointed" Users

Ask them: "What is the main benefit you get from [product]?" Their answers reveal your true value proposition — which might be different from what you think you built.

Step 3: Find More of Them

Now that you know what your best users love and who they are, find more people who match that profile. This is where your community map comes in — where do people like your best users hang out?

Step 4: Convert the "Somewhat Disappointed" Users

Ask them: "What would make you 'very disappointed' to lose this?" Their answers are your roadmap. Each feature or improvement that moves a user from "somewhat" to "very" disappointed strengthens your PMF.

Signals That You're Getting Close

PMF doesn't arrive as a single moment of revelation. Watch for these progressive signals:

• Organic word-of-mouth: Users telling others without you asking
• Unsolicited feature requests: People care enough to want more
• Low churn: People stick around month after month
• Willingness to pay more: When you raise prices, nobody leaves
• Users building workflows around your tool: It's become embedded in their daily process
• Support requests from people trying to sign up: Demand exceeding your onboarding capacity

The Solo Dev PMF Loop

1. Find 5 users who love what you built (even if 100 others are indifferent)
2. Understand why those 5 love it (their words, not your assumptions)
3. Find 5 more who match the same profile
4. Improve the product based on what your best users need
5. Repeat until "very disappointed" users outnumber the rest

This loop works whether you have 20 users or 200. The scale is different from a funded startup, but the principle is the same: find the people who love you, understand why, and find more of them.

When You Don't Have PMF Yet

If you can't find even 5 users who love your product, the issue is usually one of:

• Wrong audience: You're reaching people who don't have the problem
• Wrong problem: The problem isn't painful enough to drive adoption
• Wrong solution: Your approach to solving the problem doesn't resonate

Diagnosing which one requires honest conversations with the people who tried your product and left. Their reasons for leaving are more valuable than your reasons for building.