By PromptLeadz · Reading time 18 minutes · 50 prompts across 5 categories · Calibrated for 2026 frontier models

What separates the CRO from the sales-influencer

Sales leadership is one of the most LinkedIn-saturated disciplines in B2B. Threads about always being closing, the challenger mindset, hunting versus farming, never giving up on the deal, and 10x-ing the pipeline get tens of thousands of likes. The threads describe a vibe. The actual job is forecast math.

A CRO's primary job is producing decision-grade artifacts: forecast calls with confidence levels that survive board scrutiny, pipeline reviews that name the deals at risk and the action per deal, deal desk memos that price the trade-off correctly, comp plans that produce the named behavior without blowing up the budget, territory carves that balance TAM across the team, CRO updates that name the gap from plan without burying the news. None of these artifacts look exciting on a screenshot. All of them compound.

Six dimensions separate the CRO voice from the sales-influencer voice. Substance: the CRO names the specific deal, the dollar value, the named account; the influencer names the disposition (always closing, challenger, hunter). Forecasts: the CRO presents commit, best case, worst case with the named conditions; the influencer presents a single number and a hustle story. Trade-offs: the CRO names what is being given up to win the deal; the influencer says "win at all costs". Comp math: the CRO designs accelerators with explicit attainment modeling; the influencer says "reward the hunters". Tone: the CRO writes flat memos that hold up under finance review; the influencer writes narrative arcs that go viral. Audience: the CRO writes for the board, the CEO, the finance partner, and the AE team; the influencer writes for the algorithm.

Both voices exist in the wild. Only one survives the board meeting, the finance review of the comp plan, and the post-quarter retro. This pack 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 a CRO who has just defended a forecast in front of the CFO, not a thread from a personal-brand sales influencer who has not.

Five categories. The CRO workflow end to end.

The five categories map to the five operating disciplines that determine whether a sales org compounds or accumulates drag. Pipeline and Forecast Discipline comes first because the forecast is the contract with the board and the rest of the company. Deal Desk and Pricing comes second because pricing decisions made deal-by-deal without precedent thinking erode margin over the year. Sales Process and Methodology comes third because the process discipline is what separates predictable execution from heroic individual performance. Comp, Quota, and Territory comes fourth because compensation design is where leverage is highest and most often broken. Sales Leadership and Org comes fifth because leadership is where the CRO either scales the team or hits the founder-CRO ceiling.

Most CROs who fail to compound the team do so by skipping the unglamorous categories: forecast discipline, deal desk precedent thinking, comp plan modeling, disqualification of bad-fit deals. The thread-genre CRO skips these in favor of "always be closing" content; the actual CRO does these because they are the leverage.

1. Weekly pipeline review memo

Period: [paste week ending]. Pipeline value: [paste]. Pipeline coverage: [paste vs forecast]. Top 10 deals: [paste with stage, value, close date, named risks]. Draft a 500-word weekly pipeline review memo: the headline (what changed since last week), the top 3 deals with the specific risk and the named action, the new deals added with the source, the deals slipped with the cause (customer-side, sales-side, product-side, procurement), the coverage trajectory, the ask of the manager. Pipeline reviews that recap status without naming risks waste both people's time.

2. Forecast call with confidence levels

Period: [paste month or quarter]. Pipeline: [paste with stage and value]. Historical close rates by stage: [paste]. Draft a 600-word forecast call memo: the commit number (the deals we are confident of), the best case (commit plus stretch deals with the named conditions that move them in), the worst case (commit minus the deals at material risk), the named risks that would move the number, the actions in the next 14 days that affect the call, the ask of leadership. Forecasts presented as single numbers without confidence ranges produce surprise misses.

3. Slip analysis for deals that pushed

Deals that slipped this period: [paste with original close date, new close date, stage, reason given]. Draft a 500-word slip analysis: the slip pattern (customer-side, sales-side, product-side, procurement, legal), the named cause per slip, the structural lesson (is the slip a one-time or a pattern), the actions to prevent recurrence, the named owner per action, the cadence of review. Slip analyses that lump every slip as "customer timing" miss the actual sales-process gap.

