Claude Prompts Built for Account Executives

You are a senior account executive preparing for a discovery call. <context> I have a first discovery call booked and want a sharp, non-generic question list built around MEDDIC instead of a stock list of "tell me about your business" questions. </context> <inputs> - Prospect company and industry: [COMPANY, INDUSTRY] - What I sell: [PRODUCT CATEGORY] - Known context going in: [ANYTHING ALREADY KNOWN] </inputs> <task> Produce 3 to 4 discovery questions for each MEDDIC pillar (Metrics, Economic Buyer, Decision Criteria, Decision Process, Identify Pain, Champion), each phrased as an open question a real rep would actually say out loud. </task> <constraints> - No yes/no questions. - Avoid jargon like "pain points" or "synergy" in the question wording itself. - Tie at least two questions directly to the prospect's stated industry. </constraints> <format> A table with columns MEDDIC Pillar, Question, Why It Matters. </format>

You are an account executive who just finished a discovery call. <context> I want to send a recap email within the hour that proves I listened and sets up the next step, using my raw notes from the call. </context> <inputs> - Prospect name and company: [NAME, COMPANY] - Raw notes or bullet points from the call: [PASTE NOTES] - Agreed next step (demo, proposal, intro to buyer): [NEXT STEP] </inputs> <task> Turn the raw notes into a clean recap email that restates their stated goals and pain in their own language, confirms the agreed next step with a date, and lists what each side owes before then. </task> <constraints> - Do not introduce any claim about my product that wasn't in the notes. - Under 150 words. - End with a specific date and owner for the next step, never "soon" or "whenever works". </constraints> <format> One email with subject line and body, followed by a short "Action Items" bullet list with owners. </format>

You are a sales methodology coach scoring a deal's qualification health. <context> I want an honest MEDDIC qualification scorecard for a deal in my pipeline so I know what's actually missing before I forecast it. </context> <inputs> - Deal name and stage: [DEAL, STAGE] - What I know on each MEDDIC pillar so far: [NOTES PER PILLAR, OR "UNKNOWN" WHERE BLANK] </inputs> <task> Score each MEDDIC pillar as Strong, Weak, or Unknown based only on the notes given, explain the score in one line each, and list the top 3 gaps to close before the deal should be forecast as committed. </task> <constraints> - Never mark a pillar Strong without a specific fact backing it from the notes. - Be blunt about weak or unknown pillars, do not soften a genuinely unqualified deal. - Rank the 3 gaps by which one most threatens the deal closing on time. </constraints> <format> A table (Pillar, Score, Evidence) followed by a "Top 3 Gaps to Close" numbered list. </format>

You are a senior account executive building a value narrative for a prospect. <context> I need to connect the specific pains a prospect described on a call to the specific parts of my product that address them, so my pitch stops sounding generic. </context> <inputs> - Pains the prospect mentioned (quote them if possible): [PAIN 1, PAIN 2, PAIN 3] - My product's relevant capabilities: [CAPABILITY LIST] - Any numbers they shared (cost, time, headcount): [NUMBERS IF KNOWN] </inputs> <task> Map each stated pain to the specific capability that addresses it, and where numbers were shared, estimate a plausible business impact (time saved, cost avoided) clearly labeled as an estimate. </task> <constraints> - Every impact estimate must be labeled "estimate" and show the simple math behind it. - Do not invent a pain the prospect didn't mention. - Keep each row to one sentence per column. </constraints> <format> A table with columns Prospect's Pain (their words), Relevant Capability, Estimated Impact. </format>

You are an enterprise account executive mapping a complex buying committee. <context> This deal has multiple stakeholders and I want a clear map of who influences the decision before I plan my multi-threading strategy. </context> <inputs> - Known stakeholders and titles: [NAME/TITLE LIST] - Deal size and product: [DEAL SIZE, PRODUCT] - Anything known about each person's stance (champion, skeptic, unknown): [STANCE NOTES] </inputs> <task> Build a stakeholder map that classifies each person by likely role (economic buyer, champion, influencer, blocker, end user) and stance, and flag which key roles are missing from my known list based on typical deals of this size. </task> <constraints> - If a likely role (e.g. economic buyer) has no named person, flag it explicitly as "not yet identified", do not invent a name. - Base the "typical roles for this deal size" guidance on realistic B2B buying patterns. - Keep it to one page. </constraints> <format> A table (Name/Title, Likely Role, Stance, Notes) followed by a short "Gaps to Fill" list of missing roles. </format>

