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 — e.g., senior account executive] at [your company — e.g., a B2B SaaS company selling revenue intelligence tools]. Write a follow-up email to [recipient — e.g., the VP Sales who attended our demo yesterday]. The meeting covered [key topics — e.g., our pipeline analytics feature and the Salesforce integration]. The recipient's main concern was [specific concern — e.g., a 6-week migration timeline during Q4 close]. The goal of this email is [specific outcome — e.g., get them to schedule a technical deep-dive with their RevOps team]. Tone: [e.g., confident, specific, concise — like a trusted advisor, not a desperate seller]. Keep it under [word count — e.g., 150] words. Include a clear CTA: [what you want the reader to do — e.g., "Reply with two times that work for a 30-minute session with your RevOps lead"].

Context: [1-2 sentences — e.g., "Three stakeholders were in the demo. Our champion (Head of RevOps) is supportive. The VP Sales asked tough questions but didn't shut us down. The Sales Manager was visibly excited."]

I've pasted our [describe the data — e.g., CRM export of all closed-won and closed-lost deals from Q1, including deal size, sales cycle length, industry, number of stakeholders, and loss reason]. Analyze this from the perspective of a [role — e.g., VP Sales focused on improving win rate and reducing cycle time]. Focus on:
1. [Specific aspect — e.g., which deal characteristics predict a win vs. a loss]
2. [Specific aspect — e.g., how sales cycle length correlates with deal size and outcome]
3. [Specific aspect — e.g., what the top 3 loss reasons have in common and what we can address]

For each, provide: a finding (what the data shows), an insight (what it means for our strategy), and a recommendation (what to change next quarter).

Format as a table with columns: Aspect | Finding | Insight | Recommendation.
End with a 3-sentence executive summary of the single most impactful change we could make.

IMPORTANT: base every finding on the data I provided. If the data does not contain enough information to answer a question, say "data not provided" — do not estimate or infer.

Create a [type of document — e.g., tailored sales proposal] for [audience — e.g., the buying committee at a 300-person fintech company, including the VP Sales (economic buyer), Head of RevOps (champion), and CFO (final approver)]. Purpose: [what this document should accomplish — e.g., justify a $180K annual investment by connecting our platform capabilities to their specific operational pain points and showing projected ROI].

