Most indie startups don't fail because of one dramatic mistake. They fail from a small set of repeatable patterns: building something people like but don't urgently need, never getting it in front of the people who would pay, pricing too low to cover the founder's costs, and running out of money or energy before any of that gets fixed. Each pattern shows up early in a few numbers you can check every week, which means most of them can be caught while there's still time to change course.
Last updated: Nov 12, 2026
This guide covers how often new businesses and indie projects actually fail (with real survival data), what founders themselves say killed their startups, the six patterns that hit small self-funded products hardest, a weekly check that catches them early, and how to decide between fixing, changing course and stopping. Every figure links to its source, read on 12 November 2026. The worked example near the end is made up and labeled as such.
How often do indie startups actually fail?
Often, and that's normal. There's no official count of indie software projects, so the closest checkable numbers come from two places.
The first is the U.S. Bureau of Labor Statistics, which tracks every new private business location with employees. In its establishment age and survival data, 78.9% of locations that opened in the year to March 2025 were still open a year later, and 47.2% of those that opened in the year to March 2021 were still open in March 2026. Put the other way: about one in five closes within a year and about half within five years. Two caveats matter for indie founders. These numbers only cover businesses with employees, so solo founders without staff aren't in them. And a closed location isn't always a failure; some are sold or merged.
The second is what prolific indie makers report about their own hit rate. Pieter Levels, who runs Nomad List and Remote OK, wrote that only 4 out of 70+ projects he built made money and grew, a hit rate of about 5%. His conclusion was to ship more, not to stop.
That's the useful framing. A single project failing is the default outcome. What actually ends an indie founder's run is different: burning so much money, time or motivation on one project that there's nothing left for the next attempt. Avoiding failure patterns is mostly about failing smaller and earlier.
What are the most common reasons startups fail?
The most cited dataset is CB Insights' work on startup post-mortems. Its newer report looked at 431 VC-backed companies that shut down since 2023, with reasons identified for 385 of them. Its older study read 101 startup failure post-mortems written by the founders themselves. Most startups cited more than one reason, so the shares add up to more than 100%.
Reason | Share cited | Which study |
|---|---|---|
Ran out of capital | 70% | 385 VC-backed shutdowns since 2023 (CB Insights, Mar 2026) |
Poor product-market fit | 43% | 385 VC-backed shutdowns since 2023 |
Bad timing or market conditions | 29% | 385 VC-backed shutdowns since 2023 |
Unsustainable unit economics | 19% | 385 VC-backed shutdowns since 2023 |
No market need | 42% | 101 founder post-mortems (CB Insights) |
Ran out of cash | 29% | 101 founder post-mortems |
Got outcompeted | 19% | 101 founder post-mortems |
Lost focus | 13% | 101 founder post-mortems |
Burnout | 8% | 101 founder post-mortems |
Failure to pivot | 7% | 101 founder post-mortems |
Two things stand out. First, the same root cause tops both lists under different names: "no market need" in the older study and "poor product-market fit" in the newer one. Second, both studies are about funded startups. Indie products rarely die from a failed funding round, but they die from the same underlying problems, usually with less money and less time to notice.
Why is "ran out of money" usually not the real reason?
Because it's how the story ends, not why. The 2026 CB Insights report says this directly: running out of capital is almost always the final cause of death, and the more telling causes (weak product-market fit, bad timing, poor unit economics) explain why the money dried up.
For an indie founder, "money" usually means personal runway: savings plus product revenue, minus your own living costs and the product's bills. That changes the question you should ask. Not "do I have money?" but "at the rate things are going, does revenue catch up with my costs before my savings run out?" Paul Graham calls this being default alive or default dead, and he notes that half the founders he talks to don't know which one they are.
You can answer it in a couple of minutes. Put your cash and monthly costs into the free IndieHunt runway calculator to see how many months you have, then compare that number with how fast your revenue is actually growing. If the two lines don't meet before the cash runs out, you're default dead, and the patterns below are where to look for the reason.
Which failure patterns hit indie founders hardest?
These six show up again and again in indie post-mortems and in the studies above. Each one comes with a sign you can check and a first fix.
Building something people like but don't need
This is the "no market need" pattern, and it rarely looks like failure at first. People sign up, say nice things and never come back. One founder in the CB Insights post-mortems, behind a product called Patient Communicator, summed it up: there were no customers because nobody wanted the model being pitched. "Doctors want more patients, not an efficient office."
Early sign: signups that don't reach the core action, and almost nobody who would be upset if the product disappeared. First fix: ask your active users how they'd feel if they could no longer use it. A product-market fit survey you can run with under 100 users turns this into a number instead of a feeling.
Building before anyone can find it
CB Insights ranks poor marketing #8 of 20, noting it was common among founders who liked to code or build product but didn't enjoy marketing. That's most indie founders. The pattern looks like six months of building, one launch day, a spike, and then silence.
Early sign: you can't name the channel that brought your last five paying customers, or the answer is "launch day" for all of them. First fix: put a fixed share of each week into getting found, and keep it there even when there's a bug to chase. Launch boards and directories give you a start. Written articles keep working long after a launch week: Piece Press publishes long explainers that walk a reader through one decision, the kind of page people find when they search the problem your product solves. If you'd rather not write and place those articles yourself, Posting Dude publishes 10 editorial articles about your product every month across a 10-site network, at $249 a month for one project or $399 for up to three. It's run by the same team as IndieHunt. It won't guarantee rankings or traffic; it takes the monthly writing and publishing off your list so the getting-found work actually happens.
Feature creep instead of focus
When growth stalls, adding features feels productive. Every new feature also adds testing, support and things for a new user to understand, and it rarely fixes the reason people left. The old advice still holds: prioritize the features that serve the one problem the product exists to solve.
Early sign: your roadmap keeps growing while the share of new signups who reach the core action stays flat. First fix: freeze the feature list for two weeks and spend that time on the single step where most new users stop.
Pricing too low to survive
Unit economics show up in 19% of the 2026 shutdowns. For indie products the version is simpler: the price is so low that you'd need an unrealistic number of customers to cover your costs. A $9 product needs 223 paying customers to cover $2,000 a month in costs; a $29 product needs 69.
Early sign: when you divide your monthly costs by your price, the number of customers you need is more than you can see yourself reaching within your runway. First fix: raise the price for new customers, and keep existing customers on their current price if you want to stay on good terms with them.
A message nobody understands in five seconds
Some products are fine but described in a way that makes visitors guess what they do, who they're for or why they'd switch. Visitors don't guess; they leave. This is the pattern the first version of this post called a communication problem, and it's one of the cheapest to fix.
Early sign: visitors land on the homepage and leave without clicking anything, or customers describe the product in completely different words than your headline. First fix: write a one-page positioning brief before you rewrite the homepage, using the words your customers already use.
Losing focus and burning out
Lost focus shows up in 13% of the CB Insights post-mortems and burnout in 8%. For a solo founder these are often the same thing: a second project, a new idea and a support backlog all pulling at once, until the work stops being fun and then stops.
Early sign: you've started a new project before deciding what happens to this one, or you dread opening the inbox. First fix: decide on purpose. Either set a dated goal for this product or put it into low-maintenance mode and say so publicly. Drifting is the expensive option.

