X — number plus context
[Product] just passed [number] [users / customers / stars]. It took [time]. The first [smaller number] took [longer time]. What moved the line: [one specific thing, e.g. a feature, a post, a partner]. Thank you to everyone who [used it early / sent feedback].
LinkedIn — lessons behind the number
[Number] [customers / users] as of this week. A few things I did not expect on the way here: 1. [Lesson 1, e.g. the channel that worked was not the one we planned] 2. [Lesson 2] 3. [Lesson 3] The number is nice. The part I care about more is [a quality metric, e.g. how many are still active after 90 days]. Thanks to [customers, team, investors] for the trust. On to [next goal].
Mastodon — community milestone
[Project] reached [number] [stars / contributors / downloads]. It started as [origin in one line]. Today [number] people have contributed code, docs, or bug reports. If you have ever filed an issue: thank you. That is how it got better. #[ProjectTag] #OpenSource
Bluesky — short thank-you
[Number] [users] for [Product] today. Built by [team size] people over [time]. Thanks for every bug report and kind word along the way.
Tips
- Share how long the milestone took. A number without a timeline invites skepticism; a timeline makes it a story.
- Only post numbers you are willing to have checked. Round down rather than up.
- Name one concrete thing that moved the metric so the post teaches something instead of only celebrating.
- Pick milestones your audience understands. Customers mean more to buyers; contributors mean more to open source readers.
Frequently asked questions
Is it bragging to post a company milestone?
It reads as bragging when the post is only the number. Adding what you learned, how long it took, and who helped turns it into a useful story for other builders.
Which milestones are worth a post?
Round numbers your audience recognizes, first paying customer, first year, and any number that shows real use rather than vanity metrics like page views.