Field Guide · Before Product-Market Fit ·
Before Product-Market Fit

8 Solo Founder Mistakes

Most solo founders don't fail because the code was bad. They fail in the first few months, before anyone's paid, making the same eight mistakes. Every one of them feels like progress at the time. Here's what each one looks like, how to tell if you're making it, and what to do instead.

How To Use This Page

Short on time? Take The Self-Check first and read only the ones you didn't tick. Got a discovery call this week? Read Ask This Instead before it, and paste your notes into The Prompt after.

8
Mistakes, And The Fix
12
Questions To Ask Instead
1
Prompt To Review Your Calls
Building Alone?

Every Mistake Here Feels Like Work.

Asking friends, shipping the feature someone asked for, shaving $20 off the hosting bill. It all feels productive. Most of it is Building Theater: it looks like progress and it makes $0.

The Solo Founder Lab · Opening Soon

I'm building a place where you learn to build products that work like a real company's on your own, and get them in front of people who pay, with a CTO who's built two seven-figure software companies in your corner.

Lab.exeWaitlist Open

Make Them Once. Not Eight Times.

  • Live product teardowns. Your app, your landing page and your pricing, reviewed in front of everyone.
  • Weekly CTO office hours. Live, hot-seat style. Bring the call that went sideways and we'll work out what to ask next time.
  • Launch Pad. When you launch, the room shows up.
  • The 30-Day Launch Plan. Validate, plan, build and launch, one week at a time. Members only.

Free to join the waitlist. Opens at $49/mo, and the price goes up as seats fill, so first in pays the least.

The Pattern

They All Protect You From Hearing No.

Your Only Two Jobs

Before product-market fit, a solo founder has two jobs. Find out whether enough people have a problem bad enough to pay to fix. Then find a way to reach them that you can repeat. Code is how you test the answer. It isn't the answer.

Why Smart People Make Them

Each of these mistakes swaps a scary thing for a comfortable one. Asking a stranger becomes asking your mom. A sales call becomes a demo. Finding customers becomes building features. You stay busy, and you never have to hear that the idea isn't working.

The Fix Is Boring

Talk to strangers who have the problem. Ask about their past, not your future. Pay for the stuff that makes your app feel solid. Show up in one place every week. None of it is clever. All of it works.

Progress.log✣
Feels LikeActually Gets You
"My friends love it."Politeness, not data.
Building instead of calling.Zero conversations.
"They said they'd pay."A compliment.
A great demo.Their good manners.
Shipping what they asked for.A feature nobody uses.
A $0 hosting bill.Testers who think it's broken.
Launch day.One spike, then quiet.
More features, more ads.A bigger thing nobody's pulling for.

If a week of work left you with no new facts about a customer's problem, it was the left column.

01–04 · Talking To People

Who You Ask, And What You Ask Them

The first four happen before there's much of a product. They're about the conversations: skipping them, having them with the wrong people, or asking questions that can only get you a nice answer.

01 · The Friendly JuryWho You Ask

You asked people who love you if your idea is good.

Your mom, your college roommate and your old coworker all want you to win. So they say it's a great idea, and some of them even mean it. But none of them is your customer, and none of them will tell you it's boring, too expensive or already solved by a spreadsheet. Praise from people who love you is free. As data, it's worthless.

You're Doing It If

  • Most of your "validation" came from people who'd come to your wedding.
  • The feedback is about you ("you'd be great at this"), not about their problem.
  • Nobody has said anything that made you wince.

Do This Instead

Talk to strangers who have the problem today. If friends want to help, give them a job that actually helps: introduce you to the person they know who complains about it most.

Text To A Friend

Quick favor: who's the one person you know who complains most about [the problem]? I'd love an intro. I want to ask them how they deal with it, not sell them anything.

02 · Call ShyOutreach

You won't call, email or DM anyone you don't know.

Cold outreach feels gross, so you build instead and tell yourself the product will speak for itself. It won't. Until people talk about your product, the only way anyone hears about it is you telling them. Founders who skip this end up with a nice app and an analytics dashboard showing three visitors, all of them you.

You're Doing It If

  • You've spent more hours on the logo than on talking to customers.
  • Your plan for the first users is "launch and see who shows up."
  • You've rewritten the same message three times and never sent it.

