By PromptLeadz · Reading time 25 minutes · 100 AI sales prompts across 5 categories · Calibrated for 2026 frontier models

What separates the AE from the AE-influencer

B2B sales is one of the most LinkedIn-saturated disciplines in business. Threads about being a trusted advisor, the magic of customer obsession, value-selling, the buyer's journey, win-win negotiations, and the art of the close get tens of thousands of likes. The threads describe a vibe. The actual AE job is deal work, memo work, and disciplined buyer-respect.

An AE's primary job is producing decision-grade artifacts: cold emails buyers actually open, discovery calls that surface real pain, demos calibrated to specific buying centers, multi-stakeholder maps with named decision-makers, recap memos with specific next steps and dates, proposals that protect price integrity, MAPs that survive procurement, and post-sale handoffs that produce references and renewals. None of these artifacts look exciting on a screenshot. All of them compound across the quarter.

Six dimensions separate the AE voice from the AE-influencer voice. Substance: the AE names the specific buyer, the specific pain, the specific dollar value at stake; the influencer names the disposition (trusted advisor, value-led, buyer-first). Tradeoffs: the AE names what the buyer gives up by buying and what we give up by discounting; the influencer says "win-win" instead of "or". Numbers: the AE opens with ACV, close date, and decision criteria; the influencer opens with the relationship-building story. Ownership: the AE names the named stakeholder and the date; the influencer names the team. Tone: the AE writes short emails that respect the buyer's time; the influencer writes long emails that perform thoroughness. Audience: the AE writes for the buyer, the manager, the deal team, and Friday forecast; the influencer writes for the LinkedIn algorithm.

Both voices exist in the wild. Only one closes the quarter. This pack of 100 AI sales prompts is calibrated for the first; it explicitly rejects the second at the prompt level by banning the genre's signature phrases inline. Output reads like a memo from an AE who has just closed three deals this month, not a thread from a personal-brand AE who has not.

Five categories. The AE deal cycle end to end.

The five categories map to the five stages of a real deal: prospecting through reference. Most AE training over-indexes on the middle (discovery and demo) and under-indexes on the ends (cold email craft and post-sale referral motion). The pack rebalances by giving twenty prompts to each stage. Prospecting and Outbound comes first because pipeline is built or starved at the top of the funnel. Discovery and Qualification comes second because under-qualified deals burn the rest of the quarter. Demo and Presentation comes third because the demo is where the technical and economic buyer separate. Negotiation and Closing comes fourth because the negotiation is where price integrity and deal economics get decided. Post-Sale Handoff and Expansion comes fifth because retention, expansion, and referrals are the second compounding engine after new logo.

1. Cold email with named buyer signal

Target buyer: [paste name, role, company, segment]. Named signal: [paste recent post, job change, funding event, product launch, hiring pattern, technology adoption]. Our differentiation: [paste]. Draft a 70-word cold email: subject under 7 words referencing the signal, body that opens with the signal in the first sentence (no preamble), one line on what we shipped that maps to the signal, one binary CTA. Cold emails opening with "I hope this finds you well" produce no response.

2. Account research brief

Target account: [paste name, segment, ARR estimate]. Available sources: [paste website, news, LinkedIn, 10-K if public, podcast appearances]. Draft a 400-word account research brief: the strategic priorities named (with sources), the named buying centers with current owners, the recent triggers (hiring, funding, tech changes), the named competitors in the stack, the angle for outbound. Account research briefs that just list facts produce no outbound angle.

3. Trigger event response

Trigger event: [paste, e.g. funding, leadership change, new product, layoff, M&A]. Target buyer: [paste]. Draft a 60-word trigger-response email: the named event in the first sentence, the specific implication for them, our relevance with one proof point, the binary CTA. Trigger-response emails sent days late or with generic congratulations produce no response.

4. LinkedIn message sequence

Target buyer: [paste name, role, recent activity]. Connection status: [paste]. Draft a 3-message LinkedIn sequence: connect note under 200 characters with named signal, first DM after acceptance referencing their content not a pitch, second DM 5-7 days later with a specific resource and a binary ask. LinkedIn sequences that pitch immediately after connect produce blocks.

5. Multi-touch outbound sequence

Target buyer persona: [paste]. Available channels: [paste email, LinkedIn, phone, video]. Draft a 600-word 14-day sequence: 7-8 touches mixed across channels, each touch with a different angle (case study, peer reference, industry data, named trigger, ROI), the suppression rule (any reply), the final breakup email that respects buyer dignity. Sequences with the same email reformatted across touches produce unsubscribes.

6. Cold email follow-up

Original email: [paste]. Days since: [paste]. New information available: [paste optional]. Draft a 40-word follow-up: no "just checking in" preamble, a specific new piece of information or angle, a binary CTA. Follow-ups that read "following up on my note below" produce no response.

7. Voicemail and ringless script

Target buyer: [paste]. Named angle: [paste]. Draft a 25-second voicemail script: open with full name and company in 5 seconds, the named signal in 10 seconds, the binary CTA with a specific time window in 10 seconds. Voicemails that introduce the product before the signal produce delete-without-listening.

8. Personalized video pitch script

Target buyer: [paste]. Named research: [paste 3 specific facts]. Draft a 90-second video script: open with the buyer's name on screen plus a named signal, the specific relevance in 30 seconds, a 30-second proof point or customer outcome, the binary CTA. Video pitches without named research produce auto-delete patterns.

9. Referral request email

Mutual contact: [paste]. Target buyer: [paste]. Context of mutual relationship: [paste]. Draft a 80-word referral request: the named context with the mutual, the specific ask (intro, double opt-in, name-drop), the buyer-side benefit, the binary CTA. Referral requests that ask the mutual to vouch without specific context fail.