Include these sections:
1. Executive Summary (3-5 sentences — the business case, not the product pitch)
2. [Section — e.g., Current State — the prospect's specific challenges based on what we learned in discovery and demo]
3. [Section — e.g., Proposed Solution — how our platform addresses each challenge, with emphasis on the features they responded to most]
4. [Section — e.g., ROI Projection — projected time savings, revenue impact, and payback period based on the data I'll provide below]
5. Implementation & Timeline (specific milestones, not vague phases)
6. Recommended Next Steps (specific actions with owners and dates)

Constraints:
- Total length: [target — e.g., 2,000 words]
- Tone: [e.g., strategic and confident — this is a business case, not a brochure]
- [Any specific inclusions — e.g., reference the pilot results I'll paste below]
- [Any exclusions — e.g., do not include standard pricing — that's a separate conversation with procurement]
- [Stakeholder framing — e.g., the CFO cares about payback period and risk; the VP Sales cares about rep productivity; the Head of RevOps cares about integration depth and migration timeline]

Context: [2-3 sentences — e.g., "They completed a successful 30-day pilot with their East Coast team. Pipeline visibility improved 40% during the pilot. The VP Sales said 'this is the first time I've trusted a forecast' in their pilot debrief. Main blocker: the CFO wants to see hard ROI before approving a company-wide rollout."]

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.

Write a market analysis covering [topic]. Flag any specific statistics or claims with `[VERIFY]` so I know which ones to check against primary sources. For the analysis, recommendations, and structure — be bold and direct.

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.

I need to reverse-engineer my Ideal Customer Profile from my won deals. Here are my last 10 closed-won deals with the details I can share:

Deal 1: [Company name], [industry], [employee count], [deal size], [sales cycle length]. Champion: [their role]. Main pain point: [what problem they were solving]. Trigger: [what initiated their buying process — e.g., new VP hired, competitor launched a feature, failed audit]. Tech stack: [tools they used that are relevant]. Competitors in the deal: [who else they evaluated].

[Repeat for deals 2-10]

Based on these wins, extract:
1. The firmographic pattern — what do these companies have in common in terms of size, industry, and geography?
2. The technographic pattern — what tools, platforms, or infrastructure appear across multiple wins?
3. The behavioral pattern — what signals did these companies emit before they entered the buying cycle (hiring patterns, content themes, event attendance)?
4. The situational triggers — what events or changes triggered the buying process?
5. The anti-pattern — are there any traits that NONE of my wins share? These are disqualification criteria.

Format the output as a one-page ICP document I can share with my SDR team. Include specific thresholds (e.g., "50-200 employees" not "mid-market").

I'm preparing to pursue a Tier 1 enterprise prospect. Here's what I know:

**Prospect:** [Name], [Title] at [Company]
**My product/service:** [One sentence — what you sell and who benefits]
**My ICP criteria:** [Paste from your ICP document or summarize: industry, size, trigger signals]

**Research I've gathered:**
[Paste any combination of: LinkedIn profile summary, company About page, recent press release, job postings, earnings call excerpt, industry report mention, social media posts]

Produce a Prospect Intelligence Brief with these sections:

1. **Company Situation** — What they do, their current trajectory, and any public signals of growth or challenge. Separate facts from inferences.
2. **Recent Signals** — Anything in the last 6 months: funding, leadership changes, product launches, partnerships, hiring patterns. Flag each signal as [VERIFIED — from provided data] or [INFERRED — needs verification].
3. **Likely Pain Points** — Based on the signals and company stage, what 3 problems are they probably facing that my product addresses?
4. **Buying Committee Hypothesis** — Based on company size and structure, who is likely involved in this purchase? Map: economic buyer, champion, technical evaluator, potential blocker. Note: these are role hypotheses, not confirmed names — I need to verify on LinkedIn.
5. **Competitive Landscape** — Who else might be selling to them? What alternatives do they likely evaluate?
6. **Three Outreach Angles** — Ranked by relevance. Each angle should reference a specific signal or pain point and connect it to my offering. The first sentence of each angle should be usable as an email opener.

I'm mapping the buying committee for an enterprise deal.

**Company:** [Name], [employee count], [industry]
**Product I'm selling:** [One sentence]
**Primary contact so far:** [Name, Title]
**What I know about their org:** [Anything — LinkedIn intel, past interactions, org chart fragments, public team pages]

Based on companies of this size and type buying this category of product, map the likely buying committee:

1. **Economic Buyer** — Who controls the budget? What's their likely title? What do they care about (ROI, risk, strategic alignment)?
2. **Champion** — Who internally would advocate for this purchase? What signals suggest they have this pain point?
3. **Technical Evaluator** — Who will assess whether this integrates with their existing stack? What questions will they ask?
4. **End Users** — Who will actually use this daily? What's their likely objection?
5. **Potential Blocker** — Who might resist this purchase? Why? (competing priorities, competing vendor relationship, "we built it in-house" mentality)

For each role: suggest the most likely job title, the research I should do to identify the actual person, and one question I should be ready to answer when I encounter them.

IMPORTANT: These are ROLE HYPOTHESES based on typical buying patterns. Do not invent specific names or claim specific people hold these roles. I will verify all names and titles on LinkedIn.

I have a batch of trade show leads to research. Process these prospects at Tier 2 depth (company summary + one personalized hook + pain hypothesis).

**My product:** [One sentence]
**My ICP criteria:** [Key criteria from your ICP document]

For each prospect, provide:
1. **Company snapshot** (2-3 sentences): What they do, approximate size, current trajectory
2. **ICP fit score** (High / Medium / Low): How well do they match our criteria? Note which criteria they match and which are unknown.
3. **Likely pain point**: Based on their industry and size, what's the one problem we solve that probably keeps them up at night?
4. **Personalized hook**: One sentence I could use in an email opening that shows I know something about their situation. Base this ONLY on information I provide — do not invent company-specific details.
5. **Tier recommendation**: Should this prospect stay at Tier 2, upgrade to Tier 1 (deeper research warranted), or downgrade to Tier 3 (batch outreach only)?

Prospect 1: [Name], [Title] at [Company]. Notes from conversation: [anything you remember or wrote on the card]
Prospect 2: [Same format]
... (continue for 10-15 prospects)

After processing, summarize: How many Tier 1 upgrades? How many Tier 3 downgrades? Which 3 prospects should I prioritize this week?

I'm connecting with a prospect on LinkedIn. Write a connection request message (under 300 characters) for this person:

**Prospect:** [Name], [Title] at [Company]
**Something specific about them:** [A LinkedIn post they wrote, a company initiative they announced, a conference they spoke at, a mutual connection, a shared professional group]
**Why connecting makes sense for THEM:** [What value could this connection bring to the prospect — not to me]

Rules:
- Under 300 characters (LinkedIn's limit)
- Reference the specific detail I provided — no generic "I'd love to connect"
- Frame the connection in terms of value to THEM, not to me
- No sales pitch. No product mention. No "exploring synergies."
- Tone: professional peer, not vendor

Score these prospects against our ICP and assign tiers. Use the ICP criteria from this Project's instructions.

For each prospect, evaluate:
- **Firmographic fit** (company size, industry, geography): Strong / Partial / Weak
- **Technographic fit** (relevant tools/platforms): Match / Unknown / Mismatch
- **Behavioral signals** (hiring patterns, content, events): Present / Absent
- **Situational triggers** (recent changes that create a buying window): Active / None detected

**Tier assignment:**
- Tier 1 (deep research): Strong firmographic + at least 2 other criteria match
- Tier 2 (standard research): Strong firmographic + 1 other criteria match, OR partial firmographic + 2 other criteria match
- Tier 3 (batch outreach): Partial firmographic only, or too many unknowns to tier higher

Prospect list:
[Paste prospect names, titles, companies, and any known details]

Output as a table: Prospect | Company | Firmographic | Technographic | Behavioral | Situational | Tier | Recommended Action

Flag any factual claims about the prospect or their company with `[VERIFY]` — I will confirm these against a primary source before sending.

I need a personalized first-touch email for a cold outreach sequence.

**Prospect context** (paste their LinkedIn profile, company news, or about page):
[Paste real research from Chapter 03 here]

**What I sell:** [One sentence — product/service and primary outcome]
**Our differentiator:** [What makes us different from the obvious alternatives]
**Similar win:** [One client result — company type, what you did, measurable outcome]

Write a first-touch email following these rules:
- Under 120 words
- First sentence references something SPECIFIC from their context — not flattery, relevance
- Second sentence connects my offering to a problem implied by their context
- Third sentence is a low-commitment question (yes/no, not a meeting request)
- PS line with the similar win as social proof
- No "I hope this finds you well." No "I'd love to." No "I came across your profile and was impressed."
- Tone: peer-to-peer, not salesperson-to-prospect
- Subject line: under 6 words, curiosity-driven

For any prospect-specific claims you make in the email, add `[VERIFY]` next to the claim so I can fact-check before sending.

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]
**My offering:** [What you sell and for whom]
**The prospect's likely objection:** [The #1 reason this persona hesitates]

Write three follow-up variants:

**Branch A — Opened but didn't reply** (interested but not convinced)
- Add a new proof point or case study that deepens the value prop
- Lower the ask: offer something they can consume passively (a benchmark report, a 2-minute video, a case study PDF)
- Don't acknowledge the open — no "I see you read my email"
- Under 100 words. Subject line: reference the topic, not the follow-up.

**Branch B — Didn't open** (missed it or subject line failed)
- Completely new subject line — different angle than the original
- Rephrase the core message in a different format (if original was a question, try a bold claim or a stat)
- Under 80 words. Fresh start energy — as if email 1 never happened.

**Branch C — Replied with an objection** (engaged but resistant)
- Acknowledge their specific concern in the first sentence — no deflecting
- Share one concrete example of how a similar client had the same concern and resolved it
- End with a low-commitment ask that addresses the objection: "Would it help to see how [company] handled exactly this?"
- Under 120 words. Tone: peer-to-peer, not defensive.

No "just following up" in any version. No "I hope this finds you well."

Build a 5-touch enterprise executive email sequence for me.

**Target persona:** [Title, company size, industry]
**Their likely priorities:** [2-3 strategic concerns based on Chapter 03 research]
**What I sell:** [Product/service and primary business outcome]
**Differentiator:** [What separates you from the alternative they're probably considering]
**Best case study for this persona:** [Company name, their situation, measurable result]

Sequence parameters for enterprise executives:
- **Tone:** Formal, strategic, peer-level. No exclamation points. No "excited to share."
- **Length:** Under 100 words per email. Every sentence must survive a "so what?" test.
- **Timing:** Day 0, Day 5, Day 12, Day 19, Day 28
- **Social proof type:** Enterprise logos and scale metrics

Touch 1 (Day 0): Insight opener — one strategic observation about their industry or company. No pitch. End with a question.
Touch 2 (Day 5): Value resource — an industry insight, benchmark, or report relevant to their role. No ask.
Touch 3 (Day 12): Social proof — peer company story with measurable result. Reframe the problem from a different angle than Touch 1.
Touch 4 (Day 19): Objection preempt — address the #1 reason enterprise buyers in this segment hesitate. Be honest.
Touch 5 (Day 28): Breakup — close the loop. Offer one useful resource. Zero pressure. Permanent open door.

Subject lines: under 5 words each. No clickbait. No "Quick question."
For any specific claims about the prospect's company or industry, add `[VERIFY]` so I can fact-check.

Write a breakup email — the final email in my outreach sequence.

**Context:** I've sent 4 previous emails to [prospect type] 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 keep filling your inbox."
- Offer something genuinely useful — a resource, a benchmark, an insight — with ZERO expectation
- Close with a permanent open door: "If this becomes relevant in six months, I'm here."
- Under 80 words. No emotional manipulation. No countdown timers. No "last chance" language. No hidden pitch.
- Tone: one professional respecting another's priorities.

Write a 3-email re-engagement sequence for dormant leads.

**Context:** These prospects went cold [timeframe] ago. Original conversation was about [topic]. They know who we are and what we sell.

**Re-engagement trigger:** [Choose one: new company signal / new industry insight / new product capability / sufficient time gap]

**Trigger details:** [Describe the specific trigger — e.g., "We just published a benchmark report on [topic]" or "Their company recently announced [news]"]

Email 1 — The Re-Opener (Day 0):
- Acknowledge the gap honestly: "It's been a while" is fine as a bridge, not as the reason to reply
- Lead with the trigger — the new information that makes this email timely
- Low-friction CTA: "Worth a fresh look, or has the priority shifted?"
- Under 100 words

Email 2 — The Value Add (Day 5):
- Don't reference the silence again — move forward
- Deliver one specific insight or resource related to the trigger
- Under 80 words

Email 3 — The Gentle Close (Day 12):
- Brief check-in. "I shared a couple of things over the past two weeks — any of it resonate?"
- Offer to reconnect OR to stop reaching out. Give them explicit permission for either.
- Under 60 words

I want you to learn my email writing voice. Below are 5 emails I wrote that got replies. Study them and identify my patterns.

**My emails:**
[Paste 5 of your best cold emails or follow-ups — ones that got real responses]

**Now analyze my voice:**
- What's my typical sentence length?
- Do I use questions, statements, or commands to open?
- What's my default tone — formal, casual, blunt, warm?
- What patterns do I repeat?
- What do I never do?

**Then write the next email in my sequence using MY voice — not yours.**
Topic: [What the email needs to cover]
Recipient: [Prospect type]
Purpose: [Which touch in the 5-Touch Framework]

Anti-patterns (DO NOT include):
- "I hope this finds you well"
- "I noticed that..." or "As a leader in..."
- Opening with a question
- Exactly three bullet points
- "Would you be open to a quick chat?"
- Any sentence that starts with "I understand that..."
- Hedging phrases: "In today's fast-paced," "It's no secret that," "As you know"

I'm building an objection handling playbook from our actual won deals. Below are transcripts (or detailed notes) from deals where specific objections came up and we still closed. Analyze these and extract the playbook hiding in our own wins.

**Deal 1:** [Paste transcript excerpt or detailed notes — include the objection, the rep's response, and what happened next]

**Deal 2:** [Same format]

... (include 5-10 deals — the more, the better)

For each deal:
1. What specific objection was raised? Categorize it (price, timing, competition, authority, status quo, trust, complexity, ROI, risk, or inertia).
2. What did the rep say or do that kept the deal alive? Quote the exact language if available.
3. What PRINCIPLE made it work? (e.g., "acknowledged the concern before reframing," "asked a diagnostic question instead of defending," "shifted from features to business impact")
4. What would have happened if the rep had responded defensively instead?

After analyzing all deals:
- What patterns do you see across the winning responses? Is there a consistent framework the reps are using (maybe without realizing it)?
- Which objection categories had the strongest responses? Which ones felt like the rep got lucky rather than skilled?
- Build me a draft playbook organized by objection category, with the framework principle and 2-3 example responses drawn from these real deals.

I need to prepare for a competitive deal. The prospect currently uses [competitor name] and seems satisfied but agreed to a meeting.

**My product:** [Brief description of what you sell and your key differentiators]

**The prospect:** [Role, company type, industry, what you know about their situation]

**What I know about their current setup:** [Any intelligence about how they use the competitor — features they rely on, pain points they've mentioned, team size, contract status]

Build me a competitive positioning brief:

1. **The Validation Statement** — How to acknowledge their current solution genuinely (not a backhanded compliment)
2. **3 Diagnostic Questions** — Questions that surface the gap between what they have and what they need, WITHOUT bashing the competitor
3. **The Gap Positioning** — Based on what I know about this prospect, what's the most likely unmet need my solution addresses? Frame it around their situation, not a feature comparison.
4. **Evidence Points** — What kind of proof would be most compelling for this buyer persona? (case study, ROI data, pilot offer, peer reference)
5. **Landmines to Avoid** — What should I absolutely NOT say about this competitor? What claims would backfire?

Important: Do NOT fabricate specific claims about [competitor name]'s pricing, features, or capabilities. Flag any competitive claims with `[VERIFY]` so I can check them against our battle card or the competitor's current documentation.

When building competitive positioning, NEVER state specific competitor pricing, features, or implementation timelines as fact. Always flag uncertain competitive claims with `[VERIFY]`. Draw competitive insights from the uploaded battle cards and win/loss notes, not from your general knowledge.

I need to practice objection handling before a high-stakes call. Play the role of a prospect and make me work for it.

**My context:** I sell [what you sell] to [buyer type]. My company is [brief description].

**The prospect you're playing:** [Role, company type, size, industry. Personality: skeptical / analytical / impatient / hostile — pick one or describe]. Background: [Any relevant details — they've been burned before, they're evaluating competitors, their CEO is risk-averse, they're under budget pressure].

**Difficulty level:** [1 = cooperative, 2 = skeptical, 3 = hostile]

**Rules for you as the prospect:**
- Stay in character throughout. Don't break to offer advice mid-conversation.
- At Level 2+: don't accept my first response to any objection. Push back at least once.
- At Level 3: you've talked to our competitor and liked what you saw. You know our product's weakness is [name it]. Challenge any vague claim with "Can you be more specific?" or "Prove it."
- Raise objections naturally — don't list them. Weave them into the conversation the way a real buyer would.
- If my response is weak, show it through your behavior (skepticism, going quiet, changing the subject). Don't explain why it was weak — make me feel it.

We'll go 7 rounds of back-and-forth. After round 7, break character and give me:
1. A score out of 10 for each of my responses, with one sentence explaining why
2. The moment I was strongest — what I did right and why it worked
3. The moment I lost you — what I said that made you pull back
4. A rewritten version of my weakest response
5. One thing I should practice before the real call

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

**WON DEALS:**

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

**LOST DEALS:**

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

Run a deep structural analysis:

1. **Objection patterns:** Which objection categories appeared most in wins vs. losses? Which objection has the highest correlation with lost deals?
2. **Response quality:** In deals where the same objection appeared in both wins and losses, how did the handling differ? What did winning reps do that losing reps didn't?
3. **Timing patterns:** At what point in the sales cycle do lost deals stall? Is there a "danger zone" — a specific week or stage where deals die most often?
4. **Stakeholder patterns:** Which buyer roles appeared in won deals vs. lost deals? Is there a stakeholder configuration that predicts success?
5. **Competitive dynamics:** When a competitor was involved, what separated the wins from the losses?
6. **The hidden pattern:** What's ONE insight from this data that we probably haven't noticed — a correlation between two variables that isn't obvious from reviewing deals individually?
7. **Top 3 recommendations:** Based on these patterns, what are the 3 most impactful changes we could make to our objection handling or sales process? Grounded in THIS data, not generic advice.

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

I want to prevent our most common objections instead of just handling them better. Analyze our sales conversation flow and help me build proactive framing.

**Our typical sales process:**
1. Discovery call: [What we cover, what we ask, how long]
2. Demo/presentation: [What we show, who attends]
3. Proposal: [When it's sent, what it includes]
4. Negotiation/close: [Typical dynamics]

**Our top 3 objections (and when they typically arise):**
1. [Objection] — usually comes up during [stage]
2. [Objection] — usually comes up during [stage]
3. [Objection] — usually comes up during [stage]

For each objection:
1. Why does it arise at that specific stage? What's missing from the conversation BEFORE that point?
2. Write a **preemptive frame** — language I can use earlier in the process to address the underlying concern before it becomes an objection. Format: "Companies in your space typically ask about [X], so let me address that upfront..."
3. Where exactly in the process should this frame be deployed for maximum impact?
4. What's the risk of preemptive framing? (Sometimes addressing a concern the prospect hasn't raised yet can plant a seed of doubt.)

I manage a sales team of [number] reps. I want to mine our collective objection data for team-wide patterns and blind spots.

**Objection data by rep:**

Rep 1 — [Name/anonymous ID]:
- Deals this quarter: [X won, Y lost]
- Most frequent objections: [list]
- Objections that led to closed-won: [which ones, how handled]
- Objections that led to closed-lost: [which ones, how handled]

Rep 2: [Same format]
... (continue for all reps)

Analyze across the team:
1. **Top 5 objections by frequency** — What does the team face most often?
2. **Best handler per objection** — Which rep handles which objection best (measured by deal advancement after the objection)? What are they doing differently?
3. **Systemic weakness** — Is there an objection that NOBODY on the team handles well? What makes it hard?
4. **Buying signals in disguise** — Are any "objections" actually interest signals? (e.g., "How does implementation work?" isn't a pushback — it's engagement)
5. **Cross-pollination plan** — For each of the top 3 objections, which rep's approach should become the team standard? How would you structure a 30-minute training session around their technique?

I'm preparing for a complex enterprise deal and need to map the buying committee. Build a Stakeholder Intelligence Canvas from the data below.

**Deal context:**
- What we sell: [your product/service]
- Deal size: [approximate value]
- Sales stage: [discovery / evaluation / negotiation / final decision]

**Data sources (paste below):**
- Call transcripts or notes: [paste relevant excerpts]
- Email threads: [paste — pay attention to who's cc'd, who replies, who stays silent]
- Org chart or LinkedIn profiles: [paste or describe what you know about reporting lines]
- Champion intel: [what your champion has told you about internal dynamics]

**For each stakeholder identified, produce:**

1. **Name and role** — title and function in this deal
2. **Stakeholder type** — Decision Maker / Champion / Influencer / Blocker / End User
3. **Current stance** — Advocate / Neutral / Skeptical / Hostile / Unknown (with evidence for your assessment)
4. **Hypothesized motivation** — what they likely care about most. **Mark every motivation as [HYPOTHESIS — validate in conversation]**
5. **Decision authority** — Veto / Vote / Influence Only / None
6. **Engagement strategy** — how to approach this person specifically, what message resonates, what to avoid
7. **Risk flags** — anything in the data that suggests this person could block or delay the deal

Also flag:
- **Ghost stakeholders:** Names that appear in cc fields or are mentioned but have never spoken. These could be silent evaluators or irrelevant cc's — I need to investigate.
- **Missing roles:** Based on this deal size and company type, which stakeholder roles would you expect to be involved but aren't represented in the data? Who am I probably missing?

Be direct about gaps in the data. If the evidence is thin for a stakeholder, say so.

I need a strategic coaching session for a complex deal. Play the role of a senior sales strategist. Challenge my assumptions. Tell me what I don't want to hear.

**Deal context:**
- What we sell: [product/service and price range]
- Deal size: [value]
- Sales stage: [current stage]
- Time in current stage: [weeks]
- Total cycle so far: [weeks since first contact]
- Deal momentum: [accelerating / steady / slowing / stalled]

**Stakeholder landscape:**
[Paste your stakeholder map from the previous prompt, or summarize: who's involved, their stance, their influence]

**Competitive positioning:**
- Known competitors in this deal: [who]
- Where we win vs. them: [specific advantages]
- Where we lose vs. them: [specific weaknesses — be honest]
- What the prospect has said about alternatives: [direct quotes if available]

**Current blockers:**
- What's preventing the deal from moving forward: [be specific]
- What we've tried to unblock it: [what actions, what result]
- Internal constraints: [pricing limits, resource availability, timeline restrictions]

**Produce a Deal Strategy Brief:**

1. **Deal Health Assessment** — Are we ahead, behind, or at parity? What's the honest evidence?
2. **Primary Path** — The most likely route to close. Specific next actions per stakeholder, with sequence and timing.
3. **Contingency Path** — If the primary path hits resistance, what's Plan B?
4. **Stakeholder-Specific Messaging** — For each key stakeholder: the one message that moves them from their current stance toward advocacy. What they need to hear, from whom.
5. **Risk Assessment** — What could kill this deal that we're not seeing? What questions should we ask to surface hidden risks?
6. **Competitive Counter-Moves** — If the competitor does [X], here's our response. If the prospect brings up [competitor strength], here's the reframe.
7. **Three Things to Do This Week** — Ranked by impact. Not "follow up" — specific actions with specific people.

Don't be polite. Be useful. If this deal is in worse shape than I think, say so.

I have a negotiation call coming up and need to prepare a complete Negotiation Prep Stack. Act as a negotiation strategist.

**Deal context:**
- What we sell: [product/service]
- Deal value: [price we quoted]
- What the prospect is pushing back on: [price, terms, scope — be specific]
- What the prospect has said: [direct quotes about their concerns or demands]

**Our position:**
- Our cost structure: [what this deal costs us to deliver — margin information]
- Our alternatives: [other deals in pipeline, impact of losing this one]
- Internal constraints: [minimum price, maximum discount authority, non-negotiable terms]
- Strategic value beyond revenue: [logo value, reference potential, expansion potential]

**Their position:**
- Their alternatives: [competitors they're evaluating, status quo option, internal build option]
- Their timeline pressure: [do they have a deadline? a budget cycle? a board meeting?]
- Their stated budget: [what they've said about budget, if anything]
- Decision dynamics: [who decides, who influences, who has to approve the terms]

**Build a Negotiation Prep Stack:**

1. **BATNA Analysis** — Our BATNA and their likely BATNA. Who has more leverage and why?
2. **Walk-Away Triggers** — Specific conditions under which this deal isn't worth winning. Define the line.
3. **Concession Hierarchy** — Three tiers of concessions, ordered from lowest cost to highest:
   - Tier 1 (give first): Low cost to us, high perceived value to them
   - Tier 2 (give if needed): Medium cost, traded for a reciprocal commitment
   - Tier 3 (last resort): High cost, only if they commit to [specific trade]
   For each concession: what we give, what it costs us, what we ask for in return.
4. **Value Anchoring Points** — Three statements that reframe price as investment, tied to their specific business outcomes.
5. **Objection Responses** — For each likely pricing objection: the objection, the underlying concern, the response, and a supporting proof point.
6. **Red Lines** — What we absolutely will not concede, and the language to decline gracefully.

I need an adaptive pipeline review. Don't just answer standard questions — analyze the data and tell me what questions I should be asking this week based on what the pipeline actually shows.

**Pipeline data:**
[Paste your CRM export with: deal name, stage, value, days in current stage, days since last activity, number of contacts engaged, segment/vertical, next scheduled action, close date]

**Historical benchmarks:**
- Average days per stage for won deals: [if you have this data]
- Average win rate by segment: [if available]
- Typical deal cycle length: [your average]

**Analyze and produce:**

1. **Pipeline Composition Snapshot** — Total value by stage, by segment, by deal size tier. Flag any concentration risks (more than 40% of pipeline value in one segment, one deal, or one stage).

2. **Velocity Analysis** — Which deals are moving faster or slower than historical averages? Flag deals sitting in a stage for more than 1.5x the average.

3. **Stall Detection** — Deals with no activity in 14+ days. For each: how long since last activity, what was the last activity, and what's the risk of losing momentum.

4. **Single-Threading Risk** — Deals with only one contact engaged. These are one ghosting away from dead.

5. **Forecast Confidence** — For each deal, rate forecast confidence (High / Medium / Low) based on: stage, velocity, activity recency, and contact breadth. Calculate a confidence-weighted forecast.

6. **Top 5 Actions for This Week** — Ranked by revenue impact. Not "follow up on Deal X" — specific actions: "Schedule a technical evaluation call for Deal X to break the Stage 3 stall" or "Add a second contact to Deal Y to reduce single-threading risk."

7. **This Week's Questions** — Based on what the data shows right now, what are the three questions I should be discussing in my pipeline review meeting that I might not have thought to ask?

I need to generate a customized proposal for a deal with multiple stakeholders. Each stakeholder evaluates through a different lens. Help me build a proposal that speaks to each one.

**Deal overview:**
- Prospect: [company name and what they do]
- What we're proposing: [product/service, scope, pricing structure]
- Deal size: [value]
- Implementation timeline: [estimated]

**Stakeholder personas (who will read this proposal):**

Persona 1 — [Name, Title, e.g., CFO]:
- What they care about: [e.g., payback period, TCO, risk mitigation]
- What they fear: [e.g., cost overruns, budget surprises, poor ROI]
- Evidence that matters to them: [e.g., financial projections, case study ROI data]

Persona 2 — [Name, Title, e.g., CTO]:
- What they care about: [e.g., integration depth, migration risk, security]
- What they fear: [e.g., vendor lock-in, technical debt, disruption to current stack]
- Evidence that matters to them: [e.g., architecture diagrams, integration specs, security certifications]

Persona 3 — [Name, Title, e.g., End-User Team Lead]:
- What they care about: [e.g., ease of adoption, training timeline, daily workflow impact]
- What they fear: [e.g., another tool nobody uses, steep learning curve, workflow disruption]
- Evidence that matters to them: [e.g., user testimonials, adoption metrics from similar companies]

**Generate a proposal with:**

1. **Executive Summary** — Written for the executive sponsor. Strategic alignment, business outcomes, why now.
2. **For each persona, a dedicated section** that leads with their priorities, addresses their fears, and uses the type of evidence that resonates with them. Each section should feel like it was written specifically for that reader.
3. **ROI Section** — Financial justification with payback period, TCO comparison vs. status quo, and conservative projections. **Use only numbers I provide or flag with [NEEDS INPUT] — do not invent financial projections.**
4. **Implementation Plan** — Phased, with milestones that address each persona's concerns (CTO sees integration checkpoints, end users see training milestones, CFO sees cost gates).
5. **Risk Mitigation** — Proactively address the top fear of each persona.

Use the prospect's language from our conversations, not generic marketing language. If they said "we're drowning in manual processes," write "manual processes" not "operational inefficiencies."

I'm preparing a Quarterly Business Review for a key account. Synthesize the data below into a QBR Intelligence Brief.

**Account:** [company name]
**Contract value:** [ARR]
**Renewal date:** [date — months remaining]
**Original goals from kickoff:** [what they bought for — list 3-5 goals]

**Data inputs:**
- Usage data (past 90 days): [MAU, login frequency, feature adoption — up/down/flat vs. previous quarter]
- Support tickets (past 90 days): [count, themes, severity, tone of recent tickets]
- NPS/CSAT score: [latest score + trend]
- Last QBR summary: [one paragraph — what was discussed, what was promised]
- Champion status: [still in role? promoted? left?]

**Produce a QBR Intelligence Brief:**

1. **Scorecard** — For each original goal: Green (on track) / Yellow (at risk) / Red (off track), with one sentence of evidence.
2. **Support Ticket Analysis** — Not just volume — what patterns emerge? Are tickets shifting from "how do I?" to "why doesn't this work?" That tone shift is an early warning.
3. **Usage Opportunities** — Features they're not using that directly map to their stated goals. Don't suggest features randomly — connect each to a specific goal.
4. **Risk Flags** — Anything in this data that suggests dissatisfaction, disengagement, or churn risk. Include "silent signals" — declining logins, reduced feature breadth, champion departure.
5. **Expansion Signals** — Is there evidence they're ready for more? Growing team, new use cases emerging, feature requests that map to our premium tier.
6. **Recommended Talking Points** — What to bring up proactively, in what order, and what to avoid unless the customer raises it.
7. **Conversation Opener** — The one thing to lead with that shows you've been paying attention to their business, not just their usage data.

Mark any inferences that go beyond what the data directly shows with `[VERIFY]` — I need to validate these in 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]
- Prospect-specific assumptions I made: [list — e.g., inferred industry, assumed pain point, guessed company size from limited data]

This section is for the sales rep reviewing this output only. Do not include it in any prospect-facing content.

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 want to audit my current sales workflow for AI opportunities. Here is what my typical week looks like:

[Paste your weekly routine: prospecting activities, outreach tasks, pipeline reviews, deal prep, CRM updates, internal meetings, reporting]

For each activity, tell me:
1. Could Claude help? (Yes / Partially / No)
2. If yes: what type of help? (Research / Draft / Analyze / Strategize / Systematize)
3. Estimated time saved per occurrence
4. How often does this activity happen? (Daily / Weekly / Per-deal / Quarterly)
5. Which chapter of the book covers the relevant technique? (Ch03 Prospecting / Ch04 Outreach / Ch05 Objections / Ch06 Deal Intelligence)

Sort by "time saved x frequency" descending. My top 5 are where I start this week.

I need a Monday morning pipeline review. Here is my current pipeline:

[Paste your CRM pipeline export or list your active deals with: deal name, stage, amount, days in stage, next step, last activity date]

Give me:
1. **Advance this week** — Top 3 deals most likely to move forward with the right action. For each: the specific next step and why this week matters.
2. **At risk** — Deals showing stall signals (no activity 10+ days, stuck in stage, missing next steps). For each: the root cause hypothesis and a re-engagement action.
3. **Hidden opportunity** — One mid-funnel deal that deserves more attention than it is getting, based on deal size, stage velocity, or account potential.
4. **Kill or qualify** — Deals that should be closed-lost or sent back to discovery. Be honest.

Format as a Monday action list I can execute in order.

`[VERIFY]` Flag any assumptions about deal health that are based on inference rather than data I provided.