4. Coverage ratio diagnosis

Period: [paste]. Pipeline coverage: [paste ratio vs forecast]. Historical close rate: [paste]. Draft a 500-word coverage memo: the assessment (under-covered, well-covered, over-covered with stale pipeline), the cause of the gap (pipeline generation slowdown, conversion rate drop, deal-size shift, ICP drift), the actions needed in the next 30 days (more leads, faster qualification, stage hygiene cleanup), the named owner per action, the cadence of review. Coverage at 3x or below without explicit action produces a missed quarter.

5. Gap-to-plan response memo

Period: [paste]. Plan: [paste]. Current forecast: [paste]. Gap: [paste dollars]. Draft a 600-word gap-to-plan response: the cause of the gap (pipeline shortfall, conversion shortfall, ASP shortfall, churn impact on net new), the specific actions to close the gap (pull-forward deals, expansion in current accounts, accelerated closure of late-stage), the realistic estimate per action (not aspirational), the asks of leadership (resource, exec air cover, pricing flexibility), the kill criterion (when to revise the forecast down honestly). Gap-to-plan responses that pretend the gap will close without specific actions produce missed quarters with no learning.

6. Stage hygiene audit

Pipeline by stage: [paste]. Time-in-stage by deal: [paste]. Stage-to-stage conversion rates: [paste]. Draft a 500-word stage hygiene memo: the deals stuck more than 2x median in their stage (action: advance with the named next step or close-lost), the stages with abnormally high progression rates (often: deals stuck in late stages that should be closed-won), the stages with low conversion (process gap, qualification miss), the cleanup action per finding, the cadence of audit. Pipelines with stale deals create false coverage and produce surprise misses.

7. Win-rate trend analysis by segment

Recent close history: [paste by segment, deal size, time period]. Win rate trend: [paste]. Draft a 500-word win-rate analysis: the segments where win rate is improving (replicate the pattern), the segments where win rate is declining (cause analysis: competitive, ICP drift, AE skill, sales-cycle creep, product-fit gap), the structural actions (training, ICP narrowing, competitive enablement, product feedback to PM), the named decision-maker and timeline. Win-rate trends ignored until they show up in the forecast are visible 90 days earlier in the segment cuts.

8. Sales cycle length analysis

Recent closed-won deals: [paste with cycle length, segment, deal size]. Draft a 400-word sales cycle analysis: the median cycle by segment, the cycle creep (longer than 12 months ago) with the named cause hypothesis (procurement getting harder, deal sizes increasing, ICP shifting upmarket), the implication for forecasting and pipeline generation (longer cycle means more in-flight pipeline needed), the actions in process and qualification. Sales cycle creep ignored until it shows up as missed quarters is detectable 6 months earlier in the deal-level data.

9. Pipeline source mix audit

Pipeline by source: [paste with origin: inbound, outbound, partner, referral, marketing campaign]. Conversion rates by source: [paste]. Draft a 500-word source mix memo: the high-conversion sources (invest more, with named action), the low-conversion sources (cut, fix, or accept), the source dependency risk (concentration on one channel), the actions to diversify with named owners, the budget implication. Pipeline source mix that is heavy on one channel is fragile; this prompt forces diversification thinking.

10. Mid-quarter re-forecast memo

Quarter: [paste]. Original forecast: [paste]. Current state at mid-quarter: [paste pipeline, closed, gap]. Draft a 500-word re-forecast memo: the revised number with the confidence range, the cause of the change (positive or negative, factual), the actions in the remaining quarter, the asks of leadership, the comms plan to the team, the cadence of weekly check-ins. Mid-quarter re-forecasts presented as no-change while reality drifts produce credibility damage with leadership.

11. Deal desk approval memo

Deal: [paste, ARR, segment, products]. Asks from sales: [paste, e.g. discount %, payment terms, custom T&Cs]. Draft a 600-word deal desk approval memo: the business case (why this deal, customer fit, strategic value), the asks itemized with rationale per ask, the trade-off (revenue impact of discount vs deal value), the precedent risk (does this set a pattern across the segment), the recommended terms with approver sign-off needed, the alternative offers if asks rejected. Deal desk approvals without precedent-risk thinking erode segment margin over the year.