10. Re-engagement after no-response

Prior outreach: [paste]. New triggering event: [paste, e.g. their funding, our product update, named customer win]. Draft a 60-word re-engagement email: the named new context in the first sentence, the specific relevance, the binary CTA. Re-engagement emails that say "following up since I never heard back" produce no response.

11. Conference outreach pre-event

Conference: [paste]. Target buyers attending: [paste]. Our presence: [paste sponsor, speaker, attendee]. Draft a 70-word pre-event email: the named conference and the specific reason to meet there, the proposed 20-minute time window, the named topic worth their time, the binary CTA. Pre-event outreach asking for "30 minutes to connect" without a specific topic produces no meetings.

12. Conference follow-up post-event

Conference: [paste]. Buyer encountered: [paste, what we discussed]. Draft a 80-word post-event email: the named conversation reference in the first sentence, the specific commitment (resource, intro, next step) made or proposed, the named timeframe, the binary CTA. Post-event follow-ups that fail to reference the specific conversation produce "sorry, who is this" replies.

13. Persona-specific opener for CFO

Target CFO: [paste name, company, recent earnings or strategic priority]. Our economic value: [paste with dollars]. Draft a 65-word CFO email: open with a specific financial signal from their public posture, the dollar implication of our offering tied to their priority, one customer outcome with a number, the binary CTA. CFO emails opening with product features produce auto-archive.

14. Persona-specific opener for CTO

Target CTO: [paste name, company, technology stack signals]. Our technical fit: [paste]. Draft a 65-word CTO email: open with a specific technical signal (stack, hiring, public talks, engineering blog), the technical implication, one technical proof point or named peer customer, the binary CTA. CTO emails opening with business value produce no response; this version leads with technical credibility.

15. Persona-specific opener for VP Sales

Target VP Sales: [paste name, company, recent hiring pattern, comp model signals]. Our sales-team value: [paste]. Draft a 70-word VP Sales email: open with a specific revenue or team signal, the implication for their pipeline or productivity, one named peer outcome with a percent or dollar, the binary CTA. VP Sales emails opening with generic productivity claims produce no response.

16. Persona-specific opener for PM

Target PM: [paste name, product, recent launches or signals]. Our PM value: [paste]. Draft a 65-word PM email: open with a named product or roadmap signal, the implication for their product or velocity, one named peer customer outcome, the binary CTA. PM emails opening with sales-team benefits produce no response.

17. Persona-specific opener for Marketing

Target Marketing leader: [paste name, company, recent campaigns or content]. Our marketing-team value: [paste]. Draft a 65-word Marketing email: open with a named campaign or content signal, the implication for their pipeline or brand, one named peer outcome with a metric, the binary CTA. Marketing emails opening with feature lists produce auto-archive.

18. Account-based campaign assist

Target account: [paste]. Buying center: [paste named roles]. Marketing's ABM activity: [paste recent paid, content, events]. Draft a 500-word AE-side ABM assist plan: the named outbound touches per role aligned to marketing touches, the timing offset from marketing activity, the named angle per role, the success metric (meetings booked, opportunity created). AE-side ABM that ignores marketing activity produces redundant outreach.

19. Lost-deal reopening

Lost deal: [paste account, original close date, reason for loss]. New context: [paste, e.g. competitor pricing change, leadership change, our product update, their public signal]. Draft a 90-word reopen email: the named new context, the specific reason to revisit, the buyer-side benefit, the binary CTA. Lost-deal reopens that ignore the original loss reason fail.

20. Inbound lead 5-minute response

Inbound signal: [paste form, content download, demo request, with available context]. Draft a 60-word 5-minute response email: the acknowledgment of the specific action they took, two qualifying questions, three proposed times in the next 48 hours, the calendar link. Inbound responses that take longer than 5 minutes lose 80 percent of the conversion advantage.

21. Discovery call agenda

Account: [paste, segment, signals]. Buyer attendees: [paste names, roles]. Time: [paste, e.g. 30 minutes]. Draft a 300-word discovery agenda: opening (rapport plus mutual purpose, 3 minutes), current state probes (12 minutes), desired state probes (8 minutes), priorities and timeline probes (5 minutes), next steps and commitments (2 minutes). Discovery agendas that lead with the demo skip the discovery.

22. Discovery question bank

Buyer persona: [paste]. Product domain: [paste]. Draft a 600-word discovery question bank: ten questions on current state (specific not generic), ten on pain (with consequences), five on stakeholders and decision-making, five on timeline and budget, five on competitive landscape, five on success criteria. Discovery question banks built around our product features rather than buyer state produce shallow calls.

23. MEDDPICC qualification memo

Deal: [paste account, ACV estimate, stage]. Available information: [paste from discovery and research]. Draft a 500-word MEDDPICC memo: Metrics (named buyer-side metrics affected), Economic buyer (named with confirmation evidence), Decision criteria (in buyer language), Decision process (steps and timing), Identify pain (with consequences), Champion (named with verification), Competition (named with positioning). MEDDPICC memos with vague entries produce stalled deals.

24. Pain identification probe

Surface-level pain mentioned: [paste]. Buyer context: [paste]. Draft a 5-question probe sequence: the consequence question ("what does that cost you when it happens"), the frequency question, the workaround question, the stakeholder question ("who else feels this"), the prior-attempt question. Pain probes that stop at the surface symptom miss the root cause.

25. Champion building plan

Candidate champion: [paste name, role, motivation]. Current relationship strength: [paste]. Draft a 400-word champion plan: the named motivations of the candidate (career, peer recognition, internal influence), the resources we will provide to make them successful internally, the named introductions we will request, the named information we will share confidentially, the testing moments to validate they are a real champion. Champions never tested produce surprises at procurement.