Do This Instead

Make it small and boring. Ten messages a day for two weeks, to people who have the problem. Ask for advice, not a sale, and most of the ick goes away. Pick up the phone too: almost nobody calls anymore, so a short, polite call stands out. Most people won't answer. That's normal, not a verdict. Ask, Don't Pitch has ten ways to start and twenty scripts.

03 · The HypotheticalDiscovery

You asked if they'd pay for it, and believed the yes.

"Would you pay for this?" asks about the future, for a thing that doesn't exist, of someone who'd feel bad saying no. So they say yes to be nice. It costs them nothing. Then you launch, send them the link, and they don't sign up. They weren't lying. People are just bad at predicting what they'll do, and kind when you're in front of them.

You're Doing It If

  • Your notes say "would pay $20/mo" next to names who haven't paid anything.
  • You're counting "that's cool" and "keep me posted" as interest.
  • Your questions start with "Would you…" or "If I built…"

Do This Instead

Ask about the past. What they did the last time it happened, what it cost them, and what they've already tried and paid for. Money they've already spent is the only honest answer to "would you pay." And when you want to know if they'll pay, ask them to: a pre-order, a deposit, or a paid pilot. A card number is a yes. Everything else is a maybe. More in Ask This Instead.

04 · The Demo ReflexDiscovery

Your discovery call turned into a sales pitch.

Ten minutes in, they mention a problem that sounds like your feature, and you can't help it: "Oh, we actually do that!" Now you're sharing your screen, they're being polite, and you've stopped learning. A discovery call is for finding out how their world works. The moment you start selling, they stop telling you the truth and start managing your feelings.

You're Doing It If

  • You talked for more than a third of the call.
  • You shared your screen before they told you about their week.
  • You left with "they liked it" and no new facts.

Do This Instead

Keep the product closed and let them talk for most of the call. When they say something that lines up with what you're building, don't pitch. Say "tell me more about that," and write down their exact words. Then, in the last two minutes, if it fits:

End Of The Call

This was really useful, thank you. I'm building something for exactly the problem you described. Could I show you an early version in two weeks and get your honest take?

05–06 · Building It

What You Build, And What You Run It On

These two show up once there's something to try. One is about handing your product decisions to the people you're interviewing. The other is about the first impression your app makes on a stranger.

05 · The Feature RequestProduct

You built exactly what customers asked for.

Customers are experts on their problem. They're not product designers. When someone says "it needs a dashboard" or "add a Slack integration," that's their best guess at a fix, made in ten seconds, using the tools they already know. Build every request and you end up with a junk drawer that sort of solves twenty problems and nails none. Their job is to tell you what hurts. Yours is to work out the best way to make it stop.

You're Doing It If

  • Your roadmap is a list of customer quotes.
  • You shipped a feature and the person who asked for it never used it.
  • Every new customer gets their own setting.

Do This Instead

Treat every request as a clue to a problem. Ask "what would that let you do?" and "what happens today when you can't?" until you hit the real pain. Then design the fix yourself and test it with them. If three people ask for three different features to fix the same pain, you've found the problem. None of them found the answer, and that's fine. That part's your job.

When They Ask For A Feature

Got it. If you had that tomorrow, what would you do with it? And what do you do today, when you don't have it?

06 · The $0 StackProduct

You saved $20 a month and lost your first users.

Free hobby tiers are great for building. They're terrible for the first strangers who try your product. The app goes to sleep when nobody's using it, so the first visit hangs for ages or times out. The database pauses after a quiet week. The free email plan sends your login link to spam. Your beta tester doesn't know any of that. They just think your product is broken, and they don't come back to check.

You're Doing It If

  • The first load after a quiet hour takes more than a couple of seconds.
  • You've had to tell a tester "oh, just refresh it."
  • You picked your host by what's free, not by what's fast.

Do This Instead

Before you send the link to anyone you don't know, pay for hosting that stays on, a database that doesn't pause, and email that arrives. For most early apps that's somewhere around $20 to $50 a month. One lost beta tester costs you more than a year of it. Then test it like a stranger: open it in a private window on your phone after it's been idle for an hour. The SaaS Tech Stack has what to pay for, and the Speed Audit checks the rest.

07–08 · Reaching People

