Build in Public on X: How Indie Hackers Turn Posts Into Users

In a 2020 account of running the Indie Hackers Twitter presence, Sherry reported that the account grew from more than 20,000 followers to 39,000, while monthly impressions rose from roughly 600,000 to 3.5 million at one point. She also stated that she did not track clicks, traffic, or conversions. The case therefore documents reach and community participation; it cannot establish customer acquisition.

Her operating idea was to reflect the existing Indie Hackers community on Twitter: ask questions, summarize forum knowledge inside the feed, highlight members, and make the platform useful even when people did not click back. The account had an upstream source of material—the community—and a downstream effect it cared about—participation and recognition.

For a founder, the practical part is the recurring social job. An account can surface useful questions, connect people, or show how customers work. The metric should match that job; Sherry's account leaves the traffic and revenue question unanswered.

Write down one useful exchange that already happens around the product. Build the account around making that exchange easier to join.

In October 2025, Replymer founder Alex Belogubov reported reaching $3,000 in monthly recurring revenue six days after launch. He wrote that regular posts about progress and problems brought signups and founder DMs, and that some early users became paying customers after follow-up conversations and rapid product changes.

Belogubov already had 11,500 Twitter followers, and three launch-day posts generated a reported 120,000 impressions. Those starting conditions matter. So does the work after each post: people sent DMs or signed up, the founder continued those conversations, the product changed, and some users paid. A new account publishing similar updates would be running a different experiment.

Daniel Peris reported that INDEXED.pro approached €2,500 MRR 45 days after its November 2023 launch. The team announced the launch to about 500 pre-launch subscribers and used the founders' Twitter, LinkedIn, newsletter, and professional networks, plus a newer product account with more than 500 Twitter followers.

The launch also included Product Hunt, directory submissions, partnerships, and planned SEO work. Peris described Product Hunt as modest for traffic and sales while crediting it with visibility and backlinks. With so many channels active, the post cannot assign the reported revenue to X alone.

It does identify one X-specific mechanism: customers shared visible indexing results on social media, which Peris said helped acquire new customers. The product produced an outcome people could show, giving customer proof a role in later distribution.

Keep source-at-signup data across the whole launch mix. If customers share a product result, track the visits and signups that arrive from those shares separately from founder posts.

In a 2022 retrospective on a 30-day build-in-public challenge, Victor reported that the announcement received more than 2,000 comments. He sent interested people directly to a Notion page instead of an email-capture page, then described that choice as a mistake.

The post opens by saying that a 60-person waiting list produced $14 and that the challenge produced $50; later it says the challenge ended with $14. The accounting is internally inconsistent, so it should not be used as a conversion benchmark. The useful evidence is the handoff failure Victor described himself. An open document suited a reach goal. A product waitlist needed an explicit way to request the next update.

In a 2023 Indie Hackers post, Adam K. Stinson said he reviewed hundreds of indie hackers and found only a small minority of successful projects were visibly built in public. He described projects above $15,000 MRR whose founders had roughly 50 to 100 Twitter followers, and pointed to earned media, directories, SEO, referrals, and affiliates as alternative growth paths.

The post omits its sample, selection rules, dataset, and attribution method. That leaves us with a counter-hypothesis from community research rather than a measured base rate. It still widens the comparison set beyond the founders who publicly discuss growth on X.

For a niche B2B tool, direct outreach, integrations, comparison pages, or industry partners may reach buyers faster. A visual creator product may have an obvious social proof loop. The decision depends on where customers already search, compare, and refer.

Search for ten recent conversations in the buyer's own language. If you cannot find them, keep X as a small test and spend the main distribution effort elsewhere.