SaaS launch blog post prompt

When to use it

Use this when you need a launch blog post and want a concrete starting point rather than generic advice. Replace the fictional details with your own confirmed facts before using the result in a real setting.

The prompt

## Role
Act as a product launch writer. Apply professional judgment while keeping your reasoning understandable to someone who is not a specialist.

## Context
CedarFlow is launching a shared approvals workspace for small creative agencies. Its features are version history, named reviewers, and deadline reminders. The starter plan costs $29 per workspace monthly. A 14-day trial needs no credit card. No customer performance data exists yet.

## Objective
Introduce the product through the familiar problem of feedback scattered across email, then explain how one approval cycle works.

## Audience
The primary users are product marketers. Make the deliverable usable in their day-to-day work, with enough explanation to support decisions but no unnecessary background lecture.

## Requirements
A 650–800-word post; a headline and two alternatives; a short opening scene; three benefit-led sections; a clear trial invitation. Distinguish available features from hoped-for outcomes. Use a claim-to-feature check after the draft, identifying any sentence that still needs verification.

## Constraints
Do not invent integrations, customer quotes, adoption statistics, security certifications, or time-saving percentages. Work only with the scenario and any material explicitly supplied. Label assumptions and distinguish proposed actions from confirmed facts.

## Tone & style
Be direct, thoughtful, and specific. Prefer plain English, concrete examples, and short paragraphs. Match the language to the intended reader rather than relying on jargon or generic motivational phrasing.

## Output format
Present the requested deliverable first, using descriptive headings and tables only where they improve usability. Keep supporting notes separate from copy intended for publication or direct use. Finish with a short checklist of outstanding decisions or verification steps.

## What to avoid
Avoid filler, unsupported certainty, and details invented to make the result seem more complete. Do not let a polished presentation conceal missing information or conflicting requirements.

## Success criteria
A reader can explain who CedarFlow serves, what it does, what it costs, and what to do next. Check the result against the stated constraints before presenting it and correct any inconsistencies you find.

## Clarifying questions
Ask up to three focused questions only if missing information would materially change the result. Otherwise proceed with the fictional scenario, state any necessary assumptions briefly, and identify what a real user should confirm before relying on the output.

Why it works

• The scenario gives the model concrete facts and boundaries instead of asking it to invent a brief.
• The requirements specify the actual deliverables and the important edge cases for this task.
• The constraints make unsupported claims and unapproved commitments harder to slip into the result.
• The success criteria turn review into a practical check: a reader can explain who CedarFlow serves, what it does, what it costs, and what to do next.

Make it yours

Build a tailored version with PromptDeck by replacing the fictional scenario with your own context, audience, and constraints. Keep the verification steps so the final result reflects what you actually know.