As developers, we are plagued by a seductive delusion: “If you build it, they will come.” We tell ourselves that if the architecture is clean, the deployment pipeline seamless, the UI fast, and the service genuinely useful, users will naturally discover it.

Over the past few months, I built and launched two infrastructure tools I am genuinely proud of: Enkihost (dedicated hosting for Jekyll and Ruby) and Enkimail (a lightweight queue processor for email marketing). The code works. The servers are stable. The free tiers are live.

Yet reality has hit hard: getting actual human beings to try them out has been the hardest brick wall I’ve ever crashed into.

The Builder’s High vs. The Marketing Void

Building both projects was exhilarating. With modern developer tools, Docker, and focused vibe coding, turning an idea into production-ready software took weeks rather than months. Setting up Enkimail’s Postfix container, securing a clean IP, and tuning deliverability was deeply satisfying engineering. Launching Enkihost with automated Jekyll builds straight from Git felt like creating the tool I always wished existed.

Then came day one: opening the doors to the world.

And what happened? Crickets. Absolute, deafening silence.

Screaming Into the Social Void

Like almost every indie developer starting out, I turned to the usual playbooks: Twitter/X and Reddit.

1. The Twitter / X Echo Chamber

Posting on Twitter without an existing following is like whispering into a hurricane. You spend time crafting thoughtful threads, explaining the architectural decisions, sharing screenshots, and tagging relevant topics.

The result? 14 impressions, maybe two polite likes from bot accounts, and zero clicks to the landing page. The platform heavily favors accounts that already command massive engagement or those who spend 8 hours a day networking and replying. If you just want to build and share useful utilities, organic discovery on X is practically dead.

2. The Reddit Minefield

Next stop: Reddit. There are thriving communities for self-hosting, web development, Ruby, and marketing. But Reddit is an unforgiving landscape for builders:

  • Hyper-skepticism: Any mention of your own product is immediately flagged as spam or self-promotion, even when offered 100% free with open feedback in mind.
  • Rule friction: Navigating self-promotion rules across subreddits feels like walking on eggshells. One misstep and your post is silently removed by AutoModerator.
  • Traction lottery: The few posts that did slip through and stayed up generated a handful of upvotes, a few curious visits, and immediately faded down the front page within an hour. No sign-ups, no active testers.

The Real Problem: The High-Trust Barrier

After the initial frustration wore off, I stepped back and analyzed what is actually going on.

Enkihost and Enkimail aren’t casual weekend toy apps—they are infrastructure tools:

  1. Hosting requires trust: Changing your site’s DNS or trusting a platform with your static deployment means you need to know the server won’t vanish tomorrow. When battle-tested giants like Vercel, Netlify, or GitHub Pages exist, why would anyone take a risk on a solo project, even if it’s tailored specifically for Jekyll?
  2. Email deliverability requires immense trust: Nobody switches their email marketing queue lightly. Deliverability is business-critical; if your marketing emails get blacklisted, your revenue tanks. Asking someone to entrust their campaign queues to Enkimail requires a mountain of social proof I simply don’t have yet.
  3. Switching costs: Developers and creators are busy. Even if your tool is simpler, migrating from an existing workflow requires mental bandwidth that people rarely spend on an unknown product.

What Now?

Realizing this has been humbling, but it’s also clarifying. Building is only 10% of the battle; distribution is the remaining 90%.

Here is what I’m taking away from this wall:

  • Shouting on social feeds doesn’t work for cold products. Generic posts on Twitter and Reddit won’t magically deliver engaged users.
  • Direct, one-on-one outreach matters more. Instead of broadcasting to thousands who don’t care, I need to find five specific developers facing the exact friction Enkihost solves and help them personally.
  • Solve narrower pain points. Perhaps hosting “all Jekyll sites” is too broad. What if Enkihost focused on automated migrations from complicated hosts, or pre-configured indie themes?
  • Patience and transparency. Trust isn’t generated overnight with a witty launch tweet. It is built over months of showing up, writing about the journey, keeping the infrastructure running, and demonstrating reliability.

If you are an indie hacker or developer who has broken through this initial distribution wall for a dev tool or infrastructure product: how did you get your first 10 real users? What actually worked when social channels failed?

Drop your advice or thoughts in the comments below—I’d love to hear from anyone who has walked this road.