Stop Building Apps. Start Building Moats. (An 8-Year Autopsy of a Founder’s Soul)

You don’t have a motivation problem. You have a pattern problem. And after eight years, the pattern is killing you.

Let’s talk about the IT engineer who posted on Hacker News asking whether he should give up after eight years of building apps. He’s built tens of them. Each one starts the same way: excitement, then demotivation, then the slow realization that what he built is, in his own words, “useless.” Then he starts over. Same cycle. Same outcome. Eight years.

But here’s where it gets painful. One of his apps actually worked. A local app for his country. 3,000 weekly users. Organic growth. Zero ad spend. He was a student with no money, and he still pulled 3K users through sheer hustle and social media.

And then the copycats came.

Three apps. Better versions. Huge marketing budgets. Famous people promoting them. His users went from 3,000 to 2,000 to 1,000 to 300 to 100 to 30 to one or two.

Being first doesn’t matter if you can’t survive being copied. Being good doesn’t matter if you can’t afford to defend it.

Now he’s back with a new app. An AI prompt marketplace where creative people can earn money from prompt remixes. He’s written songs to promote it. The songs went viral. The app didn’t. He’s considering taking outside investment for the first time. And a part of him — the honest, exhausted part — is whispering: Is this just the same story again?

Yes. It is. And here’s why.

Look at the pattern. Every single time, he builds first and validates later. He falls in love with the act of creation, ships the product, and only then discovers whether anyone wants it. The excitement comes from building, not from solving a problem that someone will pay to have solved. The demotivation comes from the inevitable collision between the dream and the market.

The most dangerous thing a builder can do is confuse the joy of building with the existence of a business.

His one success — the 3K-user app — didn’t fail because it was bad. It failed because he had no moat. No defensibility. No distribution advantage. No reason for users to stay when a better-funded competitor showed up with a slicker product and celebrity endorsements. He was first, and being first was all he had.

Now look at the new app. A prompt marketplace. Let me be direct: this is one of the most commoditizable ideas in the current AI landscape. Prompts are text. Text is infinitely copyable. The moment the platform gains traction, OpenAI, Anthropic, or a well-funded startup can replicate the entire value proposition in a weekend. The “users can earn money” angle is compelling on paper, but it creates a race to the bottom on pricing and a zero-sum dynamic that rewards volume over quality.

If your competitive advantage is “I thought of it first,” you don’t have a competitive advantage. You have a head start on someone else’s success.

Here’s what the Hacker News comments got right and wrong. The commenter who said “keep trying, limited downside, unlimited upside” — that’s survivorship bias dressed as wisdom. The commenter who said “figure out how to make money first, then build the app around it” — that’s the actual answer. The commenter who said “all this experience is making you better positioned for your next project” — that’s true only if the experience produces learning. And after eight years of the same pattern, it clearly hasn’t.

Because here’s the brutal truth: experience without reflection is just repetition with more confidence.

What should he do? What should any solo founder in this position do?

First, stop building. Seriously. Stop. The next app will not be different because the thinking hasn’t changed. The pattern will repeat because patterns don’t break themselves — they break when you interrupt them deliberately.

Second, reverse the order. Before writing a single line of code, answer three questions: Who specifically has this problem? How much are they already paying to solve it (or how much pain are they in)? And what stops a better-funded competitor from taking this from me in 90 days?

Distribution is the product. Code is the commodity. The founder who owns the channel wins; the founder who owns the code gets copied.

Third, if you’re going to take investment, take it to buy distribution, not to fund API costs. API costs are a treadmill — they scale with usage and never stop. Investment should buy you a moat: exclusive partnerships, brand equity, network effects, proprietary data. If the money just keeps the servers running, you’re renting time, not building equity.

Should he give up? No. But he should give up the pattern. The eight years weren’t wasted — they were tuition. But tuition only pays off if you graduate. And graduation means internalizing the lesson that every failed app has been screaming at him: build the business first, then build the app.

The songs going viral while the app got zero attention? That’s not a funny coincidence. That’s the market telling him something. People wanted the songs. They didn’t want the app. The market is never wrong — it’s just honest in a way that hurts.

The market doesn’t reward effort. It rewards alignment. And alignment means building what people want to pay for, not what you want to build.

Eight years. Tens of apps. One near-success destroyed by copycats. A new app built on the same pattern. The question isn’t whether to give up. The question is whether he’s willing to give up the one thing that’s been failing him: the build-first, validate-later reflex that turns smart, hardworking engineers into serial disappointments.

The answer to “should I give up” is always no. The answer to “should I keep doing the same thing” is always no. The hard part is recognizing they’re the same question.