I'm a solo founder. I built my first SaaS, and like most founders, I thought the hard part was building it.
It wasn't.
After launch, I was spending more time on content than on the actual product — writing blog posts, creating social media visuals, finding the right image for every single post. It was killing my momentum.
So instead of fixing my distribution problem, I did what every developer does — I built another tool.
That tool became ThumbAPI — a REST API that generates ready-to-use thumbnails from just a title. One POST request, sized for YouTube, Instagram, LinkedIn, blog covers, or X. Built because I was tired of Canva and broken AI image prompts.
But then I had the exact same problem again. I built something useful. Nobody knew it existed.
Here's what I learned.
Building is 20% of the work. Distribution is 80%.
I launched on Product Hunt. Got some upvotes, some traffic, almost zero signups. I posted on Hacker News. Two points, three comments. I thought the product would speak for itself.
It doesn't. Nothing does.
Every founder I've read about — Bannerbear, Transistor, Plausible — they all say the same thing in hindsight. Building is the easy part. Getting people to care is the real job.
Product Hunt is not a growth channel. It's a moment.
The traffic spike from Product Hunt lasts 48 hours. If you don't have other channels ready when that wave hits, it disappears and you're back to zero.
I didn't have other channels ready. Now I'm building them one by one, the slow way.
Reddit will ban you. Until it won't.
Every subreddit has rules against self-promotion. And they should — nobody wants their community turned into an ad feed.
But there's a difference between "check out my product" and "I had this problem, built something, want to try it?" The first gets removed. The second starts a conversation.
I learned to lead with the problem, not the product. Always.
Nobody finds your WordPress plugin just because it's on WordPress.org
I built a WordPress plugin that auto-generates featured images from a post title — same API, easier for non-developers. Got it approved on WordPress.org.
Zero installs.
WordPress.org is not a discovery platform. It's a directory. People find plugins through Google, YouTube tutorials, or recommendations. Being listed means nothing if nobody is pointing to you.
What actually works (so far)
Honestly, I'm still figuring this out. But here's what has moved the needle even slightly:
- Writing posts that lead with the problem, not the product
- Being specific — "tired of Canva + AI prompt loop?" lands better than "thumbnail API"
- Showing up in communities where my actual users are, not where developers are
- Treating every comment and reply as a conversation, not a funnel
Where I am now
ThumbAPI is live. The API works. The WordPress plugin is approved. I have a free tier with no credit card required.
And I'm still learning how to tell people it exists.
If you've launched something and gone through this — what actually worked for you? I'm genuinely asking.
ThumbAPI generates thumbnails via UX/UI option or a single REST API call. Built for n8n, Make.com, Zapier, and automation workflows. Try it free at thumbapi.dev
Thumbnail for this blogpost is generated by. thumbapi.com
Top comments (3)
The "built it, nobody came" story is the most common and most painful one in indie SaaS, and the lesson is almost always the same: the building was never the hard part, distribution and a sharp ICP were. We over-index on the product because it's the part we control and enjoy, and under-invest in "who exactly is this for and where do they already hang out." Shipping is necessary but nowhere near sufficient. That realization is partly why I built Moonshift to make the build cheap and fast, so the energy goes to the part that actually decides survival, finding the people. What would you do differently next time, validate demand first or pick a much tighter niche?
Honestly, I’ve started to believe distribution is the product. Building is the easy part in comparison. Next time I’d validate demand way earlier and focus heavily on where the users already are before writing much code.
And that’s exactly what I’m currently doing with my current new SaaS validating demand first this time.
It already feels like a much better approach but probably learning even more lessons along the way 😄
"Built it, nobody came" is the most common and most painful indie lesson, and the takeaway is brutal but freeing: building was never the hard part, distribution is. We pour months into the product because building is the thing we know how to do and feel in control of, while marketing/distribution is uncomfortable and uncertain - so we hide in the codebase and call it progress. The product was probably fine; the silence was a distribution problem, not a code problem.
The reframe that actually helps next time: validate demand BEFORE you build, and budget as much energy for getting users as you did for shipping features. If anything, build less and distribute more. That's part of why I built Moonshift (a multi-agent pipeline that ships a prompt to a deployed SaaS) the way I did - make the building so cheap and fast (~$3 flat, first run free) that you can put a real thing in front of users early and cheaply, so you find out nobody's coming before you've sunk months into it. Honest, valuable post - these post-mortems help more people than the success stories. Knowing what you know now, would you have spent the build time on distribution instead, or validated the idea harder first? Curious which lesson stuck hardest.