How to Get Your First Waitlist Signups from X (2026)

X is where indie SaaS founders live. If your product is for indie makers, solo founders, or the buildinpublic crowd, the first hundred waitlist signups almost certainly come from there, not from SEO or paid ads. The catch is that X rewards a specific shape of behaviour (helpful replies, honest build-log posts, showing up daily) and punishes the shape most founders default to (cold DMs, tagged pitches, sales threads). This is the playbook I now run to fill an indie waitlist from X.

I have shipped 7 indie apps over 8 years and ended up building two tools for myself along the way: Spaceport, a SwiftUI starter that gets a paid iOS app live in days, and Lighthouse, the launch toolkit this post is mostly about. Both got their first hundred signups from X, not from Google.

Table of contents

• Why X is the right channel for indie waitlists
• The three plays that fill an indie waitlist
• Play 1: The build-in-public log
• Play 2: Reply in the right threads
• Play 3: Share the counter
• Turning an X impression into a signup
• What not to do
• Frequently asked questions

Why X is the right channel for indie waitlists

Three reasons the channel keeps working for indie SaaS in 2026, even as the platform has changed shape:

• The audience is concentrated. Indie SaaS founders, solo makers, iOS developers, and the buildinpublic crowd cluster on X in a way they do not on LinkedIn or Reddit. If your product is for them, the addressable market on X per hour of your time is much higher than any other social channel.
• The signal is public. Someone asking “what waitlist tool should I use” or “how do I get my first users” is high-intent and visible. That does not exist on email or SEO. It is the closest thing indie SaaS has to a live inbound channel.
• Trust compounds cheaply. One useful reply lands in front of hundreds of people. A month of useful replies lands in front of thousands. Neither Google nor a paid ad gives that compounding at indie budgets.

The three plays that fill an indie waitlist

Most of the “how to grow on X” advice optimises for follower count. Follower count is not the goal here; waitlist signups are. Three plays, run together, consistently move signups:

1. The build-in-public log. Post honestly about what you are building, three to five times a week.
2. Reply in the right threads. Answer questions your ideal customer is already asking, in the thread they are asking them in.
3. Share the counter. Post the waitlist number as it grows.

None of the three is a cold-DM play. Cold DMs on X have the worst signup rate of any channel I have tried and the worst reputational cost. Skip them.

Play 1: The build-in-public log

Three to five posts a week about the actual work. Not “here is my product” posts; posts about the things a real founder notices while building. Shapes that consistently land:

• The small win. “Just finally got the onboarding down from eight steps to three. Two days of work, three weeks of avoiding it.” Small wins read as honest and repeatable.
• The small loss. “Sent the launch email on Friday afternoon. Do not do that.” Losses land better than wins because they are useful to the reader who was about to make the same mistake.
• The question you had to answer. “Should you charge before product-market fit? I spent a week thinking about this and landed on yes, here is why in three tweets.” Answering your own question is a shape people follow and reply to.
• The screenshot with one sentence. A real feature ship, a real graph, a real customer email. One sentence of context. Screenshots are cheap trust.

The pattern that does not work: motivational posts, hot takes about other tools, and “here is my product (link)” posts. These read as noise even when they are sincere.

Play 2: Reply in the right threads

This is the highest-ROI move on X for indie waitlists and the one most founders skip. Someone asks a public question your product answers. You reply, in the thread, with a useful answer. The reader who asked, and everyone else reading the thread, sees you as someone who knows the space. A percentage of them click your profile, read your pinned post, and sign up for the waitlist.

The rules of the reply-in-thread play:

• The answer works even if your product does not exist. Give the useful answer first, mention your product second (or not at all in the same reply). A reply that reads as a sales pitch converts worse than a reply that reads as a genuine answer.
• Reply early, not late. A reply within the first hour of a thread lands in front of the original poster and the initial audience. A reply three days later lands in front of nobody.
• Reply where the audience already is. Threads with 50 to 500 replies are the sweet spot. A thread with 5,000 replies is noise; a thread with 3 is not enough audience for the effort.

Finding these threads by hand takes 15 minutes a day if you follow the right accounts. Tools that watch keywords and surface high-intent replies (Signals-style agents in SuperX, TweetHunter, or the built-in X search saved) can automate the discovery step so you spend the 15 minutes replying rather than scanning.