12. Discounting trade-off memo

Deal: [paste, ARR, segment]. Discount requested: [paste percent and rationale]. Customer alternatives: [paste]. Draft a 500-word discount memo: the customer-side rationale (genuine budget constraint, competitive bid, procurement game), the precedent risk in the segment, the trade-off (revenue lost vs deal closed vs precedent set), the alternative offers (multi-year commit for discount, payment terms, service credits, scope reduction), the recommended position, the walk-away threshold. Discounting decisions made deal-by-deal without precedent thinking erode pricing power over quarters.

13. MSA pushback negotiation prep

Customer: [paste]. MSA pushback points: [paste from legal redline]. Deal value: [paste]. Draft a 600-word MSA negotiation prep: the key pushback points classified (commercial: pricing, terms, scope vs legal: liability, IP, indemnification vs operational: SLA, data, audit), the position on each (hold, partial concession, structural restructure), the leverage I have (deal value, alternatives, customer urgency), the BATNA, the escalation path on our side. MSAs negotiated without explicit hold-vs-concede positions produce inconsistent terms across the book.

14. Multi-year proposal with explicit ROI math

Deal: [paste, ARR for 1 year vs N years]. Customer financial profile: [paste]. Draft a 600-word multi-year proposal: the ROI math (cumulative cost over N years vs annual renewal with assumed escalator), the customer-side benefits (lock-in pricing, predictable, exec attention, dedicated resources), the our-side benefits (revenue certainty, reduced churn risk, planning visibility), the discount structure (named percent per additional year), the contract terms protecting both sides, the close plan. Multi-year proposals without explicit ROI math produce customer pushback at procurement review.

15. T&Cs negotiation memo (auto-renewal, liability cap, IP, SLA)

Customer: [paste]. T&Cs pushback: [paste with specific clauses]. Draft a 500-word T&Cs response: the auto-renewal position (hold for self-serve, evergreen for enterprise, negotiable on cycle), the liability cap position (typically hold at fees paid in prior 12 months, negotiable up to 2x for enterprise), the IP position (no concessions on core IP), the SLA position (named uptime tier with credit-based remedy), the named legal sign-off required for each concession. T&Cs negotiated by sales without legal sign-off produce surprise customer disputes later.

16. Custom-terms request memo

Customer: [paste, ARR, segment]. Custom term requested: [paste specific clause or structure]. Draft a 400-word custom-terms memo: the operational implication (does the term materially change our delivery or risk), the financial implication, the precedent risk (will other customers ask for the same), the alternative offers, the named decision-maker, the kill criterion. Custom terms accepted without precedent thinking produce a book that diverges across customers and breaks operations.

17. Procurement-led negotiation handling

Customer: [paste]. Procurement contact: [paste]. Procurement asks: [paste]. Sponsor-side intent: [paste]. Draft a 500-word procurement handling memo: the procurement asks classified (price, terms, performance commitments, alternatives evaluation), the sponsor-side reality check (procurement asks may not reflect sponsor intent), the named escalation path back to the sponsor when procurement positions diverge from sponsor reality, the response strategy per ask, the timeline. Procurement-led negotiations handled without sponsor cross-check produce deals lost on procurement game rather than on fit.

18. Pricing escalation to leadership

Deal: [paste, ARR, customer, ask]. Why escalating: [paste, e.g. discount beyond approval threshold, custom structure, strategic deal]. Draft a 400-word escalation memo: the deal in one paragraph (size, segment, strategic value), the ask in plain terms, the trade-off (what we get, what we give up), the precedent assessment, the recommended approval condition, the named decision-maker and the deadline. Pricing escalations that bury the trade-off produce executives who feel ambushed and decline on principle.

19. Free-pilot / POC request decision

Customer: [paste, ARR potential, segment]. POC request: [paste scope, duration, cost to deliver]. Draft a 400-word POC decision memo: the qualification criteria (this customer would buy if X is true during the POC), the cost to deliver (engineer hours, customer success hours, opportunity cost), the success criteria (the named outcome that converts to a paid deal), the kill criterion (when we walk away from the POC), the alternative offers (paid pilot, time-limited license). Free POCs without explicit success criteria produce extended unpaid work that does not convert.

