Lesson 5 of 87 min read

Launches and feature announcements

Run a launch week across networks: teaser, launch day, follow-ups and proof, with a version written for each network and every link tracked.

In this lesson you will

  • Plan a launch week as a sequence, not a single post
  • Write a version of the announcement for each network
  • Tag every launch link so you can see which posts sent visits

Most SaaS launches on social are one post. It goes out on launch morning, it gets the likes it was always going to get from friends and teammates, and by the afternoon it has scrolled out of every feed. A week later nobody remembers the launch, and the team concludes that "social doesn't work for launches".

A launch is a week, not a post. Different people see your posts on different days, most of them need to hear about something more than once before they look, and the most convincing posts usually come after launch day, once there are real reactions and real questions to answer. This lesson lays out a launch week, shows how to write per-network versions, and makes sure every link is tagged so you can tell afterwards which posts did the work.

What deserves a launch week

Not every release deserves a week. Use a simple rule:

  • Launch week: a new product, a new plan or offer, a major feature that changes who the product is for, or a feature your buyers have asked for publicly.
  • Feature announcement (one to three posts): a meaningful improvement existing users will notice.
  • Changelog post only: fixes, small improvements, polish.

If you run a launch week for every release, your audience learns to ignore launch weeks. Two to four a year is plenty for most small SaaS teams.

The shape of a launch week

Here is a seven-day sequence. Day 0 is launch day.

DayJobExample post types
Day -3Tease the problemThe "before" from your positioning, without naming the feature
Day -1Signal the date"Shipping tomorrow: here's what it fixes"
Day 0LaunchThe announcement, per network; a short demo; the founder's "why"
Day +1Answer questionsThe three questions you got most on launch day, answered in public
Day +2Show it workingA walkthrough, a how-to, a before/after
Day +3ProofA reaction you have permission to share, or a specific use case
Day +5RecapWhat shipped, what's next, one link

Two things make this work:

  1. Each day has one job. A teaser that also explains pricing and asks for signups does all three badly.
  2. The days after launch are planned in advance but written on the day. You know Day +1 is "answer questions"; you write it once you know the questions.

One announcement, written for each network

Copy-pasting the same announcement everywhere is the most common launch mistake. Each network has a different reader and a different format. Start from one core message, then adapt.

The core message has four parts: what is new, who it is for, what it changes for them, and where to try it. Then:

  • LinkedIn: the full version. Lead with the problem, then the change, then one link. Line breaks between short paragraphs. The link can go in the post; test whether your audience responds better to it there or in the first comment.
  • X: a short post with the outcome in the first line, or a thread: problem, what's new, how it works in two or three posts, link at the end.
  • Bluesky: close to the X version, reworded, a little more conversational.
  • Instagram: the visual leads. A screenshot or short clip, a caption that starts with the outcome, link in your bio rather than the caption.
  • Your community (Discord or Slack): short, direct, and ends with a question or an invitation to try it and report back.
  • YouTube or TikTok: only if you have a real demo. A 30-to-60-second clip of the feature doing its job beats a talking head.

If you link to your site on launch day without tagging the links, your web analytics will file most of the visits as "direct" or a generic referral, and you will not know whether LinkedIn or X sent them. Tagging fixes this.

Use UTM parameters on every link you post:

  • utm_source: the network (linkedin, x, bluesky, discord, instagram)
  • utm_medium: social
  • utm_campaign: the launch name, the same on every network (for example, launch-week)
  • utm_content (optional): which post, if you post the link more than once (for example, day0-founder, day2-howto)

Rules: lowercase only, dashes not spaces, and write the values down before launch week so everyone uses the same ones. A tag typed as "LinkedIn" on one post and "linkedin" on another shows up as two sources.

The smaller version: a feature announcement

Most of your releases will not get a launch week. For a meaningful feature, use a compressed version of the same idea: one to three posts over a few days.

  1. The announcement on launch day, per network, with a tagged link.
  2. The how-to two or three days later: one concrete way to use it, with a screenshot.
  3. The answer a week later, if real questions came in: the most common one, answered in public.

A template for the announcement that works on most networks:

[The problem in one line, in the buyer's words.]

[What's new, in one or two lines. What it does, not what it's called.]

[Who it's for, or when to use it.]

[One link.]

Before and after, using a hypothetical feature. Say you run an invoicing tool and you shipped automatic payment reminders.

Before:

We're excited to announce Smart Reminders, our powerful new feature that
streamlines your accounts receivable workflow!

After:

Chasing late invoices by hand is the worst part of a Friday.

Invoices can now send their own reminders: a polite one on the due date,
a firmer one a week later. You choose the wording once.

For anyone who has ever put "follow up on invoices" on a to-do list.

[link]

The first version names the feature and says nothing. The second names the problem, says what happens, and tells the reader whether it is for them.

The launch-day checklist

Launch day goes wrong in small, predictable ways. Check these the day before:

  • Every link opens the right page, logged out, on a phone.
  • Every link carries its UTM tags, with the agreed values.
  • Every post has been through approval (lesson 2).
  • The landing page, docs and pricing say the same thing as the posts.
  • Someone owns replies for the whole day, on every network (lesson 7).
  • Nothing else is scheduled that day that would compete with the launch.

Worked example: our plan for launch week

Our public launch is planned for 7 December. What follows is our plan, written ahead of time, not a report of how it went. We will know that after the week, and lesson 8's report template is how we will read it.

Our launch is about an offer more than a feature: the founding offer, the money-back guarantee, and the idea on our homepage that your AI agent can plan, write and schedule your posts while you approve everything in one calendar. Following the table above, our week is shaped like this:

  • Day -3: the problem. Posting in only one place, because rewriting one idea for each network takes time nobody has.
  • Day -1: the date and what's coming, on X, LinkedIn and Bluesky.
  • Day 0: the announcement on every account, a short product clip, and a note in our Discord.
  • Day +1: answers to the questions that came in on launch day.
  • Day +2: a walkthrough: connecting your coding agent through our AI agents page and asking it to draft a week.
  • Day +3 and +5: a how-to from our free tools, and a recap.

Two of our drafted Day 0 posts. The X version:

Today we launch FoPost.

Describe a campaign to your AI agent. It plans the posts, writes a native
version for every network you connect, and puts them on one calendar.
Nothing publishes until you approve it.

[link tagged utm_source=x&utm_medium=social&utm_campaign=launch-week]

The Discord version:

We're live today. If you try it and hit anything odd, post it here with a
screenshot, and tell us which network you were posting to.

Note what is not in either: no numbers we do not have yet, no claims about results. The Day +3 proof post stays empty in our plan until there is real proof to put in it.

After the week

On Day +7, do a short review while it is fresh:

  • Which network sent the most tagged visits, and which sent the most signups?
  • Which day's post did best: the launch post, or a follow-up?
  • Which questions came up more than twice? Those are next month's how-to posts.
  • What would you cut next time?

Write the answers down. Your next launch week starts from them.

Recap

  • Reserve launch weeks for big changes, two to four a year; smaller releases get one to three posts.
  • A launch week is a sequence with one job per day: tease, signal, launch, answer, show, prove, recap.
  • Write a version for each network from one core message; never copy-paste.
  • Tag every link with consistent, lowercase UTM values agreed before the week starts.
  • Plan the proof post, but only fill it with real proof.

Exercise

Build a launch-week kit

  1. Pick your next launch or major feature and write the core message: what's new, who it's for, what it changes, where to try it.
  2. Fill in the seven-day table above with one post idea per day.
  3. Build a tagged link for each network you will post to with the UTM generator, using the same campaign value on every one. Save the links in a list.
  4. Write the Day 0 post for LinkedIn and X, then a version for Instagram, and check how the Instagram caption and image read with the Instagram post preview.
  5. Write the three questions you expect on launch day, so Day +1 has a head start.

Done looks like: a seven-day launch plan, a list of tagged links (one per network), Day 0 drafts for three networks, and three expected questions.

Go further

Per-network versions in the composer

In the FoPost composer, write the core announcement once, pick every network you connect, and let AI rewrite it for each one; then edit any network's version on its own without touching the others, and check each one in its preview before you schedule. Paste your tagged links into each version so every network carries its own source. See the composer for how per-network versions and previews work.

Check yourself

  1. 1Why are the days after launch day planned in advance but written on the day?

    You know their job ahead of time, such as answering questions, but the content depends on what actually happens on launch day.

  2. 2What goes wrong if one post tags a link "LinkedIn" and another "linkedin"?

    Your analytics treat them as two different sources, so your launch numbers get split and are harder to read.

  3. 3What belongs in the proof post if you have no real proof yet?

    Nothing. Leave it empty or replace it with a how-to; never invent results or reactions.

Academy

Keep reading, free

Tell us a little about you and the rest of this lesson, and every lesson in every course, opens on this device. No account and no card.

What describes you best?
Where do you post today? Pick any that apply.
What do you want most right now?

We use your answers to suggest lessons and to improve the Academy. They are never shown publicly. Read our Privacy Policy.