You are a senior account executive drafting a client-facing proposal. <context> I need a proposal document for a prospect that reflects what they actually told me, not a boilerplate template. </context> <inputs> - Prospect company and contact: [COMPANY, CONTACT] - Their stated goals and pains from discovery: [GOALS/PAINS] - Scope and pricing tier being proposed: [SCOPE, PRICE] - Implementation timeline: [TIMELINE] </inputs> <task> Write a proposal with an opening summary restating their goals in their language, a scope section tied to those goals, pricing, timeline, and a clear next-step section with a specific signature or call-to-action date. </task> <constraints> - Do not use the word "solution" more than once. - Every scope line must tie back to a stated goal or pain, no generic feature lists. - Keep total length under 600 words. </constraints> <format> A structured proposal document with headed sections: Summary, Scope, Investment, Timeline, Next Steps. </format>

You are an account executive building a business case to help a champion sell internally. <context> My champion needs a one-pager to justify the purchase to their finance team, focused on numbers, not features. </context> <inputs> - Cost of the deal (annual): [PRICE] - Problem being solved and its current cost (time, money, error rate): [CURRENT COST] - Expected improvement from using the product: [EXPECTED IMPROVEMENT, e.g. % time saved] - Company size or team size affected: [SIZE] </inputs> <task> Build a one-page ROI case with a simple before/after cost comparison, a payback period calculation shown step by step, and a one-line bottom line a CFO could repeat in a meeting. </task> <constraints> - Show every calculation explicitly, no unexplained numbers. - Use conservative, believable improvement assumptions, not best-case-only numbers. - Fit on one page. </constraints> <format> A one-pager with sections: Current Cost, Expected Improvement, Payback Calculation, Bottom Line. </format>

You are an account executive presenting pricing options to a prospect. <context> I want to present three pricing tiers in a way that makes the middle option the obvious choice, using our real tiers. </context> <inputs> - Tier names, prices, and included features: [TIER 1, TIER 2, TIER 3 DETAILS] - The prospect's top 2 priorities from discovery: [PRIORITIES] </inputs> <task> Build a Good/Better/Best comparison table that highlights which tier covers the prospect's top 2 priorities, with a one-line recommendation underneath pointing to the tier that best fits, and why. </task> <constraints> - Do not artificially inflate the lowest tier's weaknesses, list its real limitations only. - The recommendation must be justified by the stated priorities, not by which tier is most profitable. - Keep feature rows to the ones that actually differ between tiers. </constraints> <format> A 3-column comparison table plus a one-line recommendation sentence below it. </format>

You are an account executive preparing a one-page executive summary for a deal's economic buyer. <context> The economic buyer has limited time and hasn't been on every call. I need a one-page summary that gets them comfortable enough to approve. </context> <inputs> - Deal name and stage: [DEAL, STAGE] - Problem and business impact as understood so far: [PROBLEM, IMPACT] - Proposed solution and price: [SOLUTION, PRICE] - Champion's name and their internal case for buying: [CHAMPION, INTERNAL CASE] </inputs> <task> Write a one-page executive summary a busy VP could read in 90 seconds, covering the business problem, the proposed fix, the investment, and the expected outcome, written for someone who has not been on the detailed calls. </task> <constraints> - No sales jargon (no "synergy", "leverage", "best-in-class"). - Assume the reader is skeptical and busy, lead with the business problem, not the product. - Under 300 words. </constraints> <format> A one-page memo with a short headline, then four short sections: Problem, Proposed Fix, Investment, Expected Outcome. </format>

You are an account executive tailoring a customer proof point to a specific prospect. <context> I have a case study from a different customer and want to pitch its relevance to a new prospect in a related industry, without overstating the similarity. </context> <inputs> - Existing case study summary (customer, problem, result): [CASE STUDY SUMMARY] - New prospect's industry and situation: [PROSPECT INDUSTRY, SITUATION] </inputs> <task> Write a short talk track connecting the case study's result to the new prospect's likely situation, being explicit about what's directly comparable and what's a reasonable inference. </task> <constraints> - Clearly separate "what happened for them" from "what we'd expect for you", never blur the two. - Under 120 words. - No inflated claims beyond what the case study actually showed. </constraints> <format> A short talk track (3 to 4 sentences) plus one follow-up question to confirm the comparison holds for this prospect. </format>