20. Competitive displacement pricing memo

Customer: [paste, current vendor, contract end]. Competing vendor pricing: [paste]. Switching cost: [paste customer-side]. Draft a 500-word competitive displacement memo: the customer-side switching cost (technical migration, training, contract overlap, change management), our pricing relative to the competitor, the named unique value we offer that the competitor does not, the recommended pricing strategy (match, premium with value justification, discount with multi-year commit), the kill criterion. Competitive displacement deals priced by matching alone leak margin without winning on differentiation.

Most sales advice circulating on LinkedIn is content marketing. The work that actually compounds is the forecast memo that names the gap and the deal desk memo that names the trade-off.PromptLeadz Sales Leader Pack

21. Discovery question bank for net-new

Segment: [paste]. Product fit: [paste]. ICP profile: [paste]. Draft a 500-word discovery question bank: the qualifying questions (budget, authority, need, timeline, named explicitly), the diagnostic questions (current state, pain, why now, what triggered the search), the future-state questions (what good looks like in 12 months), the technical-fit questions, the disqualifying questions (red flags that mean we walk gracefully). Discovery question banks built around our pitch rather than the customer state produce demos to unqualified prospects.

22. MEDDPICC qualification memo

Deal: [paste]. Information gathered to date: [paste]. Draft a 600-word MEDDPICC qualification memo: Metrics (the specific customer KPIs this deal moves), Economic buyer (named, confirmed, met with), Decision criteria (what gets them to yes, in their words), Decision process (specific steps and dates), Identified pain (specific, not generic), Champion (named, validated with evidence of internal selling), Competition (named alternatives), the gap from full qualification, the actions to close the gap. MEDDPICC memos filled with assumptions rather than verified information produce surprise no-decisions.

23. Champion mapping memo

Deal: [paste]. Org map known: [paste roles and stated influence]. Draft a 500-word champion mapping memo: the named champion (person actively selling for us internally with evidence), the economic buyer (named, with budget authority confirmed), the influencers (named, with their concerns), the blockers (named, with their concerns and the path to neutralize), the named coach (provides intel, not necessarily a champion). Champion maps that confuse champion (sells for us internally) with sponsor (supports us) produce deals lost to internal politics.

24. Mutual close plan

Deal: [paste, target close date]. Outstanding steps: [paste from both sides]. Draft a 600-word mutual close plan: the customer-side commitments (named owner, dated milestone), the our-side commitments (named owner, dated milestone), the dependencies between commitments, the escalation path if either side slips, the review cadence (weekly until close), the close ceremony (who signs, where, when, in what format). Close plans built only on our side produce surprise procurement delays in the final two weeks.

25. Pre-call prep for executive meeting

Customer exec: [paste name, role, tenure, stated priorities]. Meeting context: [paste]. Draft a 400-word pre-call prep memo: the exec's stated business priorities, the exec's likely concerns about our solution, the open questions to ask (broad to specific), the position to defend if challenged, the asks to make, the worst-case scenarios and the response. Pre-call preps written as our talking points without the exec's perspective produce meetings the exec disengages from.

26. Demo prep for technical audience

Audience: [paste roles, stack, technical depth]. Use case: [paste]. Pain identified: [paste]. Draft a 500-word demo prep: the demo flow (start with the pain, show the solution, end with the integration story), the technical depth per section, the named integration points to highlight, the questions to expect with the prepared answer, the failure handling (when something breaks in the demo), the follow-up close. Technical demos built as feature tours without the pain anchor produce technical interest but no decision.

27. Demo prep for executive audience

Audience: [paste exec roles, stated priorities]. Use case: [paste]. Strategic context: [paste]. Draft a 400-word exec demo prep: the demo flow (start with the business outcome, show the proof, end with the path to deployment), the proof points the exec will care about (peer logos, business metrics, time-to-value), the open questions to ask, the close. Exec demos that walk through the product UI without the business outcome lose the room within the first five minutes.

28. Pricing conversation prep

