600 days of tuition
Orel Zilberman came to indie hacking with an unfair advantage and a humbling timeline. The advantage: nine years of software development experience, including time at two startups. The timeline: 600 days and more than a dozen failed products before anything worked.
That's the part of the story most founders skip. Six hundred days is nearly two years of building things nobody wanted, watching launches flatline, and starting over. Zilberman has been open about the stretch — not as a badge of suffering, but as the tuition every indie hacker pays. Each failed product taught him something about what users actually open their wallets for, even if the lesson only became clear in retrospect.
WriteStack itself didn't start as WriteStack. The original idea was an AI article outline generator — a clever tool in a crowded category. It was the kind of product that demos well and converts poorly. Zilberman could have spent months polishing it. Instead, he did something unfashionable: he DM'd his early users and asked what they actually struggled with.
What kept him going is worth examining. Solo founders often describe the pre-traction period as lonely and disorienting — no team to share the doubt, no investors to report to, just the quiet accumulation of things that didn't work. Zilberman's response was to keep the experiments small and the cycles fast. A dozen products in 600 days means roughly seven weeks per attempt: enough to learn, not so much that any single failure felt existential. That cadence is itself a skill, and it's one that only compounds.
The pivot users asked for
The answer changed everything. His users — creators all-in on Substack — didn't need help outlining articles. They needed help staying consistent. Writing was the fun part; the grind was scheduling Notes, tracking analytics, and maintaining a content pipeline without letting it consume their week. The real pain point wasn't creation. It was consistency.
So Zilberman pivoted the entire product around that unglamorous problem. WriteStack became the creator operating system for Substack: scheduling Notes, surfacing analytics, planning the content pipeline — the operational layer that Substack itself handles beautifully for publishing but leaves untouched for everything around it.
The pivot is a case study in listening over vision. The AI outline generator was Zilberman's idea of what users needed. The scheduling toolkit was what users told him they needed. The distance between those two things was the difference between another failed product and a business doing $11K in monthly recurring revenue.
Borrowed distribution
WriteStack's growth to over 360 paying customers and roughly $11K MRR came with almost no paid marketing. The engine was organic: Substack discovery, Google traffic, and Zilberman's own building-in-public content. For a tool serving Substack creators, there was a neat recursion here — the founder marketed to creators by creating, in the open, about building for creators.
But the most interesting growth decision was architectural. As WriteStack grew, users kept asking for the same thing: they were also posting through Buffer, and they wanted WriteStack to meet them there. Rather than building LinkedIn, X and every other integration from scratch, Zilberman plugged into Buffer's API as the distribution layer.
The logic was clean. WriteStack handles the Substack side — scheduling, analytics, content management. Buffer handles distribution to everything else. One action in WriteStack fans out everywhere. As Zilberman put it, he fell in love with Buffer's experience and support — but there was strategy too. Even if Substack eventually ships its own scheduler, WriteStack still does what Substack won't: getting a creator's Notes onto LinkedIn, X and everywhere else. For a solo founder, not rebuilding the wheel on distribution was a meaningful reduction in complexity.
Why it worked
WriteStack's story is the indie hacker ideal made real — but with the timeline intact. The 600 days and dozen failures aren't footnotes; they're the story. Most founders who quit do so around day 200, when the failures feel like evidence rather than tuition. Zilberman's edge wasn't that he avoided failure. It was that his nine years of experience let him fail efficiently, extracting the lesson from each dead product fast enough to try again.
The pivot holds the deepest lesson. Zilberman started with an AI outline generator because it was interesting to build. He ended with a scheduling toolkit because it was valuable to use. That gap — between interesting and valuable — is where most indie products die. The founders who cross it tend to share one habit: they ask users directly, early, and they actually change course based on the answer.
Finally, there's the distribution insight. Solo founders can't out-build platform teams, but they can out-position them. WriteStack didn't try to replace Substack or Buffer. It became the connective tissue between them — the layer neither platform would build, serving the creators both platforms need. In a world of giant platforms, the most defensible indie position is often the gap between two giants.
And there's a meta-lesson in the Buffer integration story. When users ask for a feature, the instinct is to build it. Zilberman's instinct was to find who'd already built it well and plug in. That restraint — the willingness to let someone else's API be the answer — is what lets a solo founder serve 360 paying customers without a team. Leverage beats headcount, every time.
The playbook
- DM your users, don't guess — Zilberman DM'd early users directly instead of guessing. The feedback revealed that consistency with Notes — not outline generation — was the real pain. Talk to users before you scale the wrong thing.
- Pivot to the boring problem — The original AI outline generator was clever but unwanted. The pivot to scheduling and analytics was less exciting and dramatically more valuable. Boring problems pay.
- Grow where your users live — Substack discovery, Google traffic and building in public drove 360+ paying customers with no paid marketing. For niche tools, being visible where your users already are beats ad spend.
- Borrow distribution via API — Rather than building LinkedIn and X integrations from scratch, WriteStack plugged into Buffer's API as the distribution layer. Let platforms handle the 'where' while you own the 'what.'
- Treat failures as tuition — Nine years of dev experience across two startups gave Zilberman the technical range to build solo. The 600 days weren't wasted — they were tuition.