Argus for build in public
Building in public is a distribution strategy that most people run as a journal. You ship, you write the honest update, you post it, and the same forty people see it. The log compounds. The audience doesn't. Argus is for the second half: it reads your real funnel, tells you which live conversations are worth 20 minutes of replies today, and drafts them in your voice, so by launch day there are people on the other end.
The job to be done
Building in public is supposed to buy you three things: early users who care, a feedback loop that stops you building the wrong thing, and an audience that is already warm when you launch. All three depend on one input - people outside your existing followers seeing the work. Miss that and you are keeping a changelog with extra steps.
The trap is that the work you can control (shipping, writing the update) is not the work that gates the outcome (reach). So you ship harder and write better hooks, both graphs stay flat, and after three months you conclude build-in-public doesn't work. It does. You were pulling the wrong lever.
Why your posts alone won't do it
Below roughly 10k followers, a post on your own timeline is mostly served to people who already follow you. Those people have already read four updates about the same feature. The impressions look like reach but almost none of it is new. A reply under someone else's rising post is the opposite: it puts you in front of an audience that has never seen you, at the moment they are actually reading. That is out-of-network reach, and at your size it is the only reliable source of it.
Which is why the build-in-public accounts that actually grow are not the ones posting the most updates. They are the ones replying every day in the rooms their future users are already in. The full argument is in the reply-first playbook and applied specifically to shipping in public in building in public on X.
What Argus does for it
- Tells you whether the updates are working. It rebuilds your real funnel from the analytics X already shows you - reach, profile visits, follows, saves - so you can see which stage leaks. An update that gets seen and converts nobody is a positioning problem. An update nobody sees is a reach problem. They need opposite fixes, and guessing which one you have is how three months disappear.
- Ranks live posts by reply opportunity. It scores posts as they land, reach-led and early-mover, so you show up under a rising thread while it is still climbing and before fifty people have said the same thing. That is the difference between a reply that gets read and one that gets buried.
- Drafts in your voice. It learns from your own best posts and writes a reply you insert with one click. Building in public only works if it sounds like a person building something, so the drafts are yours to edit, not generic engagement filler. AI drafting is optional and runs on a key you bring.
- Never automates. Everything is draft-and-insert. You press send on every single thing. The account you are building in public on is the asset, and automating actions on it is the fastest way to lose it.
What it does not do
Argus does not write your updates. It has no scheduler and no queue. It will not tell you what to build. The specifics of what you shipped, what broke, and what a number actually was - that is the entire reason anyone follows a build-in-public account, and it has to come from you. Argus handles getting those specifics in front of people.
Common questions
Why do my build-in-public posts get no traction?
Almost always because of reach, not writing. At a few hundred followers a post mostly circulates inside the people who already follow you, and they have already seen four updates about the same feature. The fix is not a better hook, it is getting in front of people who are not following you yet. That is what replies under rising posts do and what a post on your own timeline cannot.
How often should I post build-in-public updates?
Post when something real happened, not on a schedule. The compounding comes from the replies in between, which you can do daily without needing anything to have shipped. A useful shape is a few substantial updates a week plus consistent replying every day.
Does Argus write my build-in-public posts for me?
No. Argus drafts replies, not your updates. The updates should be yours, because the specifics are the whole reason building in public works. What Argus handles is the distribution half: which conversations to show up in, and a draft in your voice so 20 minutes of replying is actually 20 minutes.
Does Argus auto-reply or auto-follow?
No. Argus is draft-and-insert only. It never auto-posts, auto-replies, auto-follows, or auto-likes. You read every draft, edit it, and press send yourself. Automating the send button is the fastest way to get the account you are building in public on restricted.
See also: Argus for indie hackers · building in public on X · how Argus works
ship in public, then show up.
New here? Start on the Argus home page.