Deal: [paste, customer context]. Customer pricing signals so far: [paste]. Draft a 500-word pricing conversation prep: the framing (anchor with value before number, name the comparable deals or peer references), the price (named, with the rationale), the response to pushback (the next move, the walk-away threshold), the close (the specific yes we are asking for), the worst-case (do not give a number you do not intend to honor). Pricing conversations entered without explicit framing produce reactive discounts.

29. Disqualification memo

Deal: [paste, current state, time invested]. Red flags identified: [paste]. Draft a 400-word disqualification memo: the red flags named factually (no budget confirmed, no champion, wrong product fit, wrong ICP, indefinite timeline), the cost of continued pursuit (sales hours, technical hours, opportunity cost), the alternative use of the resource, the comms to the customer (graceful, not burning the bridge), the named decision-maker. Disqualification decisions avoided produce wasted quarters chasing deals that will never close.

30. Stage advancement criteria memo

Current stages: [paste]. Friction observed: [paste, e.g. stage definitions unclear, AE judgment varies]. Draft a 500-word stage criteria memo: the named entry criteria per stage (specific, verifiable), the exit criteria per stage (the customer-side commitments that prove advancement), the time-bound stage limit (max time in stage before disqualification or escalation), the manager review cadence per stage. Sales stages without verifiable criteria produce a pipeline that means different things to different AEs.

31. Comp plan design memo

Team: [paste headcount, role, segment]. OTE target: [paste]. Quota distribution: [paste]. Draft a 700-word comp plan design memo: the base/variable split (typically 60/40 for AEs, 70/30 for SDRs, varies for hunters vs farmers), the accelerator structure (activates at 100% with named multiplier per tier), the SPIF design (event-based, time-bound, with budget cap), the clawback rules (for churn within 90 days), the named manager override compensation, the rollout sequence with comms plan. Comp plans designed without explicit accelerator modeling produce reps who coast at quota and blowout payouts that strain the budget.

32. Quota setting from bottoms-up

Team: [paste]. Historical performance: [paste win rate, cycle, deal size by AE]. Market opportunity: [paste]. Draft a 600-word bottoms-up quota memo: the realistic quota per AE based on historical capacity and ramp adjusted, the stretch factor applied (typically 10 to 20 percent), the validation against tops-down number, the gap if any, the actions to close the gap (more pipeline, lower quotas, more headcount, segment shift), the named manager sign-off. Bottoms-up quotas that ignore the tops-down number produce a plan that does not hit company targets.

33. Quota setting from tops-down

Company plan: [paste sales target]. Team: [paste headcount]. Per-rep target implied: [paste]. Draft a 500-word tops-down quota memo: the per-rep target implied by the plan, the realism check against historical capacity, the gap analysis (if per-rep target is unrealistic, the options: hire more, expand market, raise prices, accept the miss), the manager calibration of who can hit higher targets and who cannot, the comms plan to the team. Tops-down quotas issued without bottoms-up calibration produce demoralization and attrition in the first 90 days.

34. Territory carving memo

Team: [paste headcount and segments]. Market data: [paste TAM by geo or vertical, account list]. Draft a 600-word territory carving memo: the carving approach (geo, vertical, account-list, hybrid with rationale per choice), the per-rep TAM (balanced, not concentrated on one or two reps), the named accounts per rep with the strategic priorities, the rules for new logo acquisition (which rep owns inbound from a new account), the cadence of review. Territory carving without balanced TAM produces reps fighting over the same accounts and disengaged from the rest.

35. Accelerator structure design

OTE: [paste]. Quota: [paste]. Historical attainment distribution: [paste]. Draft a 500-word accelerator memo: the threshold to activate (typically 100% of quota), the multiplier per tier (e.g., 1.5x from 100-120%, 2x from 120-150%, 2.5x above 150%), the cap question (capped vs uncapped, with the named risk per choice), the comms to the team, the modeling of total comp cost at various attainment scenarios including the long-tail blowout case. Accelerators designed without cap analysis produce blowout payouts that strain the comp budget.

36. SPIF design for a specific period

