Indie Hacker Playbooks

Founder-Led SaaS Pre-Demand and Launch

Share the problem, evidence and progress from day one to build warm leads and repeated post-launch exposure

Definition

Instead of promoting once after the product is finished, you gather demand by sharing the problem you'll solve, the results you got yourself, and your build progress from the day you start building, and you keep redistributing the same narrative after launch. Hasan Cagli's ElvixAI case: 5-day MVP, 18 days to $1K+ revenue, all organic.

Perspectives

Hasan Cagli (2026-08-17, X)

After running into a problem that cost 2–3 hours a day on backlink work for another SaaS, Hasan Cagli built ElvixAI, an MVP to automate it, in 5 days. Before the product existed, Hasan Cagli shared the problem, the 43 backlinks won from contacting 650 sites, and what was being built and why, gathering warm leads with DM me if you'd want early access.

At launch, Hasan Cagli posted a product video on X and LinkedIn, where the target audience already was, and afterward shared customers, revenue, features, failures and lessons every day — talking about the outcome after use instead of features, structuring long posts as 80–90% actionable information and 10–20% product pitch, and reusing one idea in X, LinkedIn and YouTube formats.

Over 18 days the product drew 5.5K+ visitors, 40+ paying customers and $1K+ in SaaS revenue, and the early growth was all organic. A 14-day $9 trial, timed to the product's inbox warm-up period, was also introduced.

How to apply

Limits

  • The numbers and results are the author's single case and self-report, and the visit and payment contribution per channel is not separated out.

  • The quality of the 43 backlinks, the search-traffic lift, the outreach cost and the basis for excluding service revenue are not independently verified.

  • This may favor a founder who already has an audience and direct proof of results on X. There's no guarantee a product with no audience gets the same results at the same posting frequency.

  • The daily-sharing approach has to be kept separate from information that shouldn't be public, like customer data, security and competitive advantage.

  • Original link

On this page