You are a senior account executive building an objection-handling playbook. <context> I keep hearing the same handful of objections on calls and want sharp, specific responses instead of generic "I understand your concern" scripts. </context> <inputs> - The 5 objections I hear most: [LIST OBJECTIONS, e.g. "too expensive", "need to check with IT"] - My product category and typical deal size: [PRODUCT, DEAL SIZE] </inputs> <task> For each objection, write a short response using acknowledge, reframe, evidence, question, then a natural follow-up question that moves the conversation forward. </task> <constraints> - Each response under 60 words. - Do not dismiss or argue with the objection, reframe it instead. - Every response must end in a question, never a flat statement. </constraints> <format> A table with columns Objection, Response, Follow-Up Question. </format>

You are an account executive preparing to compete against a named competitor in a deal. <context> A prospect mentioned they're also evaluating a competitor and I want sharp, honest talking points, not a takedown that sounds desperate. </context> <inputs> - Competitor name: [COMPETITOR] - What I know about their strengths and weaknesses: [KNOWN FACTS] - My product's genuine differentiators: [DIFFERENTIATORS] </inputs> <task> Build talking points that acknowledge one genuine competitor strength, then pivot to the differentiators that matter most for this prospect's likely priorities, ending with two questions that surface criteria the competitor may struggle with. </task> <constraints> - Never make an unverifiable negative claim about the competitor. - Acknowledge at least one real competitor strength before pivoting. - Keep it to talking points, not a full script. </constraints> <format> A short bulleted battlecard: Competitor Strength to Acknowledge, Our Differentiators (3 bullets), Questions to Ask (2 bullets). </format>

You are a senior account executive preparing for a pricing negotiation call. <context> I have a negotiation call coming up where the prospect is pushing on price and terms. I want a prep brief so I don't improvise concessions on the spot. </context> <inputs> - Deal size and current offer: [DEAL SIZE, OFFER] - What the prospect is pushing on (price, term length, payment terms): [ASKS] - What I'm authorized to concede and my walk-away point: [CONCESSION ROOM, WALK-AWAY] </inputs> <task> Build a negotiation brief listing likely asks, a ranked list of concessions I could trade (cheapest to most costly for us), and at least one non-price lever (timeline, scope, terms) I could offer instead of discounting. </task> <constraints> - Never recommend conceding past the stated walk-away point. - Rank concessions from lowest to highest cost to us. - Include at least one non-price concession option. </constraints> <format> A prep brief with sections: Likely Asks, Ranked Concessions (cheapest first), Non-Price Levers, Walk-Away Line. </format>

You are an account executive coordinating with legal to respond to a procurement redline. <context> Procurement sent back contract redlines and I need to respond to the prospect professionally while looping in the right internal owner. </context> <inputs> - Summary of the redlined clauses: [CLAUSE SUMMARY] - Which ones I can address directly vs. need legal for: [SPLIT] - Prospect contact name: [NAME] </inputs> <task> Write an email to the prospect acknowledging the redlines, addressing the items I can speak to directly, and setting a clear expectation for when legal will respond on the rest. </task> <constraints> - Never commit to a legal position I'm not authorized to make, defer those explicitly to "our legal team". - Give a specific turnaround date, not "soon". - Keep a collaborative, non-defensive tone throughout. </constraints> <format> One email with subject line and body, plus a short internal note to legal summarizing what needs their review. </format>

You are an account executive re-approaching a prospect who said "not now" a while back. <context> A prospect was qualified and interested but the timing wasn't right when they said no. I want to re-approach without sounding like I forgot they already turned me down. </context> <inputs> - Reason they gave for "not now" (budget, timing, other priority): [REASON] - Time elapsed since then: [TIME] - What's changed since (on my side or plausibly on theirs): [CHANGE] </inputs> <task> Write a short win-back email that directly references the original reason they declined, shows what's changed since, and offers a low-friction way to reopen the conversation. </task> <constraints> - Must explicitly reference their original stated reason, not pretend the conversation is starting fresh. - Under 100 words. - Offer a specific low-friction next step (e.g. a 10-minute call), not "let's reconnect sometime". </constraints> <format> One email with subject line and body. </format>

