Sickness Labs
Academy
22 diseases that kill indie projects — organized by the phase where they strike. Learn to recognize the symptoms before they become terminal.
Patient Zero
Founder Diseases
The diseases you carry as the person behind the project.
Founder Syndrome
When the founder becomes the bottleneck. Every decision flows through one person, and the project can't breathe without them.
Startup Burnout
The slow burn that turns passion into exhaustion. You're still shipping, but you stopped caring three months ago.
Imposter Syndrome
You shipped it, people are using it, and you're still convinced someone will figure out you have no idea what you're doing.
Procrastination
Researching, planning, reorganizing — anything but the one task that would actually move the project forward.
Incubation
Idea Diseases
The diseases that strike before a single line of code is written.
Analysis Paralysis
Trapped in an endless loop of research, comparison, and what-ifs. You know everything about the market — except how to start.
Shiny Object Syndrome
Every week there's a better idea. The current project is 60% done but the new one feels 100% exciting.
Validation Skip
Building first, asking questions never. The product is finished — but nobody was ever asked if they wanted it.
Infection
Build Diseases
The diseases that infect your product while you're building it.
Feature Creep
The product started simple. Now it has a dashboard, an API, dark mode, and a settings page with 47 toggles. Nobody asked for any of it.
Scope Creep
The timeline was two months. Then someone said "while we're at it" and now it's month six with no end in sight.
MVP Overengineering
Your MVP has a microservice architecture, CI/CD pipeline, and 90% test coverage. It has zero users.
Feature Prioritization
Everything feels urgent, nothing feels important. The backlog is a graveyard of half-started features and unranked ideas.
Symptoms
Market Diseases
The diseases that kill products after you build them but before they grow.
Customer Validation
You talked to five friends who said "that's cool." That's not validation — that's politeness.
Market Validation
The market research says there's a gap. But a gap in the market doesn't mean there's a market in the gap.
Product-Market Fit
You have users, but they're not staying. You have revenue, but it's not growing. Something fits — but not quite.
Pricing Phobia
Your product is free, freemium, or priced so low it signals "hobby project." Charging real money feels like a betrayal.
Critical
Launch Diseases
The diseases that keep your product from ever reaching people.
Launch Fear
The product is 95% ready. It's been 95% ready for four months. There's always one more thing before it's "really" ready.
No Distribution
You built it. Nobody came. Because nobody knew. Zero marketing budget, zero audience, zero plan to change that.
No Audience First
Launch day arrives and the only visitor is your own browser. You skipped the part where you build an audience before building the product.
MVP Launch
Your MVP launch strategy is "post on Reddit and hope." That's not a strategy — that's a wish.
Terminal
Graveyard Diseases
The diseases that kill projects slowly — or keep them undead.
Zombie Projects
Not alive, not dead. The domain is renewed, the server is running, and the last commit was eight months ago.
Perpetual Beta
"We're still in beta" is the startup version of "it's not you, it's me." The product will never be ready because ready means accountable.
Pivot or Quit
The hardest question in indie building: is this a problem you can fix, or a project you need to walk away from?