Period: [paste duration]. Goal: [paste, e.g. land new logos, accelerate stuck deals, expand multi-year]. Budget: [paste]. Draft a 400-word SPIF memo: the named behavior the SPIF rewards, the specific payout structure (per-deal bonus, leaderboard, top-3 prizes), the eligibility rules, the comms plan, the post-period analysis (did the SPIF produce the named behavior or just pull-forward of in-flight deals). SPIFs designed without explicit behavioral targets produce gaming and pull-forward without net new performance.

37. Mid-year quota reset memo

Period: [paste]. Quota: [paste original]. Current attainment: [paste]. Trigger for reset: [paste, e.g. market shift, product launch delay, exec direction change]. Draft a 600-word quota reset memo: the rationale for the reset (factual, not blame-shifting), the new quota structure, the comp implication (typically: keep prior accelerators in place, adjust new ones), the comms plan to the team (clear, not defensive), the named decision-maker and the timeline. Quota resets handled poorly produce attrition; this prompt forces structure.

38. AE comp dispute resolution

AE: [paste, deal, dispute]. Comp plan terms: [paste relevant section]. Draft a 400-word comp dispute resolution memo: the dispute named factually, the comp plan reading (what the plan actually says, not what the AE assumes), the precedent (have similar disputes been resolved a particular way), the recommended resolution, the comp plan clarification for future cases. Comp disputes resolved AE-by-AE without precedent thinking produce trust erosion across the team.

39. Sales credit attribution rules

Scenario: [paste, e.g. AE transition mid-deal, channel partner involvement, BDR-to-AE handoff dispute, expansion in shared account]. Draft a 500-word credit attribution memo: the named scenarios (AE transition, partner, BDR handoff, expansion, channel conflict), the credit rule per scenario (full, split, percentage-based), the named decision-maker for edge cases, the cadence of review. Credit attribution rules made ad-hoc produce political battles between AEs and erode the comp plan's credibility.

40. Manager override compensation design

Manager role: [paste, span of control]. Performance metrics: [paste]. Draft a 500-word manager comp memo: the base/variable structure (typically more base, less variable than AEs), the override calculation (percent of team quota attainment), the team-attainment thresholds and accelerators, the named behavioral metrics (team retention, AE development, pipeline coverage), the manager-specific SPIF structure. Manager comp designed as scaled AE comp produces managers who sell their own deals rather than coach the team.

A good forecast names the gap. A good comp plan names the math. A good close plan names the dates. The job is named work. The threads about the job are not.PromptLeadz Sales Leader Pack, Section 5

41. Sales kickoff (SKO) agenda

SKO date: [paste]. Team size: [paste]. Strategic priorities: [paste]. Draft a 600-word SKO agenda: the opening (last year results, named honestly), the strategic priorities for the new year (with the metric per priority), the comp plan and territory rollout with named time for Q&A, the enablement sessions (named topics, named owners), the team-building sessions (deliberate, not vague), the close (the call to action for the year). SKOs without specific strategic priorities and metrics produce expensive offsites that do not change behavior.

42. Sales leaderboard design

Team: [paste]. Behavioral goals: [paste, e.g. activity, pipeline gen, closed-won]. Draft a 400-word leaderboard memo: the named metrics on the board (typically: closed-won ARR, pipeline generated, win rate by segment), the visibility (public, manager-only, individual), the cadence (real-time, weekly, monthly), the reward structure if any, the named owner who maintains the board. Leaderboards built on activity metrics alone produce activity without outcomes.

43. Manager 1:1 cadence with AE

AE: [paste role, tenure, current performance]. Manager: [paste]. Draft a 500-word 1:1 cadence memo: the weekly 1:1 structure (open deals review, pipeline gen, blockers, one growth conversation), the monthly career conversation (development goals, calibration, comp), the quarterly comp and performance review, the cadence of skip-level meetings, the structure when performance is below the bar (more frequent 1:1s, structured PIP discussion). AE 1:1s that drift across deal status without growth conversations produce stagnant reps.

44. AE performance improvement plan

