Skip to the feed
BizHub
Post a launch

Milestones Worth Announcing, and How to Word Them

Community · 8 min read ·

Which milestones deserve an announcement, which do not, and how to word them honestly so followers celebrate with you and learn something.

Illustration: A path with small flag markers at each milestone, avatar bubbles cheering along the side, soft blue and peach

A milestone is a mark on the road: a place where you can look back and see how far you have come. Founders often feel awkward about announcing them. It can feel like boasting, or like tempting fate. Yet milestones are among the most valuable things you can share with a community, because they give people a reason to celebrate, to learn and to remember why they follow you.

This article helps you decide which milestones to share, how to word them and how to do it without feeling uncomfortable.

Why announce at all

Announcements do three useful things.

They tell people you are alive and moving. Customers and followers like to see that a business is active.

They invite celebration. People enjoy marking good news. A thank-you after a hundred users or a first year builds goodwill.

They teach. A milestone with its story attached shows others how you got there and what to try.

Wikipedia's description of online communities notes that such communities rely on members receiving benefits that compensate for the costs of taking part. Sharing a milestone is a way to give back: it offers the community a story, a lesson or a reason to smile.

Which milestones are worth sharing

Not everything needs an announcement. Choose those that matter to your audience.

Product milestones

  • A first public launch or beta
  • A major release or a feature people asked for
  • Reaching a new platform
  • A relaunch with significant changes

Customer milestones

  • Your first paying customer
  • A round number of users, said honestly
  • A notable customer, with permission
  • A story about what a customer achieved with your product

Team milestones

  • Your first hire
  • A new partner or adviser
  • A move to a new office or a shift to remote working
  • Someone leaving, with thanks

Business milestones

  • An anniversary
  • Profitability or a milestone in revenue, if you choose to share
  • Funding, if you have it and want to say
  • An award or ranking, described accurately

Learning milestones

  • A big mistake and what you changed
  • A pivot, and why
  • A decision to stop something

Learning milestones are often the most useful, because they carry the lessons.

What not to announce

  • Vanity numbers with no meaning. Page views, impressions or downloads that do not reflect real use.
  • Unconfirmed news. Wait until a deal is signed.
  • Other people's news. Ask permission before sharing someone else's milestone.
  • Things that could harm customers or colleagues. Redundancies, for example, deserve care and timing.
  • Routine events. Not every release deserves a headline.

Word it honestly

How you say it matters as much as what you say.

Be exact about what you counted

"We reached ten thousand users" could mean sign-ups, active users or visitors. Say which: "Ten thousand people have created an account, and about two thousand used the product in the past month." Honest precision builds trust.

Goodhart's observation, that a measure used as a target stops being a good measure, warns against chasing round numbers for their own sake. If you push to hit a figure for an announcement, check you have not harmed the thing that figure was meant to represent.

Do not exaggerate

Avoid "explosive growth", "viral" and "game-changing". Describe what happened. "Sign-ups doubled in March after we changed the pricing page" is more convincing than "huge growth".

Say who helped

Thank customers, teammates, early supporters and anyone who gave advice. It is generous and accurate, since few milestones are reached alone.

Add the lesson

A milestone with a lesson is a gift. "The thing that made the difference was replying to every sign-up personally in the first week" gives readers something to try.

Include the cost

If something was hard, say so. "It took eighteen months and one failed prototype." It reminds people that success is rarely smooth.

Keep the tone proportionate

A first customer is a big day for a founder, though it is a small piece of news for the world. Share it warmly, without pretending it is more than it is.

A simple structure

  1. The news in one sentence. "We shipped version one."
  2. What it means. "People can now import their data and share reports."
  3. The story. Three or four sentences about how you got there.
  4. The thanks. Name people where appropriate.
  5. The lesson. One thing you learned.
  6. What is next.
  7. A prompt. "If you try it, tell me what confuses you."

Examples of wording