How They Find It, And Whether They Want It

The last two are the expensive ones. They're what happens when the first six go unfixed: a product nobody can find, and a founder pouring more work into it anyway.

07 · Build It And They'll ComeDistribution

You have a product and no way to reach anyone.

Most solo founders spend months on the product and about an afternoon on how anyone will hear about it. But getting it in front of people is usually harder than building it, and no feature fixes that. "I'll figure out marketing after launch" tends to mean a launch post, a spike of friends, and then quiet.

You're Doing It If

  • You can't name the one place your customers spend their time.
  • Your launch plan is a single day.
  • You don't have a list of 100 people who should hear about it first.

Do This Instead

Pick one channel and show up every week, starting before the product is ready. Social media, an email list, LinkedIn, cold outreach or paid ads all work for someone. Don't try them all. Pick the one where your customers already are and you can stand doing for a year. By launch day you want an audience waiting, not a post into the void. Pick A Channel compares them.

08 · Scaling NothingFit

You're growing something nobody's pulling for.

Product-market fit is usually obvious when you have it. People sign up without you chasing them, they get annoyed when it's down, and they tell their friends. When you don't have it, that's obvious too, but it's easy to look away. So founders add features, redesign the site, hire a contractor or turn on ads. All of that makes a product nobody's pulling for a bit bigger.

You're Doing It If

  • Every customer you have, you chased personally.
  • People sign up, poke around and never come back.
  • If you turned it off tomorrow, nobody would email you.

Do This Instead

Admit where you are. Before fit, the job is to find ten people who'd be really upset to lose it, not to grow. Talk to the users who stayed and the ones who left. Narrow down to the kind of customer who uses it most, and change the product or the customer until somebody pulls. Then grow. A quick test: ask your users how they'd feel if they could no longer use it. If fewer than 40% say "very disappointed," you're not there yet.

Pick A Channel

One Channel, Every Week

Every channel works for somebody. The wrong one is the one your customers aren't on, or the one you'll quit in a month. Here's when each one fits before product-market fit.

ChannelWorks WhenWatch Out
Cold outreachEach customer is worth a lot and you can find them by name: B2B, a niche trade, local businesses.It doesn't grow on its own. It's how you get your first ten, not your first thousand.
LinkedInYour buyer has a job title, and you can write about their problem from experience.Posts about you and your launch get ignored. Posts about their problem get read.
Social videoYou can show the problem or the product in under 30 seconds, and you'll post a lot.Views aren't customers. Check that viewers look like buyers before you count it as working.
Email listYou can write something useful every week. It's the one channel nobody can take away from you.Slow to start. It needs another channel feeding it signups.
CommunitiesYour customers already hang out in a subreddit, Slack, Discord or forum, and you can be useful there.Drop links before you've helped anyone and you'll get banned.
SearchPeople already type the problem into Google or ask an AI about it.Takes months to work. Start early, alongside something faster.
Paid adsYou want to test which message gets clicks, fast, or you already know what a customer is worth.A quick way to test a headline. An expensive way to find out nobody wants it.
Pick By Where They Are

Ask the last five people you talked to where they go to learn about their work. If three say the same place, that's your channel.

Pick What You'll Keep Doing

A channel you can stand for a year beats a better one you'll quit in a month. Most channels take months before they pay off.

Start Before It's Ready

Talk about the problem in public while you build. The people who reply are your first interviews, and later, your first customers.

Ask This Instead

Questions That Get The Truth

Good discovery questions are about their life and their past, not your idea and their future. Start with the pain, get the facts, then close the loop. You won't need all twelve on one call.

1 · Find The Pain✣
"If you could wave a magic wand, what would you change about how you do this?"Lets them dream without designing. You get the outcome they want, not a feature.
"What part of it would you make go away completely?"The thing they'd delete is usually the thing they'd pay to delete.
"What's the most frustrating part?"Then stay quiet. The first answer is the polite one. The second is the real one.
"How do you handle it today?"If the answer is "we don't, really," it might not hurt enough to pay for.
2 · Get The Facts✣
"Tell me about the last time that happened."A real story beats an opinion. Ask for when, who was involved, and what broke.
"What did you do about it?"If they did nothing, it isn't a big problem yet, no matter how they talk about it.
"What have you already tried? What did you pay for it?"This is the honest version of "would you pay." Money already spent is real.
"What does it cost you when it goes wrong?"Hours, money, a lost customer, a bad review. Get a number if you can.
3 · Close The Loop✣
"Who else deals with this? Who decides what you use?"The person with the pain isn't always the person with the card.
"What would have to be true for you to switch?"Shows you what you're really up against, which is often a spreadsheet and habit.
"Is there anything I should have asked and didn't?"Some of the best answers of the whole call come from this one.
"Who else should I talk to about this?"Turns one conversation into three. Ask for an intro, not just a name.
Talk Less