AE: [paste, role, tenure]. Performance gap: [paste with specific examples and dates]. Draft a 600-word PIP memo: the gap from the bar (specific behaviors, not generic), the measurable improvements expected (tied to behaviors not just outcomes), the support I will provide (coaching, ride-alongs, enablement, ICP narrowing), the timeline (typically 60-90 days for a sales PIP), the decision point and the alternative outcome, the named manager-of-manager sign-off. Sales PIPs written defensively produce legal documents not improvement; this version names the change required.

45. Sales team quarterly retro

Quarter: [paste]. Plan vs actual: [paste]. Major events: [paste, e.g. product launch, key hire, key loss, competitive shift]. Draft a 600-word sales retro: the headline result, the wins with structural source (process, AE skill, product, market timing), the misses with structural cause (no blame), the three structural changes for next quarter (named, with owner and timeline), the comms to the team, the cadence of follow-up. Sales retros that produce "communicate better" without structural changes repeat the misses next quarter.

46. Exec stakeholder update for leadership

Period: [paste]. Audience: [paste, e.g. CEO, CFO, CMO]. Draft a 500-word exec update: the headline outcome (the ARR closed, with the gap from plan named directly), the wins by segment with named accounts, the open risks with the management response, the asks of the exec (decision, resource, air cover), the next checkpoint. Exec updates that bury the gap from plan produce executives who hear the bad news from someone else first.

47. CRO update to CEO

Period: [paste]. CEO context: [paste, e.g. board meeting prep, investor update]. Draft a 600-word CRO update: the topline (ARR, growth rate, vs plan), the segment-level cuts that explain the topline, the strategic decisions made this period, the open issues with the named path forward, the asks of the CEO (resource, exec air cover, strategic decisions), the next CEO checkpoint. CRO updates without strategic decisions named produce CEOs who feel uninformed and surprised at the board meeting.

48. Hiring profile for AE

Role: [paste segment, level, expected ramp time]. ICP: [paste]. Draft a 500-word hiring profile: the named experience requirements (years in segment, deal size sold, sales motion match), the named skills (discovery depth, multi-threading, executive selling, technical literacy), the named anti-pattern hires (the experiences that look good on paper but do not fit our motion), the interview loop, the rubric per stage, the bar raiser role. Hiring profiles without explicit anti-patterns produce hires who look good on paper and fail in the first six months.

49. Manager promotion case

AE: [paste, tenure, performance]. Manager track readiness signals: [paste]. Draft a 600-word manager promotion case: the named projects demonstrating manager-level scope (deal coaching, peer mentorship, process improvement contributions), the gaps and the closing plan, the trade-off named (top AE becomes new manager, with the risk of losing a top producer who may not be a strong manager), the recommended timing, the named decision-makers. Manager promotion cases without explicit trade-off thinking produce a team where the new manager misses both their own and team quotas.

50. AE departure response memo

Departing AE: [paste, territory, pipeline state]. Reason for departure: [paste]. Draft a 500-word departure response: the immediate handoff plan (named accounts assigned to current AEs, with comp credit rules), the pipeline review (which deals are at risk, which can survive a transition), the territory question (backfill vs absorb vs reshape), the comms to the customers (consistent, not defensive), the named decision-maker for the backfill question. AE departures handled without explicit comp-credit and customer-comms plans produce dropped deals and damaged customer relationships.

How the prompts fit a real CRO week and quarter

Daily: pipeline check on top deals, escalation triage, hard conversation prep when needed. The daily discipline catches drift before the weekly review.

Weekly: forecast call, pipeline review with each manager, deal desk approvals, exec update to CEO. The weekly cadence is where the forecast contract gets re-validated.

Monthly: segment-level win-rate review, source mix audit, manager 1:1 cadence audit, churn signal review with CSM. The monthly cadence catches trends before they become quarterly misses.

Quarterly: sales retro, quota and capacity recalibration, comp plan review, territory rebalancing, CRO board update. The quarterly cadence is where the CRO job actually shows.

Annually: SKO, comp plan redesign, territory carving for the new year, hiring plan for the year, ICP refresh based on win-rate data. The annual cadence is where the strategy gets calibrated.

Five mistakes that wreck CRO prompts