You are a senior account executive building a mutual action plan for an active deal. <context> I want a mutual action plan (MAP) I can share with the prospect that shows both sides' remaining steps to close by a target date. </context> <inputs> - Deal name and target close date: [DEAL, DATE] - Remaining steps on my side (contract, security review, etc.): [MY STEPS] - Remaining steps on their side (budget approval, legal, IT sign-off): [THEIR STEPS] - Key stakeholders involved: [STAKEHOLDERS] </inputs> <task> Build a mutual action plan listing every remaining step in date order, with an owner (my side or theirs) for each, working backward from the target close date. </task> <constraints> - Every step must have exactly one owner, never "both" or "TBD". - Order steps chronologically working backward from the close date. - Flag any step with no realistic room in the timeline. </constraints> <format> A table with columns Date, Step, Owner, Status, ordered chronologically toward the close date. </format>

You are an account executive sending a follow-up right after a sales meeting. <context> I just left a meeting and want a follow-up email out within the hour that reinforces what was agreed and moves the deal forward. </context> <inputs> - Meeting attendees and their roles: [ATTENDEES] - Key points discussed: [KEY POINTS] - Agreed next step and date: [NEXT STEP, DATE] </inputs> <task> Write a follow-up email that recaps the key points in the prospect's language, confirms the agreed next step with a specific date, and lists any open items with named owners. </task> <constraints> - Under 130 words. - No new claims beyond what was discussed in the meeting. - End with one specific date-bound next step, not a vague close. </constraints> <format> One email with subject line and body, plus a short "Open Items" bullet list with owners. </format>

You are a senior account executive doing an honest self-assessment of a deal's risk before a forecast call. <context> I need to write an honest risk assessment of a deal I'm about to commit in my forecast, so my manager isn't surprised later if it slips. </context> <inputs> - Deal name, stage, and forecast category (commit/best case/pipeline): [DEAL, STAGE, CATEGORY] - What's going well: [POSITIVES] - What's uncertain or hasn't happened yet: [UNKNOWNS OR BLOCKERS] </inputs> <task> Write a short risk memo listing the top 3 risks to this deal closing on time, a realistic probability-to-close estimate with reasoning, and one mitigation action for each risk. </task> <constraints> - Do not round the probability estimate to a falsely precise number, give a realistic range and explain it. - Every risk needs one concrete mitigation action, not just a description of the risk. - Be direct about risks even if it means recommending a lower forecast category. </constraints> <format> A memo with sections: Deal Summary, Top 3 Risks (with mitigation for each), Recommended Forecast Category. </format>

You are an account executive updating CRM notes right after a sales call. <context> I have a rough call transcript and need clean CRM notes logged fast instead of writing them from scratch. </context> <inputs> - Deal name and stage: [DEAL, STAGE] - Raw call transcript or notes: [PASTE TRANSCRIPT/NOTES] </inputs> <task> Turn the raw transcript into structured CRM notes covering what was discussed, any new stakeholder or budget information revealed, objections raised, and the agreed next step. </task> <constraints> - Only include facts actually present in the transcript, do not infer numbers or names not mentioned. - Keep it scannable for a manager skimming it in under 30 seconds. - Flag explicitly if no next step was agreed. </constraints> <format> CRM-ready notes with labeled fields: Summary, New Information, Objections Raised, Next Step, Next Step Date. </format>

You are an account executive multi-threading into a new stakeholder on an active deal. <context> A new person has entered the buying process on a deal I'm running and I want to bring them in without going around my existing champion. </context> <inputs> - New stakeholder's name and role: [NAME, ROLE] - My champion's name: [CHAMPION] - What the new stakeholder likely cares about given their role: [LIKELY PRIORITY] - Where the deal currently stands: [DEAL STATUS] </inputs> <task> Write a short introductory email to the new stakeholder that references the champion by name (so it reads as a warm intro, not a cold add), speaks to their likely priority, and proposes a brief call. </task> <constraints> - Must reference the champion by name to preserve the relationship, never bypass them silently. - Under 100 words. - Tie the ask directly to the new stakeholder's likely priority, not a generic "loop you in" message. </constraints> <format> One email with subject line and body, plus a one-line heads-up message I should send my champion first. </format>

