X still works for founders.
The game just changed.

"I posted for three months and nothing happened" and "X works great for us" are both accurate reports from the same platform. The first group was broadcasting to a follower count that can't carry anything yet; the second was replying, borrowing distribution from conversations that already had it. For a small account, replies are the offense and posts are the archive.

The feed runs on velocity: what a post earns in its first hours decides how far it travels, which makes timing a real variable (a great reply on a six-hour-old post is a note passed to a crowd that already left) and makes conversation beat applause. The reply that opens an exchange outperforms the reply that closes one.

Find a rising post in front of your buyers, write the best reply in the thread, and let its momentum carry your words. Three disciplines separate this from reply-guy farming: ride conversations in front of your buyers (curate a list of the creators and operators they follow), hold the relevance floor absolutely (an off-topic reply on a viral post teaches readers only that you interrupt), and catch posts early, measuring takeoff against that author's own baseline rather than raw numbers.

The reply itself is additive, not clever: extend the point, disagree usefully, write in your voice at conversational length, and almost never mention your product. The payoff is profile visits from people who liked how you think.

The accounts that grew from zero treat the minutes after posting as the job: every reply gets a reply, fast. Author replies stack engagement in exactly the window that shapes a post's trajectory, and visible presence changes reader behavior: people comment where the author writes back. Post when you can stay, not when a scheduling tool says engagement peaks.

The part founders miss: everyone who replies to your post about the problem you solve just self-selected. The substantive replier is a conversation already started; the recurring name is sustained interest on the record. Borrowed rooms (riding) and your own room are two halves of one engine: riding without an own-room leaks, own-room without riding starves.

X rewards showing up a lot, and it suspends accounts that show up like machines, frequently without warning. The patterns that recur in suspension post-mortems are all timing: bursts, metronome regularity, round-the-clock activity, and sudden volume cliffs. Content quality is not a safety margin.

The rules: a boring daily ceiling, irregular spacing across your waking hours, gradual ramps for any change, and one account, really. The volume tools that promise dozens of replies a day produce exactly the burst-and-metronome shape the machinery hunts, with your account as collateral.

Worked example · Thread Otter enforces the rhythm structurally: daily ceilings per account, irregular spacing, quiet hours in your timezone, and automatic backoff at the first sign of platform pushback.

Somewhere in today's firehose, someone asked for exactly what you build. The craft is writing keywords the way buyers type when they want something: problem phrases beat category terms, question shapes ("is there a tool") flag intent, and competitor names with frustration attached are the highest-intent strangers on the platform. Narrow beats broad, always.

Then skip most of what you catch. In one ten-hour window we measured, 770 keyword mentions contained exactly 2 real buying conversations. Separate the watching from the responding: the watching is mechanical and should run continuously without you; the responding is judgment, cleared in a few short passes inside your normal rhythm.

X quietly became a publishing surface, and the correct use is canonical-plus-native: the full piece lives on your blog (owned, searchable, yours), and a genuinely reformatted version ships on X with a pointer back. Feed natives who would never click out to a blog still get your depth, and a prospect who has read two thousand words of your thinking arrives pre-sold in a way no volume of replies produces.

Reformat, don't dump: the first line does everything, structure for the swipe, strip mid-body links, and cut to the strongest arc. One real essay a week riding the blog work you already do, plus daily short-form presence, is a complete content system.

Cold DMs on X die in the message-requests folder, previewed as one line of selling and swiped away. The doctrine: a DM continues a public interaction, never opens one. The ladder is surfaced, engaged publicly, engaged back, thread exhausted; at that rung the DM is natural and often welcomed. Anchor it to the thread, deliver something, ask nothing, keep it to a few sentences, and let the call emerge instead of forcing it.

The channel is small on purpose: a handful of genuinely warm conversations a week closes more business than fifty cold blasts, and you still have the account in a year.

The whole machine compresses to four motions: host your room (one post most days, every reply answered), ride the right threads (a few anchor replies), clear the signal queue (skip most of it), and advance the warm conversations. Thirty minutes of founder time, but only if the finding is already done: the unbudgeted hour of locating what deserves a reply is the part that breaks the manual version, inside an interface engineered to make locating take forever.

Sort every task by one question: is it priced by its humanity? The watching, triage, and queueing are not, and should be automated. The opinions, the judgment calls, and human-rhythm sending are, and should never be delegated.