1. Filling in the prompt with vibes instead of dollar values, named accounts, and dates. The prompts ask for ARR, close dates, named champions, specific gap-to-plan dollars. Filling with "big deal", "qualified pipeline", "strong forecast" produces output of the same low calibration that finance will reject.

2. Treating the output as the final memo. The prompts produce drafts. The actual memo is the draft after editing for accuracy, removing the LLM-cliche phrasing, and verifying every number against the CRM and the comp plan document.

3. Skipping the prompts that ask uncomfortable questions. The disqualification memo, the slip analysis, the gap-to-plan response, the AE PIP. The avoided prompts are usually the ones with the most leverage. Notice the avoidance.

4. Sharing the LLM draft externally without redaction. The prompts produce internal artifacts naming specific deals, customers, AEs, and dollar values. The outputs should not leave the sales organization without explicit review.

5. Running the sales-influencer prompts instead of these. Prompts that produce "always be closing" content reinforce the genre this pack rejects. Calibration to the LinkedIn-thread voice produces threads, not forecast memos.

Sources and further reading

The pack draws on a body of published work from senior sales leaders. Recommended reading for CROs and VP sales who want depth beyond the threads.

John McMahon, The Qualified Sales Leader, is the most rigorous public treatment of MEDDPICC qualification, deal inspection, and the operating cadence of a sales leader running an enterprise team.

Aaron Ross and Marylou Tyler, Predictable Revenue, remains the canonical text on the SDR-AE separation, outbound pipeline generation, and the operational discipline that turned sales from craft into process.

Matt Dixon and Brent Adamson, The Challenger Sale, is the original research behind the most-cited and most-misused sales methodology of the last decade. The original is rigorous; the cargo-cult version on LinkedIn is not.

Pavilion content at joinpavilion.com is the most consistent contemporary peer community for CROs and senior revenue leaders, especially on comp plan design and territory work.

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

Who is this sales leader prompt pack for?

CROs, VP sales, regional sales directors, sales managers, and senior AEs acting in a leadership capacity. Most useful for B2B SaaS sales leaders running teams of 5 to 50 reps, mid-market or enterprise motion. The prompts assume basic sales leadership literacy: MEDDPICC, pipeline coverage, comp plan structures, territory carving, deal desk discipline.

Does it work for transactional SMB and complex enterprise sales?

Yes for both, with calibration. SMB volume teams lean on the pipeline source mix, stage hygiene, and SPIF design prompts (the high-cadence work). Enterprise complex teams lean on the MEDDPICC qualification, champion mapping, mutual close plan, and deal desk prompts (the deep-deal work). The forecast and comp prompts work across both motions.

Why does the pack ban phrases like "Always Be Closing" and "Challenger Sale"?

Both are legitimate ideas reduced to LinkedIn cliches. The pack bans the cliche framing because it produces low-calibration output that performs sales hustle rather than naming the specific deal, the gap, or the trade-off. Real CROs talk about specific deals, specific dollar values, and specific dates; the cliche genre talks about mindset and hustle in general.

What output format do the prompts produce?

Forecast memo register: flat, factual, named deals, specific dollar values, specific owners and dates. The opposite of LinkedIn-thread register. The prompts are calibrated for internal use: forecast calls, pipeline reviews, deal desk memos, comp plans, CRO updates that hold up under board, finance, and CEO scrutiny.

How does this pair with other PromptLeadz packs?

Pairs with the 8-Component Skeleton framework as the foundation, the CSM Pack for the post-sale renewal motion, the Operator Pack for finance and comp dependencies, and the PM Pack for the product feedback loop. The B2B Mega Pack covers the rep-level prompts that AEs use in the field.

Are these prompts safe to share with my team?

The prompts themselves are free to share. The outputs of the forecast, comp plan, PIP, AE departure, and deal desk prompts are confidential and should not leave the sales organization. The discovery and qualification prompts are designed for AE-level use and are safe to share with the team.

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

Yes for all three. The prompts are built on the 8-component skeleton which works across frontier models. Claude tends to handle the forecast call and slip analysis most naturally; ChatGPT requires slightly tighter constraints on dollar formatting; Gemini works best when the output format is named explicitly with section headers.

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