50 AI Prompt Templates for Work (Copy, Use, and Customize)

A static prompt is a one-time tool. A prompt template is an asset that works forever.

The difference is variables. A static prompt says "Write a LinkedIn post about our new product launch." A template says "Write a LinkedIn post about {{product_name}} for {{target_audience}} that emphasizes {{key_benefit}} and ends with {{cta}}." The template adapts to any product, any audience, any campaign - without rewriting the core instruction each time.

This guide gives you 50 ready-to-use templates organized by professional function - marketing, writing, sales, development, HR, customer success, operations, and finance - plus a practical framework for building your own. All templates use {{double-bracket}} variable notation compatible with most prompt managers and AI tools.

What Makes a Prompt Template Actually Good

Before the templates: the anatomy of a reusable prompt that consistently produces good output.

A good prompt template has four components:

1. Role / Persona context - who the AI should be in this interaction 2. Task definition - the specific thing to produce 3. Context variables - the information that changes with each use 4. Output specifications - format, length, structure, tone constraints

A template that skips any of these produces inconsistent results. The role sets the frame. The task defines the job. The variables make it reusable. The output specifications make results predictable.

Example: bad static prompt

Write a blog post about AI productivity tools.

Example: good template

You are an expert B2B content writer specializing in enterprise software. Write a {{word_count}}-word blog post targeting {{target_audience}} about {{topic}}. The post should take a {{content_angle}} angle, include {{num_examples}} concrete examples, and end with a clear takeaway. Tone: {{tone}}. Format: H2 subheadings every 300 words, no bullet point overuse.

The second example produces consistent, high-quality output every time the variables are filled in - whether the topic is AI productivity, cybersecurity, or financial automation.

Jump to: Marketing · Writing & Content · Analysis & Research · Sales · Development · HR · Customer Success · Operations · Finance · Build Your Own Templates

