Building Before Validating
This is the original sin, and almost everything else flows from it. You have an idea, building feels like progress, so you spend months making the product before you have any evidence anyone wants it. Then you launch to silence. The mistake is not the building, it is the order. You committed your scarcest resources to a guess instead of checking the guess first.
Validation runs in the opposite order from instinct. Before you write code, find people with the problem and listen. Then put up a simple landing page describing the offer and see if anyone signs up or pre-orders. Then try to take money for a manual version you deliver by hand. Each step is cheap, and a no at any step saves you the entire build. The build-or-kill logic is to fail at the cheapest possible stage, not the most expensive one.
The tell that you are making this mistake is a roadmap full of features and a calendar empty of customer conversations. If you cannot name ten people who told you they have this problem in their own words, you are building on a guess. Stop and go get the evidence.
- The mistake is the order, not the building. Validate the guess before you fund it.
- Sequence: customer conversations, then a landing-page smoke test, then taking money.
- If you can't name ten people who described this problem to you, you are building blind.
No Distribution Plan
Founders obsess over the product and assume customers will find it. They will not. Build it and they will come is the second great myth after leap and the net appears. A good product with no path to its buyers loses to a mediocre product that knows exactly where its customers are and how to reach them. Distribution is not an afterthought, it is half the business.
The mistake is treating marketing as something you bolt on after launch. By then it is too late and too expensive. The fix is to choose your channel as early as you choose your product, and to validate the channel the same way you validate the idea. Where do these customers already gather? Can you reach them there for little or no money? If your only honest answer is paid ads you cannot yet afford, that is a red flag worth heeding before you build.
A practical test: before committing to build, try to get attention through your intended channel with nothing but a description of the offer. If you cannot get strangers to care about the pitch, the finished product will not magically fix that. Distribution problems do not solve themselves with more features.
- Build it and they will come is a myth. A reachable audience beats a better product.
- Pick and validate your channel as early as you pick the product.
- If you can't get strangers to care about the pitch, the finished product won't change that.
Selling a Vitamin When You Need a Painkiller
A painkiller solves a problem people already feel and are already trying to fix. A vitamin is nice to have, vaguely good for you, and easy to skip. Most failed startups are vitamins that the founder mistook for painkillers. The product is pleasant, the demos go well, and yet nobody quite gets around to paying, because the problem was never urgent enough to act on.
The danger is that vitamins are easy to validate falsely. People are polite. They will tell you an idea is interesting and that they would probably use it, because saying so costs them nothing. The way to tell a painkiller from a vitamin is to look at cost and behaviour, not opinions. Is the problem costing them time, money, or sanity right now? Are they already paying for a workaround or hacking together a solution? Real pain leaves evidence.
If you discover you are holding a vitamin, that is valuable, not fatal. You either reframe the offer around a sharper, more urgent version of the problem, or you kill it cheaply and move on. What you must not do is try to overcome weak demand with a better-looking product. You cannot polish a vitamin into a painkiller.
- Painkillers solve felt, urgent problems. Vitamins are nice-to-have and easy to skip.
- Vitamins validate falsely because people are polite. Look at behaviour and cost, not opinions.
- Evidence of a painkiller: existing workarounds, money already spent, time or sanity bleeding now.
Scaling Before You Are Ready
Premature scaling is pouring money and people into growth before you have a working, repeatable model. It is one of the most common causes of startup death, and it is seductive because it looks like ambition. You hire ahead of revenue, run ads before retention works, and expand to new markets before the first one is solid. You are stepping on the gas with the wheels off the ground.
The core error is scaling a leaky bucket. If new customers churn out as fast as you acquire them, more acquisition just empties faster and burns cash doing it. Fix the bucket first. Get a cohort of customers who stick, who use the product, who would be genuinely annoyed if it disappeared. Only then does spending to acquire more make sense, because now each new customer is worth keeping.
Discipline here is simple to state and hard to follow: do not scale anything you cannot yet repeat. Prove that you can acquire a customer profitably and keep them, on a small scale, by hand if necessary. The signal to step on the gas is a model that works reliably when it is small, not a hope that it will start working once it is big.
- Premature scaling looks like ambition and acts like a cash incinerator.
- Do not scale a leaky bucket. Fix retention before you fund acquisition.
- Step on the gas only when a small version of the model already works reliably.