26. Multi-stakeholder map

Account: [paste]. Known stakeholders: [paste names, roles, dispositions]. Buying process: [paste]. Draft a 500-word stakeholder map: each named stakeholder with role, decision authority (decider, influencer, blocker, user), our coverage level, the disposition (champion, supporter, neutral, skeptic, blocker), the named gaps, the engagement plan per gap. Single-threaded deals lose 70 percent of the time.

27. Buying process diagnosis

Buyer-stated process: [paste]. Available evidence on actual process: [paste]. Draft a 400-word buying process memo: the named steps from initial interest to signed contract, the typical duration per step, the named owners per step, the procurement and legal requirements, the gates we have not yet cleared, the named risks. Deals run without a buying process diagnosis stall at procurement.

28. Budget discovery memo

Buyer-shared budget signal: [paste]. Context: [paste recent funding, fiscal year, prior spend on category]. Draft a 300-word budget memo: the named budget owner (often different from the user), the budget category and fiscal year alignment, the prior spend on the category (or reasoning), the named approval thresholds, the realistic range our ACV must hit. Deals without budget discovery produce surprises at close.

29. Authority discovery probe

Stated decision-maker: [paste]. Available signals on actual authority: [paste]. Draft a 4-question probe to verify authority: the prior-purchase question ("the last time you bought a similar tool, who signed off"), the threshold question ("at what ACV does your CFO get involved"), the procurement question ("does this trigger formal procurement"), the board or executive question. Authority probes that take "yes I can decide" at face value produce stalled deals at sign.

30. Timeline pressure-test

Buyer-stated timeline: [paste]. Available signals: [paste fiscal year, named project, public commitment]. Draft a 300-word timeline pressure-test memo: the named drivers of urgency (named project, fiscal deadline, regulatory date, public commitment), the realistic vs aspirational timeline, the named risks to slippage, the action we take to maintain pace. Timelines stated as "as soon as possible" without named drivers are fictional.

31. Compelling event discovery

Account: [paste]. Available context: [paste]. Draft a 4-question probe sequence to surface a compelling event: the consequence question ("what happens if this is not solved by X date"), the named-event question (board meeting, audit, launch, contract renewal), the cost-of-inaction question, the alternative-to-solving question. Deals without a compelling event slip quarters.

32. Decision criteria documentation

Buyer-stated criteria: [paste]. Our actual differentiation: [paste]. Draft a 400-word criteria memo: each named criterion in buyer's words, the weight or importance assigned by the buyer, our position on each, the criteria where we lead and the criteria where we trail, the named negotiating room. Decision criteria not documented in buyer's exact words produce mid-cycle scope changes.

33. Competitive evaluation memo

Competitors in scope: [paste]. Buyer-shared evaluation signals: [paste]. Draft a 500-word competitive memo: each named competitor with their stated positioning, their likely angle in this account, our counter-position with proof points, the trap-set questions for discovery, the named references for this segment. Competitive memos that just list features miss positioning leverage.

34. Tech stack discovery

Known stack: [paste from research, hiring posts, conference talks]. Integration relevance: [paste]. Draft a 300-word stack memo: the named tools they use that affect our deployment, the integration requirements, the named technical stakeholders, the security and compliance constraints, the implementation timeline implication. Tech stack discovery skipped surfaces blockers at security review.

35. Discovery call notes synthesis

Raw notes: [paste]. Account: [paste]. Draft a 500-word synthesis memo: the named pain points with consequences, the named stakeholders surfaced with disposition, the named decision criteria, the named timeline and compelling event, the open questions for next discovery, the named risks. Discovery notes that capture quotes without synthesis produce no deal review value.

36. Discovery objection handling

Objection raised: [paste, e.g. "we are already using X", "not a priority right now", "budget is locked"]. Buyer context: [paste]. Draft a 4-step response framework: acknowledge the specific concern, probe to validate it is real (not a brush-off), reframe with a named comparison, propose a small next step. Objections accepted at face value produce dead deals.

37. Second-discovery agenda

First discovery: [paste named gaps and unanswered questions]. New stakeholder joining: [paste optional]. Draft a 300-word second-discovery agenda: the named gaps to close, the new stakeholder role and engagement plan, the proof points to share, the next-step proposal. Second discovery calls that re-run the first agenda produce buyer fatigue.

38. Champion-to-economic-buyer transition

Champion: [paste]. Economic buyer: [paste named role and signals]. Draft a 400-word transition memo: the champion-side internal sell content, the named introduction strategy, the meeting agenda for the EB call, the executive-grade message (different from the user-grade message), the buyer-side benefits relevant at the EB altitude. EB meetings entered without champion-side internal sell prep produce "I need to think about it" responses.

39. Lost discovery diagnosis

Discovery that did not produce a qualified opportunity: [paste]. Buyer signals: [paste]. Draft a 400-word loss memo: the honest read on why discovery did not qualify (not a fit, no pain, no budget, no timeline, no stakeholder access), the named lessons for similar accounts, the recommended disposition (recycle, archive, refer to marketing nurture), the named owner. Discovery losses ignored produce repeated patterns; this prompt forces the diagnosis.

40. Discovery-stage forecast call

Discovery-stage deal: [paste account, ACV estimate, stage]. Honest read: [paste]. Draft a 300-word forecast position: the named risks remaining (qualification, stakeholder, timeline, competitive, budget), the realistic close probability, the named actions in the next two weeks to advance, the kill criterion. Discovery deals forecast as commit without qualification produce missed quarters.

