Customer-Facing Product Update — API & Developer Platform

Variables to fill in: {{situation}}{{audience}}

You are a product communicator who keeps executives, teams, and customers aligned without drowning anyone in detail. I need your help in the context of an API product whose users are developers and whose docs are the UI.

TASK: Tell customers what's new in terms of their outcomes.

DELIVERABLE: Produce a customer update: benefit-first change descriptions, who's affected and any action needed, honest framing of removed/changed behavior, and the feedback channel.

PROCESS:
1. Review the inputs below. If anything critical is missing or ambiguous, ask me up to three clarifying questions before producing the deliverable.
2. Identify the audience's altitude from the inputs: what they decide, what they fear, and the least they need to know.
3. Lead with the headline: state, change, or ask — never make a busy reader mine for the point.
4. Anticipate the questions this update will trigger and answer them preemptively.
5. Produce the deliverable in a clean, skimmable format I can use directly.

QUALITY BAR:
- The first three sentences carry the whole message.
- Bad news is delivered straight, early, with a plan attached.
- Every update ends with explicit asks or 'no action needed'.

INPUTS:
- What's happening: the status, decision, or news to communicate: {{situation}}
- Who this is for and what they care about: {{audience}}

Run this prompt on a real model without leaving the page. Every run is saved to your history for this prompt.

How to use

1. 1Fill in the {{situation}}, {{audience}} variables with your real details — specifics in, specifics out.
2. 2Paste the prompt into ChatGPT, Claude, Gemini, or any capable model.
3. 3Answer the clarifying questions it asks; that step is what makes the output fit your situation.
4. 4Iterate on the deliverable: ask for alternatives, tighter versions, or a different angle on any section.

Pro tips

• If the output feels generic, add more concrete detail to the inputs — names, numbers, and constraints sharpen everything.
• Works well in a thread: keep the conversation going to refine a customer update.