How to build in public on X (Twitter)

X is where the build-in-public community lives. The #buildinpublic hashtag is an ongoing feed of founders sharing revenue, launches, and failures — which means the audience is there, but so is every other founder posting "just crossed $10k MRR 🚀" with a cropped screenshot.

Standing out on X is less about volume and more about being specific, consistent, and verifiable.

What to post

• Weekly numbers with deltas. "MRR €480 → €540 this week" beats "great week!". Deltas make small numbers interesting — nobody expects you to be big, they want to see you moving.
• Milestones as they happen. Round numbers travel: first customer, 100 users, 1,000 stars. Post them the day they happen.
• Decisions and reversals. "We killed feature X, here's why" consistently outperforms feature announcements.
• Failures with numbers. A launch that got 12 signups is a better post than a launch that "went well".

Threads work for retros; single posts work for everything else. A chart or card image roughly doubles attention versus plain text.

Make it verifiable

The cropped-screenshot problem is real: self-reported numbers on X carry almost no weight anymore. The fix is linking every claim to a live page where the current numbers are visible — if your bio and every milestone post point to the same public metrics page, followers can check your trajectory anytime, and your history becomes your credibility.

The catch is that a bare link is a worse post than a screenshot. It's a blue URL nobody clicks. Share cards fix that: the link unfurls into the numbers, so you get the visual and the proof.

This is where infrapage fits the X workflow specifically:

• Your page link unfurls as a card. X pulls the page's social card into the post — you pick up to three metrics to feature, so a link-only post still shows MRR, stars, and users at a glance.
• Every public widget has its own share card. One number, one image, plus a README badge of the same metric. A single stat can carry a post on its own.
• Milestones and recaps get permalinks. Crossing 100 users or €1k MRR generates a celebration card at its own URL; the weekly recap card packages your week-over-week deltas for the Sunday update. Both pages carry a "Share on X" button with the post text pre-filled.

Paste once — the numbers stay live, so the card you embedded in a README last quarter isn't quietly lying today.

If X is the channel you're actually growing, there's an X Followers widget too, so audience sits on the same board as revenue and uptime. Honest limitation: it refreshes once a day on Pro and every three days otherwise, because every lookup bills X API credits. Fine for a weekly update, useless for watching a number tick.

The rhythm that works

1. One substantial update per week (numbers + one lesson).
2. Milestone posts whenever they genuinely happen.
3. Daily-ish replies to other builders — the community half is what grows the audience half.

That's it. For choosing which metrics to share at all — and how to share growth without exposing sensitive absolutes — start with the full guide to building in public.