AI Prompt Templates for Marketing Teams {#marketing}

1. LinkedIn Post (Thought Leadership)

You are a professional copywriter who specializes in LinkedIn content for {{industry}} executives.

Write a LinkedIn post for {{persona}} about {{topic}}.

The post should:
- Open with a pattern-interrupting first sentence (no "I'm excited to..." openers)
- Share a specific insight or counterintuitive perspective
- Include one concrete example or data point
- Close with a single reflective question to drive comments
- Length: 150-200 words
- Tone: {{tone}} (e.g., direct/conversational/authoritative)

2. Email Newsletter Edition

Write a {{word_count}}-word newsletter edition for {{brand_name}}'s audience of {{audience_description}}.

This edition covers: {{main_topic}}

Structure:
- Subject line (A/B test: provide 3 options)
- Opening hook (2-3 sentences, immediately valuable)
- Main content section with key insight
- One actionable takeaway
- Brief CTA directing to {{destination}}

Tone: {{brand_tone}}
Avoid: {{language_to_avoid}}

3. Product Launch Announcement

Write a product launch announcement for {{product_name}} targeting {{audience}}.

Product details:
- Core benefit: {{primary_benefit}}
- Secondary benefits: {{secondary_benefits}}
- Price/availability: {{pricing_info}}
- Proof point or social proof: {{evidence}}

Deliverables:
1. Email subject line (5 options)
2. 200-word announcement email body
3. 3 social media posts (one per platform: LinkedIn, X, Instagram)
4. SMS notification (160 characters max)

4. SEO Blog Post Outline

Create a comprehensive SEO blog post outline targeting the keyword "{{target_keyword}}" for {{brand_name}}.

Target audience: {{audience_description}}
Search intent: {{informational/commercial/transactional}}
Competitor content to differentiate from: {{competitor_angles}}

Provide:
1. H1 title (include keyword, under 60 characters)
2. Meta description (under 155 characters)
3. Full H2/H3 outline with notes on what each section should cover
4. Internal linking opportunities to: {{existing_content_urls}}
5. FAQ section with 5 questions based on People Also Ask

5. Ad Copy Variants (Meta/Google)

Create ad copy for a {{campaign_objective}} campaign promoting {{product/service}}.

Target audience: {{audience_segment}}
Unique selling proposition: {{usp}}
Offer or incentive: {{offer}}
Landing page context: {{lp_description}}

Deliver for each platform:
- Google Search: 3 headlines (30 chars max each), 2 descriptions (90 chars max each)
- Meta: Primary text (125 chars), headline (40 chars), description (30 chars)  -  provide 3 creative variants
- LinkedIn: Introductory text (150 chars), headline (70 chars)  -  provide 2 variants for {{tone_1}} and {{tone_2}} approaches

6. Competitive Analysis Brief

Analyze {{competitor_name}} from the perspective of {{company_name}} competing in {{market_segment}}.

Research framework:
- Positioning: How do they position vs. us?
- Messaging: What pain points do they emphasize?
- Pricing (if public): How do they communicate value?
- Strengths: Where do they outperform us?
- Weaknesses: Where do we have the advantage?
- Recent changes: What have they announced in the last {{timeframe}}?

Format: Executive summary (100 words) followed by structured sections. Conclude with 3 strategic implications for our marketing.

7. Social Proof / Testimonial Extraction

I'm sharing a customer interview transcript below. Extract and reformat the most compelling quotes for use across our marketing channels.

Context: {{customer_name}} is a {{customer_role}} at {{customer_company}}. They use {{product_name}} for {{use_case}}.

From the transcript, provide:
1. Hero quote (1-2 sentences, captures core transformation)
2. 3 shorter pull quotes suitable for social media (under 140 characters each)
3. A paraphrased case study headline (format: "[Result] in [Timeframe]  -  [Company]")

Transcript: {{transcript}}

8. Content Repurposing Brief

I have a {{content_type}} ({{title/topic}}) that performed well. Repurpose it into:

1. LinkedIn post (200 words, thought leadership angle)
2. Email newsletter section (150 words, value-first)
3. 5 tweet-length insights (280 chars max each)
4. Short-form video script (60 seconds, hook + point + CTA)
5. Quote graphic caption (50 words)

Maintain the core insight. Adjust format and language for each platform's conventions.

Original content: {{content_to_repurpose}}

27. Brand Voice Audit

Review the following {{content_type}} and evaluate it against our brand voice guidelines.

Brand guidelines:
- Tone attributes: {{tone_attributes}}
- Approved vocabulary: {{approved_terms}}
- Avoid: {{banned_language}}
- Target reading level: {{reading_level}}

Provide:
1. Overall brand voice score (1-10) with brief justification
2. 3 specific phrases or sentences that deviate from brand voice
3. Suggested rewrites for each deviation
4. The single highest-impact change to improve brand alignment

Content to review: {{content_sample}}

28. Content Calendar Planning

Create a {{time_period}} content calendar for {{brand_name}} targeting {{primary_audience}}.

Content pillars: {{pillar_1}}, {{pillar_2}}, {{pillar_3}}
Publishing channels: {{channels}}
Publishing cadence: {{frequency}}
Upcoming campaigns or key dates: {{events}}

For each week or month, provide:
- 1 flagship content piece ({{long_form_type}}: blog post, guide, or report)
- {{social_count}} social media posts distributed across channels
- 1 email newsletter topic
- Any campaign-specific content tied to {{events}}

Format: Table with columns for Date, Channel, Content Type, Topic, Angle, and Keywords/Tags.

AI Prompt Templates for Writers and Content Creators {#writing}

9. Blog Post Draft

Write a {{word_count}}-word blog post for {{publication/brand}} on the topic: "{{topic}}"

Target keyword: {{primary_keyword}}
Secondary keywords: {{secondary_keywords}}
Target reader: {{reader_description}}
Desired outcome for reader: {{reader_takeaway}}

Style guide:
- Tone: {{tone}}
- Subheadings every 300-400 words
- Use concrete examples, not vague generalizations
- Avoid passive voice
- No bullet-point-heavy sections  -  prefer prose
- First sentence must hook immediately; no scene-setting preamble

10. Executive Summary

Write an executive summary of the following content for {{audience}} who have {{time_available}} to read it.

The summary should cover:
- The core problem or opportunity
- The key finding or recommendation
- Supporting evidence (3 data points or examples max)
- Required action or decision

Length: {{length}} (e.g., one page / 250 words / three paragraphs)
Tone: {{formal/direct/conversational}}

Content to summarize: {{content}}

11. Case Study Write-Up

Write a case study based on the following information. Format for {{audience}} (e.g., sales prospects / marketing website / industry publication).

Company: {{customer_company}}
Industry: {{industry}}
Challenge before: {{problem_statement}}
Solution implemented: {{solution}}
Results achieved: {{metrics_and_outcomes}}
Timeframe: {{timeframe}}

Format:
- Headline: "[Result]  -  How {{company}} [did thing] with [product]"
- Challenge section (150 words)
- Solution section (200 words, include specifics of how they used the product)
- Results section (150 words, lead with numbers)
- Quote from {{contact_name}}, {{title}}

12. Press Release

Write a press release announcing {{announcement}} for {{company_name}}.

Required information:
- Key facts: {{facts}}
- Quote from {{spokesperson}}, {{title}}: {{raw_quote_to_polish}}
- Context/background: {{context}}
- Company boilerplate: {{boilerplate}}
- Contact: {{pr_contact}}

Format: Standard inverted pyramid. Dateline: {{city, date}}.
Tone: Authoritative, factual, minimal hyperbole.
Lead paragraph must answer: who, what, when, where, why in two sentences.

29. Long-Form Article Draft

Write a {{word_count}}-word article on "{{title}}" for {{publication_or_brand}}.

Target keyword: {{primary_keyword}}
Secondary keywords: {{secondary_keywords}}
Target reader: {{reader_description}}
Article type: {{article_type}} (e.g., deep dive, how-to guide, expert opinion)
Differentiating angle: {{angle}}

Style guide:
- Tone: {{tone}}
- Subheadings every 300-400 words
- Concrete examples, not vague generalizations
- Avoid passive voice
- First sentence must hook immediately  -  no scene-setting preamble
- No bullet-heavy sections; prefer prose for analysis

30. YouTube Video Script

Write a {{duration}}-minute YouTube video script for {{channel_name}} on: "{{topic}}"

Channel audience: {{audience_description}}
Video goal: {{goal}} (e.g., educate, inspire, drive conversions)
Hook type: {{hook}} (e.g., surprising stat / counterintuitive claim / direct question)

Structure:
- Hook (0:00-0:30): State immediately what the viewer will learn and why it matters to them
- Context (0:30-1:30): Why this topic matters now
- Main content ({{main_duration}}): {{key_points_count}} key points, each with one concrete example
- CTA (last 30 seconds): {{cta}}

Include [ON SCREEN TEXT], [B-ROLL SUGGESTION], and [PAUSE] cues throughout.
Tone: {{tone}}

31. Editing and Revision Brief

Edit the following {{content_type}} for {{purpose}}.

Editing priorities (in order of importance):
1. Clarity: Eliminate ambiguity and vague language
2. Concision: Cut anything that doesn't serve the reader's goal
3. Flow: Ensure each paragraph follows logically from the previous
4. Voice: Match tone to {{target_tone}}

For each significant change:
- Quote the original passage
- Provide the revised version
- Explain the change in one sentence

Preserve: {{elements_to_keep}}
Do not modify: {{off_limits}}

Draft to edit: {{draft}}

32. Interview Preparation Brief

Prepare me for a media interview on {{topic}} as {{role}} at {{company}}.

Interview format: {{format}} (e.g., podcast / live TV / print / panel)
Outlet: {{outlet}}
Likely interview style: {{style}} (e.g., adversarial / friendly / technical)
Key messages to land: {{key_messages}}

Deliverables:
1. 3-sentence opening statement
2. Responses to these anticipated questions (2-3 sentences each, on-message): {{anticipated_questions}}
3. 3 bridge phrases for redirecting off-topic questions to my key messages
4. One memorable soundbite on {{key_message_1}}

Tone: Authoritative but conversational. No corporate jargon.

AI Prompt Templates for Research and Analysis {#analysis}

13. Data Interpretation Summary

Interpret the following data and write a clear narrative summary for {{audience}}.

Context: This data shows {{what_is_being_measured}} for {{time_period}}.
Key metrics to address: {{metric_1}}, {{metric_2}}, {{metric_3}}

Provide:
1. What happened (2-3 sentences)
2. Why it happened (your interpretation based on the data)
3. What it means (so what for the audience)
4. What to do next (recommended action)

Avoid: Raw number recitation without interpretation. The reader can see the numbers  -  explain what they mean.

Data: {{paste_data}}

14. Research Synthesis

Synthesize the following {{number}} sources on the topic of {{topic}} for {{audience}}.

Purpose of synthesis: {{use_case}} (e.g., inform a strategy decision / write a blog post / prepare for a board presentation)

Deliverable:
- 3-5 key themes that emerge across sources
- Notable contradictions or gaps in the research
- The 3 most actionable insights
- A 150-word summary suitable for {{use_case}}

Sources: {{paste_sources}}

15. Competitive Landscape Overview

Create a competitive landscape overview for {{product_category}} targeting {{buyer_persona}}.

Competitors to analyze: {{competitor_list}}

For each competitor, cover:
- Core positioning statement (how they describe themselves)
- Primary target customer
- Key differentiators claimed
- Pricing model (if public)
- Apparent strengths and weaknesses

Conclude with: A positioning map or whitespace analysis  -  where are the gaps in the market?

16. SWOT Analysis

Conduct a SWOT analysis for {{company/product/initiative}} in the context of {{strategic_question}}.

For each quadrant:
- Strengths: Internal advantages relevant to {{strategic_question}}
- Weaknesses: Internal limitations to address
- Opportunities: External conditions to capitalize on
- Threats: External risks to mitigate

Format: 3-5 bullet points per quadrant, each with a one-sentence explanation of relevance.
Conclude with: The single most important strategic implication from this analysis.

33. Customer and User Research Synthesis

Synthesize the following customer research into actionable insights for {{audience}}.

Research type: {{research_type}} (e.g., user interviews, survey responses, support tickets, NPS verbatims)
Number of data points: {{count}}
Research objective: {{what_we_were_trying_to_learn}}

Provide:
1. Top 3 themes that emerge most consistently across the data
2. Most surprising insight (something not anticipated)
3. Most actionable finding (the insight that should most immediately change our behavior)
4. Meaningful differences across {{segments}}, if any
5. 3 recommended next steps with owner and timeframe

Research data: {{paste_data}}

34. Business Performance Summary

Write a performance summary for {{time_period}} for {{audience}} (e.g., board / leadership / investors).

Metrics:
- {{metric_1}}: {{value}} vs. target of {{target}} ({{variance}})
- {{metric_2}}: {{value_2}} vs. target of {{target_2}}
- {{metric_3}}: {{value_3}} vs. target of {{target_3}}

Context:
- What drove performance above or below expectations: {{drivers}}
- External factors: {{external_context}}

Structure:
- Headline (one sentence: what happened)
- 3 performance highlights
- 2 underperformance areas with root cause
- Forward guidance for {{next_period}} with rationale
- 3 decisions or resources required

Tone: Direct. Use numbers, not adjectives. No hedging language.

AI Prompt Templates for Sales Teams {#sales}

17. Cold Outreach Email

Write a cold outreach email from {{sender_name}}, {{title}} at {{company}}, to {{prospect_name}}, {{prospect_title}} at {{prospect_company}}.

Context: {{what_you_know_about_their_situation}}
Offer/value prop: {{what_you_are_offering}}
Relevance trigger: {{specific_reason_for_reaching_out}}

Email structure:
- Subject line: Specific to them, not generic (provide 3 options)
- Opening: Reference the relevance trigger
- Value statement: One sentence
- Proof: One specific example or result
- Ask: Low-commitment next step
- Length: Under 100 words in the body

Tone: Direct but human. No buzzwords. No "I hope this email finds you well."

18. Sales Proposal Section - Business Case

Write the business case section of a sales proposal for {{prospect_company}}.

Their situation: {{problem_or_goal}}
Our solution: {{product/service}}
Key outcomes we deliver: {{outcome_1}}, {{outcome_2}}, {{outcome_3}}
Relevant proof: {{case_study_or_data_point}}

Business case structure:
- Cost of inaction (what it costs them to do nothing)
- Investment required (frame as ROI, not cost)
- Expected return (specific metrics with timeframe)
- Risk mitigation (why working with us reduces uncertainty)

Tone: Confident but not overselling. Let the math make the case.

19. Objection Response

Write a response to the following sales objection: "{{objection}}"

Context:
- We are selling: {{product/service}}
- To: {{buyer_type}}
- The objection likely comes from: {{root_cause}}

Response structure:
1. Acknowledge (validate, do not dismiss)
2. Clarify (optional: ask a question to understand if this is the real issue)
3. Reframe (shift perspective)
4. Evidence (proof point or example)
5. Close (move the conversation forward)

Tone: Confident, not defensive. Never argumentative.
Length: 100-150 words spoken, or one paragraph written.

20. Follow-Up Email After Meeting

Write a follow-up email after a sales meeting between {{your_name}} and {{prospect_name}} at {{prospect_company}}.

Meeting context:
- What was discussed: {{topics_covered}}
- Their stated challenges: {{pain_points}}
- Next steps agreed: {{agreed_next_steps}}
- Open questions to address: {{open_items}}

Email structure:
- Thank-you opener (one sentence, specific)
- Meeting recap (3-4 bullet points: what we covered, what we aligned on)
- Next steps section (clear owner and date for each)
- One value-add (resource, insight, or reference relevant to their situation)
- CTA for next meeting

Length: Under 200 words.

35. Discovery Call Preparation

Prepare a discovery call guide for meeting with {{prospect_name}}, {{title}} at {{prospect_company}}.

Company background: {{company_research}}
Likely use case: {{likely_use_case}}
Sales stage: {{stage}}

Prepare:
1. Opening (2 sentences): How to start without launching into a pitch
2. Situation questions (5): Open-ended questions to understand their current state
3. Problem questions (4): Questions to surface pain and its business impact
4. Implication questions (3): Questions that deepen awareness of the cost of inaction
5. Value questions (2): Questions that let them articulate what solving this would mean for them
6. Red flags indicating poor fit: {{disqualification_criteria}}
7. Closing (1 sentence): How to end with a clear commitment to next step

36. Proposal Executive Summary

Write the executive summary section of a proposal from {{our_company}} to {{prospect_company}}.

Their stated challenge: {{challenge}}
Our proposed solution: {{solution}}
Key differentiators from alternatives they are considering: {{differentiators}}
Investment: {{amount}} over {{period}}
Expected outcomes: {{outcomes_with_metrics}}

Structure:
- Opening (2 sentences): Reflect their challenge back, signal understanding
- Solution overview (3-4 sentences): What we're proposing and why this approach
- Expected outcomes (3 bullets): Specific, measurable results within {{timeframe}}
- Why us (2 sentences): The one or two things that make this the right choice
- Recommended next step (1 sentence)

Length: Under 300 words. Readable in 90 seconds.

AI Prompt Templates for Developers {#development}

21. Code Review Prompt

Review the following {{language}} code for:
1. Correctness  -  does it do what it claims to do?
2. Performance  -  are there obvious inefficiencies?
3. Security  -  any common vulnerabilities?
4. Readability  -  is it clear to another developer?
5. Test coverage  -  are edge cases handled?

For each issue found:
- Severity (critical/major/minor)
- The problem
- The fix (with code example)

Code context: {{what_this_code_does}}
Codebase conventions: {{style_guide_or_framework}}

```{{language}}
{{code_to_review}}

### 22. Technical Documentation

Write technical documentation for {{feature_or_function_name}}.

Audience: {{developer_audience}} (e.g., junior devs / external API consumers / internal team) Format: {{markdown/HTML/RST}}

Include:

• Overview (what this does in one paragraph)
• Parameters / inputs (table format: name, type, required, description, default)
• Return values (format and example)
• Example usage (2-3 code examples, from simple to complex)
• Error handling (common errors and what they mean)
• Notes or limitations

Technical context: {{paste_function_signature_or_description}}

### 23. Bug Report Analysis

Analyze the following bug report and provide a structured response.

Bug description: {{bug_description}} Error logs: {{error_logs}} Environment: {{environment_details}} Reproduction steps: {{steps_to_reproduce}}

Provide:

1. Root cause hypothesis (most likely 1-2 causes based on the evidence)
2. Diagnostic steps to confirm root cause
3. Proposed fix with code sketch
4. Potential side effects of the fix
5. Test cases to verify the fix works and doesn't regress

### 24. Architecture Decision Record (ADR)

Write an Architecture Decision Record (ADR) for the following technical decision.

Decision to be made: {{decision}} Context: {{background_and_constraints}} Options considered: {{option_1}}, {{option_2}}, {{option_3}}

ADR format:

• Title: ADR-{{number}}: {{decision_title}}
• Status: {{proposed/accepted/deprecated}}
• Context: Why this decision is needed
• Decision: What we decided and why
• Consequences: Positive outcomes, negative outcomes, risks
• Alternatives considered: Brief note on rejected options

### 37. Pull Request Description

Write a professional pull request description for the following code change.

Repository: {{repo_name}} Change type: {{type}} (e.g., feature / bug fix / refactor / dependency update) Related issue: {{issue_number}} Change summary: {{what_changed}}

Provide a PR description with these sections:

• What: 2-3 sentence summary of what changed
• Why: The problem this solves or feature this enables
• How: Key technical decisions and why (brief, for reviewers)
• Testing: What was tested and how to verify
• Breaking changes: Any breaking changes and migration steps (or "None")

Checklist items to include: tests pass, docs updated, no secrets in code, reviewed for security.

### 38. API Documentation

Write API documentation for the following endpoint.

Endpoint: {{HTTP_method}} {{path}} Service: {{service_name}} Authentication: {{auth_type}} required: {{yes/no}}

Produce:

• Summary: One sentence description
• Request parameters: Table (name, type, required/optional, description, example)
• Request body: JSON schema with field descriptions
• Success response: Schema with field descriptions and example
• Error responses: Table of status codes and their meanings
• Code examples: cURL, Python (requests), JavaScript (fetch)
• Rate limits: {{rate_limit}}
• Notes: Edge cases, deprecation warnings, or important limitations

Implementation details: {{paste_spec_or_function}}

---

## AI Prompt Templates for HR and People Operations {#hr}

### 25. Job Description

Write a job description for a {{job_title}} role at {{company_name}}, a {{company_description}}.

Role details:

• Team: {{team}}
• Reports to: {{reporting_manager}}
• Location: {{remote/hybrid/onsite - location}}
• Compensation range: {{range}} (if sharing)

Must-have qualifications: {{requirements}} Nice-to-have qualifications: {{preferred_qualifications}} Key responsibilities: {{responsibilities}}

Format:

• About the company (3 sentences)
• About the role (2 sentences)
• What you'll do (5-7 bullet points)
• What we're looking for (5-6 required, 3-4 preferred)
• Why join us (3-4 differentiated reasons, not generic)

Tone: {{company_culture}} - avoid corporate buzzwords unless they reflect genuine culture.

### 26. Performance Review Summary

Write a performance review summary for {{employee_name}}, {{job_title}}, covering {{review_period}}.

Input from manager:

• Key accomplishments: {{accomplishments}}
• Areas of strength: {{strengths}}
• Areas for development: {{development_areas}}
• Goal achievement: {{goals_met / partially_met / not_met}}
• Overall assessment: {{rating}}

Format:

• Opening summary (2-3 sentences, capture the overall performance picture)
• Key contributions (3-4 specific achievements with impact noted)
• Development observations (growth areas, framed constructively)
• Looking ahead (2-3 goals or development areas for next period)

Tone: Professional, specific, actionable. Avoid vague praise ("great team player") - ground observations in behavior.

### 39. Interview Question Bank

Create an interview question bank for hiring {{job_title}} at {{company_name}}.

Key competencies to evaluate: {{competency_1}}, {{competency_2}}, {{competency_3}}, {{competency_4}} Seniority level: {{level}}

For each competency, provide:

• 3 behavioral questions (expecting STAR-format responses)
• 2 situational questions (hypothetical scenarios)

Also include:

• 3 culture-fit questions aligned to {{company_values}}
• 2 questions candidates should ask us, and what strong answers look like
• Red flags to watch for in responses

Format: Organized by competency, with a brief note on what a strong answer demonstrates.

### 40. New Hire Onboarding Plan

Create a 30/60/90-day onboarding plan for {{job_title}} joining {{team_name}} at {{company_name}}.

Role context: {{role_context}} Manager: {{manager_name}} Key stakeholders to meet: {{stakeholders}} Critical tools and systems: {{tools}}

Days 1-30 (Learn):

• Week 1 priorities and required meetings
• Weeks 2-4: Knowledge areas, documentation, shadow sessions to complete

Days 31-60 (Contribute):

• First independent deliverables (specific and achievable)
• Key relationships to build
• Systems to reach proficiency in

Days 61-90 (Lead):

• Ownership areas to take over
• 90-day milestone check-in criteria (what "good" looks like)
• First stretch assignment

Include owner and suggested completion date for each milestone.

---

## AI Prompt Templates for Customer Success {#customer-success}

### 41. Support Escalation Response

Write a response to the following escalated customer support issue.

Customer: {{customer_name}} ({{tier}} account, customer since {{tenure}}) Issue: {{issue_description}} Business impact on them: {{impact}} Time open: {{duration}} What has been tried: {{previous_attempts}} Resolution we can offer: {{resolution}}

Structure:

• Acknowledgment: Personalized, not templated-sounding
• Explanation: What happened (brief, honest, without over-explaining)
• Action: Specific steps we are taking, with owner and timeline
• Customer action required: What we need from them (if anything)
• Commitment: Specific by-when they will hear from us next
• Escalation contact: {{direct_contact_name}} at {{contact_info}}

Tone: Empathetic, accountable, action-oriented. Never defensive.

### 42. Quarterly Business Review Narrative

Write a QBR narrative for the customer success review with {{customer_name}}.

Review period: {{quarter}} Account: {{tier}} tier, {{seats}} seats, contract value {{value}}, renews {{renewal_date}}

Performance data:

• Product adoption: {{adoption_metrics}}
• Outcomes achieved: {{outcomes}}
• Support ticket volume and resolution rate: {{support_data}}
• Satisfaction score: {{nps_or_csat}}

Structure:

• Executive summary (3 sentences): How the quarter went
• Value delivered: 3 specific outcomes tied to their original business goals
• Adoption insights: Where they excel, where there is untapped value
• Challenges: 1-2 honest areas needing attention, with our plan
• Roadmap preview: 2 upcoming features relevant to their use case
• Mutual commitments: What we commit to; what we need from them

Tone: Partner-level. Honest about challenges. Forward-looking.

### 43. Customer Success Plan

Create a 90-day success plan for {{customer_name}}, a {{company_type}} that implemented {{product_name}} to solve {{primary_goal}}.

Key stakeholders: {{stakeholders}} (economic buyer: {{buyer}}) Success definition: {{success_criteria}} Current adoption status: {{status}} Key risks: {{risks}}

Plan:

• 30-day milestones: First evidence of value (specific metrics)
• 60-day milestones: Adoption targets and integration completions
• 90-day milestones: Measurable progress toward {{primary_goal}}

For each milestone: what "done" looks like, who owns delivery (us vs. customer), what we need from the customer.

Also include:

• Monthly check-in agenda template
• Early warning signals that adoption is at risk
• Expansion triggers (signals indicating readiness for additional seats or features)

### 44. Renewal and Expansion Email

Write a renewal outreach email from {{csm_name}}, Customer Success Manager, to {{contact_name}}, {{title}} at {{customer_company}}.

Context:

• Renewal date: {{renewal_date}} ({{days_out}} days away)
• Contract value: {{value}}
• Expansion opportunity: {{expansion_type}}
• Relationship health: {{health}}
• Key wins this term: {{wins}}

Approach: {{strategy}} (e.g., value-first with soft renewal ask / direct renewal with expansion offer / recovery email)

Structure:

• Subject line (3 options)
• Opening: Reference a specific win from this term
• Value summary: 2-3 sentences on what was achieved
• Forward look: What next term enables, tied to their goals
• Ask: Clear, low-friction next step
• CTA: Specific meeting request or booking link

Length: Under 200 words.

---

## AI Prompt Templates for Operations and Project Management {#operations}

### 45. Project Brief

Write a project brief for {{project_name}} at {{company_name}}.

Overview: {{description}} Business case: {{why_now}} → expected outcome: {{outcome}} Sponsor: {{sponsor}} Lead: {{project_lead}} Core team: {{team_and_roles}} Timeline: {{start}} to {{end_date}}

Sections:

• Problem statement: The specific problem this project solves (2 sentences, no solution language)
• Objectives: 3-5 SMART outcomes
• Scope: In scope; explicitly out of scope
• Dependencies: Teams, data, systems, or approvals required
• Risks: Top 3 risks with likelihood, impact, and mitigation
• Success metrics: KPIs with targets
• Budget: {{budget_range}}
• Decision rights: Who approves what (RACI for key decisions)

Tone: Stakeholders should be able to read this in 5 minutes and know exactly what they are approving.

### 46. Meeting Summary and Action Items

Summarize the following meeting and extract action items.

Meeting type: {{type}} (e.g., strategy review / project kickoff / incident debrief) Attendees: {{attendees_and_roles}} Purpose: {{meeting_goal}}

From the notes or transcript below, produce:

1. Executive summary (3-4 sentences): What was discussed and decided
2. Key decisions (bullet list: decision + rationale + who decided)
3. Open questions (unresolved items requiring follow-up)
4. Action items (table: action | owner | due date | dependencies)
5. Parking lot (items raised but deferred)

Format each action item as: "[VERB] [specific deliverable]" - not "discuss X" but "draft proposal for X and share with team by [date]."

Meeting notes: {{notes}}

### 47. Risk Assessment

Conduct a risk assessment for {{initiative}} at {{company_name}}.

Context: {{description}} Stakeholders: {{stakeholders}} Timeline: {{timeline}}

For each risk category, identify the top 2-3 risks:

• Operational: Execution, resourcing, process gaps
• Technical: System, data, or integration failures
• People: Skills gaps, change resistance, key person dependencies
• External: Market, regulatory, vendor, or competitive threats
• Financial: Budget overrun, revenue impact, opportunity cost

For each risk provide:

• Risk statement (specific, not vague)
• Likelihood: High / Medium / Low
• Impact if realized: High / Medium / Low
• Risk score (Likelihood × Impact)
• Mitigation plan (specific action, not "monitor")
• Owner responsible for tracking

Output: Risk register table sorted by risk score, highest first.

### 48. Sprint Retrospective Summary

Summarize a sprint retrospective for {{team_name}}'s {{sprint_name}}.

Sprint context:

• Goal: {{sprint_goal}}
• Goal achieved: {{yes/partially/no}} - {{brief_reason}}
• Velocity: {{completed}} of {{planned}} points completed

From retrospective discussion notes, produce:

What went well (3-5 items): Practices worth repeating What didn't go well (3-5 items): Friction points, stated neutrally - no blame What we will try (3 experiments): Specific and testable - format: "We will try [action] to [outcome], and we will know it worked if [measurable signal]" Team health note (1 sentence): Overall morale assessment Action items: Owner + deadline for each change to implement next sprint

Retrospective notes: {{notes}}

---

## AI Prompt Templates for Finance and Business Operations {#finance}

### 49. Investment Memo and Business Case

Write a business case memo for {{initiative}} requesting {{amount}} from {{approver_title}}.

Decision needed by: {{deadline}}

Structure:

• Situation: Current state and why action is needed (2 sentences)
• Opportunity: The specific, quantified outcome this investment enables
• Options considered:
  • Option 1: Do nothing (cost of inaction)
  • Option 2: Minimal investment ({{min_option}})
  • Option 3: Proposed investment ({{proposed_option}})
• Recommendation: Why Option 3 and the reasoning
• Financial model:
  • Investment: {{breakdown}}
  • Expected return: {{return_type}} over {{period}}
  • Payback period: {{timeframe}}
  • ROI: {{percentage}}
• Risk: Top 3 risks if approved; primary risk if not approved
• Next steps: What approval enables; first 30-day actions

Length: Under 2 pages. Every sentence must earn its place.

### 50. Budget Variance Explanation

Write a budget variance explanation for {{cost_center}} for {{time_period}}.

Audience: {{finance_or_leadership}}

Variance data:

• Budgeted: {{budget}}
• Actual: {{actual}}
• Variance: {{variance_amount}} ({{percentage}} {{over/under}} budget)
• Primary cause: {{main_driver}}

Structure:

• Headline: What the variance is and the single biggest reason (1 sentence)
• Drivers: 2-3 specific factors with estimated dollar impact each
• Context: Was this anticipated? Within management control?
• Corrective action: If over budget - what changes. If under budget - was value lost or is this sustainable?
• Updated forecast: Revised projection for the remainder of {{period}} with rationale

Tone: Factual, no spin. Finance teams value directness over defensiveness.

---

## How to Build Your Own Prompt Templates {#build-your-own}

The 26 templates above cover common use cases. Here is the framework for building templates for any task that you repeat more than a few times.

**Step 1: Start with a prompt that worked**

Write a prompt naturally for a specific task. Run it and evaluate the output. Refine until you are happy with the result. This is your starting point.

**Step 2: Identify what changes between uses**

Read through your prompt and highlight everything that would change if you used this for a different version of the same task  -  a different product, audience, tone, or length. These are your variables.

**Step 3: Replace variables with `{{bracket_notation}}`**

Swap each changeable element with a `{{descriptive_variable_name}}`. Use names that are self-explanatory to anyone who uses the template later: `{{audience}}` not `{{a}}`, `{{target_keyword}}` not `{{kw}}`.

**Step 4: Preserve what makes the prompt work**

Some parts of your prompt are what make it produce good output  -  the role definition, the output format specification, the tone constraints, the structural requirements. Keep these static. Only variabilize what actually changes between uses.

**Step 5: Add a brief usage note**

For templates you will share with others, add a line at the top: "Use this for: [specific task]. Variables to fill: [list of required variables]." This prevents the common failure where team members use a template without filling all the variables.

**Step 6: Test it with different variable values**

Before sharing, run the template three times with meaningfully different variable inputs. If the output is consistently strong across variations, the template is ready. If one variation produces weak output, your core prompt structure needs refinement  -  usually the output specification is too vague or the role definition too generic.

---

## How to Store and Share Templates with Your Team

A prompt template is only valuable if the people who need it can find it in under 5 seconds.

**For individual use:** A browser extension with a searchable prompt library and variable fill-in forms is the fastest option. Type the template name, fill in the variables in the form that appears, insert  -  done in 10 seconds.

**For team use:** The library needs role-based access (so engineering can use but not edit marketing templates), usage analytics (to know which templates are earning their keep), and version history (so when someone improves a template, you can see what changed and roll back if needed).

PromptAnthology's template gallery gives you a [free template library](/tools/prompt-builder) to start building on, plus team sharing built in from day one. See our guide on [building a team prompt library](/blog/prompt-library-for-teams) for the full rollout playbook.

---

## Frequently Asked Questions

**What is the difference between a prompt and a prompt template?**

A prompt is a single, specific instruction for one use. A prompt template is a reusable framework with variable fields (`{{like_this}}`) that you fill in each time. Templates save the structure and instructions that make a prompt effective while allowing the specific content to change with each use.

**What is `{{variable}}` notation?**

Double-bracket notation (`{{variable_name}}`) is the most widely used convention for marking variable fields in prompt templates. When you fill in the variable before sending the prompt to an AI, you replace `{{variable_name}}` with the actual value. Purpose-built prompt managers like PromptAnthology provide form-based fill-in that handles this automatically.

**Do prompt templates work across ChatGPT, Claude, and Gemini?**

Yes. The template structure  -  role, task, context, output specifications  -  works across all major models. Some variables (like `{{model_specific_behavior}}`) may need adjustment for model-specific prompts, but the vast majority of well-structured templates transfer without modification.

**How do I know if my template is good?**

Test it with at least three different sets of variable inputs. If the output is consistently strong across different topics, audiences, and contexts, the template structure is solid. If output quality varies significantly based on what you put in the variables, the core prompt instructions need refinement.

**How many templates should I have?**

Start with 10-15 covering your most common tasks. Quantity is not the goal  -  quality and reusability are. A library of 15 excellent templates you use daily is worth more than 200 mediocre templates that collect dust. Expand based on what you actually need, not what you might theoretically use.

**Can I share my templates with my team?**

Yes  -  that is where templates become genuinely valuable. In PromptAnthology, templates are shareable at the folder level with role-based permissions. A team of 10 using the same set of 30 high-quality templates gets consistent output across all AI-assisted work.

---

For a full explanation of how templates fit into a broader prompt management system - including versioning, team sharing, and cross-platform access - see our [complete guide to prompt management](/blog/prompt-management-complete-guide).

## The Bottom Line

Static prompts are one-time tools. Templates are assets that compound in value over time  -  every use reinforces the structure, every refinement improves all future outputs, and every team member who accesses the template benefits from the work that went into building it.

The 50 templates in this guide are starting points. Take the ones relevant to your work, fill in your brand-specific details in the static sections, and add your own variables where needed. Then save them somewhere searchable.

**Ready to build a permanent template library?** Try PromptAnthology's [free prompt builder](/tools/prompt-builder), then save your templates to a library accessible from inside ChatGPT, Claude, and Gemini with one click.