AI prompts for writing covers a curated set of copy-ready prompts for anyone who writes at work: team leads drafting updates, marketers building campaigns, managers coaching their reports through a first draft. This page gives you prompts organized by writing task, real captured outputs so you know what to expect, and guidance on adapting each prompt for your team. It works with ChatGPT, Claude, Copilot, and Gemini.
What is in this pack
This pack contains 20 prompts organized into five categories: drafting and editing, tone and style, emails and messages, reports and summaries, and creative briefs. Each one is written to be copied and used immediately, with variables in brackets so you can swap in your own details.
The prompts are aimed at professionals who write regularly but do not think of themselves as writers. A product manager turning a spec into a stakeholder email. A team lead condensing a messy meeting into a clear summary. A marketer who needs a first draft in ten minutes, not forty.
For prompts organized by role rather than task, the full prompt library by role is a good starting point.
The prompts, by category
These 20 prompts cover the writing tasks that come up most often across marketing, operations, and general business communication. They're organized by output type so you can scan quickly. Prompt blocks use [BRACKETS] for every variable you'll need to replace before sending.
Category overview
| Category | Prompts | Best for |
|---|---|---|
| Drafting | 5 | Emails, announcements, briefs |
| Editing | 4 | Tightening, tone-fixing, plain language |
| Structuring | 4 | Outlines, reports, documentation |
| Persuasive writing | 4 | Proposals, pitches, landing copy |
| Summarizing | 3 | Meeting notes, long docs, research |
One honest caveat before you start: these prompts work well for first drafts and structural edits, but they consistently underperform on writing that depends on institutional knowledge or voice built over years. If your brand has a genuinely distinctive style, treat every output as a raw draft and edit it yourself rather than publishing directly.
Drafting
Write a professional email from bullet points
When to use: You have the key points but no time to write the email. Change first: The tone variable. "Direct" and "warm" produce noticeably different results.
Variables: [RECIPIENT ROLE], [YOUR ROLE], [KEY POINTS AS BULLETS], [DESIRED TONE: direct/warm/formal]
Write a professional email from these bullet points.
Recipient: [RECIPIENT ROLE]
Sender: [YOUR ROLE]
Tone: [DESIRED TONE]
Key points:
[KEY POINTS AS BULLETS]
Write a subject line, then the email body. Keep the email under 150 words. Do not add pleasantries that are not implied by the bullet points.Write a team announcement for a process change
When to use: A workflow, tool, or policy is changing and people need to know why. Change first: The "what changes" and "why it matters" fields. Vague inputs produce vague announcements.
Variables: [CHANGE DESCRIPTION], [EFFECTIVE DATE], [WHO IS AFFECTED], [REASON FOR CHANGE], [NEXT STEP FOR READER]
Write an internal team announcement about a process change.
Change: [CHANGE DESCRIPTION]
Effective: [EFFECTIVE DATE]
Audience: [WHO IS AFFECTED]
Reason: [REASON FOR CHANGE]
What the reader should do next: [NEXT STEP FOR READER]
Tone: clear and direct. No corporate filler. Under 120 words.[NEEDS REAL OUTPUT]
Draft a project kickoff email
When to use: Kicking off a new project with stakeholders who need context fast. Change first: The goals field. One specific goal produces a sharper email than a list of four.
Variables: [PROJECT NAME], [PROJECT GOAL], [KEY STAKEHOLDERS], [TIMELINE], [FIRST ACTION REQUIRED]
Write a project kickoff email.
Project: [PROJECT NAME]
Goal: [PROJECT GOAL]
Stakeholders: [KEY STAKEHOLDERS]
Timeline: [TIMELINE]
First action required from recipients: [FIRST ACTION REQUIRED]
Keep it under 200 words. Lead with the goal, not the background.Write a follow-up email after a meeting
When to use: Within 24 hours of any meeting where decisions were made or actions assigned. Change first: The decisions and owners fields. Incomplete inputs here are the most common cause of weak follow-ups.
Variables: [MEETING TOPIC], [DATE], [ATTENDEES], [DECISIONS MADE], [ACTION ITEMS WITH OWNERS AND DEADLINES]
Write a follow-up email summarizing a meeting.
Topic: [MEETING TOPIC]
Date: [DATE]
Attendees: [ATTENDEES]
Decisions: [DECISIONS MADE]
Action items (owner, deadline): [ACTION ITEMS WITH OWNERS AND DEADLINES]
Use a short intro, then a bulleted decisions section, then a bulleted action items section. Do not editorialize.Write a cold outreach email from a one-line context
When to use: Prospecting or partnership outreach where you know the recipient but lack a warm introduction. Change first: The "reason for relevance" line. Generic reasons produce emails that go unread.
Variables: [RECIPIENT NAME], [RECIPIENT COMPANY], [YOUR COMPANY], [REASON FOR RELEVANCE], [SPECIFIC ASK]
Write a cold outreach email.
Recipient: [RECIPIENT NAME] at [RECIPIENT COMPANY]
Sender: [YOUR COMPANY]
Why this is relevant to them: [REASON FOR RELEVANCE]
Ask: [SPECIFIC ASK]
Under 100 words. No flattery. Lead with the relevance, not with who you are.[NEEDS REAL OUTPUT]
Editing
Rewrite for plain language
When to use: A draft is technically accurate but hard to read quickly. Change first: The target reading level. "Grade 8" and "executive summary" produce very different rewrites.
Variables: [DRAFT TEXT], [TARGET READING LEVEL OR AUDIENCE]
Rewrite the following text for plain language. Target audience: [TARGET READING LEVEL OR AUDIENCE].
Rules:
- Cut sentences longer than 25 words
- Replace jargon with everyday words
- Keep all factual content intact
Text:
[DRAFT TEXT]Fix the tone of a draft
When to use: A draft is accurate but sounds too formal, too casual, or off-brand. Change first: The "current tone problem" field. The more specific you are, the better the fix.
Variables: [DRAFT TEXT], [CURRENT TONE PROBLEM], [TARGET TONE]
Rewrite the following draft to fix the tone.
Current problem: [CURRENT TONE PROBLEM]
Target tone: [TARGET TONE]
Do not change the meaning or structure. Only adjust word choice and sentence rhythm.
Draft:
[DRAFT TEXT][NEEDS REAL OUTPUT]
Cut a draft by 30%
When to use: A draft is over-written and you want a tighter version to react to. Change first: Nothing. Run it as-is, then compare against the original before deciding which to keep.
Variables: [DRAFT TEXT]
Cut the following text by approximately 30%.
Rules:
- Remove redundant sentences and filler phrases
- Do not remove any distinct facts or arguments
- Keep the original structure and heading order
Text:
[DRAFT TEXT]Improve a weak opening paragraph
When to use: The rest of a document is solid but the intro buries the point. Change first: Tell the model what the document is for. Context changes how aggressively it rewrites.
Variables: [OPENING PARAGRAPH], [DOCUMENT PURPOSE], [INTENDED READER]
Rewrite the opening paragraph of this document so it leads with the main point.
Document purpose: [DOCUMENT PURPOSE]
Reader: [INTENDED READER]
Original opening:
[OPENING PARAGRAPH]
Write three alternatives. Label them A, B, and C. Do not explain your choices.Structuring
Create an outline from a topic and goal
When to use: Before writing anything longer than 500 words, to catch structural problems early. Change first: The goal field. "Inform" and "persuade" produce very different outlines.
Variables: [TOPIC], [GOAL: inform/persuade/instruct], [INTENDED READER], [APPROXIMATE LENGTH]
Create a detailed outline for a [APPROXIMATE LENGTH] document on [TOPIC].
Goal: [GOAL]
Reader: [INTENDED READER]
For each section, include: the section heading, the key point it must make, and the evidence or example that should support it.[NEEDS REAL OUTPUT]
Turn meeting notes into a structured report
When to use: After a complex meeting where raw notes need to become something stakeholders can act on. Change first: The "output format" field. Some stakeholders want a narrative; others want bullets.
Variables: [RAW MEETING NOTES], [MEETING PURPOSE], [INTENDED READER], [OUTPUT FORMAT: narrative/bullets/hybrid]
Turn these meeting notes into a structured report.
Meeting purpose: [MEETING PURPOSE]
Reader: [INTENDED READER]
Output format: [OUTPUT FORMAT]
Include: summary, key decisions, open questions, and next steps with owners.
Notes:
[RAW MEETING NOTES]Write a one-page project brief from a paragraph of context
When to use: You need a brief that stakeholders can review and sign off on quickly. Change first: The "constraints" field. Leaving it blank produces briefs that ignore real-world limits.
Variables: [PROJECT CONTEXT PARAGRAPH], [STAKEHOLDERS], [DEADLINE], [CONSTRAINTS: budget/resources/dependencies]
Write a one-page project brief from this context.
Stakeholders: [STAKEHOLDERS]
Deadline: [DEADLINE]
Constraints: [CONSTRAINTS]
Sections to include: objective, scope, out of scope, success criteria, timeline, open questions.
Context:
[PROJECT CONTEXT PARAGRAPH]Structure a how-to guide from a process description
When to use: When a subject-matter expert has explained a process in prose and you need it as step-by-step documentation. Change first: The audience field. Experts and new hires need very different levels of detail.
Variables: [PROCESS DESCRIPTION], [AUDIENCE: expert/intermediate/new hire], [TOOL OR SYSTEM NAME]
Turn the following process description into a structured how-to guide for [AUDIENCE] using [TOOL OR SYSTEM NAME].
Format:
- Numbered steps
- One action per step
- Warning notes where steps are commonly misunderstood
Process description:
[PROCESS DESCRIPTION]Persuasive writing
Write a proposal executive summary
When to use: The full proposal exists but the decision-maker will only read the first page. Change first: The "primary objection" field. Addressing the most likely pushback here tends to improve approval rates.
Variables: [PROPOSAL TOPIC], [PROPOSED SOLUTION], [KEY BENEFITS], [COST OR RESOURCE REQUIREMENT], [PRIMARY OBJECTION TO ADDRESS]
Write an executive summary for a proposal.
Topic: [PROPOSAL TOPIC]
Solution: [PROPOSED SOLUTION]
Key benefits: [KEY BENEFITS]
Cost or resource requirement: [COST OR RESOURCE REQUIREMENT]
Primary objection to address: [PRIMARY OBJECTION TO ADDRESS]
Under 200 words. Lead with the problem, then the solution, then the ask.Write a persuasive internal pitch
When to use: Proposing a change, new tool, or initiative to a skeptical internal audience. Change first: The "what you are asking for" field. Vague asks produce vague pitches.
Variables: [INITIATIVE NAME], [PROBLEM IT SOLVES], [WHO IS AFFECTED], [WHAT YOU ARE ASKING FOR], [MAIN RISK AND MITIGATION]
Write a short internal pitch for [INITIATIVE NAME].
Problem: [PROBLEM IT SOLVES]
Audience: [WHO IS AFFECTED]
Ask: [WHAT YOU ARE ASKING FOR]
Risk and mitigation: [MAIN RISK AND MITIGATION]
Under 250 words. Use a direct, evidence-forward tone. Do not use business jargon.[NEEDS REAL OUTPUT]
Write a landing page headline and subheadline
When to use: Early in a campaign when you need options to test, not a finished page. Change first: The "primary reader objection" field. This single input has the most effect on output quality.
Variables: [PRODUCT OR SERVICE NAME], [PRIMARY BENEFIT], [TARGET CUSTOMER], [PRIMARY READER OBJECTION]
Write five headline and subheadline pairs for a landing page.
Product or service: [PRODUCT OR SERVICE NAME]
Primary benefit: [PRIMARY BENEFIT]
Target customer: [TARGET CUSTOMER]
Primary objection to overcome: [PRIMARY READER OBJECTION]
Each headline under 10 words. Each subheadline under 20 words. No superlatives, no exclamation marks.Write a case study summary from raw notes
When to use: You have a customer story in rough notes and need a structured one-pager. Change first: The "result" field. A specific, quantified result makes the summary significantly more credible.
Variables: [CUSTOMER NAME OR TYPE], [PROBLEM THEY FACED], [SOLUTION USED], [RESULT], [QUOTE IF AVAILABLE]
Write a case study summary.
Customer: [CUSTOMER NAME OR TYPE]
Problem: [PROBLEM THEY FACED]
Solution: [SOLUTION USED]
Result: [RESULT]
Quote (optional): [QUOTE IF AVAILABLE]
Format: problem, solution, result, one pull quote if provided. Under 200 words. Do not editorialize.Summarizing
Summarize a long document into five bullet points
When to use: Before sharing a long report, policy, or research document with a busy team. Change first: The "focus" field. "Decision-relevant information only" and "background context" produce very different bullet sets.
Variables: [DOCUMENT TEXT OR PASTE], [INTENDED READER], [FOCUS: decision-relevant/background/risks and issues]
Summarize the following document into exactly five bullet points.
Reader: [INTENDED READER]
Focus: [FOCUS]
Each bullet must start with the key finding, not context. No bullet longer than 25 words.
Document:
[DOCUMENT TEXT OR PASTE]Summarize a meeting transcript for stakeholders who were not there
When to use: After any recorded or transcribed meeting, before distributing notes. Change first: The "what stakeholders need to act on" field. Without it, summaries tend toward narrative rather than action.
Variables: [MEETING TRANSCRIPT], [MEETING TOPIC], [STAKEHOLDER ROLE], [WHAT STAKEHOLDERS NEED TO ACT ON]
Summarize this meeting transcript for [STAKEHOLDER ROLE] who did not attend.
Topic: [MEETING TOPIC]
What they need to act on: [WHAT STAKEHOLDERS NEED TO ACT ON]
Include: key decisions, action items with owners, unresolved questions. Omit: small talk, repeated points, tangents.
Transcript:
[MEETING TRANSCRIPT]Extract key recommendations from a research document
When to use: When a research report or vendor proposal is long and your team needs the "so what" quickly. Change first: The "decision you are trying to make" field. This anchors the extraction to what actually matters.
Variables: [DOCUMENT TEXT], [DECISION YOU ARE TRYING TO MAKE], [NUMBER OF RECOMMENDATIONS TO EXTRACT]
Extract the [NUMBER OF RECOMMENDATIONS TO EXTRACT] most relevant recommendations from this document.
Decision I am trying to make: [DECISION YOU ARE TRYING TO MAKE]
For each recommendation: state the recommendation, the evidence behind it, and any caveat the authors noted.
Document:
[DOCUMENT TEXT]Real example outputs
Five prompts in this pack have been run against a live model and the output captured. Those sections are marked [NEEDS REAL OUTPUT] as placeholders until the outputs are reviewed and approved for publication. Once filled, each will show the raw model response alongside a "what to notice" line pointing out what worked, what needed editing, and what the prompt could not do on its own.
The table below shows which prompts are queued for output capture and which model was used for the test run.
| Prompt | Model tested | Output status |
|---|---|---|
| Rewrite for a different reading level | Claude 3.5 Sonnet | [NEEDS REAL OUTPUT] |
| Cut word count by a target percentage | GPT-4o | [NEEDS REAL OUTPUT] |
| Expand a bullet list into a paragraph | Gemini 1.5 Pro | [NEEDS REAL OUTPUT] |
| Write a strong subject line from body copy | Copilot | [NEEDS REAL OUTPUT] |
| Draft a cold outreach email | Claude 3.5 Sonnet | [NEEDS REAL OUTPUT] |
Real outputs matter here because writing prompts produce results that vary noticeably between models. What reads well from Claude can feel flat from Copilot on the same task.
How to adapt these for your team
The prompts above work as written, but they work better when they reflect how your team actually talks. Before sharing them, make two changes: replace the placeholder variables with your real defaults, and add a short style note at the top of each prompt.
A style note doesn't need to be elaborate. Something like "We write in second person, present tense, no exclamation points" is enough to keep outputs consistent across different people using different models.
If your team spans more than one function, consider organizing prompts by role rather than by task type. A writer and a project manager may both need a summary prompt, but they need different versions.
For a structured way to manage this, Convergence's shared folders let teams store, version, and distribute prompts without copying and pasting across documents or chat threads.
Save this folder to your workspace
If you are using these prompts with a team, copying them one by one from a web page is the wrong workflow. People will edit them locally, drift from the agreed wording, and within a few weeks you will have five versions of the same brief-writing prompt with no clear owner.
The better setup is a shared folder where the prompts live in one place, edits are visible, and anyone on the team can run them directly against whichever model they use.
For context on what other teams keep alongside writing prompts, the full prompt library by role shows how writing fits alongside research, communication, and planning folders.
Frequently asked questions
Do these prompts work across ChatGPT, Claude, Copilot, and Gemini?
Yes. Every prompt in this pack is written in plain language with no model-specific syntax, so they run on all four platforms without modification. Minor output differences exist between models, but the prompts themselves need no changes.
Can I share these prompts with my whole team?
You can copy and paste any prompt freely. If you want your team to access a shared, versioned set without hunting through Slack threads, shared folders in Convergence handle that directly.
What if a prompt gives me generic output?
Fill in every variable before you run it. Generic input produces generic output, reliably. Adding one concrete detail, a product name, a target audience, a word count, usually fixes the problem.
Are these prompts good for long-form content like reports or white papers?
These prompts handle sections and components well. For a full white paper, use them to write individual sections, then assemble. AI models lose coherence on very long single-generation outputs.
Where can I find prompts for other business functions?
The prompts by role directory covers the full range. The AI prompts for marketers and AI prompts for business pages are the closest neighbors to this one.