You are an account executive preparing a quarterly business review for a key customer. <context> I have a QBR coming up with an existing customer and need a deck outline that shows value delivered and opens the door to expansion, not just a status update. </context> <inputs> - Customer name and product usage since last QBR: [CUSTOMER, USAGE DATA] - Results or outcomes achieved: [RESULTS] - Areas of the product they're not using yet: [UNUSED AREAS] - Known goals for their next quarter or year: [THEIR GOALS] </inputs> <task> Outline a QBR deck with a results recap slide, a usage-versus-potential slide, a roadmap-alignment slide tied to their stated goals, and a closing slide with a specific expansion or renewal ask. </task> <constraints> - Every results claim must be tied to an actual number or usage fact from the inputs. - The expansion ask must connect to an unused area they'd plausibly benefit from, not a random upsell. - Keep it to 5 slides maximum, one line of speaker notes each. </constraints> <format> A slide-by-slide outline (slide title, 2 to 3 bullet points, one line of speaker notes) for 5 slides. </format>

You are an account executive pitching an expansion to an existing customer. <context> An existing customer is a good fit for a higher tier or add-on, and I want to pitch it in a way that's clearly additive, not a hard resell. </context> <inputs> - Current plan and usage pattern: [CURRENT PLAN, USAGE] - Add-on or higher tier being pitched: [UPGRADE OPTION] - Specific trigger suggesting they need it (usage limit hit, team growth, new use case): [TRIGGER] </inputs> <task> Write a short pitch (email or talking points) that leads with the trigger, connects it to the upgrade's specific benefit, and quantifies the cost of staying on the current plan if the trigger is a limit or bottleneck. </task> <constraints> - Lead with their situation (the trigger), not with the product upgrade itself. - Quantify the cost of inaction if the trigger involves a limit, delay, or workaround. - Under 130 words. </constraints> <format> One short email with subject line and body. </format>

You are an account executive addressing a customer whose renewal is at risk. <context> A customer's usage has dropped and their renewal is coming up. I want to reach out proactively before they decide not to renew. </context> <inputs> - Customer name and renewal date: [CUSTOMER, DATE] - Sign of risk (usage drop, champion left, support tickets, no response): [RISK SIGNAL] - Original goals they had when they signed: [ORIGINAL GOALS] </inputs> <task> Write a direct, non-defensive email that names the risk signal honestly, reconnects to their original goals, and offers a specific working session to get back on track before the renewal date. </task> <constraints> - Do not use guilt or pressure language about the renewal deadline. - Name the risk signal directly rather than talking around it. - Offer one specific, scheduled next step, not an open-ended "let's talk". </constraints> <format> One email with subject line and body, plus an internal note flagging this account to my manager with the risk signal and renewal date. </format>

You are an account executive asking a satisfied customer to participate in a case study. <context> A customer has gotten strong results and I want to ask them to be featured in a case study without it feeling like extra work for them. </context> <inputs> - Customer name and the result they achieved: [CUSTOMER, RESULT] - Format being requested (short quote, written case study, video call): [FORMAT] - Any incentive being offered (discount, gift, early access): [INCENTIVE, IF ANY] </inputs> <task> Write a request email that's specific about the time commitment involved, references their actual result, and makes clear how little effort is required on their end. </task> <constraints> - State the time commitment explicitly (e.g. "15 minutes"), never leave it vague. - Reference their specific result, not a generic "you've had great success" line. - Under 100 words. </constraints> <format> One email with subject line and body. </format>

You are an account executive building an annual account plan for a strategic customer. <context> I own a strategic account and want a one-page annual plan to guide my touchpoints and growth targets for the year, not just react deal by deal. </context> <inputs> - Account name, current contract value, and renewal date: [ACCOUNT, VALUE, DATE] - Known goals or initiatives for their company this year: [THEIR INITIATIVES] - Whitespace (products/tiers they don't have yet): [WHITESPACE] - Key relationships and their strength (strong/developing/none): [RELATIONSHIPS] </inputs> <task> Build a one-page annual plan with a growth target for the year, the top 2 whitespace opportunities tied to their initiatives, a relationship-building plan for weak or missing contacts, and a quarterly touchpoint cadence. </task> <constraints> - Growth target must be justified by a specific whitespace opportunity, not a round percentage picked at random. - Flag any weak or missing key relationship as a named risk to the plan. - Fit on one page. </constraints> <format> A one-page plan with sections: Growth Target & Rationale, Top Whitespace Opportunities, Relationship Plan, Quarterly Touchpoint Cadence. </format>