Most AE advice circulating on LinkedIn is content marketing for personal brands. The work that actually closes deals is the work that does not screenshot well.PromptLeadz AI Sales Prompts Pack

41. Demo prep memo

Account: [paste, ACV estimate]. Buyer attendees: [paste names, roles]. Discovered pain: [paste]. Decision criteria: [paste]. Draft a 500-word demo prep memo: the named buyer-side pain to demonstrate against, the demo storyline (problem to outcome in 3 acts), the specific features to show and the ones to skip, the named risks and prepared responses, the next-step proposal calibrated to the audience. Demos run without prep memos default to feature tours.

42. Custom demo script

Discovered pain: [paste]. Buyer workflow: [paste]. Draft a 600-word demo script: the opening that acknowledges the named pain (no product preamble), the demo flow mapped to their workflow (not our product menu), the named outcome shown with their data or similar, the planned questions to the audience, the close that proposes a specific next step. Demos that open with product history lose the room in 5 minutes.

43. Multi-stakeholder demo plan

Demo audience: [paste mixed roles, e.g. user, manager, IT, finance]. Time: [paste]. Draft a 500-word demo plan: the storyline that lands for the highest-altitude buyer in the room, the named deep-dive segments by stakeholder, the trap-set questions that surface buying signals, the named follow-up commitments per stakeholder. Mixed-audience demos that try to address every role equally land for none of them.

44. Technical demo brief

Technical audience: [paste roles, stack]. Discovered technical requirements: [paste]. Draft a 500-word technical demo brief: the architecture and integration story, the named technical proof points (performance, scalability, security, API), the demo environment and data, the technical Q&A prep with named hard questions, the named technical references available. Technical demos that lead with business value lose technical credibility.

45. Executive demo deck

Executive audience: [paste roles]. Discovered priorities: [paste]. Draft a 10-slide executive deck outline: slide 1 named context (their priority not our intro), slide 2 the named problem in their language, slide 3 the named outcome with proof, slides 4-7 the proof points by priority, slide 8 named peer customers with outcomes, slide 9 the named investment and ROI, slide 10 the proposed next step. Executive decks that lead with company overview waste the room.

46. Sandbox or trial setup guide

Buyer technical context: [paste]. Sandbox availability: [paste]. Draft a 400-word setup guide: the named time-to-first-value in the sandbox, the prepopulated data or use case, the named user accounts and permissions, the support contact and response SLA, the success metric for the sandbox phase. Sandboxes shipped without time-to-value guidance produce abandoned trials.

47. Demo follow-up email

Demo: [paste audience, key moments, named pain addressed]. Draft a 150-word follow-up email: the named demo moments that resonated (with specific buyer reactions), the resources to share (named case study or technical doc), the specific next step with named owner and date, the binary CTA. Demo follow-ups that recap the entire demo waste buyer attention.

48. Q&A preparation memo

Anticipated hard questions: [paste based on discovery and competitive context]. Draft a 500-word Q&A prep memo: 10 named likely questions, the calibrated answer per question (no spin, no defensiveness), the named proof point per answer, the questions we cannot answer and the named escalation path. Demos without hard-question prep produce panic moments that cost trust.

49. Demo objection handling

Objection raised in demo: [paste]. Buyer context: [paste]. Draft a 4-step response: validate the specific concern with a probe, name the underlying trade-off honestly, share a peer-customer outcome on the same concern, propose a specific next step. Demo objections deflected with marketing language produce loss memos that cite "vendor over-promised".

50. Demo recap memo for buyers

Demo: [paste named participants, key moments, commitments]. Draft a 250-word recap memo that the buyer can forward internally: the named problem demonstrated against, the specific outcome shown, the technical and economic considerations, the proposed next step with the timeline, the named contacts on our side. Recap memos that the buyer cannot forward to their executive produce stalled internal selling.

51. Internal demo readout

Demo: [paste]. Deal team: [paste named manager, SE, leadership]. Draft a 300-word internal readout: the named participants and their disposition shift, the named risks surfaced, the named commitments made, the deal stage update, the named asks of the deal team. Internal readouts skipped produce sales managers learning bad news at forecast.

52. Demo-to-trial conversion plan

Demo outcome: [paste]. Trial structure available: [paste]. Draft a 400-word conversion plan: the named trial scope and time bound, the named success criteria the buyer signs up for, the named champion responsibilities, the technical and onboarding support, the named decision-meeting after trial. Trials launched without named success criteria produce "we never really tested it properly" non-decisions.

53. Buyer-side internal sell memo

Champion: [paste]. Audience champion will sell to: [paste named roles]. Draft a 500-word internal sell memo for the champion to use: the named business problem in their language, the named proposed solution with our role, the named expected outcomes with proof points, the named investment with ROI calculation, the named risks and mitigations, the recommended decision. Champions sent into internal meetings without prep produce vague pitches that fail.

54. Technical evaluation plan

Technical evaluator: [paste roles]. Evaluation criteria: [paste]. Draft a 500-word technical eval plan: the named criteria and the test per criterion, the timeline phased over 2-4 weeks, the named owners on both sides, the named go/no-go gates, the documented results template. Technical evaluations without documented results produce "the team did not have time to fully evaluate" non-decisions.

55. Reference call coordination

Buyer requesting reference: [paste their named concerns]. Available reference customers: [paste 2-3 candidates with fit]. Draft a 400-word reference coordination memo: the best-fit reference with rationale, the named questions to prep the reference for, the named concerns the buyer will surface, the logistics and timing, the post-call follow-up plan. References sent without prep produce off-message calls.

56. Security review prep