First customer: "Today a small bakery in Leeds became our first paying customer. She found us through a post in a local group and asked three questions before buying. I answered each one the same day. Thank you, and thank you to the person who shared the post."

One year: "A year ago I wrote our first line of code. Since then we have shipped forty releases, lost two customers and learned that nobody reads the settings page. Thank you to the early users who put up with the bugs."

Setback: "We have decided to stop supporting the mobile app. Usage was low and it was draining time from the main product. If you used it, I am sorry. Here is how to export your data."

Time it well

  • Share soon, while the story is fresh, but not before you are sure.
  • Avoid clashing with other major news in your community.
  • Spread them out. A steady trickle of milestones works better than a flood.
  • Revisit. On an anniversary, look back at earlier milestones to show progress.

Share it where people will see it

Post it on your own site and as a milestone or update on your listing, and mention it in your next update. If your milestone involves a launch, make sure your listing is up to date. The launches page shows what is happening in the community, and the about-the-founders page shows a plain introduction of two founders.

Celebrate other people's milestones

Communities thrive on mutual encouragement. When someone you follow announces a milestone, congratulate them with something specific: "I remember when you were still testing the prototype. Congratulations." It costs nothing and means a lot. Over time, the habit of cheering for others makes your own announcements feel natural.

Common mistakes

  1. Inflating numbers.
  2. Announcing too often.
  3. Forgetting to thank people.
  4. Making it all about you.
  5. Hiding the difficult parts.
  6. Leaving out what is next.

A worked example: a first-year post

Imagine the founder of a small accounting app writing a one-year post. She starts with the news: "Tallyup is one year old today." She explains what that means: "A year ago I had a prototype and no customers. Today about three hundred small businesses have used it in the last month." She is careful to say what she counted and notes that two hundred of those are on the free plan.

Next comes the story: the first customer, an electrician she met at a networking breakfast; the month when a bug lost a day of data for six users and what she did to put it right; the decision to stop adding features and spend a quarter on reliability. She thanks the electrician by first name, with his permission, and the six users who forgave her.

Then the lesson: "The best thing I did all year was ring every customer who cancelled. Four of them told me the same thing, and fixing it brought two back." Finally, what is next: a simple invoicing feature, and a question: "If you are a sole trader, what is the most annoying thing about doing your own books?"

The post is warm, honest and useful. It avoids exaggeration, gives credit and invites participation. It is also easy to write once you have the habit of keeping notes through the year.

Keep a milestone log

Make a simple running list in a notes app. Each time something happens that you might want to mention, add a line with the date and a few words. At the end of each quarter, read the list and decide which items deserve a post. The log also helps when you prepare for anniversaries, investor conversations or interviews, because you will not have to rely on memory.

When a milestone is a goodbye

Not every milestone is a celebration. Sometimes you will close a product, end a partnership or wind down the company. Announcing it plainly and kindly is a mark of respect for customers and followers. Say what is happening and when, explain what it means for them, tell them how to export their data, thank the people who supported you and, if you can, say what you will do next. A graceful ending is remembered long after the product itself, and it often leads to the next opportunity.

Frequently asked questions

What if my milestone is small? Small milestones, honestly shared, often get the warmest responses.

Should I include numbers? Include those you are comfortable with and can explain.

Is it fine to announce a milestone and ask for something? Yes, if the ask is modest and relevant, such as feedback or an introduction.

Questions and answers

Which milestones are worth announcing?
Those that mark a real change for customers, the team or the community: a launch, a first customer, a major release, a new hire, an anniversary or a lesson learned.
Is it showing off to announce a milestone?
Not if you share what it took and who helped. Thanking people and sharing the lesson turns a boast into a story.
How do I avoid inflating numbers?
State exactly what you counted and when, such as active accounts in the last thirty days, and do not round up.
Should I announce setbacks?
When they matter to your community, yes. Honest updates about setbacks often earn more respect than successes.

Sources

Related guides

Get help