← Back to blog

The Truth About Indie Dev: Building Is Easy, Getting Noticed Is Hard

· 4 min read
#indie dev#thoughts#making money

A Real Story

This morning I came across a post from someone sharing their one-year summary of being an indie developer after quitting their job. The product was actually pretty good—you could tell they put real effort into it. But after a full year, total revenue was under $1,000.

One thousand dollars. One year.

That number stings, but honestly, this is the reality for most indie developers.

I Tried to Acquire It—Got Turned Down

After reading his post, I thought the product itself was solid, so I reached out, chatted with him, and even offered to acquire the website.

He said no. He wanted to keep going on his own.

I totally get it. When an indie developer builds a product, they’re investing more than just time—there’s emotion in it. It’s something they built line by line. Even if it’s not making money yet, they don’t want to let go easily. That stubbornness is both an indie developer’s greatest driving force and, in some ways, their biggest risk—because sometimes pivoting is smarter than grinding.

Either way, I respect his persistence. I hope he finds his path to growth.

”Built a Website in 12 Hours and Made $XXX”

You see these posts on social media all the time: “Spent a weekend building a little tool, now making $5,000/month.”

First reaction: damn, I could do that too!

But think about it more carefully:

1. Survivorship bias. You see the one who made it. You don’t see the 999 others who did the same thing and made zero. “I built something and nobody used it” doesn’t get engagement, so you never see those stories.

2. “12 hours” is just the development time. What they don’t tell you is they might have spent years building a targeted Twitter/X audience, or they’re already a KOL in some community, or they failed 20 times before figuring this one out. 12 hours of coding, but years of marketing muscle behind it.

3. Timing and luck. Sometimes you just happen to hit a demand window—maybe a big company killed a feature and users are looking for alternatives, and you show up at exactly the right moment. That’s not replicable.

AI Made Building Easy—Then What?

With Cursor, Claude Code, and all kinds of AI dev tools, shipping a product is genuinely way easier than before. Something that used to take one person months can now realistically be done in days.

But that’s exactly the problem—lower barriers mean more competition.

If you can build something with AI in a few days, so can everyone else. The product itself is no longer a moat.

So what is the real moat? It’s whether you can make your target users aware that your product exists—and willing to pay for it.

In other words, distribution is the scarce resource.

What to Actually Pay Attention To

So next time you see someone saying “I built a product and made X dollars,” don’t just look at the product. Analyze the rest:

  • How did they get their first users? Which community? What messaging?
  • Where does their traffic come from? SEO? Social media? Word of mouth? Paid ads?
  • Did they already have an audience before the product? Often, building an audience first and then creating a product is far easier than the other way around.
  • What’s their pricing strategy? Freemium? One-time purchase? Subscription?
  • How much time do they spend on non-development work? Writing, making videos, replying to comments, customer support, SEO optimization…

These are the bridges across the massive gap between “having a product” and “making money.”

My Own Takeaway

I’ve been tinkering with various side projects myself, and honestly haven’t made much money either. But one thing is becoming increasingly clear: building it is just the beginning. Getting people to know about it is the real battle.

In the AI era, the marginal value of technical skill is dropping fast. Being able to code and use AI tools isn’t a competitive advantage anymore. The real advantage is:

  • You understand user pain points
  • You can articulate your product’s value clearly
  • You can consistently show up in front of users
  • You have the patience to go deep on one thing instead of jumping to a new project every week

At the end of the day, indie development isn’t about technical skill—it’s about marketing, patience, and understanding your users.

Those “built a website in 12 hours” stories? Take them with a grain of salt. What’s really worth studying is the part of the story that never gets written.