Play 3: Share the counter

If your waitlist page has a public counter (Lighthouse waitlists do, by default), post the number as it grows. Three shapes work:

• The milestone post. “100 signups. Weekend of quiet work.” Concrete numbers land as proof.
• The learning post. “Day 3 of the waitlist. 47 signups. The three things that drove the most: X reply in a big thread, a Show HN comment, a friend's retweet.” Naming the channels gives readers a reason to read.
• The near-cap post. If your waitlist has a soft cap or a charter-price offer for the first N, “12 spots left at the charter price” lands as a real signal, not a fake countdown.

The counter is a small, honest bit of social proof and it is the piece indie founders most consistently under- use. For the layout with the counter built in, see what to put on your waitlist landing page.

Turning an X impression into a signup

The plays above create impressions. The next job is to convert those impressions into waitlist clicks. Three things that consistently double the conversion rate from X to waitlist:

• Bio names the product and the audience. “Building [product], a [category] for [audience]. Waitlist below.” Not a job title, not a personal brand statement. Someone landing on your profile has two seconds to know what you do.
• Pinned post is the pitch, not a personal post. The pinned tweet should be your waitlist announcement with the link and a one-line pitch. Everyone who clicks your profile from a reply sees this next.
• Bio link is the waitlist landing page, directly. Not a Linktree, not your personal site with three pages between the visitor and the signup. The link should land on the page with the form. Every extra click halves the signup rate.

For the pitch itself, see how to write a one-sentence pitch for your indie SaaS. The pinned tweet is where that pitch has to work hardest.

What not to do

Four moves that consistently kill the X-to-waitlist channel and are worth naming so you can skip them:

• Cold DMs. A DM to someone who has not engaged with you is spam even if it is polite. Signup rates from cold DMs on X are near zero and the reputational cost is real: the recipient screenshots and quote-tweets it more often than they sign up.
• Tagged pitches on unrelated threads. Dropping @yourproduct into someone else's thread reads as hijacking. Reply with a useful answer instead and let the reader visit your profile.
• Engagement pods. Coordinated like-and-reply groups produce fake signals your audience notices. The algorithm has also gotten better at down-ranking obvious pod behaviour.
• Buying followers or engagement. A bloated follower count with low real engagement reads as a con to anyone actually looking. Zero waitlist signups come from this and the founders who do it usually stall the whole growth loop.

Frequently asked questions

How long before X starts producing signups?

Three to six weeks of consistent daily posting and replying, if the product is for the buildinpublic audience. Faster if you already have 500 to 1,000 followers in the space; slower if you are starting from zero. Signups arrive in clumps around specific replies or milestone posts, not evenly.

Do I need to have a follower count first?

No. The reply-in-thread play works with 50 followers. The build-in-public log builds the followers over time. The counter play works best with more followers, but the first two carry the weight for the first hundred signups.

Should I run paid X ads for a waitlist?

Almost never at indie budgets. Paid X for a waitlist costs $5 to $15 a signup and the signups usually do not convert at launch. Organic replies and build-in-public posts produce warmer signups at zero cost per signup. Save paid for after product-market fit.

What if I am raising alongside launching?

X is a public-audience channel, not an investor channel. Investors watch it, but the raise itself runs on direct outreach. Dedicated platforms like Funding Banker, a curated investor directory with pitch and outreach tracking, handle the investor side. Keep X for customer-audience signals; run the raise on its own track.

How does this fit organic growth more broadly?

X is one of four organic channels indie SaaS founders use for the first hundred signups. For the full channel-mix and the compounding math, see how to grow a waitlist organically. For where X fits in the twelve-step pre-launch shape, see the pre-launch checklist for an indie SaaS.

X fills an indie waitlist when the founder shows up consistently, replies usefully, and shares the counter honestly. It stops working when the founder tries to skip the trust-building step with cold DMs or tagged pitches. Slow, honest, in-thread: that is the three-word summary of the whole playbook.

Lighthouse gives you the waitlist landing page with the goal counter, the survey questions on the same form, the newsletter for keeping the list warm, and the feedback page for after you launch, in one place. Free trial, indie pricing. From the same indie dev behind Spaceport, a SwiftUI starter kit for shipping paid iOS apps fast.