Buyer security team: [paste roles]. Available security documentation: [paste SOC 2, ISO, pen test, DPA]. Draft a 500-word security prep memo: the named security artifacts shared in order, the named hard questions anticipated, the named technical contacts on our side, the named contractual security commitments, the timeline. Security reviews entered without prep extend deals by 30 to 60 days.

57. Proof of concept brief

Buyer POC request: [paste]. Our POC framework: [paste]. Draft a 600-word POC brief: the named POC scope (specific use case, specific data, specific user count), the named success criteria the buyer signs in writing, the timeline (2-6 weeks typical), the named owners both sides, the support model, the named decision meeting at end. POCs without signed success criteria become endless evaluation projects.

58. POC success criteria document

POC scope: [paste]. Buyer-stated objectives: [paste]. Draft a 400-word success criteria document: 5-7 named criteria with measurable thresholds, the named test or evidence per criterion, the named decision-meeting and decision-makers, the consequence of each outcome (pass leads to purchase, fail leads to specified action). Success criteria left vague produce POCs that drift into perpetual evaluation.

59. POC-to-purchase transition memo

POC results: [paste evidence against criteria]. Buyer disposition: [paste]. Draft a 400-word transition memo: the named criteria met with evidence, the named gaps and proposed resolutions, the buyer-side internal sell content for procurement, the proposed contract terms, the named decision-meeting and timeline. POCs ending without a transition memo stall in negotiation.

60. Lost demo post-mortem

Demo that lost the deal or stalled the process: [paste]. Buyer feedback: [paste]. Draft a 400-word post-mortem: the named demo moments that lost the room, the gap between buyer expectation and demo reality, the named lessons for the next similar demo, the recommended deal disposition. Demo losses without post-mortems produce repeated patterns.

61. Proposal and MSA draft

Deal: [paste account, ACV, scope, decision criteria]. Standard terms: [paste]. Draft a 700-word proposal: the named scope with specific deliverables, the named commercial terms (pricing, payment, term length), the named performance commitments, the named legal and security commitments, the named implementation plan, the named success criteria. Proposals without named performance commitments produce procurement asking for them later.

62. Pricing pushback handling

Buyer pushback: [paste, e.g. "too expensive", "competitor is cheaper", "need a discount"]. Buyer context: [paste budget signals, decision criteria]. Draft a 500-word pushback memo: the named cost-of-leaving (switching cost, value loss, internal disruption with dollars), the named value delivered priced honestly (cost per outcome not per seat), the named negotiation positions (hold, partial concession, restructure with terms), the recommended position with rationale. Pricing pushback handled by immediate discount destroys price integrity across the team.

63. Discount strategy memo

Deal: [paste ACV, stage, competitive context]. Discount under consideration: [paste percent and rationale]. Draft a 400-word discount memo: the named justification (competitive, multi-year, payment terms, named services, reference commitment), the named buyer concession in return, the named precedent risk for similar accounts, the recommended approval level. Discounts granted without named buyer concession produce a worse next negotiation.

64. Procurement engagement plan

Buyer procurement contact: [paste named role, prior experience]. Stated procurement asks: [paste]. Draft a 500-word procurement engagement plan: the named asks classified (price, terms, performance, alternatives evaluation), the named counter for each, the named escalation back to the business sponsor when procurement positions diverge from sponsor reality, the timeline and named contractual touchpoints. Procurement engaged late in the deal produces 30-60 day extensions.

65. Contract redline response

Buyer redlines received: [paste named clauses, requested changes]. Our position: [paste]. Draft a 600-word redline response: clause-by-clause acceptance, counter, or rejection with named rationale, the named alternative language we will accept, the named escalation path on disputed clauses, the named legal contact on our side. Redlines responded to without legal counsel acceptance produce delayed sign.

66. Multi-year deal structure

Buyer interest in multi-year: [paste]. Pricing options: [paste]. Customer financial cycle: [paste]. Draft a 600-word multi-year proposal: the named multi-year ROI compared to annual, the named buyer benefits (lock-in, predictability, dedicated resources), the named discount logic tied to commitment, the buyer-side internal sell, the named contract terms that protect both sides. Multi-year deals without explicit lock-in pricing terms produce repricing fights at year 2.

67. Payment terms negotiation

Buyer-stated payment ask: [paste, e.g. net 90, milestone, quarterly]. Our standard: [paste]. Draft a 400-word payment terms memo: the named impact of buyer-favorable terms (cash flow, finance team approval needed), the named alternative structures (partial upfront, milestone, quarterly with named discount), the recommended position. Payment terms agreed without finance approval produce stuck signed contracts.

68. Legal review acceleration

Legal stalling point: [paste named clauses]. Buyer legal contact: [paste]. Draft a 400-word acceleration memo: the named clauses causing delay, the named alternative language already approved in similar deals, the named escalation path on both sides, the named timeline and the consequence of slip. Legal accelerations without named alternative language produce repeated round-trips.

69. Holdback or pilot structuring

Buyer hesitation: [paste, e.g. risk, uncertainty, internal politics]. Available pilot structure: [paste]. Draft a 500-word holdback memo: the named pilot scope and time-bound, the named success criteria the buyer signs to, the named transition trigger to full deployment, the commercial structure (lower fee for pilot phase, holdback against success, named services investment). Pilots without named transition triggers become permanent pilots.

70. Stalled-deal forensic memo

Stalled deal: [paste account, stage, days stalled, last activity]. Available signals: [paste]. Draft a 500-word forensic memo: the named likely cause (champion turnover, priority shift, competitive evaluation, budget freeze, no compelling event), the named test per hypothesis, the recommended action (re-engage, escalate, push to next quarter, archive), the kill criterion. Stalled deals carried in forecast produce missed quarters; this prompt forces honest disposition.