Aim for them talking most of the call. If you're explaining, you're not learning.

Write Their Words

Write down exactly how they describe the problem. That's the copy for your landing page.

Don't Correct Them

If they're wrong about how something works, let it go. You're there to learn how they see it.

Let It Get Quiet

Count to five before you fill a silence. People often say the important thing right after a pause.

The Self-Check

Which Ones Are You Making?

Tick what's true today, not what you plan to do. Each one you can't tick points to a mistake above. Start with the lowest number you missed.

0 / 8

Start With The ConversationsFix 01 to 04 first. Everything else depends on talking to the right people.

Self.Check8
  • I've talked to at least 10 people with the problem, and none of them are friends or family.01 · The Friendly Jury
  • I've reached out to someone I don't know this week.02 · Call Shy
  • My last call had no "would you" or "if I built" questions in it.03 · The Hypothetical
  • On my last discovery call, I didn't show the product until the end, if at all.04 · The Demo Reflex
  • I can name the problem behind every feature on my roadmap.05 · The Feature Request
  • My app loads fast on a phone after it's been idle for an hour.06 · The $0 Stack
  • There's one channel I show up on every week.07 · Build It And They'll Come
  • A few people would be really upset if my product disappeared tomorrow.08 · Scaling Nothing
The Prompt

Have Claude Review Your Last Call

Most of these mistakes are invisible while you're making them. Paste your notes or the transcript from a discovery call into Claude, ChatGPT or whatever you use, under this prompt. It tells you where you pitched, what you actually learned, and what to ask next time.

Call.Review.Prompt
You're reviewing a discovery call for a solo founder who hasn't found product-market fit yet. I'm building [WHAT YOU'RE BUILDING, in a sentence] for [WHO IT'S FOR]. The person I talked to is [THEIR ROLE, and how I found them].

Be honest, not encouraging. I'd rather hear it from you than from my bank account.

Review the call below for these mistakes, and quote the exact lines:
1. Hypothetical questions: anything like "would you", "if I built" or "would you pay".
2. Pitching: where I described, demoed or defended my product before the last few minutes.
3. Leading questions: where I put the answer in the question.
4. Talk time: roughly what share of the call was me talking.
5. Feature requests I took at face value instead of asking what problem they'd solve.

Then give me:
- Facts I learned: things that happened, what they do today, what they've paid, what it costs them. Keep these separate from opinions and compliments.
- The problem in their words: their exact phrases, ready to reuse on a landing page.
- Signs of real pain, or signs it's a "nice to have". Say which way it leans and why.
- The three questions I should have asked, and when in the call to ask them.
- A short, friendly follow-up message to send them, with no pitch in it.

Here's the call:
[PASTE YOUR NOTES OR TRANSCRIPT]
Pink Means Edit Me

Swap in your own product, customer and call. A transcript works better than notes, because notes leave out what you said.

Run It On Five

After five calls, paste all five in at once and ask what problem came up most, in whose words. That's the start of your positioning.

Record With Permission

Ask at the start: "Mind if I record so I can listen instead of taking notes?" Most people say yes. Follow the rules where you and they live.

One More Thing

Mistakes Are Cheaper In A Room.

Anybody can build software now. Not everybody can build a business.

The Solo Founder Lab

It's hard to spot these from the inside. The Lab is for Founders who'd rather hear it early: weekly office hours with a CTO who's built two seven-figure software companies, and a room of other Founders who care whether anybody buys what you're making.

Lab.exe✣

Less Theater. More Customers.

Want my 30-Day Launch Plan? It's for Lab members only: validate, plan, build and launch, one week at a time.

See The Solo Founder Lab ▶