🤝260 prompts · 13 categories

The Sales Prompt Pack

260 sales prompts to fill the pipeline and close more deals.

Prospecting, cold outreach, discovery, demos, objection handling, negotiation and follow-up — a full sales team's playbook, prompt by prompt.

Get all 260 prompts — free

Drop your email and the full library unlocks instantly.

No spam. Instant access. Unsubscribe anytime.

  • 260 copy-paste prompts across 13 categories
  • Works with ChatGPT, Claude & Gemini
  • From cold outreach to closing to account expansion

Joined by 5,400+ founders & marketers

260 prompts

#001Revenue Strategy Operating System

SALES STRATEGY & REVENUE PLANNINGFounders, sales leaders, revenue teams, consultants, B2B companies, SaaS teams, agencies, and any business that needs a practical sales roadmap.

Build a complete sales strategy that connects revenue goals, customer segments, sales motions, pipeline targets, team capacity, and execution cadence.

You are a senior revenue strategist. Build a complete sales strategy operating system for my business. Business context: Company: [COMPANY] Website: [WEBSITE] Industry: [INDUSTRY] Offer: [OFFER] Average deal size: [AVERAGE DEAL SIZE] Sales cycle length: [SALES CYCLE] Current revenue: [CURRENT REVENUE] Revenue goal: [REVENUE GOAL] Target timeframe: [TIMEFRAME] Current pipeline: [CURRENT PIPELINE] Current customers: [CUSTOMERS] Ideal customer profile: [ICP] Sales team size: [TEAM SIZE] Current sales channels: [CHANNELS] Main constraints: [CONSTRAINTS] Main competitors: [COMPETITORS] Build the operating system: 1. Revenue thesis Define: - where revenue should come from - which customer segments deserve focus - which offers should be prioritized - which sales motions fit the business - which channels are most realistic - which revenue paths should be avoided 2. Sales strategy map Create a strategy across: - target segments - sales motion - offer positioning - pipeline creation - qualification - discovery - proposal - closing - expansion - retention handoff 3. Revenue math Calculate or estimate: - annual target - quarterly target - monthly target - required closed deals - required opportunities - required qualified meetings - required outbound or inbound activity - pipeline coverage needed - conversion rate assumptions Use [NEEDS DATA] where numbers are missing. 4. Execution cadence Create: - weekly sales rhythm - monthly pipeline review - quarterly strategy review - activity scorecard - deal review structure - forecast review structure - learning loop 5. Final roadmap Deliver: - first 7-day actions - first 30-day plan - first 90-day roadmap - key risks - key metrics - owner assignments - leadership decisions needed Rules: - Do not create a vague sales plan. - Do not assume all channels are equally useful. - Do not recommend activity without connecting it to revenue. - The final strategy should be specific, measurable, and execution-ready. --------------------------------------------------------------------------------

#002Revenue Goal Reverse-Engineering Model

SALES STRATEGY & REVENUE PLANNINGRevenue planning, quota setting, founder sales, pipeline planning, sales team targets, and quarterly growth planning.

Turn a revenue goal into clear pipeline, deal, meeting, conversion, activity, capacity, and timing requirements.

Act as a revenue planning analyst. Reverse-engineer my revenue goal into the exact sales activity and pipeline model needed to reach it. Inputs: Revenue target: [REVENUE TARGET] Time period: [TIME PERIOD] Average contract value: [ACV] Average order value: [AOV] Gross margin: [MARGIN] Sales cycle: [SALES CYCLE] Current pipeline value: [PIPELINE VALUE] Current win rate: [WIN RATE] Lead-to-meeting rate: [LEAD TO MEETING RATE] Meeting-to-opportunity rate: [MEETING TO OPPORTUNITY RATE] Opportunity-to-close rate: [OPP TO CLOSE RATE] Expansion revenue: [EXPANSION] Churn or cancellations: [CHURN] Sales capacity: [SALES CAPACITY] Current activity levels: [ACTIVITY] Build the model: A. Target breakdown Calculate: - annual target - quarterly target - monthly target - weekly target - new revenue needed - expansion revenue needed - replacement revenue needed B. Deal math Estimate: - deals needed - opportunities needed - qualified meetings needed - leads or accounts needed - required pipeline coverage - required pipeline creation per month C. Conversion assumptions Identify: - current conversion rates - required conversion rates - weak conversion points - unrealistic assumptions - sensitivity to deal size - sensitivity to win rate - sensitivity to sales cycle length D. Capacity check Analyze whether the current team can support: - prospecting volume - discovery calls - proposals - follow-ups - closing activity - account management - expansion work E. Scenario plan Create: - conservative scenario - realistic scenario - aggressive scenario - downside scenario For each include: - deals required - pipeline required - activity required - key assumptions - confidence level Rules: - Do not present missing assumptions as facts. - Do not ignore sales cycle lag. - Do not use one average if deal size varies heavily by segment. - Show the revenue math clearly enough that leadership can challenge it. --------------------------------------------------------------------------------

#003Sales Motion Selector

SALES STRATEGY & REVENUE PLANNINGFounders, SaaS companies, agencies, consultants, B2B teams, product-led businesses, and companies deciding between outbound, inbound, partner-led, self-serve, or enterprise sales.

Choose the best sales motion based on price point, market type, deal complexity, buyer behavior, urgency, product maturity, and available resources.

You are a go-to-market and sales motion strategist. Help me choose the best sales motion for my business. Business inputs: Product or service: [PRODUCT / SERVICE] Target customer: [TARGET CUSTOMER] Buyer role: [BUYER ROLE] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Purchase complexity: [COMPLEXITY] Market awareness: [MARKET AWARENESS] Urgency of problem: [URGENCY] Competitive intensity: [COMPETITION] Current demand: [DEMAND] Team size: [TEAM SIZE] Budget: [BUDGET] Founder involvement: [FOUNDER INVOLVEMENT] Customer acquisition channels: [CHANNELS] Business goal: [GOAL] Evaluate these sales motions: - founder-led sales - outbound sales - inbound sales - product-led sales - content-led sales - partner-led sales - community-led sales - enterprise sales - transactional sales - account-based sales - channel sales - hybrid sales motion For each motion provide: - fit score from 1 to 10 - why it fits - why it may fail - required assets - required team - expected sales cycle - pipeline source - conversion risks - best use case Then recommend: 1. Primary sales motion 2. Secondary sales motion 3. Motion to avoid for now 4. 90-day validation plan 5. Metrics to prove or disprove the motion 6. First sales play to launch Rules: - Do not recommend enterprise sales for low-value simple purchases unless justified. - Do not recommend self-serve if buyers require heavy trust-building. - Do not choose a sales motion only because it is popular. - Match the motion to buyer behavior, economics, and execution capacity. --------------------------------------------------------------------------------

#004Ideal Revenue Segment Prioritizer

SALES STRATEGY & REVENUE PLANNINGICP planning, segmentation, revenue strategy, sales focus, account prioritization, and early-stage business planning.

Identify which customer segments should receive sales focus based on revenue potential, urgency, win probability, deal size, retention, and sales effort.

Act as a revenue segmentation strategist. Help me decide which customer segment we should sell to first or prioritize next. Segments to compare: [PASTE SEGMENTS] Business context: Offer: [OFFER] Current customers: [CUSTOMERS] Best customers: [BEST CUSTOMERS] Worst-fit customers: [WORST CUSTOMERS] Revenue goal: [GOAL] Average deal size: [DEAL SIZE] Sales capacity: [CAPACITY] Market constraints: [CONSTRAINTS] Competitive landscape: [COMPETITION] Proof or case studies: [PROOF] Product limitations: [LIMITATIONS] Evaluate each segment: 1. Revenue potential Score: - market size - budget availability - willingness to pay - expansion potential - retention potential - referral potential 2. Sales efficiency Score: - ease of finding buyers - ease of reaching buyers - urgency of pain - decision speed - number of stakeholders - win probability - sales cycle length - implementation complexity 3. Strategic fit Score: - offer fit - proof fit - product fit - brand fit - competitive advantage - long-term market value 4. Risks Identify: - low budget - long procurement - high churn - low urgency - custom work risk - poor margin - weak differentiation - high support load 5. Recommendation Create: - segment ranking - best first segment - best expansion segment - segment to avoid - sales message for each priority segment - prospecting channels - deal qualification rules Rules: - Do not pick the largest segment automatically. - Do not ignore sales effort and win probability. - Do not recommend segments where the offer has weak proof. - Choose the segment most likely to create predictable revenue. --------------------------------------------------------------------------------

#005Pipeline Architecture and Coverage Planner

SALES STRATEGY & REVENUE PLANNINGSales operations, CRM setup, pipeline reviews, forecasting, quota planning, and sales team management.

Design a pipeline structure with stages, definitions, conversion assumptions, coverage ratios, aging rules, and management routines.

You are a sales operations architect. Design a pipeline system that makes revenue predictable and easy to manage. Sales context: Business: [BUSINESS] Offer: [OFFER] Revenue target: [TARGET] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Current pipeline stages: [CURRENT STAGES] Current CRM: [CRM] Current pipeline value: [PIPELINE VALUE] Current conversion rates: [CONVERSION RATES] Sales team: [TEAM] Lead sources: [LEAD SOURCES] Forecasting process: [FORECASTING PROCESS] Create the pipeline architecture: A. Stage design Define pipeline stages with: - stage name - entry criteria - exit criteria - required buyer evidence - seller action - probability range - common risks - CRM fields required Include stages for: - lead - qualified lead - discovery scheduled - discovery completed - qualified opportunity - solution fit - proposal - negotiation - verbal commit - closed won - closed lost B. Pipeline coverage model Calculate or estimate: - target bookings - pipeline required - coverage ratio - new pipeline needed monthly - stale pipeline threshold - stage conversion targets - stage aging limits C. Pipeline hygiene rules Create rules for: - moving deals forward - removing dead deals - updating close dates - next step requirement - deal notes - loss reasons - probability changes D. Review cadence Create: - weekly rep review - monthly pipeline review - quarterly pipeline strategy review - forecast inspection checklist E. Output Provide: - final pipeline stage table - required CRM fields - pipeline dashboard metrics - manager review questions - cleanup checklist Rules: - Do not allow vague stages like "interested" without entry criteria. - Do not count unqualified leads as real pipeline. - Do not inflate forecast with stale opportunities. - Pipeline quality matters more than pipeline size. --------------------------------------------------------------------------------

#006Sales Channel Portfolio Planner

SALES STRATEGY & REVENUE PLANNINGRevenue leaders, startup founders, B2B teams, service businesses, agencies, SaaS, and companies deciding where to focus sales effort.

Choose and prioritize sales channels based on buyer behavior, cost, conversion potential, time to revenue, scalability, and execution requirements.

Act as a sales channel strategist. Build a channel portfolio that can create predictable pipeline. Business context: Company: [COMPANY] Offer: [OFFER] Target buyer: [BUYER] Market: [MARKET] Deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Revenue goal: [GOAL] Current channels: [CURRENT CHANNELS] Past channel performance: [PERFORMANCE] Team capacity: [CAPACITY] Budget: [BUDGET] Brand awareness: [AWARENESS] Competitive environment: [COMPETITION] Analyze these channels: - cold email - cold calling - LinkedIn outbound - warm referrals - partner referrals - inbound content - paid search - paid social - webinars - events - communities - marketplaces - affiliate/channel partners - account-based marketing - customer expansion For each channel provide: - fit score - buyer fit - cost profile - speed to pipeline - speed to revenue - required assets - required skills - expected conversion bottleneck - scalability - risk - best first experiment Then build: 1. Primary channel strategy 2. Secondary channel strategy 3. Channel testing backlog 4. 90-day experiment plan 5. Budget allocation 6. Activity targets 7. Metrics by channel 8. Kill criteria Rules: - Do not recommend too many channels at once. - Do not choose channels without matching buyer behavior. - Do not ignore time-to-revenue. - The plan should focus execution, not create more complexity. --------------------------------------------------------------------------------

#007Sales Priorities and Tradeoff Decision Board

SALES STRATEGY & REVENUE PLANNINGSales planning, founder focus, team prioritization, quarterly planning, and reducing scattered sales activity.

Help a sales leader decide what to focus on now by comparing revenue activities across impact, urgency, confidence, effort, risk, and strategic fit.

You are a sales strategy facilitator. Help me choose the highest-value sales priorities and make explicit tradeoffs. Current situation: Revenue goal: [GOAL] Current performance: [PERFORMANCE] Current pipeline: [PIPELINE] Current team capacity: [CAPACITY] Current problems: [PROBLEMS] Current opportunities: [OPPORTUNITIES] Possible initiatives: [INITIATIVES] Timeframe: [TIMEFRAME] Constraints: [CONSTRAINTS] Evaluate each initiative: Potential initiatives may include: - improve ICP focus - rebuild sales messaging - launch outbound campaign - improve discovery process - improve proposal process - fix CRM hygiene - increase pricing - improve follow-up - create case studies - build partner channel - improve win rate - shorten sales cycle - reduce churn handoff issues - hire sales rep - train sales team - improve forecasting For each initiative provide: - impact score - urgency score - confidence score - effort score - risk score - time to impact - owner required - metric affected - dependency - reason to do it - reason not to do it Create a decision board: 1. Do now 2. Schedule next 3. Delegate 4. Test lightly 5. Ignore for now 6. Stop doing Then write: - top 3 priorities - tradeoffs accepted - what the team must say no to - weekly execution plan - success metrics - review date Rules: - Do not prioritize based only on urgency. - Do not recommend more work than the team can execute. - Do not avoid tradeoffs. - The output should create focus and momentum. --------------------------------------------------------------------------------

#008Sales Process Design and Buyer Journey Alignment

SALES STRATEGY & REVENUE PLANNINGSales teams, founders, B2B revenue teams, agencies, consultants, SaaS, enterprise sales, and complex sales cycles.

Build a sales process that matches how buyers actually become aware, evaluate, trust, decide, approve, and purchase.

Act as a buyer journey and sales process architect. Design a sales process that matches how my customers make decisions. Business context: Offer: [OFFER] Target buyer: [BUYER] Buyer roles involved: [BUYER ROLES] Pain points: [PAINS] Purchase triggers: [TRIGGERS] Objections: [OBJECTIONS] Decision criteria: [CRITERIA] Sales cycle: [SALES CYCLE] Current process: [CURRENT PROCESS] Current bottlenecks: [BOTTLENECKS] Current assets: [ASSETS] Map the buyer journey: A. Buyer stages Define what happens at each stage: - unaware - problem aware - solution aware - vendor aware - consideration - internal alignment - business case - procurement or approval - decision - onboarding handoff B. Seller actions For each stage define: - seller goal - key question to answer - discovery focus - proof needed - content or asset needed - next step - disqualification signal - CRM stage C. Friction points Identify: - confusion - lack of urgency - lack of trust - budget uncertainty - stakeholder conflict - timing issues - implementation concerns - risk concerns - competitor comparison D. Sales process design Create: - stages - exit criteria - talk tracks - required assets - follow-up timing - manager inspection points - automation opportunities E. Final output Provide: - buyer journey map - sales process map - stage checklist - asset gap list - improvement roadmap Rules: - Do not design the sales process only around seller activities. - Do not push proposals before buyer qualification. - Do not ignore internal buyer approval. - The sales process should help buyers make a confident decision. --------------------------------------------------------------------------------

#009Sales Capacity and Hiring Plan

SALES STRATEGY & REVENUE PLANNINGSales hiring, capacity planning, quota design, founder-led sales transition, scaling teams, and revenue operations.

Determine whether revenue goals require more reps, better conversion, higher prices, better pipeline, or improved productivity before hiring.

You are a sales capacity planning consultant. Determine what sales capacity is needed to hit our revenue goals and whether hiring is the right move. Inputs: Revenue target: [TARGET] Current revenue: [CURRENT REVENUE] Average deal size: [DEAL SIZE] Win rate: [WIN RATE] Sales cycle: [SALES CYCLE] Pipeline coverage: [PIPELINE COVERAGE] Current reps: [REPS] Rep productivity: [PRODUCTIVITY] Ramp time: [RAMP TIME] Quota per rep: [QUOTA] Lead volume: [LEAD VOLUME] Founder sales involvement: [FOUNDER INVOLVEMENT] Sales support resources: [SUPPORT] Current bottlenecks: [BOTTLENECKS] Budget for hiring: [BUDGET] Analyze capacity: 1. Current capacity Calculate or estimate: - current revenue capacity - realistic quota capacity - pipeline handling capacity - meeting capacity - proposal capacity - follow-up capacity - founder dependency 2. Gap analysis Identify whether the gap is caused by: - not enough pipeline - weak conversion - small deal size - long sales cycle - poor qualification - low activity - lack of sales enablement - weak sales management - insufficient headcount - poor onboarding 3. Hiring decision Recommend: - hire now - delay hiring - hire sales development first - hire account executive - hire sales manager - hire revenue operations - improve process before hiring Explain why. 4. Hiring model If hiring is recommended, define: - role - quota - ramp plan - required support - compensation assumptions - hiring timeline - success metrics - risk controls 5. Alternative levers If hiring is not the first move, recommend: - conversion improvements - pricing improvements - pipeline generation - sales process improvements - automation - founder-led sales systemization Rules: - Do not recommend hiring as the default fix. - Do not ignore ramp time. - Do not assign unrealistic quotas. - Capacity planning should be tied to revenue math and pipeline reality. --------------------------------------------------------------------------------

#010Sales Forecasting Framework

SALES STRATEGY & REVENUE PLANNINGSales leaders, revenue operations, founders, board reporting, pipeline reviews, and monthly or quarterly forecasting.

Create a reliable forecasting framework using pipeline stages, deal quality, close probability, sales cycle, historical conversion, risk factors, and scenario planning.

Act as a sales forecasting strategist. Build a forecasting framework that is realistic, inspectable, and useful for decision-making. Forecast context: Forecast period: [PERIOD] Revenue target: [TARGET] Current pipeline: [PIPELINE] Opportunities: [OPPORTUNITIES] Pipeline stages: [STAGES] Historical win rates: [WIN RATES] Average sales cycle: [SALES CYCLE] Rep forecasts: [REP FORECASTS] Deal notes: [DEAL NOTES] Close dates: [CLOSE DATES] Expansion opportunities: [EXPANSION] Churn or contraction risk: [CHURN RISK] Known risks: [RISKS] Create the forecasting system: A. Forecast categories Define: - commit - best case - pipeline - upside - at risk - excluded For each category include: - entry criteria - evidence required - probability range - manager inspection questions - common errors B. Deal inspection For each deal analyze: - buyer pain - decision process - economic buyer - timeline - budget - competition - next step - close date realism - stakeholder support - risk factors - forecast category C. Forecast scenarios Create: - conservative forecast - realistic forecast - optimistic forecast - downside forecast Include: - expected revenue - confidence level - gap to target - pipeline needed - actions required D. Forecast hygiene Create rules for: - close date changes - stale deals - missing next steps - stage aging - probability updates - rep judgment vs evidence - manager overrides E. Reporting format Provide: - weekly forecast meeting agenda - forecast dashboard - executive summary - risk register - action list Rules: - Do not forecast based only on rep optimism. - Do not count deals without clear next steps. - Do not ignore deal age or close date movement. - A good forecast should show both number and confidence. --------------------------------------------------------------------------------

#011Account-Based Revenue Planning Map

SALES STRATEGY & REVENUE PLANNINGB2B sales, enterprise sales, SaaS, agencies, high-ticket services, account-based marketing, and strategic account planning.

Build an account-based sales plan that prioritizes target accounts, stakeholders, triggers, value propositions, outreach plays, and pipeline goals.

You are an account-based revenue strategist. Build a practical account-based sales plan for my target market. Inputs: Company: [COMPANY] Offer: [OFFER] Target account list: [ACCOUNTS] Ideal customer profile: [ICP] Deal size target: [DEAL SIZE] Target industries: [INDUSTRIES] Buyer personas: [BUYERS] Known pain points: [PAINS] Trigger events: [TRIGGERS] Competitors: [COMPETITORS] Proof assets: [PROOF] Sales team capacity: [CAPACITY] Revenue goal: [GOAL] Create the ABM sales plan: 1. Account selection rules Score accounts by: - fit - revenue potential - urgency - accessibility - strategic value - technology fit - buying trigger - competitive position - relationship access 2. Account tiers Create: - Tier 1 strategic accounts - Tier 2 strong-fit accounts - Tier 3 scalable accounts - accounts to exclude For each tier define: - number of accounts - personalization depth - outreach cadence - required research - sales assets - success metrics 3. Stakeholder map For each account type identify: - economic buyer - champion - user - technical evaluator - finance approver - legal/procurement - blocker - influencer 4. Sales plays Create: - trigger-based play - pain-based play - competitor displacement play - expansion play - executive outreach play - partner-intro play 5. Pipeline targets Define: - accounts to contact - meetings needed - opportunities needed - pipeline target - expected close rate - time horizon Rules: - Do not treat account-based selling like mass outbound. - Do not over-personalize low-value accounts. - Do not ignore multi-stakeholder buying. - Focus on accounts where the business can create clear value. --------------------------------------------------------------------------------

#012Revenue Roadmap by Quarter

SALES STRATEGY & REVENUE PLANNINGAnnual planning, quarterly planning, leadership alignment, sales team execution, and revenue strategy communication.

Convert annual sales goals into a quarter-by-quarter revenue roadmap with initiatives, pipeline targets, milestones, experiments, team responsibilities, and risk controls.

Act as a VP of Sales building a quarterly revenue roadmap. Translate our sales goals into a practical execution plan. Planning context: Annual revenue goal: [ANNUAL GOAL] Current revenue run rate: [RUN RATE] Current pipeline: [PIPELINE] Current team: [TEAM] Offer mix: [OFFERS] Target segments: [SEGMENTS] Sales channels: [CHANNELS] Sales cycle: [SALES CYCLE] Conversion rates: [CONVERSIONS] Budget: [BUDGET] Strategic constraints: [CONSTRAINTS] Known risks: [RISKS] Build the roadmap: Q1 — Foundation and focus Define: - strategic priority - pipeline target - revenue target - key initiatives - process fixes - channel experiments - enablement assets - metrics Q2 — Pipeline acceleration Define: - growth priority - pipeline creation target - conversion improvements - channel scale plan - hiring or capacity actions - forecast improvements Q3 — Conversion and expansion Define: - win-rate initiatives - account expansion plays - pricing or packaging adjustments - strategic partnerships - team coaching focus Q4 — Close, renew, and plan Define: - year-end closing plan - renewal protection - expansion campaigns - forecast cleanup - next-year planning inputs For each quarter include: - revenue target - pipeline target - main initiatives - owner - deadline - leading indicators - lagging indicators - risks - executive decisions needed Rules: - Do not spread effort evenly across too many initiatives. - Do not ignore sales cycle lag. - Do not make Q4 dependent on pipeline created too late. - Roadmap should show sequence, dependencies, and tradeoffs. --------------------------------------------------------------------------------

#013Sales Strategy Risk Register

SALES STRATEGY & REVENUE PLANNINGSales planning, executive reviews, investor updates, board reporting, forecast risk, and revenue leadership.

Identify the risks that can stop a revenue plan from working and create mitigation actions before the quarter or year begins.

You are a revenue risk analyst. Build a risk register for my sales strategy and explain how to reduce the chance of missing target. Sales plan: [PASTE SALES PLAN] Business context: Revenue goal: [GOAL] Timeframe: [TIMEFRAME] Current pipeline: [PIPELINE] Team capacity: [CAPACITY] Sales channels: [CHANNELS] Target market: [MARKET] Offer: [OFFER] Sales cycle: [SALES CYCLE] Win rate: [WIN RATE] Known constraints: [CONSTRAINTS] Identify risks across: - pipeline creation - lead quality - qualification - win rate - deal size - sales cycle length - discounting - competition - buyer urgency - stakeholder approval - pricing - delivery capacity - churn or retention - team capacity - rep ramp - CRM accuracy - forecasting - market conditions - founder dependency - channel concentration For each risk provide: - risk description - likelihood - impact - early warning signal - owner - mitigation action - contingency plan - review cadence Then create: 1. Top 5 risks 2. Risks that require leadership attention 3. Risks that need weekly monitoring 4. Risks that can be accepted 5. First 10 mitigation actions 6. Forecast caveats Rules: - Do not hide uncomfortable risks. - Do not list generic risks without signals. - Do not create mitigation actions without owners. - A good sales plan should include risk management, not just targets. --------------------------------------------------------------------------------

#014Sales Strategy Narrative for Leadership

SALES STRATEGY & REVENUE PLANNINGExecutive presentations, investor updates, board decks, founder planning, sales kickoff, and cross-functional alignment.

Turn a sales plan into a clear leadership narrative that explains the revenue goal, strategy, assumptions, risks, milestones, and decisions needed.

Act as a sales strategy communicator. Turn the information below into a clear leadership-ready sales strategy narrative. Inputs: Sales goal: [GOAL] Current situation: [CURRENT STATE] Market opportunity: [MARKET] Target customers: [CUSTOMERS] Sales motion: [SALES MOTION] Channels: [CHANNELS] Pipeline model: [PIPELINE MODEL] Team plan: [TEAM PLAN] Key initiatives: [INITIATIVES] Forecast: [FORECAST] Risks: [RISKS] Decisions needed: [DECISIONS] Audience: [AUDIENCE] Tone: [TONE] Write the narrative: 1. Strategic headline Create one clear sentence that explains the sales strategy. 2. Current reality Explain: - where revenue stands now - what is working - what is not working - what changed in the market - what must improve 3. Growth logic Explain: - who we will sell to - what we will sell - how we will create pipeline - how we will convert opportunities - how we will expand accounts - how this connects to the revenue goal 4. Revenue assumptions Summarize: - deal size - win rate - sales cycle - pipeline coverage - team capacity - conversion assumptions - risk level 5. Execution plan Provide: - next 30 days - next 90 days - quarterly milestones - owners - metrics 6. Leadership ask Clarify: - decisions needed - resources needed - tradeoffs - risks of not acting Rules: - Do not use vague sales jargon. - Do not make the plan sound more certain than it is. - Do not bury the decisions leadership must make. - The narrative should make the strategy easy to understand and challenge. --------------------------------------------------------------------------------

#015Sales Experiment Portfolio Designer

SALES STRATEGY & REVENUE PLANNINGStartups, founder-led sales, sales teams improving pipeline, revenue experiments, and teams that need learning before scaling.

Build a focused sales experiment system for testing messaging, segments, channels, offers, pricing, outreach, and conversion improvements.

You are a sales experimentation strategist. Design a sales experiment portfolio that helps us discover the best path to revenue. Context: Business: [BUSINESS] Offer: [OFFER] Target customers: [CUSTOMERS] Revenue goal: [GOAL] Current bottleneck: [BOTTLENECK] Current sales motion: [SALES MOTION] Current channels: [CHANNELS] Current messaging: [MESSAGING] Current conversion rates: [CONVERSIONS] Team capacity: [CAPACITY] Experiment timeframe: [TIMEFRAME] Create experiment portfolio: A. Hypothesis generation Create hypotheses for: - target segment - buyer trigger - sales message - outreach channel - offer packaging - pricing - discovery script - proposal format - follow-up cadence - referral ask - partner channel - urgency creation B. Experiment design For each experiment include: - hypothesis - test audience - action - minimum sample size - duration - success metric - guardrail metric - required assets - owner - effort level - risk C. Prioritization Rank experiments by: - revenue impact - learning value - speed - cost - confidence - operational complexity D. Experiment calendar Create: - first 2-week tests - first 30-day tests - first 90-day tests - experiments to delay - experiments to reject E. Learning loop Define: - how to review results - how to decide scale/stop/change - what to document - how to convert wins into SOPs Rules: - Do not run too many experiments at once. - Do not scale before a signal is clear. - Do not call an experiment successful without a defined metric. - The goal is faster learning and better revenue decisions. --------------------------------------------------------------------------------

#016Sales Metrics Dashboard Builder

SALES STRATEGY & REVENUE PLANNINGSales leaders, founders, RevOps, CRM dashboards, weekly sales meetings, and sales performance management.

Design a sales dashboard that connects activities, pipeline, conversion, velocity, win rate, forecast, revenue, and strategic priorities.

Act as a sales analytics and dashboard designer. Build a sales dashboard that shows whether we are on track and what needs attention. Business context: Company: [COMPANY] Revenue goal: [GOAL] Sales motion: [SALES MOTION] Sales team: [TEAM] CRM: [CRM] Sales cycle: [SALES CYCLE] Average deal size: [DEAL SIZE] Pipeline stages: [STAGES] Lead sources: [SOURCES] Current metrics: [METRICS] Stakeholders: [STAKEHOLDERS] Reporting cadence: [CADENCE] Design the dashboard: 1. Executive view Track: - bookings - revenue closed - pipeline created - pipeline coverage - forecast - win rate - sales cycle - average deal size - target attainment - risks to target 2. Sales management view Track: - activity - meetings booked - opportunities created - stage conversion - stage aging - stale deals - next steps missing - close date movement - loss reasons - rep performance 3. Channel view Track: - pipeline by channel - win rate by channel - deal size by channel - conversion by channel - cost per opportunity - revenue by channel - channel quality 4. Deal quality view Track: - qualification quality - buyer role coverage - urgency - budget status - competition - decision date - risk level 5. Dashboard rules Define: - metric definition - data source - owner - update frequency - warning threshold - action trigger - meeting usage Rules: - Do not create metrics that nobody acts on. - Do not report activity without outcome metrics. - Do not combine pipeline stages with different quality levels. - The dashboard should support better weekly decisions. --------------------------------------------------------------------------------

#017Sales Strategy for New Market Entry

SALES STRATEGY & REVENUE PLANNINGMarket expansion, new verticals, geographic expansion, startup growth, B2B sales, agencies, SaaS, and product launches.

Create a sales plan for entering a new industry, geography, customer segment, vertical, or product category.

You are a new market sales strategist. Build a practical sales strategy for entering this new market. Expansion context: Current business: [CURRENT BUSINESS] Current customers: [CURRENT CUSTOMERS] New market: [NEW MARKET] Target buyers: [BUYERS] Offer for new market: [OFFER] Why this market: [WHY] Market knowledge: [KNOWLEDGE] Competitors: [COMPETITORS] Proof available: [PROOF] Sales channels available: [CHANNELS] Budget: [BUDGET] Team capacity: [CAPACITY] Revenue goal: [GOAL] Timeline: [TIMELINE] Build the plan: A. Market entry assumptions List the assumptions about: - buyer pain - budget - urgency - decision process - competition - differentiation - channel access - pricing - proof required B. Validation plan Create ways to validate: - customer interviews - outbound tests - landing page tests - partner conversations - expert interviews - competitor analysis - pilot offers - paid tests C. Sales strategy Define: - first segment to target - first buyer persona - first offer - first channel - first sales message - first proof asset - first outreach campaign - first conversion goal D. Revenue roadmap Create: - first 30 days - first 60 days - first 90 days - first 6 months - pipeline targets - learning targets - revenue targets E. Go/no-go criteria Define: - signals to continue - signals to pivot - signals to pause - data needed - decision date Rules: - Do not assume current messaging works in the new market. - Do not scale before validating buyer demand. - Do not ignore proof gaps. - New market entry should reduce uncertainty before increasing spend. --------------------------------------------------------------------------------

#018Offer-to-Sales Strategy Alignment Audit

SALES STRATEGY & REVENUE PLANNINGSales strategy, offer design, pricing alignment, low conversion diagnosis, founder-led sales, and revenue troubleshooting.

Check whether the offer, pricing, packaging, proof, sales motion, and buyer expectations are aligned enough to support revenue growth.

Act as a sales strategy and offer alignment auditor. Determine whether our offer is easy enough to sell and whether our sales strategy matches it. Offer context: Offer: [OFFER] Target customer: [CUSTOMER] Problem solved: [PROBLEM] Outcome promised: [OUTCOME] Pricing: [PRICING] Packaging: [PACKAGING] Guarantee or risk reversal: [GUARANTEE] Proof: [PROOF] Competitors: [COMPETITORS] Sales motion: [SALES MOTION] Sales cycle: [SALES CYCLE] Conversion issues: [ISSUES] Customer objections: [OBJECTIONS] Audit alignment: 1. Offer clarity Evaluate: - problem clarity - outcome clarity - buyer fit - scope clarity - value communication - differentiation - urgency - risk reversal 2. Pricing fit Evaluate: - price-to-value fit - buyer budget fit - margin fit - sales effort fit - discounting risk - comparison risk 3. Sales motion fit Evaluate: - self-serve fit - consultative sales fit - outbound fit - inbound fit - partner fit - enterprise fit 4. Proof fit Evaluate: - case studies - testimonials - data - demonstrations - pilots - guarantees - founder credibility - product credibility 5. Fix plan Create: - offer changes - pricing changes - packaging changes - proof assets needed - sales process changes - messaging changes - qualification changes - roadmap priority Rules: - Do not blame sales execution if the offer is hard to understand. - Do not recommend lowering price before improving value communication. - Do not ignore sales effort relative to deal size. - The offer and sales strategy must make economic sense together. --------------------------------------------------------------------------------

#019Cross-Functional Revenue Alignment Planner

SALES STRATEGY & REVENUE PLANNINGRevenue planning, GTM alignment, scaling teams, leadership planning, quarterly planning, and fixing handoff problems.

Align sales strategy with marketing, product, customer success, finance, operations, and leadership so revenue execution is not isolated.

You are a revenue alignment facilitator. Create a cross-functional plan that connects sales strategy with the rest of the business. Context: Revenue goal: [GOAL] Sales strategy: [SALES STRATEGY] Marketing strategy: [MARKETING] Product roadmap: [PRODUCT] Customer success process: [CS] Operations constraints: [OPS] Finance targets: [FINANCE] Leadership priorities: [LEADERSHIP] Current handoff issues: [HANDOFF ISSUES] Current team structure: [TEAM] Planning timeframe: [TIMEFRAME] Align the functions: A. Sales needs from marketing Define: - lead quality requirements - demand generation priorities - messaging assets - case studies - content - event support - campaign timing - channel feedback loop B. Sales needs from product Define: - product gaps affecting sales - demo requirements - roadmap communication - feature proof - competitive positioning - implementation constraints C. Sales needs from customer success Define: - onboarding handoff - expansion signals - renewal risks - customer proof collection - referral opportunities - retention feedback D. Sales needs from finance and operations Define: - pricing approvals - discount rules - contract rules - delivery capacity - margin requirements - hiring budget - forecast expectations E. Alignment system Create: - shared metrics - weekly meeting rhythm - monthly revenue review - decision rights - owner matrix - escalation process - feedback loop Rules: - Do not let sales strategy operate separately from delivery capacity. - Do not create shared goals without owners. - Do not ignore customer success in revenue planning. - Predictable revenue requires cross-functional alignment. --------------------------------------------------------------------------------

#020Full Sales Strategy and Revenue Planning Audit

SALES STRATEGY & REVENUE PLANNINGFull sales strategy reviews, founder-led companies, sales leaders, RevOps teams, agencies, consultants, SaaS companies, and annual or quarterly planning.

Audit and rebuild a complete sales strategy across goals, ICP, sales motion, pipeline, channels, pricing, team capacity, forecasting, metrics, risks, and execution.

Act as an independent sales strategy and revenue planning auditor. Review my complete sales system and create a practical roadmap for predictable revenue growth. Full context: Company: [COMPANY] Website: [WEBSITE] Industry: [INDUSTRY] Offer: [OFFER] Current revenue: [CURRENT REVENUE] Revenue target: [REVENUE TARGET] Timeframe: [TIMEFRAME] Current customers: [CUSTOMERS] Ideal customer profile: [ICP] Target segments: [SEGMENTS] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Win rate: [WIN RATE] Lead sources: [LEAD SOURCES] Current pipeline: [PIPELINE] Pipeline stages: [STAGES] Sales channels: [CHANNELS] Sales team: [TEAM] Sales process: [PROCESS] CRM setup: [CRM] Forecasting process: [FORECASTING] Sales assets: [ASSETS] Pricing and packaging: [PRICING] Competitors: [COMPETITORS] Marketing support: [MARKETING] Customer success handoff: [CS HANDOFF] Main bottlenecks: [BOTTLENECKS] Main risks: [RISKS] Constraints: [CONSTRAINTS] Audit across 40 dimensions: 1. Revenue goal clarity 2. Revenue math 3. ICP focus 4. Segment prioritization 5. Offer clarity 6. Pricing fit 7. Sales motion fit 8. Channel strategy 9. Pipeline generation 10. Pipeline coverage 11. Pipeline stage definitions 12. CRM hygiene 13. Lead qualification 14. Discovery process 15. Proposal process 16. Negotiation process 17. Closing process 18. Follow-up discipline 19. Win rate 20. Sales cycle length 21. Average deal size 22. Forecast accuracy 23. Sales capacity 24. Hiring plan 25. Sales enablement assets 26. Objection handling 27. Competitive positioning 28. Account prioritization 29. Expansion revenue 30. Customer success handoff 31. Referral system 32. Partner opportunities 33. Sales metrics 34. Dashboard quality 35. Management cadence 36. Sales experiments 37. Cross-functional alignment 38. Risk management 39. Execution roadmap 40. Overall revenue readiness For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - revenue impact - risk if ignored - recommended fix - priority - effort - confidence level Then synthesize: A. Hard truth Explain the biggest issue preventing predictable revenue. B. Revenue strategy Define: - best target segment - best sales motion - best primary channel - best secondary channel - required pipeline coverage - required conversion improvements - biggest tradeoff C. Roadmap Create: - first 24-hour fixes - first 7-day fixes - first 30-day plan - first 90-day plan - 6-month revenue roadmap - owners - dependencies - metrics D. Operating system Create: - weekly sales cadence - pipeline review structure - forecast review structure - deal review structure - experiment review structure - dashboard requirements - accountability model E. Executive summary Write a direct summary with: - fastest revenue win - highest-risk sales issue - first pipeline fix - first conversion fix - first channel test - first sales asset to build - first metric to clean up - one operating principle for predictable revenue Rules: - Do not recommend generic sales advice. - Do not ignore weak assumptions. - Do not inflate forecast confidence. - Use [NEEDS DATA], [NEEDS CUSTOMER RESEARCH], or [NEEDS CRM REVIEW] where required. - The final roadmap should be specific, prioritized, and ready for execution.

#021ICP Revenue Fit Architect

ICP, BUYER PERSONAS & ACCOUNT RESEARCHFounders, sales leaders, B2B teams, agencies, SaaS companies, consultants, and teams that need to stop selling to everyone.

Define a practical ideal customer profile based on revenue potential, urgency, fit, sales efficiency, retention potential, and ability to buy.

You are an ICP strategy architect. Build a clear ideal customer profile that helps my sales team focus on the accounts most likely to buy, stay, expand, and create profitable revenue. Business context: Company: [COMPANY] Offer: [OFFER] Current customers: [CURRENT CUSTOMERS] Best customers: [BEST CUSTOMERS] Worst customers: [WORST CUSTOMERS] Average deal size: [AVERAGE DEAL SIZE] Sales cycle: [SALES CYCLE] Win rate: [WIN RATE] Retention or churn data: [RETENTION DATA] Expansion revenue data: [EXPANSION DATA] Main competitors: [COMPETITORS] Primary sales motion: [SALES MOTION] Revenue goal: [REVENUE GOAL] Team capacity: [CAPACITY] Build the ICP in five layers: 1. Firmographic fit Define: - company size - industry - geography - business model - maturity stage - revenue range - team structure - operational complexity - buying environment 2. Problem fit Identify: - urgent pains - expensive inefficiencies - recurring problems - strategic priorities - consequences of inaction - why the problem matters now 3. Solution fit Evaluate: - how well our offer solves the problem - what use cases fit best - what use cases are weak - where our proof is strongest - what integrations, resources, or conditions must exist 4. Sales fit Assess: - ease of identifying accounts - ease of reaching decision-makers - buying speed - stakeholder complexity - budget availability - procurement friction - likelihood of competitive displacement 5. Economic fit Evaluate: - expected deal size - margin quality - retention potential - expansion potential - support burden - implementation cost - referral potential Output: - primary ICP definition - secondary ICP definition - anti-ICP definition - ICP scoring table - qualification questions - disqualification signals - best-fit account examples - sales messaging angle for the ICP - first 30-day account targeting plan Rules: - Do not define the ICP using demographics only. - Do not include segments that cannot afford the offer. - Do not ignore retention and support burden. - Use [NEEDS DATA] where customer evidence is missing. --------------------------------------------------------------------------------

#022Buyer Persona Interview Synthesizer

ICP, BUYER PERSONAS & ACCOUNT RESEARCHCustomer research, persona development, sales messaging, discovery script design, and ICP validation.

Turn messy customer interview notes into useful buyer personas with pains, triggers, objections, language, decision criteria, and sales messaging insights.

Act as a buyer research analyst. Synthesize the customer interview notes below into clear buyer personas that can improve sales strategy, messaging, qualification, and outreach. Interview notes: [PASTE INTERVIEW NOTES] Additional context: Offer: [OFFER] Target market: [TARGET MARKET] Current sales process: [SALES PROCESS] Current assumptions: [ASSUMPTIONS] Main sales goals: [GOALS] Process the notes in this order: A. Extract raw signals Separate the notes into: - direct customer pains - desired outcomes - buying triggers - objections - fears - decision criteria - alternatives considered - language patterns - emotional cues - internal politics - budget signals - timing signals B. Build persona profiles For each persona create: - persona name - job title or role - responsibilities - business pressures - personal success metrics - daily frustrations - strategic goals - buying authority - influence level - information sources - preferred communication style C. Map buying psychology For each persona explain: - what makes them care - what makes them hesitate - what they need to believe before buying - what risk they are trying to avoid - what proof they trust - what language resonates - what language creates resistance D. Translate into sales use Create: - outreach angle - discovery questions - objection handling notes - demo focus - proposal emphasis - follow-up themes - content ideas - qualification criteria E. Confidence review Label each persona insight as: - strongly supported by evidence - moderately supported - weakly supported - assumption requiring validation Rules: - Do not invent motivations not supported by the notes. - Do not create decorative personas that sales cannot use. - Use direct customer language where useful. - Flag contradictions instead of smoothing them over. --------------------------------------------------------------------------------

#023Decision-Maker and Influencer Map

ICP, BUYER PERSONAS & ACCOUNT RESEARCHB2B sales, enterprise deals, complex buying committees, account-based selling, and stakeholder mapping.

Identify every person involved in the buying decision, what they care about, what they can block, and how sales should communicate with each one.

You are a complex B2B buying committee strategist. Build a stakeholder map for selling [OFFER] into [TARGET ACCOUNT TYPE]. Deal context: Target account type: [ACCOUNT TYPE] Industry: [INDUSTRY] Offer: [OFFER] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Problem solved: [PROBLEM] Known buyer roles: [KNOWN ROLES] Current deal stage: [DEAL STAGE] Known objections: [OBJECTIONS] Competitors or alternatives: [ALTERNATIVES] Create a buying committee map: 1. Role inventory Identify likely roles: - economic buyer - champion - primary user - technical evaluator - department head - finance approver - legal/procurement - security or compliance reviewer - implementation owner - executive sponsor - potential blocker - informal influencer 2. Stakeholder analysis For each role provide: - what they care about - what they fear - what success looks like for them - what objections they may raise - what proof they need - how they evaluate vendors - what can make them say yes - what can make them block the deal - best sales message - best asset to send 3. Influence map Classify each stakeholder by: - decision power - influence level - urgency - likely attitude - risk level - access difficulty 4. Sales action plan Create: - who to contact first - who to build trust with - who to avoid overloading - who needs a business case - who needs technical proof - who needs executive alignment - meeting sequence - follow-up strategy 5. Deal risk view Flag: - missing stakeholders - hidden blockers - weak champion risk - unclear decision authority - procurement risk - budget risk - timeline risk Rules: - Do not assume one buyer controls the full decision. - Do not treat users and economic buyers the same. - Do not recommend generic messaging for all stakeholders. - Use [NEEDS ACCOUNT RESEARCH] when role assumptions require verification. --------------------------------------------------------------------------------

#024Account Research Brief Generator

ICP, BUYER PERSONAS & ACCOUNT RESEARCHAccount-based sales, enterprise prospecting, outbound preparation, strategic account planning, and personalized outreach.

Create a sales-ready research brief for a target account using company context, likely pains, relevant triggers, stakeholders, and outreach angles.

Act as a senior account researcher. Create a concise but useful account research brief that helps a salesperson prepare for outreach or a discovery call. Target account: Company name: [COMPANY NAME] Website: [WEBSITE] Industry: [INDUSTRY] Company size: [SIZE] Location: [LOCATION] Known products or services: [PRODUCTS] Recent news or triggers: [NEWS / TRIGGERS] Target buyer role: [BUYER ROLE] Our offer: [OFFER] Our proof: [PROOF] Known competitors: [COMPETITORS] Research notes: [RESEARCH NOTES] Build the brief: A. Company snapshot Summarize: - what the company does - who they serve - how they likely make money - likely strategic priorities - operational complexity - maturity level B. Fit assessment Evaluate: - ICP fit - problem fit - timing fit - budget fit - solution fit - urgency level - account priority C. Likely pains and triggers Identify: - business pains - operational pains - revenue pains - customer pains - efficiency pains - risk pains - recent trigger events - possible internal initiatives D. Stakeholder map List likely stakeholders with: - role - likely concern - best message angle - proof needed - likely objection E. Outreach strategy Create: - first email angle - LinkedIn message angle - cold call opener - discovery call opening question - relevant value hypothesis - personalization points - what not to say F. Research gaps List what still needs to be verified before outreach. Rules: - Do not fabricate company facts. - Use [NEEDS VERIFICATION] for uncertain research. - Do not over-personalize with weak or irrelevant details. - The brief should help sales start a relevant business conversation. --------------------------------------------------------------------------------

#025Pain Point Depth Miner

ICP, BUYER PERSONAS & ACCOUNT RESEARCHSales messaging, discovery calls, offer positioning, persona research, and objection handling.

Go beyond surface-level pain points and identify the business, operational, financial, emotional, political, and timing layers behind customer problems.

You are a customer pain analyst. Analyze the target buyer’s pain points deeply enough to improve sales conversations and messaging. Inputs: Target buyer: [BUYER] Target segment: [SEGMENT] Offer: [OFFER] Known pain points: [PAIN POINTS] Current customer notes: [CUSTOMER NOTES] Sales call notes: [SALES CALL NOTES] Objections: [OBJECTIONS] Competitors or alternatives: [ALTERNATIVES] Create a pain depth map: Layer 1 — Surface problem Identify what the buyer says the problem is in simple terms. Layer 2 — Operational problem Explain: - what breaks in their workflow - what slows the team down - what creates rework - what causes confusion - what creates inconsistency Layer 3 — Financial problem Estimate or describe: - cost of the problem - lost revenue - wasted labor - missed opportunities - margin impact - budget leakage - cost of delay Layer 4 — Strategic problem Explain how the pain affects: - growth - competitive position - customer experience - leadership priorities - risk exposure - scalability Layer 5 — Personal and political problem Identify: - who looks bad because of the problem - who is under pressure - who must defend the decision - who may resist change - what internal politics matter Layer 6 — Trigger and urgency Define: - why the pain becomes urgent - what event causes action - what happens if they wait - what makes the buyer prioritize this now Output: - pain hierarchy - strongest sales angles - discovery questions - message hooks - objection connections - proof needed - urgency-building language Rules: - Do not exaggerate pain beyond evidence. - Do not confuse symptoms with root causes. - Do not assume every pain is urgent. - Use buyer language, not internal company language. --------------------------------------------------------------------------------

#026Buying Trigger Detection System

ICP, BUYER PERSONAS & ACCOUNT RESEARCHProspecting, outbound targeting, account scoring, sales timing, trigger-based messaging, and pipeline generation.

Identify the events, changes, signals, and conditions that make a prospect more likely to buy now.

Act as a sales trigger intelligence strategist. Build a buying trigger system for identifying accounts that are more likely to need [OFFER] now. Context: Offer: [OFFER] Target market: [MARKET] Ideal customer profile: [ICP] Buyer roles: [BUYERS] Problem solved: [PROBLEM] Current customers: [CUSTOMERS] Past closed-won triggers: [CLOSED WON TRIGGERS] Past closed-lost reasons: [CLOSED LOST REASONS] Available data sources: [DATA SOURCES] Sales channels: [CHANNELS] Build the trigger system: 1. Trigger categories Identify possible triggers across: - leadership changes - funding events - hiring patterns - expansion - layoffs or restructuring - new product launches - technology changes - regulatory changes - competitor moves - customer growth - negative reviews - operational scaling - new locations - procurement cycles - budget planning windows - content or social signals 2. Trigger qualification For each trigger define: - why it matters - what pain it may create - which buyer cares - urgency level - fit with our offer - false positive risk - data source to monitor - outreach angle 3. Trigger scoring Create a trigger score based on: - recency - relevance - pain strength - account fit - buyer accessibility - budget likelihood - competitive timing 4. Sales plays Build: - trigger-based email - LinkedIn opener - call opener - discovery questions - follow-up angle - proof asset to use 5. Monitoring workflow Create: - weekly trigger review - account list update process - CRM tagging rules - owner assignments - alert thresholds Rules: - Do not treat every company update as a buying trigger. - Do not use triggers without connecting them to business pain. - Do not over-personalize based on weak signals. - Trigger-based outreach should feel timely, not creepy. --------------------------------------------------------------------------------

#027Account Segmentation Matrix Builder

ICP, BUYER PERSONAS & ACCOUNT RESEARCHAccount prioritization, outbound planning, territory planning, ABM, sales focus, and pipeline creation.

Segment target accounts into practical sales categories based on fit, value, urgency, accessibility, and sales effort.

You are an account segmentation strategist. Build a practical account segmentation matrix for my sales team. Inputs: Target account list: [ACCOUNT LIST] ICP criteria: [ICP CRITERIA] Firmographic data: [FIRMOGRAPHIC DATA] Technographic data: [TECH DATA] Buying trigger data: [TRIGGERS] Engagement data: [ENGAGEMENT] Revenue potential: [REVENUE POTENTIAL] Known relationships: [RELATIONSHIPS] Offer: [OFFER] Sales capacity: [CAPACITY] Create segmentation matrix: Axis 1 — Fit Score account fit using: - industry fit - company size fit - pain fit - tech stack fit - maturity fit - geographic fit - offer fit Axis 2 — Value Score value using: - potential deal size - expansion potential - retention potential - strategic logo value - referral potential - margin quality Axis 3 — Timing Score timing using: - buying triggers - budget cycle - recent change - active research signals - urgency indicators - implementation readiness Axis 4 — Accessibility Score access using: - known contacts - buyer visibility - warm intro availability - channel access - outbound reachability - stakeholder clarity Then create account tiers: - Tier A: high-fit, high-value, high-timing - Tier B: high-fit but lower timing - Tier C: good-fit scalable accounts - Tier D: nurture accounts - Tier E: avoid or deprioritize For each tier provide: - sales motion - personalization level - outreach cadence - research depth - asset requirements - owner - success metric Rules: - Do not treat all accounts equally. - Do not overinvest in low-fit accounts. - Do not ignore timing and accessibility. - The segmentation must guide daily sales action. --------------------------------------------------------------------------------

#028Buyer Language Extraction Engine

ICP, BUYER PERSONAS & ACCOUNT RESEARCHSales copy, outreach, discovery, objection handling, landing pages, proposals, and call scripts.

Extract the exact words, phrases, objections, emotional cues, and value language buyers use so sales messaging sounds relevant and natural.

Act as a buyer language analyst. Extract useful sales language from the raw material below. Raw material: [PASTE CALL TRANSCRIPTS, REVIEWS, SURVEYS, EMAILS, CRM NOTES, INTERVIEW NOTES] Context: Offer: [OFFER] Target buyer: [BUYER] Target segment: [SEGMENT] Sales goal: [GOAL] Current messaging: [CURRENT MESSAGING] Extract and organize buyer language: A. Pain language Find phrases buyers use to describe: - frustrations - inefficiencies - risks - delays - costs - confusion - broken processes - missed opportunities B. Outcome language Find phrases buyers use to describe: - desired results - success - speed - confidence - simplicity - control - growth - peace of mind C. Objection language Find phrases buyers use when they worry about: - price - timing - complexity - implementation - trust - switching - internal approval - competing priorities D. Trigger language Find phrases that reveal: - why now - what changed - what made the problem urgent - who is pushing the decision - what happens if they do nothing E. Message translation Turn the extracted language into: - outreach hooks - cold email lines - discovery questions - landing page headlines - proposal phrases - objection responses - follow-up angles F. Language rules Create: - words to use - words to avoid - phrases that feel authentic - phrases that sound too vendor-like - message tone guidance Rules: - Do not rewrite buyer language into corporate jargon. - Do not invent quotes. - Keep exact language in quotation marks only if it appears in the raw material. - If evidence is thin, label the insight as [LOW CONFIDENCE]. --------------------------------------------------------------------------------

#029Prospect Qualification Question Designer

ICP, BUYER PERSONAS & ACCOUNT RESEARCHDiscovery calls, inbound qualification, outbound calls, demos, SDR scripts, and sales process design.

Build qualification questions that reveal fit, urgency, budget, authority, timing, pain, risk, and likelihood to buy without making the call feel robotic.

You are a sales discovery and qualification expert. Create a qualification question set for selling [OFFER] to [TARGET BUYER]. Sales context: Offer: [OFFER] Target buyer: [BUYER] Ideal customer profile: [ICP] Main pain solved: [PAIN] Deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Disqualification criteria: [DISQUALIFICATION] Current discovery process: [CURRENT PROCESS] Common bad-fit customers: [BAD FIT] Common objections: [OBJECTIONS] Build questions in this structure: 1. Opening context questions Create questions that help understand: - role - priorities - current situation - why they are exploring now - what prompted the conversation 2. Pain and impact questions Create questions that reveal: - problem severity - workflow impact - financial impact - team impact - customer impact - cost of inaction 3. Fit questions Create questions that reveal: - use case fit - process fit - tech fit - team readiness - implementation fit - support requirements 4. Buying process questions Create questions that reveal: - decision process - stakeholders - timeline - budget - approval path - procurement steps - competing priorities 5. Commitment questions Create questions that reveal: - urgency - next-step willingness - internal ownership - evaluation criteria - risk concerns 6. Scoring guide For each question provide: - why it matters - strong-fit answer - weak-fit answer - red flag answer - follow-up question Rules: - Do not make the questions sound like an interrogation. - Do not ask budget questions before value is established unless needed for qualification. - Do not ask questions that can be answered by basic research. - The questions should help both buyer and seller decide if there is a real fit. --------------------------------------------------------------------------------

#030Anti-ICP and Bad-Fit Customer Profiler

ICP, BUYER PERSONAS & ACCOUNT RESEARCHQualification, sales focus, churn reduction, margin improvement, customer success alignment, and founder-led sales.

Define which prospects should be avoided because they create low margins, long sales cycles, poor retention, excessive support, or weak product fit.

Act as a bad-fit customer analyst. Help me define our anti-ICP so the sales team stops pursuing accounts that waste time or create poor revenue. Context: Offer: [OFFER] Current customers: [CUSTOMERS] Bad-fit customers: [BAD FIT CUSTOMERS] Churned customers: [CHURNED CUSTOMERS] Low-margin customers: [LOW MARGIN CUSTOMERS] Difficult implementation cases: [DIFFICULT CASES] Support-heavy accounts: [SUPPORT HEAVY ACCOUNTS] Closed-lost reasons: [CLOSED LOST] Refunds or cancellations: [REFUNDS] Sales team complaints: [SALES FEEDBACK] Customer success feedback: [CS FEEDBACK] Analyze bad fit across: A. Company profile Identify patterns in: - industry - size - maturity - budget - geography - business model - team structure - technology stack B. Problem profile Identify accounts where: - the pain is not urgent - the problem is too small - the problem is outside our scope - the buyer misunderstands the problem - the account wants a different solution C. Buying profile Identify warning signs: - no decision-maker access - no budget - unclear timeline - endless research mode - unrealistic expectations - procurement complexity - constant discount pressure D. Delivery profile Identify accounts that create: - excessive customization - high support burden - low adoption - implementation delays - low retention - poor margins - unhappy stakeholders E. Anti-ICP rules Create: - hard disqualification rules - soft warning signs - qualification questions - CRM fields - rep coaching notes - polite disqualification language - alternative recommendation language Rules: - Do not define anti-ICP emotionally. - Use patterns, not one-off bad experiences. - Do not reject accounts only because they are small unless economics support it. - The goal is better focus, not arrogance. --------------------------------------------------------------------------------

#031Buyer Objection Research Map

ICP, BUYER PERSONAS & ACCOUNT RESEARCHObjection handling, discovery improvement, sales enablement, content planning, and persona research.

Research why different buyer personas hesitate, delay, reject, compare, or block a purchase and translate those objections into sales strategy.

You are a buyer objection researcher. Map the objections that different buyer personas may raise before purchasing [OFFER]. Inputs: Offer: [OFFER] Target personas: [PERSONAS] Target segment: [SEGMENT] Known objections: [KNOWN OBJECTIONS] Closed-lost notes: [CLOSED LOST NOTES] Sales call notes: [CALL NOTES] Competitors: [COMPETITORS] Pricing: [PRICING] Implementation requirements: [IMPLEMENTATION] Proof assets: [PROOF] Create the objection map: For each persona, analyze objections in these categories: 1. Value objections - "Why do we need this?" - "Is this important enough?" - "What happens if we wait?" 2. Trust objections - "Can we believe you?" - "Will this work for us?" - "Do you understand our situation?" 3. Price objections - "Is this worth the cost?" - "Can we justify the budget?" - "Is there a cheaper option?" 4. Risk objections - "Will implementation fail?" - "Will our team adopt it?" - "Will this create more work?" 5. Timing objections - "Why now?" - "Can this wait?" - "Do we have capacity?" 6. Political objections - "Who needs to approve?" - "Who might block this?" - "Who owns the outcome?" For every objection provide: - root concern - buyer language - early warning signal - discovery question - proof needed - response angle - asset to use - prevention strategy Rules: - Do not write generic rebuttals. - Do not dismiss objections as excuses. - Do not use pressure tactics. - Strong objection handling should reduce risk and improve buyer confidence. --------------------------------------------------------------------------------

#032Prospect Research Scorecard

ICP, BUYER PERSONAS & ACCOUNT RESEARCHProspecting, SDR workflows, account prioritization, CRM scoring, outbound lists, and lead qualification.

Score prospects using objective criteria so sales teams can decide who deserves research, personalization, outreach, follow-up, or disqualification.

Act as a prospect research and scoring specialist. Build a scorecard that ranks prospects by sales priority. Prospect data: [PASTE PROSPECT OR ACCOUNT DATA] Sales context: Offer: [OFFER] ICP: [ICP] Target buyer: [BUYER] Revenue goal: [GOAL] Average deal size: [DEAL SIZE] Sales motion: [SALES MOTION] Available research sources: [SOURCES] Current qualification rules: [RULES] Create a scorecard with 100 total points: A. Fit score — 30 points Score: - industry fit - company size fit - role fit - use case fit - geographic fit - business model fit B. Pain score — 20 points Score: - likely problem severity - visible pain signals - current inefficiency - urgency evidence - cost of inaction C. Timing score — 15 points Score: - recent trigger - budget cycle - growth event - hiring signal - technology change - leadership change D. Value score — 20 points Score: - deal size potential - expansion potential - retention potential - strategic value - referral potential E. Accessibility score — 15 points Score: - contact availability - warm introduction - buyer visibility - engagement signal - channel reachability Then output: - scoring table - priority tier - recommended next action - personalization angle - research gaps - disqualification notes - CRM field suggestions Rules: - Do not score prospects using vague enthusiasm. - Do not prioritize accounts with high value but no access or timing. - Do not over-score weak signals. - The scorecard should make prospecting decisions faster and more consistent. --------------------------------------------------------------------------------

#033Persona-Specific Value Proposition Builder

ICP, BUYER PERSONAS & ACCOUNT RESEARCHSales messaging, outreach, landing pages, proposals, decks, demos, and persona-specific enablement.

Create tailored value propositions for different buyer personas based on their pains, goals, metrics, objections, and decision role.

You are a persona-based value proposition strategist. Create tailored value propositions for each buyer persona involved in buying [OFFER]. Inputs: Offer: [OFFER] Core outcome: [OUTCOME] Target segment: [SEGMENT] Buyer personas: [PERSONAS] Known pains: [PAINS] Known goals: [GOALS] Objections: [OBJECTIONS] Proof: [PROOF] Competitors: [COMPETITORS] Current messaging: [MESSAGING] For each persona, create a value proposition card: 1. Persona role Define: - role in company - role in buying process - personal success metrics - business priorities - likely influence level 2. Pain and motivation Identify: - top 3 pains - top 3 desired outcomes - cost of inaction - emotional pressure - internal pressure 3. Value proposition Write: - one-sentence value proposition - practical value explanation - financial value explanation - strategic value explanation - personal win for the buyer 4. Proof match Recommend: - case study - metric - testimonial - demo moment - comparison point - risk reducer 5. Sales usage Create: - outreach hook - discovery angle - demo focus - proposal section - follow-up message - objection response Rules: - Do not use the same value proposition for every persona. - Do not make claims without proof. - Do not focus only on company value if the buyer has personal risk. - The value proposition should sound like it was built for that role. --------------------------------------------------------------------------------

#034Buying Journey Research Blueprint

ICP, BUYER PERSONAS & ACCOUNT RESEARCHSales process design, persona research, pipeline strategy, content planning, and buyer enablement.

Research and map how prospects move from problem awareness to vendor selection, internal approval, purchase, onboarding, and expansion.

Act as a buyer journey researcher. Build a research blueprint that explains how my target customers actually buy. Context: Offer: [OFFER] Target customer segment: [SEGMENT] Buyer personas: [PERSONAS] Current sales process: [SALES PROCESS] Current assumptions: [ASSUMPTIONS] Known closed-won notes: [CLOSED WON NOTES] Known closed-lost notes: [CLOSED LOST NOTES] Sales cycle: [SALES CYCLE] Deal size: [DEAL SIZE] Research and map the journey: Stage 1: Status quo Answer: - what problem exists - why they tolerate it - what makes it easy to ignore - who notices it first - what language they use Stage 2: Trigger Answer: - what changes - why the issue becomes urgent - who pushes action - what deadlines or consequences appear Stage 3: Exploration Answer: - what they search for - who they ask - what categories they compare - what information they trust - what confusion exists Stage 4: Evaluation Answer: - what vendors they compare - what criteria matter - who influences evaluation - what proof they need - what objections emerge Stage 5: Internal approval Answer: - who must approve - what business case is needed - what risks must be reduced - what procurement steps happen Stage 6: Purchase and implementation Answer: - what makes them commit - what causes delay - what onboarding concerns exist - what success must look like early Output: - buyer journey map - key questions by stage - content needed by stage - sales actions by stage - stakeholder involvement by stage - deal risks by stage - research gaps to validate Rules: - Do not assume buyers follow a linear journey. - Do not ignore internal approval. - Do not map only what sales does. - Use [NEEDS CUSTOMER INTERVIEWS] where evidence is missing. --------------------------------------------------------------------------------

#035Closed-Won Customer Pattern Analyzer

ICP, BUYER PERSONAS & ACCOUNT RESEARCHICP refinement, account scoring, sales strategy, outbound targeting, and win-rate improvement.

Identify the patterns behind won customers so sales can understand what high-probability accounts, buyers, triggers, and messages look like.

You are a closed-won analysis expert. Analyze our successful customers and identify the patterns that should guide future sales targeting. Closed-won data: [PASTE CLOSED-WON CUSTOMER DATA] Additional context: Offer: [OFFER] Sales cycle: [SALES CYCLE] Deal size range: [DEAL SIZE] Sales channels: [CHANNELS] Sales team notes: [NOTES] Customer success notes: [CS NOTES] Expansion data: [EXPANSION] Retention data: [RETENTION] Analyze patterns across: A. Account characteristics Find patterns in: - industry - company size - geography - maturity - business model - team structure - technology stack - funding or growth stage B. Buyer characteristics Find patterns in: - buyer role - seniority - department - decision power - personal goals - communication style - urgency level C. Trigger patterns Find: - events before buying - internal changes - external pressure - growth signals - budget timing - competitive pressure D. Sales process patterns Analyze: - source channel - first message angle - discovery themes - objections - proof used - stakeholders involved - time to close - discounting - next-step behavior E. Outcome patterns Analyze: - retention - expansion - satisfaction - support burden - profitability - referral behavior Output: - ideal closed-won pattern - strongest ICP signals - strongest buyer signals - strongest trigger signals - account scoring recommendations - messaging recommendations - qualification rules - risks of overgeneralizing Rules: - Do not build strategy from one outlier win. - Do not ignore retention after the sale. - Do not confuse correlation with causation. - Use confidence levels for each pattern. --------------------------------------------------------------------------------

#036Closed-Lost and No-Decision Pattern Analyzer

ICP, BUYER PERSONAS & ACCOUNT RESEARCHWin-loss analysis, objection research, sales process improvement, ICP refinement, and forecast accuracy.

Understand why deals are lost, delayed, ghosted, or end in no decision and convert those patterns into better qualification and sales strategy.

Act as a win-loss research analyst. Analyze closed-lost and no-decision deals to find patterns that should change our prospecting, qualification, messaging, or sales process. Data: Closed-lost deals: [CLOSED LOST DATA] No-decision deals: [NO DECISION DATA] Lost reasons: [LOST REASONS] Sales notes: [SALES NOTES] Call notes: [CALL NOTES] Competitors involved: [COMPETITORS] Deal sizes: [DEAL SIZES] Sales cycle length: [SALES CYCLE] Buyer roles: [BUYER ROLES] Lead sources: [SOURCES] Analyze losses by category: 1. Bad-fit losses Identify patterns where the account should not have been pursued. 2. Weak-urgency losses Identify where the buyer cared but not enough to act. 3. Competitive losses Identify where another solution won and why. 4. Price and budget losses Identify whether price was the real issue or a value communication issue. 5. Process losses Identify internal sales process issues: - poor qualification - weak discovery - no champion - unclear next step - wrong stakeholder - weak business case - slow follow-up 6. Timing losses Identify deals that may re-open later and what trigger would matter. Output: - top loss patterns - root causes - qualification changes - messaging changes - discovery improvements - account targeting changes - follow-up strategy - no-decision recovery plays - CRM loss reason improvements Rules: - Do not accept CRM loss reasons at face value. - Do not blame price without checking value and urgency. - Do not treat no-decision as the same as competitor loss. - Use [NEEDS CALL REVIEW] where notes are too thin. --------------------------------------------------------------------------------

#037Buyer Research Question Bank

ICP, BUYER PERSONAS & ACCOUNT RESEARCHCustomer interviews, ICP research, persona development, sales discovery, market research, and messaging development.

Build a structured research question bank for interviews, surveys, discovery calls, and win-loss analysis.

You are a customer and buyer research strategist. Create a question bank that helps us deeply understand our ideal buyers. Research goal: [RESEARCH GOAL] Context: Offer: [OFFER] Target buyer: [BUYER] Target segment: [SEGMENT] Current assumptions: [ASSUMPTIONS] What we need to learn: [LEARNING GOALS] Research format: [INTERVIEWS / SURVEYS / SALES CALLS / WIN-LOSS] Audience relationship: [CUSTOMER / PROSPECT / LOST DEAL / TARGET ACCOUNT] Create question banks for: A. Role and context Questions about: - responsibilities - priorities - success metrics - team structure - current workflow B. Problem discovery Questions about: - pain points - frequency - severity - root causes - current workarounds - cost of inaction C. Buying triggers Questions about: - what changed - why now - what made the problem urgent - what deadlines exist - who pushed action D. Evaluation process Questions about: - alternatives considered - vendor criteria - trusted sources - decision-makers - budget - approval process E. Objections and risk Questions about: - concerns - blockers - internal resistance - implementation fears - switching costs - proof needed F. Messaging and language Questions about: - words they use - phrases that resonate - messages they dislike - outcomes they value - claims they distrust For each question include: - when to ask it - what it reveals - strong follow-up - signal to listen for Rules: - Do not ask leading questions. - Do not ask questions that force agreement. - Do not ask too many questions in one interview. - The questions should reveal truth, not validate our assumptions. --------------------------------------------------------------------------------

#038Persona-Based Outreach Angle Matrix

ICP, BUYER PERSONAS & ACCOUNT RESEARCHCold email, LinkedIn outreach, account-based sales, outbound messaging, and campaign personalization.

Create outreach angles for each buyer persona based on their pains, triggers, responsibilities, objections, and likely priorities.

Act as a sales messaging strategist. Build an outreach angle matrix for each buyer persona we want to reach. Inputs: Offer: [OFFER] Target segment: [SEGMENT] Buyer personas: [PERSONAS] Known pains: [PAINS] Buying triggers: [TRIGGERS] Objections: [OBJECTIONS] Proof assets: [PROOF] Competitors or alternatives: [ALTERNATIVES] Tone: [TONE] Channel: [EMAIL / LINKEDIN / CALL / MULTI-CHANNEL] Create the matrix: For each persona provide: 1. Persona context - role - likely priority - likely pressure - likely success metric - likely buying influence 2. Pain-based angle - message idea - first line - reason it works - risk of using it 3. Trigger-based angle - trigger - message idea - personalization logic - follow-up question 4. Outcome-based angle - desired result - message idea - proof to mention - CTA 5. Risk-reduction angle - buyer concern - message idea - proof or asset - objection prevention 6. Executive angle - business-level framing - financial or strategic value - concise CTA Then create: - best angle by persona - angle to avoid by persona - 3 subject lines - 3 LinkedIn openers - 3 call openers - follow-up themes Rules: - Do not use the same angle for every persona. - Do not make personalization fake or shallow. - Do not overpromise outcomes. - Outreach should feel relevant before it feels clever. --------------------------------------------------------------------------------

#039Total Addressable Account Universe Mapper

ICP, BUYER PERSONAS & ACCOUNT RESEARCHTAM mapping, account list building, territory planning, outbound strategy, ABM, and market focus.

Build a research plan for identifying the full universe of target accounts, narrowing it into priority tiers, and deciding where sales should focus first.

You are a B2B account universe mapper. Help me define and prioritize the total addressable account universe for selling [OFFER]. Business context: Offer: [OFFER] Target market: [MARKET] Current ICP: [ICP] Geography: [GEOGRAPHY] Industries: [INDUSTRIES] Company size range: [SIZE RANGE] Buyer roles: [BUYERS] Revenue goal: [GOAL] Sales capacity: [CAPACITY] Data sources available: [DATA SOURCES] Competitors: [COMPETITORS] Build the account universe plan: 1. Account universe definition Define: - inclusion criteria - exclusion criteria - required firmographic fields - required technographic fields - required trigger fields - required buyer fields - account data sources 2. Market segmentation Segment accounts by: - industry - size - geography - maturity - technology stack - growth stage - pain likelihood - buying trigger - strategic value 3. Account tiering Create tier logic: - Tier 1: strategic high-value accounts - Tier 2: strong-fit target accounts - Tier 3: scalable outbound accounts - Tier 4: nurture accounts - excluded accounts 4. Research workflow Define: - data fields to collect - enrichment process - quality checks - duplicate handling - account ownership - update cadence 5. Sales activation Create: - outreach approach by tier - personalization depth - expected volume - success metrics - CRM tagging - weekly account review process Rules: - Do not build a list bigger than the team can work. - Do not include accounts that fail basic fit criteria. - Do not confuse TAM with immediate sales focus. - The account universe should support action, not just market sizing. --------------------------------------------------------------------------------

#040Full ICP, Buyer Persona and Account Research Audit

ICP, BUYER PERSONAS & ACCOUNT RESEARCHSales strategy audits, outbound planning, account-based sales, founder-led sales, revenue operations, agencies, and B2B growth teams.

Audit the complete customer targeting system across ICP, personas, account segmentation, buying triggers, stakeholder maps, qualification, messaging, and prospect prioritization.

Act as an independent ICP, buyer persona, and account research auditor. Review my current targeting system and rebuild it into a practical sales research engine. Full context: Company: [COMPANY] Website: [WEBSITE] Offer: [OFFER] Revenue goal: [REVENUE GOAL] Current customers: [CURRENT CUSTOMERS] Best customers: [BEST CUSTOMERS] Worst customers: [WORST CUSTOMERS] Closed-won data: [CLOSED WON] Closed-lost data: [CLOSED LOST] Churned customers: [CHURNED CUSTOMERS] Current ICP: [CURRENT ICP] Current personas: [CURRENT PERSONAS] Target account list: [ACCOUNT LIST] Buyer roles: [BUYER ROLES] Sales channels: [CHANNELS] Sales motion: [SALES MOTION] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Win rate: [WIN RATE] Main objections: [OBJECTIONS] Buying triggers: [TRIGGERS] Customer interview notes: [INTERVIEWS] Sales call notes: [CALL NOTES] CRM fields: [CRM FIELDS] Research tools: [TOOLS] Team capacity: [CAPACITY] Known targeting problems: [PROBLEMS] Audit across 40 dimensions: 1. ICP clarity 2. ICP evidence quality 3. Firmographic fit 4. Technographic fit 5. Problem fit 6. Urgency fit 7. Budget fit 8. Sales cycle fit 9. Retention fit 10. Expansion fit 11. Anti-ICP clarity 12. Segment prioritization 13. Account tiering 14. Account scoring 15. Buyer persona usefulness 16. Buyer role clarity 17. Economic buyer identification 18. Champion identification 19. Influencer mapping 20. Blocker identification 21. Buying committee understanding 22. Pain point depth 23. Trigger event clarity 24. Objection research 25. Decision criteria understanding 26. Procurement and approval understanding 27. Buyer language quality 28. Closed-won pattern analysis 29. Closed-lost pattern analysis 30. No-decision analysis 31. Qualification questions 32. Disqualification rules 33. Prospect research workflow 34. Account research brief quality 35. Outreach personalization logic 36. CRM data quality 37. Research source quality 38. Sales and customer success feedback loop 39. Targeting execution cadence 40. Overall account research maturity For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - revenue impact - risk if ignored - recommended fix - priority - effort - confidence level Then synthesize: A. Hard truth Explain the biggest targeting mistake we are making. B. Ideal customer system Define: - primary ICP - secondary ICP - anti-ICP - highest-priority segment - strongest buyer persona - key buying trigger - main disqualification signal C. Account research system Create: - account scoring model - persona research template - stakeholder map template - trigger monitoring workflow - buyer language extraction process - closed-won and closed-lost review cadence D. Sales activation roadmap Create: - first 24-hour fixes - first 7-day research cleanup - first 30-day targeting plan - first 90-day account research system - owner assignments - CRM updates - metrics to track E. Executive summary Write a direct summary with: - best ICP opportunity - worst-fit segment to stop pursuing - first account research improvement - first persona insight to validate - first qualification rule to add - first trigger to monitor - first CRM field to fix - one operating principle for better targeting Rules: - Do not create decorative personas. - Do not define ICP without evidence. - Do not ignore bad-fit customers. - Use [NEEDS DATA], [NEEDS CUSTOMER INTERVIEWS], [NEEDS CRM CLEANUP], or [NEEDS ACCOUNT RESEARCH] where required. - The final output should make targeting sharper, prospecting easier, and sales conversations more relevant.

#041Lead Generation Operating System Builder

LEAD GENERATION & PROSPECTING SYSTEMSFounders, sales leaders, SDR teams, agencies, B2B SaaS companies, consultants, and teams that need a repeatable prospecting engine.

Build a complete lead generation system that connects ICP focus, lead sources, qualification rules, prospecting channels, ownership, cadence, and revenue targets.

You are a senior lead generation strategist. Build a practical lead generation operating system for my business. Business context: Company: [COMPANY] Website: [WEBSITE] Offer: [OFFER] Target market: [TARGET MARKET] Ideal customer profile: [ICP] Buyer personas: [BUYER PERSONAS] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Revenue target: [REVENUE TARGET] Current lead sources: [CURRENT LEAD SOURCES] Current prospecting process: [CURRENT PROCESS] Sales team size: [TEAM SIZE] Tools available: [TOOLS] CRM: [CRM] Current bottlenecks: [BOTTLENECKS] Lead quality issues: [QUALITY ISSUES] Build the operating system: 1. Lead generation strategy Define: - best-fit lead types - primary lead sources - secondary lead sources - sources to avoid - lead volume target - lead quality target - sales handoff requirements - weekly execution rhythm 2. Prospecting workflow Design the process from: - ICP definition - account sourcing - contact sourcing - trigger research - data enrichment - lead scoring - list QA - outreach assignment - follow-up tracking - pipeline conversion review 3. Qualification rules Create: - fit criteria - disqualification criteria - required account data - required contact data - trigger signals - buyer role requirements - minimum quality threshold 4. Lead source portfolio Evaluate: - LinkedIn - company databases - industry directories - communities - job boards - funding databases - events - webinars - referrals - partners - website intent - content engagement - review sites - competitor mentions 5. Execution plan Create: - first 7-day setup - first 30-day lead generation plan - first 90-day scaling plan - owner assignments - metrics dashboard - QA checklist - reporting cadence Rules: - Do not optimize for lead volume at the expense of fit. - Do not create a system that depends on one channel only. - Do not send leads to sales without clear quality standards. - Use [NEEDS DATA] where assumptions require verification. --------------------------------------------------------------------------------

#042Qualified Prospect Source Map

LEAD GENERATION & PROSPECTING SYSTEMSProspecting strategy, outbound planning, market entry, list building, sales team focus, and channel prioritization.

Identify the best places to find qualified prospects and rank lead sources by fit, accessibility, data quality, buyer relevance, cost, and speed to pipeline.

Act as a prospect sourcing analyst. Create a source map that shows where we can reliably find qualified prospects for [OFFER]. Inputs: Offer: [OFFER] ICP: [ICP] Target industries: [INDUSTRIES] Target geographies: [GEOGRAPHIES] Buyer roles: [BUYER ROLES] Company size range: [SIZE RANGE] Sales motion: [SALES MOTION] Average deal size: [DEAL SIZE] Current lead sources: [CURRENT SOURCES] Available tools: [TOOLS] Budget: [BUDGET] Prospecting capacity: [CAPACITY] Map potential lead sources across these categories: A. Public company sources Include: - company websites - industry directories - association member lists - award lists - conference speaker lists - exhibitor lists - job postings - press releases - local business listings - marketplace profiles B. Professional network sources Include: - LinkedIn search - Sales Navigator - founder networks - investor portfolios - alumni networks - niche communities - Slack groups - newsletters - podcast guest lists C. Intent and trigger sources Include: - hiring signals - funding signals - technology adoption - content engagement - review activity - competitor switching signals - expansion announcements - leadership changes - regulatory changes D. Ranking table For every source score: - ICP fit - buyer visibility - data freshness - contact accessibility - trigger visibility - cost - speed to pipeline - scalability - false positive risk E. Recommendation Provide: - top 5 sources to start with - sources to test later - sources to avoid - weekly sourcing workflow - sample search queries - QA rules - expected output format Rules: - Do not recommend generic sources without explaining why they fit the ICP. - Do not prioritize sources where buyer roles cannot be identified. - Do not confuse available data with qualified demand. - The final source map should guide daily prospecting work. --------------------------------------------------------------------------------

#043Target Account List Builder

LEAD GENERATION & PROSPECTING SYSTEMSABM, outbound campaigns, SDR prospecting, territory planning, founder-led sales, and strategic account selection.

Build a high-quality target account list from ICP criteria, market filters, trigger signals, company data, and sales priorities.

You are a B2B target account list builder. Create a clean, prioritized account list strategy for prospecting. Account list goal: [DESCRIBE ACCOUNT LIST GOAL] Context: Offer: [OFFER] ICP criteria: [ICP CRITERIA] Target industries: [INDUSTRIES] Target geographies: [GEOGRAPHIES] Company size: [COMPANY SIZE] Revenue range: [REVENUE RANGE] Technology criteria: [TECH CRITERIA] Buying triggers: [TRIGGERS] Excluded accounts: [EXCLUSIONS] Competitors: [COMPETITORS] Sales capacity: [CAPACITY] Campaign timeframe: [TIMEFRAME] Data sources available: [DATA SOURCES] Build the account list system: 1. Inclusion criteria Define exactly which accounts should be included based on: - firmographic fit - problem likelihood - budget likelihood - buying trigger - market position - technology fit - geography - strategic value 2. Exclusion criteria Define which accounts should be removed because of: - poor fit - low budget - wrong size - wrong geography - low urgency - bad margin - unsupported use case - existing customer conflict - competitor ownership - legal or compliance restrictions 3. Tiering model Create: - Tier 1 strategic accounts - Tier 2 high-fit accounts - Tier 3 scalable outbound accounts - Tier 4 nurture accounts - rejected accounts For each tier define: - number of accounts - research depth - personalization level - outreach cadence - owner - success metric 4. Account data schema Create required fields: - company name - website - industry - size - location - buyer roles - trigger - fit score - value score - timing score - source - notes - next action 5. QA workflow Create checks for: - duplicates - outdated data - missing website - wrong industry - weak fit - no buyer visibility - no trigger - poor source quality Rules: - Do not build a list bigger than the team can actually work. - Do not include accounts that fail core ICP rules. - Do not rely on one data source without QA. - A good account list should be smaller, cleaner, and more actionable. --------------------------------------------------------------------------------

#044Buying Signal Detection Engine

LEAD GENERATION & PROSPECTING SYSTEMSTrigger-based prospecting, outbound timing, sales intelligence, lead scoring, account monitoring, and pipeline creation.

Create a repeatable system for finding buying signals that indicate a prospect may be ready for outreach now.

Act as a buying signal intelligence analyst. Build a system for detecting accounts that are more likely to need [OFFER] soon. Context: Offer: [OFFER] Problem solved: [PROBLEM] ICP: [ICP] Buyer roles: [BUYER ROLES] Current customers: [CUSTOMERS] Closed-won triggers: [CLOSED WON TRIGGERS] Closed-lost reasons: [CLOSED LOST REASONS] Available monitoring sources: [SOURCES] Prospecting channels: [CHANNELS] Sales team capacity: [CAPACITY] Identify buying signals in these groups: 1. Growth signals Examples may include: - hiring for relevant roles - new locations - funding - product launches - market expansion - increased ad spend - new partnerships 2. Pain signals Examples may include: - negative reviews - support complaints - operational delays - public customer complaints - compliance pressure - hiring for problem-related roles - job posts mentioning broken workflows 3. Change signals Examples may include: - new executive - restructuring - new department - new technology - vendor replacement - merger or acquisition - regulatory change 4. Intent signals Examples may include: - website visits - content downloads - webinar attendance - category research - comparison page visits - review site activity - pricing page visits 5. Competitive signals Examples may include: - competitor dissatisfaction - competitor contract timing - competitor pricing changes - migration conversations - replacement hiring For each signal provide: - what it means - why it matters - buyer pain it suggests - data source - false positive risk - urgency level - outreach angle - qualification question - lead score impact Then create: - signal scoring model - weekly monitoring workflow - CRM tagging system - alert rules - first outreach play - follow-up strategy Rules: - Do not treat weak signals as proof of intent. - Do not mention sensitive signals in a creepy way. - Do not over-personalize from uncertain data. - Buying signals should guide timing, not replace qualification. --------------------------------------------------------------------------------

#045Contact Data Research and Verification SOP

LEAD GENERATION & PROSPECTING SYSTEMSSDR teams, outbound operations, list building, CRM hygiene, sales assistants, and prospecting workflows.

Create a safe, accurate workflow for finding, verifying, organizing, and maintaining contact data for prospecting.

You are a sales data operations specialist. Build a contact data research and verification SOP for my prospecting workflow. Context: Target accounts: [TARGET ACCOUNTS] Buyer roles: [BUYER ROLES] Offer: [OFFER] ICP: [ICP] Tools available: [TOOLS] CRM: [CRM] Email verification tool: [EMAIL TOOL] LinkedIn workflow: [LINKEDIN WORKFLOW] Compliance requirements: [COMPLIANCE] Current data issues: [DATA ISSUES] Team responsible: [TEAM] Create the SOP: A. Contact identification Define how to find: - economic buyers - champions - end users - technical evaluators - finance approvers - procurement contacts - executive sponsors - influencers - blockers B. Data fields required Create a contact data schema: - full name - job title - company - department - seniority - LinkedIn URL - email - phone, if allowed - location - source - confidence level - last verified date - buyer role - notes - opt-out status C. Verification workflow Define steps for: - role verification - company verification - email verification - duplicate detection - title normalization - contact freshness - domain matching - bounced email handling - outdated contact removal D. Compliance and quality rules Create rules for: - permitted sources - consent and opt-out handling - unsubscribe requirements - data minimization - region-specific compliance review - sensitive data avoidance - documentation E. Maintenance cadence Create: - weekly QA - monthly list refresh - bounce review - CRM cleanup - ownership model - escalation process Rules: - Do not scrape or store data in ways that violate applicable rules. - Do not use unverified contacts for high-priority campaigns. - Do not mix personal and business contact data without review. - Use [NEEDS LEGAL REVIEW] where compliance requirements are uncertain. --------------------------------------------------------------------------------

#046Lead Scoring Model Designer

LEAD GENERATION & PROSPECTING SYSTEMSSales operations, inbound qualification, outbound prioritization, CRM scoring, SDR routing, and pipeline quality improvement.

Build a lead scoring model that ranks prospects by fit, pain, timing, engagement, value, accessibility, and likelihood to convert.

Act as a lead scoring architect. Create a practical lead scoring model for prioritizing prospects. Inputs: Offer: [OFFER] ICP: [ICP] Buyer personas: [PERSONAS] Lead sources: [SOURCES] Current leads: [LEADS] Closed-won patterns: [CLOSED WON] Closed-lost patterns: [CLOSED LOST] CRM fields: [CRM FIELDS] Sales motion: [SALES MOTION] Average deal size: [DEAL SIZE] Sales capacity: [CAPACITY] Build a 100-point lead scoring model: 1. Fit score — 30 points Include: - industry fit - company size fit - geography fit - business model fit - technology fit - buyer role fit - use case fit 2. Pain score — 20 points Include: - problem severity - visible pain signal - urgency - cost of inaction - match to our strongest outcome 3. Timing score — 15 points Include: - recent trigger - buying cycle - budget window - active evaluation - implementation readiness 4. Value score — 20 points Include: - potential deal size - expansion potential - retention likelihood - strategic value - margin quality 5. Engagement and access score — 15 points Include: - website engagement - content engagement - reply behavior - warm intro - contact completeness - stakeholder access Define: - score thresholds - lead tiers - routing rules - disqualification rules - fast-track rules - nurture rules - manual review rules - CRM field mapping Then provide: - scoring table - examples of high-score leads - examples of deceptive low-quality leads - calibration process - monthly review cadence Rules: - Do not score engagement higher than fit. - Do not treat all lead sources equally. - Do not create a model that sales cannot understand. - Lead scoring must improve prioritization, not hide uncertainty. --------------------------------------------------------------------------------

#047Prospecting Workflow Automation Blueprint

LEAD GENERATION & PROSPECTING SYSTEMSSales operations, SDR workflows, CRM automation, RevOps, founder-led sales, and scaling outbound systems.

Design a repeatable prospecting workflow that uses automation for research, routing, reminders, enrichment, tracking, and QA without losing personalization or control.

You are a prospecting workflow automation architect. Design an automation blueprint for my lead generation and prospecting process. Workflow context: Current process: [CURRENT PROCESS] Offer: [OFFER] ICP: [ICP] Lead sources: [LEAD SOURCES] Sales channels: [CHANNELS] CRM: [CRM] Enrichment tools: [ENRICHMENT TOOLS] Email tools: [EMAIL TOOLS] LinkedIn tools: [LINKEDIN TOOLS] Data storage: [DATA STORAGE] Team roles: [TEAM ROLES] Compliance requirements: [COMPLIANCE] Manual bottlenecks: [BOTTLENECKS] Automation risks: [RISKS] Design the automation blueprint: A. Workflow stages Map: - source discovery - account capture - contact capture - enrichment - verification - scoring - deduplication - assignment - personalization research - outreach sequence enrollment - follow-up reminders - reply routing - CRM updates - reporting B. Automation suitability For each stage decide: - automate fully - automate partially - keep manual - require human review Explain why. C. Data flow Define: - trigger event - source app - destination app - fields passed - required transformations - error handling - duplicate rules - failure alerts D. QA gates Create checks for: - wrong company - wrong contact - bad email - duplicate lead - poor ICP fit - missing opt-out - weak personalization - invalid routing - sequence mistakes E. Implementation plan Create: - first workflow to automate - tools needed - setup steps - testing checklist - rollout plan - monitoring dashboard - owner assignments Rules: - Do not automate outreach enrollment without data quality checks. - Do not create workflows that hide errors. - Do not automate personalization so much that it becomes fake. - Use [NEEDS LEGAL REVIEW] for compliance-sensitive automation. --------------------------------------------------------------------------------

#048Outbound List Quality Auditor

LEAD GENERATION & PROSPECTING SYSTEMSCold email lists, LinkedIn outbound lists, CRM imports, SDR QA, agency deliverables, and campaign preparation.

Audit a prospecting list for fit, completeness, accuracy, duplicates, risky data, weak signals, poor segmentation, and outreach readiness.

Act as an outbound list quality auditor. Review this prospecting list and determine whether it is ready for outreach. Prospecting list: [PASTE LIST OR DESCRIBE FIELDS] Campaign context: Offer: [OFFER] ICP: [ICP] Buyer personas: [PERSONAS] Campaign goal: [GOAL] Target segment: [SEGMENT] Outreach channel: [CHANNEL] Required fields: [REQUIRED FIELDS] Disqualification rules: [DISQUALIFICATION] Compliance requirements: [COMPLIANCE] Audit the list: 1. Fit quality Check: - industry fit - company size fit - geography fit - buyer role fit - use case fit - account tier - trigger relevance 2. Data completeness Check: - company name - website - contact name - title - email - LinkedIn URL - source - segment - score - personalization note - verification status 3. Data accuracy Check: - duplicate accounts - duplicate contacts - outdated titles - invalid domains - personal emails - generic inboxes - bounced emails - mismatched company/contact - suspicious records 4. Segmentation quality Check whether the list is grouped by: - persona - industry - trigger - company size - pain point - account tier - outreach angle 5. Outreach readiness Classify each record as: - ready - needs research - needs verification - nurture only - reject Output: - list quality score - top issues - recommended fixes - rejected record criteria - segmentation improvements - CRM import checklist - campaign launch decision Rules: - Do not approve a list only because it has many contacts. - Do not send campaigns to unverified or poor-fit records. - Do not ignore compliance and opt-out rules. - A smaller clean list is better than a larger weak list. --------------------------------------------------------------------------------

#049LinkedIn Prospecting System Designer

LEAD GENERATION & PROSPECTING SYSTEMSB2B prospecting, founder-led sales, consultants, SaaS, agencies, SDR teams, and social selling.

Create a LinkedIn prospecting system for finding accounts, identifying buyers, researching signals, prioritizing contacts, and starting relevant conversations.

You are a LinkedIn prospecting strategist. Build a LinkedIn-based lead generation system for [OFFER]. Context: Offer: [OFFER] ICP: [ICP] Target industries: [INDUSTRIES] Target company size: [COMPANY SIZE] Target geographies: [GEOGRAPHIES] Buyer roles: [BUYER ROLES] Sales Navigator access: [YES / NO] Current LinkedIn profile positioning: [PROFILE] Current audience: [AUDIENCE] Outreach limits: [LIMITS] Brand voice: [VOICE] Current results: [RESULTS] Build the system: A. Search strategy Create search filters for: - accounts - buyer roles - seniority - geography - industry - company size - keywords - recent activity - job changes - posted content - mutual connections B. Prospect qualification Define how to evaluate: - company fit - role fit - problem likelihood - trigger signal - activity level - connection path - conversation potential C. Engagement workflow Create: - profile view strategy - follow strategy - comment strategy - connection request strategy - DM strategy - follow-up strategy - content interaction plan D. Message angles Create: - trigger-based opener - content-based opener - mutual-context opener - problem-based opener - resource-sharing opener - referral-style opener E. Daily and weekly cadence Define: - daily search volume - daily engagement targets - connection targets - DM targets - follow-up cadence - CRM logging rules - metrics to track Rules: - Do not pitch immediately without context unless the buyer signal is strong. - Do not use fake familiarity. - Do not optimize for connection volume only. - LinkedIn prospecting should create relevant conversations, not spam. --------------------------------------------------------------------------------

#050Warm Referral Lead Generation System

LEAD GENERATION & PROSPECTING SYSTEMSFounder-led sales, consulting, agencies, high-ticket B2B, early-stage SaaS, professional services, and relationship-based selling.

Build a repeatable system for generating qualified leads through customers, partners, investors, advisors, communities, and personal networks.

Act as a referral lead generation strategist. Build a warm referral system that creates qualified introductions without sounding needy or transactional. Context: Offer: [OFFER] ICP: [ICP] Best customer types: [BEST CUSTOMERS] Existing customers: [CUSTOMERS] Partners: [PARTNERS] Investors/advisors: [ADVISORS] Professional network: [NETWORK] Communities: [COMMUNITIES] Proof assets: [PROOF] Referral history: [REFERRAL HISTORY] Revenue goal: [GOAL] Design the referral system: 1. Referral source map Segment sources into: - current customers - past customers - partners - advisors - investors - peers - vendors - community leaders - newsletter audience - social media audience 2. Referral fit rules Define what makes a good referral: - company profile - buyer role - problem - timing - budget - urgency - relationship strength - introduction quality 3. Ask strategy Create referral asks for: - happy customer - strategic partner - investor or advisor - peer founder - community contact - newsletter subscriber - LinkedIn connection For each ask include: - timing - message - why it works - what to avoid - follow-up timing 4. Introduction workflow Create: - referral brief - intro blurb - qualification questions - handoff process - thank-you message - status update template - referral tracking fields 5. Monthly operating rhythm Define: - referral source review - ask targets - introduction targets - conversion tracking - relationship maintenance - reward or recognition rules Rules: - Do not ask for vague "anyone who might need this" referrals. - Do not make the referrer do the work. - Do not overuse relationships. - The best referral asks are specific, easy, and respectful. --------------------------------------------------------------------------------

#051Event and Conference Prospecting Playbook

LEAD GENERATION & PROSPECTING SYSTEMSB2B sales, event prospecting, conference ROI, field sales, founder networking, sponsorships, and trade show follow-up.

Build a system for finding and converting prospects before, during, and after events, conferences, webinars, trade shows, and industry gatherings.

You are an event prospecting strategist. Create a complete prospecting playbook for [EVENT NAME] or [EVENT TYPE]. Event context: Event: [EVENT] Location or format: [LOCATION / ONLINE] Date: [DATE] Attendee profile: [ATTENDEES] Exhibitors or sponsors: [EXHIBITORS] Speakers: [SPEAKERS] Our offer: [OFFER] ICP: [ICP] Buyer roles: [BUYER ROLES] Sales goal: [GOAL] Team attending: [TEAM] Assets available: [ASSETS] Build the playbook: A. Pre-event prospecting Create: - target account list - speaker prospect list - exhibitor prospect list - attendee research workflow - meeting booking message - LinkedIn engagement plan - email outreach sequence - qualification criteria B. Event-day workflow Create: - conversation opener - qualification questions - note-taking template - follow-up priority tags - meeting routing - demo or asset usage - booth or networking strategy C. Post-event follow-up Create: - same-day follow-up - 48-hour follow-up - 7-day follow-up - content share message - meeting booking CTA - no-response path - nurture path D. Lead scoring Score event leads by: - fit - role - urgency - conversation quality - buying trigger - next-step commitment - relationship strength E. ROI tracking Track: - meetings booked - opportunities created - pipeline value - closed revenue - cost per opportunity - lessons learned Rules: - Do not wait until after the event to start prospecting. - Do not treat badge scans as qualified leads. - Do not send generic post-event messages. - Event prospecting should turn context into relevant conversations. --------------------------------------------------------------------------------

#052Inbound Lead Qualification Router

LEAD GENERATION & PROSPECTING SYSTEMSInbound sales, website leads, demo requests, contact forms, lead routing, SDR workflows, and CRM automation.

Create a system for routing inbound leads based on fit, urgency, intent, source, buyer role, company value, and next best action.

Act as an inbound lead qualification and routing architect. Design a system that routes every inbound lead to the correct next action. Inbound context: Offer: [OFFER] Inbound sources: [SOURCES] Lead forms: [FORMS] Current routing process: [CURRENT ROUTING] CRM: [CRM] Sales team: [TEAM] ICP: [ICP] Buyer personas: [PERSONAS] Revenue goal: [GOAL] Response time target: [RESPONSE TIME] Common bad-fit leads: [BAD FIT] Compliance requirements: [COMPLIANCE] Create the routing system: 1. Lead types Classify inbound leads into: - high-intent demo request - pricing request - content lead - newsletter lead - webinar lead - partner inquiry - support request - job seeker - vendor pitch - bad-fit inquiry - spam 2. Qualification fields Define required fields: - company - website - role - company size - industry - use case - urgency - budget range - source - message - consent status 3. Routing rules Create rules for: - immediate sales follow-up - SDR qualification - founder follow-up - partner team - customer support - nurture sequence - reject/spam - manual review 4. SLA and response playbook Define: - response time by lead type - first response template - qualification questions - meeting booking path - follow-up cadence - escalation rules 5. Measurement Track: - response time - qualification rate - meeting booked rate - opportunity creation rate - win rate by source - disqualification reasons - revenue by lead type Rules: - Do not treat every inbound lead as sales-ready. - Do not delay high-intent leads. - Do not route bad-fit leads to senior sellers. - The system should protect sales time while improving buyer experience. --------------------------------------------------------------------------------

#053Competitor Displacement Prospecting System

LEAD GENERATION & PROSPECTING SYSTEMSCompetitive sales, SaaS prospecting, B2B services, category competition, replacement campaigns, and account-based outbound.

Build a prospecting system for identifying accounts using competing solutions and creating ethical, relevant outreach around switching triggers and unmet needs.

You are a competitive prospecting strategist. Build a competitor displacement lead generation system for [OFFER]. Context: Our offer: [OFFER] Target competitors: [COMPETITORS] ICP: [ICP] Why customers switch: [SWITCH REASONS] Our advantages: [ADVANTAGES] Our weaknesses: [WEAKNESSES] Proof: [PROOF] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Available data sources: [DATA SOURCES] Compliance limits: [LIMITS] Build the system: A. Account identification Find accounts that may use competitors through: - public technology data - case studies - job descriptions - customer logos - reviews - community discussions - integration pages - marketplace listings - procurement posts - migration content engagement B. Switch signal detection Identify signals such as: - negative reviews - hiring around implementation - public complaints - pricing dissatisfaction - contract renewal timing - feature gaps - integration gaps - scaling pain - leadership changes C. Qualification logic Score accounts by: - competitor usage confidence - pain likelihood - switching feasibility - account fit - timing - deal value - risk D. Messaging strategy Create: - non-attack outreach angle - problem-based opener - switching-risk reducer - comparison asset idea - migration offer - discovery questions - proof to use E. Ethics and QA Define: - claims to avoid - competitor statements requiring proof - data sources allowed - tone guidelines - compliance review triggers Rules: - Do not make false claims about competitors. - Do not attack competitors in outreach. - Do not assume competitor usage without evidence. - The strategy should be helpful, credible, and buyer-safe. --------------------------------------------------------------------------------

#054Niche Directory and Database Prospecting Plan

LEAD GENERATION & PROSPECTING SYSTEMSLocal services, B2B prospecting, agencies, SaaS, vertical markets, ecommerce vendors, and industry-specific sales.

Use niche directories, databases, marketplaces, association lists, and public indexes to source qualified accounts with repeatable research rules.

Act as a niche prospecting researcher. Build a lead sourcing plan using directories, databases, marketplaces, and public lists. Target niche: [NICHE] Context: Offer: [OFFER] ICP: [ICP] Target geography: [GEOGRAPHY] Target company type: [COMPANY TYPE] Buyer role: [BUYER ROLE] Required account data: [REQUIRED DATA] Required contact data: [CONTACT DATA] Current sources: [CURRENT SOURCES] Tools available: [TOOLS] Campaign goal: [GOAL] Create the sourcing plan: 1. Source discovery Identify categories of sources: - industry directories - certification databases - association member lists - marketplace listings - government or public registries - event exhibitor lists - vendor directories - review platforms - local business listings - partner ecosystem directories 2. Source evaluation For each source type explain: - why it may contain qualified accounts - what data can be extracted - what data may be missing - how fresh the data may be - false positive risks - compliance considerations - best use case 3. Research workflow Create: - search queries - extraction fields - data normalization rules - duplicate removal rules - account fit check - contact research step - verification step - CRM import format 4. Prioritization Rank accounts by: - niche fit - size signal - specialization - location - buyer visibility - trigger signal - potential value 5. Output Provide: - source list template - account list template - QA checklist - weekly sourcing target - next action process Rules: - Do not scrape sources where terms prohibit it. - Do not assume directory presence equals buying intent. - Do not import unverified data directly into campaigns. - Directory prospecting must be filtered and qualified. --------------------------------------------------------------------------------

#055Job Posting Lead Signal Miner

LEAD GENERATION & PROSPECTING SYSTEMSB2B prospecting, hiring-trigger outreach, SaaS sales, agencies, consultants, HR tech, RevOps, operations, and IT services.

Use job postings to identify accounts with hiring signals that reveal growth, pain, budget, technology changes, operational needs, and potential buying intent.

You are a job posting intelligence analyst. Build a prospecting system that uses job postings to detect relevant sales opportunities. Context: Offer: [OFFER] Problem solved: [PROBLEM] ICP: [ICP] Buyer roles: [BUYER ROLES] Target industries: [INDUSTRIES] Target geographies: [GEOGRAPHIES] Job boards or sources: [SOURCES] Current customer hiring patterns: [PATTERNS] Sales goal: [GOAL] Create the job signal system: A. Relevant job categories Identify job titles that may signal: - growth - operational complexity - new initiative - broken process - technology adoption - compliance need - customer support pressure - revenue expansion - implementation need B. Keyword signal library Create keywords to look for in job descriptions related to: - tools - workflows - pain points - responsibilities - transformation projects - reporting problems - scaling needs - compliance requirements - vendor management - automation C. Signal interpretation For each signal provide: - what it may mean - possible buyer pain - likely stakeholder - outreach relevance - false positive risk - confidence level D. Prospecting workflow Create: - search query examples - account capture process - contact research process - lead score impact - CRM tagging - outreach timing - follow-up cadence E. Messaging Create: - hiring-trigger cold email angle - LinkedIn opener - call opener - discovery question - value hypothesis Rules: - Do not assume a job posting proves budget for our offer. - Do not make the outreach feel like surveillance. - Do not mention sensitive internal assumptions as facts. - Use job postings as context for relevance, not as pressure. --------------------------------------------------------------------------------

#056Website Visitor and Intent Lead System

LEAD GENERATION & PROSPECTING SYSTEMSInbound sales, product-led sales, B2B SaaS, content-led lead generation, demand capture, and RevOps workflows.

Turn website visits, content engagement, form behavior, product usage, and intent signals into prioritized sales follow-up.

Act as an intent-based lead generation strategist. Build a system for converting website and content engagement into qualified sales opportunities. Intent context: Website: [WEBSITE] Offer: [OFFER] ICP: [ICP] Traffic sources: [TRAFFIC SOURCES] Tracked events: [EVENTS] High-intent pages: [HIGH INTENT PAGES] Content assets: [CONTENT ASSETS] Forms: [FORMS] Product usage signals: [USAGE SIGNALS] CRM: [CRM] Analytics tools: [ANALYTICS] Sales team capacity: [CAPACITY] Privacy/compliance requirements: [COMPLIANCE] Build the intent system: 1. Intent signal map Classify signals as: - low intent - medium intent - high intent - urgent intent - non-sales intent Include examples such as: - pricing page visits - demo page visits - comparison page visits - repeat visits - case study views - webinar attendance - calculator usage - content download - trial activation - abandoned form - return visitor from target account 2. Lead scoring Create score weights for: - account fit - buyer role - page intent - engagement depth - recency - frequency - source quality - company value - known trigger 3. Sales action rules Define: - immediate outreach - nurture email - retargeting - SDR research - AE follow-up - founder follow-up - no action - manual review 4. Outreach plays Create: - pricing page follow-up - case study follow-up - webinar follow-up - comparison page follow-up - abandoned demo form follow-up - repeat visitor follow-up 5. Safeguards Define: - privacy-safe language - data quality checks - false positive handling - opt-out respect - compliance review Rules: - Do not make outreach sound like "we saw you visited this page" unless appropriate and compliant. - Do not treat anonymous traffic as qualified demand. - Do not over-alert sales on weak signals. - Intent data should improve timing and relevance. --------------------------------------------------------------------------------

#057Prospecting Cadence and Capacity Planner

LEAD GENERATION & PROSPECTING SYSTEMSSDR teams, founder-led sales, outbound planning, sales management, prospecting discipline, and pipeline creation.

Design a realistic weekly prospecting cadence based on lead sourcing, research time, personalization depth, outreach volume, follow-ups, and sales capacity.

You are a sales execution planner. Build a prospecting cadence that our team can actually follow consistently. Context: Team size: [TEAM SIZE] Roles: [ROLES] Weekly capacity: [WEEKLY CAPACITY] Revenue target: [REVENUE TARGET] Pipeline target: [PIPELINE TARGET] Average deal size: [DEAL SIZE] Expected conversion rates: [CONVERSION RATES] Lead sources: [LEAD SOURCES] Outreach channels: [CHANNELS] Research depth required: [RESEARCH DEPTH] Personalization level: [PERSONALIZATION] Current activity: [CURRENT ACTIVITY] Current bottlenecks: [BOTTLENECKS] Build the cadence: A. Weekly activity model Calculate or estimate: - accounts sourced - accounts researched - contacts found - contacts verified - personalized messages prepared - first touches sent - follow-ups sent - calls made - LinkedIn actions - meetings booked - opportunities expected B. Time allocation Break the week into: - list building - research - data verification - writing/personalization - sending - calling - LinkedIn engagement - follow-up - CRM updates - review and learning C. Cadence design Create: - daily schedule - weekly rhythm - batching rules - follow-up timing - quality control moments - manager review points D. Capacity warning Identify: - unrealistic activity goals - bottlenecks - work that should be automated - work that should be delegated - work that should be reduced - quality risks E. Metrics Define: - input metrics - quality metrics - conversion metrics - pipeline metrics - learning metrics Rules: - Do not create a cadence that assumes unlimited research time. - Do not chase activity volume while ignoring lead quality. - Do not skip follow-up capacity. - Prospecting cadence should be ambitious but operationally possible. --------------------------------------------------------------------------------

#058Multi-Channel Prospecting System

LEAD GENERATION & PROSPECTING SYSTEMSB2B outbound, account-based selling, founder-led sales, SDR teams, high-value deals, and multi-touch prospecting.

Build a coordinated prospecting system across email, LinkedIn, phone, referrals, events, communities, and content engagement.

Act as a multi-channel prospecting strategist. Create a coordinated prospecting system for reaching [BUYER PERSONA] at [TARGET ACCOUNT TYPE]. Context: Offer: [OFFER] ICP: [ICP] Buyer persona: [BUYER PERSONA] Target account type: [ACCOUNT TYPE] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Channels available: [CHANNELS] Brand voice: [VOICE] Proof assets: [PROOF] Team capacity: [CAPACITY] Compliance limits: [COMPLIANCE] Current results: [RESULTS] Design the system: 1. Channel role map Assign a purpose to each channel: - email - LinkedIn connection - LinkedIn comment - LinkedIn DM - phone call - voicemail - referral ask - community interaction - event touchpoint - content retargeting - direct mail, if relevant For each channel define: - best use - worst use - timing - message style - success metric 2. Sequence architecture Create a sequence with: - touch number - channel - timing - message objective - personalization depth - CTA - exit condition 3. Personalization logic Define: - account-level personalization - persona-level personalization - trigger-based personalization - content-based personalization - mutual-context personalization 4. Follow-up rules Create: - reply handling - no-response handling - soft rejection handling - referral handling - wrong-person handling - timing objection handling 5. Optimization plan Define: - test variables - weekly review metrics - improvement cadence - channel kill criteria - scaling criteria Rules: - Do not repeat the same message across channels. - Do not use every channel if the deal size does not justify it. - Do not make the sequence feel robotic. - Each touch should add context, not just ask again. --------------------------------------------------------------------------------

#059Prospecting Dashboard and Reporting System

LEAD GENERATION & PROSPECTING SYSTEMSSales managers, RevOps, SDR teams, founders, outbound reporting, lead generation operations, and weekly pipeline reviews.

Build a dashboard that tracks prospecting volume, quality, conversion, source performance, response patterns, meetings, opportunities, and pipeline contribution.

You are a sales analytics designer. Build a prospecting dashboard that shows whether lead generation is working and what to improve. Context: Offer: [OFFER] ICP: [ICP] Sales channels: [CHANNELS] Lead sources: [SOURCES] Team: [TEAM] CRM: [CRM] Outreach tools: [TOOLS] Revenue goal: [GOAL] Pipeline target: [PIPELINE TARGET] Current metrics: [CURRENT METRICS] Reporting cadence: [CADENCE] Stakeholders: [STAKEHOLDERS] Design the dashboard: A. Source metrics Track: - accounts sourced - contacts sourced - source quality - source cost - source freshness - duplicate rate - fit rate - verification rate B. Activity metrics Track: - first touches - follow-ups - calls - LinkedIn actions - referral asks - accounts worked - contacts worked - sequences started - sequences completed C. Quality metrics Track: - ICP fit score - buyer role fit - trigger presence - personalization quality - bounce rate - wrong-person rate - opt-out rate - spam complaint risk D. Conversion metrics Track: - reply rate - positive reply rate - meeting booked rate - show rate - opportunity creation rate - pipeline created - closed-won revenue - conversion by source - conversion by persona - conversion by message angle E. Management view Create: - weekly dashboard layout - review questions - red flag thresholds - action triggers - owner assignments - data hygiene checklist Rules: - Do not report activity without quality and conversion. - Do not let vanity metrics hide poor pipeline creation. - Do not compare channels without considering lead quality. - The dashboard should tell the team what to do next. --------------------------------------------------------------------------------

#060Full Lead Generation and Prospecting Systems Audit

LEAD GENERATION & PROSPECTING SYSTEMSSales leaders, founders, SDR managers, RevOps teams, agencies, B2B companies, outbound teams, and full prospecting system redesign.

Audit and rebuild the full prospecting system across ICP, lead sources, account lists, contact data, buying signals, scoring, routing, cadence, automation, QA, reporting, and pipeline impact.

Act as an independent lead generation and prospecting systems auditor. Review my current prospecting engine and create a practical roadmap for building predictable qualified pipeline. Full context: Company: [COMPANY] Website: [WEBSITE] Offer: [OFFER] Revenue target: [REVENUE TARGET] Pipeline target: [PIPELINE TARGET] ICP: [ICP] Buyer personas: [BUYER PERSONAS] Target segments: [SEGMENTS] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Current lead sources: [LEAD SOURCES] Current account lists: [ACCOUNT LISTS] Current contact data process: [CONTACT PROCESS] Current tools: [TOOLS] CRM: [CRM] Outreach channels: [CHANNELS] Current prospecting cadence: [CADENCE] Current lead scoring: [SCORING] Current routing process: [ROUTING] Current automation: [AUTOMATION] Current reporting: [REPORTING] Conversion rates: [CONVERSION RATES] Closed-won patterns: [CLOSED WON] Closed-lost patterns: [CLOSED LOST] Main bottlenecks: [BOTTLENECKS] Compliance requirements: [COMPLIANCE] Team capacity: [CAPACITY] Audit across 40 dimensions: 1. ICP clarity 2. Segment focus 3. Lead source strategy 4. Source diversity 5. Source quality 6. Account list quality 7. Account tiering 8. Account scoring 9. Contact data completeness 10. Contact data accuracy 11. Buyer role identification 12. Buying signal detection 13. Trigger monitoring 14. Intent data usage 15. Referral system 16. LinkedIn prospecting 17. Event prospecting 18. Directory sourcing 19. Job posting signal usage 20. Competitor displacement targeting 21. Lead scoring model 22. Disqualification rules 23. Lead routing rules 24. Inbound lead qualification 25. Outbound list QA 26. Personalization workflow 27. Multi-channel sequence design 28. Follow-up discipline 29. Prospecting cadence 30. Team capacity fit 31. CRM hygiene 32. Data enrichment process 33. Duplicate management 34. Compliance controls 35. Automation quality 36. Reporting quality 37. Source-to-pipeline tracking 38. Feedback loop with sales 39. Experiment cadence 40. Overall prospecting maturity For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - pipeline impact - risk if ignored - recommended fix - priority - effort - confidence level Then synthesize: A. Hard truth Explain the biggest weakness in the current prospecting system. B. Prospecting strategy Define: - best lead sources - best target segment - best buyer roles - best buying signals - best prospecting channel mix - lead quality standard - first system to fix C. 90-day roadmap Create: - first 24-hour cleanup - first 7-day setup - first 30-day lead generation system - first 60-day optimization plan - first 90-day scaling plan - owners - dependencies - metrics D. Operating system Create: - weekly sourcing cadence - list QA workflow - lead scoring rules - routing rules - prospecting dashboard - experiment backlog - CRM field requirements - compliance checklist E. Executive summary Write a direct summary with: - fastest qualified pipeline win - highest-risk data issue - first lead source to test - first lead source to stop - first automation to build - first QA gate to add - first metric to clean up - one operating principle for prospecting quality Rules: - Do not recommend more lead volume before fixing lead quality. - Do not ignore compliance or data accuracy. - Do not automate a broken process. - Use [NEEDS DATA], [NEEDS CRM REVIEW], [NEEDS LEGAL REVIEW], or [NEEDS SALES FEEDBACK] where required. - The final output should make prospecting more focused, repeatable, measurable, and tied to pipeline.

#061Cold Email Conversation Starter Builder

COLD OUTREACH & SALES MESSAGINGB2B outbound, founder-led sales, SDR campaigns, agency prospecting, SaaS outreach, consultants, and high-intent account-based campaigns.

Write cold emails that start real sales conversations by connecting a specific buyer problem, relevant trigger, clear value hypothesis, and low-friction CTA.

You are a cold email strategist who writes concise, relevant, non-spammy sales emails. Create a cold email system for reaching [BUYER PERSONA] at [TARGET ACCOUNT TYPE]. Context: Offer: [OFFER] Target buyer: [BUYER PERSONA] Target segment: [SEGMENT] Buyer pain: [PAIN] Buying trigger: [TRIGGER] Company context: [COMPANY CONTEXT] Proof or credibility: [PROOF] Competitor or alternative: [ALTERNATIVE] Desired next step: [CTA] Tone: [TONE] Restrictions: [RESTRICTIONS] Build the cold email in this structure: 1. Relevance line Write 5 opening lines that connect to one of these: - account trigger - role responsibility - industry change - company initiative - likely pain - recent signal - shared context 2. Problem line Write 5 versions that describe the problem without exaggerating or sounding generic. 3. Value hypothesis Write 5 versions that explain how we may help, using cautious language such as: - “teams usually look for…” - “we typically help with…” - “this may be relevant if…” - “the pattern we often see is…” 4. Credibility line Write 5 versions using: - result - customer type - case study - relevant experience - process - specialization 5. CTA Write 8 low-friction CTAs: - interest-based - permission-based - relevance-check - short-call - wrong-person - resource-share - timing-check - problem-validation Then assemble: - 3 complete cold emails under 120 words - 3 shorter versions under 70 words - 3 subject lines - 3 follow-up angles - one version that feels more direct - one version that feels more consultative Rules: - Do not use hype. - Do not pretend to know facts that are only assumptions. - Do not start with “I hope you’re well.” - Do not make the CTA too demanding. - The email should feel like a relevant business note from a real person. --------------------------------------------------------------------------------

#062LinkedIn Connection Message System

COLD OUTREACH & SALES MESSAGINGLinkedIn outbound, social selling, founder-led sales, consultants, agencies, SaaS teams, and relationship-based prospecting.

Create LinkedIn connection messages and first DMs that feel natural, specific, and conversation-first instead of pitch-heavy.

Act as a LinkedIn sales messaging coach. Write a connection and first-message system for reaching prospects without sounding automated. Inputs: Target buyer: [BUYER] Target account type: [ACCOUNT TYPE] Offer: [OFFER] Reason to connect: [REASON] Shared context: [SHARED CONTEXT] Prospect activity: [POST / COMMENT / PROFILE DETAIL] Likely pain: [PAIN] Desired conversation: [CONVERSATION GOAL] Tone: [TONE] Create the LinkedIn messaging system: A. Connection request options Write 10 connection requests: - mutual context version - industry observation version - content appreciation version - role-based version - event-based version - founder-to-founder version - peer learning version - short direct version - non-sales version - curiosity version Each must be under 250 characters. B. First DM options after acceptance Write 8 first DMs: - soft relevance check - useful resource share - question-first approach - trigger-based approach - pain-pattern approach - proof-light approach - permission-based pitch - wrong-person redirect C. Conversation path Create responses for: - “Sure, tell me more” - “Not interested” - “We already have a solution” - “Maybe later” - “Send info” - “Who do you work with?” - no reply after connection D. Personalization rules Give rules for: - what to mention - what not to mention - how to reference posts - how to avoid sounding fake - when to pitch - when to stay conversational Rules: - Do not send a full pitch in the connection request. - Do not flatter in a generic way. - Do not pretend to have read something you did not read. - LinkedIn messaging should create a real conversation before trying to sell. --------------------------------------------------------------------------------

#063Multi-Touch Outreach Sequence Architect

COLD OUTREACH & SALES MESSAGINGSDR teams, outbound campaigns, account-based selling, high-ticket B2B sales, founder-led sales, and sales teams building repeatable cadences.

Design a complete multi-touch outreach sequence across email, LinkedIn, phone, voicemail, and value-add follow-ups.

You are a multi-channel outbound sequence architect. Build a prospecting sequence that earns attention without feeling repetitive. Campaign context: Offer: [OFFER] Target buyer: [BUYER] ICP: [ICP] Primary pain: [PAIN] Buying trigger: [TRIGGER] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Channels available: [CHANNELS] Proof assets: [PROOF] Content assets: [ASSETS] Tone: [TONE] Sequence length: [NUMBER OF TOUCHES] Compliance limits: [COMPLIANCE] Design the sequence: 1. Sequence strategy Define: - main message theme - primary buyer pain - personalization logic - channel role - reason for each touch - exit criteria - success metric 2. Touch-by-touch plan For each touch include: - day - channel - message objective - personalization requirement - message copy - CTA - alternative CTA - when to stop or change path 3. Message variation Create versions for: - busy executive - department manager - technical evaluator - founder - operations leader - revenue leader 4. Follow-up logic Create follow-ups for: - opened but no reply - clicked but no reply - replied with timing objection - replied with wrong-person signal - replied asking for info - connected on LinkedIn but did not respond 5. QA Check the sequence for: - repetition - weak personalization - spam triggers - overlong messages - unclear CTA - excessive pressure - channel mismatch Rules: - Do not repeat the same ask in every touch. - Do not make every message about the seller. - Do not use fake urgency. - Each touch should add a new reason to respond. --------------------------------------------------------------------------------

#064Personalization Angle Generator

COLD OUTREACH & SALES MESSAGINGCold emails, LinkedIn messages, ABM campaigns, founder outreach, SDR research, and high-quality prospecting.

Generate relevant personalization angles for outbound messages using account signals, buyer role, industry context, triggers, and business pain.

Act as an outbound personalization strategist. Turn the prospect information below into useful personalization angles that can start a relevant conversation. Prospect data: Company: [COMPANY] Website: [WEBSITE] Industry: [INDUSTRY] Company size: [SIZE] Target buyer role: [ROLE] Recent trigger: [TRIGGER] Prospect post or public quote: [POST / QUOTE] Job posting signal: [JOB POSTING] Technology signal: [TECH SIGNAL] Growth signal: [GROWTH SIGNAL] Pain signal: [PAIN SIGNAL] Our offer: [OFFER] Our proof: [PROOF] Generate personalization angles in these categories: 1. Account-based angle Connect the message to: - company stage - business model - growth priority - operational complexity - market position 2. Role-based angle Connect the message to: - responsibilities - KPIs - pressure - common problems - decision role 3. Trigger-based angle Connect the message to: - recent change - hiring - expansion - funding - leadership change - product launch - regulation - competitor movement 4. Pain-pattern angle Connect the message to a likely problem, but mark it as a hypothesis. 5. Proof-match angle Connect our credibility to a similar company, use case, or situation. For each angle provide: - message opening line - why it may work - risk of sounding fake - confidence level - best CTA - follow-up angle Then choose: - top 3 safest angles - top 3 strongest angles - angles to avoid - missing research needed Rules: - Do not invent personalization. - Do not mention sensitive assumptions directly. - Do not use personalization that has no connection to the offer. - Better personalization should make the message more relevant, not longer. --------------------------------------------------------------------------------

#065Subject Line and Preview Text Lab

COLD OUTREACH & SALES MESSAGINGCold email campaigns, outbound testing, follow-up sequences, sales email optimization, and deliverability-conscious prospecting.

Create cold email subject lines and preview text combinations that are short, relevant, clear, and aligned with the message.

You are a cold email subject line specialist. Create subject lines and preview text for a sales outreach campaign. Campaign context: Offer: [OFFER] Target buyer: [BUYER] Target segment: [SEGMENT] Pain point: [PAIN] Trigger: [TRIGGER] Email body summary: [EMAIL BODY SUMMARY] Tone: [TONE] Brand style: [BRAND STYLE] Words to avoid: [WORDS TO AVOID] Compliance or deliverability concerns: [CONCERNS] Create subject lines by category: A. Direct subject lines Write 10 subject lines that are clear and specific. B. Problem-based subject lines Write 10 subject lines connected to the buyer’s pain. C. Trigger-based subject lines Write 10 subject lines based on the trigger or timing. D. Curiosity-safe subject lines Write 10 subject lines that create interest without clickbait. E. Personalized subject lines Write 10 subject lines using placeholders: - [company] - [role] - [trigger] - [initiative] - [industry] F. Follow-up subject lines Write 10 subject lines for follow-ups. For each subject line provide: - preview text - best use case - risk level - why it works - spam or clickbait risk - length check Then recommend: - top 5 safest subject lines - top 5 highest-curiosity subject lines - top 5 executive-friendly subject lines - top 3 to test first Rules: - Do not use fake replies such as “Re:” unless it is a real reply. - Do not use misleading urgency. - Do not overpromise in the subject line. - Subject line and email body must match. --------------------------------------------------------------------------------

#066Follow-Up Message Recovery System

COLD OUTREACH & SALES MESSAGINGCold email follow-ups, LinkedIn follow-ups, stalled deals, proposal follow-up, no-response sequences, and sales pipeline recovery.

Write follow-ups that revive conversations, handle silence, add new context, and give prospects easy ways to respond.

Act as a sales follow-up strategist. Write follow-up messages for prospects who have not responded or have gone quiet. Context: Original message: [ORIGINAL MESSAGE] Offer: [OFFER] Target buyer: [BUYER] Prospect context: [CONTEXT] Last interaction: [LAST INTERACTION] Time since last message: [TIME] Likely reason for silence: [REASON] Proof or asset available: [ASSET] Desired next step: [CTA] Tone: [TONE] Create follow-up messages for these situations: 1. No response after first cold email Write: - short nudge - value-add follow-up - question-based follow-up - wrong-person follow-up - breakup-style follow-up 2. Opened but no reply Write: - relevance-check follow-up - problem-specific follow-up - low-friction CTA follow-up 3. Clicked or engaged but no reply Write: - resource-based follow-up - insight-based follow-up - meeting CTA follow-up 4. After a discovery call Write: - summary follow-up - next-step follow-up - stakeholder-forwardable follow-up - urgency follow-up 5. After proposal sent Write: - decision support follow-up - objection surfacing follow-up - stakeholder alignment follow-up - close-date follow-up For each message include: - subject line or opener - body - CTA - why it works - when to send - when not to send Rules: - Do not guilt the buyer. - Do not write “just checking in” without adding value. - Do not create fake urgency. - Follow-up should make responding easier, not more pressured. --------------------------------------------------------------------------------

#067Cold Call Opener and Talk Track Builder

COLD OUTREACH & SALES MESSAGINGSDR teams, founders, outbound calling, appointment setting, B2B prospecting, and call script improvement.

Create cold call openers, permission-based intros, problem statements, qualification questions, objection responses, and next-step asks.

You are a cold call coach. Build a natural call opener and talk track for reaching [BUYER PERSONA]. Call context: Offer: [OFFER] Target buyer: [BUYER] Target account type: [ACCOUNT TYPE] Likely pain: [PAIN] Buying trigger: [TRIGGER] Source of contact: [SOURCE] Proof point: [PROOF] Call goal: [CALL GOAL] Common objections: [OBJECTIONS] Tone: [TONE] Build the call system: A. First 10 seconds Write 8 openers: - permission-based - direct - trigger-based - role-based - problem-based - referral-based - event-based - voicemail-friendly B. Problem framing Write 5 short problem statements that sound conversational. C. Qualification questions Create questions for: - current situation - pain severity - priority - ownership - timing - current solution - decision process D. Objection handling Write responses to: - “Not interested” - “Send me an email” - “We already have a vendor” - “No budget” - “Too busy” - “How did you get my number?” - “Call me later” E. Next-step asks Write CTAs for: - 15-minute call - referral to right person - permission to send resource - follow-up date - qualification call Rules: - Do not make the call sound like a script. - Do not argue with the prospect. - Do not pitch before earning a few seconds of attention. - The goal is a relevant conversation, not a monologue. --------------------------------------------------------------------------------

#068Referral Ask Message Builder

COLD OUTREACH & SALES MESSAGINGReferral sales, founder-led growth, customer referrals, partner introductions, investor/advisor networks, and warm outreach.

Write referral asks that are specific, respectful, easy to forward, and useful for generating warm introductions.

Act as a referral messaging strategist. Create referral ask messages that help me get warm introductions to qualified prospects. Context: My offer: [OFFER] Ideal prospect: [ICP] Target buyer: [BUYER] Reason this buyer benefits: [VALUE] Current relationship with referrer: [RELATIONSHIP] Proof or credibility: [PROOF] Specific target accounts, if any: [TARGET ACCOUNTS] Tone: [TONE] Preferred channel: [EMAIL / LINKEDIN / TEXT] Create referral messages for: 1. Happy customer Write a message asking for introductions without making them feel obligated. 2. Past customer Write a message that reopens the relationship and asks carefully. 3. Partner Write a message that frames mutual value. 4. Investor or advisor Write a concise, high-signal intro request. 5. Peer founder or operator Write a casual but specific ask. 6. Community contact Write a lightweight request that does not feel extractive. Also create: - forwardable intro blurb - shorter forwardable version - “no worries if not” version - follow-up after no reply - thank-you message after intro - update message after meeting - CRM tracking fields Rules: - Do not ask for “anyone who might be interested.” - Do not make the referrer write the explanation. - Do not make the ask too broad. - The easier the referral is to understand, the more likely it is to happen. --------------------------------------------------------------------------------

#069DM Conversation Starter Matrix

COLD OUTREACH & SALES MESSAGINGSocial selling, community-based prospecting, founder outreach, creator partnerships, SaaS sales, agencies, and networking.

Create short direct messages for X, Instagram, Slack, Discord, communities, and private groups that start relevant conversations without pitching too fast.

You are a conversational sales messaging expert. Create DM conversation starters for [PLATFORM] that feel human, useful, and not spammy. Context: Platform: [PLATFORM] Target person: [PERSON] Their context: [CONTEXT] Offer: [OFFER] Reason for outreach: [REASON] Shared community or topic: [SHARED CONTEXT] Their recent post or comment: [POST / COMMENT] Desired conversation: [GOAL] Tone: [TONE] Create DM starters in these styles: A. Community-first Write 5 messages that reference the shared space. B. Post-based Write 5 messages that respond to something they said. C. Question-first Write 5 messages that ask a thoughtful, easy question. D. Helpful resource Write 5 messages that offer something useful without forcing a sale. E. Founder/operator peer Write 5 messages that feel like one builder talking to another. F. Soft sales relevance Write 5 messages that mention the problem lightly and ask permission. For each message include: - when to use it - why it works - risk of sounding salesy - natural next reply - follow-up if they respond positively - follow-up if they do not respond Rules: - Do not send long DMs as a first touch. - Do not pretend to be part of a relationship that does not exist. - Do not pitch immediately in communities where it is inappropriate. - The first DM should open a door, not force a decision. --------------------------------------------------------------------------------

#070Executive Outreach Message Designer

COLD OUTREACH & SALES MESSAGINGCEO, CFO, COO, CRO, VP, founder, enterprise outreach, strategic accounts, and high-ticket B2B sales.

Write concise executive-level outreach that respects time, focuses on strategic outcomes, and avoids junior-level feature pitching.

Act as an executive sales messaging advisor. Write outreach for senior decision-makers who do not have time for generic sales emails. Executive context: Executive role: [ROLE] Target company: [COMPANY] Industry: [INDUSTRY] Strategic priority: [PRIORITY] Likely business pain: [PAIN] Trigger: [TRIGGER] Our offer: [OFFER] Business outcome: [OUTCOME] Proof: [PROOF] Desired CTA: [CTA] Tone: [TONE] Build executive messaging: 1. Executive relevance frame Create 5 short frames based on: - revenue - cost - risk - speed - customer experience - operational leverage - strategic priority 2. Cold email versions Write: - 60-word version - 90-word version - direct version - consultative version - board-level version - referral-to-team version 3. LinkedIn versions Write: - connection request - first DM - follow-up DM - resource-share DM 4. Executive CTA options Create CTAs for: - quick relevance check - referral to right owner - 15-minute executive conversation - permission to send one idea - benchmark discussion 5. Quality review Evaluate each message for: - strategic relevance - brevity - specificity - credibility - no-fluff score - pressure level Rules: - Do not lead with features. - Do not over-explain. - Do not ask for 30 minutes unless the value is clear. - Senior buyers need business relevance fast. --------------------------------------------------------------------------------

#071Objection-Aware Outreach Writer

COLD OUTREACH & SALES MESSAGINGCold outreach, competitive markets, expensive offers, consultative sales, SaaS, agencies, and sales enablement.

Write sales messages that proactively reduce common objections around price, trust, timing, complexity, implementation, and switching risk.

You are an objection-aware sales copywriter. Write outbound messages that reduce buyer hesitation before it becomes a hard objection. Inputs: Offer: [OFFER] Target buyer: [BUYER] Primary pain: [PAIN] Common objections: [OBJECTIONS] Reason buyers hesitate: [HESITATION] Proof: [PROOF] Risk reversal: [RISK REVERSAL] Implementation details: [IMPLEMENTATION] Competitors or alternatives: [ALTERNATIVES] Tone: [TONE] For each objection, create: 1. Objection diagnosis Explain: - root concern - buyer fear - when it appears - what not to say - what proof helps 2. Outreach angle Write: - one cold email opening - one value line - one proof line - one CTA - one follow-up message Create angles for objections such as: - “too expensive” - “bad timing” - “we already have a vendor” - “not a priority” - “too much work to implement” - “not sure this will work for us” - “we tried something like this before” - “need internal approval” 3. Message assembly Build: - 3 full cold emails - 3 LinkedIn DMs - 3 follow-ups - 3 call openers Rules: - Do not sound defensive. - Do not mention objections in a way that creates new doubts. - Do not argue with the buyer. - Good outreach lowers perceived risk while staying concise. --------------------------------------------------------------------------------

#072Industry-Specific Outreach Adapter

COLD OUTREACH & SALES MESSAGINGVertical campaigns, agencies, SaaS, consultants, B2B services, account-based outbound, and segment testing.

Adapt one sales message across multiple industries while preserving the core offer and making each version feel relevant to that industry.

Act as a vertical sales messaging strategist. Adapt this outbound message for multiple industries without making it generic. Base message: [PASTE BASE MESSAGE] Context: Offer: [OFFER] Industries to target: [INDUSTRIES] Buyer role: [BUYER ROLE] Core pain: [CORE PAIN] Core outcome: [CORE OUTCOME] Proof: [PROOF] Tone: [TONE] CTA: [CTA] For each industry create: A. Industry context Identify: - likely business pressure - likely pain expression - likely KPI - likely buying trigger - likely objection - relevant proof angle B. Adapted message Write: - subject line - cold email under 120 words - LinkedIn DM under 500 characters - follow-up under 80 words - call opener C. Messaging notes Explain: - what changed from the base message - why it fits the industry - what to avoid saying - confidence level - research needed D. Comparison table Create a table showing: - industry - pain angle - outcome angle - proof angle - CTA - risk Rules: - Do not simply swap industry names. - Do not use stereotypes about industries. - Do not make unsupported claims. - Adapt the message to how the industry actually experiences the problem. --------------------------------------------------------------------------------

#073Founder-Led Outreach Voice Builder

COLD OUTREACH & SALES MESSAGINGFounder-led sales, early-stage startups, consultants, agencies, solo founders, productized services, and relationship-first outreach.

Write outreach that sounds like a founder or operator, not a scripted SDR, while still being strategic and clear.

You are a founder-led sales writing coach. Help me write outreach that sounds personal, direct, and credible without sounding polished in a fake way. Founder context: Founder background: [BACKGROUND] Company: [COMPANY] Offer: [OFFER] Target buyer: [BUYER] Why this buyer matters: [WHY] Problem we solve: [PROBLEM] What we are learning: [LEARNING] Current traction: [TRACTION] Proof: [PROOF] Tone preferences: [TONE] Words to avoid: [WORDS TO AVOID] Build founder-led outreach: 1. Voice principles Define: - how the founder should sound - how direct to be - how much proof to include - how to mention early-stage status, if relevant - how to ask without sounding needy 2. Message formats Write: - short cold email - longer thoughtful email - LinkedIn connection request - LinkedIn DM - warm intro follow-up - post-engagement DM - reactivation message 3. Founder-specific angles Create versions based on: - “I noticed a pattern” - “I’m talking to people like you” - “We built this because…” - “Curious if this is relevant” - “Could use your perspective” - “This may not be a fit, but…” 4. CTA options Write CTAs for: - feedback call - relevance check - pilot conversation - problem validation - intro to right person 5. Voice QA Check for: - sounding too salesy - sounding too casual - sounding too vague - too much founder story - weak business value Rules: - Do not hide the sales intent completely. - Do not over-polish the founder’s voice. - Do not write like a marketing automation template. - Founder-led outreach should feel honest and specific. --------------------------------------------------------------------------------

#074Value Proposition Message Compression

COLD OUTREACH & SALES MESSAGINGComplex B2B offers, SaaS, agencies, consultants, enterprise sales, technical products, and messaging clarity.

Compress a complex offer into short, clear sales messages for email, DMs, calls, one-liners, subject lines, and follow-ups.

Act as a sales message compression expert. Turn my complex offer into short, clear outreach messages that buyers can understand quickly. Offer context: Offer: [OFFER] Target buyer: [BUYER] Problem solved: [PROBLEM] Current long explanation: [LONG EXPLANATION] Main outcome: [OUTCOME] Differentiator: [DIFFERENTIATOR] Proof: [PROOF] Common confusion: [CONFUSION] Buyer objections: [OBJECTIONS] Compress the message into these formats: 1. One-liners Create: - 5 plain-English versions - 5 outcome-led versions - 5 problem-led versions - 5 executive versions - 5 casual founder versions 2. Cold email value lines Write 10 value lines under 25 words. 3. LinkedIn DM value lines Write 10 value lines under 200 characters. 4. Cold call explanation Write: - 10-second version - 20-second version - 30-second version 5. Follow-up recap Write 5 versions that explain the value after a first conversation. 6. Clarity test For each top message evaluate: - clarity - specificity - buyer relevance - credibility - risk of jargon - risk of overpromising Rules: - Do not use buzzwords unless the buyer uses them. - Do not explain every feature. - Do not make the message clever at the cost of clarity. - The buyer should understand the value in one read. --------------------------------------------------------------------------------

#075Sales Message A/B Test Planner

COLD OUTREACH & SALES MESSAGINGOutbound optimization, SDR teams, cold email campaigns, LinkedIn prospecting, RevOps, and messaging experiments.

Design controlled tests for outreach messages, subject lines, CTAs, personas, value propositions, triggers, and follow-up angles.

You are a sales messaging experimentation strategist. Design A/B tests that improve outbound performance without confusing the results. Campaign context: Offer: [OFFER] Target audience: [AUDIENCE] Channel: [CHANNEL] Current message: [CURRENT MESSAGE] Current metrics: [METRICS] List size: [LIST SIZE] Conversion goal: [GOAL] Testing timeframe: [TIMEFRAME] Variables we want to test: [VARIABLES] Constraints: [CONSTRAINTS] Build the testing plan: A. Hypothesis library Create hypotheses for testing: - subject line - opening line - pain angle - outcome angle - proof line - CTA - message length - personalization type - follow-up timing - buyer persona - trigger angle B. Test design For each test define: - control - variant - audience - sample size guidance - success metric - guardrail metric - duration - confidence requirements - what to keep constant C. Test calendar Create: - first test - second test - third test - tests to delay - tests to avoid D. Results interpretation Explain what to do if: - opens improve but replies do not - replies improve but meetings do not - positive replies improve but fit is poor - unsubscribes increase - results are inconclusive E. Documentation Create: - test log template - decision rules - learning summary template - message library update process Rules: - Do not test too many variables at once. - Do not optimize only for open rate. - Do not declare a winner from tiny samples. - Better messaging should improve qualified conversations, not vanity metrics. --------------------------------------------------------------------------------

#076Call-to-Action Friction Reducer

COLD OUTREACH & SALES MESSAGINGCold emails, LinkedIn messages, DMs, follow-ups, sales sequences, founder outreach, and low-friction prospecting.

Improve outreach CTAs so prospects can respond easily without feeling pressured into a big commitment too early.

Act as a sales CTA optimization specialist. Rewrite my outreach CTAs so they feel easier, clearer, and more appropriate for the buyer’s stage. Current message: [PASTE MESSAGE] Context: Offer: [OFFER] Target buyer: [BUYER] Buyer awareness stage: [AWARENESS STAGE] Relationship stage: [COLD / WARM / ACTIVE DEAL] Desired next step: [NEXT STEP] Current CTA: [CTA] Tone: [TONE] Common buyer resistance: [RESISTANCE] Analyze the CTA: 1. CTA friction diagnosis Identify: - time commitment friction - decision friction - risk friction - relevance uncertainty - unclear next step - too much pressure - too many asks - weak reason to respond 2. CTA alternatives Write CTAs in these categories: - permission-based - relevance-check - wrong-person redirect - interest-check - problem-validation - resource-share - two-option CTA - soft calendar CTA - executive-friendly CTA - no-pressure CTA 3. Channel adaptation Rewrite the CTA for: - cold email - LinkedIn DM - cold call - voicemail - follow-up email - proposal follow-up 4. Recommendation Choose: - best CTA for first touch - best CTA for second touch - best CTA for executive buyer - best CTA for technical buyer - best CTA for warm referral Rules: - Do not ask for a meeting before creating enough relevance. - Do not use vague CTAs like “thoughts?” unless context supports it. - Do not include multiple competing asks. - The CTA should make the next response easy. --------------------------------------------------------------------------------

#077Relevance-First Sales Message Audit

COLD OUTREACH & SALES MESSAGINGCold email QA, LinkedIn message review, outbound campaign cleanup, sales enablement, and messaging improvement.

Audit any sales message for relevance, clarity, personalization, credibility, tone, CTA strength, and spam risk.

You are a strict sales message editor. Audit this outreach message and improve it so it feels more relevant, clear, and human. Message to audit: [PASTE MESSAGE] Context: Offer: [OFFER] Target buyer: [BUYER] Target account type: [ACCOUNT TYPE] Outreach channel: [CHANNEL] Buyer pain: [PAIN] Trigger or personalization: [TRIGGER] Desired CTA: [CTA] Tone: [TONE] Compliance limits: [COMPLIANCE] Audit the message across 12 criteria: 1. Relevance 2. Specificity 3. Buyer focus 4. Pain clarity 5. Value clarity 6. Credibility 7. Personalization quality 8. Brevity 9. Tone 10. CTA strength 11. Spam risk 12. Conversation likelihood For each criterion provide: - score from 1 to 10 - what is working - what is weak - exact fix Then rewrite the message in 5 versions: - minimal edit - more direct - more consultative - more executive-friendly - shorter version under 75 words Also provide: - better subject lines - better opening lines - better CTA options - phrases to remove - final recommendation Rules: - Do not make the message longer unless necessary. - Do not add hype. - Do not add fake personalization. - The improved message should sound like a real person wrote it. --------------------------------------------------------------------------------

#078Warm Outreach Reactivation Message Builder

COLD OUTREACH & SALES MESSAGINGPipeline reactivation, lost deal follow-up, old lead campaigns, renewal conversations, referrals, and warm prospecting.

Write messages to restart conversations with past leads, old opportunities, former customers, inactive contacts, and previous referrals.

Act as a warm outreach reactivation strategist. Write messages that restart old conversations without sounding awkward or pushy. Context: Contact type: [PAST LEAD / CLOSED LOST / OLD CUSTOMER / REFERRAL / OLD CONVERSATION] Last interaction: [LAST INTERACTION] Time since last contact: [TIME] Previous interest: [INTEREST] Reason conversation stopped: [REASON] New trigger or update: [UPDATE] Offer: [OFFER] New proof or asset: [PROOF] Desired next step: [CTA] Tone: [TONE] Create reactivation messages for: A. Past lead Write: - casual restart - value-add restart - trigger-based restart - direct relevance check B. Closed-lost opportunity Write: - timing change message - new proof message - problem still relevant message - no-pressure check-in C. Old customer Write: - reconnect message - expansion conversation message - feedback-based message - referral ask message D. Previous referral Write: - thank-you and update - new relevant ask - easy forwardable message E. Stalled conversation Write: - clean follow-up - “should I close the loop?” message - new angle message - wrong-time recovery For each message include: - subject line or opener - body - CTA - when to use - when not to use - personalization note Rules: - Do not pretend the relationship is warmer than it is. - Do not guilt people for not responding. - Do not restart without a reason. - Warm outreach should feel respectful and easy to answer. --------------------------------------------------------------------------------

#079Persona-Based Outreach Sequence Splitter

COLD OUTREACH & SALES MESSAGINGComplex B2B sales, enterprise outreach, multi-stakeholder campaigns, ABM, SaaS, and high-ticket services.

Split one outbound campaign into different message tracks for economic buyers, champions, users, technical evaluators, and procurement roles.

You are a multi-stakeholder sales messaging strategist. Build persona-specific outreach tracks for the same target account type. Campaign context: Offer: [OFFER] Target account type: [ACCOUNT TYPE] Personas involved: [PERSONAS] Core business problem: [PROBLEM] Proof: [PROOF] Sales goal: [GOAL] Outreach channels: [CHANNELS] Sequence length: [LENGTH] Tone: [TONE] Create separate message tracks for: 1. Economic buyer Focus on: - business outcome - financial impact - strategic risk - decision confidence 2. Champion Focus on: - internal problem - personal win - proof they can share - how to build the case 3. End user Focus on: - workflow pain - ease of use - daily improvement - adoption 4. Technical evaluator Focus on: - implementation - integration - security - reliability - technical fit 5. Finance or procurement Focus on: - ROI - risk reduction - terms - cost justification - vendor confidence For each persona create: - first email - LinkedIn DM - follow-up 1 - follow-up 2 - cold call opener - main CTA - asset to send - objection to expect - language to avoid Then provide: - sequence order - who to contact first - when to multi-thread - when to stop - CRM tagging rules Rules: - Do not send the same message to every stakeholder. - Do not bypass the champion carelessly. - Do not overload technical buyers with business fluff. - Multi-stakeholder outreach should respect each person’s role in the decision. --------------------------------------------------------------------------------

#080Full Cold Outreach and Sales Messaging Audit

COLD OUTREACH & SALES MESSAGINGSales teams, founders, SDR managers, agencies, B2B SaaS, consultants, RevOps teams, and anyone improving outbound messaging quality.

Audit and rebuild a complete cold outreach messaging system across email, LinkedIn, DMs, calls, sequences, personalization, subject lines, CTAs, follow-ups, testing, and QA.

Act as an independent cold outreach and sales messaging auditor. Review my current outbound messaging system and rebuild it into a conversation-generating sales messaging engine. Full context: Company: [COMPANY] Website: [WEBSITE] Offer: [OFFER] Target market: [MARKET] ICP: [ICP] Buyer personas: [PERSONAS] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Current cold emails: [COLD EMAILS] Current LinkedIn messages: [LINKEDIN MESSAGES] Current DMs: [DMS] Current call scripts: [CALL SCRIPTS] Current follow-ups: [FOLLOW-UPS] Current subject lines: [SUBJECT LINES] Current CTAs: [CTAS] Current proof assets: [PROOF] Current personalization approach: [PERSONALIZATION] Current sequence: [SEQUENCE] Current metrics: [METRICS] Common objections: [OBJECTIONS] Closed-won insights: [CLOSED WON] Closed-lost insights: [CLOSED LOST] Compliance requirements: [COMPLIANCE] Brand voice: [VOICE] Main messaging problems: [PROBLEMS] Audit across 40 dimensions: 1. ICP-message fit 2. Persona-message fit 3. Relevance 4. Opening line quality 5. Personalization quality 6. Pain clarity 7. Problem specificity 8. Value clarity 9. Proof strength 10. Credibility 11. Brevity 12. Tone 13. Spam risk 14. Subject line quality 15. Preview text quality 16. CTA friction 17. Conversation likelihood 18. Email structure 19. LinkedIn structure 20. DM structure 21. Cold call opener 22. Voicemail quality 23. Follow-up strategy 24. Sequence logic 25. Multi-channel coordination 26. Objection prevention 27. Trigger relevance 28. Industry adaptation 29. Executive messaging 30. Technical buyer messaging 31. Referral ask quality 32. Warm reactivation quality 33. A/B testing discipline 34. Message library organization 35. Compliance safety 36. Deliverability risk 37. CRM tracking 38. Learning loop 39. Sales feedback usage 40. Overall outreach readiness For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - likely performance impact - risk if ignored - recommended fix - priority - effort - confidence level Then synthesize: A. Hard truth Explain the biggest reason my outreach is not starting enough qualified conversations. B. Messaging strategy Define: - strongest message angle - weakest message angle - best persona to target first - best channel to lead with - best proof to use - best CTA style - messages to stop using C. Rebuilt outreach system Create: - improved cold email - improved LinkedIn message - improved DM - improved cold call opener - improved follow-up sequence - improved subject lines - improved CTA bank D. 30-day optimization plan Create: - first 24-hour message cleanup - first 7-day rewrite plan - first 14-day test plan - first 30-day campaign plan - metrics to track - QA checklist - owner assignments E. Executive summary Write a direct summary with: - fastest messaging win - highest-risk message problem - first subject line test - first CTA fix - first sequence change - first personalization rule - first follow-up improvement - one operating principle for cold outreach quality Rules: - Do not make outreach more aggressive just to increase replies. - Do not use fake personalization. - Do not optimize for opens instead of qualified conversations. - Use [NEEDS DATA], [NEEDS SALES FEEDBACK], [NEEDS CUSTOMER LANGUAGE], or [NEEDS COMPLIANCE REVIEW] where required. - The final system should make outreach more relevant, respectful, clear, and effective.

#081Discovery Call Architecture Builder

SALES CALLS, DISCOVERY & QUALIFICATIONFounders, account executives, SDRs, consultants, agencies, SaaS sales teams, B2B services, and anyone who needs more useful sales conversations.

Build a complete discovery call structure that uncovers business pain, buyer context, urgency, fit, decision process, budget logic, risk, and next steps.

You are a senior sales discovery coach. Design a complete discovery call architecture for selling [OFFER] to [BUYER PERSONA]. Sales context: Offer: [OFFER] Target buyer: [BUYER PERSONA] Target account type: [ACCOUNT TYPE] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Main problem solved: [PROBLEM] Current discovery process: [CURRENT PROCESS] Common objections: [OBJECTIONS] Disqualification criteria: [DISQUALIFICATION] Desired next step: [NEXT STEP] Build the call architecture: 1. Pre-call intent Define: - what we must learn - what the buyer must understand - what we should not pitch too early - what would make the call successful - what would make the call a poor use of time 2. Opening structure Create: - warm opener - context-setting statement - agenda confirmation - permission-based question - transition into discovery 3. Discovery sections Design question blocks for: - current situation - pain and problem depth - business impact - urgency and timing - current solution - decision process - stakeholders - budget logic - success criteria - risk and objections - next step commitment 4. Qualification logic For each question block provide: - question - why it matters - strong-fit answer - weak-fit answer - red flag answer - follow-up question 5. Call ending Create: - fit summary - buyer confirmation question - next-step recommendation - calendar-close language - polite disqualification language Rules: - Do not turn the call into an interrogation. - Do not pitch before understanding the buyer’s situation. - Do not ask questions that could be answered from basic research. - The call should help both sides decide whether there is a real fit. --------------------------------------------------------------------------------

#082Pain Discovery Deep-Dive Script

SALES CALLS, DISCOVERY & QUALIFICATIONDiscovery calls, consultative selling, complex B2B sales, enterprise sales, high-ticket offers, and conversion improvement.

Create a call script that moves from surface pain to operational, financial, strategic, emotional, and political impact.

Act as a consultative sales expert. Build a pain discovery script that helps me uncover the real problem behind what the buyer says at first. Inputs: Buyer persona: [BUYER] Target segment: [SEGMENT] Offer: [OFFER] Surface pain: [SURFACE PAIN] Known workflow issues: [WORKFLOW ISSUES] Known business impact: [BUSINESS IMPACT] Common buyer language: [BUYER LANGUAGE] Common objections: [OBJECTIONS] Create a pain discovery flow: A. Surface pain questions Write questions that uncover: - what is happening - when it started - how often it happens - who is affected - what the buyer has already tried B. Operational impact questions Write questions that uncover: - delays - manual work - rework - handoff problems - process gaps - quality issues - internal friction C. Financial impact questions Write questions that uncover: - cost of the problem - lost revenue - wasted time - wasted budget - missed opportunities - margin impact - cost of waiting D. Strategic impact questions Write questions that uncover: - growth limitations - customer experience risk - leadership pressure - market risk - scalability problems - competitive disadvantage E. Personal and political impact questions Write questions that uncover: - who owns the problem - who is under pressure - who may resist change - who needs to support the decision - what failure would mean internally F. Summary language Write 5 ways to summarize the pain back to the buyer in a way that sounds accurate and respectful. Rules: - Do not exaggerate the buyer’s pain. - Do not force a pain if the buyer does not feel one. - Do not ask financial impact questions too aggressively. - The goal is clarity, not pressure. --------------------------------------------------------------------------------

#083Qualification Scorecard for Live Calls

SALES CALLS, DISCOVERY & QUALIFICATIONSDR qualification, AE discovery, inbound demos, outbound calls, CRM notes, and sales process standardization.

Create a practical live-call qualification scorecard that helps sellers assess fit, urgency, authority, need, budget, timing, and next-step commitment.

You are a sales qualification systems designer. Build a live-call qualification scorecard for [OFFER]. Context: Offer: [OFFER] ICP: [ICP] Buyer personas: [PERSONAS] Deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Minimum qualification criteria: [MINIMUM CRITERIA] Current qualification method: [CURRENT METHOD] Bad-fit customer patterns: [BAD FIT] Closed-won patterns: [CLOSED WON] Closed-lost patterns: [CLOSED LOST] Build a 100-point scorecard: 1. Fit score — 20 points Assess: - company fit - role fit - use case fit - industry fit - maturity fit 2. Need score — 20 points Assess: - pain severity - problem frequency - business impact - current workaround - cost of inaction 3. Urgency score — 15 points Assess: - trigger event - timeline - deadline - priority level - consequences of waiting 4. Authority and stakeholders score — 15 points Assess: - decision-maker access - champion strength - stakeholder clarity - internal alignment - approval process 5. Budget and value score — 15 points Assess: - budget availability - value recognition - ROI logic - price sensitivity - funding path 6. Next-step commitment score — 15 points Assess: - specific next step - calendar commitment - buyer ownership - stakeholder involvement - follow-up responsiveness For each score category provide: - questions to ask - positive signals - negative signals - red flags - CRM field - recommended next action Then create: - qualified threshold - nurture threshold - disqualification threshold - manager review threshold Rules: - Do not use the scorecard as a rigid script. - Do not qualify based on enthusiasm alone. - Do not ignore weak next-step commitment. - A qualified lead should have evidence, not just interest. --------------------------------------------------------------------------------

#084Urgency and Timing Detector

SALES CALLS, DISCOVERY & QUALIFICATIONDiscovery calls, pipeline quality, forecast accuracy, qualification, sales coaching, and reducing no-decision deals.

Help sellers understand whether the buyer has real urgency, artificial curiosity, future interest, or no current reason to act.

Act as a sales urgency analyst. Create a discovery system that reveals whether a prospect has a real reason to act now. Inputs: Offer: [OFFER] Buyer persona: [BUYER] Problem solved: [PROBLEM] Typical trigger events: [TRIGGERS] Typical sales cycle: [SALES CYCLE] Common no-decision reasons: [NO DECISION REASONS] Current call notes: [CALL NOTES] Build the urgency detector: A. Timing questions Create questions that uncover: - why the buyer is looking now - what changed recently - what deadline exists - what happens if they wait - who is pushing the issue - whether this is a funded initiative - what else competes for attention B. Urgency signals Classify signals into: - urgent - active but not urgent - exploratory - future nurture - no real urgency For each signal provide: - what it sounds like - what it means - what to ask next - likely sales action C. False urgency patterns Identify phrases that may sound urgent but are weak, such as: - “just exploring” - “maybe next quarter” - “we are interested” - “send information” - “we need to think about it” Explain how to test each one. D. Urgency-building without pressure Create ways to help the buyer clarify: - cost of delay - business impact - missed opportunity - internal timeline - next decision milestone E. Next-step recommendation Recommend what to do when urgency is: - strong - medium - weak - unclear - absent Rules: - Do not create fake urgency. - Do not pressure buyers who are not ready. - Do not forecast deals with weak timing as likely to close soon. - Real urgency must be tied to business consequences. --------------------------------------------------------------------------------

#085Budget and Value Conversation Guide

SALES CALLS, DISCOVERY & QUALIFICATIONDiscovery calls, high-ticket sales, SaaS demos, consulting sales, proposal preparation, and price objection prevention.

Help sellers discuss budget, pricing, value, ROI, and financial fit without sounding awkward, premature, or defensive.

You are a sales coach specializing in budget and value conversations. Build a natural budget discovery guide for [OFFER]. Context: Offer: [OFFER] Price range: [PRICE RANGE] Target buyer: [BUYER] Average deal size: [DEAL SIZE] Main business outcome: [OUTCOME] Common price objections: [PRICE OBJECTIONS] Typical budget owner: [BUDGET OWNER] Current budget question: [CURRENT QUESTION] Design the guide: 1. Value-first setup Write ways to introduce budget only after understanding: - problem impact - priority level - desired outcome - decision timeline - business value 2. Budget discovery questions Create questions for: - existing budget - budget owner - budget timing - approval threshold - previous spend - cost of current problem - value expectations - financial decision criteria 3. Price anchoring language Write language for: - giving a range - checking fit - explaining value - avoiding sticker shock - comparing cost to inaction - connecting price to business outcome 4. Red flag answers Identify what it means when the buyer says: - “we have no budget” - “that seems expensive” - “send pricing first” - “we need the cheapest option” - “budget is not the issue” - “we need approval” 5. Follow-up paths Create next-step language for: - strong budget fit - uncertain budget - low budget - wrong budget owner - budget not approved yet Rules: - Do not ask budget questions before creating relevance. - Do not hide pricing if the buyer needs it to qualify. - Do not defend price aggressively. - Budget conversation should clarify fit and value. --------------------------------------------------------------------------------

#086Decision Process Mapping Script

SALES CALLS, DISCOVERY & QUALIFICATIONComplex B2B sales, enterprise deals, stakeholder mapping, forecast accuracy, procurement-heavy sales, and deal progression.

Reveal how a buyer actually makes decisions, who is involved, what approvals are required, and where deals may get stuck.

Act as a decision-process discovery expert. Build a script that helps me understand how this prospect will evaluate, approve, and purchase [OFFER]. Inputs: Offer: [OFFER] Target account type: [ACCOUNT TYPE] Buyer role: [BUYER ROLE] Deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Known stakeholders: [STAKEHOLDERS] Current deal stage: [DEAL STAGE] Procurement complexity: [PROCUREMENT] Common deal delays: [DELAYS] Create the decision process map: A. Decision discovery questions Write questions that uncover: - who is involved - who owns the problem - who signs off - who controls budget - who can block the decision - who will use the solution - who evaluates technical fit - who handles legal/procurement - what approval steps exist B. Evaluation criteria questions Write questions that uncover: - must-have criteria - nice-to-have criteria - risk concerns - competitor comparisons - success requirements - internal business case needs C. Timeline questions Write questions that uncover: - target decision date - implementation date - internal deadlines - meeting dates - procurement timing - budget cycle D. Stakeholder map output Create a table with: - stakeholder - role in decision - influence level - likely concern - proof needed - seller action - missing access risk E. Deal progression plan Recommend: - who to meet next - what asset to send - what question to ask - what approval step to confirm - what risk to reduce Rules: - Do not accept “I’m the decision-maker” without understanding the full process. - Do not skip procurement or finance if they are involved. - Do not forecast without decision process evidence. - Decision clarity is part of qualification. --------------------------------------------------------------------------------

#087Poor-Fit Prospect Detection System

SALES CALLS, DISCOVERY & QUALIFICATIONQualification, sales efficiency, customer success alignment, consulting, agencies, SaaS, and high-touch sales.

Help sellers identify bad-fit prospects early before they consume time, require excessive customization, discount heavily, churn, or create delivery problems.

You are a sales qualification and disqualification strategist. Build a poor-fit detection system for discovery calls. Context: Offer: [OFFER] Ideal customer profile: [ICP] Anti-ICP: [ANTI-ICP] Bad-fit customer examples: [BAD-FIT EXAMPLES] Churned customer patterns: [CHURN PATTERNS] Support-heavy customers: [SUPPORT PATTERNS] Delivery constraints: [CONSTRAINTS] Common red flags: [RED FLAGS] Build the system: 1. Bad-fit categories Identify red flags across: - company fit - problem fit - urgency - budget - expectations - decision process - implementation readiness - values and behavior - support requirements - customization requests - discount pressure 2. Detection questions Create questions that reveal: - unrealistic expectations - low urgency - poor internal ownership - no budget - weak problem fit - unsupported use case - excessive complexity - poor adoption potential 3. Red flag interpretation For each red flag provide: - what it sounds like - why it matters - severity level - follow-up question - disqualification rule - possible nurture path 4. Polite disqualification language Write: - soft no-fit response - not-now response - referral to another solution - nurture offer - expectation reset - scope clarification 5. CRM and handoff rules Create: - disqualification reasons - notes to capture - follow-up timing - nurture category - escalation rule Rules: - Do not disqualify based on assumptions alone. - Do not shame the prospect. - Do not continue deals that cannot succeed. - Good qualification protects both the seller and the buyer. --------------------------------------------------------------------------------

#088Discovery Call Agenda and Opening Script

SALES CALLS, DISCOVERY & QUALIFICATIONDiscovery calls, demo calls, consultation calls, inbound sales, outbound sales, and founder-led sales.

Create a clear call opening that sets expectations, earns permission, frames the agenda, and makes the buyer comfortable sharing useful context.

Act as a sales call opening coach. Create an opening structure that makes discovery calls focused, respectful, and productive. Call context: Call type: [DISCOVERY / DEMO / CONSULTATION / QUALIFICATION] Offer: [OFFER] Buyer persona: [BUYER] How the call was booked: [SOURCE] Buyer’s stated interest: [INTEREST] Expected call length: [LENGTH] Desired outcome: [OUTCOME] Tone: [TONE] Create opening scripts for: A. Standard discovery call Include: - greeting - appreciation - agenda - permission - buyer-first question - transition B. Inbound demo request Include: - why they booked - what they hope to see - context before demo - qualification setup C. Outbound booked meeting Include: - reminder of why you reached out - relevance statement - permission to ask questions D. Executive call Include: - concise agenda - strategic relevance - time respect - decision-focused setup E. Consultative call Include: - expectation setting - no-pressure framing - diagnostic approach - next-step clarity Also create: - 10 agenda options - 10 opening questions - 5 ways to reset if the buyer wants to jump straight to pricing - 5 ways to reset if the buyer wants to jump straight to demo Rules: - Do not make the opening too long. - Do not talk about yourself too much. - Do not hide the purpose of the call. - The opening should create trust and structure quickly. --------------------------------------------------------------------------------

#089Discovery Question Ladder

SALES CALLS, DISCOVERY & QUALIFICATIONSales calls, discovery coaching, SDR qualification, consultative selling, and improving conversation flow.

Build a question sequence that starts broad, narrows into specifics, tests impact, confirms urgency, and leads to a clear next step.

You are a discovery question designer. Create a question ladder that guides a sales conversation from context to commitment. Inputs: Offer: [OFFER] Buyer: [BUYER] Problem area: [PROBLEM AREA] Desired outcome: [OUTCOME] Sales stage: [STAGE] Known information: [KNOWN INFO] Unknowns: [UNKNOWNS] Build the ladder: Level 1 — Context questions Create questions that reveal: - role - current situation - priorities - current process - reason for conversation Level 2 — Problem questions Create questions that reveal: - pain - frequency - root cause - affected teams - current workaround Level 3 — Impact questions Create questions that reveal: - business cost - operational impact - customer impact - leadership pressure - risk Level 4 — Urgency questions Create questions that reveal: - timing - trigger - consequence of delay - priority against other initiatives Level 5 — Decision questions Create questions that reveal: - stakeholders - criteria - budget - process - approval path Level 6 — Commitment questions Create questions that reveal: - willingness to act - next step ownership - timeline - internal alignment For each question provide: - when to ask - what answer to listen for - follow-up question - red flag - how to transition to next level Rules: - Do not ask all questions mechanically. - Do not jump to decision questions before pain is understood. - Do not assume the buyer is ready to buy because they booked a call. - The ladder should create a natural conversation. --------------------------------------------------------------------------------

#090Call Note Taking and CRM Summary Generator

SALES CALLS, DISCOVERY & QUALIFICATIONSales reps, sales managers, RevOps, CRM hygiene, pipeline reviews, call coaching, and post-call follow-up.

Turn messy call notes into clean CRM summaries, qualification scores, next steps, risks, follow-ups, and deal recommendations.

Act as a sales call analyst. Turn the raw call notes below into a clean CRM-ready summary and next-step plan. Raw call notes: [PASTE CALL NOTES OR TRANSCRIPT] Sales context: Offer: [OFFER] Buyer persona: [BUYER] Account: [ACCOUNT] Deal stage: [STAGE] Sales process: [PROCESS] Qualification criteria: [CRITERIA] Next-step goal: [GOAL] Create the call summary: 1. Account and buyer context Summarize: - company situation - buyer role - stated priorities - current process - current tools or vendors - reason for conversation 2. Pain and impact Extract: - main pain - root cause - business impact - operational impact - urgency - cost of inaction 3. Qualification status Assess: - fit - need - urgency - authority - budget - timeline - decision process - next-step commitment 4. Stakeholders and decision process Identify: - known stakeholders - missing stakeholders - approvers - blockers - champion strength - procurement steps 5. Deal risks Flag: - weak urgency - unclear budget - no decision-maker - weak pain - competitor risk - timing risk - implementation risk - poor fit 6. Follow-up plan Create: - follow-up email - next meeting agenda - questions to ask next - asset to send - CRM fields to update - manager review notes Rules: - Do not invent missing information. - Use [NOT DISCUSSED] where the call did not cover something. - Do not overstate deal quality. - The summary should be useful for both the seller and sales manager. --------------------------------------------------------------------------------

#091Discovery Call Follow-Up Email Writer

SALES CALLS, DISCOVERY & QUALIFICATIONAEs, founders, consultants, agencies, SaaS sales, discovery calls, demo follow-ups, and proposal preparation.

Write follow-up emails after discovery calls that summarize the buyer’s situation, confirm next steps, reduce risk, and move the deal forward.

You are a sales follow-up writer. Write a clear follow-up email after a discovery call that feels specific, useful, and action-oriented. Call context: Buyer name: [BUYER NAME] Company: [COMPANY] Offer: [OFFER] Call notes: [CALL NOTES] Pain discussed: [PAIN] Business impact: [IMPACT] Buyer goals: [GOALS] Objections or concerns: [CONCERNS] Decision process: [DECISION PROCESS] Agreed next step: [NEXT STEP] Asset to include: [ASSET] Tone: [TONE] Write follow-up email versions: A. Standard recap Include: - thank-you - concise summary - key pain - desired outcome - agreed next step - date/time - resource link B. Executive-forwardable recap Write a version the buyer can forward internally. C. Technical follow-up Write a version focused on implementation, fit, and requirements. D. Business case follow-up Write a version focused on ROI, impact, and decision criteria. E. Unclear next-step recovery Write a version when the call ended without a firm next step. Also create: - subject lines - bullet summary format - next meeting agenda - questions still open - CRM note version Rules: - Do not write a generic thank-you note. - Do not introduce new claims not discussed on the call. - Do not make the email too long. - The follow-up should make the next step easy and obvious. --------------------------------------------------------------------------------

#092Discovery Call Objection Surfacer

SALES CALLS, DISCOVERY & QUALIFICATIONConsultative sales, complex deals, pricing discussions, enterprise sales, proposal preparation, and sales coaching.

Help sellers uncover hidden objections during discovery before they appear late in the sales process.

Act as a sales objection detection coach. Create a discovery process that surfaces concerns early and makes buyers comfortable sharing hesitation. Context: Offer: [OFFER] Target buyer: [BUYER] Common objections: [OBJECTIONS] Typical hidden concerns: [HIDDEN CONCERNS] Deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Decision process: [DECISION PROCESS] Current objection handling issue: [ISSUE] Build the objection surfacing system: A. Permission language Write 8 ways to invite honest concerns without making the buyer defensive. B. Concern discovery questions Create questions for objections related to: - price - timing - trust - implementation - adoption - switching cost - internal approval - competing priorities - vendor comparison - past failed attempts C. Objection interpretation For each objection type identify: - what the buyer may really mean - what to ask next - what proof helps - what response to avoid - whether it is fixable or disqualifying D. Late-stage risk prevention Create questions to ask before: - demo - proposal - legal review - procurement - final decision - implementation handoff E. Buyer-safe response language Write responses that: - acknowledge concern - clarify context - reduce risk - invite next step - avoid pressure Rules: - Do not argue with objections. - Do not wait until proposal stage to ask about concerns. - Do not treat all objections as buying signals. - The buyer should feel safer, not cornered. --------------------------------------------------------------------------------

#093Demo Qualification Gatekeeper

SALES CALLS, DISCOVERY & QUALIFICATIONSaaS demos, sales teams, inbound demo requests, SDR-to-AE handoffs, founder-led calls, and pipeline quality control.

Decide whether a prospect should receive a demo, strategy session, proposal, nurture path, or disqualification based on discovery evidence.

You are a demo qualification gatekeeper. Create a framework to decide whether a prospect is ready for a demo or needs more discovery first. Context: Offer: [OFFER] Demo type: [DEMO TYPE] Buyer persona: [BUYER] ICP: [ICP] Current demo process: [CURRENT PROCESS] Minimum qualification criteria: [CRITERIA] Common demo problems: [PROBLEMS] Sales cycle: [SALES CYCLE] Average deal size: [DEAL SIZE] Build the gatekeeper framework: 1. Demo readiness criteria Define what must be known before demo: - buyer role - problem - use case - urgency - current solution - success criteria - stakeholders - budget range - timeline - decision process 2. Demo-not-ready signals Identify signs such as: - unclear pain - no business impact - wrong persona - no use case - no decision process - no timeline - purely educational interest - poor ICP fit 3. Routing decision Create rules for: - proceed to demo - run deeper discovery - send educational content - route to self-serve - nurture - disqualify - refer elsewhere 4. Demo preparation If qualified, create: - demo focus areas - buyer-specific use cases - proof to show - questions to ask during demo - close for next step 5. SDR-to-AE handoff Create: - handoff notes - required fields - risks - open questions - recommended demo angle Rules: - Do not demo just because the buyer asked. - Do not use demos to replace discovery. - Do not waste AE time on low-fit prospects. - The right demo should feel tailored to a real buying situation. --------------------------------------------------------------------------------

#094Champion Strength Evaluator

SALES CALLS, DISCOVERY & QUALIFICATIONEnterprise sales, complex B2B sales, account management, pipeline reviews, forecast accuracy, and stakeholder strategy.

Help sellers identify whether they have a real internal champion, a friendly contact, a user advocate, or no influence inside the account.

Act as a complex sales strategist. Evaluate whether my contact is a real champion and what I need to do next. Deal context: Account: [ACCOUNT] Offer: [OFFER] Primary contact: [CONTACT] Contact role: [ROLE] Deal stage: [STAGE] Buyer pain: [PAIN] Decision process: [DECISION PROCESS] Stakeholders: [STAKEHOLDERS] Call notes: [CALL NOTES] Next step: [NEXT STEP] Evaluate champion strength: A. Champion criteria Assess whether the contact: - owns the problem - has influence - has access to decision-makers - understands business value - wants change - can explain our value internally - shares internal information - helps navigate stakeholders - commits to next steps - warns us about risks B. Classify the contact Choose one: - true champion - potential champion - friendly coach - interested user - evaluator - blocker - low-influence contact C. Champion test questions Create questions to ask that reveal: - internal influence - decision access - willingness to advocate - stakeholder knowledge - urgency - risk awareness D. Enablement plan If they are a champion, create: - business case support - internal email draft - stakeholder map - proof package - objection handling notes If they are not a champion, create: - multi-threading plan - executive access request - next stakeholder to meet - risk mitigation Rules: - Do not confuse friendliness with influence. - Do not rely on one contact in a complex deal. - Do not ask a weak contact to sell internally without support. - Champion strength should be based on behavior, not enthusiasm. --------------------------------------------------------------------------------

#095Inbound Discovery Triage System

SALES CALLS, DISCOVERY & QUALIFICATIONDemo requests, contact forms, inbound sales, lead routing, SDR teams, SaaS, agencies, and founder-led sales.

Create a fast qualification process for inbound leads that separates urgent buyers, good-fit evaluators, low-fit leads, support requests, and nurture contacts.

You are an inbound sales triage architect. Build a discovery and qualification system for inbound leads. Inbound context: Offer: [OFFER] Inbound form fields: [FORM FIELDS] Lead sources: [SOURCES] ICP: [ICP] Buyer personas: [PERSONAS] Current response process: [PROCESS] Response time goal: [SLA] Common lead types: [LEAD TYPES] Sales team capacity: [CAPACITY] Build the triage system: 1. Inbound lead categories Classify leads into: - urgent high-fit buyer - high-fit evaluator - good-fit but early-stage - low-fit lead - student/researcher - vendor pitch - support request - partner inquiry - spam 2. First-response questions Create short questions to determine: - role - company fit - problem - urgency - timeline - budget logic - decision process - desired outcome 3. Routing rules Create routing for: - immediate call booking - SDR qualification - AE follow-up - founder follow-up - nurture path - self-serve resource - customer support - reject/spam 4. Call script by lead type Write a short discovery flow for: - demo request - pricing request - content lead - referral lead - webinar lead - contact form inquiry 5. Measurement Track: - speed to lead - qualification rate - meeting booked rate - opportunity rate - no-show rate - disqualification reasons - source quality - revenue by lead type Rules: - Do not make high-intent leads wait. - Do not book every inbound lead automatically. - Do not ask too many form questions before human contact. - Triage should protect sales time and improve buyer experience. --------------------------------------------------------------------------------

#096Discovery Call Coaching Scorecard

SALES CALLS, DISCOVERY & QUALIFICATIONSales managers, call reviews, AE coaching, SDR coaching, onboarding, revenue teams, and sales enablement.

Evaluate a sales rep’s discovery call and provide coaching on questions, listening, qualification, control, empathy, next steps, and deal risk.

Act as a sales manager reviewing a discovery call. Score the call and give coaching that will improve future conversations. Call transcript or notes: [PASTE TRANSCRIPT OR NOTES] Sales context: Offer: [OFFER] Buyer persona: [BUYER] Deal stage: [STAGE] Rep goal: [GOAL] Sales methodology, if any: [METHODOLOGY] Qualification criteria: [CRITERIA] Score the call across 15 areas: 1. Preparation 2. Opening and agenda 3. Buyer rapport 4. Question quality 5. Listening 6. Pain discovery 7. Impact discovery 8. Urgency discovery 9. Decision process discovery 10. Budget/value discovery 11. Stakeholder mapping 12. Objection surfacing 13. Qualification judgment 14. Call control 15. Next-step close For each area provide: - score from 1 to 10 - evidence from the call - what was strong - what was missed - coaching note - better question or phrase Then provide: - top 3 strengths - top 3 improvement areas - missed red flags - missed opportunities - better call path - recommended next step for the deal - rep practice assignment Rules: - Do not give vague praise. - Do not coach everything at once. - Do not assume facts not present in the call. - Coaching should be specific, behavior-based, and useful. --------------------------------------------------------------------------------

#097Next-Step Commitment Closer

SALES CALLS, DISCOVERY & QUALIFICATIONDiscovery calls, demos, proposal calls, consultative sales, SDR handoffs, and pipeline progression.

Help sellers end calls with clear, mutual next steps instead of vague follow-ups, weak promises, or stalled deals.

You are a sales conversation closer focused on clean next steps. Build language that turns discovery calls into clear commitments. Context: Offer: [OFFER] Call type: [CALL TYPE] Buyer persona: [BUYER] Deal stage: [STAGE] What was learned: [CALL LEARNINGS] Buyer interest level: [INTEREST] Known risks: [RISKS] Desired next step: [DESIRED NEXT STEP] Alternative next steps: [ALTERNATIVES] Create next-step closing language: A. Fit confirmation Write phrases to confirm: - the problem - desired outcome - urgency - fit - open concerns - mutual value B. Next-step recommendations Write language for: - scheduling a demo - scheduling a technical review - involving another stakeholder - sending a proposal - building a business case - sharing a case study - running a pilot - disqualifying politely - moving to nurture C. Commitment questions Create questions that test: - real interest - timeline - ownership - stakeholder access - buyer effort - decision process - next-step seriousness D. Calendar-close options Write: - direct version - consultative version - executive version - low-pressure version - multi-stakeholder version E. Weak next-step recovery Write responses when the buyer says: - “send me information” - “we’ll get back to you” - “let’s reconnect later” - “I need to talk internally” - “not sure yet” Rules: - Do not end with vague follow-up. - Do not push for a next step if fit is weak. - Do not treat “send info” as a real next step without clarifying. - A next step should include owner, action, date, and purpose. --------------------------------------------------------------------------------

#098Sales Methodology Customizer

SALES CALLS, DISCOVERY & QUALIFICATIONSales process design, sales training, RevOps, managers, B2B teams, SaaS, enterprise sales, and methodology implementation.

Customize a qualification and discovery approach using frameworks like MEDDICC, BANT, SPICED, Sandler, Challenger, or a lightweight custom model.

Act as a sales methodology consultant. Customize a discovery and qualification framework for my business instead of forcing a generic model. Business context: Offer: [OFFER] Target buyer: [BUYER] Deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Sales motion: [SALES MOTION] Current methodology: [CURRENT METHODOLOGY] Team maturity: [TEAM MATURITY] Pipeline problems: [PIPELINE PROBLEMS] Qualification gaps: [GAPS] CRM requirements: [CRM] Compare these methodologies: - BANT - MEDDICC - SPICED - Sandler - Challenger - GPCT - custom lightweight qualification model For each provide: - fit score - strengths - weaknesses - best use case - risks for our team - questions it would add - CRM fields it requires Then recommend: 1. Best primary framework 2. Elements to borrow from other frameworks 3. Elements to avoid 4. Custom qualification stages 5. Required discovery questions 6. Required CRM fields 7. Coaching plan 8. Adoption plan Create a custom call guide with: - opening - question flow - qualification checkpoints - red flags - next-step rules - manager inspection questions Rules: - Do not force enterprise methodology onto a simple sale. - Do not choose a framework only because it is popular. - Do not create so many fields that reps stop using them. - The methodology should improve deal quality and forecast accuracy. --------------------------------------------------------------------------------

#099Proposal Readiness Checklist

SALES CALLS, DISCOVERY & QUALIFICATIONConsultants, agencies, SaaS, B2B services, enterprise sales, proposal-heavy sales processes, and reducing wasted proposals.

Decide whether a prospect is ready for a proposal by checking pain clarity, value, budget, decision process, stakeholders, timing, success criteria, and risks.

You are a proposal readiness advisor. Determine whether this prospect is ready for a proposal or whether more discovery is needed first. Deal context: Account: [ACCOUNT] Buyer: [BUYER] Offer: [OFFER] Call notes: [CALL NOTES] Pain: [PAIN] Impact: [IMPACT] Urgency: [URGENCY] Budget: [BUDGET] Decision process: [DECISION PROCESS] Stakeholders: [STAKEHOLDERS] Success criteria: [SUCCESS CRITERIA] Known objections: [OBJECTIONS] Desired proposal scope: [SCOPE] Evaluate proposal readiness: 1. Required evidence Check whether we know: - the real problem - business impact - desired outcome - buyer urgency - decision criteria - budget path - decision-maker - approval process - timeline - scope - risk concerns - next step after proposal 2. Readiness score Score from 1 to 100 across: - pain clarity - value clarity - authority clarity - budget clarity - timing clarity - stakeholder alignment - solution fit - next-step commitment 3. Missing discovery List: - unanswered questions - risky assumptions - stakeholders not engaged - budget gaps - decision gaps - scope gaps - proof gaps 4. Recommendation Choose: - send proposal now - send lightweight recap first - schedule deeper discovery - involve another stakeholder - send estimate only - disqualify - nurture 5. If proposal is ready Create: - proposal angle - executive summary - scope emphasis - proof to include - risk reduction section - close plan Rules: - Do not send proposals to unqualified prospects. - Do not use proposals to answer questions that should be handled in conversation. - Do not assume the buyer will sell internally without support. - A proposal should confirm a deal path, not create one from scratch. --------------------------------------------------------------------------------

#100Full Sales Calls, Discovery and Qualification Audit

SALES CALLS, DISCOVERY & QUALIFICATIONSales leaders, founders, SDR managers, AE teams, consultants, agencies, SaaS companies, RevOps, and full sales process improvement.

Audit and rebuild the complete call system across preparation, opening, discovery, pain, urgency, qualification, budget, stakeholders, objections, next steps, CRM notes, and coaching.

Act as an independent sales call, discovery, and qualification auditor. Review my current call process and rebuild it into a stronger system for qualified pipeline and clearer next steps. Full context: Company: [COMPANY] Website: [WEBSITE] Offer: [OFFER] Target market: [MARKET] ICP: [ICP] Buyer personas: [PERSONAS] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Current discovery script: [SCRIPT] Current qualification criteria: [CRITERIA] Current call recordings or notes: [CALL NOTES] Current CRM fields: [CRM FIELDS] Current handoff process: [HANDOFF] Current demo process: [DEMO PROCESS] Current proposal process: [PROPOSAL PROCESS] Current conversion rates: [CONVERSION RATES] Common objections: [OBJECTIONS] Closed-won insights: [CLOSED WON] Closed-lost insights: [CLOSED LOST] No-decision reasons: [NO DECISION] Sales team skill gaps: [SKILL GAPS] Main call problems: [PROBLEMS] Audit across 40 dimensions: 1. Pre-call research 2. Call objective clarity 3. Opening and agenda 4. Buyer rapport 5. Question flow 6. Listening quality 7. Context discovery 8. Pain discovery 9. Root cause discovery 10. Business impact discovery 11. Urgency discovery 12. Timing clarity 13. Current solution discovery 14. Competitor/alternative discovery 15. Budget and value discussion 16. Decision process mapping 17. Stakeholder mapping 18. Economic buyer identification 19. Champion identification 20. Procurement awareness 21. Success criteria discovery 22. Objection surfacing 23. Risk discovery 24. Poor-fit detection 25. Qualification scoring 26. Disqualification discipline 27. Demo readiness 28. Proposal readiness 29. Next-step clarity 30. Calendar commitment 31. Follow-up quality 32. CRM note quality 33. SDR-to-AE handoff 34. Manager coaching 35. Call scorecard 36. Forecast reliability 37. Buyer experience 38. Methodology fit 39. Rep adoption 40. Overall discovery maturity For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - pipeline impact - risk if ignored - recommended fix - priority - effort - confidence level Then synthesize: A. Hard truth Explain the biggest weakness in the current discovery and qualification process. B. Rebuilt call system Create: - improved call opening - improved question flow - improved qualification scorecard - improved red flag list - improved budget discussion - improved decision process map - improved next-step close - improved follow-up format C. Sales team enablement Create: - call preparation checklist - live call cheat sheet - CRM note template - manager coaching scorecard - call review agenda - rep practice drills D. 30-day improvement roadmap Create: - first 24-hour fix - first 7-day call process update - first 14-day coaching plan - first 30-day implementation plan - metrics to track - owner assignments E. Executive summary Write a direct summary with: - fastest call improvement - highest-risk qualification gap - first question to add - first question to remove - first CRM field to fix - first coaching focus - first next-step rule - one operating principle for better discovery Rules: - Do not make the call process longer unless it becomes more useful. - Do not treat interest as qualification. - Do not ignore missing stakeholders or unclear next steps. - Use [NEEDS DATA], [NEEDS CALL REVIEW], [NEEDS CRM REVIEW], or [NEEDS MANAGER COACHING] where required. - The final system should improve call quality, pipeline quality, and forecast confidence.

#101Demo Narrative Blueprint Builder

DEMOS, PRESENTATIONS & VALUE COMMUNICATIONSaaS demos, product walkthroughs, consultative sales calls, founder-led demos, agency presentations, and B2B value communication.

Build a sales demo narrative that connects buyer pain, product moments, proof, business impact, and a clear next step instead of showing random features.

You are a sales demo narrative strategist. Build a buyer-specific demo narrative for presenting [PRODUCT / OFFER] to [BUYER PERSONA]. Context: Product or offer: [PRODUCT / OFFER] Target buyer: [BUYER PERSONA] Target account: [ACCOUNT] Industry: [INDUSTRY] Buyer pain: [PAIN] Current workflow: [CURRENT WORKFLOW] Desired outcome: [OUTCOME] Known objections: [OBJECTIONS] Proof available: [PROOF] Competitors or alternatives: [ALTERNATIVES] Demo length: [DEMO LENGTH] Desired next step: [NEXT STEP] Create the demo blueprint: 1. Demo promise Write a one-sentence promise that explains what the buyer will understand by the end of the demo. 2. Buyer context recap Create a short recap that shows: - what the buyer is trying to improve - why the problem matters - what outcome they care about - what risk they want to avoid 3. Narrative arc Build the demo in this sequence: - current problem - cost of staying the same - better future state - product capability - proof that it works - buyer-specific use case - next step 4. Demo moments Select 5 to 7 product moments and for each explain: - what to show - why it matters - which buyer pain it connects to - what business outcome it supports - what proof to mention - what question to ask after showing it 5. Transition language Write smooth transitions between sections so the demo feels like a story, not a feature tour. 6. Closing sequence Create: - summary of value - confirmation question - objection check - recommended next step - calendar-close language Rules: - Do not show features that are not connected to buyer pain. - Do not start the demo with a product tour. - Do not assume the buyer understands why each feature matters. - Every demo moment must connect to a business outcome. --------------------------------------------------------------------------------

#102Buyer-Specific Product Walkthrough Planner

DEMOS, PRESENTATIONS & VALUE COMMUNICATIONProduct-led sales, demos after discovery, inbound demo requests, account executives, sales engineers, and customer-facing founders.

Prepare a product walkthrough tailored to one buyer role, one use case, one pain point, and one decision stage.

Act as a buyer-specific product walkthrough planner. Turn the information below into a walkthrough that feels custom to the prospect. Inputs: Buyer role: [BUYER ROLE] Buyer seniority: [SENIORITY] Company type: [COMPANY TYPE] Use case: [USE CASE] Problem they mentioned: [PROBLEM] Current process: [CURRENT PROCESS] Decision stage: [DECISION STAGE] Product capabilities: [CAPABILITIES] Features to avoid: [FEATURES TO AVOID] Proof assets: [PROOF ASSETS] Demo environment limitations: [LIMITATIONS] Build the walkthrough: A. Buyer lens Explain: - what this buyer likely cares about - what they do not care about - what they need to see - what they need to believe - what would create confusion B. Walkthrough path Create a step-by-step walkthrough with: - screen or section - talking point - buyer problem addressed - outcome explained - question to ask - risk to avoid C. Role-specific emphasis Adapt the walkthrough for: - economic buyer - daily user - technical evaluator - operations leader - finance approver D. Timing plan Break the demo into: - first 2 minutes - main walkthrough - proof moment - Q&A moment - close E. Personalization checklist List exactly what should be customized before the call. Rules: - Do not show the same walkthrough to every buyer. - Do not over-explain low-value features. - Do not ignore the buyer’s decision stage. - The walkthrough should make the product feel relevant, not just capable. --------------------------------------------------------------------------------

#103Feature-to-Outcome Translation Engine

DEMOS, PRESENTATIONS & VALUE COMMUNICATIONSales demos, sales decks, product marketing, pitch scripts, landing pages, proposal writing, and value communication.

Translate product features into buyer outcomes, business value, emotional relief, risk reduction, and proof-backed messaging.

You are a value communication expert. Translate the features below into clear buyer outcomes that sales can use in demos and presentations. Inputs: Product: [PRODUCT] Target buyer: [BUYER] Target segment: [SEGMENT] Feature list: [FEATURES] Buyer pains: [PAINS] Buyer goals: [GOALS] Business metrics affected: [METRICS] Proof available: [PROOF] Common confusion: [CONFUSION] For each feature create a translation card: 1. Feature name Name the feature in plain English. 2. What it does Explain the feature simply in one sentence. 3. Buyer problem solved Connect the feature to a specific pain. 4. Practical outcome Explain what becomes easier, faster, cleaner, safer, or more reliable. 5. Business outcome Explain the impact on: - revenue - cost - time - productivity - risk - customer experience - visibility - decision-making 6. Emotional outcome Explain how the buyer may feel after the problem is solved: - more confident - less stressed - more in control - less exposed - more credible internally 7. Proof connection Recommend: - metric - case study - testimonial - example - demo moment 8. Demo line Write a sentence the seller can say during the demo. 9. Avoid saying List any feature-first or jargon-heavy phrasing to avoid. Rules: - Do not describe features without buyer impact. - Do not claim measurable ROI unless proof exists. - Do not use internal product language if buyers would not use it. - Every feature should answer: “So what?” --------------------------------------------------------------------------------

#104ROI Explanation and Business Case Presenter

DEMOS, PRESENTATIONS & VALUE COMMUNICATIONHigh-ticket sales, executive presentations, procurement conversations, CFO approval, proposal support, and enterprise sales.

Create a simple ROI explanation that helps buyers understand financial value, cost of inaction, payback logic, and business justification.

Act as a business case and ROI communication advisor. Build a clear ROI explanation for [OFFER] that a buyer can understand and share internally. Business context: Offer: [OFFER] Buyer: [BUYER] Company type: [COMPANY TYPE] Problem solved: [PROBLEM] Current cost of problem: [CURRENT COST] Expected improvement: [IMPROVEMENT] Price or investment: [PRICE] Implementation effort: [EFFORT] Timeline to value: [TIMELINE] Proof or benchmarks: [PROOF] Assumptions: [ASSUMPTIONS] Create the ROI presentation: 1. Value hypothesis Write a cautious value hypothesis using the available data. 2. Cost of current state Break down potential costs across: - wasted labor - lost revenue - delayed work - customer churn - errors - rework - risk exposure - opportunity cost 3. Value drivers Identify the main value drivers: - savings - growth - productivity - speed - risk reduction - retention - conversion - visibility 4. ROI model Create a simple model with: - input assumptions - low-case estimate - expected-case estimate - high-case estimate - payback logic - sensitivity factors 5. CFO-friendly explanation Write a concise financial explanation without hype. 6. Buyer-forwardable summary Write a short internal message the buyer can send to finance or leadership. 7. Risk notes List what must be validated before claiming ROI. Rules: - Do not invent financial numbers. - Use ranges when exact data is missing. - Separate proven results from assumptions. - Make the business case simple enough to share internally. --------------------------------------------------------------------------------

#105Use-Case Presentation Builder

DEMOS, PRESENTATIONS & VALUE COMMUNICATIONUse-case demos, sales presentations, solution consulting, technical sales, proposal meetings, and buyer enablement.

Build a focused presentation around one buyer use case, showing problem, workflow, solution path, proof, outcomes, implementation, and next steps.

You are a use-case presentation strategist. Create a presentation plan for showing how [OFFER] solves [USE CASE] for [BUYER / ACCOUNT]. Inputs: Use case: [USE CASE] Buyer persona: [BUYER] Account context: [ACCOUNT CONTEXT] Current workflow: [CURRENT WORKFLOW] Pain points: [PAINS] Desired outcomes: [OUTCOMES] Product capabilities: [CAPABILITIES] Proof assets: [PROOF] Implementation requirements: [REQUIREMENTS] Known objections: [OBJECTIONS] Presentation length: [LENGTH] Create the presentation: Slide or section 1: Why this use case matters Include: - buyer problem - business impact - urgency - affected stakeholders Slide or section 2: Current state Show: - current workflow - friction points - manual work - risk - cost of delay Slide or section 3: Future state Show: - improved workflow - better decision-making - reduced friction - expected outcomes Slide or section 4: How the solution works Map: - capability - workflow step - buyer benefit - proof point Slide or section 5: Example scenario Create a realistic scenario showing the use case in action. Slide or section 6: Results and proof Recommend: - metric - case study - testimonial - before/after comparison Slide or section 7: Implementation path Explain: - setup - timeline - owner - support - risks - success criteria Slide or section 8: Recommended next step Create a clear next-step ask. Rules: - Do not make the presentation a general product overview. - Do not include unrelated use cases. - Do not overload slides with features. - The buyer should leave understanding one use case deeply. --------------------------------------------------------------------------------

#106Proof Point Selection Matrix

DEMOS, PRESENTATIONS & VALUE COMMUNICATIONSales decks, demos, case studies, proposals, executive presentations, objection handling, and buyer confidence building.

Choose the strongest proof points for a specific buyer, sales stage, objection, use case, and value narrative.

Act as a proof strategy advisor. Help me choose which proof points to use in a demo or presentation. Context: Offer: [OFFER] Buyer persona: [BUYER] Target account: [ACCOUNT] Industry: [INDUSTRY] Use case: [USE CASE] Sales stage: [STAGE] Known concerns: [CONCERNS] Competitors: [COMPETITORS] Available proof assets: [PROOF ASSETS] Metrics available: [METRICS] Case studies available: [CASE STUDIES] Testimonials available: [TESTIMONIALS] Build the proof matrix: A. Proof inventory Classify available proof into: - metrics - case studies - testimonials - logos - screenshots - benchmarks - before/after examples - process proof - implementation proof - security/compliance proof - expert credibility B. Buyer-proof fit For each proof point evaluate: - relevance to buyer role - relevance to industry - relevance to use case - credibility - specificity - objection coverage - emotional impact - shareability - risk of overclaiming C. Proof by sales moment Recommend proof for: - opening credibility - problem validation - product walkthrough - ROI explanation - objection handling - executive summary - technical review - proposal follow-up D. Proof gaps Identify missing proof needed to strengthen the deal. E. Final proof stack Create: - primary proof point - secondary proof point - backup proof point - proof to avoid - how to phrase each proof point Rules: - Do not use famous logos if they are not relevant. - Do not overuse proof that does not match the buyer’s situation. - Do not make unsupported claims. - Proof should reduce risk and make value believable. --------------------------------------------------------------------------------

#107Discovery-to-Demo Mapping System

DEMOS, PRESENTATIONS & VALUE COMMUNICATIONAEs, sales engineers, founders, SaaS demos, discovery-led sales, and customized product presentations.

Turn discovery call notes into a demo plan that only shows what matters to the buyer and avoids generic product touring.

You are a discovery-to-demo translator. Convert discovery notes into a personalized demo plan. Discovery notes: [PASTE DISCOVERY NOTES] Additional context: Offer: [OFFER] Buyer persona: [BUYER] Account: [ACCOUNT] Deal stage: [STAGE] Product capabilities: [CAPABILITIES] Demo length: [LENGTH] Known stakeholders: [STAKEHOLDERS] Known objections: [OBJECTIONS] Desired next step: [NEXT STEP] Create the demo plan: 1. What we learned Extract: - buyer pain - current process - desired outcome - business impact - urgency - decision criteria - stakeholders - objections - open questions 2. Demo priorities Rank what to show: - must show - should show - optional - avoid showing Explain why. 3. Demo path Create the sequence: - recap - agenda - first product moment - second product moment - proof moment - objection-reduction moment - buyer-specific scenario - close 4. Questions during demo Create questions that check: - relevance - fit - concern - urgency - decision process - next step 5. Follow-up assets Recommend: - case study - one-pager - ROI model - technical documentation - stakeholder recap - proposal Rules: - Do not include features that are unrelated to discovery. - Do not ignore unanswered questions from discovery. - Do not make the demo longer than necessary. - The demo should prove that we listened. --------------------------------------------------------------------------------

#108Executive Pitch Narrative Constructor

DEMOS, PRESENTATIONS & VALUE COMMUNICATIONCEO, CFO, COO, CRO, VP-level presentations, board-facing summaries, enterprise sales, strategic accounts, and high-value deals.

Build a concise executive-level pitch that frames the offer around strategic priorities, financial impact, risk reduction, and decision confidence.

Act as an executive pitch strategist. Create a concise pitch narrative for presenting [OFFER] to [EXECUTIVE ROLE]. Executive context: Executive role: [ROLE] Company: [COMPANY] Industry: [INDUSTRY] Strategic priority: [PRIORITY] Business problem: [PROBLEM] Cost of inaction: [COST OF INACTION] Desired business outcome: [OUTCOME] Our offer: [OFFER] Differentiator: [DIFFERENTIATOR] Proof: [PROOF] Investment range: [PRICE] Decision needed: [DECISION] Build the executive narrative: A. Strategic opener Write 5 ways to open with a business-level insight. B. Problem framing Explain the problem in terms of: - revenue - cost - speed - risk - customer experience - operational leverage - competitive position C. Value thesis Write a clear thesis: - what changes - why it matters - why now - why this approach - why we are credible D. Executive slide outline Create 6 sections: - current challenge - business impact - future state - recommended approach - proof and risk reduction - decision and next step E. Executive talk track Write a 3-minute talk track. F. Pushback handling Prepare responses to: - “Why now?” - “Why this over alternatives?” - “What is the risk?” - “What is the expected return?” - “What do you need from us?” Rules: - Do not pitch features to executives. - Do not use junior-level operational detail unless asked. - Do not overstate certainty. - Executive communication must be brief, strategic, and decision-oriented. --------------------------------------------------------------------------------

#109Technical Demo Readiness Checklist

DEMOS, PRESENTATIONS & VALUE COMMUNICATIONSales engineers, technical buyers, SaaS demos, IT evaluations, security reviews, implementation calls, and complex B2B products.

Prepare a technical demo that answers implementation, integration, security, reliability, data, workflow, and technical-fit concerns.

You are a technical demo preparation expert. Build a readiness checklist and talk track for presenting [PRODUCT] to technical stakeholders. Technical context: Product: [PRODUCT] Technical buyer: [TECHNICAL BUYER] Use case: [USE CASE] Current systems: [CURRENT SYSTEMS] Integrations needed: [INTEGRATIONS] Data requirements: [DATA REQUIREMENTS] Security requirements: [SECURITY] Compliance requirements: [COMPLIANCE] Implementation timeline: [TIMELINE] Known technical concerns: [CONCERNS] Demo environment: [DEMO ENVIRONMENT] Create the technical demo plan: 1. Pre-demo readiness Check: - demo environment - test data - integrations - permissions - user roles - backup plan - security documentation - API documentation - implementation notes 2. Technical buyer priorities Explain what they likely care about: - architecture - reliability - scalability - data flow - access control - integrations - configuration - support - maintenance - failure modes 3. Demo flow Create a technical walkthrough with: - setup context - workflow demonstration - integration point - data movement - permission model - admin controls - reporting/logging - error handling - implementation path 4. Questions to ask Create questions about: - current stack - constraints - integration requirements - security review - implementation resources - success criteria - approval path 5. Risk handling Prepare answers for: - implementation complexity - downtime - data migration - security - compliance - scalability - support ownership Rules: - Do not hide technical limitations. - Do not overcomplicate the demo with irrelevant architecture. - Do not make unsupported security claims. - Technical buyers need clarity, honesty, and implementation confidence. --------------------------------------------------------------------------------

#110Demo Agenda and Timebox Designer

DEMOS, PRESENTATIONS & VALUE COMMUNICATION15-minute demos, 30-minute demos, executive briefings, product walkthroughs, sales calls, and demo coaching.

Create a tight demo agenda that protects time, keeps the conversation focused, and prevents feature wandering.

Act as a demo timeboxing coach. Build a structured agenda for a [DEMO LENGTH] demo of [OFFER]. Inputs: Demo length: [DEMO LENGTH] Buyer persona: [BUYER] Deal stage: [STAGE] Buyer goals: [GOALS] Pain points: [PAINS] Product areas to show: [PRODUCT AREAS] Proof points: [PROOF] Questions to answer: [QUESTIONS] Desired next step: [NEXT STEP] Create the agenda: A. Time allocation Break the demo into timed segments: - opening - buyer recap - agenda confirmation - product walkthrough - proof moment - questions - next step B. Segment objective For each segment define: - goal - what to say - what to show - what to avoid - question to ask C. Time protection language Write phrases for: - redirecting feature detours - parking unrelated questions - handling early pricing questions - managing long stakeholder questions - skipping irrelevant areas - moving to next step D. Shorter version Create a compressed version for when time is cut in half. E. Longer version Create an expanded version for deeper stakeholder review. Rules: - Do not let the demo become a product tour. - Do not spend more time on features than on buyer relevance. - Do not save next steps for the final 30 seconds. - A strong agenda makes the demo feel controlled but not rigid. --------------------------------------------------------------------------------

#111Product Storytelling Script Builder

DEMOS, PRESENTATIONS & VALUE COMMUNICATIONSales presentations, demos, pitch decks, product launches, founder pitches, webinars, and narrative-driven selling.

Turn product capabilities into a memorable story with context, tension, change, proof, and buyer transformation.

You are a product storytelling expert. Write a story-driven sales script for [PRODUCT / OFFER]. Story context: Product or offer: [PRODUCT / OFFER] Buyer: [BUYER] Problem: [PROBLEM] Old way: [OLD WAY] New way: [NEW WAY] Transformation: [TRANSFORMATION] Proof: [PROOF] Founder or product origin: [ORIGIN] Competitive difference: [DIFFERENCE] Tone: [TONE] Presentation length: [LENGTH] Build the story: 1. The world before Describe the buyer’s current state: - frustration - inefficiency - uncertainty - risk - missed opportunity 2. The tension Explain why the old way no longer works. 3. The insight Introduce the key insight behind the product. 4. The new path Show how the product changes the workflow or decision. 5. The proof Add proof that makes the story believable. 6. The buyer transformation Explain who the buyer becomes after solving the problem: - faster operator - clearer decision-maker - more trusted leader - more efficient team - less exposed organization 7. The call to action Write the final transition into next steps. Create: - 60-second version - 3-minute version - 7-minute version - demo narration version - pitch deck narration version Rules: - Do not make the seller the hero. - Do not overdramatize. - Do not use vague transformation language. - The buyer and their problem should drive the story. --------------------------------------------------------------------------------

#112Objection-Aware Demo Flow

DEMOS, PRESENTATIONS & VALUE COMMUNICATIONSales demos, competitive deals, high-ticket offers, technical products, procurement-heavy sales, and consultative selling.

Build a demo flow that proactively addresses objections around price, complexity, adoption, trust, technical fit, timing, switching, and risk.

Act as an objection-aware demo strategist. Design a demo that prevents and handles objections naturally. Context: Offer: [OFFER] Buyer persona: [BUYER] Use case: [USE CASE] Known objections: [OBJECTIONS] Competitors: [COMPETITORS] Implementation requirements: [IMPLEMENTATION] Proof assets: [PROOF] Pricing concern: [PRICING CONCERN] Adoption concern: [ADOPTION CONCERN] Technical concern: [TECHNICAL CONCERN] Create the objection-aware flow: A. Objection map For each likely objection identify: - root concern - when it may appear - what buyer needs to see - what proof helps - what not to say B. Demo prevention moments Insert moments in the demo that reduce concern before it is raised: - complexity reducer - adoption proof - implementation clarity - value explanation - risk reduction - switching support - technical confidence - customer proof C. Live objection responses Write natural responses to: - “This looks complicated” - “Our team may not use this” - “We already have a tool” - “This seems expensive” - “How long does implementation take?” - “What if this does not work for us?” - “We need security review” - “This is not a priority right now” D. Check-in questions Create questions that invite concerns throughout the demo. E. Close Create closing language that asks what risks remain. Rules: - Do not wait until the end to handle every concern. - Do not dismiss objections. - Do not overpromise simplicity. - A strong demo makes risk visible and manageable. --------------------------------------------------------------------------------

#113Before-and-After Value Visualization Builder

DEMOS, PRESENTATIONS & VALUE COMMUNICATIONSales presentations, demos, pitch decks, proposals, landing pages, value narratives, and buyer education.

Create a clear before-and-after explanation that helps buyers visualize the difference between their current state and improved future state.

You are a before-and-after value visualization expert. Build a clear comparison that shows the value of moving from the current state to the future state with [OFFER]. Inputs: Buyer: [BUYER] Current state: [CURRENT STATE] Pain points: [PAINS] Offer: [OFFER] Future state: [FUTURE STATE] Product capabilities: [CAPABILITIES] Outcomes: [OUTCOMES] Metrics: [METRICS] Proof: [PROOF] Create the visualization: 1. Current state map Describe: - workflow - friction - manual work - delays - risks - costs - emotional burden 2. Future state map Describe: - improved workflow - reduced friction - faster execution - better visibility - lower risk - stronger outcomes - buyer confidence 3. Comparison table Create a table with columns: - area - before - after - business impact - proof or assumption 4. Value narrative Write a short narrative that explains the transition from before to after. 5. Demo moments Identify which product moments best demonstrate the transformation. 6. Visual suggestions Suggest simple ways to present this: - slide layout - workflow diagram - checklist - scorecard - timeline - side-by-side view Rules: - Do not make the future state unrealistic. - Do not claim exact improvements without data. - Do not focus only on emotional benefits or only on numbers. - The buyer should clearly see what changes and why it matters. --------------------------------------------------------------------------------

#114Stakeholder-Specific Presentation Adapter

DEMOS, PRESENTATIONS & VALUE COMMUNICATIONMulti-stakeholder B2B sales, enterprise deals, demos with mixed audiences, procurement reviews, technical evaluations, and executive presentations.

Adapt the same demo or presentation for different stakeholders so each person hears the value in their own language.

Act as a stakeholder messaging strategist. Adapt this demo or presentation for each stakeholder in the buying committee. Base presentation: [PASTE BASE PRESENTATION OR OUTLINE] Deal context: Offer: [OFFER] Account: [ACCOUNT] Use case: [USE CASE] Stakeholders: [STAKEHOLDERS] Known pains: [PAINS] Known objections: [OBJECTIONS] Decision process: [DECISION PROCESS] Proof assets: [PROOF] Desired next step: [NEXT STEP] Adapt for these stakeholders: 1. Executive sponsor Focus on: - strategic value - business impact - risk - decision confidence 2. Economic buyer Focus on: - ROI - cost of inaction - budget logic - measurable outcomes 3. Department leader Focus on: - team performance - operational improvement - adoption - accountability 4. Daily user Focus on: - ease of use - workflow relief - time saved - reduced frustration 5. Technical evaluator Focus on: - integration - implementation - security - scalability - reliability 6. Procurement or finance Focus on: - vendor confidence - pricing logic - contract risk - approval requirements For each stakeholder create: - adapted opening - key points to emphasize - proof to use - objections to expect - language to avoid - CTA - follow-up asset Rules: - Do not use one generic presentation for everyone. - Do not overwhelm non-technical stakeholders with technical depth. - Do not ignore procurement and finance concerns. - Good value communication changes with the audience. --------------------------------------------------------------------------------

#115Live Demo Risk and Backup Plan

DEMOS, PRESENTATIONS & VALUE COMMUNICATIONSales engineers, AEs, founders, technical demos, live product demos, high-stakes presentations, and enterprise evaluations.

Prepare for demo failure, technical issues, unexpected questions, missing data, product limitations, time cuts, stakeholder changes, and presentation risk.

You are a live demo risk manager. Create a backup plan for a high-stakes demo of [PRODUCT / OFFER]. Demo context: Product or offer: [PRODUCT / OFFER] Buyer: [BUYER] Account: [ACCOUNT] Demo length: [LENGTH] Demo environment: [ENVIRONMENT] Product areas to show: [AREAS] Known limitations: [LIMITATIONS] Stakeholders attending: [STAKEHOLDERS] Technical dependencies: [DEPENDENCIES] Internet or platform risks: [RISKS] Desired next step: [NEXT STEP] Build the risk plan: A. Demo risk register Identify risks across: - login failure - slow loading - integration failure - missing data - broken feature - permission issue - wrong audience - surprise stakeholder - time cut - pricing question - competitive question - security question - product limitation For each risk provide: - likelihood - impact - warning sign - prevention step - backup plan - language to use live B. Backup materials Recommend: - screenshots - short video - slide backup - sample workflow - case study - technical one-pager - FAQ - ROI summary C. Recovery language Write phrases for: - acknowledging an issue - keeping confidence - moving to backup - parking a question - admitting a limitation - promising follow-up D. Pre-demo checklist Create a checklist for 24 hours before, 1 hour before, and 5 minutes before. Rules: - Do not pretend technical problems cannot happen. - Do not hide limitations if they matter. - Do not let one failed feature ruin the whole value narrative. - A backup plan should protect buyer confidence. --------------------------------------------------------------------------------

#116Demo Follow-Up Asset Generator

DEMOS, PRESENTATIONS & VALUE COMMUNICATIONPost-demo follow-up, complex B2B sales, stakeholder enablement, proposal preparation, and deal progression.

Create follow-up materials after a demo, including recap emails, stakeholder summaries, use-case notes, proof packages, next-step plans, and internal business case assets.

Act as a post-demo buyer enablement writer. Create follow-up assets that help the buyer remember the value, share it internally, and move to the next step. Demo context: Buyer: [BUYER] Account: [ACCOUNT] Offer: [OFFER] Demo notes: [DEMO NOTES] Features shown: [FEATURES SHOWN] Pains addressed: [PAINS] Outcomes discussed: [OUTCOMES] Questions asked: [QUESTIONS] Objections raised: [OBJECTIONS] Stakeholders present: [STAKEHOLDERS] Proof used: [PROOF] Agreed next step: [NEXT STEP] Create these follow-up assets: 1. Post-demo recap email Include: - what was discussed - value points - open questions - agreed next step - resources 2. Buyer-forwardable summary Write a concise internal summary the buyer can forward to colleagues. 3. Stakeholder-specific summaries Create summaries for: - executive - technical evaluator - daily user - finance/procurement 4. Demo value map Create a table: - pain - feature shown - outcome - proof - remaining question - next action 5. Follow-up resource package Recommend: - case study - ROI model - technical doc - security doc - implementation plan - pricing overview - comparison guide 6. Next meeting agenda Create an agenda for the next call. Rules: - Do not send a generic “thanks for your time” email. - Do not introduce new promises not shown in the demo. - Do not make the buyer do all the internal selling alone. - Follow-up should preserve momentum and reduce decision friction. --------------------------------------------------------------------------------

#117Competitive Demo Differentiation Script

DEMOS, PRESENTATIONS & VALUE COMMUNICATIONCompetitive sales, SaaS demos, replacement deals, comparison presentations, procurement reviews, and late-stage evaluations.

Show how a product differs from competitors during a demo without attacking competitors or making unsupported claims.

You are a competitive demo strategist. Build a differentiation script for presenting [OFFER] when the buyer is comparing us against [COMPETITORS]. Competitive context: Our offer: [OFFER] Competitors: [COMPETITORS] Buyer persona: [BUYER] Use case: [USE CASE] Buyer evaluation criteria: [CRITERIA] Our strengths: [STRENGTHS] Our weaknesses: [WEAKNESSES] Competitor strengths: [COMPETITOR STRENGTHS] Proof: [PROOF] Known objections: [OBJECTIONS] Create the competitive demo plan: A. Positioning frame Write a neutral way to explain: - what we are best for - what we are not best for - when competitors may be a fit - why buyers choose us B. Differentiation moments Identify demo moments that show: - workflow difference - speed difference - usability difference - flexibility difference - reporting difference - implementation difference - support difference - ROI difference C. Comparison language Write phrases that are: - fair - specific - proof-backed - non-attacking - buyer-centered D. Competitive objection responses Prepare responses to: - “Competitor X does this too” - “They are cheaper” - “They are better known” - “They already integrate with us” - “Their team promised the same result” E. Decision guide Create a buyer-friendly comparison table based on evaluation criteria. Rules: - Do not attack competitors. - Do not claim superiority without proof. - Do not hide where competitors may be better. - The goal is buyer clarity, not competitor bashing. --------------------------------------------------------------------------------

#118Pilot, Trial or POC Presentation Plan

DEMOS, PRESENTATIONS & VALUE COMMUNICATIONSaaS pilots, enterprise POCs, paid trials, implementation tests, technical evaluations, and complex B2B sales.

Present a pilot, trial, or proof-of-concept in a way that defines scope, success criteria, timeline, ownership, risks, and conversion path.

Act as a pilot and proof-of-concept sales advisor. Build a presentation plan for proposing a [PILOT / TRIAL / POC] for [OFFER]. Context: Offer: [OFFER] Buyer: [BUYER] Account: [ACCOUNT] Use case: [USE CASE] Problem: [PROBLEM] Desired outcome: [OUTCOME] Pilot scope: [SCOPE] Timeline: [TIMELINE] Success criteria: [SUCCESS CRITERIA] Stakeholders: [STAKEHOLDERS] Technical requirements: [REQUIREMENTS] Commercial terms: [TERMS] Risks: [RISKS] Build the presentation: 1. Why pilot Explain: - what the pilot is meant to prove - what uncertainty it reduces - why it is the right next step - what it is not meant to prove 2. Pilot design Define: - scope - users - workflow - data - integrations - timeline - support - responsibilities 3. Success criteria Create measurable criteria for: - adoption - speed - accuracy - efficiency - revenue impact - cost reduction - user feedback - technical fit 4. Governance Define: - owner on buyer side - owner on seller side - check-in cadence - issue escalation - decision meeting 5. Conversion path Explain: - what happens after success - commercial next step - rollout plan - procurement path - decision date 6. Presentation script Write a 5-minute talk track. Rules: - Do not propose a pilot without success criteria. - Do not let the pilot become free consulting. - Do not create an open-ended trial with no decision path. - A good pilot should reduce risk and lead to a decision. --------------------------------------------------------------------------------

#119Sales Deck Value Narrative Auditor

DEMOS, PRESENTATIONS & VALUE COMMUNICATIONPitch decks, sales presentations, investor-like commercial decks, proposal decks, webinars, and enterprise sales decks.

Audit a sales deck for buyer relevance, narrative flow, value clarity, proof, slide logic, objection coverage, and next-step strength.

Act as a sales deck auditor. Review my sales deck outline and improve it so it communicates value more clearly. Sales deck outline or slides: [PASTE DECK OUTLINE OR SLIDE TEXT] Context: Offer: [OFFER] Target buyer: [BUYER] Target account type: [ACCOUNT TYPE] Sales stage: [STAGE] Presentation goal: [GOAL] Buyer pain: [PAIN] Desired outcome: [OUTCOME] Proof: [PROOF] Known objections: [OBJECTIONS] Time available: [TIME] Audit the deck across 15 criteria: 1. Buyer relevance 2. Opening strength 3. Problem clarity 4. Urgency 5. Current-state explanation 6. Future-state clarity 7. Solution logic 8. Feature-to-value translation 9. Proof strength 10. Differentiation 11. ROI or business impact 12. Objection coverage 13. Slide simplicity 14. Narrative flow 15. Next-step clarity For each criterion provide: - score from 1 to 10 - what works - what is weak - exact fix - slide-level recommendation Then create: - improved deck structure - slides to remove - slides to add - slides to combine - better section titles - stronger opening - stronger close - presenter notes for key slides Rules: - Do not make the deck longer unless it becomes more useful. - Do not lead with company history unless it builds trust quickly. - Do not overload slides with text. - A sales deck should help the buyer decide, not just inform. --------------------------------------------------------------------------------

#120Full Demos, Presentations and Value Communication Audit

DEMOS, PRESENTATIONS & VALUE COMMUNICATIONSales leaders, founders, AEs, sales engineers, SaaS teams, consultants, agencies, RevOps, and teams that need stronger value communication.

Audit and rebuild the complete sales demo and presentation system across narrative, discovery alignment, feature-to-value translation, proof, ROI, stakeholder messaging, objection handling, follow-up, and next steps.

Act as an independent demos, presentations, and value communication auditor. Review my current sales presentation system and rebuild it into a buyer-specific value engine. Full context: Company: [COMPANY] Website: [WEBSITE] Offer: [OFFER] Target market: [MARKET] ICP: [ICP] Buyer personas: [PERSONAS] Sales cycle: [SALES CYCLE] Average deal size: [DEAL SIZE] Current demo script: [DEMO SCRIPT] Current deck: [DECK] Current product walkthrough: [WALKTHROUGH] Current value proposition: [VALUE PROPOSITION] Current ROI explanation: [ROI] Current proof assets: [PROOF] Current case studies: [CASE STUDIES] Current follow-up assets: [FOLLOW-UP ASSETS] Common objections: [OBJECTIONS] Competitors: [COMPETITORS] Discovery notes: [DISCOVERY NOTES] Demo conversion rates: [CONVERSION RATES] Proposal conversion rates: [PROPOSAL RATES] Main demo problems: [PROBLEMS] Audit across 40 dimensions: 1. Discovery-to-demo alignment 2. Buyer-specific narrative 3. Opening clarity 4. Agenda control 5. Pain recap 6. Current-state framing 7. Future-state framing 8. Feature selection 9. Feature-to-value translation 10. Product walkthrough flow 11. Use-case relevance 12. Executive value communication 13. Technical value communication 14. User value communication 15. Finance/procurement communication 16. Proof selection 17. Case study relevance 18. ROI explanation 19. Cost of inaction explanation 20. Differentiation 21. Competitive comparison 22. Objection prevention 23. Objection handling 24. Implementation clarity 25. Adoption clarity 26. Risk reduction 27. Demo pacing 28. Slide simplicity 29. Storytelling 30. Presenter talk track 31. Live demo readiness 32. Backup plan 33. Q&A handling 34. Next-step close 35. Post-demo follow-up 36. Buyer-forwardable summary 37. Stakeholder enablement 38. Sales engineer collaboration 39. Measurement and coaching 40. Overall value communication maturity For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - buyer impact - revenue impact - risk if ignored - recommended fix - priority - effort - confidence level Then synthesize: A. Hard truth Explain the biggest reason our demos or presentations may not be converting. B. Rebuilt value communication system Create: - improved demo narrative - improved product walkthrough - improved sales deck structure - improved ROI explanation - improved proof strategy - improved stakeholder-specific messaging - improved objection-aware flow - improved follow-up package C. Demo enablement kit Create: - pre-demo checklist - discovery-to-demo mapper - feature-to-value cheat sheet - proof selection matrix - demo agenda template - live demo risk checklist - post-demo email template - manager coaching scorecard D. 30-day improvement roadmap Create: - first 24-hour fix - first 7-day demo cleanup - first 14-day sales deck update - first 30-day demo coaching plan - metrics to track - owner assignments E. Executive summary Write a direct summary with: - fastest demo improvement - weakest value communication point - first feature to remove from the demo - first proof point to add - first ROI explanation to improve - first stakeholder message to customize - first follow-up asset to build - one operating principle for better demos Rules: - Do not make the demo more impressive at the expense of buyer relevance. - Do not show features that discovery did not justify. - Do not use proof that does not match the buyer’s situation. - Use [NEEDS DATA], [NEEDS DISCOVERY NOTES], [NEEDS SALES FEEDBACK], or [NEEDS PRODUCT REVIEW] where required. - The final system should help buyers understand value, trust the solution, and agree to a clear next step.

#121Objection Intelligence Map Builder

OBJECTION HANDLING & DEAL ADVANCEMENTSales teams, founders, account executives, SDRs, consultants, agencies, SaaS companies, and anyone who needs a structured way to handle objections without sounding defensive.

Build a complete objection map that separates surface objections from root concerns and gives sellers clear response paths.

You are a senior sales strategist. Build an objection intelligence map for selling [OFFER] to [BUYER PERSONA]. Context: Offer: [OFFER] Target buyer: [BUYER PERSONA] Target account type: [ACCOUNT TYPE] Deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Current sales stage: [SALES STAGE] Common objections: [OBJECTIONS] Closed-won reasons: [CLOSED WON REASONS] Closed-lost reasons: [CLOSED LOST REASONS] Competitors or alternatives: [COMPETITORS] Proof available: [PROOF] Main risk buyers perceive: [RISK] Build the objection map: 1. Objection categories Group objections into: - price - budget - timing - priority - trust - risk - competition - authority - internal buy-in - implementation - urgency - status quo - procurement - technical fit 2. Root cause diagnosis For every objection, explain: - what the buyer says - what the buyer may actually mean - why it appears - whether it is rational, emotional, political, or procedural - whether it is fixable or disqualifying 3. Response path For each objection create: - acknowledgment - clarifying question - value reframe - proof point - risk reducer - next-step question - when to stop pushing 4. Deal impact Score each objection by: - severity - likelihood - deal risk - urgency impact - stakeholder impact - forecast impact 5. Seller cheat sheet Create a quick reference table with: - objection - root concern - best question - best proof - best next step - red flag Rules: - Do not argue with the buyer. - Do not treat every objection as a buying signal. - Do not answer before diagnosing. - The goal is to create clarity and advance the deal only when fit is real. --------------------------------------------------------------------------------

#122Price Objection Value Reframe System

OBJECTION HANDLING & DEAL ADVANCEMENTHigh-ticket sales, SaaS pricing conversations, agency proposals, consulting offers, enterprise sales, and sellers who hear “too expensive.”

Handle price objections by connecting cost to value, business impact, risk, alternatives, payback, and the cost of inaction.

Act as a value-based sales coach. Build a price objection handling system for [OFFER]. Inputs: Offer: [OFFER] Price or pricing range: [PRICE] Target buyer: [BUYER] Business outcome: [OUTCOME] Current cost of problem: [COST OF PROBLEM] Alternative options: [ALTERNATIVES] Proof or ROI data: [PROOF] Common price objection wording: [PRICE OBJECTION] Buyer budget context: [BUDGET CONTEXT] Discount policy: [DISCOUNT POLICY] Create the system: A. Price objection diagnosis Explain what each statement may mean: - “This is too expensive” - “We do not have budget” - “Can you do it cheaper?” - “Your competitor is cheaper” - “We need to justify the cost” - “This is more than expected” - “We are not sure the ROI is there” For each, identify: - real concern - risk level - missing information - best clarifying question - wrong response to avoid B. Value reframe scripts Write responses that reframe price around: - cost of inaction - wasted time - lost revenue - risk reduction - implementation speed - quality improvement - strategic priority - comparison to alternatives - payback period C. ROI conversation guide Create: - questions to quantify value - simple ROI formula - low / expected / high value scenario - buyer-friendly explanation - internal business case paragraph D. Discount protection Create language for: - holding price - trading discount for scope - offering phased rollout - offering lower tier - declining discount respectfully - asking what budget would make sense E. Advancement close Write next-step language that moves from price concern to a decision path. Rules: - Do not apologize for the price. - Do not discount before understanding the value gap. - Do not invent ROI numbers. - Price objections should become value conversations, not arguments. --------------------------------------------------------------------------------

#123Timing Objection Advancement Flow

OBJECTION HANDLING & DEAL ADVANCEMENTDeals stuck in “later,” prospects saying “not now,” Q4/Q1 budget timing, long sales cycles, and sales teams trying to reduce stalled pipeline.

Turn timing objections into a clearer understanding of urgency, priority, internal deadlines, opportunity cost, and future decision milestones.

You are a sales deal advancement coach. Create a timing objection flow for prospects who say [TIMING OBJECTION]. Deal context: Offer: [OFFER] Buyer persona: [BUYER] Account: [ACCOUNT] Current stage: [STAGE] Known pain: [PAIN] Known impact: [IMPACT] Known urgency: [URGENCY] Known deadline: [DEADLINE] Current next step: [NEXT STEP] Timing objection: [TIMING OBJECTION] Sales cycle: [SALES CYCLE] Build the flow: 1. Timing objection types Classify the objection as one of: - real timing constraint - low priority - no urgency - budget cycle delay - internal resource constraint - decision avoidance - stakeholder misalignment - unclear value - polite rejection 2. Clarifying questions Create questions that uncover: - why now is not the right time - what must happen before action - what deadline matters - who controls timing - what happens if nothing changes - what would make this more urgent - when the topic will be revisited 3. Response scripts Write responses for: - “circle back next quarter” - “not a priority right now” - “we are too busy” - “we need to wait for budget” - “we have other projects first” - “timing is bad” - “maybe later” 4. Advancement options Recommend next steps such as: - scheduled future meeting - internal business case - stakeholder intro - diagnostic session - pilot scoping - nurture path - disqualification 5. Deal decision Create a decision tree: - advance now - create future milestone - nurture - close-lost - disqualify Rules: - Do not create fake urgency. - Do not accept “later” without defining what changes later. - Do not keep weak timing deals in active pipeline. - The goal is to clarify whether timing is real or a cover for another concern. --------------------------------------------------------------------------------

#124Trust and Credibility Gap Closer

OBJECTION HANDLING & DEAL ADVANCEMENTEarly-stage companies, new categories, founder-led sales, consulting, SaaS, agencies, enterprise buyers, and competitive deals.

Help sellers handle buyer hesitation caused by lack of trust, weak proof, unknown brand, limited case studies, or fear of making the wrong choice.

Act as a trust-building sales advisor. Create a credibility plan for a buyer who is interested but not fully confident. Context: Offer: [OFFER] Buyer: [BUYER] Account type: [ACCOUNT TYPE] Buyer concern: [CONCERN] Company credibility level: [CREDIBILITY LEVEL] Proof assets: [PROOF ASSETS] Customer examples: [CUSTOMERS] Case studies: [CASE STUDIES] Testimonials: [TESTIMONIALS] Security or compliance proof: [SECURITY] Implementation proof: [IMPLEMENTATION PROOF] Competitors: [COMPETITORS] Build the trust plan: A. Trust gap diagnosis Identify which trust gap is present: - unknown company - unproven category - lack of similar customer proof - fear of implementation failure - fear of internal embarrassment - concern about support - concern about long-term stability - concern about exaggerated claims B. Credibility assets Choose the strongest trust builders: - customer story - metric - founder expertise - process explanation - demo proof - implementation plan - reference call - security documentation - pilot - guarantee or risk reversal C. Trust-building messages Write: - cold follow-up response - call response - post-demo email - executive reassurance - technical reassurance - procurement reassurance D. Proof sequencing Explain what proof to use: - early in deal - after discovery - during demo - after objection - before proposal - before final decision E. Confidence close Write a next-step question that checks whether the buyer has enough confidence to move forward. Rules: - Do not overclaim. - Do not use irrelevant proof. - Do not respond to trust concerns with pressure. - Trust is built by specificity, transparency, and proof. --------------------------------------------------------------------------------

#125Competitive Objection Decision Guide

OBJECTION HANDLING & DEAL ADVANCEMENTCompetitive SaaS sales, agencies replacing vendors, consultants, enterprise evaluations, procurement processes, and comparison-heavy deals.

Handle objections involving competitors, alternatives, existing vendors, cheaper options, in-house solutions, and status quo without attacking the other choice.

You are a competitive sales strategist. Build a decision guide for handling competitive objections against [COMPETITOR / ALTERNATIVE]. Context: Our offer: [OFFER] Competitor or alternative: [COMPETITOR] Buyer: [BUYER] Use case: [USE CASE] Current vendor status: [CURRENT VENDOR] Buyer’s stated objection: [OBJECTION] Our strengths: [STRENGTHS] Our weaknesses: [WEAKNESSES] Competitor strengths: [COMPETITOR STRENGTHS] Competitor weaknesses, if verified: [COMPETITOR WEAKNESSES] Proof: [PROOF] Decision criteria: [CRITERIA] Create the guide: 1. Neutral positioning Write a fair statement explaining: - where we are strongest - where the competitor may be stronger - what kind of buyer should choose us - what decision criteria matter most 2. Objection responses Handle: - “We already use [competitor]” - “[Competitor] is cheaper” - “[Competitor] has more features” - “[Competitor] is better known” - “We can build this in-house” - “We are happy with our current vendor” - “We are evaluating several options” 3. Comparison table Create a buyer-friendly comparison across: - fit for use case - speed to value - ease of adoption - implementation effort - flexibility - support - risk - total cost - business outcome 4. Discovery questions Create questions that reveal: - what they like about the competitor - what is missing - what switching would require - what decision criteria matter - what risk they are trying to avoid 5. Advancement plan Recommend: - proof to send - demo angle - stakeholder to involve - comparison asset - pilot or evaluation path - next-step language Rules: - Do not attack competitors. - Do not make claims without proof. - Do not pretend we are better for every buyer. - Competitive selling should help the buyer make a clearer decision. --------------------------------------------------------------------------------

#126Authority and Internal Buy-In Mapper

OBJECTION HANDLING & DEAL ADVANCEMENTEnterprise sales, multi-stakeholder deals, founder-led sales, consultative sales, procurement-heavy deals, and complex buying committees.

Handle authority objections by mapping stakeholders, influence, approval paths, internal champions, blockers, and the assets needed to create buy-in.

Act as a stakeholder strategy advisor. Build an authority and internal buy-in plan for this deal. Deal context: Offer: [OFFER] Account: [ACCOUNT] Primary contact: [CONTACT] Contact role: [ROLE] Current objection: [AUTHORITY OBJECTION] Known stakeholders: [STAKEHOLDERS] Unknown stakeholders: [UNKNOWN STAKEHOLDERS] Decision process: [DECISION PROCESS] Business pain: [PAIN] Proof: [PROOF] Current next step: [NEXT STEP] Build the plan: A. Authority diagnosis Determine whether the objection means: - the contact lacks decision authority - the contact lacks budget authority - the contact needs internal consensus - procurement is involved - finance is involved - technical approval is needed - executive sponsorship is missing - the buyer is avoiding a decision B. Stakeholder map Create a table: - stakeholder - role in decision - likely concern - influence level - current access - proof needed - seller action - risk if ignored C. Buy-in questions Create questions to ask the contact: - who needs to be involved - what each person cares about - what objections they expect internally - what information would help - how decisions like this are usually made - what would block approval D. Champion enablement Create: - internal summary - forwardable business case - stakeholder-specific talking points - objection FAQ - next meeting invite language E. Advancement options Write language for: - asking to include another stakeholder - asking for executive alignment - asking for finance/procurement input - asking for technical review - pausing if no internal path exists Rules: - Do not bypass the primary contact disrespectfully. - Do not assume one person can approve the deal. - Do not rely on a champion without enabling them. - Deals advance when the internal path is visible. --------------------------------------------------------------------------------

#127Implementation Risk Reducer

OBJECTION HANDLING & DEAL ADVANCEMENTSaaS implementation, services onboarding, enterprise sales, technical evaluations, operations buyers, customer success handoffs, and post-demo objections.

Handle buyer concerns about setup, migration, adoption, training, disruption, complexity, and operational risk.

You are an implementation confidence advisor. Build a response system for prospects worried that [OFFER] will be hard to implement. Context: Offer: [OFFER] Buyer: [BUYER] Use case: [USE CASE] Implementation requirements: [REQUIREMENTS] Typical timeline: [TIMELINE] Buyer resources needed: [RESOURCES] Known complexity: [COMPLEXITY] Support provided: [SUPPORT] Onboarding process: [ONBOARDING] Proof of successful implementation: [PROOF] Buyer objection: [OBJECTION] Create the implementation risk reducer: 1. Implementation concern map Identify concerns around: - time - team capacity - migration - integrations - training - adoption - disruption - data quality - technical risk - change management - internal ownership 2. Response framework For each concern provide: - acknowledgment - clarifying question - honest explanation - risk reducer - proof point - next step 3. Implementation plan Create a simple plan with: - phase - owner - buyer responsibility - seller responsibility - timeline - success checkpoint - risk mitigation 4. Adoption confidence Create language showing how users will adopt: - training - templates - support - documentation - pilot users - feedback loop - success metrics 5. Deal advancement Write next-step language for: - implementation review call - technical scoping - pilot - onboarding plan review - customer reference - disqualification if implementation is not feasible Rules: - Do not promise zero effort. - Do not minimize real complexity. - Do not advance without confirming buyer resources. - Implementation confidence comes from clarity, not optimism. --------------------------------------------------------------------------------

#128Urgency and No-Decision Deal Rescue

OBJECTION HANDLING & DEAL ADVANCEMENTStalled opportunities, no-decision deals, pipeline cleanup, enterprise sales, long sales cycles, and sales coaching.

Rescue deals that are stuck because the buyer sees value but lacks urgency, priority, consequences, or a clear reason to change now.

Act as a no-decision deal rescue strategist. Analyze why this deal is stuck and create a plan to restore urgency or exit cleanly. Deal context: Account: [ACCOUNT] Offer: [OFFER] Buyer: [BUYER] Stage: [STAGE] Pain discussed: [PAIN] Value discussed: [VALUE] Current objection: [OBJECTION] Last interaction: [LAST INTERACTION] Time stalled: [TIME STALLED] Next step status: [NEXT STEP STATUS] Known stakeholders: [STAKEHOLDERS] Known competitors: [COMPETITORS] Forecast category: [FORECAST] Analyze the deal: A. Stalled deal diagnosis Choose the most likely cause: - weak pain - unclear value - no executive priority - no deadline - no champion - hidden objection - budget uncertainty - stakeholder misalignment - status quo preference - competing internal project - poor next step B. Evidence review List: - evidence that urgency is real - evidence that urgency is weak - missing information - assumptions that need validation C. Urgency restoration questions Create questions that clarify: - what happens if nothing changes - why this matters now - what deadline exists - who cares internally - what priority this competes with - what decision milestone is next D. Rescue plays Create: - executive reframe email - champion reactivation message - stakeholder alignment request - business impact recap - cost of inaction summary - pilot proposal - close-the-loop email E. Decision recommendation Choose: - advance - requalify - move to nurture - close-lost - disqualify Rules: - Do not manufacture urgency. - Do not keep no-decision deals in active pipeline forever. - Do not confuse interest with intent. - A rescued deal needs a real business reason to move. --------------------------------------------------------------------------------

#129Procurement and Legal Objection Playbook

OBJECTION HANDLING & DEAL ADVANCEMENTEnterprise sales, B2B SaaS, vendor onboarding, procurement-heavy deals, legal review, security reviews, and late-stage deal management.

Handle procurement, legal, compliance, contract, terms, security, and vendor approval objections while keeping the deal organized and moving.

You are a late-stage deal advancement advisor. Build a procurement and legal objection playbook for [OFFER]. Deal context: Offer: [OFFER] Account: [ACCOUNT] Buyer: [BUYER] Deal size: [DEAL SIZE] Current stage: [STAGE] Procurement process: [PROCUREMENT PROCESS] Legal requirements: [LEGAL REQUIREMENTS] Security requirements: [SECURITY REQUIREMENTS] Contract concerns: [CONTRACT CONCERNS] Commercial terms: [TERMS] Deadline: [DEADLINE] Internal owner: [OWNER] Create the playbook: 1. Process map Map the path through: - business approval - procurement intake - vendor registration - security review - legal review - finance approval - purchase order - signature - implementation kickoff 2. Objection library Handle objections around: - payment terms - data processing - liability - termination - security documentation - insurance - vendor risk - pricing structure - service-level commitments - procurement timeline 3. Response templates Create language for: - buyer update - procurement response - legal clarification - security documentation handoff - escalation request - mutual action plan - deadline risk warning 4. Deal control system Create: - mutual action plan - owner table - deadline tracker - document checklist - escalation triggers - weekly update format 5. Risk management Identify: - red flags - stuck points - missing documents - commercial risks - legal review risks - forecast risks Rules: - Do not give legal advice. - Use [NEEDS LEGAL REVIEW] where legal judgment is required. - Do not let procurement become invisible. - Late-stage deals need process control, not more persuasion. --------------------------------------------------------------------------------

#130Discount Request Handling Matrix

OBJECTION HANDLING & DEAL ADVANCEMENTSaaS sales, agencies, consultants, B2B services, enterprise sales, renewals, procurement conversations, and price negotiation.

Handle discount requests by protecting value, understanding buyer constraints, negotiating scope, trading concessions, and avoiding unnecessary margin loss.

Act as a pricing and negotiation coach. Create a discount handling matrix for [OFFER]. Context: Offer: [OFFER] Standard price: [PRICE] Buyer: [BUYER] Deal size: [DEAL SIZE] Buyer reason for discount: [REASON] Value delivered: [VALUE] Proof: [PROOF] Alternatives: [ALTERNATIVES] Margin constraints: [MARGIN] Discount policy: [POLICY] Negotiation stage: [STAGE] Build the matrix: A. Discount request diagnosis Classify the request: - budget constraint - procurement tactic - value uncertainty - competitor comparison - approval threshold - cash flow issue - low urgency - habit of negotiating - scope mismatch B. Clarifying questions Create questions that uncover: - what budget exists - what value is missing - what decision depends on price - what scope matters most - what timeline matters - what they can trade for discount C. Response options Create scripts for: - holding firm - reducing scope - phased rollout - annual commitment - faster payment - multi-year agreement - case study exchange - referral commitment - lower tier - pilot offer D. Give-get table Create a table: - buyer asks for - seller can offer - seller asks in return - risk - when to use E. Walk-away criteria Define when to stop negotiating. Rules: - Do not discount without a reason and trade. - Do not reduce price while keeping full scope. - Do not punish good-fit buyers, but protect value. - Negotiation should create mutual commitment, not margin leakage. --------------------------------------------------------------------------------

#131“Send Me Information” Response System

OBJECTION HANDLING & DEAL ADVANCEMENTCold calls, discovery calls, demos, early conversations, objections, SDR follow-up, and prospects avoiding commitment.

Turn the vague “send me information” objection into a clearer next step, qualification path, stakeholder handoff, or respectful exit.

You are a sales conversation recovery coach. Build a response system for when a prospect says: “send me information.” Context: Offer: [OFFER] Buyer: [BUYER] Conversation source: [COLD CALL / EMAIL / LINKEDIN / DISCOVERY / DEMO] What was discussed: [DISCUSSION] Buyer interest level: [INTEREST] Known pain: [PAIN] Known stage: [STAGE] Desired next step: [NEXT STEP] Asset available: [ASSET] Create the response system: 1. Diagnosis Explain what “send me information” may mean: - genuine interest - no time - polite rejection - unclear value - wrong person - needs internal sharing - wants pricing - wants proof - avoiding a call 2. Live response options Write scripts for: - phone call response - discovery call response - demo response - LinkedIn DM response - email response 3. Clarifying questions Create questions that ask: - what information would be useful - who it is for - what problem they are evaluating - when they plan to review - whether a specific use case matters - whether another person should be included 4. Follow-up packages Create targeted info packages for: - executive - technical evaluator - finance - user team - procurement - early-stage researcher 5. Advancement close Write language to turn the info request into: - scheduled follow-up - stakeholder intro - discovery call - resource-only nurture - disqualification Rules: - Do not send generic collateral without context. - Do not treat “send info” as a committed next step. - Do not pressure the buyer if they only need a resource. - Make the information useful and the next step explicit. --------------------------------------------------------------------------------

#132Ghosted Deal Revival Planner

OBJECTION HANDLING & DEAL ADVANCEMENTStalled pipeline, no-response opportunities, post-demo silence, proposal follow-up, founder-led sales, and SDR/AE follow-up.

Re-engage prospects who stopped replying by diagnosing why they went quiet and using respectful, value-added revival messages.

Act as a stalled deal recovery strategist. Create a ghosted deal revival plan for this opportunity. Deal context: Account: [ACCOUNT] Contact: [CONTACT] Offer: [OFFER] Deal stage before silence: [STAGE] Last message sent: [LAST MESSAGE] Last buyer response: [BUYER RESPONSE] Time since last reply: [TIME] Pain discussed: [PAIN] Value discussed: [VALUE] Objections raised: [OBJECTIONS] Next step that was expected: [EXPECTED NEXT STEP] Known stakeholders: [STAKEHOLDERS] Build the revival plan: A. Silence diagnosis Estimate likely reasons: - lost priority - hidden objection - budget issue - internal blocker - competitor selected - timing changed - no real pain - weak champion - overwhelmed buyer - poor follow-up For each reason provide: - evidence - confidence level - best response angle B. Message sequence Write: - short nudge - value recap - new insight follow-up - stakeholder help message - objection surfacing message - close-the-loop message - future nurture message C. Channel plan Recommend use of: - email - LinkedIn - phone - voicemail - referral - champion - executive contact D. Exit criteria Define when to: - keep pursuing - move to nurture - close-lost - disqualify E. CRM update Write a CRM note summarizing the plan. Rules: - Do not guilt or shame the buyer. - Do not send repeated “checking in” messages. - Do not keep chasing indefinitely. - Revival should add clarity or value with each touch. --------------------------------------------------------------------------------

#133Risk Reversal and Confidence Builder

OBJECTION HANDLING & DEAL ADVANCEMENTHigh-risk purchases, new vendors, expensive offers, unproven categories, enterprise sales, consulting, SaaS, and deal advancement.

Reduce buyer fear by designing guarantees, pilots, phased starts, success checkpoints, references, proof, and implementation safeguards.

You are a buyer risk reduction strategist. Create risk reversal options for [OFFER] that help the buyer move forward without creating bad business terms. Context: Offer: [OFFER] Buyer: [BUYER] Account type: [ACCOUNT TYPE] Main perceived risk: [RISK] Price: [PRICE] Implementation effort: [EFFORT] Proof available: [PROOF] Support available: [SUPPORT] Delivery constraints: [CONSTRAINTS] Terms we can offer: [TERMS] Terms we cannot offer: [LIMITS] Design risk reducers: 1. Risk inventory List buyer risks across: - financial risk - implementation risk - adoption risk - performance risk - stakeholder risk - vendor risk - switching risk - timing risk - reputational risk 2. Risk reversal options Create options such as: - pilot - phased rollout - success milestone - paid diagnostic - onboarding guarantee - reference call - implementation plan - cancellation clause - service-level promise - training package - proof package 3. Option evaluation For each option provide: - buyer benefit - seller risk - operational cost - when to use - when to avoid - required conditions 4. Messaging Write: - discovery call language - proposal language - executive reassurance - procurement reassurance - follow-up email 5. Recommendation Choose the best 3 risk reducers for this deal. Rules: - Do not offer guarantees that cannot be honored. - Do not transfer all risk to the seller. - Do not use risk reversal to save a bad-fit deal. - Strong risk reduction makes the decision feel safer and more specific. --------------------------------------------------------------------------------

#134Technical and Security Objection Handler

OBJECTION HANDLING & DEAL ADVANCEMENTSaaS, enterprise sales, sales engineers, technical demos, security reviews, IT buyers, legal/procurement stages, and complex product sales.

Handle objections about integrations, data security, compliance, reliability, performance, permissions, technical fit, and IT approval.

Act as a technical sales engineer and security-aware sales advisor. Build objection responses for technical and security concerns about [PRODUCT]. Context: Product: [PRODUCT] Buyer: [BUYER] Technical stakeholder: [TECHNICAL STAKEHOLDER] Use case: [USE CASE] Current tech stack: [TECH STACK] Integrations: [INTEGRATIONS] Security documentation: [SECURITY DOCS] Compliance requirements: [COMPLIANCE] Known limitations: [LIMITATIONS] Technical objections: [OBJECTIONS] Create the handler: A. Technical objection map Handle concerns around: - integration complexity - API limitations - data migration - permissions - admin control - uptime - scalability - reporting - data ownership - access control - compliance - security review - implementation timeline B. Response structure For each objection provide: - plain-English explanation - technical explanation - clarification question - documentation to share - proof point - limitation to disclose - next technical step C. Escalation path Define when to involve: - sales engineer - product team - security team - legal - implementation lead - customer success D. Technical next steps Create options: - technical review call - architecture walkthrough - security questionnaire - sandbox demo - proof-of-concept - integration scoping E. Buyer-safe language Write language that is transparent without creating unnecessary fear. Rules: - Do not make technical claims without proof. - Use [NEEDS TECHNICAL REVIEW] where required. - Use [NEEDS LEGAL REVIEW] for compliance commitments. - Technical objections need precision, not persuasion. --------------------------------------------------------------------------------

#135Status Quo Objection Breakthrough

OBJECTION HANDLING & DEAL ADVANCEMENTCategory creation, new solution sales, operations improvement, workflow software, consulting, agencies, and prospects comfortable with current processes.

Help sellers handle “we are fine as is,” “we already have a process,” or “not a priority” by uncovering hidden costs, friction, risk, and missed opportunities.

You are a status quo sales strategist. Create a breakthrough plan for prospects who prefer their current way of working. Context: Offer: [OFFER] Buyer: [BUYER] Current process or solution: [CURRENT PROCESS] Status quo objection: [OBJECTION] Known pain signals: [PAIN SIGNALS] Potential cost of inaction: [COST] Competitors or alternatives: [ALTERNATIVES] Proof: [PROOF] Sales stage: [STAGE] Build the breakthrough plan: 1. Status quo diagnosis Determine whether the buyer is staying put because of: - no pain - hidden pain - low awareness - fear of change - no executive priority - weak value - switching cost - internal politics - lack of trust - genuine good fit with current process 2. Discovery questions Create questions that reveal: - what works today - what breaks sometimes - what takes too long - what is manual - what creates risk - what gets delayed - what leadership wants improved - what they would change if it were easy 3. Reframe angles Write reframes around: - efficiency - risk - scalability - visibility - quality - customer experience - team frustration - missed growth 4. Respectful response scripts Write responses to: - “we are fine” - “we already have a process” - “not a priority” - “we do this manually” - “we built something internally” - “our current vendor is good enough” 5. Deal decision Recommend when to advance, nurture, or disqualify. Rules: - Do not insult the current process. - Do not assume the status quo is bad. - Do not force change where there is no pain. - The goal is to reveal whether staying the same has a cost. --------------------------------------------------------------------------------

#136Champion Enablement Kit Builder

OBJECTION HANDLING & DEAL ADVANCEMENTMulti-stakeholder sales, complex B2B deals, enterprise sales, consulting, SaaS, procurement-heavy deals, and champion-led advancement.

Equip an internal champion with the messaging, proof, business case, objection answers, stakeholder notes, and next-step plan needed to sell internally.

Act as a champion enablement strategist. Build an internal selling kit for my champion at [ACCOUNT]. Deal context: Account: [ACCOUNT] Champion: [CHAMPION] Champion role: [ROLE] Offer: [OFFER] Problem discussed: [PROBLEM] Business impact: [IMPACT] Desired outcome: [OUTCOME] Known stakeholders: [STAKEHOLDERS] Known objections: [OBJECTIONS] Decision process: [DECISION PROCESS] Proof assets: [PROOF] Next step: [NEXT STEP] Create the kit: A. Champion briefing Write a concise summary of: - the problem - why it matters - why now - proposed solution - expected outcome - next decision B. Stakeholder-specific talking points Create notes for: - executive sponsor - finance - procurement - technical evaluator - end users - department leader C. Internal objection FAQ Create answers to likely internal objections: - price - timing - risk - implementation - current vendor - priority - security - adoption - proof D. Forwardable assets Write: - internal email - executive summary - one-slide business case - meeting invite blurb - decision criteria checklist E. Champion coaching Tell the champion: - who to involve - what to ask - what risk to watch - what proof to share - when to bring us back in Rules: - Do not make the champion do all the work. - Do not overload the champion with too much material. - Do not assume the champion knows how to sell internally. - A champion needs simple, credible, forwardable support. --------------------------------------------------------------------------------

#137Objection Handling Roleplay Simulator

OBJECTION HANDLING & DEAL ADVANCEMENTSales training, SDR coaching, AE practice, founder sales practice, objection drills, onboarding, and call preparation.

Practice live objection handling through realistic buyer roleplay, coaching feedback, better responses, and deal advancement recommendations.

You are a realistic buyer and sales coach. Run an objection handling roleplay for selling [OFFER] to [BUYER PERSONA]. Roleplay setup: Offer: [OFFER] Buyer persona: [BUYER PERSONA] Account type: [ACCOUNT TYPE] Sales stage: [STAGE] Buyer pain: [PAIN] Buyer personality: [PERSONALITY] Objections to practice: [OBJECTIONS] Difficulty level: [EASY / MEDIUM / HARD] Goal of roleplay: [GOAL] Run the roleplay in this format: 1. Buyer scene Set the situation: - who the buyer is - what they care about - what they are skeptical about - what they are not saying openly 2. Roleplay round Ask one buyer objection at a time. After I respond, evaluate: - what worked - what was weak - what I missed - whether I diagnosed before responding - whether I advanced the deal - better version of my response - follow-up question I should ask 3. Objection progression Use objections from these categories: - price - timing - authority - budget - competition - trust - implementation - urgency - internal buy-in - risk 4. Scoring After the full roleplay, score: - composure - diagnosis - empathy - clarity - value reframe - proof use - next-step control - overall deal advancement 5. Practice plan Give 5 drills to improve my weakest areas. Rules: - Do not reveal the perfect answer before I respond. - Make the buyer realistic, not hostile for no reason. - Do not accept vague seller answers. - The goal is better live judgment, not memorized scripts. --------------------------------------------------------------------------------

#138Deal Advancement Decision Tree

OBJECTION HANDLING & DEAL ADVANCEMENTPipeline management, sales coaching, stage progression, deal reviews, CRM process design, and reducing stalled opportunities.

Create a decision tree that tells sellers what to do next based on objection type, buyer response, stakeholder status, urgency, budget, and deal risk.

Act as a deal advancement architect. Create a decision tree for moving opportunities forward after objections appear. Deal context: Offer: [OFFER] Sales process stages: [STAGES] Current opportunity stage: [CURRENT STAGE] Buyer persona: [BUYER] Common objections: [OBJECTIONS] Qualification criteria: [CRITERIA] Next-step options: [NEXT STEP OPTIONS] Disqualification rules: [DISQUALIFICATION] CRM fields: [CRM FIELDS] Build the decision tree: Start with the objection type: - price - timing - budget - authority - trust - competition - implementation - risk - procurement - technical fit - internal buy-in - no urgency - ghosting For each path include: 1. Clarify What question must the seller ask first? 2. Diagnose What answer indicates: - real blocker - solvable concern - hidden objection - weak deal - disqualification 3. Respond What message, proof, or asset should be used? 4. Advance Choose next action: - book next call - involve stakeholder - send business case - run technical review - send proof - create mutual action plan - move to nurture - close-lost - disqualify 5. CRM update Define: - stage change - risk tag - next action date - owner - notes required Rules: - Do not advance deals without evidence. - Do not keep unclear deals in late-stage pipeline. - Do not treat objections the same across all deal stages. - The decision tree should make next actions obvious. --------------------------------------------------------------------------------

#139Mutual Action Plan for Stuck Deals

OBJECTION HANDLING & DEAL ADVANCEMENTLate-stage deals, enterprise sales, procurement processes, multi-stakeholder opportunities, proposal follow-up, and forecast control.

Create a mutual action plan that turns objections into clear owners, dates, decisions, documents, stakeholder meetings, and closing milestones.

You are a mutual action plan specialist. Build a practical action plan to move this deal from objection to decision. Deal context: Account: [ACCOUNT] Offer: [OFFER] Buyer: [BUYER] Current stage: [STAGE] Target close date: [TARGET DATE] Main objection: [OBJECTION] Known stakeholders: [STAKEHOLDERS] Decision process: [DECISION PROCESS] Procurement steps: [PROCUREMENT] Technical steps: [TECHNICAL STEPS] Legal steps: [LEGAL] Commercial steps: [COMMERCIAL] Current risks: [RISKS] Create the mutual action plan: A. Decision goal Define: - what decision needs to be made - who makes it - by when - what evidence is needed B. Milestone plan Create a table with: - milestone - owner - buyer owner - seller owner - date - required input - output - risk - fallback action C. Objection resolution steps Break the objection into: - information needed - stakeholder needed - proof needed - decision needed - deadline D. Communication plan Create: - buyer-facing MAP email - weekly update format - escalation note - reminder message - missed-deadline recovery message E. Forecast recommendation Assess: - confidence level - close risk - missing evidence - forecast category - next manager action Rules: - Do not create a mutual action plan that only the seller owns. - Do not set fake dates. - Do not ignore procurement, legal, or technical dependencies. - A mutual action plan should make progress visible. --------------------------------------------------------------------------------

#140Full Objection Handling and Deal Advancement Audit

OBJECTION HANDLING & DEAL ADVANCEMENTSales leaders, founders, account executives, SDR managers, RevOps teams, consultants, agencies, SaaS companies, and teams improving pipeline conversion.

Audit and rebuild the complete objection handling and deal advancement system across price, timing, trust, competition, budget, authority, risk, implementation, internal buy-in, procurement, follow-up, and next-step control.

Act as an independent objection handling and deal advancement auditor. Review my current sales process and rebuild it into a stronger system for handling objections and moving qualified deals forward. Full context: Company: [COMPANY] Website: [WEBSITE] Offer: [OFFER] Target market: [MARKET] ICP: [ICP] Buyer personas: [PERSONAS] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Current sales process: [SALES PROCESS] Current objection list: [OBJECTIONS] Current objection responses: [RESPONSES] Current follow-up messages: [FOLLOW-UPS] Current proposal process: [PROPOSAL PROCESS] Current negotiation process: [NEGOTIATION] Current procurement process: [PROCUREMENT] Current CRM stages: [CRM STAGES] Current conversion rates: [CONVERSION RATES] Stalled deal examples: [STALLED DEALS] Closed-won insights: [CLOSED WON] Closed-lost insights: [CLOSED LOST] Discount policy: [DISCOUNT POLICY] Proof assets: [PROOF] Main deal advancement problems: [PROBLEMS] Audit across 40 dimensions: 1. Objection diagnosis quality 2. Price objection handling 3. Budget objection handling 4. Timing objection handling 5. Trust objection handling 6. Competition objection handling 7. Authority objection handling 8. Internal buy-in handling 9. Implementation risk handling 10. Technical objection handling 11. Security objection handling 12. Procurement objection handling 13. Legal objection handling 14. Status quo objection handling 15. No-urgency handling 16. “Send me info” handling 17. Ghosted deal recovery 18. Discount request handling 19. Risk reversal strategy 20. Proof usage 21. ROI explanation 22. Cost of inaction explanation 23. Champion enablement 24. Stakeholder mapping 25. Multi-threading 26. Executive alignment 27. Mutual action plans 28. Next-step clarity 29. Follow-up quality 30. Proposal readiness 31. Negotiation discipline 32. Deal qualification discipline 33. Disqualification discipline 34. CRM risk tracking 35. Forecast accuracy 36. Manager deal coaching 37. Seller confidence 38. Buyer experience 39. Sales enablement assets 40. Overall deal advancement maturity For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - revenue impact - deal risk - recommended fix - priority - effort - confidence level Then synthesize: A. Hard truth Explain the biggest reason deals are slowing down, stalling, discounting, or going to no-decision. B. Rebuilt objection handling system Create: - objection diagnosis framework - price response framework - timing response framework - trust response framework - competitive response framework - implementation risk response - internal buy-in response - discount response - ghosted deal recovery path C. Deal advancement operating system Create: - deal review checklist - stakeholder map template - mutual action plan template - champion enablement kit - next-step rules - CRM risk fields - proof selection guide - disqualification rules D. 30-day improvement roadmap Create: - first 24-hour cleanup - first 7-day response rewrite - first 14-day sales coaching plan - first 30-day implementation plan - metrics to track - owner assignments E. Executive summary Write a direct summary with: - fastest win - highest-risk objection - first response to rewrite - first proof asset to build - first deal stage rule to fix - first coaching drill to run - first CRM field to add - one operating principle for advancing deals Rules: - Do not teach sellers to pressure buyers. - Do not keep bad-fit deals alive with clever objection handling. - Do not discount before diagnosing value, authority, and timing. - Use [NEEDS DATA], [NEEDS SALES FEEDBACK], [NEEDS LEGAL REVIEW], [NEEDS PROCUREMENT REVIEW], or [NEEDS MANAGER COACHING] where required. - The final system should improve buyer clarity, seller confidence, pipeline quality, and deal progression.

#141Proposal Strategy Architect

PROPOSALS, PRICING & NEGOTIATIONB2B proposals, SaaS deals, consulting proposals, agency proposals, enterprise sales, founder-led sales, and proposal-heavy sales processes.

Build a sales proposal strategy that turns discovery insights into a clear recommendation, value narrative, scope, pricing logic, risks, proof, and next-step plan.

You are a senior proposal strategist. Build a proposal strategy for selling [OFFER] to [BUYER / ACCOUNT]. Deal context: Offer: [OFFER] Buyer: [BUYER] Account: [ACCOUNT] Industry: [INDUSTRY] Sales stage: [STAGE] Discovery notes: [DISCOVERY NOTES] Buyer pain: [PAIN] Business impact: [IMPACT] Desired outcome: [OUTCOME] Decision criteria: [DECISION CRITERIA] Known stakeholders: [STAKEHOLDERS] Known objections: [OBJECTIONS] Budget context: [BUDGET] Competitors or alternatives: [COMPETITORS] Proof available: [PROOF] Proposed price range: [PRICE RANGE] Desired next step: [NEXT STEP] Build the proposal strategy: 1. Proposal goal Define: - what decision the proposal must help the buyer make - what uncertainty the proposal must reduce - what internal conversation the proposal must support - what the buyer must believe after reading it - what the proposal should not try to do 2. Buyer-centered proposal angle Create: - core problem statement - business impact statement - future-state statement - value thesis - reason to act now - reason to choose this approach 3. Recommended proposal structure Create the proposal sections in order: - executive summary - buyer situation - problem and impact - recommended solution - scope - deliverables - timeline - investment - expected value - proof - risks and assumptions - next steps 4. Section-by-section guidance For each section provide: - purpose - key message - exact content to include - what to avoid - proof or data needed - buyer question it answers 5. Proposal advancement plan Create: - who should receive the proposal - how to present it live - what to say before sending - follow-up timing - decision meeting agenda - CRM notes to update Rules: - Do not write a generic proposal. - Do not lead with deliverables before business value. - Do not hide assumptions. - The proposal should confirm a decision path, not replace discovery. --------------------------------------------------------------------------------

#142Executive Summary Proposal Writer

PROPOSALS, PRICING & NEGOTIATIONProposal openings, board-ready sales documents, enterprise proposals, consulting proposals, agency proposals, and executive-facing deal communication.

Write a sharp executive summary that explains the buyer’s situation, why it matters, what is recommended, what value is expected, and what decision is needed.

Act as an executive proposal writer. Create an executive summary for a proposal that a senior buyer can understand quickly and forward internally. Inputs: Buyer company: [COMPANY] Buyer role: [BUYER ROLE] Offer: [OFFER] Current situation: [CURRENT SITUATION] Pain points: [PAINS] Business impact: [IMPACT] Desired outcome: [OUTCOME] Recommended solution: [SOLUTION] Investment: [INVESTMENT] Timeline: [TIMELINE] Proof: [PROOF] Risks or assumptions: [RISKS / ASSUMPTIONS] Decision needed: [DECISION] Write the executive summary in this structure: A. Situation in one paragraph Explain what is happening in the buyer’s business. B. Why it matters Connect the issue to: - revenue - cost - speed - risk - customer experience - team productivity - strategic priority C. Recommended path Explain what we recommend and why. D. Expected value State the expected value clearly, separating: - proven facts - reasonable assumptions - value still to validate E. Investment and commitment Explain the investment, timeline, and buyer responsibilities. F. Decision request End with the specific decision or next step required. Create 3 versions: - concise version under 180 words - detailed version under 350 words - CFO-friendly version focused on business case Also provide: - 5 stronger opening lines - 5 weaker phrases to avoid - 5 internal-forwarding subject lines - one paragraph the champion can paste into an internal email Rules: - Do not use hype. - Do not overpromise results. - Do not include unnecessary company history. - The executive summary must make the proposal easier to approve. --------------------------------------------------------------------------------

#143Scope and Deliverables Clarifier

PROPOSALS, PRICING & NEGOTIATIONService proposals, consulting engagements, agency retainers, implementation projects, SaaS onboarding, custom projects, and preventing scope creep.

Turn vague deal discussions into a precise scope with deliverables, responsibilities, exclusions, dependencies, assumptions, and change-control rules.

You are a scope definition specialist. Convert the messy deal context below into a clean proposal scope that protects both buyer and seller. Context: Offer: [OFFER] Buyer: [BUYER] Problem to solve: [PROBLEM] Desired outcome: [OUTCOME] Requested deliverables: [REQUESTED DELIVERABLES] Seller responsibilities: [SELLER RESPONSIBILITIES] Buyer responsibilities: [BUYER RESPONSIBILITIES] Timeline: [TIMELINE] Resources available: [RESOURCES] Known constraints: [CONSTRAINTS] Possible scope creep risks: [RISKS] Pricing model: [PRICING MODEL] Build the scope: 1. Scope statement Write a plain-English scope summary. 2. Deliverables table Create a table with: - deliverable - description - format - owner - due date or phase - acceptance criteria - dependency - excluded items 3. Buyer responsibilities List what the buyer must provide: - access - data - approvals - feedback - stakeholders - technical resources - decision support 4. Exclusions Write a clear exclusion list for anything not included. 5. Assumptions State assumptions about: - timelines - data availability - stakeholder access - approval speed - platform limitations - change requests 6. Change-control language Write proposal-ready language explaining how additional requests will be handled. 7. Scope risk notes Identify the top 10 risks that could create scope creep and how to prevent them. Rules: - Do not leave ambiguous deliverables. - Do not promise unlimited revisions or support unless explicitly included. - Do not hide buyer responsibilities. - A strong scope should reduce misunderstandings before the deal is signed. --------------------------------------------------------------------------------

#144Pricing Architecture Designer

PROPOSALS, PRICING & NEGOTIATIONSaaS pricing, consulting offers, agency retainers, implementation quotes, enterprise proposals, tiered packages, and custom pricing.

Design a pricing structure that matches buyer value, scope, risk, margin needs, packaging logic, and negotiation flexibility.

Act as a pricing architect. Design a pricing structure for [OFFER] that is easy to understand, defensible, and aligned with buyer value. Inputs: Offer: [OFFER] Target buyer: [BUYER] Use case: [USE CASE] Scope options: [SCOPE OPTIONS] Value created: [VALUE] Costs to deliver: [COSTS] Margin target: [MARGIN] Competitor pricing: [COMPETITOR PRICING] Buyer budget range: [BUDGET] Sales cycle: [SALES CYCLE] Implementation effort: [EFFORT] Support level: [SUPPORT] Risk level: [RISK] Preferred pricing model: [MODEL] Design the pricing architecture: A. Pricing model options Evaluate: - fixed fee - retainer - subscription - usage-based - per-seat - per-location - milestone-based - performance-based - hybrid - enterprise custom For each provide: - fit score - buyer clarity - seller risk - margin potential - negotiation flexibility - when to use - when to avoid B. Recommended pricing structure Create: - package name - included scope - price - billing terms - implementation fee - optional add-ons - renewal logic - expansion logic C. Value justification Explain the price using: - business outcome - cost of inaction - operational savings - risk reduction - speed to value - proof D. Negotiation guardrails Define: - floor price - acceptable concessions - non-negotiables - scope tradeoffs - payment term tradeoffs - approval needed for exceptions E. Buyer explanation Write a proposal-ready pricing explanation. Rules: - Do not choose a pricing model only because it is common. - Do not make pricing so complex that buyers cannot approve it. - Do not price below delivery risk. - Pricing should reflect value, cost, risk, and strategic fit. --------------------------------------------------------------------------------

#145Quote Structure and Line-Item Builder

PROPOSALS, PRICING & NEGOTIATIONFormal quotes, service estimates, SaaS quotes, implementation pricing, procurement documents, agency proposals, and sales operations.

Create a clean quote with line items, descriptions, quantities, terms, optional add-ons, exclusions, and pricing notes that buyers can understand.

You are a quote structure specialist. Build a buyer-friendly quote for [OFFER]. Quote context: Buyer: [BUYER] Company: [COMPANY] Offer: [OFFER] Scope: [SCOPE] Deliverables: [DELIVERABLES] Pricing model: [PRICING MODEL] Base price: [BASE PRICE] Add-ons: [ADD-ONS] Discounts, if any: [DISCOUNTS] Billing schedule: [BILLING] Contract term: [TERM] Implementation fees: [IMPLEMENTATION] Taxes or fees: [TAXES / FEES] Validity period: [VALIDITY] Terms: [TERMS] Create the quote: 1. Quote summary Write a concise summary of what the quote includes. 2. Line-item table Create a table with: - item - description - quantity - unit price - total price - billing timing - notes 3. Optional add-ons List add-ons separately with: - buyer benefit - price - when recommended - whether optional or required 4. Exclusions and assumptions Clarify: - not included - buyer responsibilities - dependencies - assumptions - expiration date - change request process 5. Pricing notes Explain: - why fees are structured this way - what drives cost - where flexibility exists - where flexibility does not exist 6. Buyer-ready language Write a clean pricing section for a proposal or quote document. 7. Internal approval notes Flag anything requiring manager, finance, legal, or delivery review. Rules: - Do not bury fees in vague language. - Do not mix optional and required items without labeling them. - Do not hide implementation or support costs. - A good quote should be easy to approve and hard to misinterpret. --------------------------------------------------------------------------------

#146Value Justification Business Case Builder

PROPOSALS, PRICING & NEGOTIATIONCFO approval, enterprise sales, expensive proposals, procurement discussions, internal champion enablement, and high-ticket offers.

Build a value justification narrative that connects price to measurable business impact, strategic outcomes, risk reduction, and cost of inaction.

Act as a business case advisor. Build a value justification for the proposed investment in [OFFER]. Inputs: Offer: [OFFER] Buyer: [BUYER] Company: [COMPANY] Investment amount: [PRICE] Current pain: [PAIN] Current cost of problem: [COST OF PROBLEM] Desired outcomes: [OUTCOMES] Metrics affected: [METRICS] Proof available: [PROOF] Implementation effort: [EFFORT] Expected timeline to value: [TIMELINE] Assumptions: [ASSUMPTIONS] Decision criteria: [CRITERIA] Build the business case: A. Value thesis Write one clear paragraph explaining why the investment makes business sense. B. Value driver breakdown For each value driver provide: - driver name - current issue - expected improvement - metric affected - confidence level - proof or assumption - buyer data needed Include drivers such as: - revenue lift - cost savings - labor efficiency - faster execution - reduced errors - lower churn - better conversion - reduced risk - improved visibility - improved customer experience C. Cost of inaction Explain what may happen if the buyer delays or does nothing. D. ROI model Create: - low-case scenario - expected-case scenario - high-case scenario - payback logic - sensitivity factors E. Internal approval summary Write a short summary the buyer can send to finance or leadership. F. Caveats List what must be validated before making strong ROI claims. Rules: - Do not fabricate metrics. - Separate facts from assumptions. - Use ranges when exact numbers are missing. - The goal is decision confidence, not inflated ROI. --------------------------------------------------------------------------------

#147Negotiation Preparation Brief

PROPOSALS, PRICING & NEGOTIATIONSales negotiations, proposal reviews, procurement calls, pricing conversations, enterprise deals, consulting contracts, and margin protection.

Prepare a negotiation plan with objectives, tradeable items, non-negotiables, buyer motivations, likely asks, concessions, counters, and walk-away rules.

You are a negotiation preparation coach. Build a negotiation brief for an upcoming conversation with [BUYER / ACCOUNT]. Deal context: Offer: [OFFER] Buyer: [BUYER] Account: [ACCOUNT] Deal size: [DEAL SIZE] Current proposal: [PROPOSAL] Current price: [PRICE] Buyer objections: [OBJECTIONS] Buyer leverage: [BUYER LEVERAGE] Seller leverage: [SELLER LEVERAGE] Competitors: [COMPETITORS] Timeline pressure: [TIMELINE] Margin requirements: [MARGIN] Approval limits: [LIMITS] Desired outcome: [OUTCOME] Create the negotiation brief: 1. Negotiation objective Define: - ideal outcome - acceptable outcome - minimum acceptable outcome - walk-away point - relationship goal 2. Buyer motivation analysis Identify: - what buyer wants - what buyer fears - what buyer may use as leverage - what buyer actually needs - what buyer may be testing 3. Give-get matrix Create a table with: - buyer ask - possible concession - seller ask in return - value to buyer - cost to seller - approval required - risk 4. Non-negotiables Define: - pricing floor - scope limits - legal limits - delivery limits - support limits - timeline limits 5. Response scripts Write responses for: - discount request - competitor price comparison - payment term request - extra scope request - faster timeline request - cancellation clause request - procurement pressure 6. Call plan Create: - opening - questions to ask - issues to confirm - trade options - close language - follow-up email Rules: - Do not concede without receiving value in return. - Do not negotiate against yourself. - Do not reveal the floor too early. - Good negotiation protects value while helping the buyer move forward. --------------------------------------------------------------------------------

#148Discount Boundary and Concession Planner

PROPOSALS, PRICING & NEGOTIATIONSaaS sales, consulting, agencies, enterprise deals, procurement negotiations, renewal pricing, and sales teams protecting margin.

Create discount boundaries, approval rules, concession tradeoffs, scope protection, and language for responding to discount requests.

Act as a discount governance specialist. Build a discount and concession plan for [OFFER]. Inputs: Offer: [OFFER] Standard price: [PRICE] Gross margin target: [MARGIN] Buyer segment: [SEGMENT] Deal size: [DEAL SIZE] Current discount request: [REQUEST] Reason for request: [REASON] Competitive pressure: [COMPETITION] Strategic value of account: [STRATEGIC VALUE] Scope: [SCOPE] Approval rules: [APPROVAL RULES] Non-negotiables: [NON-NEGOTIABLES] Build the discount plan: A. Discount diagnosis Classify the request as: - budget limitation - procurement tactic - value uncertainty - competitor pressure - approval threshold problem - timing incentive opportunity - strategic account investment - weak fit B. Discount tiers Create: - no-discount response - small discount option - medium discount option - strategic discount option - disallowed discount For each include: - required approval - required trade - impact on margin - risk - when appropriate C. Give-get options List trades such as: - annual prepayment - multi-year term - reduced scope - faster signature - public case study - reference call - limited support - fewer seats - phased rollout D. Seller language Write scripts for: - holding price - trading for commitment - reducing scope instead of price - explaining discount policy - saying no respectfully - involving manager approval E. Final recommendation Recommend the best response and why. Rules: - Do not discount to solve unclear value. - Do not give a concession without a buyer commitment. - Do not reduce price while keeping full scope. - Discounting should be controlled, intentional, and documented. --------------------------------------------------------------------------------

#149Procurement Response Pack

PROPOSALS, PRICING & NEGOTIATIONEnterprise sales, late-stage deals, SaaS procurement, vendor onboarding, legal review, finance approval, and complex purchasing processes.

Prepare responses to procurement questions about pricing, vendor risk, terms, documentation, approvals, deadlines, discounts, and process requirements.

You are a procurement-facing sales advisor. Build a response pack for working with procurement on [DEAL / OFFER]. Context: Offer: [OFFER] Account: [ACCOUNT] Procurement contact: [PROCUREMENT CONTACT] Business buyer: [BUSINESS BUYER] Deal size: [DEAL SIZE] Current status: [STATUS] Procurement requirements: [REQUIREMENTS] Commercial terms: [TERMS] Requested concessions: [CONCESSIONS] Documents requested: [DOCUMENTS] Deadline: [DEADLINE] Legal or security issues: [ISSUES] Create the procurement response pack: 1. Procurement process map Create a checklist for: - vendor registration - finance approval - security review - legal review - purchase order - signature - invoicing - implementation kickoff 2. Response templates Write responses for: - pricing justification - discount request - payment terms - contract redlines - vendor risk questionnaire - security documentation request - insurance request - data processing request - deadline pressure - purchase order delay 3. Commercial position Define: - where we can be flexible - where we cannot be flexible - what requires approval - what tradeoffs are acceptable - what risks need escalation 4. Buyer alignment Create language to keep the business sponsor involved and prevent procurement from reframing the deal only around price. 5. Document tracker Create a table with: - document - owner - status - deadline - blocker - next action Rules: - Do not give legal advice. - Use [NEEDS LEGAL REVIEW] for contract terms. - Use [NEEDS SECURITY REVIEW] for security claims. - Procurement should be managed as a process, not treated as an obstacle. --------------------------------------------------------------------------------

#150Contract Positioning and Terms Explainer

PROPOSALS, PRICING & NEGOTIATIONContract discussions, sales proposals, procurement reviews, legal handoffs, SaaS agreements, consulting contracts, and service agreements.

Explain contract terms, commercial logic, service boundaries, renewal terms, cancellation terms, SLAs, responsibilities, and risk allocation in buyer-friendly language.

Act as a contract positioning advisor. Help me explain key commercial terms for [OFFER] in buyer-friendly language without giving legal advice. Contract context: Offer: [OFFER] Buyer: [BUYER] Contract type: [CONTRACT TYPE] Term length: [TERM] Pricing: [PRICING] Payment terms: [PAYMENT TERMS] Renewal terms: [RENEWAL] Cancellation terms: [CANCELLATION] Service levels: [SLA] Buyer responsibilities: [BUYER RESPONSIBILITIES] Seller responsibilities: [SELLER RESPONSIBILITIES] Limitations: [LIMITATIONS] Common buyer concerns: [CONCERNS] Create the terms explainer: A. Plain-English explanation Explain each term: - what it means - why it exists - how it protects both sides - what flexibility may exist - what requires legal review B. Buyer concern responses Write responses to concerns about: - term length - auto-renewal - payment timing - cancellation rights - liability - service levels - support limits - data terms - implementation responsibilities C. Proposal-ready wording Write a commercial terms section for the proposal. D. Internal handoff notes Flag: - terms sales can explain - terms requiring legal - terms requiring finance - terms requiring executive approval E. Negotiation notes Identify: - flexible terms - non-negotiable terms - possible tradeoffs - risks of changing each term Rules: - Do not provide legal advice. - Use [NEEDS LEGAL REVIEW] where legal interpretation is required. - Do not oversimplify terms in a misleading way. - Contract language should create clarity and confidence. --------------------------------------------------------------------------------

#151Proposal Personalization Engine

PROPOSALS, PRICING & NEGOTIATIONAccount-based proposals, enterprise sales, consulting, agencies, SaaS, founder-led sales, and avoiding generic proposal templates.

Personalize a proposal for a specific account using buyer language, discovery notes, stakeholder concerns, industry context, goals, and proof.

You are an account-based proposal personalization expert. Personalize this proposal so it feels written specifically for [ACCOUNT]. Base proposal: [PASTE BASE PROPOSAL] Account context: Account: [ACCOUNT] Industry: [INDUSTRY] Buyer personas: [BUYERS] Discovery notes: [DISCOVERY NOTES] Buyer language: [BUYER LANGUAGE] Pain points: [PAINS] Business goals: [GOALS] Stakeholder concerns: [CONCERNS] Decision criteria: [CRITERIA] Proof most relevant: [PROOF] Competitors: [COMPETITORS] Personalize the proposal: 1. Personalization opportunities Identify where the proposal should be customized: - title - opening - problem statement - business impact - recommended solution - scope - proof - pricing explanation - risks - next steps 2. Buyer-language rewrite Rewrite key sections using the buyer’s own language where appropriate. 3. Stakeholder alignment Adapt sections for: - executive sponsor - economic buyer - technical evaluator - end user - finance/procurement 4. Proof matching Select proof that matches: - industry - use case - company size - buyer pain - risk concern - desired outcome 5. Generic language removal List generic phrases to remove and replace them with specific alternatives. 6. Final personalized version Produce the improved proposal copy. Rules: - Do not fake personalization. - Do not insert irrelevant details just to sound custom. - Do not copy buyer language in a way that sounds unnatural. - Personalization should make the proposal more relevant and easier to approve. --------------------------------------------------------------------------------

#152Proposal Risk and Assumption Register

PROPOSALS, PRICING & NEGOTIATIONComplex proposals, custom projects, implementation-heavy deals, consulting, agencies, enterprise SaaS, legal/procurement review, and delivery handoff.

Identify proposal risks, assumptions, dependencies, scope uncertainties, delivery constraints, buyer responsibilities, and deal risks before sending.

Act as a proposal risk reviewer. Build a risk and assumption register for this proposal before it is sent. Proposal context: Offer: [OFFER] Buyer: [BUYER] Scope: [SCOPE] Timeline: [TIMELINE] Price: [PRICE] Deliverables: [DELIVERABLES] Buyer responsibilities: [BUYER RESPONSIBILITIES] Seller responsibilities: [SELLER RESPONSIBILITIES] Known unknowns: [UNKNOWNS] Implementation constraints: [CONSTRAINTS] Legal or compliance needs: [LEGAL / COMPLIANCE] Delivery team concerns: [DELIVERY CONCERNS] Create the register: 1. Risk categories Identify risks across: - scope - timeline - budget - stakeholder access - data availability - technical dependencies - buyer responsiveness - legal approval - procurement - implementation - adoption - measurement - success criteria 2. Risk table For each risk provide: - risk description - probability - impact - owner - early warning sign - mitigation - proposal language needed - escalation point 3. Assumptions table For each assumption provide: - assumption - why it matters - who must confirm - when to confirm - risk if false - proposal wording 4. Proposal edits Write sections that clarify: - assumptions - dependencies - exclusions - buyer responsibilities - timeline conditions - change-control rules 5. Send/no-send recommendation Recommend whether to send, revise, gather more data, or involve legal/delivery. Rules: - Do not hide material risks. - Do not push delivery risk onto the team after the sale. - Do not use vague assumptions. - A strong proposal makes risk visible before signature. --------------------------------------------------------------------------------

#153Package and Tier Comparison Builder

PROPOSALS, PRICING & NEGOTIATIONSaaS tiers, service packages, consulting options, agency retainers, productized services, enterprise plans, and proposal options.

Create clear pricing tiers or package options that help buyers choose without confusion, over-customization, or unnecessary discounting.

You are a packaging and pricing strategist. Create package options for [OFFER] that help the buyer choose the right level of value. Context: Offer: [OFFER] Buyer: [BUYER] Use cases: [USE CASES] Buyer needs: [NEEDS] Budget range: [BUDGET] Delivery capacity: [CAPACITY] Margin target: [MARGIN] Current package ideas: [PACKAGE IDEAS] Must-include features or services: [MUST INCLUDE] Optional features or services: [OPTIONAL] Expansion path: [EXPANSION] Build the package system: A. Tier strategy Define the purpose of each tier: - entry tier - core recommended tier - premium tier - enterprise/custom tier B. Tier table Create a comparison table with: - package name - best for - included items - excluded items - buyer outcome - price - timeline - support level - implementation level - proof needed - upgrade trigger C. Recommendation logic Explain: - which tier to recommend first - which tier protects margin - which tier reduces risk - which tier may cause confusion - which tier should be removed D. Buyer-facing explanation Write a proposal section that explains the options clearly. E. Sales guidance Create guidance for: - how to present tiers - how to prevent buyers choosing only cheapest option - how to handle custom requests - how to upsell without pressure Rules: - Do not create too many tiers. - Do not make the cheapest tier too valuable. - Do not make tiers differ only by quantity. - Tiers should reflect buyer maturity, value, and implementation needs. --------------------------------------------------------------------------------

#154Payment Terms and Cash Flow Negotiation Guide

PROPOSALS, PRICING & NEGOTIATIONConsulting, agencies, SaaS contracts, implementation projects, enterprise deals, custom work, and finance-sensitive buyers.

Prepare payment terms, billing schedules, deposit requirements, milestone payments, annual prepay options, and cash-flow-friendly negotiation language.

Act as a commercial terms strategist. Build a payment terms guide for negotiating [OFFER] with [BUYER]. Inputs: Offer: [OFFER] Buyer: [BUYER] Price: [PRICE] Contract term: [TERM] Delivery timeline: [TIMELINE] Seller cash-flow needs: [CASH FLOW NEEDS] Buyer payment preference: [BUYER PREFERENCE] Implementation costs: [IMPLEMENTATION COSTS] Margin constraints: [MARGIN] Standard terms: [STANDARD TERMS] Acceptable alternatives: [ALTERNATIVES] Non-negotiables: [NON-NEGOTIABLES] Create the guide: 1. Payment structure options Evaluate: - upfront payment - deposit plus milestones - monthly billing - quarterly billing - annual prepay - usage-based billing - payment after delivery - hybrid structure For each include: - buyer benefit - seller benefit - seller risk - cash-flow impact - when to use - when to avoid 2. Recommended terms Create the best payment structure for this deal. 3. Negotiation scripts Write responses to: - “Can we pay after delivery?” - “Can we do net 60 or net 90?” - “Can we split payments?” - “Can we start now and pay later?” - “Can we avoid an upfront fee?” - “Can we pay monthly instead of annually?” 4. Give-get logic List what the seller should request in exchange for more flexible payment terms. 5. Proposal-ready wording Write the payment terms section. Rules: - Do not accept payment terms that create delivery or cash-flow risk without compensation. - Do not change billing terms without documenting them. - Do not treat payment terms as minor details. - Payment structure should support both buyer approval and seller stability. --------------------------------------------------------------------------------

#155Proposal Review and Redline Response Assistant

PROPOSALS, PRICING & NEGOTIATIONProposal revisions, procurement redlines, legal review, pricing negotiation, stakeholder feedback, complex deals, and late-stage sales.

Respond to buyer feedback, proposal edits, redlines, requested changes, pricing pushback, scope changes, and term objections.

You are a proposal revision and redline response advisor. Help me respond to buyer-requested changes without weakening the deal unnecessarily. Buyer feedback or redlines: [PASTE FEEDBACK / REDLINES] Proposal context: Offer: [OFFER] Buyer: [BUYER] Original scope: [ORIGINAL SCOPE] Original price: [ORIGINAL PRICE] Original terms: [ORIGINAL TERMS] Requested changes: [CHANGES] Deal importance: [DEAL IMPORTANCE] Margin limits: [MARGIN LIMITS] Legal limits: [LEGAL LIMITS] Delivery constraints: [DELIVERY CONSTRAINTS] Negotiation stage: [STAGE] Analyze the feedback: A. Change classification For each requested change classify as: - acceptable - acceptable with tradeoff - needs clarification - needs legal review - needs finance approval - needs delivery review - high risk - reject politely B. Impact analysis For each change explain: - revenue impact - margin impact - delivery impact - legal risk - timeline impact - precedent risk - buyer relationship impact C. Response recommendation Create: - suggested response - counterproposal - trade request - language to avoid - internal reviewer needed D. Revised proposal language Write updated wording for approved changes. E. Buyer email Write a concise email that explains: - changes accepted - changes needing discussion - rationale - next step Rules: - Do not accept redlines blindly. - Use [NEEDS LEGAL REVIEW] where legal interpretation is required. - Use [NEEDS FINANCE REVIEW] where margin or billing changes are material. - Every accepted concession should be intentional. --------------------------------------------------------------------------------

#156Strategic Deal Desk Advisor

PROPOSALS, PRICING & NEGOTIATIONSales leaders, RevOps, finance, deal desk teams, enterprise deals, pricing exceptions, custom proposals, and executive approvals.

Create an internal deal desk review that assesses pricing, margin, risk, approval needs, discounting, scope, legal terms, and close probability.

Act as an internal deal desk advisor. Review this deal and prepare an approval recommendation. Deal context: Account: [ACCOUNT] Offer: [OFFER] Sales owner: [SALES OWNER] Buyer: [BUYER] Deal size: [DEAL SIZE] Standard price: [STANDARD PRICE] Proposed price: [PROPOSED PRICE] Requested discount: [DISCOUNT] Contract term: [TERM] Payment terms: [PAYMENT TERMS] Scope: [SCOPE] Delivery requirements: [DELIVERY] Legal exceptions: [LEGAL EXCEPTIONS] Security requirements: [SECURITY] Strategic value: [STRATEGIC VALUE] Close probability: [CLOSE PROBABILITY] Competitive situation: [COMPETITION] Approval deadline: [DEADLINE] Create the deal desk review: 1. Deal summary Summarize: - buyer problem - proposed solution - commercial structure - requested exceptions - decision deadline 2. Financial analysis Evaluate: - gross revenue - net revenue after discount - margin impact - cash-flow impact - implementation cost - support cost - expansion potential 3. Risk analysis Evaluate: - delivery risk - legal risk - financial risk - procurement risk - reputation risk - strategic risk - precedent risk 4. Approval recommendation Choose: - approve as proposed - approve with conditions - request changes - reject - escalate to executive review 5. Conditions and counters Create: - required buyer commitments - scope changes - payment changes - contract conditions - internal owners 6. Sales response guidance Write seller-facing language for communicating the approved position to the buyer. Rules: - Do not approve discounts without business rationale. - Do not ignore delivery cost. - Do not approve legal exceptions without review. - Deal desk should protect margin, reduce risk, and support good deals. --------------------------------------------------------------------------------

#157Proposal Follow-Up Sequence Builder

PROPOSALS, PRICING & NEGOTIATIONPost-proposal follow-up, stalled proposals, consulting sales, agency deals, SaaS deals, enterprise opportunities, and sales pipeline management.

Create a follow-up sequence after sending a proposal that keeps momentum, surfaces objections, supports internal buy-in, and protects the decision timeline.

You are a post-proposal follow-up strategist. Build a follow-up sequence for a proposal sent to [BUYER / ACCOUNT]. Proposal context: Offer: [OFFER] Buyer: [BUYER] Account: [ACCOUNT] Proposal sent date: [DATE] Proposal amount: [AMOUNT] Main value: [VALUE] Known objections: [OBJECTIONS] Decision process: [DECISION PROCESS] Stakeholders: [STAKEHOLDERS] Expected decision date: [DECISION DATE] Agreed next step: [NEXT STEP] Proof assets: [PROOF] Relationship strength: [RELATIONSHIP] Build the sequence: A. Follow-up principles Define: - how often to follow up - what value to add - when to ask direct questions - when to involve stakeholders - when to close the loop B. Message sequence Write: - same-day proposal recap - 2-day value reinforcement - stakeholder support email - objection-surfacing email - decision-date reminder - procurement/process email - close-the-loop email - nurture fallback email C. Each message must include: - subject line - purpose - body - CTA - when to send - what to do if they respond - what to do if they do not respond D. Internal support assets Recommend: - executive summary - pricing explanation - ROI model - case study - FAQ - implementation plan - comparison table E. Pipeline decision rules Define when to: - keep active - requalify - move to commit - move to nurture - close-lost Rules: - Do not send repeated “checking in” emails. - Do not let the proposal sit without a decision path. - Do not pressure without adding clarity. - Proposal follow-up should help the buyer make progress internally. --------------------------------------------------------------------------------

#158Renewal, Expansion and Upsell Proposal Builder

PROPOSALS, PRICING & NEGOTIATIONCustomer success, account management, SaaS renewals, agency retainers, consulting expansion, service upgrades, and land-and-expand sales.

Create proposals for renewals, expansions, upgrades, additional services, and account growth while protecting value and reducing churn risk.

Act as an account growth proposal strategist. Build a renewal or expansion proposal for [CUSTOMER / ACCOUNT]. Account context: Customer: [CUSTOMER] Current product or service: [CURRENT OFFER] Current contract value: [CURRENT VALUE] Renewal date: [RENEWAL DATE] Current usage: [USAGE] Results achieved: [RESULTS] Customer goals: [GOALS] Problems still unsolved: [UNSOLVED PROBLEMS] Expansion opportunity: [EXPANSION] Proposed new price: [NEW PRICE] Risks: [RISKS] Stakeholders: [STAKEHOLDERS] Relationship health: [HEALTH] Create the proposal: 1. Account success recap Summarize: - original goals - progress made - outcomes achieved - proof of value - customer quote or feedback 2. Current gap analysis Explain: - what is working - what remains limited - what has changed in the customer’s business - what risk exists if they stay at current level 3. Expansion recommendation Present: - recommended upgrade - new scope - new capabilities - expected outcomes - implementation plan - support plan 4. Pricing explanation Explain the price change using: - added value - increased usage - expanded scope - improved outcome - service level - strategic priority 5. Objection handling Prepare responses to: - price increase - no budget - current plan is enough - need to evaluate competitors - adoption concerns - internal approval 6. Renewal close plan Create: - timeline - decision date - stakeholder plan - mutual action plan - follow-up sequence Rules: - Do not treat renewal as automatic. - Do not ask for expansion without proving current value. - Do not hide price increases. - Growth proposals should connect past value to future opportunity. --------------------------------------------------------------------------------

#159Proposal Quality Control Checklist

PROPOSALS, PRICING & NEGOTIATIONProposal QA, sales managers, founders, RevOps, agencies, consultants, SaaS teams, and high-stakes proposal reviews.

Audit a proposal before sending to ensure it is clear, buyer-specific, value-based, priced correctly, scoped safely, proof-backed, and easy to approve.

You are a strict proposal quality reviewer. Audit this proposal before it is sent. Proposal draft: [PASTE PROPOSAL] Deal context: Offer: [OFFER] Buyer: [BUYER] Account: [ACCOUNT] Discovery notes: [DISCOVERY NOTES] Buyer pain: [PAIN] Decision criteria: [CRITERIA] Price: [PRICE] Scope: [SCOPE] Known objections: [OBJECTIONS] Desired next step: [NEXT STEP] Score the proposal across 20 criteria: 1. Buyer-specific opening 2. Problem clarity 3. Business impact 4. Value thesis 5. Recommended solution 6. Scope clarity 7. Deliverable clarity 8. Buyer responsibilities 9. Timeline realism 10. Pricing clarity 11. Value justification 12. Proof relevance 13. Risk and assumptions 14. Exclusions 15. Implementation clarity 16. Differentiation 17. Objection coverage 18. Decision path 19. Next-step clarity 20. Overall approval readiness For each criterion provide: - score from 1 to 10 - what works - what is weak - exact fix - revised wording if needed Then provide: - top 5 edits before sending - sections to remove - sections to add - vague phrases to replace - risk warnings - final send/no-send recommendation Rules: - Do not make the proposal longer unless it becomes clearer. - Do not add unsupported claims. - Do not ignore scope or pricing ambiguity. - A proposal is ready only when the buyer can understand, justify, and approve it. --------------------------------------------------------------------------------

#160Full Proposals, Pricing and Negotiation Audit

PROPOSALS, PRICING & NEGOTIATIONSales leaders, founders, agencies, consultants, SaaS companies, RevOps teams, deal desk teams, account executives, and companies improving close rates while protecting margin.

Audit and rebuild the complete proposal, pricing, quote, negotiation, discounting, procurement, terms, follow-up, and deal desk system.

Act as an independent proposals, pricing, and negotiation auditor. Review my current system and rebuild it into a stronger commercial process that improves close probability while protecting margin. Full context: Company: [COMPANY] Website: [WEBSITE] Offer: [OFFER] Target market: [MARKET] ICP: [ICP] Buyer personas: [PERSONAS] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Current proposal template: [PROPOSAL TEMPLATE] Current quote format: [QUOTE FORMAT] Current pricing model: [PRICING MODEL] Current packages or tiers: [PACKAGES] Current discount policy: [DISCOUNT POLICY] Current negotiation process: [NEGOTIATION PROCESS] Current procurement process: [PROCUREMENT PROCESS] Current contract terms: [TERMS] Current approval rules: [APPROVAL RULES] Current proposal follow-up process: [FOLLOW-UP PROCESS] Win/loss insights: [WIN LOSS] Common objections: [OBJECTIONS] Margin targets: [MARGIN] Delivery constraints: [CONSTRAINTS] Legal constraints: [LEGAL] Main commercial problems: [PROBLEMS] Audit across 40 dimensions: 1. Proposal strategy 2. Executive summary strength 3. Buyer problem clarity 4. Business impact clarity 5. Value thesis 6. Solution recommendation 7. Scope definition 8. Deliverable clarity 9. Buyer responsibilities 10. Exclusions 11. Assumptions 12. Timeline realism 13. Pricing model fit 14. Pricing clarity 15. Quote structure 16. Tier/package logic 17. Value justification 18. ROI explanation 19. Cost of inaction 20. Proof relevance 21. Risk disclosure 22. Implementation clarity 23. Differentiation 24. Competitive positioning 25. Discount governance 26. Concession discipline 27. Negotiation preparation 28. Give-get logic 29. Payment terms 30. Procurement handling 31. Contract positioning 32. Legal handoff 33. Deal desk approval 34. Margin protection 35. Proposal follow-up 36. Stakeholder enablement 37. Renewal/expansion proposal quality 38. CRM documentation 39. Sales manager review 40. Overall commercial readiness For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - revenue impact - margin impact - deal risk - recommended fix - priority - effort - confidence level Then synthesize: A. Hard truth Explain the biggest reason proposals, pricing, or negotiations are weakening close probability or margin. B. Rebuilt proposal system Create: - improved proposal structure - improved executive summary framework - improved scope section - improved pricing explanation - improved value justification - improved risk and assumptions section - improved next-step section C. Rebuilt pricing and negotiation system Create: - pricing architecture - discount boundary policy - give-get matrix - negotiation prep brief - procurement response plan - payment terms guide - deal desk approval rules D. Proposal operating kit Create: - proposal QA checklist - quote template - internal approval checklist - redline response guide - follow-up sequence - champion-forwardable summary - CRM fields to track E. 30-day improvement roadmap Create: - first 24-hour cleanup - first 7-day proposal rewrite plan - first 14-day pricing governance plan - first 30-day negotiation enablement plan - metrics to track - owner assignments F. Executive summary Write a direct summary with: - fastest proposal improvement - highest margin risk - first pricing fix - first negotiation rule - first discount control - first procurement process fix - first follow-up change - one operating principle for better commercial deals Rules: - Do not optimize only for close rate while damaging margin. - Do not hide deal risk inside vague proposal language. - Do not discount without a documented give-get. - Use [NEEDS DATA], [NEEDS FINANCE REVIEW], [NEEDS LEGAL REVIEW], [NEEDS DELIVERY REVIEW], or [NEEDS MANAGER APPROVAL] where required. - The final system should make proposals clearer, pricing more defensible, negotiations more disciplined, and deals easier to approve.

#161Close Readiness Diagnostic

CLOSING, FOLLOW-UP & PIPELINE ACCELERATIONAccount executives, founders, sales managers, consultants, agencies, SaaS teams, and anyone who needs to separate real closing opportunities from optimistic pipeline.

Determine whether a deal is truly ready to close by checking pain, value, urgency, budget, authority, risk, decision process, legal/procurement, and next-step commitment.

You are a senior sales closing strategist. Diagnose whether this opportunity is actually ready to close or still needs more deal work. Deal context: Offer: [OFFER] Account: [ACCOUNT] Buyer: [BUYER] Current deal stage: [STAGE] Deal size: [DEAL SIZE] Target close date: [TARGET CLOSE DATE] Pain discussed: [PAIN] Business impact: [IMPACT] Value discussed: [VALUE] Decision process: [DECISION PROCESS] Stakeholders involved: [STAKEHOLDERS] Budget status: [BUDGET] Known objections: [OBJECTIONS] Legal/procurement status: [LEGAL / PROCUREMENT] Last next step: [LAST NEXT STEP] Recent buyer activity: [BUYER ACTIVITY] Forecast category: [FORECAST CATEGORY] Run the close readiness diagnostic: 1. Close evidence review Assess whether we have clear evidence for: - real pain - quantified impact - compelling event - decision owner - budget path - buying criteria - internal champion - stakeholder alignment - procurement path - legal path - implementation confidence - final decision timeline 2. Readiness score Score the deal from 1 to 100 across: - need - value - urgency - authority - budget - stakeholder coverage - risk resolution - mutual next step - procurement/legal progress - buyer commitment 3. Missing evidence List: - information not yet confirmed - assumptions being made - stakeholders not yet engaged - unresolved objections - weak signals - forecast risks 4. Close path recommendation Choose one: - close-ready - closeable with specific actions - needs requalification - needs stakeholder alignment - needs procurement/legal work - likely stalled - should move to nurture - should close-lost 5. Next 5 actions Create the exact next 5 actions with: - owner - message or call objective - asset needed - deadline - success signal - risk if skipped Rules: - Do not treat verbal interest as close readiness. - Do not assume budget or authority if not confirmed. - Do not recommend closing pressure when the buyer still lacks clarity. - A deal is close-ready only when the buyer has a real decision path. --------------------------------------------------------------------------------

#162Non-Pushy Closing Conversation Script

CLOSING, FOLLOW-UP & PIPELINE ACCELERATIONConsultative sales, founder-led sales, service sales, SaaS sales, proposal calls, late-stage meetings, and relationship-based closing.

Create a natural closing conversation that confirms fit, addresses remaining concerns, aligns on value, and asks for a decision without pressure tactics.

Act as a consultative closing coach. Write a closing conversation script for [OFFER] that feels confident, clear, and respectful. Inputs: Offer: [OFFER] Buyer: [BUYER] Account: [ACCOUNT] Deal stage: [STAGE] Pain confirmed: [PAIN] Desired outcome: [OUTCOME] Value case: [VALUE CASE] Proposal or price: [PRICE] Known concerns: [CONCERNS] Stakeholders: [STAKEHOLDERS] Decision timeline: [TIMELINE] Preferred tone: [TONE] Build the script: A. Fit recap Write a short recap that confirms: - what the buyer wants to solve - why it matters - what outcome they want - why the recommended solution fits B. Concern check Create 8 questions that surface final hesitation before asking for a decision. C. Decision invitation Write 5 closing asks: - direct but respectful - consultative - executive-level - soft close - mutual-plan close D. Response paths Write responses for when the buyer says: - yes - maybe - not yet - we need to think - send this to finance - we need another stakeholder - timing is not right - price is still a concern E. Next-step lock Create language that confirms: - owner - action - date - required documents - internal decision milestone - fallback if delayed Rules: - Do not use manipulative urgency. - Do not ignore unresolved objections. - Do not talk past the buyer’s hesitation. - The close should feel like a clear decision conversation, not a trap. --------------------------------------------------------------------------------

#163Follow-Up Sequence After Final Meeting

CLOSING, FOLLOW-UP & PIPELINE ACCELERATIONLate-stage sales, proposal review meetings, demo follow-ups, executive calls, procurement handoffs, and stalled final decisions.

Build a follow-up sequence after a final sales meeting that keeps momentum, reinforces value, supports internal buy-in, confirms decision timing, and prevents ghosting.

You are a late-stage follow-up strategist. Create a follow-up sequence after a final sales meeting with [BUYER / ACCOUNT]. Meeting context: Offer: [OFFER] Account: [ACCOUNT] Buyer: [BUYER] Meeting date: [DATE] Meeting type: [MEETING TYPE] What was discussed: [DISCUSSION] Value confirmed: [VALUE] Decision criteria: [CRITERIA] Remaining concerns: [CONCERNS] Stakeholders present: [STAKEHOLDERS PRESENT] Stakeholders missing: [STAKEHOLDERS MISSING] Decision timeline: [TIMELINE] Agreed next step: [NEXT STEP] Assets available: [ASSETS] Create the follow-up sequence: 1. Same-day recap Write a concise email that includes: - what was confirmed - remaining open items - agreed next step - owner and date - useful resource 2. Value reinforcement message Write a message that reminds the buyer why the decision matters without sounding pushy. 3. Stakeholder support message Write a forwardable summary for internal sharing. 4. Concern-surfacing message Write a message that invites honest hesitation. 5. Decision-date reminder Write a message that references the agreed timeline and asks what is needed to stay on track. 6. Close-the-loop message Write a respectful message if the buyer goes quiet. For each message include: - subject line - when to send - body - CTA - what to do if they reply - what to do if they do not reply Rules: - Do not send generic “just checking in” emails. - Do not add pressure without adding clarity. - Do not let the buyer carry all internal communication alone. - Every follow-up must either clarify, support, or advance the decision. --------------------------------------------------------------------------------

#164Stalled Deal Requalification Framework

CLOSING, FOLLOW-UP & PIPELINE ACCELERATIONPipeline cleanup, stuck opportunities, sales management, RevOps, no-response prospects, long sales cycles, and forecast discipline.

Requalify a stalled deal to determine whether it should be accelerated, nurtured, closed-lost, or rebuilt with a stronger business case.

Act as a stalled pipeline analyst. Requalify this deal and tell me what to do next. Opportunity context: Account: [ACCOUNT] Offer: [OFFER] Buyer: [BUYER] Deal value: [VALUE] Current stage: [STAGE] Days in stage: [DAYS IN STAGE] Last meaningful interaction: [LAST INTERACTION] Last buyer commitment: [COMMITMENT] Pain identified: [PAIN] Urgency identified: [URGENCY] Budget status: [BUDGET] Authority status: [AUTHORITY] Stakeholders: [STAKEHOLDERS] Main objection: [OBJECTION] Competitors: [COMPETITORS] Forecast category: [FORECAST] Requalify the deal: A. Stall diagnosis Choose the most likely cause: - weak pain - weak urgency - no budget - missing decision-maker - hidden competitor - internal priority changed - poor champion - unresolved risk - procurement delay - no next-step ownership - seller overestimated interest B. Evidence table Create a table with: - positive signal - negative signal - missing evidence - confidence level - meaning for forecast C. Requalification questions Write questions to ask the buyer that test: - current priority - decision timeline - stakeholder alignment - budget path - concern level - next-step seriousness D. Recovery plan Create: - one email - one call opener - one LinkedIn message - one executive reframe - one close-lost message E. Recommendation Choose: - accelerate - requalify live - move to nurture - close-lost - rebuild business case - involve manager - involve executive sponsor Rules: - Do not keep stale deals active because they once showed interest. - Do not forecast a deal without recent buyer commitment. - Do not chase indefinitely. - A stalled deal must either regain evidence or leave active pipeline. --------------------------------------------------------------------------------

#165Ethical Urgency Builder

CLOSING, FOLLOW-UP & PIPELINE ACCELERATIONLate-stage deals, timing objections, no-decision prevention, consultative selling, B2B sales, and pipeline acceleration.

Create real urgency by clarifying business consequences, decision milestones, opportunity cost, internal deadlines, and cost of delay without using fake scarcity.

You are an ethical urgency strategist. Build a non-pushy urgency plan for [DEAL / OFFER]. Context: Offer: [OFFER] Buyer: [BUYER] Account: [ACCOUNT] Problem: [PROBLEM] Current impact: [IMPACT] Desired outcome: [OUTCOME] Known deadline: [DEADLINE] Potential cost of delay: [COST OF DELAY] Competing priorities: [PRIORITIES] Decision process: [DECISION PROCESS] Current urgency level: [URGENCY LEVEL] Buyer timing objection: [TIMING OBJECTION] Create the urgency plan: 1. Urgency source analysis Identify which urgency sources are real: - financial cost - operational delay - customer impact - compliance risk - seasonal deadline - leadership priority - contract renewal - headcount constraint - competitive pressure - missed revenue window - implementation timeline 2. Cost-of-delay questions Create questions that help the buyer quantify: - what happens if nothing changes - how long the problem can continue - who is affected - what internal deadline matters - what opportunity is missed - what gets harder later 3. Urgency narrative Write a clear explanation of why timing matters based only on known facts. 4. Decision milestone plan Create a timeline with: - decision date - approval date - contract date - implementation date - value realization date - fallback date 5. Buyer-safe language Write phrases that create clarity without pressure. Rules: - Do not invent deadlines. - Do not use fake scarcity. - Do not shame the buyer for waiting. - Ethical urgency is based on consequences the buyer already cares about. --------------------------------------------------------------------------------

#166Decision Deadline Management System

CLOSING, FOLLOW-UP & PIPELINE ACCELERATIONEnterprise sales, proposal follow-up, procurement-heavy deals, sales managers, complex approvals, and deals with target close dates.

Manage decision deadlines by defining owners, milestones, risks, fallback actions, reminder messages, and escalation paths.

Act as a decision deadline manager. Build a system to keep this deal moving toward a real decision date. Deal context: Account: [ACCOUNT] Offer: [OFFER] Buyer: [BUYER] Target decision date: [DECISION DATE] Target contract date: [CONTRACT DATE] Implementation start date: [IMPLEMENTATION DATE] Decision process: [DECISION PROCESS] Stakeholders: [STAKEHOLDERS] Procurement steps: [PROCUREMENT] Legal steps: [LEGAL] Open risks: [RISKS] Current owner: [OWNER] Current status: [STATUS] Build the deadline system: A. Deadline reality check Assess whether the date is: - buyer-owned - seller-created - tied to a business event - tied to procurement - tied to implementation - unrealistic - unsupported by evidence B. Milestone tracker Create a table with: - milestone - owner - due date - required input - output - dependency - risk - fallback action C. Reminder messages Write messages for: - one week before deadline - three days before deadline - day of deadline - missed deadline - new deadline request - stakeholder delay - procurement delay D. Escalation rules Define when to involve: - manager - executive sponsor - champion - legal - procurement - finance - customer success E. Forecast update Recommend how the deadline affects forecast category. Rules: - Do not treat a target date as real unless the buyer confirms it. - Do not let missed deadlines pass silently. - Do not escalate emotionally. - Deadline management should create transparency and accountability. --------------------------------------------------------------------------------

#167Ghosting Prevention Plan

CLOSING, FOLLOW-UP & PIPELINE ACCELERATIONDiscovery calls, demos, proposal follow-up, final-stage deals, SDR handoffs, account executives, and founder-led sales.

Reduce ghosting by creating stronger next steps, buyer-owned commitments, useful follow-up assets, stakeholder alignment, and early warning signals.

You are a sales ghosting prevention expert. Build a plan to prevent this prospect from going silent after the next interaction. Context: Offer: [OFFER] Buyer: [BUYER] Account: [ACCOUNT] Current stage: [STAGE] Next meeting type: [MEETING TYPE] Known pain: [PAIN] Known urgency: [URGENCY] Known stakeholders: [STAKEHOLDERS] Known objections: [OBJECTIONS] Past ghosting patterns: [PATTERNS] Current next-step process: [PROCESS] Create the prevention plan: 1. Ghosting risk diagnosis Assess risk across: - weak pain - weak urgency - unclear decision process - no calendar commitment - wrong contact - no stakeholder access - no internal value case - unresolved objection - generic follow-up - unclear CTA 2. Before-call prevention Create questions to ask before the call ends: - what happens next - who owns the next step - who else is involved - what could delay this - what information is needed - what date makes sense 3. Commitment design Create next steps that require buyer ownership: - stakeholder intro - internal review - document feedback - technical checklist - business case validation - decision meeting 4. Follow-up assets Recommend assets that make silence less likely. 5. Early warning plan Define what to do after: - no reply after 2 days - no reply after 5 days - no reply after 10 days - missed meeting - vague reply Rules: - Do not blame the buyer for ghosting. - Do not rely on “I’ll follow up next week.” - Do not end meetings without a specific commitment. - Ghosting prevention starts before the follow-up email. --------------------------------------------------------------------------------

#168Final Objection Checkpoint

CLOSING, FOLLOW-UP & PIPELINE ACCELERATIONLate-stage calls, proposal reviews, contract discussions, executive alignment, procurement handoffs, and deal close conversations.

Surface final hidden objections before a close, proposal approval, procurement handoff, or signature request.

Act as a final-stage sales coach. Create a final objection checkpoint for this deal before we ask for a decision. Deal context: Offer: [OFFER] Account: [ACCOUNT] Buyer: [BUYER] Deal stage: [STAGE] Proposal status: [PROPOSAL STATUS] Price: [PRICE] Value case: [VALUE CASE] Stakeholders: [STAKEHOLDERS] Decision criteria: [CRITERIA] Known objections: [OBJECTIONS] Procurement/legal status: [PROCUREMENT / LEGAL] Target decision date: [DATE] Build the checkpoint: A. Hidden objection categories Check for: - price concern - budget uncertainty - timing hesitation - authority gap - stakeholder misalignment - trust gap - competitor risk - implementation fear - procurement delay - legal concern - technical risk - no-decision risk B. Final checkpoint questions Write direct but safe questions that uncover: - what could stop the deal - who still has concerns - what has not been discussed - what finance may challenge - what legal may challenge - what implementation may challenge - what the buyer is personally unsure about C. Response options For each possible final concern provide: - what to say - what proof to use - what asset to send - who to involve - what next step to set D. Decision readiness statement Write a summary that confirms whether the buyer feels ready to proceed. E. Close or pause recommendation Tell me whether to ask for signature, schedule another meeting, involve stakeholders, or pause. Rules: - Do not skip final objections just to force the close. - Do not ask for signature if unresolved risk remains. - Do not make the buyer feel trapped. - The checkpoint should make the decision cleaner. --------------------------------------------------------------------------------

#169Micro-Commitment Close Builder

CLOSING, FOLLOW-UP & PIPELINE ACCELERATIONComplex B2B sales, long sales cycles, skeptical buyers, early-stage conversations, multi-stakeholder deals, and consultative selling.

Move deals forward through small, meaningful buyer commitments instead of jumping from interest directly to a large close.

You are a micro-commitment sales strategist. Build a sequence of small commitments that moves this buyer toward a decision. Context: Offer: [OFFER] Buyer: [BUYER] Account: [ACCOUNT] Current deal stage: [STAGE] Buyer interest level: [INTEREST] Pain: [PAIN] Urgency: [URGENCY] Decision complexity: [COMPLEXITY] Stakeholders: [STAKEHOLDERS] Current next step: [NEXT STEP] Main risk: [RISK] Create the micro-commitment path: 1. Commitment ladder Build commitments across stages: - reply - call booking - problem validation - data sharing - stakeholder intro - technical review - business case review - proposal review - procurement start - signature - kickoff 2. Commitment quality For each commitment define: - what the buyer does - why it matters - what it proves - what it costs the buyer - what it unlocks - weak version to avoid 3. Language library Write asks for: - low-friction commitment - medium commitment - high-intent commitment - executive commitment - champion commitment - procurement commitment 4. Risk signals Explain what it means if the buyer refuses each commitment. 5. Next action Recommend the next best micro-commitment for this deal. Rules: - Do not mistake passive agreement for commitment. - Do not ask for a commitment that is too big too early. - Do not create meaningless steps. - Each commitment should reveal real intent or move the process forward. --------------------------------------------------------------------------------

#170Champion Re-Activation Message System

CLOSING, FOLLOW-UP & PIPELINE ACCELERATIONMulti-stakeholder deals, complex B2B sales, stalled opportunities, champion-led internal selling, and pipeline revival.

Re-engage a champion who has gone quiet or lost momentum by giving them useful internal support, clarity, and a low-friction way to restart the deal.

Act as a champion re-activation strategist. Create a message system to re-engage my champion at [ACCOUNT]. Champion context: Champion name: [CHAMPION] Champion role: [ROLE] Account: [ACCOUNT] Offer: [OFFER] Original pain: [PAIN] Original value: [VALUE] Last conversation: [LAST CONVERSATION] Last commitment: [COMMITMENT] Time since last contact: [TIME] Known stakeholders: [STAKEHOLDERS] Likely internal blockers: [BLOCKERS] Assets available: [ASSETS] Create the re-activation system: A. Champion status diagnosis Estimate whether the champion is: - still interested but busy - blocked internally - lost urgency - lacking authority - missing proof - evaluating competitors - avoiding bad news - no longer involved B. Message angles Write messages using these angles: - helpful recap - internal support - new proof - decision timeline check - stakeholder support - business impact reminder - close-the-loop - future nurture C. Champion enablement asset Create a short internal summary the champion can forward. D. Ask options Create low-friction asks: - “Should we pause this?” - “Who else should be included?” - “Is this still a priority?” - “Would a short internal summary help?” - “Should we revisit later?” E. Escalation logic Explain when to: - keep working through champion - ask for another stakeholder - go executive-level - move to nurture - close-lost Rules: - Do not guilt the champion. - Do not assume silence means rejection. - Do not make the champion do internal selling unsupported. - Re-activation must be useful, respectful, and specific. --------------------------------------------------------------------------------

#171Buyer Forwardable Internal Summary

CLOSING, FOLLOW-UP & PIPELINE ACCELERATIONChampion enablement, internal buy-in, late-stage deals, proposal follow-up, executive alignment, procurement preparation, and reducing deal friction.

Create a concise internal summary a buyer can forward to stakeholders to explain the problem, solution, value, proof, decision needed, and next step.

You are a buyer enablement writer. Create a forwardable internal summary for [BUYER] to send inside [ACCOUNT]. Deal context: Offer: [OFFER] Account: [ACCOUNT] Buyer: [BUYER] Internal audience: [INTERNAL AUDIENCE] Problem discussed: [PROBLEM] Business impact: [IMPACT] Recommended solution: [SOLUTION] Expected value: [VALUE] Investment: [INVESTMENT] Proof: [PROOF] Implementation notes: [IMPLEMENTATION] Known risks: [RISKS] Decision needed: [DECISION] Next step: [NEXT STEP] Write the internal summary: 1. Subject line options Create 8 internal email subject lines. 2. Executive version Write a concise version for leadership. 3. Finance version Write a version focused on cost, value, ROI, and approval logic. 4. Technical version Write a version focused on implementation, security, integration, and risk. 5. Team version Write a version focused on workflow improvement and user impact. 6. Decision section Write a clear internal decision request: - what needs approval - by when - from whom - what happens next 7. FAQ Answer likely internal questions: - why now - why this vendor - why this price - what risk exists - what implementation requires - what happens if we wait Rules: - Do not make it sound like marketing copy. - Do not overclaim results. - Do not hide risks. - The buyer should be able to forward this without rewriting it. --------------------------------------------------------------------------------

#172Close-the-Loop Email Generator

CLOSING, FOLLOW-UP & PIPELINE ACCELERATIONGhosted deals, stalled proposals, no-response prospects, cold outreach follow-up, late-stage silence, and pipeline cleanup.

Write respectful close-the-loop emails that stop endless follow-up, invite honest replies, and preserve future opportunities.

Act as a respectful sales follow-up writer. Write close-the-loop emails for a prospect who has stopped responding. Context: Offer: [OFFER] Buyer: [BUYER] Account: [ACCOUNT] Last interaction: [LAST INTERACTION] Last message sent: [LAST MESSAGE] Time since response: [TIME] Pain discussed: [PAIN] Value discussed: [VALUE] Expected next step: [EXPECTED NEXT STEP] Relationship tone: [TONE] Reason for outreach: [REASON] Create close-the-loop options: A. Soft close-the-loop Write a warm message that gives the buyer permission to pause. B. Direct close-the-loop Write a concise message that asks whether to close the file. C. Value-added close-the-loop Write a message that includes a useful resource or insight. D. Timing reset Write a message that asks whether a later date makes more sense. E. Breakup with future door open Write a respectful final message that leaves the relationship intact. For each version include: - subject line - email body - CTA - when to send - when not to send - likely interpretation Also create: - LinkedIn DM version - voicemail version - CRM note - nurture tag recommendation Rules: - Do not shame the buyer. - Do not use manipulative breakup language. - Do not send more follow-ups after the final message unless they reply. - Close-the-loop should clean the pipeline and protect the relationship. --------------------------------------------------------------------------------

#173Pipeline Acceleration Prioritizer

CLOSING, FOLLOW-UP & PIPELINE ACCELERATIONSales managers, account executives, founders, RevOps, weekly pipeline reviews, forecast meetings, and pipeline cleanup.

Identify which opportunities deserve attention this week and what action will most likely move each one forward.

You are a pipeline acceleration advisor. Prioritize my open opportunities and recommend the highest-leverage action for each one. Pipeline data: [PASTE OPPORTUNITY LIST WITH STAGE, VALUE, LAST ACTIVITY, NEXT STEP, CLOSE DATE, NOTES] Sales context: Offer: [OFFER] Sales cycle: [SALES CYCLE] Average deal size: [AVG DEAL SIZE] Qualification criteria: [CRITERIA] Forecast categories: [FORECAST CATEGORIES] Team capacity this week: [CAPACITY] Revenue target: [TARGET] Analyze the pipeline: 1. Opportunity triage Classify each opportunity as: - accelerate now - protect and progress - requalify - nurture - close-lost - manager review - procurement/legal watch - no action this week 2. Acceleration score Score each opportunity from 1 to 100 based on: - value - close probability - urgency - buyer commitment - stakeholder coverage - next-step clarity - time in stage - deal risk - effort required - forecast impact 3. Best next action For each opportunity recommend one action: - call - email - stakeholder intro - executive summary - proof asset - mutual action plan - procurement check - technical review - pricing clarification - close-the-loop 4. This-week plan Create: - top 5 deals to focus on - exact action for each - message or call objective - expected outcome - deadline 5. Forecast notes Identify: - deals to downgrade - deals to upgrade - deals with fake close dates - deals missing next steps - deals likely to slip Rules: - Do not prioritize only by deal size. - Do not keep stale deals active without evidence. - Do not recommend vague follow-up. - The output should tell me exactly what to do this week. --------------------------------------------------------------------------------

#174Mutual Action Plan for Closing

CLOSING, FOLLOW-UP & PIPELINE ACCELERATIONEnterprise deals, late-stage opportunities, procurement processes, complex sales, implementation-heavy offers, and forecast control.

Create a buyer-facing mutual action plan with milestones, owners, dates, documents, approvals, risks, and decision checkpoints.

Act as a mutual action plan specialist. Build a closing-focused mutual action plan for [ACCOUNT]. Deal context: Account: [ACCOUNT] Offer: [OFFER] Buyer: [BUYER] Target decision date: [DECISION DATE] Target signature date: [SIGNATURE DATE] Implementation start date: [IMPLEMENTATION DATE] Stakeholders: [STAKEHOLDERS] Approval steps: [APPROVAL STEPS] Procurement steps: [PROCUREMENT] Legal steps: [LEGAL] Technical steps: [TECHNICAL] Open questions: [OPEN QUESTIONS] Known risks: [RISKS] Create the mutual action plan: A. Shared objective Write the shared goal in buyer-friendly language. B. Milestone table Create a table with: - milestone - purpose - buyer owner - seller owner - due date - input needed - output expected - risk - fallback plan C. Decision checkpoints Define where the buyer must decide: - solution fit - business case - technical approval - commercial approval - legal approval - final signature - kickoff readiness D. Communication cadence Create: - weekly update format - stakeholder reminder - missed milestone message - escalation message - decision meeting agenda E. Buyer-facing email Write an email introducing the mutual action plan. Rules: - Do not create a plan that only the seller owns. - Do not set dates the buyer has not agreed to. - Do not ignore legal, procurement, or technical dependencies. - A mutual action plan should make progress visible and shared. --------------------------------------------------------------------------------

#175Decision Meeting Agenda Builder

CLOSING, FOLLOW-UP & PIPELINE ACCELERATIONFinal calls, executive decision meetings, proposal review calls, procurement alignment, stakeholder meetings, and closing complex deals.

Create a structured decision meeting agenda that helps stakeholders resolve final questions and commit to a next action.

You are a decision meeting facilitator. Build an agenda for a meeting where [ACCOUNT] needs to decide whether to move forward with [OFFER]. Meeting context: Offer: [OFFER] Account: [ACCOUNT] Attendees: [ATTENDEES] Meeting length: [LENGTH] Decision needed: [DECISION] Problem: [PROBLEM] Value case: [VALUE CASE] Proposal status: [PROPOSAL STATUS] Open questions: [OPEN QUESTIONS] Known objections: [OBJECTIONS] Decision deadline: [DEADLINE] Build the agenda: 1. Meeting objective Write a clear objective for the meeting. 2. Pre-read Recommend what to send before the meeting: - proposal - executive summary - ROI note - proof asset - technical documentation - implementation plan - FAQ 3. Agenda by time Break the meeting into: - context recap - business value confirmation - open questions - stakeholder concerns - decision criteria review - next-step options - final commitment 4. Facilitator script Write: - opening statement - transition between sections - concern-surfacing questions - decision question - closing language 5. Decision outcomes Prepare paths for: - yes - yes with conditions - not yet - needs more stakeholder input - procurement/legal review - no decision Rules: - Do not let the meeting become another vague discussion. - Do not ignore silent stakeholders. - Do not ask for a decision before concerns are surfaced. - The meeting should end with a documented outcome. --------------------------------------------------------------------------------

#176Pipeline Slip Prevention System

CLOSING, FOLLOW-UP & PIPELINE ACCELERATIONSales managers, forecast calls, RevOps, AEs, enterprise sales, quarterly close planning, and pipeline quality improvement.

Identify deals likely to slip and create a prevention plan with earlier risk detection, better next steps, stakeholder alignment, and close-date discipline.

Act as a forecast and pipeline slip prevention expert. Identify why deals slip and build a prevention system for my pipeline. Pipeline context: Pipeline list: [PIPELINE LIST] Current quarter target: [TARGET] Sales cycle: [SALES CYCLE] Forecast categories: [FORECAST] Common slip reasons: [SLIP REASONS] CRM stages: [STAGES] Current close date rules: [RULES] Team behavior patterns: [PATTERNS] Build the slip prevention system: A. Slip risk indicators Identify warning signs such as: - no buyer-owned next step - close date changed multiple times - no stakeholder access - procurement not started - legal not started - no compelling event - no decision process - weak champion - unanswered pricing concern - stale last activity B. Deal risk scoring Create a scoring model for slip risk: - low risk - medium risk - high risk - likely slip - remove from forecast C. Prevention actions For each risk recommend: - seller action - manager action - buyer-facing message - CRM update - deadline D. Forecast meeting questions Create manager questions that reveal fake close dates. E. Close-date rules Define when a close date may remain, move, or be removed. Rules: - Do not accept close dates without buyer evidence. - Do not let sellers move dates without explaining the cause. - Do not rely on optimism. - Slip prevention requires earlier detection, not end-of-quarter pressure. --------------------------------------------------------------------------------

#177Re-Engagement Campaign for Old Opportunities

CLOSING, FOLLOW-UP & PIPELINE ACCELERATIONClosed-lost opportunities, old demos, stalled proposals, expired trials, past inbound leads, and pipeline revival campaigns.

Build a re-engagement campaign for old opportunities that uses new context, value, timing, and respectful outreach to restart conversations.

You are a sales re-engagement campaign strategist. Create a campaign to revive old opportunities for [OFFER]. Context: Offer: [OFFER] Old opportunity list: [OPPORTUNITY LIST] Original lead source: [SOURCE] Original pain: [PAIN] Reason stalled or lost: [REASON] Time since last contact: [TIME] New product updates: [UPDATES] New proof: [PROOF] New market context: [MARKET CONTEXT] Target buyer: [BUYER] Desired CTA: [CTA] Create the campaign: 1. Segment the old opportunities Group by: - lost to competitor - no decision - no budget - bad timing - ghosted - not enough trust - missing feature - implementation concern - low priority - wrong stakeholder 2. Message angle by segment For each segment create: - re-entry angle - subject line - email - LinkedIn message - call opener - proof to include - CTA 3. Timing cadence Create a 4-touch sequence: - touch 1: re-entry - touch 2: useful update - touch 3: buyer-specific value - touch 4: close-the-loop 4. Qualification questions Create questions to determine whether the account is worth reopening. 5. Success metrics Define: - reply rate - meeting booked rate - opportunity reopened rate - requalification rate - pipeline created - revenue closed Rules: - Do not pretend the previous conversation never happened. - Do not send generic “wanted to reconnect” emails. - Do not revive bad-fit accounts. - Re-engagement should be specific, timely, and respectful. --------------------------------------------------------------------------------

#178Closing Confidence Scorecard for Sales Managers

CLOSING, FOLLOW-UP & PIPELINE ACCELERATIONSales managers, founders, revenue leaders, weekly deal reviews, forecast calls, AE coaching, and late-stage pipeline management.

Give managers a structured way to inspect closing opportunities, test forecast confidence, coach reps, and identify deal risks.

Act as a sales manager running a close-plan review. Build a closing confidence scorecard for this opportunity. Deal context: Account: [ACCOUNT] Offer: [OFFER] Rep: [REP] Deal value: [VALUE] Stage: [STAGE] Forecast category: [FORECAST] Target close date: [CLOSE DATE] Pain: [PAIN] Value: [VALUE CASE] Decision process: [DECISION PROCESS] Budget: [BUDGET] Stakeholders: [STAKEHOLDERS] Champion: [CHAMPION] Procurement/legal: [PROCUREMENT / LEGAL] Next step: [NEXT STEP] Risks: [RISKS] Score the deal across 18 criteria: 1. Pain clarity 2. Business impact 3. Compelling event 4. Value case 5. Budget confirmation 6. Economic buyer access 7. Champion strength 8. Stakeholder coverage 9. Decision process clarity 10. Decision criteria 11. Competition status 12. Implementation confidence 13. Legal progress 14. Procurement progress 15. Mutual action plan 16. Buyer-owned next step 17. Close date evidence 18. Forecast confidence For each criterion provide: - score from 1 to 10 - evidence - missing evidence - manager coaching question - required action Then provide: - forecast recommendation - top 3 deal risks - top 3 acceleration actions - message the rep should send next - manager escalation recommendation - CRM updates required Rules: - Do not score based on rep optimism. - Do not accept “they liked it” as evidence. - Do not ignore missing stakeholders. - Manager review should improve forecast accuracy and deal execution. --------------------------------------------------------------------------------

#179Late-Stage Buyer Enablement Pack

CLOSING, FOLLOW-UP & PIPELINE ACCELERATIONComplex B2B sales, proposal follow-up, champion support, executive approval, procurement preparation, and late-stage deal acceleration.

Create the buyer-facing assets needed to help an opportunity move from interest to approval and signature.

You are a buyer enablement strategist. Build a late-stage buyer enablement pack for [ACCOUNT]. Deal context: Offer: [OFFER] Account: [ACCOUNT] Primary buyer: [BUYER] Stakeholders: [STAKEHOLDERS] Decision stage: [STAGE] Problem: [PROBLEM] Business impact: [IMPACT] Recommended solution: [SOLUTION] Investment: [INVESTMENT] Proof available: [PROOF] Implementation notes: [IMPLEMENTATION] Known concerns: [CONCERNS] Approval steps: [APPROVAL STEPS] Create the enablement pack: A. Executive summary Write a one-page summary covering: - problem - business impact - recommended solution - expected value - decision needed B. Stakeholder FAQ Answer questions from: - executive sponsor - finance - procurement - technical team - daily users - legal - implementation owner C. Business case snapshot Create: - value drivers - cost of inaction - ROI assumptions - proof points - risks and mitigations D. Decision checklist Create a checklist the buyer can use internally. E. Email templates Write: - buyer-to-executive email - buyer-to-finance email - buyer-to-technical team email - buyer-to-procurement email - buyer-to-users email F. Next-step plan Create a simple timeline from approval to kickoff. Rules: - Do not make the buyer translate our value alone. - Do not overload the pack with unnecessary material. - Do not hide risks or assumptions. - Buyer enablement should make internal approval easier. --------------------------------------------------------------------------------

#180Full Closing, Follow-Up and Pipeline Acceleration Audit

CLOSING, FOLLOW-UP & PIPELINE ACCELERATIONSales leaders, founders, RevOps teams, account executives, SDR managers, consultants, agencies, SaaS companies, and teams improving late-stage conversion.

Audit and rebuild the complete closing and follow-up system across deal readiness, next steps, urgency, ghosting, re-engagement, decision deadlines, mutual action plans, forecast confidence, and pipeline acceleration.

Act as an independent closing, follow-up, and pipeline acceleration auditor. Review my current system and rebuild it into a stronger process for moving qualified opportunities to clear decisions without using pushy tactics. Full context: Company: [COMPANY] Website: [WEBSITE] Offer: [OFFER] Target market: [MARKET] ICP: [ICP] Buyer personas: [PERSONAS] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Current sales stages: [SALES STAGES] Current close process: [CLOSE PROCESS] Current follow-up sequences: [FOLLOW-UP SEQUENCES] Current pipeline data: [PIPELINE DATA] Current forecast categories: [FORECAST CATEGORIES] Current CRM fields: [CRM FIELDS] Current proposal process: [PROPOSAL PROCESS] Current procurement/legal process: [PROCUREMENT / LEGAL] Common stall reasons: [STALL REASONS] Common ghosting reasons: [GHOSTING REASONS] Win/loss insights: [WIN LOSS] Manager review process: [MANAGER REVIEW] Main closing problems: [PROBLEMS] Audit across 40 dimensions: 1. Close readiness criteria 2. Qualification before close 3. Final objection detection 4. Value recap quality 5. Urgency clarity 6. Cost-of-delay clarity 7. Decision process clarity 8. Decision deadline quality 9. Stakeholder coverage 10. Champion enablement 11. Economic buyer alignment 12. Procurement progress 13. Legal progress 14. Technical approval progress 15. Implementation confidence 16. Proposal follow-up 17. Post-demo follow-up 18. Close-the-loop messaging 19. Ghosting prevention 20. Stalled deal requalification 21. Re-engagement process 22. Mutual action plans 23. Buyer-owned next steps 24. Calendar commitment 25. Micro-commitments 26. Executive summaries 27. Buyer enablement assets 28. Internal forwarding support 29. Pipeline prioritization 30. Pipeline hygiene 31. Close date discipline 32. Slip prevention 33. Forecast confidence 34. Manager deal inspection 35. CRM risk tracking 36. Deal acceleration plays 37. Disqualification discipline 38. Seller confidence 39. Buyer experience 40. Overall late-stage sales maturity For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - revenue impact - forecast impact - risk if ignored - recommended fix - priority - effort - confidence level Then synthesize: A. Hard truth Explain the biggest reason deals are not closing, are slipping, or are going quiet. B. Rebuilt closing system Create: - close readiness checklist - final objection checkpoint - ethical urgency framework - decision deadline system - mutual action plan template - non-pushy closing script - buyer enablement pack - close-the-loop sequence C. Rebuilt pipeline acceleration system Create: - weekly pipeline triage method - deal acceleration score - stalled deal requalification path - ghosting prevention process - re-engagement campaign - close date rules - manager inspection questions - CRM fields to track D. 30-day improvement roadmap Create: - first 24-hour cleanup - first 7-day follow-up rewrite - first 14-day deal review upgrade - first 30-day pipeline acceleration rollout - metrics to track - owner assignments E. Executive summary Write a direct summary with: - fastest closing improvement - highest-risk pipeline problem - first follow-up to rewrite - first CRM field to add - first manager question to ask - first buyer enablement asset to build - first close-date rule to enforce - one operating principle for closing without pressure Rules: - Do not teach pressure tactics. - Do not keep bad-fit opportunities alive with clever follow-up. - Do not forecast deals without buyer-owned next steps. - Use [NEEDS DATA], [NEEDS CRM REVIEW], [NEEDS MANAGER REVIEW], [NEEDS LEGAL REVIEW], or [NEEDS PROCUREMENT REVIEW] where required. - The final system should improve deal clarity, buyer confidence, forecast accuracy, and pipeline movement.

#181CRM Operating System Blueprint

CRM, PIPELINE MANAGEMENT & SALES OPERATIONSSales leaders, founders, RevOps teams, sales operations managers, account executives, SDR teams, and companies that need CRM clarity without overcomplication.

Design a practical CRM operating system that defines stages, fields, owners, rules, hygiene standards, automation, reports, and management rhythms.

You are a CRM and sales operations architect. Build a complete CRM operating system for [COMPANY] selling [OFFER] to [ICP]. Business context: Company: [COMPANY] Offer: [OFFER] Target market: [MARKET] ICP: [ICP] Buyer personas: [BUYER PERSONAS] Sales motion: [SALES MOTION] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Team roles: [TEAM ROLES] Current CRM: [CRM] Current sales stages: [CURRENT STAGES] Current CRM problems: [PROBLEMS] Reports needed: [REPORTS] Leadership goals: [GOALS] Build the CRM operating system: 1. CRM purpose Define what the CRM must help the team do: - track opportunities - qualify deals - forecast revenue - manage follow-up - inspect pipeline - measure activity - improve conversion - protect handoffs - support coaching - create leadership visibility 2. Object architecture Define how to use: - leads - contacts - accounts - opportunities - activities - tasks - notes - campaigns - custom objects, if needed For each object explain: - purpose - required fields - owner - update rules - common mistakes to avoid 3. Stage architecture Create clean sales stages with: - stage name - definition - entry criteria - exit criteria - required fields - allowed next stages - disqualification rules - manager review trigger 4. Field governance Recommend: - required fields - optional fields - fields to remove - picklist values - validation rules - duplicate prevention - hygiene rules 5. Operating cadence Create weekly CRM rhythms for: - rep updates - pipeline review - forecast inspection - stalled deal cleanup - manager coaching - leadership reporting 6. Success metrics Define how to measure whether the CRM system is working. Rules: - Do not create fields nobody will maintain. - Do not design stages based only on seller activity. - Do not make the CRM a dumping ground. - The CRM should make execution easier and pipeline visibility more trustworthy. --------------------------------------------------------------------------------

#182Pipeline Stage Exit Criteria Builder

CRM, PIPELINE MANAGEMENT & SALES OPERATIONSCRM cleanup, sales process design, RevOps, sales managers, founder-led sales, pipeline reviews, and stage conversion improvement.

Create stage definitions and exit criteria that prevent vague pipeline movement, fake progress, and inaccurate forecasting.

Act as a sales process designer. Build precise pipeline stage rules for [SALES PROCESS]. Inputs: Offer: [OFFER] Buyer type: [BUYER TYPE] Sales motion: [SALES MOTION] Current stages: [CURRENT STAGES] Current problems with stages: [PROBLEMS] Typical buyer journey: [BUYER JOURNEY] Qualification criteria: [QUALIFICATION] Decision process: [DECISION PROCESS] Required sales activities: [ACTIVITIES] Required buyer commitments: [BUYER COMMITMENTS] Create the stage system in this format: A. Stage dictionary For every stage provide: - stage name - plain-English definition - seller action happening here - buyer action happening here - evidence required - required fields - minimum activity required - common false-positive signal - common reason deals get stuck - allowed next stage - allowed fallback stage B. Entry and exit rules For each stage define: - what must be true before a deal enters - what must be true before a deal exits - what evidence is not enough - what manager should inspect C. Stage movement examples Create examples of: - correct stage movement - incorrect stage movement - deal that should move backward - deal that should be disqualified - deal that should be moved to nurture D. CRM enforcement Recommend: - required fields by stage - validation rules - task creation rules - aging alerts - manager approval points E. Sales team explanation Write a short explanation reps can understand. Rules: - Do not use stages that only describe seller hope. - Do not advance a deal without buyer evidence. - Do not make stages too granular for the team to use. - Good stages reflect buying progress, not just selling activity. --------------------------------------------------------------------------------

#183Deal Health Scoring Model

CRM, PIPELINE MANAGEMENT & SALES OPERATIONSForecasting, pipeline reviews, sales coaching, CRM dashboards, RevOps analysis, enterprise sales, and weekly opportunity inspection.

Build a deal health scoring system that shows which opportunities are strong, risky, stalled, over-forecasted, or missing key evidence.

You are a sales analytics and deal inspection expert. Create a deal health scoring model for [COMPANY]. Context: Offer: [OFFER] Sales cycle: [SALES CYCLE] Average deal size: [DEAL SIZE] Current CRM fields: [CRM FIELDS] Current sales stages: [STAGES] Current forecast categories: [FORECAST CATEGORIES] Common win signals: [WIN SIGNALS] Common loss signals: [LOSS SIGNALS] Common stall reasons: [STALL REASONS] Manager priorities: [PRIORITIES] Build the model: 1. Deal health dimensions Create scoring criteria for: - pain clarity - business impact - buyer urgency - budget status - authority coverage - stakeholder coverage - champion strength - decision process clarity - next-step quality - recent activity - proof fit - proposal status - legal/procurement progress - implementation risk - competitive risk - close date confidence 2. Scoring rules For each dimension provide: - score 0 - score 1 - score 2 - score 3 - weight - CRM fields needed - evidence required 3. Health categories Define thresholds for: - healthy - needs attention - high risk - stalled - over-forecasted - disqualify or nurture 4. Dashboard output Create the recommended dashboard views: - deal health by owner - deal health by stage - high-risk commit deals - no-next-step deals - aging deals - close-date risk - missing stakeholder deals 5. Coaching actions For each health category recommend: - rep action - manager action - buyer-facing action - CRM update Rules: - Do not score based on seller optimism. - Do not use fields that the team will not keep updated. - Do not treat activity volume as deal health by itself. - The score should make risk visible before it affects forecast. --------------------------------------------------------------------------------

#184Revenue Forecast Confidence Analyzer

CRM, PIPELINE MANAGEMENT & SALES OPERATIONSSales leaders, RevOps, founders, weekly forecast meetings, board reporting, revenue planning, and quarter-end forecasting.

Analyze forecast confidence by inspecting pipeline quality, close dates, stage probability, deal health, historical conversion, risk, and coverage.

Act as a revenue forecasting analyst. Analyze this pipeline and produce a forecast confidence report. Pipeline data: [PASTE PIPELINE DATA] Additional context: Forecast period: [PERIOD] Revenue target: [TARGET] Sales cycle: [SALES CYCLE] Historical win rates by stage: [WIN RATES] Average deal size: [AVG DEAL SIZE] Forecast categories: [FORECAST CATEGORIES] Stage definitions: [STAGE DEFINITIONS] Current month or quarter: [TIMEFRAME] Known risks: [RISKS] Leadership questions: [QUESTIONS] Create the forecast report: A. Forecast summary Provide: - best-case forecast - likely forecast - conservative forecast - commit forecast - gap to target - confidence level - main risk B. Pipeline quality review Analyze: - stage distribution - close date concentration - aged opportunities - stale opportunities - missing next steps - high-value risky deals - low-probability deals in forecast - opportunities without decision process - opportunities without recent activity C. Deal-level risk table For each material deal provide: - deal name - value - stage - close date - forecast category - risk level - missing evidence - recommended action - forecast adjustment D. Scenario modeling Create scenarios: - conservative - realistic - upside - slip scenario - downside scenario E. Leadership actions Recommend: - deals to inspect - forecast categories to adjust - pipeline gaps to fill - manager coaching priorities - CRM hygiene fixes Rules: - Do not accept CRM probabilities blindly. - Do not forecast deals with no buyer-owned next step as high confidence. - Do not hide uncertainty. - Forecast confidence must be based on evidence, not hope. --------------------------------------------------------------------------------

#185CRM Data Hygiene Cleanup Plan

CRM, PIPELINE MANAGEMENT & SALES OPERATIONSCRM admins, RevOps, sales operations, founders, sales managers, CRM migrations, dashboard repair, and pipeline cleanup.

Clean CRM data by identifying duplicates, stale records, missing fields, inconsistent stages, bad close dates, owner issues, and unusable reports.

You are a CRM data hygiene specialist. Create a cleanup plan for this CRM environment. CRM context: CRM platform: [CRM PLATFORM] Objects used: [OBJECTS] Team size: [TEAM SIZE] Current data problems: [PROBLEMS] Reports affected: [REPORTS] Required fields: [REQUIRED FIELDS] Stage definitions: [STAGE DEFINITIONS] Duplicate issues: [DUPLICATES] Data sources: [DATA SOURCES] Automation currently active: [AUTOMATIONS] Cleanup deadline: [DEADLINE] Build the cleanup plan: 1. Data issue inventory Identify possible issues across: - duplicate leads - duplicate contacts - duplicate accounts - missing owners - missing close dates - outdated close dates - stale opportunities - wrong stages - missing required fields - inconsistent picklists - bad source attribution - incomplete activity history - orphan records - inactive users owning records 2. Cleanup priority matrix Rank issues by: - reporting impact - forecast impact - sales execution impact - automation impact - customer experience impact - cleanup difficulty - urgency 3. Cleanup workflow Create steps for: - audit - export - backup - deduplication - field standardization - stage correction - owner correction - stale deal cleanup - automation validation - dashboard verification 4. Governance rules Define how to prevent problems from returning: - required fields - validation rules - duplicate rules - naming standards - lifecycle rules - owner rules - audit cadence 5. Communication plan Write a short message to the sales team explaining: - what will change - what they must update - why it matters - deadline - support available Rules: - Do not clean data without a backup. - Do not merge records when ownership or activity history is unclear. - Do not create rules that block reps unnecessarily. - Data hygiene should improve trust in the CRM, not add bureaucracy. --------------------------------------------------------------------------------

#186Sales Activity Reporting System

CRM, PIPELINE MANAGEMENT & SALES OPERATIONSSDR teams, account executives, sales managers, RevOps, founder-led sales teams, weekly scorecards, and activity-to-outcome analysis.

Build activity reports that show meaningful sales execution, not just raw volume, by connecting actions to pipeline movement and outcomes.

Act as a sales operations reporting designer. Build an activity reporting system for [SALES TEAM]. Context: Team type: [TEAM TYPE] Roles: [ROLES] Sales motion: [SALES MOTION] Target market: [MARKET] Current activity metrics: [CURRENT METRICS] Current CRM fields: [FIELDS] Current reporting problems: [PROBLEMS] Revenue goals: [GOALS] Manager questions: [QUESTIONS] Design the activity reporting system: A. Activity taxonomy Define how to track: - calls - emails - LinkedIn messages - meetings booked - meetings held - demos - proposals sent - follow-ups - stakeholder introductions - procurement touches - close-plan actions B. Quality indicators For each activity type define: - low-quality version - acceptable version - high-quality version - CRM evidence required - buyer outcome expected C. Activity-to-outcome reporting Create dashboards showing: - activity by rep - activity by stage - activity by account segment - activity to meetings - meetings to opportunities - opportunities to proposals - proposals to closed-won - follow-up speed - stale deal activity gaps D. Coaching interpretation Explain what managers should do when: - activity is high but conversion is low - activity is low but conversion is high - meetings are booked but not held - proposals are sent but not closed - follow-ups happen without progression E. Report cadence Recommend: - daily view - weekly view - monthly view - leadership view Rules: - Do not reward meaningless activity. - Do not compare reps without context. - Do not track everything if nobody will use it. - Activity reporting should explain execution quality and pipeline movement. --------------------------------------------------------------------------------

#187Sales Dashboard Design Brief

CRM, PIPELINE MANAGEMENT & SALES OPERATIONSCRM dashboards, sales reporting, leadership visibility, forecast meetings, pipeline reviews, sales operations, and RevOps system design.

Design dashboards for reps, managers, RevOps, and leadership that show the right CRM data at the right level of detail.

You are a sales dashboard architect. Create dashboard briefs for different CRM users. Business context: Company: [COMPANY] CRM: [CRM] Sales motion: [SALES MOTION] Team roles: [ROLES] Revenue target: [TARGET] Current dashboards: [CURRENT DASHBOARDS] Current reporting problems: [PROBLEMS] Available CRM fields: [FIELDS] Leadership priorities: [PRIORITIES] Create dashboards for: 1. Individual rep dashboard Must answer: - what should I work on today? - which deals need follow-up? - which tasks are overdue? - where am I against quota? - which opportunities are at risk? 2. Sales manager dashboard Must answer: - which reps need coaching? - which deals are at risk? - which stages are stuck? - where is pipeline aging? - what forecast changed this week? 3. RevOps dashboard Must answer: - where is process leakage? - what fields are missing? - what data quality issues exist? - what automation is failing? - what reporting logic needs repair? 4. Leadership dashboard Must answer: - will we hit target? - what is the forecast range? - where is pipeline coverage weak? - what risks threaten revenue? - what actions are needed? For each dashboard provide: - purpose - audience - charts or tables - filters - fields required - refresh cadence - decision it supports - warning signs - actions triggered Rules: - Do not put every metric on every dashboard. - Do not design dashboards without a decision use case. - Do not mix rep execution views with board-level reporting. - A dashboard is useful only if it changes behavior or decisions. --------------------------------------------------------------------------------

#188Pipeline Hygiene Rules and Alerts Builder

CRM, PIPELINE MANAGEMENT & SALES OPERATIONSSales operations, RevOps, CRM admins, sales managers, pipeline reviews, forecast improvement, and CRM process enforcement.

Create rules and alerts that keep the pipeline clean by flagging stale deals, missing next steps, bad close dates, skipped stages, and inactive opportunities.

Act as a pipeline hygiene rules designer. Create CRM rules and alerts for keeping the pipeline accurate. Inputs: CRM platform: [CRM] Sales stages: [STAGES] Average sales cycle: [SALES CYCLE] Required fields: [FIELDS] Activity standards: [ACTIVITY STANDARDS] Current hygiene problems: [PROBLEMS] Forecast categories: [FORECAST] Team roles: [ROLES] Manager preferences: [PREFERENCES] Build the rules: A. Hygiene rule library Create rules for: - no next step - no recent activity - close date in the past - close date moved too many times - opportunity aging in stage - missing stakeholder - missing amount - missing decision process - missing forecast category - skipped stage - proposal sent with no follow-up - commit deal with unresolved risk For each rule provide: - trigger condition - severity - owner - notification timing - required action - escalation path - dashboard view B. Alert messages Write alert copy for: - rep notification - manager notification - RevOps report - leadership exception report C. Exceptions Define when alerts should not fire. D. Cleanup cadence Create: - daily rep hygiene routine - weekly manager review - monthly RevOps audit - quarterly stage review E. CRM implementation notes Recommend validation rules, workflows, tasks, or reports. Rules: - Do not create alert fatigue. - Do not block sales work unless the field is truly required. - Do not punish reps for CRM design problems. - Hygiene rules should protect forecast quality and next-step discipline. --------------------------------------------------------------------------------

#189Lead-to-Opportunity Conversion Workflow

CRM, PIPELINE MANAGEMENT & SALES OPERATIONSSDR teams, inbound sales, outbound teams, RevOps, CRM admins, startup sales systems, and lead management improvement.

Define a clean workflow for converting leads into opportunities with qualification rules, routing, ownership, stages, handoffs, and CRM field requirements.

You are a lead management and sales operations expert. Build a lead-to-opportunity conversion workflow for [COMPANY]. Context: Company: [COMPANY] Offer: [OFFER] Lead sources: [LEAD SOURCES] ICP: [ICP] Buyer personas: [PERSONAS] Sales team roles: [ROLES] Qualification criteria: [QUALIFICATION] Current lead stages: [LEAD STAGES] Current opportunity stages: [OPPORTUNITY STAGES] Routing rules: [ROUTING] Current problems: [PROBLEMS] CRM platform: [CRM] Create the workflow: 1. Lead lifecycle Define stages for: - new lead - contacted - engaged - qualified - disqualified - nurture - converted to opportunity For each stage include: - definition - owner - required action - required fields - SLA - next stage - disqualification reason 2. Qualification gate Define the minimum evidence needed before creating an opportunity: - ICP fit - problem fit - buyer role - interest level - timing - authority - potential value - next meeting or buyer commitment 3. Routing logic Create rules based on: - geography - segment - company size - industry - source - product interest - named account ownership - rep capacity 4. Handoff standards Define what SDR or marketing must pass to AE: - notes - pain - source - buyer language - timeline - objections - next step - meeting context 5. Reporting Define metrics to track: - lead response time - lead-to-meeting conversion - meeting held rate - lead-to-opportunity rate - opportunity quality - disqualification reasons Rules: - Do not create opportunities from weak leads. - Do not lose source attribution during conversion. - Do not allow unclear ownership. - A conversion workflow should improve pipeline quality, not inflate pipeline volume. --------------------------------------------------------------------------------

#190Sales Process Bottleneck Finder

CRM, PIPELINE MANAGEMENT & SALES OPERATIONSSales leaders, RevOps, sales managers, founders, revenue operations audits, process improvement, and pipeline acceleration.

Diagnose where the sales process is leaking revenue by analyzing conversion rates, stage aging, activity gaps, win/loss patterns, and handoff issues.

Act as a sales process analyst. Find the biggest bottlenecks in this sales process and recommend fixes. Data: Sales process stages: [STAGES] Stage conversion rates: [CONVERSION RATES] Stage aging data: [AGING] Win/loss data: [WIN LOSS] Activity data: [ACTIVITY] Pipeline data: [PIPELINE] Source data: [SOURCES] Team structure: [TEAM] Current problems: [PROBLEMS] Analyze the process: A. Funnel inspection For each stage identify: - conversion rate - average time in stage - drop-off rate - likely bottleneck - evidence needed - potential root cause B. Bottleneck categories Diagnose issues across: - lead quality - qualification - discovery - demos - proposal - pricing - procurement - legal - follow-up - stakeholder access - CRM hygiene - rep behavior C. Root cause analysis For each bottleneck separate: - process problem - people problem - messaging problem - market problem - CRM problem - reporting problem - buyer behavior problem D. Fix plan Recommend: - quick fix - system fix - coaching fix - CRM fix - reporting fix - enablement asset - metric to monitor E. Prioritized action plan Create a 30-day plan ranked by: - revenue impact - effort - speed - confidence - owner Rules: - Do not assume the lowest conversion stage is automatically the biggest problem. - Do not prescribe coaching when the process is broken. - Do not prescribe automation before fixing definitions. - Bottleneck analysis should lead to operational fixes, not vague recommendations. --------------------------------------------------------------------------------

#191Forecast Meeting Operating Rhythm

CRM, PIPELINE MANAGEMENT & SALES OPERATIONSSales managers, founders, CROs, RevOps, account executives, pipeline reviews, forecast calls, and revenue leadership meetings.

Build a weekly forecast meeting structure that improves forecast accuracy, deal inspection, accountability, and action without wasting time.

You are a revenue meeting designer. Create a forecast meeting operating rhythm for [SALES TEAM]. Context: Team size: [TEAM SIZE] Roles attending: [ROLES] Forecast cadence: [CADENCE] Current forecast process: [CURRENT PROCESS] Current meeting problems: [PROBLEMS] CRM fields available: [FIELDS] Forecast categories: [CATEGORIES] Revenue target: [TARGET] Sales cycle: [SALES CYCLE] Design the rhythm: 1. Meeting purpose Define what the meeting is for and what it is not for. 2. Pre-work Create required preparation for: - reps - managers - RevOps - leadership Include: - CRM updates - deal risk notes - forecast changes - close-date changes - next-step confirmations 3. Agenda Build a timed agenda for: - forecast rollup - category changes - high-risk commit deals - biggest upside deals - stuck deals - close date slips - pipeline coverage gaps - action commitments 4. Deal inspection questions Create questions managers should ask about: - pain - urgency - budget - authority - champion - procurement - legal - next step - close date evidence - forecast confidence 5. Output format Define what must be documented after the meeting: - forecast changes - deal actions - owners - deadlines - escalations - CRM updates Rules: - Do not let the meeting become a storytelling session. - Do not review every deal in detail. - Do not accept weak evidence for forecast changes. - Forecast meetings should produce decisions and actions. --------------------------------------------------------------------------------

#192CRM Field Governance and Data Dictionary

CRM, PIPELINE MANAGEMENT & SALES OPERATIONSRevOps, CRM admins, sales operations, Salesforce or HubSpot cleanup, reporting consistency, onboarding reps, and CRM scaling.

Create a CRM data dictionary that defines fields, ownership, allowed values, update rules, reporting purpose, and governance standards.

Act as a CRM governance architect. Build a data dictionary and field governance system for [CRM]. CRM context: CRM platform: [CRM] Sales process: [SALES PROCESS] Objects: [OBJECTS] Current fields: [CURRENT FIELDS] Reports needed: [REPORTS] Automation dependencies: [AUTOMATIONS] Data quality problems: [PROBLEMS] Users: [USERS] Admin rules: [ADMIN RULES] Create the data dictionary: A. Field classification Classify fields into: - required - optional - system-generated - automation-controlled - deprecated - manager-only - RevOps-only - leadership reporting field B. Field dictionary table For each field provide: - field name - object - definition - data type - allowed values - owner - required stage - update frequency - report usage - automation dependency - validation rule - example correct value - example incorrect value C. Picklist cleanup Recommend: - values to keep - values to merge - values to remove - values to rename - new values needed D. Governance rules Define: - who can create fields - approval process - naming convention - documentation requirement - quarterly review process - field retirement process E. User enablement Write a simple guide explaining the most important fields to reps. Rules: - Do not create fields without a report, workflow, or decision use case. - Do not allow duplicate fields with similar meaning. - Do not let old picklist values corrupt reporting. - Field governance should make CRM data trustworthy and easier to maintain. --------------------------------------------------------------------------------

#193Sales Operations SLA and Ownership Matrix

CRM, PIPELINE MANAGEMENT & SALES OPERATIONSSales operations design, handoff cleanup, inbound lead response, deal support, CRM governance, cross-functional teams, and operational accountability.

Define ownership and service-level expectations across SDRs, AEs, managers, RevOps, marketing, customer success, finance, and leadership.

You are a sales operations accountability designer. Build an SLA and ownership matrix for [SALES ORGANIZATION]. Context: Company: [COMPANY] Sales motion: [SALES MOTION] Teams involved: [TEAMS] Current handoffs: [HANDOFFS] Current ownership problems: [PROBLEMS] Lead sources: [LEAD SOURCES] Opportunity stages: [STAGES] Customer handoff process: [CUSTOMER HANDOFF] CRM platform: [CRM] Revenue goals: [GOALS] Build the SLA system: 1. Ownership map Define ownership for: - new leads - inbound response - outbound prospects - account records - contact records - opportunity records - next steps - proposal support - procurement support - legal handoff - closed-won handoff - closed-lost reason - CRM hygiene - forecast updates 2. SLA table Create a table with: - process area - owner - backup owner - trigger event - required action - SLA time - CRM update required - escalation rule - failure consequence 3. Handoff checklist Create handoff checklists for: - marketing to sales - SDR to AE - AE to sales engineer - sales to legal/procurement - sales to customer success - sales to finance 4. Escalation paths Define when and how to escalate: - missed SLA - unclear owner - blocked deal - missing data - urgent buyer request - late-stage risk 5. Reporting Define SLA metrics and dashboard views. Rules: - Do not leave shared ownership undefined. - Do not create SLAs nobody can meet. - Do not escalate every minor delay. - Clear ownership should reduce confusion and speed up execution. --------------------------------------------------------------------------------

#194Sales Automation QA and Workflow Audit

CRM, PIPELINE MANAGEMENT & SALES OPERATIONSSalesforce, HubSpot, Pipedrive, Zoho, RevOps, CRM admins, sales operations, automation cleanup, and CRM migration preparation.

Audit CRM automations, alerts, tasks, sequences, routing, lifecycle changes, and reporting dependencies to prevent broken workflows and bad data.

Act as a CRM automation QA specialist. Audit the current sales automations and identify what should be fixed, removed, simplified, or added. Automation context: CRM platform: [CRM] Current automations: [AUTOMATIONS] Sales process: [SALES PROCESS] Lead routing rules: [ROUTING] Stage automation: [STAGE AUTOMATION] Task automation: [TASKS] Sequences: [SEQUENCES] Alerts: [ALERTS] Reports affected: [REPORTS] Known issues: [ISSUES] Team complaints: [COMPLAINTS] Run the audit: A. Automation inventory Classify each automation as: - routing - notification - task creation - stage update - lifecycle update - field update - sequence enrollment - reporting support - manager alert - data hygiene - integration sync B. Risk check For each automation evaluate: - purpose - owner - trigger - action - dependency - failure mode - data risk - user experience risk - reporting risk - recommendation C. Broken workflow scenarios Identify likely issues: - duplicate tasks - conflicting stage changes - bad routing - missing alerts - alert fatigue - wrong lifecycle stage - untracked source data - automation loops - sequence mistakes - stale owner assignment D. Simplification plan Recommend what to: - keep - remove - merge - rebuild - document - test - monitor E. QA checklist Create a testing checklist for future automations. Rules: - Do not automate a broken process. - Do not add alerts without clear action. - Do not allow automations without owners. - Automation should reduce friction and improve accuracy, not create hidden errors. --------------------------------------------------------------------------------

#195Win/Loss Reason Taxonomy Builder

CRM, PIPELINE MANAGEMENT & SALES OPERATIONSClosed-won analysis, closed-lost analysis, CRM picklist cleanup, sales coaching, product feedback, marketing insights, and revenue strategy.

Build a clean win/loss reason taxonomy that helps leadership understand why deals are won, lost, delayed, discounted, or stuck.

You are a win/loss insights architect. Create a practical win/loss reason taxonomy for [COMPANY]. Context: Offer: [OFFER] Market: [MARKET] ICP: [ICP] Current win reasons: [WIN REASONS] Current loss reasons: [LOSS REASONS] Closed-won notes: [CLOSED WON NOTES] Closed-lost notes: [CLOSED LOST NOTES] Competitors: [COMPETITORS] Pricing feedback: [PRICING FEEDBACK] Product feedback: [PRODUCT FEEDBACK] Current CRM picklists: [PICKLISTS] Build the taxonomy: 1. Reason categories Create categories for: - price - budget - timing - competition - no decision - poor fit - missing feature - trust - implementation risk - stakeholder alignment - procurement/legal - value unclear - product strength - relationship strength - urgency - business priority 2. Picklist design Create clean CRM picklists for: - primary win reason - secondary win reason - primary loss reason - secondary loss reason - no-decision reason - competitor lost to - discount driver - product gap 3. Definitions For every reason provide: - definition - when to use - when not to use - example CRM note - follow-up question for manager 4. Reporting views Recommend reports that show: - losses by reason - losses by segment - losses by competitor - no-decision patterns - discount reasons - wins by value driver - product gaps by revenue impact 5. Operating process Define when and how reps must update reasons. Rules: - Do not use vague reasons like “not interested” without detail. - Do not allow too many picklist values. - Do not mix buyer reason with seller assumption. - Win/loss reasons should help the business improve decisions. --------------------------------------------------------------------------------

#196Pipeline Coverage and Gap Analysis

CRM, PIPELINE MANAGEMENT & SALES OPERATIONSSales leaders, RevOps, founders, board reporting, quarterly planning, pipeline generation, and revenue forecasting.

Calculate whether there is enough pipeline to hit targets and identify where the gap exists by source, segment, stage, rep, quarter, and forecast category.

Act as a pipeline coverage analyst. Analyze whether current pipeline is enough to hit [TARGET]. Inputs: Revenue target: [TARGET] Current pipeline: [PIPELINE DATA] Forecast period: [PERIOD] Win rates by stage: [WIN RATES] Average deal size: [AVG DEAL SIZE] Sales cycle length: [SALES CYCLE] Pipeline sources: [SOURCES] Segments: [SEGMENTS] Rep capacity: [CAPACITY] Historical pipeline coverage ratio: [HISTORICAL COVERAGE] Current forecast: [FORECAST] Create the analysis: A. Coverage calculation Calculate: - total pipeline - weighted pipeline - commit pipeline - best-case pipeline - pipeline coverage ratio - gap to target - pipeline needed - new pipeline required - time-adjusted pipeline gap B. Gap by dimension Analyze gap by: - stage - source - segment - product - rep - region - close month - deal size band - forecast category C. Risk interpretation Identify: - too much late-stage dependence - not enough early-stage creation - high concentration risk - close date bunching - weak conversion assumptions - rep capacity constraints D. Action plan Recommend actions to close the gap: - create new pipeline - accelerate existing deals - requalify stale deals - improve conversion - focus source investment - adjust forecast - shift rep capacity E. Leadership summary Write a concise executive summary with the main number, risk, and action. Rules: - Do not use weighted pipeline blindly if probabilities are unreliable. - Do not treat all pipeline dollars as equal. - Do not ignore sales cycle timing. - Coverage analysis must show where revenue risk actually sits. --------------------------------------------------------------------------------

#197Sales Rep Performance and Coaching Report

CRM, PIPELINE MANAGEMENT & SALES OPERATIONSSales managers, founders, sales enablement, RevOps, weekly one-on-ones, quarterly reviews, and performance improvement plans.

Build a rep performance report that connects activity, pipeline creation, conversion, deal quality, forecast accuracy, and coaching needs.

You are a sales performance analyst. Create a rep-level performance and coaching report. Inputs: Rep name: [REP] Role: [ROLE] Quota: [QUOTA] Performance period: [PERIOD] Activity data: [ACTIVITY] Pipeline created: [PIPELINE CREATED] Opportunities owned: [OPPORTUNITIES] Conversion rates: [CONVERSION] Win/loss data: [WIN LOSS] Forecast accuracy: [FORECAST ACCURACY] Average deal size: [AVG DEAL SIZE] Sales cycle: [SALES CYCLE] CRM hygiene data: [CRM HYGIENE] Manager notes: [NOTES] Create the report: 1. Performance snapshot Summarize: - quota attainment - pipeline created - closed-won revenue - forecast accuracy - activity level - conversion performance - CRM hygiene 2. Strengths Identify the rep’s strongest areas with evidence. 3. Risk areas Identify issues across: - low activity - poor conversion - weak discovery - low deal quality - slow follow-up - poor next-step discipline - over-forecasting - CRM hygiene - proposal conversion - discounting 4. Coaching diagnosis Separate problems into: - skill gap - process gap - territory gap - pipeline gap - messaging gap - CRM discipline gap - manager support gap 5. Coaching plan Create a 30-day plan with: - focus area - coaching activity - practice drill - manager support - measurable target - review date 6. One-on-one agenda Create a meeting agenda for discussing the report with the rep. Rules: - Do not evaluate reps by activity alone. - Do not blame reps for bad process or poor territory data. - Do not ignore forecast behavior. - Performance reporting should create better coaching, not just pressure. --------------------------------------------------------------------------------

#198CRM Adoption Improvement Plan

CRM, PIPELINE MANAGEMENT & SALES OPERATIONSSales leaders, RevOps, founders, CRM admins, sales managers, low CRM usage teams, and CRM rollout projects.

Improve CRM adoption by identifying why reps avoid updates, simplifying workflows, clarifying value, reducing friction, and creating better management habits.

Act as a CRM adoption strategist. Build a plan to improve CRM usage across [SALES TEAM]. Context: CRM platform: [CRM] Team size: [TEAM SIZE] Roles: [ROLES] Current adoption problems: [PROBLEMS] Rep complaints: [COMPLAINTS] Manager complaints: [MANAGER COMPLAINTS] Required updates: [REQUIRED UPDATES] Current dashboards: [DASHBOARDS] Current automations: [AUTOMATIONS] Training history: [TRAINING] Leadership expectations: [EXPECTATIONS] Build the adoption plan: A. Adoption diagnosis Identify likely causes: - too many fields - unclear value - duplicate work - poor mobile usability - bad automation - manager inconsistency - unclear stages - low trust in data - no consequences - no coaching use - poor onboarding B. Friction reduction Recommend what to: - remove - simplify - automate - standardize - pre-fill - make optional - make required - move to manager-only - document C. Behavior system Create habits for: - daily rep updates - post-call notes - next-step entry - weekly pipeline cleanup - manager inspection - forecast updates D. Enablement plan Create: - quick-start guide - training session outline - example records - common mistakes guide - manager coaching prompts E. Adoption metrics Track: - login frequency - activity logging - missing fields - stale deals - next-step completeness - stage accuracy - forecast update timeliness - dashboard usage Rules: - Do not solve adoption with training only. - Do not force reps into low-value admin work. - Do not ask for data managers do not use. - CRM adoption improves when the system is useful, simple, and inspected. --------------------------------------------------------------------------------

#199Sales Operations Quarterly Review

CRM, PIPELINE MANAGEMENT & SALES OPERATIONSRevOps, sales operations leaders, founders, CROs, sales managers, quarterly planning, process improvement, and system scaling.

Run a quarterly review of sales operations to evaluate CRM quality, process performance, pipeline accuracy, reporting usefulness, automation health, and operational priorities.

You are a sales operations quarterly review facilitator. Prepare a complete quarterly review for [COMPANY]. Quarter context: Company: [COMPANY] Quarter: [QUARTER] Revenue target: [TARGET] Actual revenue: [ACTUAL] Pipeline data: [PIPELINE] Forecast accuracy: [FORECAST ACCURACY] CRM health metrics: [CRM HEALTH] Sales process metrics: [PROCESS METRICS] Activity metrics: [ACTIVITY] Win/loss insights: [WIN LOSS] Automation issues: [AUTOMATION ISSUES] Reporting issues: [REPORTING ISSUES] Team feedback: [FEEDBACK] Leadership priorities: [PRIORITIES] Create the review: 1. Executive summary Write: - what improved - what worsened - what remains unclear - biggest revenue risk - biggest operational win - next-quarter priority 2. CRM health review Evaluate: - data completeness - stage accuracy - close date quality - duplicate rate - stale opportunities - required field compliance - dashboard trust 3. Process performance Review: - conversion by stage - velocity - average deal size - win rate - loss reasons - sales cycle length - handoff quality 4. Forecast performance Analyze: - forecast accuracy - slipped deals - commit reliability - best-case reliability - stage probability accuracy 5. Operations roadmap Create next-quarter initiatives ranked by: - impact - effort - owner - timeline - dependencies - success metric 6. Leadership discussion questions Create questions that help leadership decide priorities. Rules: - Do not turn the review into a data dump. - Do not hide reporting limitations. - Do not recommend too many initiatives. - The quarterly review should drive operational decisions for the next quarter. --------------------------------------------------------------------------------

#200Full CRM, Pipeline Management and Sales Operations Audit

CRM, PIPELINE MANAGEMENT & SALES OPERATIONSSales leaders, founders, RevOps teams, CRM admins, sales operations managers, CROs, consultants, agencies, SaaS companies, and teams that need a cleaner revenue operating system.

Audit and rebuild the complete sales operations system across CRM architecture, pipeline stages, data quality, forecasting, dashboards, activity reporting, automation, process visibility, and operating cadence.

Act as an independent CRM, pipeline management, and sales operations auditor. Review my current system and rebuild it into a cleaner operating model that improves execution, visibility, forecast trust, and pipeline movement. Full context: Company: [COMPANY] Website: [WEBSITE] Offer: [OFFER] Target market: [MARKET] ICP: [ICP] Buyer personas: [PERSONAS] Sales motion: [SALES MOTION] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Team structure: [TEAM STRUCTURE] CRM platform: [CRM] Current CRM objects: [OBJECTS] Current sales stages: [STAGES] Current required fields: [FIELDS] Current dashboards: [DASHBOARDS] Current reports: [REPORTS] Current automations: [AUTOMATIONS] Current forecast process: [FORECAST PROCESS] Current pipeline review process: [PIPELINE REVIEW] Current activity reporting: [ACTIVITY REPORTING] Current lead routing: [LEAD ROUTING] Current handoffs: [HANDOFFS] Current CRM problems: [CRM PROBLEMS] Current sales operations problems: [OPS PROBLEMS] Leadership reporting needs: [LEADERSHIP NEEDS] Audit across 45 dimensions: 1. CRM object architecture 2. Lead lifecycle clarity 3. Account structure 4. Contact data quality 5. Opportunity structure 6. Stage definitions 7. Stage entry criteria 8. Stage exit criteria 9. Required field logic 10. Field governance 11. Picklist quality 12. Duplicate management 13. Source attribution 14. Owner assignment 15. Lead routing 16. SDR-to-AE handoff 17. AE-to-CS handoff 18. Activity tracking 19. Next-step discipline 20. Pipeline hygiene 21. Stale deal management 22. Close date quality 23. Forecast category rules 24. Forecast accuracy 25. Deal health scoring 26. Pipeline coverage reporting 27. Stage conversion visibility 28. Sales cycle visibility 29. Win/loss reason quality 30. Rep performance reporting 31. Manager coaching visibility 32. Leadership dashboard quality 33. RevOps dashboard quality 34. Rep dashboard usefulness 35. Automation health 36. Alert usefulness 37. CRM adoption 38. Data completeness 39. Data trust 40. Meeting cadence 41. Forecast meeting quality 42. Pipeline review quality 43. Quarterly operations review 44. Process documentation 45. Overall sales operations maturity For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - revenue impact - forecast impact - execution impact - recommended fix - priority - effort - confidence level Then synthesize: A. Hard truth Explain the biggest reason the CRM or sales operations system is not trusted, not used, or not helping revenue execution. B. Rebuilt CRM operating model Create: - object architecture - clean sales stages - stage entry and exit criteria - required fields by stage - data dictionary outline - owner rules - hygiene rules - automation principles C. Rebuilt pipeline management system Create: - deal health score - pipeline hygiene rules - stage aging alerts - close date rules - stalled deal rules - forecast category rules - pipeline review cadence D. Rebuilt reporting system Create dashboards for: - individual reps - sales managers - RevOps - leadership - forecast meetings - quarterly reviews E. Sales operations toolkit Create: - CRM data dictionary template - pipeline review agenda - forecast meeting agenda - activity report design - win/loss taxonomy - SLA and ownership matrix - automation QA checklist - CRM adoption plan F. 30-day improvement roadmap Create: - first 24-hour cleanup - first 7-day CRM hygiene fix - first 14-day pipeline rule rollout - first 30-day reporting and cadence upgrade - owner assignments - success metrics G. Executive summary Write a direct summary with: - fastest CRM improvement - highest forecast risk - first field to fix - first dashboard to rebuild - first automation to audit - first pipeline rule to enforce - first meeting cadence to change - one operating principle for sales operations Rules: - Do not add complexity for its own sake. - Do not create fields, dashboards, or automations without a decision use case. - Do not blame reps before checking CRM design and manager behavior. - Use [NEEDS CRM DATA], [NEEDS SALES FEEDBACK], [NEEDS REVOPS REVIEW], [NEEDS MANAGER REVIEW], or [NEEDS LEADERSHIP DECISION] where required. - The final system should make CRM data cleaner, pipeline movement clearer, forecasting more trustworthy, and sales execution easier.

#201Strategic Account Relationship Map

ACCOUNT MANAGEMENT, EXPANSION & RETENTIONAccount managers, customer success managers, sales teams, founders, enterprise accounts, strategic customers, and post-sale relationship planning.

Build a complete relationship map for an existing customer account, including stakeholders, influence, risks, expansion paths, decision dynamics, and relationship gaps.

You are a strategic account management advisor. Build a relationship map for [ACCOUNT] so we can manage the relationship more intentionally, reduce churn risk, and identify expansion opportunities. Account context: Customer account: [ACCOUNT] Current product/service: [CURRENT OFFER] Current contract value: [CONTRACT VALUE] Customer industry: [INDUSTRY] Customer size: [COMPANY SIZE] Original buyer: [ORIGINAL BUYER] Current main contact: [MAIN CONTACT] Known users: [USERS] Known executives: [EXECUTIVES] Known blockers: [BLOCKERS] Contract renewal date: [RENEWAL DATE] Current account health: [HEALTH] Known goals: [GOALS] Known issues: [ISSUES] Expansion ideas: [EXPANSION IDEAS] Create the relationship map: 1. Stakeholder inventory List every known stakeholder and define: - name or role - department - relationship strength - influence level - decision power - daily usage level - business priority - likely concerns - current sentiment - communication preference - next relationship action 2. Influence structure Identify: - economic buyer - executive sponsor - power user - technical owner - procurement contact - finance reviewer - legal contact - internal champion - silent influencer - likely blocker - replacement risk if a contact leaves 3. Relationship gaps Find missing relationships across: - executive level - operational level - technical level - finance/procurement - end users - adjacent departments - expansion decision-makers 4. Account risk analysis Identify risks caused by: - single-threaded relationship - weak executive connection - low user engagement - poor internal visibility - unclear business value - unresolved service issues - competitor access - leadership change 5. Relationship growth plan Create a 90-day plan with: - who to engage - why they matter - message angle - meeting objective - asset to share - timing - expected outcome Rules: - Do not treat one happy contact as account security. - Do not assume the original buyer is still the most important person. - Do not push expansion before relationship coverage is strong. - The output should help us become multi-threaded, trusted, and harder to replace. --------------------------------------------------------------------------------

#202Customer Health Score Designer

ACCOUNT MANAGEMENT, EXPANSION & RETENTIONCustomer success teams, account managers, SaaS companies, service businesses, retention programs, renewal forecasting, and churn prevention.

Create a customer health score that combines usage, outcomes, relationship strength, support issues, sentiment, renewal risk, expansion potential, and executive alignment.

Act as a customer success operations strategist. Design a customer health scoring model for [CUSTOMER SEGMENT]. Inputs: Product or service: [OFFER] Customer segment: [SEGMENT] Current health signals: [CURRENT SIGNALS] Usage data available: [USAGE DATA] Support data available: [SUPPORT DATA] Relationship data available: [RELATIONSHIP DATA] Renewal data available: [RENEWAL DATA] Expansion data available: [EXPANSION DATA] Known churn patterns: [CHURN PATTERNS] Known expansion patterns: [EXPANSION PATTERNS] CRM/CS platform: [PLATFORM] Team capacity: [CAPACITY] Build the health score: A. Health dimensions Define scoring categories for: - product/service adoption - active usage - value realization - goal progress - support experience - relationship strength - executive alignment - renewal readiness - commercial risk - stakeholder change - sentiment - expansion readiness B. Scoring logic For each dimension provide: - score 0 - score 1 - score 2 - score 3 - weight - data source - update frequency - owner - evidence required C. Health categories Define thresholds for: - green / healthy - light risk - medium risk - high risk - save plan required - expansion-ready - renewal-ready D. Action rules For each category define: - account manager action - customer success action - leadership action - customer-facing message - internal note - review cadence E. Dashboard design Recommend dashboard views for: - health by segment - health by CSM - health by renewal date - high-risk accounts - expansion-ready accounts - accounts with no executive sponsor - accounts with declining usage Rules: - Do not make the score too complex to maintain. - Do not rely only on usage data. - Do not ignore qualitative relationship signals. - A useful health score should trigger action, not just describe status. --------------------------------------------------------------------------------

#203Renewal Risk Early Warning System

ACCOUNT MANAGEMENT, EXPANSION & RETENTIONRenewal management, SaaS retention, customer success teams, account managers, enterprise customers, service retainers, and revenue protection.

Detect renewal risk early by analyzing usage decline, stakeholder changes, unresolved issues, value gaps, budget pressure, competitor signals, and weak executive alignment.

You are a renewal risk analyst. Build an early warning system for renewals across [CUSTOMER BASE / ACCOUNT LIST]. Context: Customer list: [CUSTOMER LIST] Current contract values: [CONTRACT VALUES] Renewal dates: [RENEWAL DATES] Usage trends: [USAGE TRENDS] Support history: [SUPPORT HISTORY] Relationship notes: [RELATIONSHIP NOTES] Business outcomes achieved: [OUTCOMES] Open issues: [ISSUES] Competitor mentions: [COMPETITORS] Budget signals: [BUDGET SIGNALS] Stakeholder changes: [CHANGES] Current renewal process: [PROCESS] Build the early warning system: 1. Risk signal library Create warning signals across: - declining usage - low login or engagement - missed onboarding milestones - unresolved support tickets - negative sentiment - executive sponsor gone - champion changed roles - no QBR attendance - reduced meeting frequency - value not measured - procurement pressure - budget cuts - competitor evaluation - contract questions - delayed response 2. Risk scorecard Create a scorecard with: - signal - severity - probability of churn - detection method - data source - owner - first response action - escalation trigger 3. Renewal timeline Create a timeline for: - 180 days before renewal - 120 days before renewal - 90 days before renewal - 60 days before renewal - 30 days before renewal - final renewal week 4. Save motion For high-risk accounts, create: - internal risk brief - customer discovery questions - value recovery plan - executive outreach - service recovery steps - renewal negotiation guidance 5. Leadership report Create a concise renewal risk report format. Rules: - Do not wait until the renewal date to identify risk. - Do not confuse silence with satisfaction. - Do not treat all churn risk as a discount problem. - Renewal risk should be detected, owned, and acted on early. --------------------------------------------------------------------------------

#204QBR Strategy and Narrative Builder

ACCOUNT MANAGEMENT, EXPANSION & RETENTIONQBRs, executive reviews, customer success meetings, strategic account management, retention planning, and expansion discussions.

Build a quarterly business review that proves value, uncovers new priorities, strengthens executive trust, and opens expansion or renewal conversations.

Act as a QBR strategist. Create a high-impact QBR for [CUSTOMER] that feels useful to the customer, not like a vendor report. Inputs: Customer: [CUSTOMER] Current solution: [CURRENT SOLUTION] Contract value: [CONTRACT VALUE] Original goals: [ORIGINAL GOALS] Current goals: [CURRENT GOALS] Usage data: [USAGE DATA] Results achieved: [RESULTS] Support issues: [SUPPORT ISSUES] Customer feedback: [FEEDBACK] Upcoming priorities: [PRIORITIES] Renewal date: [RENEWAL DATE] Expansion opportunities: [EXPANSION OPPORTUNITIES] Attendees: [ATTENDEES] Meeting length: [LENGTH] Build the QBR: A. QBR objective Define what this QBR must accomplish for: - the customer - the executive sponsor - the day-to-day users - the account team - the renewal or expansion path B. Narrative arc Create the QBR story in this sequence: - where we started - what changed - what value was created - what still needs attention - what the customer should do next - how we can support future goals C. Slide-by-slide outline Create slides with: - title - purpose - key message - data needed - talking points - question to ask - risk to avoid D. Conversation prompts Create questions for: - executive priorities - value perception - team adoption - unresolved friction - future initiatives - renewal confidence - expansion relevance E. Follow-up plan Create: - recap email - action tracker - owner list - renewal next step - expansion next step - internal account update Rules: - Do not make the QBR only about usage metrics. - Do not surprise the customer with bad news. - Do not pitch expansion before confirming current value. - A QBR should create insight, alignment, and next steps. --------------------------------------------------------------------------------

#205Expansion Opportunity Discovery Map

ACCOUNT MANAGEMENT, EXPANSION & RETENTIONAccount expansion, cross-sell, upsell, SaaS growth, service retainers, customer success, and strategic account planning.

Identify realistic expansion opportunities inside an existing account based on usage, unmet needs, departments, workflows, business priorities, and stakeholder signals.

You are an account expansion strategist. Find practical expansion opportunities inside [ACCOUNT] without forcing an upsell. Account context: Customer: [ACCOUNT] Current product/service: [CURRENT OFFER] Current users: [USERS] Current departments: [DEPARTMENTS] Current contract: [CONTRACT] Usage patterns: [USAGE] Known goals: [GOALS] Known pain points: [PAINS] Open requests: [REQUESTS] Support history: [SUPPORT] Customer maturity: [MATURITY] Available add-ons/products/services: [EXPANSION OPTIONS] Relationship map: [RELATIONSHIP MAP] Create the expansion map: 1. Expansion source scan Look for opportunities from: - more users - more seats - more departments - more locations - new workflows - premium features - advanced support - consulting services - integrations - training - automation - reporting - compliance - strategic advisory 2. Fit analysis For each opportunity provide: - expansion idea - buyer pain it solves - department affected - stakeholder to engage - proof needed - likely objection - estimated value - implementation complexity - timing fit - confidence level 3. Expansion readiness Classify each opportunity as: - ready now - nurture - validate first - not enough value - too risky - wait until renewal 4. Discovery questions Write questions that reveal expansion need without sounding like a sales pitch. 5. Account action plan Create a 60-day plan with: - relationship step - value proof step - discovery step - internal alignment step - proposal step Rules: - Do not recommend expansion if current value is weak. - Do not upsell features disconnected from customer goals. - Do not rely on seller assumptions. - Expansion should feel like the next logical step in the customer’s success. --------------------------------------------------------------------------------

#206Churn Save Plan Generator

ACCOUNT MANAGEMENT, EXPANSION & RETENTIONHigh-risk accounts, renewal rescue, customer success escalation, service recovery, SaaS churn prevention, and executive retention intervention.

Create a structured save plan for a customer at risk of churn, including diagnosis, value recovery, executive outreach, issue resolution, renewal strategy, and retention options.

Act as a churn save strategist. Build a save plan for [CUSTOMER] that addresses the real cause of risk rather than offering a quick discount. Customer context: Customer: [CUSTOMER] Current contract value: [VALUE] Renewal date: [RENEWAL DATE] Risk level: [RISK LEVEL] Reason for churn risk: [REASON] Usage trend: [USAGE] Support issues: [ISSUES] Relationship status: [RELATIONSHIP] Business outcomes achieved: [OUTCOMES] Unmet expectations: [UNMET EXPECTATIONS] Competitor risk: [COMPETITOR] Budget risk: [BUDGET] Stakeholders involved: [STAKEHOLDERS] Internal owner: [OWNER] Build the save plan: A. Risk diagnosis Classify the risk as: - value gap - adoption gap - relationship gap - product/service gap - support failure - implementation failure - budget pressure - stakeholder change - competitor displacement - strategic priority change - poor fit B. Root cause questions Write questions to ask the customer to validate the real issue. C. Recovery plan Create actions across: - immediate response - support resolution - executive communication - user adoption - business value proof - roadmap clarification - commercial options - renewal timeline D. Save offer options Create retention options that may include: - success plan - training - executive review - temporary service credit - phased renewal - reduced scope - extended implementation support - contract restructuring For each option include: - when to use - value to customer - cost to seller - risk - approval needed E. Final recommendation Recommend whether to save, restructure, downgrade, nurture, or accept churn. Rules: - Do not assume every churn risk should be saved. - Do not offer discounts before diagnosing value. - Do not promise fixes that delivery cannot support. - The save plan must protect trust, margin, and long-term fit. --------------------------------------------------------------------------------

#207Customer Success and Sales Alignment Playbook

ACCOUNT MANAGEMENT, EXPANSION & RETENTIONPost-sale teams, SaaS companies, agencies, service businesses, RevOps, customer success operations, and revenue teams with handoff problems.

Align sales, account management, and customer success around ownership, expansion, renewals, risks, handoffs, and customer communication.

You are a revenue operations alignment specialist. Build a playbook that aligns sales, account management, and customer success for [COMPANY]. Company context: Company: [COMPANY] Offer: [OFFER] Customer segments: [SEGMENTS] Sales process: [SALES PROCESS] Onboarding process: [ONBOARDING] Renewal process: [RENEWAL] Expansion process: [EXPANSION] Current team roles: [ROLES] Current handoff problems: [PROBLEMS] CRM/CS tools: [TOOLS] Key metrics: [METRICS] Build the playbook: 1. Ownership boundaries Define ownership for: - closed-won handoff - onboarding - success plan - customer health - support escalation - renewal risk - expansion discovery - expansion sales - pricing discussion - executive alignment - churn save plan 2. Handoff standards Create handoff checklists for: - sales to onboarding - onboarding to customer success - customer success to account management - account management to sales specialist - customer success to support - account team to leadership 3. Shared account plan Define the fields every account plan must include: - customer goals - success criteria - stakeholders - adoption status - risks - expansion signals - renewal timeline - next actions 4. Meeting cadence Create cadences for: - weekly risk review - monthly expansion review - quarterly account review - pre-renewal review - post-churn review 5. Escalation rules Define when to involve: - sales leader - CS leader - product - support - finance - legal - executive sponsor Rules: - Do not let customers experience internal handoff confusion. - Do not make expansion purely a sales responsibility. - Do not let renewal risk sit only with customer success. - Alignment should create one customer-facing team, not internal friction. --------------------------------------------------------------------------------

#208Adoption Acceleration Plan

ACCOUNT MANAGEMENT, EXPANSION & RETENTIONSaaS onboarding, customer success, implementation teams, account managers, retention programs, and customers not getting full value.

Increase product or service adoption by identifying usage gaps, user friction, role-based barriers, training needs, habit formation, and value moments.

Act as an adoption strategist. Build an adoption acceleration plan for [CUSTOMER] using the information below. Inputs: Customer: [CUSTOMER] Product/service: [OFFER] Current users: [USERS] Intended users: [INTENDED USERS] Current usage data: [USAGE DATA] Important workflows: [WORKFLOWS] Adoption goals: [GOALS] Known blockers: [BLOCKERS] Training completed: [TRAINING] Support issues: [SUPPORT ISSUES] Customer maturity: [MATURITY] Time since launch: [TIME SINCE LAUNCH] Business outcomes expected: [OUTCOMES] Create the plan: A. Adoption gap analysis Identify gaps across: - user activation - feature usage - workflow integration - team habits - training completion - manager reinforcement - technical setup - internal communication - perceived value - executive visibility B. User segment plan For each user group define: - user role - current behavior - desired behavior - barrier - motivation - training need - success moment - adoption message - metric to track C. 30-day adoption sprint Create weekly actions: - week 1 diagnosis - week 2 enablement - week 3 habit reinforcement - week 4 value proof D. Customer-facing communication Write: - adoption kickoff message - user training invitation - manager enablement message - executive progress update E. Success metrics Define what adoption success looks like in measurable terms. Rules: - Do not blame users for poor adoption before identifying friction. - Do not send training without connecting it to outcomes. - Do not measure adoption only by logins. - Adoption should create repeated value moments for the customer. --------------------------------------------------------------------------------

#209Account Expansion Business Case Builder

ACCOUNT MANAGEMENT, EXPANSION & RETENTIONUpsell proposals, cross-sell offers, premium plan upgrades, additional services, enterprise expansions, and customer executive approvals.

Build a business case for expansion that connects additional spend to customer goals, measurable outcomes, risk reduction, efficiency, and strategic value.

You are an expansion business case advisor. Build a customer-facing business case for expanding [CURRENT OFFER] inside [ACCOUNT]. Account context: Customer: [ACCOUNT] Current solution: [CURRENT OFFER] Current spend: [CURRENT SPEND] Proposed expansion: [EXPANSION] Expansion price: [PRICE] Current outcomes achieved: [OUTCOMES] Remaining gaps: [GAPS] Customer strategic priorities: [PRIORITIES] Stakeholders: [STAKEHOLDERS] Usage or adoption data: [USAGE] Operational pain: [PAIN] Proof available: [PROOF] Expected implementation effort: [EFFORT] Known objections: [OBJECTIONS] Build the business case: 1. Current value foundation Summarize: - what has already been achieved - what value is proven - what adoption exists - what customer goals are supported 2. Expansion problem statement Explain: - what remains unresolved - what limits current value - what risk exists if nothing changes - what opportunity is being missed 3. Expansion value drivers For each value driver provide: - driver - current baseline - expected improvement - metric affected - confidence level - proof or assumption - customer data needed 4. Investment logic Explain the price using: - business value - operational savings - revenue opportunity - risk reduction - speed to outcome - scale benefits 5. Internal approval summary Write a summary the customer can send to finance or leadership. Rules: - Do not sell expansion before proving current value. - Do not fabricate ROI. - Separate facts from assumptions. - Expansion should look like a rational business decision, not a vendor upsell. --------------------------------------------------------------------------------

#210Referral Ask Strategy for Existing Customers

ACCOUNT MANAGEMENT, EXPANSION & RETENTIONAccount managers, founders, customer success teams, consultants, agencies, SaaS companies, and businesses growing through customer relationships.

Create a respectful referral strategy that identifies the right customers, timing, ask language, incentive options, and follow-up process.

Act as a referral growth strategist. Build a referral ask system for existing customers of [COMPANY]. Inputs: Company: [COMPANY] Offer: [OFFER] Best customer profile: [BEST CUSTOMERS] Customer results: [RESULTS] Customer satisfaction signals: [SATISFACTION SIGNALS] Target referral audience: [REFERRAL TARGET] Existing referral process: [PROCESS] Incentive policy: [INCENTIVES] Relationship tone: [TONE] Sales motion: [SALES MOTION] Build the referral system: A. Referral readiness criteria Define when a customer is ready to be asked based on: - outcome achieved - positive feedback - renewal status - relationship strength - executive sponsorship - usage/adoption - NPS or satisfaction - recent success moment B. Referral target map Identify who the customer may know: - peers in same role - companies in same industry - partner companies - vendors - investor portfolio companies - professional communities - local networks C. Ask scripts Write referral asks for: - email - call - LinkedIn - post-QBR - post-success milestone - executive sponsor - founder-to-founder D. Customer-friendly referral kit Create: - one-sentence intro - short forwardable blurb - ideal referral profile - optional intro email - thank-you message E. Follow-up process Define: - when to follow up - how to track referral source - how to thank the customer - how to report referral outcome Rules: - Do not ask customers who have unresolved issues. - Do not make the referral request feel transactional. - Do not require the customer to write everything from scratch. - A good referral ask should be easy, specific, and respectful. --------------------------------------------------------------------------------

#211Executive Sponsor Engagement Plan

ACCOUNT MANAGEMENT, EXPANSION & RETENTIONEnterprise account management, renewal protection, expansion, executive QBRs, strategic accounts, and multi-threaded customer relationships.

Strengthen senior-level relationships inside customer accounts by creating relevant executive touchpoints, value narratives, and strategic conversations.

You are an executive relationship strategist. Build an executive sponsor engagement plan for [ACCOUNT]. Account context: Customer: [ACCOUNT] Executive sponsor: [EXECUTIVE SPONSOR] Sponsor role: [ROLE] Current relationship strength: [RELATIONSHIP STRENGTH] Current solution: [OFFER] Business value delivered: [VALUE] Strategic priorities: [PRIORITIES] Renewal date: [RENEWAL DATE] Expansion potential: [EXPANSION] Known risks: [RISKS] Current day-to-day contacts: [CONTACTS] Executive communication history: [HISTORY] Create the engagement plan: 1. Executive relevance filter Define what this executive cares about: - strategic goals - financial outcomes - risk - operational efficiency - team performance - customer experience - competitive position - transformation initiatives 2. Executive touchpoint calendar Create touchpoints for: - first alignment meeting - QBR invitation - value milestone update - risk escalation - renewal planning - expansion discussion - executive thank-you - annual strategy review 3. Message themes Write executive-level messages around: - business outcomes - risk reduction - strategic alignment - adoption progress - value proof - upcoming opportunity - decision support 4. Meeting agenda Create a 30-minute executive meeting agenda with: - opening - value recap - strategic questions - risk discussion - next priority - commitment request 5. Relationship risk plan Explain what to do if: - executive sponsor is disengaged - sponsor leaves - sponsor is not the economic buyer - sponsor delegates everything - sponsor only appears at renewal Rules: - Do not waste executive time with operational updates. - Do not contact executives only when asking for renewal or expansion. - Do not overuse executive escalation. - Executive engagement should create strategic trust before commercial pressure. --------------------------------------------------------------------------------

#212Account Review Cadence Designer

ACCOUNT MANAGEMENT, EXPANSION & RETENTIONAccount management teams, customer success teams, revenue leadership, strategic account reviews, weekly risk meetings, and retention operations.

Create a repeatable account review cadence that helps teams inspect customer health, renewal risk, expansion opportunities, adoption, support issues, and next actions.

Act as an account review operations designer. Build a repeatable account review cadence for [TEAM / COMPANY]. Context: Company: [COMPANY] Customer segments: [SEGMENTS] Team roles: [ROLES] Number of accounts: [ACCOUNT COUNT] Current review process: [CURRENT PROCESS] Current problems: [PROBLEMS] CRM/CS tools: [TOOLS] Metrics available: [METRICS] Renewal cycle: [RENEWAL CYCLE] Expansion goals: [EXPANSION GOALS] Leadership needs: [LEADERSHIP NEEDS] Design the cadence: A. Account review types Create different review formats for: - weekly risk review - monthly account review - quarterly strategic account review - renewal readiness review - expansion review - churn post-mortem - executive account review B. Review agenda For each review type include: - purpose - attendees - accounts included - pre-work - agenda - decision outputs - required CRM updates - follow-up owner C. Account scoring inputs Define what must be reviewed: - health score - usage/adoption - business outcomes - support issues - relationship coverage - renewal timing - expansion signals - open risks - next actions D. Decision rules Define when to: - escalate - create save plan - ask for executive support - pursue expansion - schedule QBR - downgrade account priority - move to nurture E. Templates Create: - account review note template - risk summary template - expansion note template - leadership summary template Rules: - Do not review every account with the same depth. - Do not make reviews status-only. - Do not leave meetings without owners and deadlines. - Account reviews should create decisions, not just discussion. --------------------------------------------------------------------------------

#213Renewal Conversation Script Builder

ACCOUNT MANAGEMENT, EXPANSION & RETENTIONSaaS renewals, service retainers, customer success, account management, founder-led renewals, and recurring revenue businesses.

Create renewal conversation scripts that confirm value, surface risk, handle objections, discuss pricing, and create a clear renewal path.

You are a renewal conversation coach. Write scripts for a renewal conversation with [CUSTOMER]. Renewal context: Customer: [CUSTOMER] Current offer: [OFFER] Current contract value: [VALUE] Renewal date: [DATE] Usage/adoption: [USAGE] Results achieved: [RESULTS] Known issues: [ISSUES] Customer goals: [GOALS] Renewal risk: [RISK] Price change, if any: [PRICE CHANGE] Stakeholders: [STAKEHOLDERS] Desired renewal outcome: [OUTCOME] Create the scripts: 1. Opening script Write a natural opening that frames the renewal as a value and planning conversation. 2. Value confirmation questions Create questions that ask about: - results achieved - value perception - adoption - user experience - remaining needs - executive priorities - future goals 3. Risk-surfacing questions Create questions that uncover: - dissatisfaction - budget concern - competitor review - internal priority shift - usage gap - stakeholder concern - procurement issue 4. Renewal ask options Write renewal asks for: - confident renewal - cautious renewal - renewal with price increase - renewal with expansion - renewal with downgrade risk - renewal after service issue 5. Objection responses Write responses to: - “We need to evaluate alternatives.” - “The price is too high.” - “We are not using it enough.” - “Budget is tight.” - “We need to talk internally.” - “We are not sure about value.” 6. Follow-up email Write a recap email with next steps. Rules: - Do not start renewal talks too late. - Do not assume satisfaction. - Do not make the conversation only about contract terms. - A renewal conversation should validate value and reveal risk early. --------------------------------------------------------------------------------

#214Customer Feedback to Revenue Insight Converter

ACCOUNT MANAGEMENT, EXPANSION & RETENTIONVoice-of-customer programs, customer success teams, product feedback loops, account reviews, churn analysis, and expansion planning.

Convert customer feedback into actionable retention, expansion, product, service, support, and account management insights.

Act as a customer feedback analyst. Turn raw customer feedback into revenue-relevant insights. Customer feedback input: [PASTE FEEDBACK, CALL NOTES, SURVEY RESPONSES, SUPPORT NOTES, QBR NOTES, OR INTERVIEW TRANSCRIPTS] Business context: Offer: [OFFER] Customer segment: [SEGMENT] Account value: [ACCOUNT VALUE] Renewal date: [RENEWAL DATE] Expansion goal: [EXPANSION GOAL] Known product roadmap: [ROADMAP] Support constraints: [SUPPORT CONSTRAINTS] Team responsible: [TEAM] Analyze the feedback: A. Feedback classification Classify each theme as: - adoption issue - value gap - product request - support issue - workflow friction - pricing concern - relationship concern - expansion signal - churn risk - testimonial opportunity - roadmap input B. Revenue meaning For each theme explain: - what it means for retention - what it means for expansion - what it means for renewal timing - what it means for product/service improvement - what account action is needed C. Signal strength Rate each insight by: - frequency - severity - revenue impact - urgency - confidence - owner D. Account actions Create actions for: - account manager - customer success - product - support - leadership - sales E. Customer response Write a customer-facing response that acknowledges the feedback and explains next steps. Rules: - Do not treat all feedback as equally important. - Do not promise roadmap changes without approval. - Do not ignore positive feedback as a source of referrals or testimonials. - Feedback should become action, not just documentation. --------------------------------------------------------------------------------

#215Testimonial and Case Study Opportunity Finder

ACCOUNT MANAGEMENT, EXPANSION & RETENTIONAccount managers, customer success teams, marketing teams, founders, agencies, consultants, SaaS companies, and proof-driven growth.

Identify which customers are ready for testimonials, case studies, reviews, referrals, or public proof assets and create the right ask.

You are a customer advocacy strategist. Identify customer proof opportunities from the account data below. Customer/account data: Customer list: [CUSTOMER LIST] Results achieved: [RESULTS] Customer feedback: [FEEDBACK] Usage/adoption: [USAGE] Relationship strength: [RELATIONSHIP] Industry: [INDUSTRY] Account size: [SIZE] Renewal status: [RENEWAL] Expansion status: [EXPANSION] Known sensitivities: [SENSITIVITIES] Marketing permissions: [PERMISSIONS] Find advocacy opportunities: 1. Proof readiness score Score each customer on: - measurable outcome - customer enthusiasm - relationship strength - brand relevance - story clarity - permission likelihood - renewal stability - expansion sensitivity 2. Proof asset fit Recommend the best asset type: - short testimonial - review - logo use - written case study - video case study - webinar - reference call - referral intro - podcast/interview - anonymous story 3. Story angle For each recommended customer create: - before state - problem - why they chose us - implementation moment - result - emotional or operational change - quote angle - proof data needed 4. Ask scripts Write asks for: - email - call - post-QBR - post-renewal - executive sponsor - power user 5. Approval process Create a customer-friendly approval workflow. Rules: - Do not ask for public proof during unresolved issues. - Do not pressure customers for testimonials. - Do not publish sensitive details without permission. - Advocacy should feel like celebrating real customer success. --------------------------------------------------------------------------------

#216Multi-Threaded Account Plan Builder

ACCOUNT MANAGEMENT, EXPANSION & RETENTIONStrategic account management, enterprise accounts, customer success, renewal planning, expansion planning, and key account reviews.

Create an account plan that connects customer goals, stakeholders, risks, adoption, renewal, expansion, communication cadence, and next actions.

Act as a strategic account planner. Build a multi-threaded account plan for [ACCOUNT]. Account inputs: Account: [ACCOUNT] Industry: [INDUSTRY] Current contract: [CONTRACT] Current revenue: [REVENUE] Current solution: [SOLUTION] Original reason for buying: [ORIGINAL REASON] Customer goals: [GOALS] Business outcomes achieved: [OUTCOMES] Usage/adoption: [USAGE] Relationship map: [RELATIONSHIP MAP] Health score: [HEALTH] Renewal date: [RENEWAL] Expansion potential: [EXPANSION] Risks: [RISKS] Open support issues: [SUPPORT] Competitors: [COMPETITORS] Create the account plan: A. Account thesis Write a one-paragraph strategic summary of the account. B. Customer success plan Define: - customer outcomes - success metrics - current progress - adoption priorities - support priorities - value proof needed C. Relationship plan Map: - current relationships - missing relationships - executive sponsor path - power user path - blocker management - procurement/finance path D. Commercial plan Define: - renewal strategy - expansion strategy - pricing risk - procurement timing - contract risks - revenue potential E. 90-day action plan Create actions by week with: - owner - customer stakeholder - goal - message angle - expected output - risk F. Account review summary Create a one-page internal summary for leadership. Rules: - Do not build account plans that are just notes. - Do not ignore relationship gaps. - Do not plan expansion without value proof. - The account plan should be specific enough to manage execution. --------------------------------------------------------------------------------

#217Customer Escalation Response Plan

ACCOUNT MANAGEMENT, EXPANSION & RETENTIONCustomer success, account management, support escalations, enterprise accounts, service failures, churn prevention, and relationship repair.

Manage customer escalations with calm communication, internal ownership, root-cause review, resolution steps, executive updates, and trust recovery.

You are a customer escalation leader. Build an escalation response plan for [CUSTOMER ISSUE]. Escalation context: Customer: [CUSTOMER] Issue: [ISSUE] Severity: [SEVERITY] Customer impact: [IMPACT] Affected stakeholders: [STAKEHOLDERS] Timeline so far: [TIMELINE] Current owner: [OWNER] Internal teams involved: [TEAMS] Root cause known?: [ROOT CAUSE] Customer sentiment: [SENTIMENT] Renewal/expansion risk: [RISK] Requested resolution: [REQUEST] Constraints: [CONSTRAINTS] Create the escalation plan: 1. Immediate response Write: - internal incident summary - customer acknowledgement message - executive update, if needed - owner assignment - communication cadence 2. Impact assessment Clarify: - what happened - who is affected - business impact - operational impact - timeline impact - renewal risk - trust risk 3. Resolution workflow Create steps for: - diagnosis - workaround - permanent fix - customer confirmation - internal QA - documentation - post-resolution review 4. Communication templates Write: - first response - update message - delay message - resolution message - apology message - executive summary 5. Trust recovery Recommend actions to rebuild confidence after the issue is resolved. Rules: - Do not overpromise resolution timing. - Do not blame internal teams or the customer. - Do not leave the customer guessing. - Escalation handling should reduce uncertainty and rebuild trust. --------------------------------------------------------------------------------

#218Downgrade and Save Alternative Planner

ACCOUNT MANAGEMENT, EXPANSION & RETENTIONAt-risk renewals, budget pressure, usage gaps, customer success, account management, SaaS retention, and service retainer protection.

Create downgrade, pause, restructure, and partial-renewal options that retain customer value when full renewal or expansion is not possible.

Act as a retention commercial strategist. Build alternative paths for a customer who may not renew at the current level. Customer context: Customer: [CUSTOMER] Current contract: [CURRENT CONTRACT] Current price: [PRICE] Renewal date: [DATE] Reason for downgrade risk: [REASON] Usage/adoption: [USAGE] Value achieved: [VALUE] Customer budget status: [BUDGET] Customer goals: [GOALS] Must-have needs: [MUST HAVES] Nice-to-have needs: [NICE TO HAVES] Margin constraints: [MARGIN] Available plans/services: [OPTIONS] Build alternatives: A. Retention path options Create options such as: - full renewal - reduced scope renewal - phased renewal - downgrade - temporary pause - limited support plan - success recovery plan - department-specific renewal - usage-based option - managed exit B. Option comparison table For each option include: - customer fit - seller revenue impact - margin impact - delivery impact - risk - when to offer - what to ask in return - approval needed C. Value preservation language Write language explaining each option without making it sound like failure. D. Negotiation guardrails Define: - minimum acceptable terms - concessions allowed - concessions not allowed - give-get tradeoffs - escalation rules E. Recommended path Recommend the best retention option and explain why. Rules: - Do not treat downgrade as automatic churn. - Do not protect revenue in a way that destroys trust. - Do not reduce price without adjusting scope or terms. - The goal is to preserve value, relationship, and future expansion potential. --------------------------------------------------------------------------------

#219Customer Lifecycle Communication Calendar

ACCOUNT MANAGEMENT, EXPANSION & RETENTIONCustomer success programs, account management systems, SaaS lifecycle emails, service businesses, retention operations, and scalable post-sale communication.

Create a lifecycle communication calendar from onboarding through renewal, expansion, advocacy, and long-term retention.

You are a customer lifecycle communication strategist. Build a communication calendar for customers after they buy [OFFER]. Inputs: Offer: [OFFER] Customer segment: [SEGMENT] Customer journey stages: [STAGES] Onboarding process: [ONBOARDING] Typical adoption milestones: [MILESTONES] Renewal cycle: [RENEWAL CYCLE] Expansion moments: [EXPANSION MOMENTS] Customer success resources: [RESOURCES] Team capacity: [CAPACITY] Tone: [TONE] Create the lifecycle calendar: 1. Lifecycle stages Map communication across: - welcome - onboarding kickoff - first value moment - adoption reinforcement - usage check - success milestone - QBR - risk check - expansion discovery - renewal planning - advocacy/referral - long-term relationship 2. Calendar table For each communication include: - timing - trigger - sender - recipient - message purpose - subject line - core message - CTA - personalization data - success metric 3. Message templates Write templates for: - welcome email - onboarding progress email - usage check-in - value milestone note - risk check-in - QBR invitation - expansion discovery note - renewal planning note - referral ask 4. Automation recommendations Identify what can be automated and what must stay human. 5. Quality controls Create rules to prevent over-messaging or generic communication. Rules: - Do not send messages without a clear customer benefit. - Do not automate sensitive retention conversations. - Do not make every communication a sales pitch. - Lifecycle communication should build trust and make value visible. --------------------------------------------------------------------------------

#220Full Account Management, Expansion and Retention Audit

ACCOUNT MANAGEMENT, EXPANSION & RETENTIONCustomer success leaders, account managers, sales leaders, founders, RevOps teams, SaaS companies, agencies, consultants, and recurring revenue businesses.

Audit and rebuild the full post-sale revenue system across relationship management, health scoring, adoption, QBRs, renewals, expansion, referrals, churn prevention, and customer success alignment.

Act as an independent account management, expansion, and retention auditor. Review my current post-sale revenue system and rebuild it into a stronger operating model that protects revenue, grows existing accounts, and improves customer trust. Full context: Company: [COMPANY] Website: [WEBSITE] Offer: [OFFER] Customer segments: [SEGMENTS] Current customer count: [CUSTOMER COUNT] Average contract value: [ACV] Renewal cycle: [RENEWAL CYCLE] Current retention rate: [RETENTION RATE] Current churn rate: [CHURN RATE] Current expansion revenue: [EXPANSION REVENUE] Current account management process: [ACCOUNT MANAGEMENT PROCESS] Current customer success process: [CUSTOMER SUCCESS PROCESS] Current onboarding process: [ONBOARDING] Current QBR process: [QBR] Current renewal process: [RENEWAL] Current expansion process: [EXPANSION] Current referral process: [REFERRALS] Current health score: [HEALTH SCORE] Current CRM/CS tools: [TOOLS] Known churn reasons: [CHURN REASONS] Known expansion drivers: [EXPANSION DRIVERS] Current team roles: [ROLES] Main post-sale problems: [PROBLEMS] Audit across 45 dimensions: 1. Customer segmentation 2. Account ownership 3. Sales-to-CS handoff 4. Onboarding quality 5. Success plan quality 6. Adoption tracking 7. First value moment 8. Usage visibility 9. Health scoring 10. Relationship mapping 11. Executive sponsor engagement 12. Multi-threading 13. Customer communication cadence 14. Support escalation process 15. Value realization tracking 16. Business outcome reporting 17. QBR quality 18. Customer feedback loop 19. Renewal timeline 20. Renewal risk detection 21. Renewal conversation quality 22. Churn save process 23. Downgrade management 24. Pricing and renewal terms 25. Expansion signal detection 26. Expansion discovery 27. Expansion business case 28. Cross-sell readiness 29. Upsell readiness 30. Account planning 31. Referral process 32. Testimonial process 33. Case study process 34. Executive reporting 35. Customer success and sales alignment 36. Product feedback handoff 37. Support handoff 38. Customer lifecycle messaging 39. CRM/CS data quality 40. Dashboard quality 41. Account review cadence 42. Revenue forecasting for renewals 43. Revenue forecasting for expansion 44. Team accountability 45. Overall post-sale revenue maturity For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - retention impact - expansion impact - customer trust impact - risk if ignored - recommended fix - priority - effort - confidence level Then synthesize: A. Hard truth Explain the biggest reason the current post-sale system is leaking retention, expansion, or customer trust. B. Rebuilt account management system Create: - customer segmentation model - account ownership rules - relationship map template - account plan template - executive sponsor plan - account review cadence C. Rebuilt retention system Create: - health score model - renewal risk early warning system - renewal timeline - churn save plan - downgrade alternative plan - lifecycle communication calendar D. Rebuilt expansion system Create: - expansion signal library - expansion readiness score - expansion discovery questions - expansion business case template - referral ask system - advocacy and case study workflow E. Team operating model Create: - sales-to-CS handoff checklist - CS-to-AM expansion handoff - escalation rules - QBR operating standard - renewal meeting agenda - dashboard requirements F. 30-day improvement roadmap Create: - first 24-hour cleanup - first 7-day account risk review - first 14-day renewal and expansion system setup - first 30-day post-sale operating cadence - owner assignments - metrics to track G. Executive summary Write a direct summary with: - fastest retention improvement - highest churn risk - first expansion system to build - first QBR improvement - first health score field to add - first lifecycle message to write - first account review rule to enforce - one operating principle for long-term customer revenue Rules: - Do not focus only on expansion while ignoring customer value. - Do not treat retention as a renewal-date activity. - Do not recommend generic customer success advice. - Use [NEEDS CUSTOMER DATA], [NEEDS CRM/CS DATA], [NEEDS PRODUCT INPUT], [NEEDS SUPPORT REVIEW], [NEEDS LEADERSHIP DECISION], or [NEEDS FINANCE REVIEW] where required. - The final system should make customer value visible, risks actionable, expansion natural, and retention more predictable.

#221Sales Playbook Architecture Builder

SALES ENABLEMENT, PLAYBOOKS & TEAM TRAININGSales leaders, founders, enablement managers, RevOps teams, account executives, SDR teams, and companies that need consistent sales execution across the team.

Build a complete sales playbook that gives reps clear guidance on ICP, positioning, messaging, qualification, discovery, demos, objections, follow-up, pricing, and deal progression.

You are a sales enablement architect. Build a practical sales playbook for [COMPANY] selling [OFFER] to [ICP]. Business context: Company: [COMPANY] Offer: [OFFER] Target market: [MARKET] ICP: [ICP] Buyer personas: [BUYER PERSONAS] Sales motion: [SALES MOTION] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Team roles: [TEAM ROLES] Current sales process: [SALES PROCESS] Common objections: [OBJECTIONS] Main competitors: [COMPETITORS] Current enablement gaps: [GAPS] Create the sales playbook: 1. Playbook purpose Define what this playbook helps reps do: - find the right prospects - qualify opportunities - run better conversations - explain value - handle objections - advance deals - protect margin - use CRM properly - close with clarity 2. Core sections Create the full playbook structure with: - ICP and account fit - buyer personas - positioning - value proposition - messaging pillars - prospecting talk tracks - discovery guide - qualification framework - demo guide - objection library - competitive battlecards - proposal guidance - follow-up templates - CRM rules - manager coaching notes 3. Section-by-section content For each section provide: - purpose - what reps need to know - exact guidance to include - templates or scripts needed - examples - common mistakes - manager inspection question 4. Usage rules Define how reps should use the playbook during: - prospecting - discovery - demo prep - proposal creation - negotiation - follow-up - pipeline review 5. Maintenance plan Create: - owner - update cadence - feedback loop - win/loss input process - version control method - adoption metrics Rules: - Do not create a theoretical manual. - Do not include content reps will never use. - Do not make the playbook a static document that becomes outdated. - The playbook must help reps execute better this week. --------------------------------------------------------------------------------

#222New Sales Rep Onboarding Ramp Plan

SALES ENABLEMENT, PLAYBOOKS & TEAM TRAININGNew account executives, SDRs, BDRs, customer-facing sales hires, founder-led teams hiring first reps, sales managers, and enablement leaders.

Create a structured onboarding plan that helps new reps learn the market, offer, ICP, sales process, tools, talk tracks, and performance expectations quickly.

Act as a sales onboarding designer. Create a ramp plan for a new [ROLE] joining [COMPANY]. Inputs: Company: [COMPANY] Offer: [OFFER] Role: [ROLE] Sales motion: [SALES MOTION] Target market: [MARKET] ICP: [ICP] Buyer personas: [PERSONAS] Sales cycle: [SALES CYCLE] Tools used: [TOOLS] Current onboarding materials: [MATERIALS] Expected ramp time: [RAMP TIME] Performance targets: [TARGETS] Manager support available: [SUPPORT] Build the onboarding plan: A. Ramp outcomes Define what the rep must be able to do by: - day 1 - week 1 - week 2 - week 4 - day 60 - day 90 B. Learning curriculum Create modules for: - company and market - product or service - ICP and personas - buyer pains - positioning - messaging - discovery - qualification - demo or pitch - objections - CRM process - pricing and proposals - competitors - internal handoffs C. Practice assignments For each module create: - practice exercise - role-play activity - written assignment - call shadowing task - manager review point - pass/fail criteria D. Certification gates Create certification checkpoints for: - ICP understanding - pitch delivery - discovery questions - objection handling - CRM hygiene - demo readiness - proposal explanation - forecast discipline E. Manager coaching plan Create a weekly coaching rhythm with: - agenda - questions - scorecard - feedback method - rep self-assessment Rules: - Do not overload the rep with passive reading. - Do not let onboarding end before real selling behavior is inspected. - Do not certify reps based only on completion. - The ramp plan must create measurable selling readiness. --------------------------------------------------------------------------------

#223Discovery Script and Question Bank

SALES ENABLEMENT, PLAYBOOKS & TEAM TRAININGDiscovery calls, account executives, SDR qualification, founder-led sales, sales training, call coaching, and qualification improvement.

Build a discovery script and question bank that helps reps uncover pain, urgency, impact, decision process, budget, stakeholders, and next steps without sounding robotic.

You are a sales discovery coach. Create a discovery script for selling [OFFER] to [BUYER PERSONA]. Context: Offer: [OFFER] Buyer persona: [BUYER PERSONA] Industry: [INDUSTRY] Typical pain points: [PAINS] Desired outcomes: [OUTCOMES] Common objections: [OBJECTIONS] Qualification criteria: [QUALIFICATION] Sales stage: [STAGE] Call length: [CALL LENGTH] Tone: [TONE] Build the discovery system: 1. Call opening Write: - warm opening - agenda setting - permission-based transition - reason for asking questions - expectation setting 2. Question map Create questions for: - current situation - problem symptoms - business impact - urgency - previous attempts - decision criteria - stakeholder map - budget path - timeline - risk concerns - success metrics - next steps 3. Follow-up probes For each question category create: - surface-level question - deeper question - quantified impact question - emotional/business consequence question - disqualification question 4. Listening cues List signals that indicate: - high urgency - weak fit - hidden stakeholder - budget risk - no-decision risk - competitor involvement - implementation concern 5. Call close Write scripts for: - qualified next step - not-ready prospect - poor-fit prospect - stakeholder-introduction ask - proposal follow-up - demo handoff Rules: - Do not interrogate the buyer. - Do not pitch too early. - Do not ask questions that are already answered by public information. - Discovery should create clarity for both buyer and seller. --------------------------------------------------------------------------------

#224Objection Library Builder

SALES ENABLEMENT, PLAYBOOKS & TEAM TRAININGSales teams, account executives, SDRs, founders, sales enablement, objection training, role-play sessions, and call coaching.

Build a reusable objection-handling library with diagnosis, response principles, proof assets, talk tracks, follow-up questions, and manager coaching notes.

Act as an objection enablement specialist. Build an objection library for [OFFER]. Inputs: Offer: [OFFER] ICP: [ICP] Buyer personas: [PERSONAS] Current objections: [OBJECTIONS] Sales stages where objections appear: [STAGES] Competitors: [COMPETITORS] Proof assets available: [PROOF] Pricing model: [PRICING] Implementation process: [IMPLEMENTATION] Common reasons deals are lost: [LOSS REASONS] Create the objection library: A. Objection categories Organize objections by: - price - budget - timing - trust - competition - authority - implementation - risk - internal resources - status quo - missing feature - ROI uncertainty - procurement/legal - no urgency B. Objection diagnosis For each objection provide: - what the buyer says - what it may actually mean - stage where it appears - seriousness level - questions to ask before responding - proof needed - common seller mistake C. Response framework Create for each objection: - short response - consultative response - executive-level response - follow-up question - next-step recommendation - email follow-up version D. Training scenarios Create 10 role-play scenarios using the most important objections. E. Manager coaching notes Provide: - what good handling sounds like - what weak handling sounds like - scorecard criteria - coaching question Rules: - Do not treat every objection as resistance. - Do not respond before diagnosing the concern. - Do not use aggressive rebuttals. - Strong objection handling should increase buyer confidence, not pressure. --------------------------------------------------------------------------------

#225Qualification Framework Designer

SALES ENABLEMENT, PLAYBOOKS & TEAM TRAININGSDRs, account executives, sales managers, RevOps, founder-led sales, pipeline quality improvement, and sales process standardization.

Create a qualification framework that helps reps decide which deals deserve time, what evidence is required, and when to disqualify or nurture.

You are a sales qualification framework designer. Build a qualification system for [COMPANY]. Context: Company: [COMPANY] Offer: [OFFER] Target customers: [TARGET CUSTOMERS] Sales motion: [SALES MOTION] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Current qualification method: [CURRENT METHOD] Common bad-fit deals: [BAD FIT DEALS] Common good-fit signals: [GOOD FIT SIGNALS] Disqualification reasons: [DISQUALIFICATION REASONS] CRM fields available: [FIELDS] Build the framework: 1. Qualification dimensions Define criteria for: - ICP fit - problem fit - urgency - impact - budget path - authority - stakeholder access - decision process - timeline - technical fit - implementation fit - strategic fit 2. Scoring model Create a 0-3 scoring guide for each dimension: - 0 = not qualified - 1 = weak evidence - 2 = acceptable evidence - 3 = strong evidence Include: - evidence required - question to ask - CRM field to update - red flag - manager review trigger 3. Stage-specific qualification Define what must be true at: - lead qualification - discovery - demo - proposal - commit - closed-won 4. Disqualification rules Create clear rules for: - poor ICP fit - no pain - no urgency - no stakeholder access - no budget path - unrealistic requirements - bad timing - poor implementation fit 5. Rep guidance Write a one-page guide reps can use during calls. Rules: - Do not qualify based on enthusiasm alone. - Do not disqualify too early when evidence is missing. - Do not create a framework that is too complex to use live. - Qualification should protect time and improve pipeline quality. --------------------------------------------------------------------------------

#226Competitive Battlecard Generator

SALES ENABLEMENT, PLAYBOOKS & TEAM TRAININGSaaS sales, B2B services, agencies, consultants, crowded markets, competitive deals, sales training, and objection handling.

Create competitive battlecards that help reps position against alternatives, explain differentiation, handle competitor claims, and win without trash-talking.

Act as a competitive enablement strategist. Build a battlecard for [COMPETITOR / ALTERNATIVE] against [OUR OFFER]. Inputs: Our company: [COMPANY] Our offer: [OFFER] Competitor or alternative: [COMPETITOR] Target buyer: [BUYER] Market segment: [SEGMENT] Competitor strengths: [STRENGTHS] Competitor weaknesses: [WEAKNESSES] Our strengths: [OUR STRENGTHS] Our weaknesses: [OUR WEAKNESSES] Common buyer comparisons: [COMPARISONS] Proof assets: [PROOF] Pricing context: [PRICING] Build the battlecard: A. Competitive snapshot Summarize: - who they are - when they are considered - why buyers choose them - where they are strong - where they are vulnerable - when we should not compete B. Positioning angle Create: - one-sentence positioning - differentiation narrative - buyer problem we solve better - where we are not a fit - risk of choosing the alternative C. Discovery questions Write questions that reveal: - buyer priorities - competitor fit gaps - implementation concerns - hidden decision criteria - switching risk - proof needed D. Objection responses Write responses to: - competitor is cheaper - competitor has more features - competitor is more known - competitor is already approved - competitor seems safer - we are comparing options E. Rep talk track Create: - short call response - executive response - email response - demo positioning note - proposal positioning paragraph Rules: - Do not insult competitors. - Do not make claims without proof. - Do not pretend we win every scenario. - A battlecard should help reps guide buyers toward the right decision. --------------------------------------------------------------------------------

#227Persona-Based Sales Messaging Guide

SALES ENABLEMENT, PLAYBOOKS & TEAM TRAININGAccount executives, SDRs, sales playbooks, multi-stakeholder deals, enterprise selling, product marketing, and sales enablement content.

Create tailored messaging for each buyer persona so reps can speak to different pains, goals, objections, metrics, and decision criteria.

You are a persona messaging strategist. Build a sales messaging guide for [OFFER] across buyer personas. Context: Offer: [OFFER] Target account type: [ACCOUNT TYPE] Buyer personas: [PERSONAS] Known pains: [PAINS] Desired outcomes: [OUTCOMES] Business metrics affected: [METRICS] Common objections: [OBJECTIONS] Proof available: [PROOF] Sales channels: [CHANNELS] Create the guide: 1. Persona cards For each persona provide: - role - responsibilities - goals - pressures - pains - success metrics - buying triggers - objections - language they use - decision influence - proof they trust 2. Message map For each persona write: - primary value message - secondary value message - opening line - discovery angle - problem statement - impact statement - proof point - CTA - phrase to avoid 3. Conversation adaptation Explain how to adjust messaging for: - executive buyer - technical evaluator - financial buyer - daily user - procurement - internal champion - skeptical stakeholder 4. Multi-persona alignment Create language that connects different stakeholder priorities into one shared value story. 5. Enablement format Turn the guide into a field-ready cheat sheet. Rules: - Do not use the same message for every persona. - Do not over-personalize with stereotypes. - Do not lead with features unless the persona cares about technical detail. - Good persona messaging should help reps sound relevant quickly. --------------------------------------------------------------------------------

#228Demo Narrative and Talk Track Builder

SALES ENABLEMENT, PLAYBOOKS & TEAM TRAININGSaaS demos, product walkthroughs, sales engineers, account executives, founders, demo training, and product-led sales conversations.

Build a demo narrative that connects buyer problems to product value, proof, business outcomes, and clear next steps.

Act as a demo enablement coach. Create a demo narrative for [OFFER] targeted at [BUYER / ACCOUNT]. Demo context: Offer: [OFFER] Buyer persona: [BUYER PERSONA] Account: [ACCOUNT] Use case: [USE CASE] Pain points: [PAINS] Desired outcome: [OUTCOME] Features to show: [FEATURES] Features to avoid: [AVOID] Competitors or alternatives: [COMPETITORS] Proof points: [PROOF] Demo length: [LENGTH] Next step desired: [NEXT STEP] Build the demo enablement kit: A. Demo strategy Define: - main story - buyer problem to anchor on - outcome to show - features to prioritize - proof to include - risk to reduce - decision to advance B. Demo flow Create a timed flow: - opening - discovery recap - agenda - use-case setup - feature sequence - value moments - proof insertions - objection checkpoints - recap - next-step ask C. Talk track Write exact language for: - opening the demo - transitioning between features - connecting feature to outcome - checking relevance - handling questions - avoiding feature dumping - closing the demo D. Customization rules Explain how to adapt the demo for: - executive - practitioner - technical evaluator - finance - procurement - mixed audience E. Demo scoring rubric Create criteria for reviewing demo quality. Rules: - Do not show every feature. - Do not demo before confirming the buyer’s context. - Do not make the demo a product tour. - A strong demo should make value easier to understand. --------------------------------------------------------------------------------

#229Role-Play Scenario Pack Builder

SALES ENABLEMENT, PLAYBOOKS & TEAM TRAININGSales training, onboarding, team coaching, manager-led practice, certification, bootcamps, and skill development.

Create realistic sales role-play scenarios for training reps on discovery, objections, demos, negotiation, closing, and difficult buyer conversations.

You are a sales training simulation designer. Build a role-play scenario pack for [TEAM / ROLE]. Training context: Team role: [ROLE] Offer: [OFFER] Buyer personas: [PERSONAS] Sales skills to train: [SKILLS] Common mistakes: [MISTAKES] Common objections: [OBJECTIONS] Sales stages: [STAGES] Experience level: [EXPERIENCE LEVEL] Training duration: [DURATION] Create 12 role-play scenarios: For each scenario include: 1. Scenario title 2. Buyer profile Include: - role - company type - current situation - hidden concern - level of urgency - decision power - personality style - likely objections 3. Rep objective Define what the rep must accomplish. 4. Scenario setup Provide background the rep receives before the conversation. 5. Buyer instructions Write instructions for the person playing the buyer: - how to respond - what to reveal only if asked - what objections to raise - what strong rep behavior unlocks - what weak rep behavior triggers 6. Evaluation rubric Score: - preparation - opening - questioning - listening - relevance - value communication - objection handling - next-step control - tone - CRM follow-up 7. Debrief questions Create manager-led questions after each role-play. Rules: - Do not make scenarios too easy. - Do not make buyers unrealistically hostile. - Do not reward memorized scripts over good judgment. - Role-play should train real selling behavior, not theater. --------------------------------------------------------------------------------

#230Sales Call Coaching Scorecard

SALES ENABLEMENT, PLAYBOOKS & TEAM TRAININGDiscovery calls, demos, cold calls, qualification calls, sales coaching, call reviews, onboarding, certification, and manager enablement.

Create a call coaching scorecard that helps managers evaluate calls consistently and give specific feedback reps can apply.

Act as a sales call coaching expert. Build a call scorecard for [CALL TYPE]. Inputs: Call type: [CALL TYPE] Offer: [OFFER] Buyer persona: [BUYER] Sales stage: [STAGE] Call goal: [GOAL] Team skill level: [SKILL LEVEL] Common call issues: [ISSUES] Sales methodology: [METHODOLOGY] Manager priorities: [PRIORITIES] Create the scorecard: A. Evaluation categories Create scoring criteria for: - preparation - opening - agenda setting - rapport - buyer research - discovery depth - pain diagnosis - impact quantification - listening - relevance - value communication - objection handling - competitive positioning - next-step control - call close - CRM follow-up B. Scoring guide For each category provide: - score 1 description - score 3 description - score 5 description - evidence to listen for - common coaching note - example of strong language - example of weak language C. Call summary format Create a manager-friendly format for: - what worked - what needs improvement - biggest missed opportunity - next coaching focus - rep action item D. Coaching questions Create questions that help the rep self-assess. E. Practice assignment Recommend drills based on low-scoring areas. Rules: - Do not make the scorecard too long to use. - Do not score personality instead of behavior. - Do not give vague feedback like “be more confident.” - Call coaching should create one clear improvement action. --------------------------------------------------------------------------------

#231Sales Meeting Prep Brief Generator

SALES ENABLEMENT, PLAYBOOKS & TEAM TRAININGDiscovery calls, demos, proposal reviews, executive meetings, account planning, enterprise sales, and sales manager coaching.

Create pre-call briefs that help reps prepare for meetings with account context, buyer priorities, likely objections, questions, proof, and meeting objectives.

You are a sales meeting preparation assistant. Build a meeting prep brief for an upcoming sales conversation. Meeting details: Account: [ACCOUNT] Website: [WEBSITE] Buyer names and roles: [BUYERS] Meeting type: [MEETING TYPE] Offer: [OFFER] Sales stage: [STAGE] Previous interactions: [INTERACTIONS] Known pains: [PAINS] Known goals: [GOALS] Known objections: [OBJECTIONS] Competitors: [COMPETITORS] CRM notes: [CRM NOTES] Desired outcome: [OUTCOME] Create the prep brief: 1. Account snapshot Summarize: - business model - likely priorities - relevant market context - potential use cases - possible buying triggers 2. Buyer hypothesis For each attendee provide: - likely goals - likely concerns - influence level - questions they may ask - proof they may need - best message angle 3. Meeting objective Define: - primary objective - secondary objective - minimum acceptable outcome - next-step target 4. Conversation plan Create: - opening - questions to ask - points to validate - proof to share - objections to prepare for - close language 5. Risk checklist Flag: - missing stakeholder - weak urgency - unclear budget - unclear decision process - competitive risk - implementation concern Rules: - Do not pretend hypotheses are facts. - Do not overprepare with irrelevant research. - Do not enter the meeting without a next-step goal. - A good prep brief should help the rep sound informed and focused. --------------------------------------------------------------------------------

#232Follow-Up Template Library

SALES ENABLEMENT, PLAYBOOKS & TEAM TRAININGSDRs, account executives, sales managers, sales enablement, pipeline acceleration, post-call follow-up, proposal follow-up, and re-engagement.

Build a reusable library of follow-up messages for different sales stages, buyer situations, objections, and pipeline movement needs.

Act as a sales follow-up copywriter and enablement builder. Create a follow-up template library for [OFFER]. Context: Offer: [OFFER] Buyer personas: [PERSONAS] Sales stages: [STAGES] Common next steps: [NEXT STEPS] Common objections: [OBJECTIONS] Tone: [TONE] Channels: [EMAIL / LINKEDIN / DM / PHONE] Current follow-up problems: [PROBLEMS] Create templates for: 1. After first call Include: - recap - pain confirmed - value connection - next step - resource 2. After demo Include: - demo recap - use cases shown - questions answered - stakeholder follow-up - decision path 3. After proposal Include: - proposal recap - value reinforcement - open concerns - deadline - next meeting 4. No response Create: - gentle nudge - helpful resource - timing reset - close-the-loop - nurture fallback 5. Objection-specific follow-ups Create templates for: - price concern - timing concern - stakeholder review - competitor comparison - implementation risk - budget approval - procurement delay For each template include: - subject line - body - CTA - personalization fields - when to use - when not to use - CRM note to log Rules: - Do not write generic “checking in” messages. - Do not make every follow-up ask for time. - Do not ignore the buyer’s last concern. - Follow-up should create clarity and movement. --------------------------------------------------------------------------------

#233Buyer Enablement Asset Builder

SALES ENABLEMENT, PLAYBOOKS & TEAM TRAININGEnterprise sales, complex deals, champion enablement, proposal follow-up, procurement support, sales decks, one-pagers, and account executives.

Create reusable buyer-facing assets that help prospects explain value internally, compare options, justify spend, and reach a decision.

You are a buyer enablement strategist. Build a set of buyer-facing assets for [OFFER]. Inputs: Offer: [OFFER] Target account type: [ACCOUNT TYPE] Buyer personas: [PERSONAS] Common internal stakeholders: [STAKEHOLDERS] Main value drivers: [VALUE DRIVERS] Common objections: [OBJECTIONS] Decision criteria: [CRITERIA] Proof available: [PROOF] Implementation process: [IMPLEMENTATION] Pricing model: [PRICING] Create the asset system: A. Asset inventory Recommend assets such as: - one-page executive summary - internal forwarding email - ROI calculator - comparison guide - implementation checklist - security FAQ - stakeholder FAQ - business case template - proof library - procurement checklist B. Asset brief for each item For each asset define: - purpose - target reader - sales stage - buyer question answered - content outline - proof needed - format - length - owner - update cadence C. Priority roadmap Rank assets by: - deal impact - frequency of use - effort - urgency - buyer friction removed D. Create the first three assets Write draft content for the top 3 recommended assets. E. Rep usage guide Explain when and how reps should use each asset. Rules: - Do not create assets only sellers like. - Do not overload buyers with too much content. - Do not hide risks buyers need to evaluate. - Buyer enablement should help internal decisions happen faster. --------------------------------------------------------------------------------

#234Sales Content Inventory and Gap Audit

SALES ENABLEMENT, PLAYBOOKS & TEAM TRAININGSales enablement teams, product marketing, RevOps, sales leaders, content cleanup, playbook updates, and asset management.

Audit existing sales content, identify what is outdated or missing, and build a roadmap for enablement assets reps will actually use.

Act as a sales content auditor. Review my current sales enablement assets and identify what to keep, fix, remove, or create. Current assets: [PASTE ASSET LIST OR LINKS] Business context: Offer: [OFFER] Target market: [MARKET] Buyer personas: [PERSONAS] Sales stages: [STAGES] Common objections: [OBJECTIONS] Competitors: [COMPETITORS] Common deal blockers: [BLOCKERS] Rep feedback: [REP FEEDBACK] Manager feedback: [MANAGER FEEDBACK] Audit the content: A. Asset classification Classify each asset by: - sales stage - buyer persona - format - use case - owner - freshness - quality - usage level - revenue relevance B. Quality review Score each asset on: - clarity - buyer relevance - proof strength - objection coverage - accuracy - design/readability - rep usability - decision support C. Gap analysis Identify missing assets for: - prospecting - discovery - demo - proposal - negotiation - procurement - competitor comparison - onboarding - expansion - renewal D. Retirement list Identify assets that should be: - removed - archived - merged - rewritten - updated - redesigned E. Roadmap Create a 30/60/90-day asset roadmap with: - asset name - priority - owner - inputs needed - deadline - success metric Rules: - Do not keep assets because they took effort to create. - Do not create content without a sales-stage use case. - Do not ignore rep adoption data. - The asset library should become smaller, sharper, and easier to use. --------------------------------------------------------------------------------

#235Sales Certification Program Designer

SALES ENABLEMENT, PLAYBOOKS & TEAM TRAININGSales onboarding, team training, enablement leaders, managers, sales certification, quality control, and scaling sales teams.

Build a certification program that verifies reps can explain the offer, qualify buyers, run discovery, handle objections, use CRM, and progress deals correctly.

You are a sales certification program designer. Create a certification system for [ROLE] at [COMPANY]. Context: Role: [ROLE] Company: [COMPANY] Offer: [OFFER] Sales process: [SALES PROCESS] Buyer personas: [PERSONAS] Required skills: [SKILLS] Current training materials: [MATERIALS] Manager expectations: [EXPECTATIONS] Ramp timeline: [TIMELINE] Performance standards: [STANDARDS] Design the certification program: 1. Certification levels Create levels such as: - product knowledge certified - messaging certified - discovery certified - demo certified - objection certified - CRM certified - full sales-ready certified 2. Requirements by level For each level define: - skill being tested - materials to study - live exercise - written exercise - role-play scenario - pass criteria - failure criteria - remediation path 3. Assessment rubrics Create scorecards for: - pitch - discovery - qualification - demo - objection handling - follow-up - CRM update - forecast explanation 4. Certification schedule Build a timeline from first day to full certification. 5. Governance Define: - who certifies - how often reps recertify - how results are documented - what happens if a rep does not pass - how managers use certification results Rules: - Do not certify based only on attendance. - Do not make certification feel like punishment. - Do not test trivia instead of selling behavior. - Certification should protect quality and improve confidence. --------------------------------------------------------------------------------

#236Manager Coaching Cadence Builder

SALES ENABLEMENT, PLAYBOOKS & TEAM TRAININGSales managers, frontline leaders, founders managing reps, enablement teams, coaching programs, one-on-ones, and performance improvement.

Create a structured coaching cadence that helps managers inspect calls, review pipeline, improve skills, reinforce playbooks, and support consistent rep development.

Act as a frontline sales coaching designer. Build a coaching cadence for managers leading [TEAM / ROLE]. Inputs: Team role: [ROLE] Team size: [TEAM SIZE] Sales motion: [SALES MOTION] Current coaching process: [CURRENT PROCESS] Manager capacity: [CAPACITY] Rep experience levels: [EXPERIENCE] Performance issues: [ISSUES] Enablement materials: [MATERIALS] CRM data available: [CRM DATA] Call recordings available: [CALLS] Create the coaching system: A. Coaching rhythm Design: - weekly one-on-one - call review - pipeline review - role-play session - deal strategy session - team training - monthly skill review - quarterly development review B. Each session format For each coaching session provide: - purpose - duration - preparation - agenda - manager questions - rep self-assessment - output - follow-up action C. Skill focus map Create coaching tracks for: - prospecting - discovery - qualification - demo - objection handling - negotiation - follow-up - CRM hygiene - forecast discipline D. Coaching documentation Create a template for tracking: - skill focus - evidence - feedback - action item - deadline - improvement signal E. Manager standards Define what good coaching looks like and what to avoid. Rules: - Do not make coaching only about pipeline pressure. - Do not give vague feedback without practice. - Do not coach everything at once. - A strong cadence should create visible rep improvement over time. --------------------------------------------------------------------------------

#237SDR-to-AE Handoff Playbook

SALES ENABLEMENT, PLAYBOOKS & TEAM TRAININGSDR teams, BDR teams, account executives, inbound sales, outbound sales, RevOps, sales managers, and sales process design.

Create a clear handoff process between SDRs and AEs that protects context, improves meeting quality, prevents duplicated questions, and improves conversion.

You are a sales handoff operations expert. Build an SDR-to-AE handoff playbook for [COMPANY]. Context: Company: [COMPANY] Offer: [OFFER] Lead sources: [LEAD SOURCES] SDR role: [SDR ROLE] AE role: [AE ROLE] Qualification criteria: [QUALIFICATION] Current handoff problems: [PROBLEMS] CRM platform: [CRM] Meeting booking process: [BOOKING PROCESS] Required CRM fields: [FIELDS] Build the handoff playbook: 1. Handoff principles Define what the handoff must preserve: - buyer context - pain - urgency - qualification evidence - source attribution - objections - meeting objective - stakeholder notes - next-step expectation 2. Qualification minimum Define what must be confirmed before handoff: - ICP fit - buyer role - problem - interest - timing - authority level - company context - next meeting purpose 3. Handoff note template Create a CRM note template with: - account summary - buyer summary - pain - impact - current situation - trigger - objections - qualification score - meeting objective - recommended AE angle 4. AE prep process Define what AE must do before the meeting. 5. Feedback loop Create a process for AEs to rate lead quality and help SDRs improve. Rules: - Do not let SDRs pass vague interest as qualified pipeline. - Do not make buyers repeat everything they already shared. - Do not allow handoffs without CRM context. - A good handoff increases buyer trust and AE effectiveness. --------------------------------------------------------------------------------

#238Sales Enablement Knowledge Base Designer

SALES ENABLEMENT, PLAYBOOKS & TEAM TRAININGEnablement teams, sales leaders, RevOps, startups scaling sales, Notion libraries, Google Drive cleanup, internal wikis, and CRM-linked resources.

Design a sales enablement knowledge base that organizes playbooks, scripts, battlecards, training, templates, assets, and updates so reps can find what they need quickly.

Act as a sales enablement knowledge base architect. Design an organized knowledge base for [SALES TEAM]. Context: Team: [TEAM] Company: [COMPANY] Offer: [OFFER] Current asset locations: [LOCATIONS] Current problems: [PROBLEMS] Sales stages: [STAGES] Buyer personas: [PERSONAS] Tools used: [TOOLS] Asset owners: [OWNERS] Update cadence: [CADENCE] Create the knowledge base: A. Navigation structure Design top-level sections for: - start here - sales playbook - ICP and personas - messaging - scripts - discovery - demos - objections - competitors - pricing - proposals - follow-up - CRM process - training - coaching - buyer assets - updates B. Page template Create a template for each asset page with: - purpose - owner - last updated - sales stage - persona - when to use - when not to use - copyable content - related assets - feedback link C. Search and naming rules Define: - naming conventions - tags - folder rules - archived content rules - version control - owner responsibilities D. Launch plan Create: - cleanup steps - migration plan - announcement - training session - adoption metrics E. Governance Define how new assets are requested, approved, updated, and retired. Rules: - Do not create a library reps cannot navigate. - Do not store outdated assets next to current assets. - Do not create pages without owners. - The knowledge base should reduce search time and improve consistency. --------------------------------------------------------------------------------

#239Win/Loss Learning Loop for Enablement

SALES ENABLEMENT, PLAYBOOKS & TEAM TRAININGSales enablement, product marketing, sales leaders, RevOps, win/loss programs, competitive intelligence, and continuous sales improvement.

Turn win/loss insights into better talk tracks, training modules, objection handling, battlecards, messaging, and sales process improvements.

You are a win/loss enablement analyst. Build a learning loop that converts closed deal insights into sales training and playbook updates. Inputs: Closed-won notes: [CLOSED WON NOTES] Closed-lost notes: [CLOSED LOST NOTES] Win/loss reasons: [REASONS] Call recordings or summaries: [CALLS] Competitor notes: [COMPETITORS] Pricing feedback: [PRICING] Objection data: [OBJECTIONS] Rep feedback: [REP FEEDBACK] Manager feedback: [MANAGER FEEDBACK] Current playbook: [PLAYBOOK] Create the learning loop: 1. Insight extraction Identify patterns across: - why buyers choose us - why buyers choose competitors - why buyers do nothing - what objections appear most - what messaging works - where reps lose control - what proof matters - where deals stall 2. Enablement translation Convert insights into: - new talk tracks - updated discovery questions - objection responses - battlecard updates - pricing explanation updates - demo adjustments - follow-up templates - training modules 3. Feedback cycle Create a monthly process for: - collecting closed deal notes - reviewing calls - interviewing reps - updating content - training the team - measuring adoption - tracking performance changes 4. Output templates Create templates for: - win insight - loss insight - enablement action - playbook change - training topic - manager coaching question 5. Metrics Define how to measure if the learning loop improves performance. Rules: - Do not collect win/loss data without using it. - Do not treat one lost deal as a universal pattern. - Do not update playbooks without training the team. - Enablement should become smarter after every deal cycle. --------------------------------------------------------------------------------

#240Full Sales Enablement, Playbooks and Team Training Audit

SALES ENABLEMENT, PLAYBOOKS & TEAM TRAININGSales leaders, founders, enablement teams, RevOps, sales managers, SaaS companies, agencies, consultants, and teams that need repeatable sales performance.

Audit and rebuild the complete sales enablement system across playbooks, onboarding, training, talk tracks, qualification, discovery, objection handling, battlecards, coaching, certification, and asset management.

Act as an independent sales enablement auditor. Review my current sales enablement system and rebuild it into a practical operating system that improves consistency, rep readiness, buyer conversations, and revenue execution. Full context: Company: [COMPANY] Website: [WEBSITE] Offer: [OFFER] Target market: [MARKET] ICP: [ICP] Buyer personas: [PERSONAS] Sales motion: [SALES MOTION] Sales team roles: [ROLES] Team size: [TEAM SIZE] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] Current sales process: [SALES PROCESS] Current playbook: [PLAYBOOK] Current onboarding process: [ONBOARDING] Current training materials: [TRAINING] Current scripts and talk tracks: [SCRIPTS] Current objection library: [OBJECTIONS] Current battlecards: [BATTLECARDS] Current qualification framework: [QUALIFICATION] Current coaching process: [COACHING] Current certification process: [CERTIFICATION] Current sales asset library: [ASSETS] Current CRM process: [CRM PROCESS] Win/loss insights: [WIN LOSS] Rep feedback: [REP FEEDBACK] Manager feedback: [MANAGER FEEDBACK] Main enablement problems: [PROBLEMS] Audit across 45 dimensions: 1. Playbook completeness 2. Playbook usability 3. ICP clarity 4. Persona clarity 5. Positioning clarity 6. Messaging consistency 7. Prospecting talk tracks 8. Discovery script quality 9. Discovery question depth 10. Qualification framework 11. Demo narrative 12. Value communication 13. Objection library 14. Competitive battlecards 15. Pricing explanation 16. Proposal guidance 17. Follow-up templates 18. Buyer enablement assets 19. Internal forwarding assets 20. CRM usage guidance 21. SDR-to-AE handoff 22. AE-to-CS handoff 23. New rep onboarding 24. Ramp milestones 25. Practice assignments 26. Role-play quality 27. Call coaching scorecards 28. Manager coaching cadence 29. Certification standards 30. Rep skill visibility 31. Training reinforcement 32. Sales content inventory 33. Asset searchability 34. Asset freshness 35. Asset ownership 36. Enablement adoption 37. Rep feedback loop 38. Manager feedback loop 39. Win/loss learning loop 40. Competitive intelligence updates 41. Product update enablement 42. Enablement metrics 43. Enablement governance 44. 30-day improvement priorities 45. Overall sales enablement maturity For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - sales impact - buyer impact - manager impact - recommended fix - priority - effort - confidence level Then synthesize: A. Hard truth Explain the biggest reason the current enablement system is not improving rep performance or buyer conversations. B. Rebuilt sales playbook Create: - playbook structure - required sections - field-ready scripts - qualification rules - discovery guide - demo guide - objection library structure - battlecard structure - follow-up templates - CRM guidance C. Rebuilt training system Create: - onboarding path - ramp milestones - role-play program - certification gates - call coaching cadence - manager coaching rhythm - rep skill scorecard D. Rebuilt asset system Create: - asset inventory structure - buyer enablement asset list - content gap roadmap - knowledge base structure - governance rules - update cadence E. 30-day enablement roadmap Create: - first 24-hour cleanup - first 7-day playbook fix - first 14-day training upgrade - first 30-day enablement rollout - owner assignments - adoption metrics - performance metrics F. Executive summary Write a direct summary with: - fastest enablement improvement - biggest rep readiness gap - first playbook section to rebuild - first talk track to improve - first asset to create - first coaching habit to install - first certification gate to add - one operating principle for stronger sales enablement Rules: - Do not create enablement content that reps cannot use in live selling. - Do not solve every problem with another document. - Do not separate training from manager coaching. - Use [NEEDS REP FEEDBACK], [NEEDS MANAGER REVIEW], [NEEDS CALL DATA], [NEEDS CRM DATA], or [NEEDS LEADERSHIP DECISION] where required. - The final system should make reps more prepared, conversations more consistent, and revenue execution easier to manage.

#241AI Prospect Research Brief Builder

AI SALES AUTOMATION & REVENUE SYSTEMSSDRs, BDRs, account executives, founder-led sales, account-based selling, enterprise prospecting, and teams using AI for faster account preparation.

Turn scattered public and CRM account information into a concise sales research brief that helps reps personalize outreach, prepare calls, and identify business-relevant angles.

You are an AI sales research analyst. Create a prospect research brief for [ACCOUNT] so a sales rep can prepare a relevant conversation without wasting time. Inputs: Company name: [COMPANY] Website: [WEBSITE] Target buyer: [BUYER NAME / ROLE] Offer we sell: [OFFER] Target ICP: [ICP] Industry: [INDUSTRY] Known CRM notes: [CRM NOTES] Recent interaction history: [INTERACTION HISTORY] Known competitors or alternatives: [COMPETITORS] Public information available: [PASTE RESEARCH OR LINKS] Sales stage: [STAGE] Desired next action: [NEXT ACTION] Build the research brief: A. Account snapshot Summarize: - what the company does - likely business model - likely customers - likely growth priorities - likely operational pressures - relevant market context Mark anything uncertain as [NEEDS VERIFICATION]. B. Buyer relevance map For the target buyer, identify: - likely responsibilities - likely goals - likely pains - likely metrics they care about - likely objections - language they may use internally - what proof they will trust C. Sales angle selection Create 5 outreach or meeting angles ranked by: - relevance - confidence - business impact - personalization strength - risk of sounding generic D. Conversation prep Create: - opening observation - 7 discovery questions - 3 value hypotheses - 3 possible objections - proof asset to use - next-step suggestion E. Rep-ready summary Write a 120-word briefing the rep can read before a call. Rules: - Do not invent facts. - Do not use fake personalization. - Do not mention sensitive or private assumptions. - Separate verified facts from hypotheses. - The output must help a human rep make a better judgment, not replace the rep. --------------------------------------------------------------------------------

#242Outreach Personalization Engine

AI SALES AUTOMATION & REVENUE SYSTEMSCold email, LinkedIn outreach, DMs, outbound campaigns, account-based prospecting, SDR workflows, and AI-assisted personalization at scale.

Generate personalized outreach messages from researched signals while keeping the message specific, concise, ethical, and human-sounding.

Act as a senior outbound copywriter and personalization QA reviewer. Create personalized outreach for [BUYER] at [ACCOUNT]. Context: Offer: [OFFER] Target persona: [PERSONA] Account: [ACCOUNT] Buyer role: [ROLE] Personalization signals: [SIGNALS] Pain hypothesis: [PAIN HYPOTHESIS] Business outcome we support: [OUTCOME] Proof point: [PROOF] CTA: [CTA] Channel: [EMAIL / LINKEDIN / DM] Tone: [TONE] Max length: [LENGTH] Produce the outreach in this sequence: 1. Signal audit Classify each signal as: - strong and usable - weak but usable - too generic - risky or irrelevant - needs verification 2. Message strategy Select one primary angle and explain in one sentence why it fits. 3. Draft variations Write: - version A: direct business angle - version B: problem-led angle - version C: proof-led angle - version D: curiosity-led angle - version E: referral-style angle 4. Subject lines or openers Create 10 options. 5. Human QA Review the best draft for: - does it sound automated? - is the personalization real? - is the ask too big? - is the message too long? - is the value clear? - could the buyer reply easily? 6. Final version Provide one final recommended message. Rules: - Do not use exaggerated flattery. - Do not imply personal knowledge we do not have. - Do not over-personalize from irrelevant data. - Do not write generic “I noticed your company is growing” copy. - The final message must be easy for a real salesperson to send. --------------------------------------------------------------------------------

#243AI Lead Scoring and Routing Model

AI SALES AUTOMATION & REVENUE SYSTEMSRevOps teams, SDR teams, inbound lead management, CRM automation, marketing-to-sales handoffs, lead qualification, and sales operations.

Build an AI-assisted lead scoring and routing model that prioritizes qualified prospects while keeping criteria transparent and reviewable by humans.

You are a revenue operations analyst. Design an AI-assisted lead scoring and routing model for [COMPANY]. Business context: Company: [COMPANY] Offer: [OFFER] ICP: [ICP] Buyer personas: [PERSONAS] Lead sources: [LEAD SOURCES] Current lead fields: [FIELDS] Current routing rules: [ROUTING] Current lead quality problems: [PROBLEMS] Sales territories: [TERRITORIES] Team roles: [ROLES] CRM platform: [CRM] Data available to AI: [DATA] Data not allowed: [RESTRICTED DATA] Design the model: A. Scoring dimensions Create a scoring system for: - firmographic fit - role fit - problem fit - intent signal - engagement level - company size fit - industry fit - timing signal - source quality - potential deal size - urgency proxy - disqualification risk B. Score explanation For each dimension provide: - score range - field needed - positive signals - negative signals - missing-data behavior - human review trigger C. Routing logic Create routing rules by: - territory - segment - product interest - company size - account ownership - inbound priority - named account status - rep capacity D. Human oversight Define: - when AI can auto-prioritize - when AI must ask for review - when AI must not route automatically - who approves edge cases E. CRM implementation Recommend: - fields to add - fields to standardize - dashboards - alerts - weekly QA process - feedback loop from sales Rules: - Do not use hidden or unexplainable scoring. - Do not score on sensitive personal attributes. - Do not route leads without ownership clarity. - Do not treat missing data as negative unless explicitly justified. - The model must improve prioritization without removing human judgment. --------------------------------------------------------------------------------

#244AI CRM Update Assistant SOP

AI SALES AUTOMATION & REVENUE SYSTEMSSales teams, RevOps, CRM admins, account executives, SDRs, sales managers, and teams trying to reduce manual CRM work.

Create a standard operating procedure for using AI to turn calls, emails, notes, and meetings into clean CRM updates without corrupting data.

Act as a CRM workflow designer. Create an SOP for an AI assistant that updates CRM records from sales activity notes. Inputs: CRM platform: [CRM] Objects to update: [LEADS / CONTACTS / ACCOUNTS / OPPORTUNITIES] Allowed fields: [ALLOWED FIELDS] Fields AI must not update: [LOCKED FIELDS] Source materials: [CALL NOTES / EMAILS / TRANSCRIPTS / MEETING NOTES] Sales stages: [STAGES] Required CRM standards: [STANDARDS] Common data problems: [PROBLEMS] Approval rules: [APPROVAL RULES] Create the SOP: 1. AI assistant role Define what the assistant can do and cannot do. 2. Input format Create a template for giving AI: - source notes - account name - contact name - opportunity name - current stage - current next step - current owner - update request 3. Extraction rules Tell AI how to extract: - pain - impact - stakeholders - objections - next step - decision process - budget signal - timing signal - competitor mention - follow-up task - risk note 4. CRM update format Output changes as: - field name - old value - proposed new value - evidence from source - confidence level - human approval needed - reason for update 5. QA checklist Before applying updates, check: - no invented facts - no overwritten critical fields - no ambiguous owner changes - no stage movement without evidence - no duplicated notes - no private or sensitive information added unnecessarily 6. Escalation rules Define when the assistant must stop and ask a human. Rules: - Do not update CRM fields without source evidence. - Do not move stages unless exit criteria are met. - Do not replace manager judgment. - Do not store unnecessary sensitive information. - Every proposed update must be traceable to the source. --------------------------------------------------------------------------------

#245Call Summary to Deal Action Converter

AI SALES AUTOMATION & REVENUE SYSTEMSCall recording analysis, post-call workflows, account executives, SDRs, sales managers, CRM updates, and pipeline follow-up.

Convert sales call transcripts into concise summaries, CRM notes, follow-up tasks, risk flags, and next-step recommendations.

You are an AI sales call analyst. Convert this call transcript into deal actions. Call context: Account: [ACCOUNT] Buyer: [BUYER] Seller: [SELLER] Offer: [OFFER] Sales stage before call: [STAGE] Call type: [DISCOVERY / DEMO / PROPOSAL / NEGOTIATION / RENEWAL] Transcript or notes: [TRANSCRIPT] Current CRM notes: [CRM NOTES] Expected outcome: [EXPECTED OUTCOME] Create the output: A. 10-line call summary Summarize only what was actually discussed. B. Buyer signal extraction Extract: - stated pain - quantified impact - desired outcome - urgency signal - budget signal - authority signal - decision process - stakeholders mentioned - competitors mentioned - objections raised - implementation concerns - legal/procurement concerns C. Deal action table Create a table with: - action - owner - due date - why it matters - source evidence - risk if skipped D. CRM note Write a clean CRM note in this format: - call purpose - buyer context - key pain - value discussed - objections - next step - risk - follow-up required E. Follow-up draft Write a follow-up email with: - recap - open questions - promised resources - next-step confirmation - CTA F. Deal risk assessment Classify the deal as: - stronger after call - unchanged - weaker after call - needs requalification - likely stalled Rules: - Do not infer facts not stated in the transcript. - Do not make the buyer sound more committed than they were. - Use [NEEDS HUMAN REVIEW] for ambiguous moments. - The output should help the rep act immediately after the call. --------------------------------------------------------------------------------

#246AI Follow-Up Generation Quality Gate

AI SALES AUTOMATION & REVENUE SYSTEMSAI email assistants, SDR teams, account executives, sales managers, outbound teams, post-call workflows, and follow-up automation.

Build a QA system that checks AI-generated sales follow-ups for relevance, accuracy, tone, next-step clarity, and buyer trust before sending.

Act as a sales follow-up QA reviewer. Review and improve this AI-generated follow-up before it is sent. Inputs: Original buyer conversation: [CONVERSATION / NOTES] Buyer: [BUYER] Account: [ACCOUNT] Sales stage: [STAGE] Offer: [OFFER] Promised next step: [NEXT STEP] AI-generated draft: [DRAFT] Tone standard: [TONE] Compliance or brand rules: [RULES] Run the quality gate: 1. Accuracy check Identify: - claims supported by the conversation - claims not supported - exaggerated value statements - missing promised items - incorrect next steps - invented urgency - unclear timing 2. Buyer relevance check Evaluate: - does it reference the buyer’s real concern? - does it answer the right question? - does it support the current stage? - does it help the buyer move internally? - does it avoid generic filler? 3. Trust check Score the draft from 1 to 10 on: - clarity - specificity - honesty - tone - helpfulness - CTA quality - pressure level - length 4. Fix list Provide: - must remove - must add - must clarify - must soften - must make more specific 5. Final follow-up Rewrite the message. 6. Send recommendation Choose: - ready to send - send after human review - do not send - needs missing data Rules: - Do not approve a message with unsupported claims. - Do not increase pressure to create false urgency. - Do not hide uncertainty. - The final message must protect buyer trust. --------------------------------------------------------------------------------

#247AI Proposal Drafting Copilot

AI SALES AUTOMATION & REVENUE SYSTEMSAccount executives, consultants, agencies, SaaS sales, enterprise proposals, service proposals, and founder-led sales.

Use AI to draft sales proposals that are specific to the buyer’s problem, decision criteria, value case, implementation needs, pricing logic, and next steps.

You are a proposal drafting copilot. Create a buyer-specific proposal draft for [ACCOUNT]. Deal context: Account: [ACCOUNT] Buyer: [BUYER] Offer: [OFFER] Problem discussed: [PROBLEM] Business impact: [IMPACT] Desired outcome: [OUTCOME] Decision criteria: [CRITERIA] Stakeholders: [STAKEHOLDERS] Recommended solution: [SOLUTION] Scope: [SCOPE] Pricing: [PRICING] Timeline: [TIMELINE] Implementation process: [IMPLEMENTATION] Proof points: [PROOF] Known objections: [OBJECTIONS] Legal or procurement requirements: [REQUIREMENTS] Tone: [TONE] Draft the proposal: A. Buyer-specific opening Write a short opening that proves we understand their situation. B. Problem and impact Frame the business problem without exaggeration. C. Recommended solution Explain: - what is included - how it works - why it fits - what is not included - assumptions D. Value case Connect the solution to: - business outcome - operational improvement - cost reduction - revenue opportunity - risk reduction - team efficiency E. Implementation plan Create: - phases - responsibilities - timeline - buyer requirements - success milestones F. Pricing explanation Explain the investment in value-based language. G. Risk reversal Add appropriate confidence builders: - proof - references - pilot structure - milestones - support model - exit or review point H. Next steps Create a clear approval path. Rules: - Do not invent proof, case studies, or guarantees. - Do not overpromise outcomes. - Do not hide scope assumptions. - Use [NEEDS HUMAN REVIEW] for pricing, legal, claims, and timelines. - The proposal should sound like it was written for this buyer, not generated from a template. --------------------------------------------------------------------------------

#248Pipeline Risk Detection Agent

AI SALES AUTOMATION & REVENUE SYSTEMSSales managers, RevOps, account executives, pipeline reviews, forecast calls, and AI-assisted deal inspection.

Identify hidden pipeline risks from CRM data and recommend specific actions before deals slip, stall, or disappear.

Act as an AI pipeline risk detection agent. Review this pipeline data and flag deals that need attention. Pipeline data: [PASTE CRM PIPELINE DATA] Additional context: Sales stages: [STAGES] Stage exit criteria: [EXIT CRITERIA] Forecast categories: [FORECAST CATEGORIES] Average sales cycle: [SALES CYCLE] Target period: [PERIOD] Current revenue target: [TARGET] Common slip reasons: [SLIP REASONS] Required next-step rules: [NEXT STEP RULES] Analyze the pipeline using these lenses: 1. Risk patterns Flag deals with: - stale activity - no buyer-owned next step - close date in the past - repeated close date movement - stage aging - missing decision process - missing economic buyer - missing budget evidence - late procurement - unresolved legal risk - weak champion - no recent engagement - suspiciously high forecast category 2. Risk scoring For each flagged deal provide: - risk score from 1 to 100 - risk category - evidence - likely consequence - recommended forecast adjustment - recommended next action - owner - due date 3. Pipeline view Group deals into: - protect - accelerate - requalify - manager review - close-lost candidate - nurture - procurement/legal watch 4. Priority actions Create a top 10 action list for this week. 5. Manager notes Write questions a manager should ask the rep for each high-risk deal. Rules: - Do not downgrade deals without explaining evidence. - Do not rely only on deal size. - Do not assume CRM probabilities are accurate. - Use [NEEDS CRM REVIEW] where data is incomplete. - The output must produce action, not just analysis. --------------------------------------------------------------------------------

#249AI Weekly Sales Manager Revenue Brief

AI SALES AUTOMATION & REVENUE SYSTEMSSales managers, founders, CROs, RevOps, weekly revenue meetings, leadership reporting, and forecast preparation.

Generate a weekly sales leadership brief from pipeline, activity, forecast, risks, and team performance data.

You are an AI sales operations analyst. Build a weekly revenue brief for [SALES TEAM]. Inputs: Reporting period: [PERIOD] Revenue target: [TARGET] Closed-won this period: [CLOSED WON] Pipeline created: [PIPELINE CREATED] Current pipeline: [PIPELINE] Forecast data: [FORECAST] Activity data: [ACTIVITY] Rep performance data: [REP DATA] Stage conversion data: [CONVERSION] Slipped deals: [SLIPPED DEALS] At-risk deals: [AT RISK DEALS] Win/loss notes: [WIN LOSS] Manager priorities: [PRIORITIES] Create the brief: 1. Executive summary Write 8 bullets covering: - where we stand - forecast confidence - biggest risk - biggest opportunity - rep/team issue - pipeline gap - action needed - leadership decision needed 2. Numbers that matter Create a table with: - metric - current value - previous period - change - interpretation - action required 3. Pipeline health Analyze: - coverage - stage distribution - close date quality - aging - stale deals - pipeline concentration - source quality 4. Forecast movement Explain: - what moved up - what moved down - what slipped - what is uncertain - what needs inspection 5. Team execution Identify: - strongest performers - reps needing support - activity-to-outcome patterns - CRM hygiene issues - coaching priorities 6. Next-week action plan Create: - top 5 manager actions - top 5 rep actions - RevOps actions - leadership decisions Rules: - Do not hide uncertainty. - Do not turn this into a data dump. - Do not invent reasons if the data does not show them. - Use [NEEDS DATA] where information is missing. - The brief should help leadership make decisions quickly. --------------------------------------------------------------------------------

#250AI Sales Inbox and Reply Triage System

AI SALES AUTOMATION & REVENUE SYSTEMSSDR teams, account executives, inbound replies, cold outreach, customer expansion, renewals, sales inbox management, and CRM-linked workflows.

Use AI to categorize prospect and customer replies, identify intent, recommend next actions, draft responses, and prevent important messages from being missed.

Act as a sales inbox triage assistant. Classify these messages and recommend what the sales team should do next. Inputs: Messages: [PASTE EMAILS / DMS / REPLIES] Offer: [OFFER] Sales process: [SALES PROCESS] Current pipeline stages: [STAGES] Reply categories used: [CATEGORIES] CRM context: [CRM CONTEXT] Tone standard: [TONE] Response SLA: [SLA] For each message, output: A. Classification Choose one: - positive buying intent - meeting request - objection - pricing question - timing issue - referral - unsubscribe / not interested - wrong contact - support request - procurement/legal - competitor mention - unclear response - spam/noise B. Urgency Score urgency: - immediate - today - this week - nurture - no action C. Required action Provide: - owner - action - deadline - CRM update - follow-up task - escalation if needed D. Draft response Write a response that: - answers the actual message - uses the right tone - includes one clear CTA - avoids overexplaining - avoids pressure E. Automation recommendation Say whether this reply can be: - auto-responded - drafted for human review - routed to rep - routed to manager - routed to support - ignored Rules: - Do not auto-send sensitive or high-value replies. - Do not ignore unsubscribe or opt-out requests. - Do not guess buyer intent when unclear. - Use [HUMAN REVIEW REQUIRED] when the stakes are high. - The system must reduce response time without reducing judgment. --------------------------------------------------------------------------------

#251Account Expansion Signal Monitor

AI SALES AUTOMATION & REVENUE SYSTEMSAccount management, customer success, expansion sales, renewals, SaaS teams, agencies, service providers, and revenue systems for existing customers.

Identify expansion, upsell, cross-sell, and renewal opportunities by analyzing customer usage signals, account changes, support history, relationship health, and business triggers.

You are an AI account expansion analyst. Review this customer account and identify expansion opportunities. Account context: Customer: [CUSTOMER] Current products/services: [CURRENT PRODUCTS] Contract value: [CONTRACT VALUE] Renewal date: [RENEWAL DATE] Usage data: [USAGE DATA] Support tickets: [SUPPORT DATA] Customer success notes: [CS NOTES] Sales notes: [SALES NOTES] Business changes: [BUSINESS CHANGES] Stakeholders: [STAKEHOLDERS] Past objections: [OBJECTIONS] Available expansion offers: [EXPANSION OFFERS] Health score: [HEALTH SCORE] Analyze the account: 1. Expansion signal scan Look for signals such as: - high usage - usage growth - new teams using product - feature adoption - repeated manual work - support requests indicating need - new business unit - hiring growth - new locations - renewal pressure - executive interest - unmet use case 2. Risk signal scan Identify churn or contraction risks: - declining usage - unresolved tickets - poor stakeholder engagement - sponsor change - low adoption - budget pressure - negative feedback - competitor mention 3. Opportunity map For each expansion opportunity provide: - recommended offer - reason - supporting evidence - buyer persona - value angle - timing - confidence - risk - next action 4. Outreach plan Write: - customer success internal note - account manager email - executive check-in - QBR agenda item - renewal conversation angle 5. Decision recommendation Choose: - pursue now - warm up first - wait until renewal - involve customer success - resolve risk before selling - no expansion fit Rules: - Do not push expansion when the customer is unhealthy. - Do not infer usage value without evidence. - Do not create aggressive upsell language. - Expansion should feel like customer success, not pressure. --------------------------------------------------------------------------------

#252AI Discovery Question Generator by Account

AI SALES AUTOMATION & REVENUE SYSTEMSDiscovery calls, demos, executive meetings, account planning, SDR qualification, AE preparation, and personalized sales conversations.

Generate account-specific discovery questions from buyer persona, company context, CRM notes, and sales stage.

Act as a sales discovery strategist. Generate a custom discovery question set for a meeting with [ACCOUNT]. Meeting context: Account: [ACCOUNT] Buyer roles attending: [BUYERS] Offer: [OFFER] Sales stage: [STAGE] Known account context: [ACCOUNT CONTEXT] Known pain or hypothesis: [PAIN] CRM notes: [CRM NOTES] Meeting goal: [GOAL] Call length: [LENGTH] Questions already asked: [PAST QUESTIONS] Topics to avoid: [AVOID] Create a question plan: A. Question priority map Group questions by priority: - must ask - ask if time - ask only if relevant - do not ask yet B. Question types Create questions for: - current workflow - pain symptoms - business impact - urgency - past attempts - decision criteria - stakeholder alignment - budget path - implementation constraints - risk concerns - success metrics - next step C. Account-specific versions Rewrite generic questions so they reference the account context without sounding forced. D. Follow-up probes For each must-ask question provide: - deeper probe - quantification probe - decision process probe - disqualification probe E. Conversation flow Order the questions into a natural call sequence. F. Red flags List answers that would signal: - poor fit - no urgency - hidden stakeholder - weak authority - budget risk - no-decision risk Rules: - Do not ask questions answered in the CRM notes. - Do not overload the buyer with too many questions. - Do not sound like a survey. - Questions should help the buyer think clearly, not just extract information. --------------------------------------------------------------------------------

#253AI Objection Library Maintenance Agent

AI SALES AUTOMATION & REVENUE SYSTEMSSales enablement, sales managers, RevOps, call review, objection handling, playbook updates, and continuous training.

Use real sales conversations to update objection libraries, improve response guidance, identify new objections, and remove outdated talk tracks.

You are an AI sales enablement analyst. Update the objection library using recent sales conversations and deal outcomes. Inputs: Current objection library: [OBJECTION LIBRARY] Recent call summaries: [CALL SUMMARIES] Lost deal notes: [LOST NOTES] Won deal notes: [WON NOTES] Competitor mentions: [COMPETITOR DATA] Pricing feedback: [PRICING FEEDBACK] Manager feedback: [MANAGER FEEDBACK] Rep feedback: [REP FEEDBACK] Offer: [OFFER] ICP: [ICP] Perform the update: 1. Objection discovery Identify: - new objections - objections increasing in frequency - objections decreasing in frequency - objections that changed wording - objections by persona - objections by stage - objections tied to competitors - objections tied to pricing - objections tied to implementation 2. Response performance review For each existing response classify: - keep - improve - remove - replace - needs proof - needs manager review - needs product input - needs legal review 3. Updated objection entry For each important objection create: - buyer wording - what it may mean - diagnosis questions - short response - consultative response - proof to use - follow-up email - next-step recommendation - common mistake 4. Training recommendations Create: - top 5 objections to train this month - role-play scenario for each - call review examples needed - manager coaching question 5. Playbook change log Write what changed and why. Rules: - Do not update based on one isolated conversation unless marked [LOW CONFIDENCE]. - Do not create aggressive rebuttals. - Do not invent proof. - Do not hide objections that indicate real product or fit problems. - The library must become more accurate from field evidence. --------------------------------------------------------------------------------

#254AI Sales Sequence Experiment Designer

AI SALES AUTOMATION & REVENUE SYSTEMSSDR teams, outbound campaigns, cold email testing, LinkedIn outreach, sales development leaders, RevOps, and AI-assisted experimentation.

Design outreach and follow-up experiments with clear hypotheses, message variants, success metrics, sample rules, and learning loops.

Act as a sales experimentation strategist. Design an AI-assisted sales sequence experiment for [CAMPAIGN]. Campaign context: Offer: [OFFER] Target segment: [SEGMENT] Buyer persona: [PERSONA] Channel: [CHANNEL] Current sequence: [CURRENT SEQUENCE] Current performance: [PERFORMANCE] Main hypothesis: [HYPOTHESIS] Known objections: [OBJECTIONS] Proof points: [PROOF] Constraints: [CONSTRAINTS] Desired outcome: [OUTCOME] Build the experiment: A. Experiment hypothesis Write a clear hypothesis: - what we will change - why we believe it matters - what metric should improve - what result would prove or disprove it B. Test design Define: - audience - sample size - test duration - control version - test version - holdout rules - exclusions - stopping criteria C. Message variants Create: - control-friendly rewrite - problem-led variant - trigger-led variant - proof-led variant - referral-style variant - short-form variant D. Metrics Track: - deliverability - open rate if available - reply rate - positive reply rate - meeting booked rate - meeting held rate - opportunity created rate - disqualification rate - unsubscribe rate E. Learning plan Create: - how to analyze results - what to do if test wins - what to do if test loses - what to test next - what not to overinterpret Rules: - Do not optimize only for opens. - Do not test too many variables at once. - Do not declare a winner without enough data. - Do not use AI-generated personalization without QA. - The goal is better revenue conversations, not vanity metrics. --------------------------------------------------------------------------------

#255Revenue Workflow Automation Mapper

AI SALES AUTOMATION & REVENUE SYSTEMSRevOps, sales operations, automation planning, CRM workflows, sales process design, no-code tools, Zapier, Make, n8n, HubSpot, Salesforce, and pipeline systems.

Map a repeatable sales workflow and identify where AI, automation, CRM rules, human review, and quality checks should be used.

You are a revenue workflow automation architect. Map and improve this sales workflow using AI and automation. Workflow to automate: Workflow name: [WORKFLOW] Current trigger: [TRIGGER] Current steps: [CURRENT STEPS] Tools involved: [TOOLS] CRM platform: [CRM] Sales roles involved: [ROLES] Data passed between steps: [DATA] Current problems: [PROBLEMS] Manual tasks: [MANUAL TASKS] Risk areas: [RISKS] Compliance constraints: [CONSTRAINTS] Desired outcome: [OUTCOME] Create the automation map: 1. Current-state workflow Document: - step - owner - tool - input - action - output - delay - error point - manual effort 2. Automation opportunity scan Classify each step as: - automate fully - AI draft with human review - AI classify only - human decision required - remove step - combine steps - keep manual 3. Future-state workflow Design the improved workflow with: - trigger - action - data mapping - AI prompt or logic - human approval point - error handling - fallback path - CRM update - notification - success metric 4. QA and guardrails Define: - what AI must not do - what needs approval - what fields are locked - what errors trigger alerts - what logs must be saved 5. Implementation plan Create: - phase 1 manual-assisted version - phase 2 partial automation - phase 3 scaled automation - testing checklist - rollback plan Rules: - Do not automate a broken process. - Do not remove human review from high-stakes decisions. - Do not create hidden CRM updates. - Do not pass private data into tools that are not approved. - Automation should reduce friction while protecting accuracy. --------------------------------------------------------------------------------

#256Revenue Data QA Bot

AI SALES AUTOMATION & REVENUE SYSTEMSRevOps, sales operations, CRM admins, forecast reporting, leadership dashboards, board reporting, and revenue analytics QA.

Create an AI-assisted quality assurance system that checks sales reports, CRM exports, forecast files, and revenue dashboards for errors, missing data, inconsistencies, and risky assumptions.

Act as a revenue data QA analyst. Review this sales data or report for accuracy risks before it is shared. Data/report: [PASTE DATA OR REPORT] Context: Reporting period: [PERIOD] CRM source: [CRM SOURCE] Report purpose: [PURPOSE] Audience: [AUDIENCE] Definitions used: [DEFINITIONS] Known data limitations: [LIMITATIONS] Required metrics: [METRICS] Business rules: [RULES] Run the QA review: A. Completeness check Flag: - missing fields - missing records - incomplete time periods - blank owners - blank close dates - missing source data - missing stage definitions - missing forecast category logic B. Consistency check Look for: - duplicate records - inconsistent picklists - impossible dates - mismatched totals - conflicting definitions - stage/probability mismatch - close date errors - currency inconsistencies C. Logic check Evaluate: - formula accuracy - forecast assumptions - conversion calculations - pipeline coverage math - weighted pipeline logic - stage aging rules - win rate assumptions D. Risk summary Create: - critical issues - moderate issues - minor issues - questions to ask - confidence level E. Fix instructions For each issue provide: - issue - likely cause - how to verify - recommended fix - owner - urgency Rules: - Do not “clean” data silently. - Do not change formulas without explaining the impact. - Do not hide low confidence. - Use [NEEDS SOURCE CHECK] when raw data is required. - The report should not be shared until critical issues are resolved. --------------------------------------------------------------------------------

#257AI Sales Assistant Role and Prompt System

AI SALES AUTOMATION & REVENUE SYSTEMSTeams building internal AI assistants, custom GPTs, sales copilot workflows, SDR support, AE support, manager support, RevOps support, and repeatable revenue systems.

Define a reusable AI sales assistant with clear responsibilities, allowed actions, forbidden actions, input templates, output formats, and review rules.

You are designing an internal AI sales assistant for [COMPANY]. Create the assistant specification and operating prompt. Company context: Company: [COMPANY] Offer: [OFFER] ICP: [ICP] Sales motion: [SALES MOTION] Sales team roles: [ROLES] CRM: [CRM] Approved tools: [TOOLS] Allowed data sources: [DATA SOURCES] Restricted data: [RESTRICTED DATA] Main use cases: [USE CASES] Quality standards: [STANDARDS] Human review rules: [REVIEW RULES] Create the assistant system: A. Assistant mission Define the assistant’s purpose in one paragraph. B. Allowed use cases Specify how the assistant supports: - prospect research - outreach drafting - CRM note cleanup - call summary - follow-up drafting - objection prep - proposal drafting - pipeline risk review - manager reporting - sales enablement search C. Forbidden actions List what the assistant must never do, including: - invent facts - auto-send messages without approval - update locked CRM fields - use restricted data - make legal claims - promise outcomes - apply pressure tactics - change forecast categories without review D. Master prompt Write the reusable system prompt for the assistant. E. Input templates Create templates for: - prospect research request - outreach request - call summary request - CRM update request - follow-up request - pipeline analysis request F. Output contracts Define required formats for each use case. G. QA framework Create a review checklist before human use. Rules: - Do not make the assistant autonomous beyond approved boundaries. - Do not bury safety rules at the end. - Do not allow unverifiable claims. - The assistant should increase rep speed while preserving human accountability. --------------------------------------------------------------------------------

#258Human-in-the-Loop Sales Automation Guardrails

AI SALES AUTOMATION & REVENUE SYSTEMSSales operations, RevOps, legal-conscious teams, enterprise sales, AI adoption, CRM automation, outbound automation, and leadership governance.

Design approval gates, escalation rules, QA checks, and risk controls for AI-assisted sales automation.

Act as an AI sales governance designer. Build human-in-the-loop guardrails for using AI in sales workflows. Context: Company: [COMPANY] Sales workflows using AI: [WORKFLOWS] Tools used: [TOOLS] CRM: [CRM] Data types used: [DATA] Team roles: [ROLES] Current risk concerns: [RISKS] Legal/compliance constraints: [CONSTRAINTS] Brand voice standards: [VOICE] Approval preferences: [APPROVALS] Build the guardrail system: 1. Risk classification Classify AI tasks into: - low risk - medium risk - high risk - prohibited For each category provide examples. 2. Approval gates Define when human approval is required for: - outbound messages - follow-ups - proposal drafts - pricing language - contract language - CRM updates - forecast changes - lead routing - data enrichment - customer expansion messages 3. QA checklist Create checks for: - factual accuracy - personalization accuracy - tone - compliance - claims - privacy - data source - buyer pressure - hallucination - CRM evidence 4. Escalation paths Define when to involve: - sales manager - RevOps - legal - finance - customer success - executive sponsor 5. Audit log design Specify what must be logged: - AI input - AI output - data source - human reviewer - edits made - approval status - send/update timestamp 6. Team policy Write a plain-English AI sales usage policy reps can follow. Rules: - Do not let AI send high-stakes messages without review. - Do not allow AI to use restricted data. - Do not let AI make pricing, legal, or forecast decisions alone. - Guardrails should enable safe use, not block useful work. --------------------------------------------------------------------------------

#259AI Sales Stack and Tool Governance Plan

AI SALES AUTOMATION & REVENUE SYSTEMSSales leaders, RevOps, founders, IT teams, enablement managers, AI adoption planning, vendor evaluation, and revenue technology strategy.

Choose, organize, and govern AI tools for sales so teams avoid duplicated tools, unsafe workflows, messy data, and unclear ownership.

You are an AI revenue systems advisor. Create an AI sales stack and governance plan for [COMPANY]. Company context: Company: [COMPANY] Sales team size: [TEAM SIZE] Sales motion: [SALES MOTION] CRM: [CRM] Current sales tools: [TOOLS] Current AI tools: [AI TOOLS] Main workflows: [WORKFLOWS] Budget: [BUDGET] Security constraints: [SECURITY] Data privacy constraints: [PRIVACY] Integration requirements: [INTEGRATIONS] Current pain points: [PAIN POINTS] Leadership goals: [GOALS] Build the plan: A. Workflow-to-tool map Map tools to: - prospect research - enrichment - outreach drafting - sequencing - call recording - call summaries - CRM updates - forecasting - reporting - proposal drafting - enablement search - coaching B. Tool evaluation criteria Create a scorecard for: - CRM integration - data security - accuracy - usability - workflow fit - human review controls - reporting - admin governance - cost - scalability - support C. Stack recommendation Recommend: - tools to keep - tools to remove - tools to replace - tools to consolidate - tools to test - workflows to avoid automating D. Ownership model Define: - business owner - technical owner - admin owner - data owner - training owner - approval owner E. Rollout plan Create: - pilot workflow - pilot team - success metrics - QA process - adoption plan - risk review - scale decision Rules: - Do not recommend tools without a workflow reason. - Do not add AI tools that create duplicate data. - Do not ignore security and privacy constraints. - Do not optimize for novelty over revenue impact. - The stack should make sales execution faster, safer, and more measurable. --------------------------------------------------------------------------------

#260Full AI Sales Automation and Revenue Systems Audit

AI SALES AUTOMATION & REVENUE SYSTEMSSales leaders, founders, RevOps teams, sales operations managers, enablement teams, account executives, SDR teams, AI adoption teams, SaaS companies, agencies, consultants, and revenue organizations building AI leverage.

Audit and rebuild the complete AI-enabled sales system across research, personalization, CRM updates, call summaries, lead scoring, follow-up, proposals, reporting, pipeline analysis, governance, and revenue workflows.

Act as an independent AI sales automation and revenue systems auditor. Review my current sales process and design a practical AI-enabled operating system that increases speed, quality, visibility, and revenue execution without removing human judgment. Full context: Company: [COMPANY] Website: [WEBSITE] Offer: [OFFER] Target market: [MARKET] ICP: [ICP] Buyer personas: [PERSONAS] Sales motion: [SALES MOTION] Sales team roles: [ROLES] Team size: [TEAM SIZE] Average deal size: [DEAL SIZE] Sales cycle: [SALES CYCLE] CRM platform: [CRM] Current sales tools: [TOOLS] Current AI tools: [AI TOOLS] Current prospect research process: [RESEARCH PROCESS] Current outreach process: [OUTREACH PROCESS] Current CRM update process: [CRM PROCESS] Current call summary process: [CALL SUMMARY PROCESS] Current follow-up process: [FOLLOW-UP PROCESS] Current proposal process: [PROPOSAL PROCESS] Current lead scoring process: [LEAD SCORING] Current reporting process: [REPORTING] Current pipeline review process: [PIPELINE REVIEW] Current automation workflows: [AUTOMATIONS] Current governance rules: [GOVERNANCE] Data restrictions: [DATA RESTRICTIONS] Main problems: [PROBLEMS] Leadership goals: [GOALS] Audit across 50 dimensions: 1. Prospect research automation 2. Account briefing quality 3. Buyer persona enrichment 4. Outreach personalization 5. Cold email drafting 6. LinkedIn message drafting 7. Follow-up generation 8. Follow-up QA 9. Call summary accuracy 10. CRM note generation 11. CRM field update safety 12. Lead scoring 13. Lead routing 14. Reply triage 15. Meeting prep briefs 16. Discovery question generation 17. Objection prep 18. Competitive intelligence support 19. Proposal drafting 20. Proposal QA 21. Pricing language review 22. Buyer enablement asset drafting 23. Pipeline risk detection 24. Deal health scoring 25. Forecast reporting 26. Manager revenue briefs 27. Rep performance insights 28. Sales activity reporting 29. Account expansion signals 30. Renewal risk signals 31. Win/loss insight extraction 32. Enablement content updates 33. Sales sequence experimentation 34. Workflow automation design 35. No-code automation readiness 36. Data quality checks 37. Dashboard QA 38. AI assistant role clarity 39. Human approval gates 40. Restricted data handling 41. Hallucination controls 42. Audit logs 43. Tool ownership 44. AI stack overlap 45. CRM integration quality 46. Rep adoption 47. Manager adoption 48. Training requirements 49. Revenue impact measurement 50. Overall AI sales system maturity For each dimension provide: - score from 1 to 10 - diagnosis - evidence from my context - revenue impact - speed impact - quality risk - automation opportunity - human review requirement - recommended fix - priority - effort - confidence level Then synthesize: A. Hard truth Explain the biggest reason AI is not yet improving sales execution, pipeline quality, or revenue visibility. B. AI workflow map Create a practical map for: - prospect research - outreach drafting - reply triage - call summaries - CRM updates - follow-up generation - proposal drafting - pipeline analysis - reporting - expansion monitoring For each workflow include: - trigger - input - AI task - human review point - output - CRM update - quality check - success metric C. Human-in-the-loop governance Create: - low-risk AI tasks - medium-risk AI tasks - high-risk AI tasks - prohibited tasks - approval gates - audit log requirements - escalation rules D. AI sales assistant system Design: - assistant mission - allowed use cases - forbidden actions - master prompt - input templates - output formats - QA checklist E. AI sales automation roadmap Create: - first 24-hour quick win - first 7-day pilot - first 14-day workflow rollout - first 30-day revenue system upgrade - first 60-day stack optimization - first 90-day governance and scaling plan F. Metrics Define how to measure: - time saved - follow-up speed - CRM completeness - message quality - meeting conversion - pipeline risk detection - forecast accuracy - proposal turnaround - rep adoption - manager adoption - revenue impact G. Executive summary Write a direct summary with: - fastest AI sales win - highest-risk automation - first workflow to automate - first workflow not to automate - first CRM field to protect - first QA gate to install - first dashboard to build - first training session to run - one operating principle for AI-assisted sales Rules: - Do not recommend automation before fixing process clarity. - Do not let AI auto-send high-stakes buyer messages. - Do not let AI update critical CRM fields without evidence. - Do not use restricted or sensitive data. - Do not invent facts, proof, pricing, guarantees, case studies, or buyer intent. - Use [NEEDS DATA], [NEEDS HUMAN REVIEW], [NEEDS CRM REVIEW], [NEEDS LEGAL REVIEW], [NEEDS REVOPS REVIEW], or [NEEDS MANAGER REVIEW] where required. - The final system should improve speed, quality, pipeline visibility, forecast trust, and human decision-making.

Unlock all 260 prompts