71. Competitive close memo

Competitor in final selection: [paste]. Buyer evaluation criteria: [paste]. Our position: [paste]. Draft a 600-word competitive close memo: the named criteria honestly assessed for both vendors, the named differentiator emphasis for our position, the named trap-set questions for the buyer to ask the competitor, the named references for the segment, the named offer structure if needed. Competitive close moments without prepared trap-set questions produce buyer indecision favoring the incumbent.

72. Deal-team escalation memo

Deal at risk: [paste]. Named asks: [paste internal needs, e.g. exec sponsor call, custom commitment, services investment]. Draft a 400-word escalation memo: the named deal value at risk, the named issue, the named asks of the deal team or leadership, the named timeline of the close window, the named consequence of no escalation. Deal-team escalations made too late produce "we could have saved that" post-mortems.

73. Buyer silence response

Days since last buyer response: [paste]. Last known disposition: [paste]. Available new signals: [paste optional]. Draft a 70-word breakup-style email: the acknowledgment that priorities have shifted, the named specific question to confirm, the named alternative if not interested (referral, deferred timeline, named different solution). Silence-response emails that beg for replies produce no response; this version offers dignity exits.

74. End-of-quarter close plan

Deal: [paste ACV, stage, named gaps to close]. Days remaining: [paste]. Draft a 400-word close plan: the named gates remaining (champion sign-off, legal, procurement, exec sponsor, signature), the named owners and dates per gate, the daily standup discipline, the named contingency if any gate slips, the named close-of-business commitment. EOQ deals run without daily ownership produce slips into next quarter.

75. Negotiation prep with Voss-style frames

Upcoming negotiation: [paste named topics, buyer counterparts]. Our positions: [paste]. Draft a 500-word negotiation prep memo: the named labels for buyer-side emotions to surface ("it seems like price flexibility is important to your team"), the named calibrated questions for each topic, the named mirroring opportunities, the named accusations audit (everything they could say about us), the named BATNA. Negotiations entered without labels and accusation audits produce defensive reactions.

76. Implementation services scoping

Buyer implementation needs: [paste]. Our services menu: [paste]. Draft a 500-word services scoping memo: the named scope (in scope and out of scope), the named pricing, the named timeline phased in milestones, the named buyer-side prerequisites, the named acceptance criteria per milestone. Services scoped vaguely produce "that was supposed to be included" disputes.

77. Order form details

Deal terms agreed: [paste]. Standard order form: [paste]. Draft a 400-word order form memo: the named line items with quantities and pricing, the named billing details, the named term length and renewal terms, the named addendums or attachments referenced, the named signers on both sides, the named effective date. Order forms with vague line items produce billing disputes.

78. Internal close-or-kill memo

Deal facing close-or-kill decision: [paste]. Honest read: [paste]. Draft a 400-word internal memo: the named state of the deal (committed signals vs unresolved gaps), the named realistic probability of close in named window, the named decision (push to close, defer to next quarter with named action, archive), the named owner and date. Close-or-kill decisions deferred produce dead deals carried in forecast.

79. Won-deal kickoff email

Deal won: [paste named buyer team, ACV, scope, start date]. Draft a 200-word kickoff email: the named congratulations to the buyer team, the named transition to customer success or implementation, the named introduction to the new contacts, the named first milestones and dates, the named contact for any pre-kickoff questions. Kickoff emails sent late produce "the sales team disappeared after signing" comments.

80. Lost-deal post-mortem

Lost deal: [paste account, ACV, named loss reason cited by buyer]. Internal context: [paste]. Draft a 500-word post-mortem: the named honest loss reason (often different from buyer-cited), the named decisions that contributed (qualification, stakeholder coverage, competitive positioning, pricing, timing), the named lessons for similar accounts, the named pattern to share with the team, the recommended deal disposition (recycle in 6 months, archive permanently). Lost deals without honest post-mortems produce repeated patterns.

81. Customer success handoff memo

Deal won: [paste account, ACV, named buyer team, deal context]. CSM assigned: [paste]. Draft a 500-word handoff memo: the named buyer-side priorities and success criteria, the named stakeholders with disposition, the named commitments made during sales, the named risks and watch items, the named touchpoints sales will maintain, the first 30-60-90 named milestones. Handoff memos that skip sales commitments produce CSM-side surprises at 60 days.

82. Implementation kickoff plan

Customer: [paste]. Implementation scope: [paste]. Draft a 400-word kickoff plan: the named goals named in customer business terms (not feature adoption), the named primary stakeholder and economic buyer, the timeline with named measurable milestones, the named risks the customer should know, the named action commitments out of the meeting. Kickoffs that close on "excited to partner" produce no shared definition of success.

83. 30-day check-in agenda

Customer: [paste account, deployment status]. Stated milestones: [paste]. Draft a 300-word check-in agenda: the named status against the 30-day milestone, the named issues surfaced, the named decisions or commitments needed, the named next steps to the 60-day milestone. 30-day check-ins that drift into "how is it going" miss the calibration moment.

84. Quarterly account review prep

Account: [paste ACV, tenure, current health]. Period: [paste]. Draft a 500-word QBR prep memo: the named outcome metrics tied to buying case, the named expansion or risk signals, the named stakeholder engagement state, the named asks of the customer for next quarter, the named asks of us. AE-side QBR prep without named outcome metrics produces feature-tour QBRs.

85. Expansion opportunity scan

Account: [paste, current product footprint, organizational map]. Adjacent products or use cases: [paste]. Draft a 500-word expansion scan: the named departments or teams not yet served, the named use cases adjacent to current usage, the named stakeholders to engage, the named buying triggers required, the timeline to qualified opportunity. Expansion scans built on our quarter rather than customer readiness produce stalled cross-sell.

