Don't build technology searching for a solution.
I've been building startups for 15+ years — my own and alongside other founders. These are the patterns I keep running into. If any of these hit close to home, it's not too late. But you do need to stop and talk to your customers.
1) Founders need to lead sales
The founders aren't selling. They've hired an agency or brought on a marketing person, and now they're wondering why nothing's moving.
Here's what happens every time: the new hire shows up, looks around, and goes "…who is our customer? What problem are we solving?" They're stuck before they start — because the founders never figured that out themselves.
No one will understand your customer's pain the way you do. Not an agency, not a sales hire, not a growth marketer. Early sales isn't about pitching features. It's about asking questions and actually listening. You're not closing deals yet — you're learning what matters.
You need to close the first customers yourself. Once you've got happy customers, know your ICP cold, and understand the positioning and the problem — then bring in marketing and sales leaders. Not before.
2) Features don't close deals — solving customer problems does
Your landing page reads like a spec sheet. Technical details that people generally don't pay attention to. Your sales call is a product tour. And your prospect is sitting there thinking "cool, but what does this actually do for me?"
If you've talked to your customers (see #1), you already know what they care about. Lead with that. How do they describe the problem you solve? Use their words, not yours. The technical stuff matters — but it's not the opening act.
3) Your target customer is "everyone"
The team keeps saying "anyone could use this" — but nobody is. There's a massive roadmap, repos for every platform, and zero paying users.
This is fear disguised as ambition. Picking a specific customer feels like leaving money on the table. It's actually the opposite. You can't build something that matters for everyone. Pick the person you understand best, go deep, and expand from there.
4) You won't ship because pricing isn't perfect
The product's ready for feedback. But instead of putting it in front of people, you're spending weeks designing a pricing page with 4 tiers, enterprise plans, and annual discount toggles. For a product nobody's used yet.
Same goes for payment integrations. Don't spend two to four weeks wiring up Stripe when you could take the sale over the phone or in person. Don't add obstacles between you and a yes — especially at the beginning. That extra friction isn't worth it when you're trying to learn if anyone actually wants what you're building.
Talk to customers. Understand the value they'd place on what you're building. Charge something — anything — and iterate. Every startup I've ever worked with has changed pricing dozens of times. Your v1 price is a guess. Make the guess and move.
5) Over-engineered, under-validated
Two years in. Version 20. More developers than customers. You've got Stripe integrations, dark mode, referral loops, automated email sequences — the whole stack. What you don't have is anyone paying you.
In the early days, do things that don't scale. Collect credit cards over the phone. Manually onboard people. Run customer support yourself. Update the database by hand if you have to. The infrastructure can come later. Right now you need to know if anyone actually wants this thing.
If you need a cautionary tale, look up General Magic. Brilliant product. Years ahead of its time. Zero market.
These aren't theoretical. I've made some of these mistakes myself, and I've watched founders I care about make the rest. The fix is almost always the same: stop building for a minute and go talk to your customers.