Book Prompts

I've uploaded [describe the document briefly]. Summarize it in 5 bullet points that I could send to my boss. Each bullet should be one sentence. Focus on decisions made, actions required, and anything that needs immediate attention.

I've uploaded my meeting notes from [date/meeting name]. Turn these into a clean action item list. For each item, include: what needs to be done, who owns it (if mentioned), and the deadline (if mentioned). If an owner or deadline isn't clear, flag it as "TBD." Format as a numbered list.

I've uploaded [describe the document]. Read it carefully and tell me the 3 things I should be most concerned about. For each concern, explain why it matters and suggest one concrete next step.

You are a [your role] at [your company]. Write an email to [recipient and their role] about [subject]. The goal of this email is [specific outcome you want]. Tone: [professional/casual/urgent/empathetic]. Keep it under [word count] words. Include a clear CTA: [what you want the recipient to do].

Context: [1-2 sentences about the situation — what happened, what's at stake, what the recipient already knows]

I've uploaded [describe the document(s)]. Analyze this from the perspective of a [role relevant to the analysis]. Focus on:
1. [Specific aspect #1]
2. [Specific aspect #2]
3. [Specific aspect #3]

For each, provide: a finding (what the data shows), an insight (what it means), and a recommendation (what to do about it).

Format as a table with columns: Aspect | Finding | Insight | Recommendation.
End with a 3-sentence executive summary of the most important takeaway.

Create a [type of document] for [audience]. Purpose: [what this document should accomplish].

Include these sections:
1. Executive Summary (3-5 sentences, the key message upfront)
2. [Section name] — [brief description of what goes here]
3. [Section name] — [brief description]
4. [Section name] — [brief description]
5. Recommendations / Next Steps (numbered list of specific actions)

Constraints:
- Total length: [target length]
- Tone: [specify]
- [Any specific inclusions or exclusions]

Context: [2-3 sentences about the situation this document addresses]

I wrote the following text for [original audience]. Rewrite it for [new audience]. Keep the core message intact, but adjust:
- Vocabulary level: [simpler/more technical/industry-specific]
- Tone: [formal/casual/empathetic/authoritative]
- Length: [shorter/same/longer]
- Emphasis: [what matters most to this new audience]

Original text:
[paste your text here]

I've uploaded [meeting notes / document / email thread]. Extract every decision that was made, whether explicitly stated or implied. For each decision, provide:
- The decision itself (one sentence)
- Who made it or who's responsible
- Any deadline or timeline mentioned
- Open questions that remain unresolved

Format as a numbered list. Separate confirmed decisions from implied/unclear decisions. End with a section called "Needs Clarification" for anything ambiguous.

I need to [describe the task or decision]. Give me 3 distinct options — not variations of the same approach, but genuinely different strategies. For each option:
- Name it (a short, memorable label)
- Describe the approach (3-4 sentences)
- Best case scenario: what happens if it works
- Biggest risk: what could go wrong
- Effort level: Low / Medium / High
- Time to results: [timeframe]

After presenting all three, tell me which one you'd recommend for [my specific situation] and why.

You are a prompt engineering coach. I'm going to describe a task I do regularly, and I want you to help me build a reusable prompt template for it.

The task: [describe what you do, who it's for, what good output looks like]

Build me a prompt template with these elements:
- Role (who should Claude be for this task?)
- Context placeholders (what changes each time I do this task? Use [BRACKETS] for fill-in-the-blank sections)
- Task description (clear, specific deliverable)
- Format instructions (how should the output be structured?)
- Constraints (tone, length, exclusions)

After the template, give me 3 tips for customizing it each time I use it — what to always change, what to sometimes change, and what to never change.

Here are 3 samples of my writing style:

Sample 1: [paste a paragraph from an email you wrote]

Sample 2: [paste a paragraph from a report or post you wrote]

Sample 3: [paste a paragraph from a different context]

Analyze my writing style: sentence length, vocabulary level, tone, use of humor, formality level, how I structure arguments. Then write [the thing you need] matching my voice exactly. Don't imitate — absorb the patterns and write naturally in that style.

I gave Claude this prompt:
"[paste your original prompt]"

And got this output:
"[paste the output you're unhappy with]"

What's wrong with my prompt? Diagnose the specific issues — be blunt, not diplomatic. Then rewrite the prompt to fix each issue you identified. Explain what you changed and why.

I'm evaluating [decision or proposal]. Respond three times from three different perspectives:

**Perspective 1 — The Skeptical CFO:** Focus on financial risk, ROI uncertainty, and opportunity cost. What could go wrong? What are we not seeing?

**Perspective 2 — The Enthusiastic CMO:** Focus on market opportunity, brand impact, and competitive advantage. Why should we move fast?

**Perspective 3 — The Pragmatic COO:** Focus on execution feasibility, team capacity, and operational complexity. Can we actually pull this off?

After all three perspectives, write a 5-sentence synthesis that identifies the strongest argument from each perspective and recommends a path forward that addresses the CFO's biggest concern while capturing the CMO's biggest opportunity.

**The Complete Multiplication Workflow (all-in-one version)**

I'm going to give you a blog post. Your job is to create a complete content package, but I want you to approach each platform differently — not just reformat the same content.

**Step 1:** First, extract: the 5 key insights, any stats/data, the main argument in one sentence, and 3 standalone quotable lines.

**Step 2:** Then create:

**LinkedIn (3 posts):** Each post focuses on ONE insight (not all five). 800-1,200 words. First person. Open with a personal observation, build with an example, close with a question. Each post should feel like its own mini-essay, not a summary of the blog post.

**Twitter/X (10 tweets):** Standalone. Under 280 characters. Mix: bold statements, stats, contrarian reframes, provocative questions. No hashtags.

**Email snippet (1):** 200 words. Tease the most surprising finding. Subject line under 50 characters. CTA: "Read the full piece →"

**Newsletter intro (1):** 150 words. Use the main argument as a conversation starter for the week. Don't reference the blog post directly.

**Instagram carousel (1):** 8 slides. Slide 1 = hook question. Slides 2-7 = one key point each (under 25 words per slide). Slide 8 = CTA + 5 hashtags.

Here's the blog post:
[Paste your blog post here]

I've pasted a blog post below. Turn it into a content package for the following channels:

1. **LinkedIn** (3 posts): Each post should focus on a different key insight from the article. 800-1,200 words each. Professional but conversational tone. End each with a question to drive comments. First person — "I" not "We."

2. **Twitter/X** (5 tweets): Standalone insights. Under 280 characters each. Mix of bold statements, data points, and contrarian takes. No hashtags.

3. **Email newsletter** (1): 200-word excerpt that teases the blog post. Casual, direct tone. Subject line included. CTA: "Read the full piece →"

4. **Instagram carousel** (1): Text for 8 slides. First slide = hook. Last slide = CTA. Middle slides = one point per slide in short, punchy language. Include 5 relevant hashtags.

Here's the blog post:
[Paste your blog post here]

Write a cold outreach email from me ([your name], [your role] at [your company]) to [recipient role] at a [type of company].

About us: [One sentence about what your company does and for whom]
About them: [One sentence about the recipient's company or a specific observation — recent news, a post they published, a product they launched]

Goal: Get a 15-minute introductory call. Not a sales pitch — a conversation.

Constraints:
- Under 120 words total
- Opening line must reference something specific about THEM (not about us)
- No "I hope this finds you well" or any variant
- End with a low-commitment CTA: "Worth a 15-minute chat?"
- PS line with one specific, relevant result: "PS: We helped [similar company] achieve [specific result] in [timeframe]."

Tone: Direct, respectful, zero fluff. Write like a busy person talking to another busy person.

Create a 5-email nurture sequence for leads who downloaded our [lead magnet name — e.g., "2026 Marketing Trends Report"].

About us: [What your company does, your key value proposition]
About the leads: [Who they are, why they downloaded, where they are in the buying journey]

Sequence structure:
- **Email 1 (Day 0):** Deliver the asset. Warm welcome. One sentence about us — no more.
- **Email 2 (Day 3):** Share one actionable insight from the report. "Here's the one thing most people miss..."
- **Email 3 (Day 7):** Case study or social proof. "Here's how [company] applied this..."
- **Email 4 (Day 12):** Address the main objection your audience has. Be honest about it.
- **Email 5 (Day 18):** Soft CTA. "If any of this resonated, here's a way to go deeper: [offer]."

Each email: Under 200 words. Subject line included. Tone: helpful first, sales second. First person singular. No "we are excited" or corporate-speak.

Generate the complete 5-email cold outreach sequence below. Write each email in full — not just a description, the actual email I would send. Keep each under 150 words.

**Context:** I'm [your name], [your role] at [company]. We help [target audience] with [core value prop].

**Prospect profile:** [Role] at [company type], likely dealing with [key pain point].

**Sequence:**

- **Email 1 (Day 0):** Open with a specific observation about their company or industry. One pain point. One line about how we've helped similar companies. CTA: "Worth 15 minutes?"

- **Email 2 (Day 3):** Follow up on Email 1. Share a quick, useful insight related to their pain point — something they can use even if they never reply. No pitch. End with: "Thought this might be useful."

- **Email 3 (Day 7):** Social proof. One specific result from a similar company. Short — under 80 words. CTA: "Happy to share how they did it."

- **Email 4 (Day 14):** Address the most common objection directly: "Most [role]s I talk to worry about [objection]. Here's what we've found..." Honest, not salesy.

- **Email 5 (Day 21):** Breakup email. "I've reached out a few times and haven't heard back — totally fine. If [pain point] becomes a priority, here's how to reach me. Deleting you from my follow-up list either way."

Tone: Direct, respectful, no filler. Each email should feel like a different conversation, not the same pitch reworded. No "I hope this finds you well." No "just checking in." No "circling back."

I'm going to share content from a competitor. Analyze it and tell me:

1. **Target audience:** Who are they writing for? What role, company size, and pain points?
2. **Positioning:** How do they position themselves? What's their main claim?
3. **Messaging themes:** What 3-5 themes come up repeatedly?
4. **Tone and style:** How do they sound? (Professional/casual/technical/aspirational?)
5. **Gaps:** What topics or angles do they NOT address? What's missing?
6. **Vulnerabilities:** Based on their messaging, where could a competitor (us) differentiate?

Be specific. Use quotes from their content to support each point.

Here's their content:
[Paste competitor's homepage copy, 3-5 blog posts, or social media posts]

I've pasted content from a competitor's website below. It includes their About page, pricing page, and three recent blog posts. Analyze each layer separately:

**Layer 1 — Positioning & Identity:**
Who do they say they are? What's their founding story or mission? What words do they use most often to describe themselves? What do they want the reader to feel?

**Layer 2 — Pricing Strategy:**
How many tiers? What's the anchor price? What features are gated behind higher tiers? What objections does their pricing page pre-empt? Is there a free tier, and if so, what's the conversion hook?

**Layer 3 — Content Strategy:**
What topics do their blog posts cover? What audience are they writing for in practice (not just who they claim)? What's their content quality level — thought leadership, SEO-driven, product marketing, or a mix? What content formats do they use?

**Layer 4 — Strategic Gaps:**
Based on ALL the above, identify: (1) three audience segments they're ignoring, (2) three topics they haven't addressed that their audience likely cares about, (3) one positioning angle they've left wide open for a competitor.

Use direct quotes from their content to support every claim. Don't speculate — analyze what's in front of you.

Here's the content:
[Paste About page, pricing page, and 3 blog posts]

Help me build a monthly content calendar. Here's my setup:

**Company:** [What you do, for whom]
**Content pillars:** [3-4 themes you want to cover — e.g., "product how-tos, industry trends, customer stories, thought leadership"]
**Channels:** [Blog, LinkedIn, email newsletter, Twitter — whatever you use]
**Frequency:** [e.g., "2 blog posts/week, daily LinkedIn, weekly newsletter"]
**Current priorities:** [Product launches, events, seasonal themes this month]

Create a 4-week content calendar with:
- Date and channel for each piece
- Content pillar it maps to
- Headline or hook
- 1-sentence description of the angle
- Content type (how-to, opinion, case study, listicle, etc.)

Format as a table. Ensure variety across pillars, channels, and content types. No two consecutive posts should be on the same theme.

Build me a one-week content calendar across three platforms. Here's the context:

**Content pillars and sub-topics:**

- Pillar 1: [name] — Sub-topics: [list 4-5]
- Pillar 2: [name] — Sub-topics: [list 4-5]
- Pillar 3: [name] — Sub-topics: [list 4-5]
- Pillar 4: [name] — Sub-topics: [list 4-5]

**Platform schedule:**

- **LinkedIn:** 3 posts this week. Mix: 1 thought leadership (long-form, 800+ words), 1 tactical tip (short, 200 words), 1 engagement post (question or poll).
- **Email newsletter:** 1 send on Thursday. Theme ties to the best-performing LinkedIn post from last week: [topic]. 500 words max.
- **Twitter/X:** 5 posts. Mix: 2 standalone insights, 1 data point, 1 retweet-with-comment prompt, 1 question.

**This week's priority:** [Product launch / event / seasonal theme / none]

For each piece, give me: Day, Platform, Pillar, Content type, Headline/hook, 1-sentence brief, and any reference material I should include.

Format as a table sorted by day.

**Create a Brand Voice File**

I want to build a comprehensive brand voice file for my Claude Projects. Help me create one by interviewing me. Ask me the following questions one at a time (wait for my answer before moving to the next):

1. If your brand were a person at a dinner party, how would they talk? Who would they remind you of? (A specific public figure, a fictional character, a type of person)
2. Show me 3 pieces of content you've written that sound EXACTLY like your brand at its best. (I'll paste them)
3. What words or phrases does your brand NEVER use? What makes you cringe when you see it in your content?
4. Who is your primary reader? Describe them in a sentence — their role, their biggest frustration, and what they need from you.
5. Show me a piece of content from a competitor or another brand that sounds like what you DON'T want to sound like.

After I answer all five, compile a brand voice file with these sections:
- **Tone Spectrum:** 2-3 sentences using the "we sound like X, not Y" format
- **DO list:** 7 specific writing rules based on the patterns in my samples
- **DON'T list:** 7 specific anti-patterns based on my cringes and the competitor example
- **Gold Standard Samples:** My 3 pieces, with annotations highlighting the key voice patterns
- **Audience Persona:** A 5-sentence portrait of my primary reader
- **Platform Modifiers:** How this voice should adjust for LinkedIn, email, and Twitter/X

I'm writing a blog post targeting the keyword "[your keyword]."

**Context:**
- Search intent: [informational / commercial / comparison / how-to]
- Target audience: [who they are, what they already know, what they need]
- Our angle: [what makes our take different — our experience, our data, our methodology]
- Competitor content: [optional — "The top 3 results for this keyword are: [brief description of each]"]

Create a content brief with:
1. **Title** — Include the keyword naturally. Make it specific enough to click on, not generic.
2. **Meta description** — Under 155 characters. Include the keyword. Make it a reason to click, not a summary.
3. **H2 subheadings** (6-8) — Each should be a question or promise that makes the reader want to keep scrolling.
4. **Key points per section** — 3-4 bullet points per H2 describing what to cover.
5. **Recommended word count** — Based on the depth of the topic and the intent.
6. **Internal linking opportunities** — Suggest 3-5 topics we might have existing content about that could link to/from this article.
7. **Content differentiation** — One paragraph explaining how this article should differ from what's already ranking. What angle are the competitors NOT taking?

I need A/B test variants for [a blog post headline / an email subject line / an ad headline / a CTA button].

**The current version:** "[Your existing headline or subject line]"

**Context:**
- Audience: [who they are]
- Goal: [clicks / opens / conversions / signups]
- Platform: [blog, email, Google Ads, Facebook, LinkedIn]
- Tone: [match my brand voice — confident, direct, no buzzwords]

Generate 10 variants using these angles:

1. **Two curiosity-driven** — Make the reader NEED to know the answer
2. **Two data-driven** — Lead with a specific number or result
3. **Two contrarian** — Challenge a common assumption
4. **Two benefit-first** — State the outcome, not the topic
5. **Two urgency/scarcity** — Create a reason to click NOW (without being clickbait)

For each variant, add a one-line note explaining the psychological lever it pulls. Keep all variants under [character limit for your platform].

**The Complete Repurposing Pipeline (all-in-one version)**

I'm uploading a transcript of a [podcast episode / webinar / conference talk]. My goal is to create a complete content package from this single source.

**Step 1 — Extract:** Read the transcript and pull out: the 8 most valuable insights (ranked by how surprising they'd be to [your audience]), any specific numbers or results mentioned, 5 quotable one-liners, and the most debate-worthy opinion.

**Step 2 — Create:**

**LinkedIn (3 posts):** Each focuses on ONE insight. 800-1,200 words. First person. Open with a personal observation, build with evidence, close with a question. Each should feel like its own essay.

**Twitter/X:** One 7-tweet thread from the most controversial opinion + 5 standalone tweets from the quotable lines. Under 280 characters each. No hashtags.

**Newsletter (1):** 600 words. Built around the most surprising insight. Subject line included. Tone: smart colleague, not marketing department.

**Email snippets (3):** 80-100 words each. Each opens differently (data, opinion, question). Each ends with a CTA to the full episode.

Here's the transcript:
[Paste transcript]

Before writing any email, I need you to build an empathy map for my recipient.

**Recipient profile:**
- Role: [their job title and responsibilities]
- Company type: [size, industry, stage]
- Current pain: [the problem keeping them up at night]
- Goal: [what success looks like for them this quarter]
- Biggest objection to what I'm offering: [why they'd say no]
- How they read email: [on phone during commute / at desk between meetings / scanning subject lines only]

Now write a [type of email] that:
1. Opens by demonstrating that I understand their pain — not by describing my product
2. Bridges from their pain to one specific way I can help
3. Proves it with one concrete result from a similar company
4. Ends with a CTA that matches their energy level (busy = low-commitment, engaged = higher-commitment)

Under 150 words. No "I hope this finds you well." No "we're excited." The email should feel like it was written by someone who actually understands their job.

Write a LinkedIn post about [topic]. 1,000-1,200 words.

**Structure:**
- **Hook (2 lines):** Start with [a personal admission / a surprising data point / a contrarian claim]. This must create a gap — the reader needs to click "see more" to resolve it.
- **Body:** Tell the story behind the hook. Include one specific example with real details (names, numbers, outcomes). Build toward an insight the reader didn't see coming.
- **Close:** End with a specific question that invites the reader to share a parallel experience from their own career.

**Rules:** First person. No hashtags in the body. No "I'm excited to share." No listicle format — flowing paragraphs with one-line breaks between thoughts. The post should read like a conversation, not a presentation.

**My context:** [Your role, your industry, your audience on LinkedIn]

Here are my raw meeting notes. Extract the following:

**1. Action items** — For each one, include: what needs to happen, who owns it, and the deadline (or "TBD" if not discussed). Format as a numbered list.

**2. Decisions made** — What was agreed upon in this meeting? List each decision clearly.

**3. Open questions** — What was raised but not resolved? What needs follow-up before anyone can act?

**4. Key dates** — Any dates or deadlines mentioned.

Attendees: [list who was in the meeting]
Meeting date: [date]

Here are the notes:
[Paste your raw notes]

Here is the full transcript (or detailed notes) from a [type of meeting — e.g., client review, strategy session, team retrospective].

Analyze this meeting at three levels:

**Level 1 — Actions & Decisions**
- Action items with owner, deadline, and dependency (or "TBD" if not discussed)
- Decisions made, with any conditions or caveats attached

**Level 2 — Open Threads**
- Questions raised but not answered
- Topics introduced but deferred ("let's discuss this offline")
- Disagreements that were acknowledged but not resolved

**Level 3 — Meeting Dynamics**
- Key sentiment shifts: where did the conversation shift from positive to concerned (or vice versa)?
- Strongest reactions: what statements generated the most discussion or pushback?
- Unspoken concerns: based on the language used, what topics might people be hesitant about?

Meeting type: [client call / internal strategy / team retrospective / etc.]
Attendees: [names and roles]
Meeting date: [date]

Here's the transcript:
[Paste full transcript or detailed notes]

I'm going to give you a brain dump about a new project. It's rough and unstructured — that's fine. Turn it into a professional project brief with these sections:

1. **Project name** (suggest one if I didn't give one)
2. **Objective** — What are we trying to achieve? One paragraph.
3. **Background** — Why are we doing this? What problem does it solve?
4. **Scope** — What's included. What's explicitly excluded.
5. **Deliverables** — List of tangible outputs with estimated dates.
6. **Stakeholders** — Who's involved and what's their role (sponsor, lead, contributor, reviewer).
7. **Timeline** — Key milestones and dates.
8. **Risks** — What could go wrong. For each risk, include likelihood (high/medium/low) and a mitigation approach.
9. **Open questions** — Anything that's unclear and needs resolution before work begins.

Here's my brain dump:
[Just talk. Type stream-of-consciousness about the project. What it is, why it matters, who's involved, when it needs to be done, what you're worried about.]

Here's my raw project data for this week. Create three different status updates from this information:

**Version 1 — Team Update:**
Bullet format. Task-level detail. Include who completed what, what's in progress, what's blocked, and what's due next week. Tone: direct, no fluff.

**Version 2 — Management Update:**
Executive summary format. 3-5 bullet points max. Focus on: milestone progress (% complete), risks or blockers that need escalation, budget status (if relevant), and one key decision needed. Tone: professional, concise.

**Version 3 — Client Update:**
Email format. Friendly but professional. Focus on: what was delivered this week, what's coming next, any timeline changes (with explanation), and next steps. No internal jargon. No mention of internal resource issues.

Here's the raw data:
[Paste your notes: what happened this week, what's done, what's stuck, any numbers]

Here is the current status data for all my active projects. For each project, generate THREE stakeholder reports. Use the reference file for project details, stakeholder names, and reporting preferences.

**For each project, produce:**

**1. Executive Summary** (1 page max)
- Project health indicator: 🟢 On track / 🟡 At risk / 🔴 Off track
- Key accomplishment this period (one sentence)
- Decisions needed from leadership (numbered list — if none, say "No decisions required")
- Budget status: on budget / X% over or under
- Next milestone and date

**2. Team Update** (detailed, action-oriented)
- Completed this week (task, owner, outcome)
- In progress (task, owner, expected completion, blockers)
- New assignments (task, owner, deadline, dependencies)
- Blockers requiring escalation
- Shoutout: one team contribution worth recognizing

**3. Client Report** (professional, forward-looking)
- Progress against agreed milestones
- Deliverables completed or in review
- Next steps and expected dates
- Anything we need from the client (approvals, data, feedback)
- No internal details. No resource conflicts. No budget discussions.

**Raw data for this period:**
[Paste your weekly notes — can be messy, bullet points, even voice-to-text dumps]

I need to present a decision to stakeholders. Help me create a decision document.

**The decision:** [What needs to be decided — e.g., "Which CRM platform should we adopt?"]

**Context:** [Why this decision matters now. What prompted it. Any constraints — budget, timeline, team preferences.]

**Options:**
- Option A: [Describe it]
- Option B: [Describe it]
- Option C: [Describe it — or "status quo / do nothing"]

**Evaluation criteria:** [What matters most — e.g., cost, ease of adoption, integration with existing tools, scalability, vendor support]

Create a decision document with:
1. **Executive summary** — The decision needed, in 2-3 sentences.
2. **Criteria and weighting** — List the evaluation criteria. Assign each a weight (high/medium/low priority).
3. **Options analysis** — For each option, evaluate against each criterion. Be specific about costs, benefits, and tradeoffs. Don't be diplomatically vague — be direct about weaknesses.
4. **Comparison table** — Options as columns, criteria as rows, with brief assessments.
5. **Recommendation** — Pick one. Explain why. Acknowledge what you're giving up.
6. **Risks of the recommendation** — What could go wrong with this choice.
7. **Next steps** — If stakeholders approve, what happens first?

Here is my project plan for [project name]:

[Paste your plan — can be a structured timeline, a list of tasks with owners and dates, or even a rough description of what needs to happen in what order]

Perform three analyses:

**1. Dependency Map**
Identify every dependency between tasks. For each dependency, specify:
- Which task depends on which
- Whether it's a hard dependency (cannot start until the other finishes) or soft dependency (could start in parallel with risk)
- The impact if the upstream task is delayed by 1 week

**2. Pre-Mortem Analysis**
Imagine it's [project end date + 1 month]. The project has failed. It went over budget, over time, and the deliverables were rejected by stakeholders. Working backward from this failure, identify:
- The 5 most likely causes of failure, ranked by probability
- For each cause: the earliest warning sign that would indicate this risk is materializing
- For each cause: one specific action to mitigate the risk NOW, before it happens

**3. Bottleneck Identification**
Which person, team, or resource appears most frequently across the plan? Flag any single point of failure — a person or resource that, if unavailable for a week, would stall the entire project.

Be direct and specific. Don't soften the risks to be polite.

I'm going to describe a process from my organization. It's going to be informal — like I'm explaining it to a new hire over coffee. Turn it into a professional Standard Operating Procedure (SOP) with:

1. **Process name and purpose** — What this process does and why it matters.
2. **When to use this process** — The trigger or situation that kicks it off.
3. **Prerequisites** — What you need before you start (access, tools, approvals).
4. **Step-by-step procedure** — Numbered steps. Each step should be one clear action. If a step has a decision point ("if X, do Y; if not, do Z"), format it as a decision branch.
5. **Common mistakes** — What goes wrong and how to avoid it.
6. **Troubleshooting** — If something breaks, here's what to check.
7. **Checklist version** — A condensed checkbox list for someone who's done this before and just needs a reminder.

Here's how the process works:
[Describe it. Be messy. Include the workarounds, the exceptions, the "what I usually do when X happens." All of it.]

I have an important meeting in [timeframe]. I need a Pre-Meeting Intelligence Brief — not a simple agenda, but a strategic preparation document.

**Meeting context:**
- Meeting type: [client review / budget defense / vendor negotiation / steering committee / etc.]
- Attendees: [name, role, and their likely perspective or concern — be honest about politics]
- Meeting objective: [What needs to happen for this meeting to be a success?]

**Source materials** (paste below):
- Previous meeting notes or summary: [paste]
- Email threads since last meeting: [paste relevant exchanges]
- Current project status: [paste status data, timeline, or dashboard export]
- Any known issues or tensions: [describe briefly]

**Produce a Pre-Meeting Intelligence Brief with:**

1. **Situation Summary** (5 sentences max) — Where things stand right now, honestly. No spin.
2. **Per-Attendee Briefing** — For each attendee: their likely priorities, their open items from last meeting (resolved or not), potential objections or concerns they may raise, and what THEY need from this meeting.
3. **Talking Points** — The 3-5 points I must cover, in priority order, with suggested framing for each.
4. **Landmines** — Topics that could derail the meeting if handled poorly. For each: what the issue is, why it's sensitive, and a recommended approach.
5. **Decision Map** — Decisions that need to be made in this meeting, who has authority to make them, and what information they need to decide.
6. **Preparation Checklist** — Specific things I should do or bring before the meeting (data to pull, people to pre-align, documents to share in advance).

Be direct. Flag real risks. Don't sanitize the politics — I need to walk in with clear eyes.

It's Friday. Here's everything that happened in my work week:

**Processed meeting summaries:**
[Paste the action items and decisions from each meeting this week — use the outputs Claude already generated for you]

**Tasks completed this week:**
[List what you finished — can be from your PM tool, your to-do list, or just from memory]

**Tasks NOT completed (carried over):**
[What didn't get done and why]

**Notable emails or messages:**
[Anything important that happened outside of meetings — a client complaint, a deadline change, a new opportunity, a team issue]

Produce a Weekly Review with these sections:

**1. Week in Review** (5-7 bullet points)
What were the most significant things that happened this week? Focus on outcomes, not activities. Not "had 6 meetings" but "secured client approval on Q3 campaign direction."

**2. Decisions Made**
List every decision that was finalized this week, across all meetings and communications.

**3. Action Items Status**
Compile ALL action items from the week. For each one: what it is, who owns it, current status (done / in progress / not started / blocked), and deadline.

**4. Emerging Risks**
Based on the patterns you see — delayed tasks, unresolved questions, resource conflicts — what risks are developing? Flag anything that could become a problem in the next 2 weeks if not addressed.

**5. Next Week's Priorities**
Based on what happened this week and what's pending, what are the 3-5 most important things to focus on next week? Rank them.

**6. Parking Lot**
Items that were mentioned this week but aren't urgent enough for next week. Things to revisit in 2-4 weeks.

Here are 47 customer support tickets from the past month. Analyze them and produce a product brief with the following sections:

**1. Issue frequency ranking** — List every distinct issue mentioned, ranked by how many tickets reference it. Include the count for each.

**2. Severity assessment** — For each issue, rate severity as Critical (customers threatening to leave), High (significant frustration), Medium (inconvenience), or Low (minor feedback). Base this on the language customers use, not your assumption about importance.

**3. Root cause clustering** — Group related issues that likely share an underlying cause. For example, "slow response time" and "no follow-up on my ticket" might both point to a staffing or process problem in support.

**4. Specific product features mentioned** — Which features, pages, or touchpoints are named? Quote the exact words customers use.

**5. Actionable recommendations** — Based on the patterns, suggest 5 specific changes, prioritized by impact (how many customers affected × severity). For each recommendation, cite the ticket numbers that support it.

**6. Verbatim quotes** — Pull the 5 most powerful customer quotes that illustrate the biggest problems. These should be presentation-ready.

Here are the tickets:
[Paste all 47 tickets]

I'm pasting content from three sources about [TOPIC]. Read all three and produce a unified synthesis — NOT three separate summaries. Structure it as:

**1. Points of agreement** — What do all three sources say or imply? These are your highest-confidence findings.

**2. Points of contradiction** — Where do the sources disagree? For each contradiction, explain the likely reason (different methodology, different time period, different definition of terms, different sample).

**3. Gaps** — What important questions do none of the three sources address? What would a fourth report need to cover?

**4. Five key takeaways** — Synthesize across all three sources. Each takeaway should draw from at least two sources. Indicate your confidence level (high/medium/low) based on source agreement.

**5. Source quality note** — Any observations about the reliability or bias of each source (industry-funded study, small sample size, outdated data, etc.).

[VERIFY] Flag any specific statistics, percentages, or data points in your output that I should independently verify before using in a client deliverable.

Source 1: [Paste or describe]
Source 2: [Paste or describe]
Source 3: [Paste or describe]

I need to make a decision between [NUMBER] options. Help me build a weighted criteria matrix.

**The decision:** [What you're deciding]

**The options:**
- Option A: [Description]
- Option B: [Description]
- Option C: [Description]

**Evaluation criteria and weights** (I've assigned importance on a 1-10 scale):
- [Criterion 1]: weight [X]/10
- [Criterion 2]: weight [X]/10
- [Criterion 3]: weight [X]/10
[Add more as needed]

For each option, score it 1-5 on each criterion. Multiply the score by the weight. Produce:
1. A comparison table with scores, weighted scores, and totals
2. A clear winner with the reasoning
3. A sensitivity analysis — if I changed the weight of [most important criterion] by ±2 points, would the winner change?
4. One paragraph per stakeholder group explaining how the recommendation serves their priority

Be direct about each option's weaknesses. Don't hedge.

Here is our financial data: [paste the relevant numbers — revenue, costs, margins, or whatever you have].

I'm not a finance expert. Help me understand what I'm looking at:

**1. Pattern identification** — What trends or anomalies stand out? What's changing and in which direction?

**2. Hypothesis generation** — For each anomaly or notable pattern, suggest three possible explanations ranked by likelihood. For each explanation, tell me what data I'd need to confirm or rule it out.

**3. Questions I should ask** — Give me 5 specific questions to bring to the CFO or finance team. Make them smart enough to show I've done my homework, specific enough to get useful answers.

**4. Context I'm missing** — What additional data would change this analysis? What don't these numbers tell me?

[VERIFY] All specific numbers in your response should come directly from the data I provided. Flag any number that is your calculation or estimate rather than a direct data point.

Important: I am NOT looking for financial advice or recommendations. I need an investigation framework — hypotheses and questions, not conclusions.

Here is our budget vs. actual data for [TIME PERIOD]:

[Paste the data — line items, budgeted amounts, actual amounts]

Write a CFO-ready budget narrative that covers:

**1. Executive overview** — Three sentences maximum. What's the headline? Are we over, under, or on track? What's the single most important variance?

**2. Variance analysis** — For every line item where actual differs from budget by more than 10%, explain:
- The size and direction of the variance (dollars and percentage)
- Two plausible explanations for the variance (rank by likelihood)
- Whether this is a one-time event or a trend to monitor

**3. Category patterns** — Group variances into themes. Are the overages concentrated in one department? Is there a pattern (e.g., all people-related costs are up, all marketing spend is down)?

**4. Questions for the finance team** — Five specific questions that the data raises but can't answer. These should demonstrate analytical thinking, not just "why is this number high?"

**5. Recommended actions** — Three concrete next steps, each linked to a specific variance or pattern.

[VERIFY] Every number in your response must come directly from the data I provided. Flag any calculated figure (percentages, totals, comparisons) so I can verify the arithmetic.

Tone: professional, direct, suitable for a board or leadership audience. No jargon that a non-finance executive wouldn't understand.

I'm about to make a significant decision. Here's my plan and reasoning:

[PASTE YOUR PLAN, PROPOSAL, OR STRATEGY]

Perform an Assumption Audit:

**1. Extract assumptions** — List every assumption embedded in this plan. Include the obvious ones AND the ones I probably don't realize I'm making. Aim for at least 10.

**2. Rate each assumption** on a scale:
- **Well-supported**: backed by data or direct evidence I've provided
- **Reasonable**: plausible but unverified — based on general knowledge or industry norms
- **Questionable**: depends on conditions that may not hold, or contradicts common patterns
- **Untested**: no basis provided — I may be assuming this without realizing it

**3. Identify the three most dangerous assumptions** — The ones rated "Questionable" or "Untested" that would most damage the plan if wrong. For each:
- What happens to the plan if this assumption fails?
- How would I test this assumption before committing?
- What's the earliest signal that this assumption is wrong?

**4. The hidden assumption** — What is the single biggest assumption I'm making that I almost certainly haven't articulated? The thing I'm taking for granted that I shouldn't be?

Be direct. I'd rather be uncomfortable now than wrong later.

I need to do strategic scenario planning for my business. Here's the context:

**Business:** [Brief description — industry, size, main revenue sources, geographic market]
**Strategic question:** [The decision or direction you're evaluating]
**Time horizon:** [How far ahead — 1 year, 3 years, 5 years]
**Key uncertainties:** [2-3 things you're unsure about — market growth, competitor moves, regulation, technology shifts]

Build three scenarios:

**Scenario 1 — Optimistic:** Things go better than expected. What does this look like? Be specific: revenue trajectory, market position, team size, competitive landscape. Don't make it a fantasy — make it a realistic best case.

**Scenario 2 — Base case:** The most likely trajectory given current trends. What stays the same? What changes gradually? Where are the slow-building pressures?

**Scenario 3 — Pessimistic:** Things go worse than expected. Again, not a catastrophe — a realistic downside. What breaks first? What cascades?

For EACH scenario, provide:

- **Key assumptions** — What has to be true for this scenario to play out?
- **Early warning signals** — What would I see in the next 90 days that tells me this scenario is becoming reality? Give me specific, observable indicators — not vague trends.
- **Recommended actions** — If this scenario materializes, what should I do? What should I stop doing? What should I accelerate?
- **The strategic bet** — What's the one investment or decision that pays off in this scenario but not in the others?

Then: **The robust strategy** — What actions make sense across ALL three scenarios? These are the no-regret moves I should make regardless of which future materializes.

I'm preparing to reach out to [prospect name], [their role] at [company name]. Here's what I know about them and their company:

[Paste any information you have — LinkedIn profile summary, company website excerpt, recent news, their latest social media post]

Based on this information:
1. What are their likely top 3 priorities in their role right now?
2. What business challenges might they be facing given their industry and company stage?
3. What specific angle should I use to connect my offering ([one sentence about what you sell]) to their situation?
4. Write a one-sentence opening line that references something specific about THEM — not about me.

Be specific. No generic observations like "your company is growing" — reference concrete details from the information I provided.

Write a cold outreach email from me ([your name], [your role] at [your company]) to [prospect name], [their role] at [their company].

What we do: [One sentence — what you sell and who it's for]
What I know about them: [Paste the research from the previous prompt, or your own notes]
Specific observation: [One thing you noticed about them — a post, an announcement, a hiring pattern]

Goal: Start a conversation. Not a sale — a conversation about [specific topic relevant to their situation].

Rules:
- Under 120 words. Every sentence must earn its place.
- First sentence references THEM. Not me, not my company, not my product.
- No "I hope this finds you well." No "I noticed your company is growing." No "As a fellow [anything]."
- End with a low-commitment ask: "Worth a 15-minute chat?" or "Is this even on your radar?"
- Add a PS with one specific result: "PS: We helped [similar company] [specific outcome] in [timeframe]."
- Tone: One busy professional writing to another. Respectful, direct, zero filler.

I have 10 prospects to research for outreach this week. For each one, I'll provide their name, role, company, and one piece of context I found (a LinkedIn post, a company announcement, a job listing, anything). Analyze each prospect and give me:

1. Their most likely current priority based on their role + company context
2. One specific observation I can reference in my opening line
3. The connection angle between their situation and what I sell: [one sentence about your offering]
4. A draft opening line (one sentence, under 25 words, about THEM not me)

Prospect 1: [Name], [Role] at [Company]. Context: [paste one thing you found]
Prospect 2: [Same format]
... (continue for all 10)

Be specific for each prospect. If any prospect's context is too thin for meaningful personalization, flag it and tell me what additional information to find.

Mark any factual claims about the prospect or their company with [VERIFY] — I will confirm these before sending.

I'm preparing a high-priority outreach to [prospect name], [their role] at [company name]. I've assembled a research stack — analyze ALL of it before writing.

**Their LinkedIn profile summary:**
[Paste the full About section and recent activity]

**Company About page:**
[Paste key paragraphs from their website]

**Recent news or press release:**
[Paste one recent article, announcement, or blog post]

**Job listings (if relevant):**
[Paste any open roles that signal strategic direction — e.g., "hiring 3 data engineers" suggests a data infrastructure push]

**What I sell:**
[Two sentences: what your product/service does and who it's for]

Based on this full research stack:

1. Identify the ONE connection between their current trajectory and my offering that would be most surprising and relevant to them. Not the obvious one — the second-order insight.
2. Write a 100-word outreach message that opens with that insight. No flattery. No "I was impressed by your company." Just the insight, the connection, and a question.
3. Suggest a subject line under 8 words that references their specific situation.
4. Flag any claims you're making about the prospect or their company with [VERIFY] — I need to confirm these are accurate before sending.

Create a 5-email outreach sequence for [prospect type — e.g., "VP of Marketing at B2B SaaS companies with 50-200 employees"].

About us: [What you sell, your key value prop, your ideal customer]
Our differentiator: [What makes you different from the obvious alternatives]

Sequence structure:
- **Email 1 (Day 0):** Personalized opening referencing their specific situation. One insight that shows I understand their world. No pitch. End with a curiosity-driven question.
- **Email 2 (Day 3):** Share a relevant resource or contrarian insight. Something they'd forward to a colleague. Brief mention of how it connects to what we do. No CTA beyond "thought you'd find this interesting."
- **Email 3 (Day 7):** Case study email. "[Company like theirs] was dealing with [problem like theirs]. Here's what happened." End with: "Seeing anything similar on your end?"
- **Email 4 (Day 14):** Address the #1 objection I hear from this buyer type: [state the objection]. Be honest about it. No hard sell.
- **Email 5 (Day 21):** Breakup email. Remove all pressure. Offer something genuinely useful (a guide, a benchmark, an introduction) with no strings attached. "If the timing is ever right, I'm here."

Each email: Under 150 words. Subject line included. No "I hope this finds you well," "just following up," or "I wanted to circle back."

I'm running an outreach sequence for [prospect type]. I need signal-based follow-up variants — different emails depending on what the prospect did with my previous message.

**My previous email was about:** [one-sentence summary of what you sent]
**My offering:** [what you sell and for whom]

**Write three follow-up variants:**

**Branch A — Opened but didn't reply** (interested but not convinced)
- Acknowledge their time without saying "I see you opened my email" (that's creepy)
- Add a new angle or proof point that addresses the most likely reason they hesitated
- Lower the ask: instead of a meeting, offer something they can consume passively (a case study, a benchmark report, a 2-minute video)
- Tone: confident, not desperate. You're offering value, not begging for attention.

**Branch B — Didn't open** (missed it or subject line failed)
- New subject line — completely different angle than the original
- Rephrase the core message in a different way (if the first email led with a question, this one leads with a statistic or a bold claim)
- Keep it even shorter than the original — under 80 words
- Tone: fresh start, as if the first email never happened

**Branch C — Replied with an objection** (engaged but resistant)
- Acknowledge their specific concern directly — no deflecting, no pivoting to features
- Share one concrete example of how another client had the same concern and how it was resolved
- End with a low-commitment ask that addresses the objection: "Would it help to see how [similar company] handled exactly this?"
- Tone: peer-to-peer, not salesperson-to-prospect

Each variant: under 120 words. Subject line included. No "just following up" in any version.

Write a breakup email — the final email in my outreach sequence to [prospect name/type].

Context: I've sent [X] previous emails about [topic]. No response.

Rules:
- Open by acknowledging the silence without guilt-tripping: "I've reached out a few times and I know your inbox is relentless."
- State clearly that this is the last email: "I won't fill your inbox further."
- Offer something genuinely useful — a resource, an introduction, an insight — with ZERO expectation of reciprocity
- Close with a permanent open door: "If this becomes relevant in 6 months, my door is open."
- Under 100 words. No emotional manipulation. No countdown timers. No "last chance" language.
- Tone: One professional respecting another's priorities.

I'm building an objection handling playbook for my sales team. Below are real objection responses that led to won deals. Analyze them and help me build a systematic playbook.

**Objection: "It's too expensive"**
[Paste 2-3 real responses from your team that worked]

**Objection: "We're using [competitor] already"**
[Paste 2-3 real responses that worked]

**Objection: "This isn't a priority right now"**
[Paste 2-3 real responses that worked]

**Objection: "I need to check with my [boss/team/committee]"**
[Paste 2-3 real responses that worked]

For each objection:
1. What pattern makes these responses effective? What's the underlying principle?
2. Write 3 response variants: one for a skeptical executive, one for a cautious manager, one for an enthusiastic champion who needs ammunition for internal selling.
3. What should you NEVER say in response to this objection?

I'm going to share notes from 10 closed deals — my best 5 wins and my 5 most painful losses. For each deal, I'll include: the prospect type, the main objections that came up, how we responded, and the outcome.

**WON DEALS:**

Deal 1: [Prospect type, industry, deal size. Key objection: "...". Our response: "...". Outcome: closed in X weeks.]
Deal 2: [Same format]
... (continue for 5 wins)

**LOST DEALS:**

Deal 6: [Prospect type, industry, deal size. Key objection: "...". Our response: "...". Outcome: lost to competitor / went silent / chose to do nothing.]
Deal 7: [Same format]
... (continue for 5 losses)

Analyze these deals and tell me:

1. What patterns separate the wins from the losses? Not obvious factors like price — the underlying dynamics.
2. Which objections appeared in both wins AND losses? How did the handling differ?
3. Where did our responses in lost deals go wrong? What should we have said instead?
4. What's the one objection we handle well and the one we handle poorly?
5. Build me a "red flag" checklist: early signals from these lost deals that should have warned us.

I'm running a quarterly win/loss analysis. Below is data from [number] deals closed in [quarter/time period] — both won and lost. For each deal I've included: prospect company profile, deal size, stakeholders involved, sales cycle length, key objections, competitive situation, and outcome.

**WON DEALS:**

Deal 1: [Company profile: industry, size, stage. Deal value: $X. Key stakeholders: [roles involved]. Sales cycle: X weeks. Main objections: "...". Competitor in play: [yes/no, who]. Outcome: won, signed in week X.]
Deal 2: [Same format]
... (continue for all wins)

**LOST DEALS:**

Deal N: [Same format. Outcome: lost — reason: went with competitor / no decision / budget cut / champion left / other.]
... (continue for all losses)

Run a deep structural analysis:

1. **Stakeholder patterns:** Which roles appeared in won deals vs. lost deals? Is there a stakeholder configuration that predicts success?
2. **Timing patterns:** At what point in the sales cycle do won deals accelerate and lost deals stall? Is there a "danger zone" week where deals go cold?
3. **Objection trajectories:** In won deals, how did objections evolve from first to last? In lost deals, did objections escalate, repeat, or go silent?
4. **Competitive dynamics:** When a competitor was in play, what differentiated the wins from the losses? Was it positioning, pricing, timing, or relationship?
5. **The hidden pattern:** What's ONE insight from this data that we probably haven't noticed — a correlation between two factors that isn't obvious from reviewing deals individually?
6. **Actionable recommendations:** Based on these patterns, give me 3 specific changes to our sales process that would shift the win rate. Not generic advice — changes grounded in THIS data.

Be direct. If the data suggests we're doing something wrong, say so.

I need to practice handling a tough objection before a real call tomorrow.

**My situation:** I sell [what you sell] to [buyer type]. The prospect is [describe them — role, company type, personality if you know it].

**The objection I expect:** "[The specific objection — e.g., 'We tried something like this two years ago and it was a disaster']"

**My current best response:** "[Write your planned response]"

Play the role of this prospect. Stay in character. Be tough but realistic — not cartoonishly difficult. When I give my response:
- Push back with a follow-up objection that a real buyer would raise
- If my response is weak, make it obvious through your reaction (skepticism, changing the subject, going quiet)
- If my response is strong, acknowledge it subtly but raise the next concern

We'll go 5 rounds. After round 5, break character and give me:
1. A score out of 10 for each of my responses (with one sentence explaining why)
2. The moment where I was strongest
3. The moment where I lost them
4. A rewritten version of my weakest response

I have a critical deal meeting coming up. I need you to act as a deal strategy coach and help me prepare a negotiation strategy.

**Deal context:**
- What we sell: [your product/service and price range]
- Deal size: [approximate value]
- Sales stage: [discovery / proposal / negotiation / final decision]
- Timeline: [when the prospect needs to decide, and why]

**The people:**
- My champion: [name, role, what they care about, how much authority they have]
- The decision-maker: [name, role, what we know about their priorities]
- The blocker (if any): [name, role, why they might resist]
- Procurement/legal: [involved? what's their typical behavior?]

**Competitive landscape:**
- Known competitors in the deal: [who else they're talking to]
- Our strengths vs. theirs: [where we win]
- Our weaknesses vs. theirs: [where we lose — be honest]

**History:**
- Key conversations so far: [summarize what's been discussed and agreed]
- Objections raised: [what concerns have surfaced]
- Open questions: [what we still don't know]

**Produce a Deal Strategy Brief with:**

1. **Deal Health Assessment** — Honest evaluation: are we ahead, behind, or at parity? What's the evidence?
2. **Stakeholder Map** — For each person involved: their likely priority, their preferred outcome, and the message that resonates with them specifically
3. **Negotiation Strategy:**
   - Opening position: where to start and why
   - Concession hierarchy: what to give up first, what to protect at all costs, in what order
   - Walk-away triggers: conditions under which this deal isn't worth winning
4. **Objection Battle Cards** — For each likely objection: the objection, why they feel it, the response that addresses the root cause (not the surface complaint), and a proof point
5. **Meeting Choreography** — How to structure the meeting: opening (first 5 minutes), core discussion, the ask, and the close. What to say first, what to save for later.
6. **Risk Factors** — What could kill this deal that we're not seeing? What should we ask to uncover hidden risks?

Be direct. Challenge my assumptions. Tell me what I don't want to hear.

I just had a discovery call with [prospect name] at [company]. Here are my raw notes from the call:

[Paste your notes — messy is fine. Include what they said they need, their pain points, timeline, budget signals, decision process, and any specific requests]

Our standard proposal structure:
1. Executive Summary (their situation + our recommendation)
2. Understanding Your Needs (paraphrase their pain points — prove we listened)
3. Proposed Solution (map our offerings to their specific needs)
4. Implementation Timeline (align with their stated timeline)
5. Investment (pricing, packages, payment terms)
6. Why Us (differentiators relevant to THEIR evaluation criteria)
7. Next Steps

Write a proposal draft following this structure. Use their actual language from the call notes — if they said "we're drowning in manual processes," use "manual processes" not "operational inefficiencies." Tone: Confident but not arrogant. We understand their problem and have a clear path to solving it.

Flag anything where you're uncertain or where my notes are incomplete with [NEEDS INPUT].

Here are support ticket summaries for my 20 highest-value accounts over the past 3 months. For each account, I've listed: ticket count, brief topic summary, and tone notes (if any).

[Paste your account-by-account ticket summaries]

Analyze these accounts and give me:

1. **Churn risk ranking:** Sort all 20 accounts from highest to lowest churn risk. For the top 5, explain your reasoning in one sentence each.
2. **Pattern detection:** Are there common themes across the at-risk accounts? (e.g., same feature area, same onboarding gap, same team size)
3. **Silent risk:** Which accounts have suspiciously LOW ticket volume? No tickets can mean satisfaction — or it can mean they've stopped trying and are quietly evaluating alternatives.
4. **Intervention playbook:** For each of the top 5 at-risk accounts, suggest a specific outreach action — not "schedule a call" but a targeted message addressing what the ticket data reveals.

Mark any inferences about account health that go beyond what the ticket data shows with [VERIFY] — I need to cross-check these against usage data and account manager notes.

I manage a portfolio of [number] accounts. For each account below, I've compiled their health data from the past 90 days. Turn this data into a Health Score Narrative — a human-readable assessment that tells me what's happening, why, and what to do about it.

**Account 1: [Company name]**
- Usage metrics: [Monthly active users, login frequency trend, feature adoption — up/down/flat vs. previous quarter]
- Support tickets: [Count, themes, severity, tone of recent tickets]
- NPS/CSAT score: [Latest score + trend]
- Contract details: [Value, renewal date, months remaining]
- Last QBR summary: [One sentence — what was discussed]

**Account 2: [Same format]**
... (continue for all accounts)

For each account, provide:

1. **Health narrative (3-4 sentences):** What's the story behind these numbers? Not "usage is down 15%" — WHY is usage likely down and what does it mean for the relationship?
2. **Risk level:** Healthy / Needs Attention / At Risk — with one sentence justifying the rating
3. **Expansion signal:** Is there anything in this data that suggests they're ready for more? (Increasing usage, new teams onboarding, feature requests that map to our premium tier)
4. **Recommended action:** One specific thing I should do THIS WEEK for this account. Not "schedule a check-in" — a targeted action based on what the data reveals.
5. **Conversation opener:** If I called this customer today, what's the one thing I should lead with based on their data?

Flag any interpretations that go beyond what the data directly shows with [VERIFY] — I may need to cross-check with account manager notes or direct conversation.

Here is my task diary from the past week — a log of every repetitive task I performed, with approximate time spent and frequency.

Analyze this diary and produce an **Automation Priority Matrix** with:

1. **For each task, calculate an Automation Score:**
   - Frequency (times per week) × Time per instance (minutes) × Error factor (1 = never fails, 1.5 = occasional errors, 2 = frequent errors) = **Automation Score**
   - Sort by score, highest first

2. **Top 5 Automation Candidates** — The five tasks with the highest scores. For each one:
   - Estimated weekly time saved
   - Recommended automation tool (Zapier, Make, Claude Connector, Cowork, or manual with Claude)
   - Complexity rating: Easy (under 30 minutes to set up) / Medium (1-2 hours) / Hard (half a day or more)
   - One-sentence description of the automation

3. **The "Quick Win" Pick** — Which ONE task should I automate first? Choose based on: highest score, easiest to implement, lowest risk of error. Explain why.

4. **Leave These Manual** — Tasks from the diary that should NOT be automated, and why (too rare, too judgment-heavy, too risky).

Here is my task diary:
[Paste your week of logs]

You are a client relations assistant for [YOUR COMPANY NAME]. A potential client just submitted a contact form. Here are their details:

Name: {Name from form}
Company: {Company from form}
Message: {Message from form}

Draft a personalized response that:
- Acknowledges their specific request (reference something from their message)
- Briefly explains how [YOUR COMPANY] can help with that specific need
- Suggests a 15-minute discovery call
- Keeps the tone warm, professional, and concise (under 150 words)
- Does NOT make up any facts about our services — stick to the general value proposition

Sign the email as [YOUR NAME], [YOUR TITLE].

A new contact form was submitted. Analyze the inquiry and draft two versions of a response:

VERSION A: Formal (for corporate inquiries)
VERSION B: Casual (for startup/freelancer inquiries)

Submission details:
Name: {{Name}}
Company: {{Company}}
Message: {{Message}}

For each version:
- Reference something specific from their message
- Propose a next step appropriate to their likely company size
- Keep each version under 120 words
- Flag if the inquiry seems urgent (mentions deadline, "ASAP," or time pressure)

Search my inbox for all emails from clients in the last 7 days that mention "proposal" or "quote." For each one:

1. Summarize what they are asking for (one sentence)
2. Rate the urgency: LOW / MEDIUM / HIGH based on language and deadlines mentioned
3. Draft a brief acknowledgment email (2-3 sentences) confirming I received their request and will respond within 24 hours

Format the output as a table with columns: Client Name, Summary, Urgency, Draft Response.

I need you to [SPECIFIC TASK].

**Files to work with:** [folder path or specific file names]

**Expected output:** [what the final deliverable should look like — format, length, structure]

**Priorities:** [what matters most — accuracy of numbers? Completeness? Speed? A specific angle or framing?]

**Flag for my review:** [anything you want Claude to highlight rather than decide on its own — ambiguous data, judgment calls, items that need human approval]

You are my email triage assistant. An email just arrived. Here are the details:

From: {Sender}
Subject: {Subject}
Body: {Body snippet — first 500 characters}

Classify this email into ONE category:
- URGENT: Requires response within 2 hours (client deadline, executive request, time-sensitive)
- RESPOND: Needs a thoughtful response within 24 hours
- INFORMATIONAL: No response needed, but worth reading (newsletters, updates, FYI)
- LOW: Can wait or be ignored (promotions, non-essential notifications)

Then write a one-sentence summary of what the email is about.

Output format:
Category: [category]
Summary: [one sentence]
Suggested action: [what I should do, in 10 words or fewer]

Here are rough notes from a meeting that just ended:

Meeting: {Event Title}
Attendees: {Attendees}
Notes: {Your rough notes — paste or upload}

Create a structured meeting summary:

## Decisions Made
[Bullet list of decisions, with who made the call]

## Action Items
[Bullet list, each with: Owner, Task, Deadline if mentioned]

## Open Questions
[Anything unresolved that needs follow-up]

## Key Takeaways
[2-3 sentences capturing the most important outcome of this meeting]

Keep it concise. If something was not mentioned in the notes, do not invent it.

A new blog post was just published. Here is the content:

Title: {Title}
Content: {Full text or excerpt}

Create the following social media drafts:

**LINKEDIN POST** (150-200 words)
- Professional tone, thought-leadership angle
- Start with a hook that makes people stop scrolling
- End with a question to drive engagement

**TWITTER/X THREAD** (3 tweets, max 280 characters each)
- Punchy, direct, conversational
- Tweet 1: The surprising insight
- Tweet 2: The evidence or example
- Tweet 3: The takeaway + link placeholder [LINK]

**EMAIL NEWSLETTER SNIPPET** (50-75 words)
- Teaser that makes subscribers click through to the full post
- Include one compelling stat or insight from the post

Do not add hashtags unless they are directly relevant. No generic hashtags like #AI #Innovation.

At the end of your response, add a confidence section:

CONFIDENCE CHECK:
- Claims I am certain about: [list]
- Claims that need human verification [VERIFY]: [list]
- Data I could not access or confirm: [list]

This section is for the human reviewer only. Do not include it in any client-facing output.

I have built the following automations for my business. For each one, I will give you the time the task took before automation, the time it takes now (including review), and how often it runs per month.

[Paste your automation list here — name, time before, time after, frequency]

My approximate hourly rate (loaded cost): $[YOUR RATE]
My automation platform cost: $[MONTHLY COST]

Calculate:
1. Monthly time saved per automation (in hours)
2. Monthly dollar savings per automation
3. Total monthly and annual ROI after platform costs
4. Rank the automations by ROI from highest to lowest
5. Flag any automation that is not paying for its share of the platform cost

Present this as a clean table, then give me a one-paragraph executive summary I can share with my manager.

Here is the transcript/notes from a recent talk I gave:

Title: {Title}
Event: {Conference/webinar name}
Content: {Full transcript or detailed notes}

Create a full content repurposing package:

**BLOG POST** (1,200-1,500 words)
- Transform the talk into a structured article with introduction, 3-4 key sections, and conclusion
- Add subheadings for scannability
- Include a call-to-action at the end

**LINKEDIN POSTS** (5 separate posts, one per business day)
- Each post pulls a DIFFERENT insight from the talk
- Each starts with a hook (counterintuitive statement, surprising stat, or provocative question)
- Each is 150-200 words
- Day 1: The most surprising finding
- Day 2: A practical tip the audience can use today
- Day 3: A common mistake the talk debunked
- Day 4: A personal story or behind-the-scenes moment
- Day 5: The big-picture takeaway, linking to the blog post

**X/TWITTER THREAD** (5 tweets)
- Tweet 1: Bold claim from the talk
- Tweets 2-4: Supporting evidence or examples
- Tweet 5: Takeaway + [LINK] placeholder

**NEWSLETTER SNIPPET** (75-100 words)
- Personal angle: why this talk mattered to me
- One key takeaway for the reader
- Link to the full blog post

**INSTAGRAM CAROUSEL** (5 slides, text only)
- Slide 1: Hook headline
- Slides 2-4: One key point per slide (short, punchy, under 30 words each)
- Slide 5: Call-to-action (follow for more, link in bio, etc.)

For ALL platforms: no generic hashtags, no buzzwords, no "In today's fast-paced world" energy. Sound like a smart human sharing what they learned, not a brand account running content.

I'm preparing a board presentation for [date]. Here's the raw material:

**Quarterly data:** [Paste revenue, growth metrics, key KPIs]
**Customer feedback themes:** [Paste top 3-5 themes from support/NPS/interviews]
**Competitive changes:** [What shifted in the market this quarter]
**Decisions needed:** [What I need the board to weigh in on]

Build a board deck outline with these sections:
1. Executive summary (3 bullets max — what happened, what it means, what we need)
2. Key metrics vs. plan (table format — metric, target, actual, variance)
3. Market context (what changed externally and why it matters for us)
4. Strategic decisions requiring board input (frame each as a clear question with 2-3 options and your recommendation)
5. 90-day outlook (priorities for next quarter)

Tone: Confident but honest. If something went wrong, say so and explain what you learned. Investors respect transparency over spin. Write like a founder who respects the board's time and intelligence.

Flag any claims that would need external verification with [VERIFY].

I need a competitive intelligence brief for [your company name]. Here's what I know:

**Our positioning:** [One paragraph about what you do and for whom]
**Known competitors:** [List them with one sentence each about their positioning]
**Recent market changes:** [New entrants, pricing changes, feature launches, acquisitions]
**What I'm trying to decide:** [The strategic question this analysis should inform]

Produce a brief with:
1. Competitive landscape map — position each player on two axes: [axis 1, e.g., price] and [axis 2, e.g., feature depth]
2. Threat assessment — rank competitors by threat level to our specific positioning, with reasoning
3. Gaps we can exploit — where no competitor is strong
4. Risks to watch — what could change the landscape in the next 6 months

Use only the information I've provided. Do NOT invent competitor features, pricing, or market data. If you need more information to complete a section, say so.

I need to hire a [role] for my company. Here's the context:

**Company stage:** [Seed/Series A/growth/etc. and team size]
**Why this role now:** [What triggered the need]
**What success looks like in 90 days:** [The concrete outcomes this person should deliver]
**Team context:** [Who they'll work with, who they report to, what's the team dynamic]
**Budget range:** [Salary range if known]

Create:
1. A job description that leads with impact, not a skills checklist. What will this person accomplish, not what boxes they check.
2. An interview scorecard with 5 evaluation criteria, weighted by importance, with sample questions for each.
3. A "red flags" list — what should disqualify a candidate for THIS specific role at THIS specific company stage.

Write the job description to attract builders, not resume optimizers. No buzzword bingo. No "fast-paced environment" or "wear many hats" — say what you actually mean.

You are a content strategist writing for [company name]. Here's our brand voice:

**Tone:** [e.g., "Confident but not arrogant. Helpful but not patronizing. We use humor sparingly and never at the customer's expense."]
**Vocabulary we use:** [List 5-10 words/phrases that define your brand]
**Vocabulary we avoid:** [List 5-10 words/phrases that are off-brand]
**Example of our voice done well:** [Paste one piece of content you're proud of]

Write [content type — e.g., "5 LinkedIn posts"] for this audience: [describe your target audience in one sentence].

Topic: [The subject or theme]
Goal: [What you want the reader to do — click, share, comment, visit]

Each post should feel like it was written by the same person who wrote the example above. Match the sentence length, the rhythm, and the level of formality. No hashtag spam. No "In today's fast-paced world." No generic calls to action.

Draft a campaign brief for the following launch:

**Product/Feature:** [What you're launching and why it matters]
**Target audience:** [Primary and secondary segments]
**Key message:** [The one thing the audience should remember]
**Competitive context:** [What alternatives exist and why ours is different]
**Channels:** [Where this campaign will run]
**Timeline:** [Key dates — launch, pre-launch, post-launch]
**Budget range:** [Total campaign budget]
**Success metrics:** [How you'll know this worked]

Structure the brief with: Executive Summary, Audience Deep-Dive, Messaging Framework (primary message, supporting proof points, objection responses), Channel Strategy (what goes where and why), Creative Direction (mood, references, constraints), Timeline, and Measurement Plan.

Write this so an agency or freelancer could execute without a follow-up meeting. Every section should answer "what" and "why" — not leave decisions to the reader.

I've collected recent content from our top 3 competitors. Analyze it and tell me what we can learn.

**Competitor A — [Name]:**
[Paste 3-5 recent posts, articles, or campaigns]

**Competitor B — [Name]:**
[Paste 3-5 recent posts, articles, or campaigns]

**Competitor C — [Name]:**
[Paste 3-5 recent posts, articles, or campaigns]

**Our recent content:** [Paste 3-5 of your own for comparison]

Analyze:
1. Themes — What topics is each competitor focusing on? What are they ignoring?
2. Tone — How does each competitor's voice compare to ours?
3. Gaps — What topics or angles does NO competitor cover that our audience cares about?
4. Threats — Where is a competitor doing something better than us?
5. Recommendations — Three specific content plays we should make in the next 30 days based on this analysis.

Be direct. If a competitor is doing something better, say so. No false reassurance.

I'm responding to a client request. Here's the context:

**Client:** [Company name, size, industry]
**Their problem:** [What they told you they need, in their words]
**The real problem:** [What you think they actually need, based on your expertise]
**My approach:** [How you'd solve it — 3-5 bullet points]
**Relevant experience:** [2-3 similar projects you've completed, with outcomes]
**Budget range:** [If discussed]
**Timeline:** [Proposed duration]

Draft a proposal with:
1. Executive summary — Mirror their language for the problem. Show you heard them. Then reframe it with your diagnosis.
2. Approach — What you'll do, in what order, and why this sequence matters.
3. Deliverables — Concrete list of what they'll receive, with format and timing.
4. Your qualifications — Not a resume. Two relevant case studies that demonstrate you've solved this type of problem before.
5. Investment — Frame the cost in terms of the value they'll receive, not just the hours you'll work.
6. Next steps — What happens if they say yes.

Write in my voice: [describe your writing style in one sentence — e.g., "direct, no consulting jargon, occasionally dry humor"]. This should read like a letter from a trusted advisor, not a corporate capability deck.

I've completed research for a client deliverable. Here are my raw notes:

[Paste your research notes — interviews, data, observations, meeting notes]

The deliverable is a [type — e.g., "strategic assessment," "market entry recommendation," "organizational diagnostic"].

The client's key question is: [The question this deliverable must answer]

Synthesize these notes into:
1. Key findings — The 5-7 most important insights, ranked by impact
2. Supporting evidence — For each finding, 2-3 data points or quotes from the research
3. Implications — What each finding means for the client's business
4. Recommendations — Specific actions the client should take, in priority order
5. Risks — What could go wrong if they act (or don't act) on these findings

Do NOT add information beyond what's in my notes. If my notes don't support a strong conclusion on a topic, say "insufficient data" rather than speculating. I'll add depth where needed.

Here are my notes from this week's client work:

[Paste meeting notes, email exchanges, project updates, observations]

Extract:
1. Reusable frameworks — Any approach or methodology I used this week that could apply to future clients
2. Pattern recognition — Recurring themes across clients (if notes cover multiple clients)
3. Lessons learned — What worked, what didn't, and why
4. Content opportunities — Insights that could become blog posts, LinkedIn posts, or case studies (anonymized)
5. Process improvements — How I could deliver similar work faster or better next time

Format this as a weekly debrief I can add to my personal knowledge base. Keep it scannable — bullet points, not paragraphs.

I need a job description for the following role:

**Role:** [Title]
**Department:** [Where this role sits]
**Why we're hiring:** [What triggered this — growth, replacement, new function]
**What this person will accomplish in their first 90 days:** [Concrete outcomes]
**What this person will accomplish in their first year:** [Concrete outcomes]
**Skills the hiring manager listed:** [Paste the full list]

Rewrite this as a job posting that attracts strong candidates:
1. Open with the IMPACT of the role — what this person will build, change, or own. Not a skills checklist.
2. Separate skills into "You must bring this on day one" (3-5 max) and "You'll develop this here" (the rest).
3. Describe the team and who they'll work with — real humans, not org chart boxes.
4. Include "You'll thrive here if..." and "This might not be for you if..." sections — honest role fit signals.
5. Flag any requirement that might unnecessarily narrow the candidate pool (e.g., requiring a degree for a skills-based role, requiring 10+ years for a role where 5 would suffice).

Tone: Warm, direct, human. This is marketing — you're selling an opportunity, not listing requirements. No "fast-paced environment," no "rockstar," no "wear many hats." Say what you mean.

I need to draft an internal communication about a sensitive topic.

**Situation:** [Describe what happened or what's changing — e.g., restructuring, policy change, leadership departure]
**Who will read this:** [Audience — all employees, affected team, managers only]
**What they're probably feeling:** [Anxiety, confusion, anger, uncertainty — be honest]
**Key facts they need:** [Timeline, impact on them, what changes, what stays the same]
**What we're doing to support them:** [Concrete actions — severance, transition support, open Q&A sessions]
**What we need from them:** [Specific ask — patience, feedback, questions to HR]

Write this email with:
- An opening that acknowledges the difficulty honestly. No corporate euphemisms. No "exciting changes."
- Facts presented clearly and completely. No information gaps that breed rumors.
- Empathy that's genuine, not performed. Acknowledge what they're losing, not just what they're gaining.
- Concrete next steps with dates. "We'll share more soon" is not acceptable — give a date.
- A closing that invites questions and means it.

Tone: Empathetic, honest, respectful. If this is bad news, it should sound like bad news delivered by someone who cares — not like bad news dressed up as an opportunity.

Build an interview framework for the following role:

**Role:** [Title and level]
**Key competencies to assess:** [3-5 competencies that matter most]
**Team culture:** [Describe the team's working style and values]
**Common hiring mistakes for this role:** [What's gone wrong in past hires — if known]

Create:
1. A scorecard with the competencies weighted by importance (must total 100%)
2. For each competency: 2 behavioral interview questions (ask what they DID, not what they WOULD do)
3. For each question: what a strong answer includes, what a weak answer sounds like, and one follow-up probe
4. A "culture add" assessment — not "culture fit" (we're not looking for clones). What perspectives or experiences would strengthen the team?
5. Red flags — specific signals that this candidate won't succeed in THIS role at THIS company

Format the scorecard so every interviewer can score independently and scores can be compared objectively in the debrief.

I need to document a standard operating procedure. Here's the process as my team described it:

[Paste a messy, conversational description of the process — record yourself or a team member walking through it]

**Process name:** [What this process is called]
**Who does it:** [Roles involved]
**How often:** [Daily/weekly/triggered by an event]
**Tools used:** [Software, forms, equipment]
**What goes wrong most often:** [Common failure points]

Turn this into a clean SOP with:
1. Purpose — Why this process exists (one sentence)
2. Scope — Who this applies to and when
3. Step-by-step procedure — Numbered steps, each with: the action, who does it, what tool they use, and what the expected output is
4. Decision points — Where someone needs to make a judgment call, explain the criteria
5. Exception handling — What to do when things don't follow the normal path (use the common failures I listed)
6. Quality checks — How to verify each critical step was done correctly

Write this so a new employee on their first week could follow it without asking questions. If a step is ambiguous, flag it — don't guess.

I need to evaluate vendors for [what you're purchasing]. Here's the context:

**Our requirements:** [Must-have features and capabilities]
**Nice-to-haves:** [Features we want but could live without]
**Constraints:** [Budget range, timeline, integration needs, team size]
**Vendors being evaluated:** [List them with one sentence about each]

Create:
1. A weighted scoring matrix — categories: functionality fit, integration capability, total cost of ownership, vendor stability, implementation timeline, support quality. Weight each category based on our requirements.
2. For each category: 3-4 specific evaluation questions to ask during demos
3. A "demo scorecard" I can fill in during each vendor presentation
4. After I paste my demo notes, score each vendor and produce a comparison table with a recommendation

The matrix should be defensible in front of leadership — no subjective scores without reasoning.

Here's this week's operations data:

[Paste metrics — production numbers, incident reports, SLA performance, headcount, budget vs. actual, etc.]

Write an operations summary for leadership with:
1. Headlines — The 3 most important things from this week, in order of business impact
2. Performance vs. targets — Where we're on track, where we're behind, and why
3. Incidents and resolutions — What went wrong, what we did, what we changed to prevent it
4. Resource and capacity status — Are we over or under capacity? Where are the bottlenecks?
5. Decisions needed — What requires leadership input this week, with options and your recommendation

Tone: Clear, factual, no spin. If performance is down, say so and explain the cause. Leadership respects candor. They don't respect dashboards that make everything look green when it isn't.

Use only the data I provided. If a metric seems incomplete or anomalous, flag it rather than explaining it away.

Research this prospect and draft a personalized outreach email:

**Prospect:** [Name, role, company]
**What I know:** [Paste LinkedIn summary, recent posts, company news, anything you've found]
**What we sell:** [One sentence — your value proposition]
**Similar client result:** [One example — "We helped [company] achieve [outcome] in [timeframe]"]

Step 1: Based on what I've provided, identify their likely top 3 priorities and the biggest challenge they're probably facing right now.

Step 2: Draft a cold email under 100 words. Rules:
- First sentence about THEM, not us
- Reference something specific from the information I provided
- End with a low-friction ask
- PS with the similar client result
- No "I hope this finds you well," no "I noticed your company is growing," no filler
- Tone: One professional to another. Direct. Respectful. Human.

Use only the information I provided for personalization. Do NOT invent facts about this prospect or their company.

I'm stuck on a deal and need a fresh strategic perspective.

**The deal:** [Company, size, what they'd buy]
**Current stage:** [Where it is in the pipeline]
**Decision-makers:** [Who's involved, what each one cares about]
**Champion:** [Who's supporting us internally and why]
**Blockers:** [What's preventing the deal from closing]
**History:** [What's happened so far — meetings, objections, delays]
**Competitive situation:** [Who else they're considering, if known]

Analyze this deal and give me:
1. Diagnosis — Why is this deal stuck? What's the real blocker (it might not be what I think)?
2. Stakeholder map — What does each decision-maker need to hear to say yes?
3. Three potential moves — Different approaches I could take this week to un-stick the deal, ranked by likelihood of success
4. A business case draft — Something my champion can share internally to build support
5. Kill criteria — At what point should I walk away and focus elsewhere?

Be direct. If the deal looks dead, say so. My time is valuable.

I just finished a sales call. Here are my raw notes:

[Paste voice memo transcript or typed notes — messy is fine]

Extract and format for my CRM:
1. **Key pain points mentioned** — In the prospect's words
2. **Decision criteria** — What matters to them (explicit and implied)
3. **Timeline** — Any dates or urgency signals
4. **Budget signals** — Anything about budget, pricing sensitivity, or approval process
5. **Competitive mentions** — Other vendors they referenced
6. **Objections raised** — Concerns, pushback, or hesitations
7. **Next steps** — What was agreed, with dates
8. **Deal health assessment** — Based on these notes, rate this deal as: strong, progressing, at risk, or stalled. Explain why.

Keep it concise. My CRM fields have character limits. No fluff.

I need to draft an AI usage policy for my company. Here's the context:

**Company:** [Size, industry, type of work you do]
**Current AI usage:** [How people are using AI now — formal or informal]
**Sensitive data we handle:** [Types of data — client data, financial data, personal data, etc.]
**Regulatory environment:** [Any industry-specific regulations — GDPR, HIPAA, financial compliance, etc.]
**Company culture:** [Risk tolerance — conservative, moderate, progressive]

Draft a company AI policy covering:
1. Purpose statement — Why we're creating this policy (enable responsible AI use, not restrict it)
2. Scope — Who this applies to and which AI tools it covers
3. Data classification — Three tiers (green/yellow/red) with specific examples from our industry
4. Approved use cases — What employees CAN use AI for, with examples
5. Restricted use cases — What requires manager approval first
6. Prohibited use cases — What is never acceptable
7. Disclosure guidelines — When and how to tell clients, partners, or stakeholders that AI was used
8. Quality assurance — The verify/trust framework applied to our work (what must be human-reviewed before going external)
9. Data handling — How to anonymize sensitive information before using it as AI input
10. Policy review schedule — How often we revisit this policy (recommend quarterly in the first year)

Tone: Enabling, not policing. This should make people confident about using AI, not afraid of violating rules. Think guardrails on a highway — they keep you safe while letting you move fast.

[VERIFY] all regulatory references against our actual compliance requirements before publishing.

Here's my AI ROI tracking data from the last quarter:

[Paste your tracker — task, time saved, quality notes, patterns]

Also, here's what I tried that didn't work well:
[List tasks where AI didn't help much or made things worse]

Analyze this data and give me:
1. **ROI Summary** — Total hours saved, estimated dollar value (use a loaded cost of $[your hourly rate x 1.5] per hour), and the top 3 highest-ROI tasks
2. **Pattern Analysis** — What types of tasks benefit most from AI? What types don't? Why?
3. **Quality Impact** — Where did AI improve quality beyond just speed? Where did quality suffer?
4. **Blind Spots** — Based on my task list, what recurring tasks am I NOT using AI for that I probably should be?
5. **Next Quarter Plan** — Three specific experiments to run next quarter based on these patterns
6. **The "Stop Doing" List** — Any AI-assisted tasks where the time investment isn't worth the return

Be honest. If AI isn't helping in an area, say so. I'd rather reallocate my effort than keep using a tool out of habit.

I'm about to open a new position. Before writing the job description, help me pressure-test the role definition:

**What triggered this hire:** [Growth, departure, new function, pain point]
**Current team structure:** [Who does what today]
**Tasks this person would take over:** [List them]
**Tasks this person would create:** [New responsibilities that don't exist yet]
**Budget constraint:** [Salary range]

Challenge me:
1. Could any of these tasks be redistributed to existing team members instead of hiring?
2. Are we hiring for one role or accidentally combining two? (Look for mismatched skill profiles)
3. Is the seniority level right for the tasks described? (Am I overqualifying or underqualifying?)
4. What's the opportunity cost of NOT hiring for 3 more months?

Be direct. If this hire doesn't make sense, say so. Better to know now than after the offer.

Here's our department's budget vs. actual for this quarter:

[Paste the data — line items, budgeted amounts, actual amounts]

Write a budget narrative for the finance review meeting:
1. **Executive summary** — Three sentences: where we are overall, the biggest variance, and one action being taken
2. **Favorable variances** — What came in under budget and why (use the context I'll provide for each)
3. **Unfavorable variances** — What exceeded budget, why, and what we're doing about it
4. **Forecast impact** — Based on Q[current] actuals, what does this suggest for the full-year forecast?
5. **Decisions needed** — Any budget reallocations or approvals needed from leadership

Use ONLY the data and context I provide. Do NOT invent explanations for variances — if I haven't explained a variance, flag it as "explanation needed" so I can fill it in.

Tone: Factual, confident, concise. Executives don't read budget narratives for pleasure. Respect their time.

I'm building a knowledge base for my consulting practice. Here's a completed client deliverable:

[Paste the deliverable — anonymize client details first]

Extract:
1. **Frameworks used** — Any analytical framework, assessment model, or structured approach used in this deliverable. Name it, describe it in one paragraph, and note where in the document it appears.
2. **Methodology** — The step-by-step approach taken. What was the research method? What data was collected? How was it analyzed?
3. **Reusable templates** — Any structure (table, matrix, scorecard, checklist) that could be reused for a different client in a different industry.
4. **Key insights** — Client-agnostic findings that apply beyond this specific engagement. What did you learn about the PROBLEM TYPE, not just the client?
5. **Data sources** — What external sources were referenced? Are they still current?

Format this as a knowledge base entry I can search later. Use clear headers, tags (e.g., #strategy #competitive-analysis #healthcare), and cross-references to related concepts.

Important: This must be fully anonymized. Replace all client names with "[Client]", specific revenue figures with "[Revenue figure]", and any identifying details with generic placeholders.