86. Multi-product cross-sell brief

Account: [paste primary product, current ARR]. Adjacent product: [paste]. Customer signal: [paste]. Draft a 400-word cross-sell brief: the named use case fit assessed honestly, the named champion who would sponsor it, the timing tied to customer cycle, the named decision-makers, the kill criterion. Cross-sell pursued without honest fit assessment produces double-sold-then-churned outcomes.

87. Referral request post-go-live

Customer at value-realized milestone: [paste outcome with metrics]. Named champion: [paste]. Draft a 200-word referral request: the named value moment as anchor, the named specific peers in their network (industry, role, geography), the named friction-free intro path (double opt-in), the named buyer-side benefit of giving the referral. Referral requests made before value realization fail.

88. Case study request

Customer at value-realized: [paste]. Specific outcome with metric: [paste]. Draft a 400-word case study request: the named outcome as the anchor (in the first sentence), the named specific featurable result, the named buyer-side benefit (industry recognition, internal positioning), the named time commitment, the named approval process. Case study requests without named outcome anchor produce vague testimonials.

89. Reference call request

Customer: [paste, profile]. Prospect requesting reference: [paste, role, similar fit]. Draft a 200-word reference request: the named match rationale (role, segment, use case), the named time commitment, the named buyer-side benefit (peer relationship, industry positioning), the named prep we will provide, the named timeline. Reference requests sent without match rationale produce declines.

90. NPS-respondent expansion outreach

NPS responder: [paste customer, role, score, comment]. Current product footprint: [paste]. Draft a 150-word outreach email: the named anchor in their NPS comment, the named adjacent opportunity tied to their feedback, the binary CTA to discuss, the named timing. NPS expansion outreach that does not reference the specific feedback produces no response.

91. At-risk account save plan

Account: [paste ACV, named risk, current health]. Stakeholders: [paste]. Draft a 500-word save plan: the named issue in the first paragraph, the named executive sponsor approach, the named value reset (rebuilding the buying case), the named offer (commercial, technical, organizational), the named timeline with milestones, the named kill criterion, the named decision-maker on our side. Save plans without named owners and kill criteria become permanent at-risk status.

92. Churn-risk forensic memo

Account: [paste]. Risk signals: [paste]. Draft a 500-word churn forensic memo: the named cause hypotheses (sponsor turnover, value gap, vendor consolidation, budget pressure, deployment failure), the named evidence, the named probability of churn, the named save plan with owners and timeline, the named kill criterion. Churn forensics that report risk without cause produce no save action.

93. Renewal preparation memo

Account: [paste ACV, renewal date, current health]. Named risks: [paste]. Draft a 500-word renewal prep memo: the named realistic forecast (commit, best case, worst case), the named confidence level with rationale, the named actions in the next 90 days that affect the forecast, the named procurement engagement plan, the named expansion case if applicable. Renewals run without 90-day preparation produce surprise procurement battles.

94. Multi-year renewal proposal

Account: [paste current ARR, history]. Multi-year option: [paste]. Customer financial cycle: [paste]. Draft a 500-word proposal: the named multi-year ROI compared to annual, the named buyer benefits, the named discount logic tied to commitment level, the customer-side internal sell, the named contract terms. Multi-year renewals proposed without buyer-side internal sell prep stall.

95. Champion turnover protocol

Champion departing: [paste]. Replacement: [paste, status]. Draft a 400-word transition memo: the named relationship health pre-transition, the named risks the transition creates, the named introduction path to replacement, the named immediate value reminder for the new sponsor, the named contingency if no replacement is named. Champion turnover handled passively produces renewal surprises.

96. Customer business review prep

Customer: [paste]. Audience: [paste named stakeholders]. Draft a 500-word CBR prep memo: the named business outcome story, the named adoption health, the named expansion or risk signals, the named asks, the named next checkpoint. AE-side CBR prep without customer business outcomes leads with our roadmap and loses the room.

97. Win-back campaign for churned account

Churned account: [paste churn date, reason, current state]. New context: [paste, our product update, named competitor weakness, leadership change]. Draft a 200-word win-back email: the named acknowledgment of past relationship, the named new specific context, the buyer-side benefit, the binary CTA. Win-back emails ignoring the original churn reason produce no response.

98. Account team annual plan

Account: [paste tier, ARR, deployment depth, organizational map]. Team: [paste named CSM, SE, AE roles]. Draft a 700-word annual plan: the named multi-year revenue thesis, the named buying centers and white-space, the named relationship strategy per executive, the named risks, the named cadence per touchpoint, the named milestones quarterly. Strategic accounts run without annual plans default to reactive motion.

99. Pipeline coverage memo (personal book)

AE personal pipeline: [paste deals by stage, ACV, probability, close date]. Quota and capacity: [paste]. Draft a 500-word personal coverage memo: the named coverage ratio against quota, the named gap by stage, the named action to fill the gap (new prospecting, deal acceleration, save plan), the named risks to the named commit, the weekly review cadence. AE personal coverage memos that report pipeline without coverage math produce missed quotas.

100. AE quarterly career plan

AE current role: [paste level, tenure, performance]. Aspirations: [paste]. Draft a 400-word career plan: the named target (promotion, lateral move, skill gap closure), the named evidence to build, the named manager support, the named development actions (training, peer shadow, named projects), the named check-in cadence. AEs without quarterly career plans drift into reactive career outcomes.

How the prompts fit a real AE week and quarter

Daily: inbox triage with prompted responses, prospecting volume against block, demo prep memos when on the calendar, deal-specific follow-up drafts, end-of-day deal notes synthesis.

