Product launch announcement

Write a clear launch announcement for a blog post, email or LinkedIn, built around the customer problem rather than hype.

Change note: Initial version

Prompt

Write a launch announcement for {{product_name}}.

Channel and format: {{channel}}
What is launching: {{what}}
Who it is for: {{audience}}
The problem it solves: {{problem}}
Key features and what each does for the user: {{features}}
Availability, pricing and any launch offer: {{availability}}
Call to action: {{cta}}
Voice: {{voice}}

Structure
1. A headline (give three options) that states what is new and why a reader would care. No "Introducing" unless it is the clearest option.
2. An opening of two or three sentences describing the problem as the reader experiences it, then what we built.
3. A short section on the most important capabilities, each tied to a concrete outcome. Maximum {{max_features}} items.
4. One honest sentence about who it is for and who it is not for yet, if the information supports that.
5. Availability and pricing, stated plainly.
6. A single call to action.

Constraints
- Only use facts I provided. Do not invent customer quotes, numbers, awards or roadmap promises. Use [placeholder] where I should add a quote or metric.
- Avoid: "game-changing", "revolutionary", "excited to announce" (use a specific, human opener instead), and exclamation marks.
- Match the length to the channel: email under 250 words, LinkedIn under 200 words, blog 400-600 words.

Variables

• {{product_name}}Product nametext

  Default: Plotline Capacity View

• {{channel}}Channelselect

  Options: Customer email, Blog post, LinkedIn post, Product Hunt description, Press release

  Default: Customer email

• {{what}}What is launchinglong

  Default: A new view that shows each team member's workload by week across all projects, with automatic overbooking alerts.

• {{audience}}Who it is fortext

  Default: Project leads at small design and creative agencies

• {{problem}}The problem it solveslong

  Default: Leads find out someone is overbooked only after a deadline slips.

• {{features}}Features and outcomeslong

  Default: Weekly workload heatmap: spot clashes at a glance. Overbooking alerts: get warned when a plan exceeds someone's capacity. Calendar sync: capacity reflects real leave and meetings.

• {{availability}}Availability and pricingtext

  Default: Live today for all paid plans at no extra cost

• {{cta}}Call to actiontext

  Default: Open Capacity View in your workspace

• {{voice}}Voicetext

  Default: Plain-spoken, practical, a little dry

• {{max_features}}Max features to mentionnumber

  Default: 3

Example output

**Headline options**
1. See who is overbooked before the deadline slips
2. New: Capacity View shows team workload by week
3. A clearer view of who has room to take on work

Subject: Know who is overbooked before it costs you a deadline

Most project leads learn that someone is overloaded when a deadline has already slipped. By then the options are overtime or an awkward email to the client.

Today we are releasing Capacity View in Plotline. It shows each person's workload by week across every project, so clashes are visible while you can still move things.

What you can do with it
- **Spot clashes at a glance.** A weekly heatmap shows who is light and who is stretched.
- **Get warned early.** Overbooking alerts fire when a plan exceeds someone's capacity.
- **Trust the numbers.** Calendar sync means leave and meetings reduce capacity automatically.

It is built for project leads at small creative agencies. If you plan work for one or two people, it may be more than you need; for teams of five and up, it should pay off quickly.

Capacity View is live today on all paid plans at no extra cost.

[Open Capacity View in your workspace]

[placeholder: add one customer quote or early-access result if you have one]

Notes

The prompt forces a problem-first opening and bans the usual launch clichés, which makes the result read like a person wrote it. Run it once per channel to get properly sized versions.