How do you spot a failure pattern before it's fatal?
Check the same five things every week, in the same order, and write the answers down. It takes about 20 minutes and catches every pattern above while it's still cheap to fix.
Months of runway. Cash divided by monthly net burn (your costs minus revenue). If it dropped since last week, find out why.
Core-action rate. Of last week's signups, how many did the one thing your product exists for? This is your early read on market need.
Where paying customers came from. For each new paying customer, write down the channel. You're looking for one you can repeat on purpose.
Customers needed at today's price. Monthly costs divided by price. If the answer is far beyond what you can reach in your runway, pricing is a problem now, not later.
Hours spent building vs. getting found. If building is above 80% for three weeks in a row, the "nobody can find it" pattern is likely on its way.
None of these need a dashboard. A spreadsheet with one row per week is enough, and seeing the trend over six to eight weeks tells you far more than any single week.
What does a failure-pattern review look like for a real product?
Here's a worked example. Tallyvine is a made-up product: a payment-reminder tool for freelance designers, built and run by one founder. The numbers are invented to show the method; only the math is real.
Five months after launch, the founder has $14,000 in savings, personal living costs of $1,900 a month, tools and hosting at $150 a month, and $240 in monthly revenue from 16 customers paying $15 each. Net burn is $1,900 + $150 - $240 = $1,810 a month, so runway is $14,000 / $1,810, or about 7.7 months.
Check | What Tallyvine found | Pattern it points to | Next step |
|---|---|---|---|
Runway | About 7.7 months, shrinking each month | Default dead at current growth | Set a dated review for month 3 of the remaining runway |
Core-action rate | 52 of 410 signups (12.7%) sent a first reminder | Weak need, or a confusing first step | Watch five new users set up their first reminder |
Paying-customer source | 9 of 16 came from one forum thread for freelance designers | One promising channel, not yet repeated | Spend 2 hours a day where those designers already talk |
Customers needed at $15 | $2,050 / $15 = 137 customers | Pricing too low to survive | Raise to $29 for new customers: $2,050 / $29 = 71 customers |
Feature list | 23 open requests, 4 started | Feature creep | Freeze the list for two weeks; park the 4 started items until onboarding is fixed |
The review doesn't say "give up" or "keep going". It says the product has a real signal (customers from one specific community) buried under three fixable patterns: a price that needs 137 customers, a first step most signups never finish, and a growing feature list. The founder now knows what to work on for the next month, and has a date to decide whether it worked.
When should you change course, and when should you stop?
Set the decision date before you need it. If you wait until the money is nearly gone, every option looks worse and you'll decide in a panic.
Keep going and fix execution when the people who reach the core action stay and pay, but too few reach it or find you. That's an onboarding, pricing or distribution problem.
Change course when one group of users or one use case is clearly working and the rest isn't. Narrow to what works. The EarlyHunt guide on how to decide whether to pivot your startup walks through the signals and pivot types.
Stop when, after a fair test with a fixed date, almost nobody reaches the core action and the people who do don't come back. Stopping on purpose keeps savings, time and energy for the next attempt.
Failure to pivot shows up in 7% of the CB Insights post-mortems. The more common indie version is not a failure to pivot but a failure to decide anything at all.
What mistakes make a failing indie startup fail faster?
Treating launch day as the plan. A launch is one day of attention. Without a channel that keeps working, the drop after it is guaranteed.
Counting signups instead of activated users. Signups feel like progress. Users who reach the core action and come back are the only number that predicts revenue.
Raising the stakes instead of lowering them. Quitting a job, hiring or paying for ads before there's a working signal makes every pattern above more expensive.
Copying funded-startup advice. Growth at any cost makes sense with investor money behind you. With savings, profit sooner is usually the safer goal.
Keeping the results private. Founders who share real numbers in communities get faster, more honest feedback, and sometimes their first customers.
Frequently Asked Questions
What percentage of startups fail?
For U.S. businesses with employees, BLS data shows about 21% of new locations close within a year and about 53% within five years. For indie software projects there's no official number, but experienced makers report most projects never make meaningful money; Pieter Levels puts his own hit rate at about 5%.
What is the number one reason startups fail?
Running out of money is cited most often, but it's usually the result, not the cause. Underneath it, the most common root cause is building something the market doesn't need badly enough: 42% in CB Insights' 101 post-mortems and 43% poor product-market fit in its 2026 analysis.
Do bootstrapped startups fail less than VC-backed ones?
There's no reliable dataset comparing the two directly. Bootstrapped products tend to be smaller and cheaper to run, so they can survive longer on less, but they also have less money to fix mistakes. The patterns that kill them are largely the same.
How long should I give an indie product before quitting?
Long enough for a fair test, with a date set in advance. A reasonable window is three to six months after launch for a repeatable signal to show up: users reaching the core action, coming back, and paying. If your runway is shorter than that, shrink the test, not the decision.
Is it ever too late to pivot?
It's too late when you no longer have the money, time or energy to test the new direction properly. That's why the decision date matters: pivoting with six months of runway left is a plan, while pivoting with six weeks left is usually a gamble.
Failure patterns are boring in the best way: the same few show up again and again, and each one leaves signs weeks before it becomes fatal. Check your numbers every week, fix the pattern they point to, and set a date to decide. That alone puts you ahead of most of the founders in those post-mortems.