Weekly: personal pipeline coverage review, deal-team standup with named risks, 1:1 prep with named asks of manager, top-3-deals close plan, cold outbound block discipline.

Monthly: qualification audit on the book, lost-deal post-mortems for the patterns, account research refresh on top accounts, marketing-sales alignment review, named expansion opportunities scan.

Quarterly: personal book annual plan refresh for top accounts, strategic-account QBRs, manager performance review with named evidence, career plan update, named pipeline rescue if needed.

Annually: book review with manager, named career conversation, hiring or interview loop participation, year-end deal pattern analysis, named referral and case study harvest.

A good cold email produces a reply. A good discovery call produces a multi-stakeholder map. A good negotiation produces a deal with price integrity. The AE job is deal work and memo work. The threads about the job are not.PromptLeadz AI Sales Prompts Pack, Section 6

Five mistakes that wreck AE prompts

1. Filling the prompt with vibes instead of named buyers, dollar values, and dates. The prompts ask for ACV, named stakeholders, specific dates, and named pain. Filling with "engaged", "interested", "warm" produces output of the same low calibration that buyers ignore and managers question.

2. Pasting LLM output directly into outbound sequencers. The prompts produce drafts. The actual email is the draft after editing for the specific account, removing LLM-cliche phrasing, and adding the one-line signal that only you know. AEs who paste raw output get flagged for spammy patterns.

3. Skipping the prompts that ask uncomfortable questions. The honest qualification memo, the lost-deal post-mortem, the close-or-kill internal decision, the at-risk account save plan. The avoided prompts are usually the ones with the most leverage.

4. Sharing the LLM draft externally without redaction. The prompts produce internal artifacts naming specific accounts, dollar values, deal risks, and competitive intel. The outputs should not leave the sales team without explicit review.

5. Running the AE-influencer prompts instead of these. Prompts that produce "trusted advisor" content reinforce the genre this pack rejects. Calibration to the LinkedIn-thread voice produces threads, not pipeline.

Sources and further reading

The pack draws on a body of public work from senior B2B sales practitioners and researchers. Recommended reading for AEs who want depth beyond the threads.

Chris Voss's Never Split the Difference remains the most useful public work on negotiation labels, calibrated questions, mirroring, and accusation audits. The negotiation prep prompt draws directly on these frames.

Matt Dixon's The Challenger Sale and The JOLT Effect are the foundational research on why buyers stall and how AEs handle indecision rather than just objection.

Anthony Iannarino's writing at thesalesblog.com is one of the most rigorous public bodies of B2B sales practitioner writing.

Lori Richardson and the Women in Sales community at scoremoresales.com covers practitioner realities with substance over content marketing.

MEDDPICC by Andy Whyte is the definitive book on the MEDDPICC qualification framework referenced in this pack.

About PromptLeadz

PromptLeadz publishes free component-built prompt packs and the production-grade Drop-in utilities that wrap them. The franchise covers role-based packs (PM, EM, CSM, Sales Leader, Operator, Data Analyst, VC), format-based packs (.md agent files in breadth and depth), and the underlying frameworks (the 8-Component Skeleton, the Anti-Prompt-Engineering Manifesto).

Every pack rejects the LinkedIn-influencer voice at the prompt level by banning the genre's signature phrases inline. The result is output calibrated for memos that survive peer review, not threads that go viral. Free packs ship with no email gate at promptleadz.com.

Questions people ask about AI sales prompts

Who is this AI sales prompts pack for?

Account executives, senior AEs, enterprise AEs, SDRs, BDRs, and individual contributor sellers who own a book of business. Most useful for AEs at B2B SaaS, fintech, and tech-enabled services companies running deals between five thousand and five million in ACV.

How is this different from the Sales Leader Pack?

The Sales Leader Pack (50 prompts) is calibrated for the CRO and VP Sales. This AE pack (100 prompts) is calibrated for the individual contributor seller: cold emails that get opened, discovery calls that surface pain, demos that earn next meetings, negotiations that protect price integrity, and post-sale handoffs that produce references.

Why does the pack ban phrases like just checking in and circling back?

Both phrases are content-free follow-ups that signal the AE has nothing new to say. Buyers read them as the seller running a sequence rather than respecting the buyer's time. Real AEs follow up with a new piece of information, not a check-in.

What output format do the AI sales prompts produce?

Memo register for internal artifacts (discovery notes, deal reviews, win-loss analyses). Buyer-respecting format for external artifacts (cold emails under 80 words, follow-ups under 40, proposals with named commitments, recap memos with named owners).

How does this pair with other PromptLeadz packs?

Pairs with the Sales Leader Pack, the AI Marketing Prompts Pack for marketing-sales alignment, the CSM Pack for the post-sale handoff, the 8-Component Skeleton, and the B2B Mega Pack.

Do these AI sales prompts work with Claude, ChatGPT, and Gemini?

Yes for all three. The prompts are built on the 8-Component Skeleton which works across Claude Opus 4.7, GPT-5.5, Gemini 3.1, and the open-source frontier.

Will these prompts replace my Outreach, Salesloft, or Apollo sequences?

No. Sequencers automate delivery; these prompts produce the content. Run the prompt to draft, edit for the specific account, paste into the sequencer.

Are these AI sales prompts safe to share with prospects?

The prompts themselves are free to share with the sales team. The internal artifacts (deal reviews, pricing strategy, lost-deal post-mortems, personal pipeline) are confidential and should not leave the sales organization.

The franchise: free packs, frameworks, and the manifesto

The thesis: The Anti-Prompt-Engineering Manifesto. The framework: The 8-Component Skeleton.

Free packs, no email gate · Calibrated for 2026 frontier models · promptleadz.com