Why build in public on X
Building in public turns your daily work into posts: you don’t have to invent topics, you report what actually happened.
The first payoff isn’t reach, it’s consistency. A founder who ships always has something to say: a feature out, a customer gone, a price changed, a wrong target. Nobody else can write those facts for you, and that’s what makes an account worth following.
The second payoff comes from how X ranks posts. The code X published predicts, for each reader, the probability of several actions and adds them up with weights; replies, quotes, sharing by DM and copying the link count far more than a like. A post about a real decision, with a number and an honest question, gives people a reason to reply and to send it to someone. The X algorithm guide has the full list of weights.
Building in public also gives you a clear identity: people know what you’re making, for whom, and where you stand. It’s personal branding on X applied to a project.
Cadence: small and steady beats rare and loud
A pace you can keep beats a big monthly story: one progress post a week, one recap a month, and events as they happen.
The For You feed keeps a post eligible for 48 hours, and it spaces out posts from the same author in one load: each extra post from the same account gets a lower score. Ten posts on launch day and then three weeks of silence loses twice. Spread it out.
- Weekly: one post about something you shipped or learned, with a specific detail.
- Monthly: a short recap (rounded numbers, what worked, what you’re changing).
- On events: a milestone, a release, a failure, a pricing decision.
- In between: replies to other founders in your niche, which matter as much as your posts (see the guide on replies and mentions).
For timing, start from the benchmarks in the best time to post guide, then measure on your own posts.
MRR milestones: share a number without bragging
An MRR milestone is interesting because of what made it possible: give the number, the time it took, and the causes.
The milestone post is the most expected format in build in public, and the most often wasted: a number, a rocket, a thank you. What people want is the cause. What changed between the last milestone and this one? A channel, a feature, a price, a different customer?
[Product] just crossed [milestone] in MRR. It took [time] since [previous milestone]. What actually made the difference: 1. [cause 1, with one specific detail] 2. [cause 2] 3. [what I stopped doing] What I’m changing for the next one: [decision].
Swap every bracket for your real numbers. If there’s no clear cause, say so: that’s an honest post too.
Round if you prefer (“just over $2k”), but never inflate. Someone will cross-check eventually, and a build in public account lives on its credibility.
You also don’t have to remember every milestone: Hypepen automations prepare a draft when your Stripe MRR crosses the threshold you set, or when you publish a GitHub release. The draft waits for your approval.
Releases: show what changes for the user
Tell a release from the user’s side: the problem it solves, before and after, then the technical detail for those who care.
“Version 2.4 is out” gives nobody a reason to stop scrolling. “You can now [do X] without [chore Y]” does. Keep the full list for your changelog and pick one change for the post.
Until today, [task] meant [painful steps]. Now in [product]: [what happens instead, in one sentence]. Why we built it: [what users told you or what you saw]. [Screenshot or short video of the new flow]
A screenshot or a clip beats a description: X also predicts photo expands and video opens.
Your product link can go in the post itself: X says links aren’t penalized. If you’d rather keep the post clean, put it in a reply right below.
Failures and hard calls
Failure posts are often the most useful in your series, as long as they end on a specific lesson rather than a confession.
A flat launch, a feature nobody uses, a price set too low: everyone goes through these and few talk about them. The structure that works: what you believed, what happened, what you’ll do differently.
I spent [time] on [feature or project]. [Honest result, e.g. almost nobody uses it]. What I believed: [assumption]. What the data says: [observation]. The rule I’m keeping: [concrete rule you’ll apply next time].
Don’t blame a customer or a competitor: reports and blocks are the most negative signals in X’s ranking.
Which metrics to track
Track your product metrics to feed your posts, and your X metrics to know which posts deserve a follow-up.
| Metric | What it tells you | What to do with it |
|---|---|---|
| MRR and active customers | Where the product stands | Material for recaps and milestones |
| Churn | Whether the value holds over time | A failure or a fix post |
| Replies per post | Whether the topic gets your niche talking | Write again on the same pillar |
| Follows per post | Whether the post makes people want more | Spot the topics that bring followers |
| Impressions | Raw reach | Compare to your own median, not others’ |
MRR and active customers
- What it tells you
- Where the product stands
- What to do with it
- Material for recaps and milestones
Churn
- What it tells you
- Whether the value holds over time
- What to do with it
- A failure or a fix post
Replies per post
- What it tells you
- Whether the topic gets your niche talking
- What to do with it
- Write again on the same pillar
Follows per post
- What it tells you
- Whether the post makes people want more
- What to do with it
- Spot the topics that bring followers
Impressions
- What it tells you
- Raw reach
- What to do with it
- Compare to your own median, not others’
Compare each post to the median of your own posts, never to a bigger account: it’s the only comparison that tells you whether a topic worked. The guide to getting followers without cheating covers how to read what makes people follow you.
Mistakes that wear your audience out
- The same milestone post copied every month: X forbids identical or near-identical posts.
- Bait (“like if you want part two”, “RT for the link”): it gets old fast, and Hypepen’s reach hints flag it.
- Numbers nobody can check, or rounded in your favor: once found out, they cost more than ten good posts earn.
- Ten-post threads for one idea: a long post or three posts are enough. To split cleanly, use the thread splitter.
- Talking only to other founders: if your product is for customers, write about their problems too, not just your metrics.
For more reusable structures, see the X post templates.
Frequently asked questions
Should I share my exact MRR?
No. A rounded number is enough to show progress. What matters is why it changed and what you decided next. Never post an inflated number.
Does building in public work before you have customers?
Yes. Before customers, you write about the problem, your interviews, your choice of target and price. Those posts often bring your first users.
How many posts a week?
One progress post a week and a monthly recap is a pace most founders can hold. Add events as they happen, and reply to others in between.
Can build in public posts be automated?
You can have a draft prepared automatically when something happens (a revenue milestone, a new release), as long as you read and approve it. X forbids duplicate posts and aggressive automation.