The GTM Executive’s Guide to Deep Research: How to Turn AI Into Your Most Valuable Sales Weapon

<goal>

Create a comprehensive pre-call briefing document for an upcoming discovery call. I need to understand this prospect and company deeply enough to have a strategic conversation, not just a product pitch.

</goal>

<context>

I'm an AE at [Your Company]. We provide [brief product/service description] to [target customer type]. 

My upcoming call:

- Prospect: [Name], [Title] at [Company]

- Call type: [Discovery / Demo / Negotiation]

- Deal size potential: [Estimated ACV]

- How they found us: [Inbound source / Outbound / Referral]

What I already know: [Any existing intel from LinkedIn, previous conversations, CRM notes]

Our main competitors they might be evaluating: [List if known]

</context>

<content>

Research and include the following:Company Overview- Business model and revenue streams

- Company stage, size, and recent funding/financial health

- Key products/services and target customers

- Tech stack (especially relevant integrations)Strategic Context- Recent company news (funding, acquisitions, leadership changes, product launches)

- Stated strategic priorities from earnings calls, press releases, or executive interviews

- Job postings that reveal internal initiatives or pain points

- Industry headwinds or tailwinds affecting themProspect Profile- Career trajectory and time in current role

- Likely priorities based on their function and company stage

- Content they've published or engaged with

- Mutual connections or shared experiencesPain Point Hypothesis- 3-5 likely challenges based on their role, industry, and company stage

- Evidence supporting each hypothesis

- How our solution specifically addresses eachCompetitive Intelligence- Solutions they're likely already using

- Competitors they might be evaluating

- Our differentiation angles for this specific accountConversation Starters- 3 personalized opening angles based on recent news or initiatives

- 5 discovery questions tailored to their likely situation

- Potential landmines or sensitive topics to avoidDeal Intelligence- Likely buying committee members and their priorities

- Potential champions vs. blockers

- Estimated timeline drivers (contract renewals, budget cycles, initiatives)

</content>

<style>

Format as a 2-page briefing I can review in 10 minutes before the call. Use bullet points for scannability. Lead with the most important insights. Include a "30-second summary" at the top with the 3 most critical things I need to know.

</style>

<sources>

Prioritize: company website, recent press releases, earnings calls/investor presentations, LinkedIn profiles, industry news, Glassdoor/employee reviews for cultural context, job postings, G2/Capterra reviews (if they're a software company). Cite all sources so I can dig deeper on key points.

</sources>

<instructions>

Before starting your research, share your research plan for my review. Focus on actionable insights over general background. Flag any conflicting information you find. If you can't find information on a specific area, note that explicitly rather than guessing.

</instructions>

<goal>

Validate and refine our Ideal Customer Profile (ICP) based on current market conditions. We need to determine if our targeting is still optimal or if we should adjust our focus to improve conversion rates and deal velocity.

</goal>

<context>

Company: [Your company name]

Product: [What you sell and core value proposition]

Current ACV: [Average contract value]

Sales cycle: [Typical length]

Current win rate: [If known]

Current ICP Definition:

- Industry: [Current industry focus]

- Company size: [Employee count / revenue range]

- Geography: [Target regions]

- Buyer persona: [Primary buyer title/function]

- Key characteristics: [Other defining traits]

Our best customers (reference accounts):[Company A] - [Why they're great: usage, expansion, NPS, etc.][Company B] - [Why they're great][Company C] - [Why they're great]Customers that churned or struggled:[Company X] - [What went wrong][Company Y] - [What went wrong]Primary competitors: [List main competitors]

Hypothesis we want to test: [Any specific assumptions you want validated]

</context>

<content>

Analyze and deliver:ICP Validation Assessment- Evidence supporting our current ICP definition

- Evidence challenging our current ICP definition

- Market segments we may be overlooking

- Segments we're targeting that may not be idealMarket Dynamics Analysis- How has our target market evolved in the past 12-18 months?

- Funding and investment trends in our target segments

- Emerging buyer needs or pain points

- Technology adoption patterns affecting our value propositionCompetitive Positioning Shifts- How are competitors defining their ICP?

- Segments competitors are winning vs. losing

- White space opportunities they're missing

- Positioning changes that affect our differentiationRefined ICP Recommendation- Primary ICP (highest probability of success)

- Secondary ICP (expansion opportunity)

- Exclusion criteria (who we should NOT target)

For each ICP tier, specify:

- Firmographic criteria (industry, size, geography, growth stage)

- Technographic indicators (tech stack signals)

- Behavioral triggers (events indicating buying intent)

- Negative indicators (red flags to disqualify)

- Estimated market size (number of companies)Buying Committee Map- Primary buyer persona (the champion)

- Economic buyer (budget holder)

- Technical evaluator (if applicable)

- Key priorities and objections for eachQualification Framework- BANT/MEDDIC criteria specific to our new ICP

- 5-7 qualification questions for SDRs

- Scoring rubric with point valuesMessaging Implications- How positioning should shift based on ICP refinement

- Key messages by persona

- Proof points that resonate with refined ICP

</content>

<style>

Structure using the Pyramid Principle—lead with your recommendation, then supporting analysis. Use comparison tables where helpful (current vs. proposed ICP). Include a confidence level (high/medium/low) for each recommendation with rationale.

</style>

<sources>

Prioritize: industry analyst reports, funding databases (Crunchbase, PitchBook mentions), competitive intelligence, G2/Capterra market data, job posting trends, industry publications, customer review sites. Avoid vendor marketing content. Cite all sources with dates.

</sources>

<instructions>

Share your research plan before executing. Challenge our assumptions—we want honest assessment, not validation of what we already believe. Where data is limited, clearly state that you're making inferences and explain your reasoning.

</instructions>

<goal>

Create a comprehensive competitive battlecard that sales reps can use during live deals. This needs to be honest, specific, and immediately actionable—not marketing fluff.

</goal>

<context>

Our Company: [Your company name]

Our Product: [Brief description]

Our Positioning: [How we describe ourselves]

Our Pricing: [Pricing model and approximate ranges]

Our Strengths: [What we believe we do best]

Our Weaknesses: [Honest assessment of gaps]

Competitor to Analyze: [Competitor name]

Competitor Website: [URL]

Recent competitive deals:

- Deal we won against them: [Brief description of why]

- Deal we lost to them: [Brief description of why]

What we currently believe about them: [Existing assumptions to validate/challenge]

</context>

<content>

Build a battlecard with these sections:Competitor Snapshot (1 paragraph)- Who they are, core product, primary market

- Funding/company stage/trajectory

- Recent momentum (growing, stable, struggling?)Head-to-Head Comparison Matrix| Capability | Us | Them | Winner | Notes |

Cover: Core features, pricing, implementation, support, integrations, security/compliance, reporting, scalabilityPositioning Analysis- How they describe themselves (exact messaging from website)

- Their stated differentiators

- Target customer according to their marketing

- Key proof points they emphasizePricing Intelligence- Pricing model and structure

- Published pricing (if available)

- Pricing gathered from reviews/discussions

- Common discounting patterns

- Total cost of ownership considerationsTheir Ideal Customer vs. Ours- Where they win (be honest)

- Where we win

- True toss-up scenarios

- Signals that indicate they're the better fitStrengths to Acknowledge- What they genuinely do well

- Why certain customers choose them

- Credibility points we can't dismissWeaknesses to Exploit- Common complaints from G2/Capterra reviews (with quotes)

- Known product gaps or limitations

- Implementation/support issues

- Customer churn indicatorsObjection HandlingFor each common objection when competing against them:

- The objection

- Why prospects raise it

- Response framework

- Proof point to referenceTrap-Setting Discovery Questions- Questions that expose their weaknesses

- Questions that highlight our strengths

- Questions to understand if prospect is a better fit for themLandmines to Avoid- Topics where they have advantage

- Claims we shouldn't make

- Comparisons that backfireRecent Intelligence- Product launches (last 6 months)

- Pricing changes

- Leadership changes

- Funding/acquisition news

- Strategic pivotsQuick Reference Talk Tracks- 30-second positioning against them

- Response to "why shouldn't we just go with [Competitor]?"

- Response to "they're cheaper"

- Response to "[Competitor] has feature X"

</content>

<style>

Format for quick scanning during live calls. Use tables for comparisons. Bold key phrases reps should say verbatim. Keep talk tracks conversational, not scripted. Include a 1-page "cheat sheet" summary at the beginning.

</style>

<sources>

Research: competitor website (especially pricing, case studies, integrations pages), G2 and Capterra reviews (last 12 months), Reddit and community discussions, LinkedIn posts from their employees, Glassdoor reviews, press releases, funding announcements, job postings (reveal strategic priorities), YouTube demos, podcast appearances by their leadership. Always cite sources.

</sources>

<instructions>

Be brutally honest. A battlecard that pretends we're better at everything is useless. Clearly distinguish between verified facts and inferences. For each claim, indicate confidence level. Flag anything that needs human verification before using in deals.

</instructions>

<goal>

Conduct a comprehensive market expansion analysis to determine whether [target vertical/segment] represents a viable growth opportunity. This analysis will inform a go/no-go investment decision and, if positive, the initial GTM approach.

</goal>

<context>

Our Company: [Company name]

Current Business:

- Product: [What you sell]

- Current verticals: [Where you sell today]

- Current ACV: [Average deal size]

- Current sales cycle: [Length]

- Current win rate: [If known]

- ARR/Revenue: [Current scale]

- Team size: [Sales, marketing, CS headcount]

Expansion Target: [Vertical/segment being evaluated]

Why we're considering this market:

- [Hypothesis 1: e.g., "Customers in this vertical have asked for our product"]

- [Hypothesis 2: e.g., "Our technology applies to their use case"]

- [Hypothesis 3: e.g., "Competitors are succeeding here"]

Resources available for expansion: [Budget, headcount, timeline constraints]

What would make this a "go" decision: [Minimum TAM, win rate expectations, timeline to payback]

</context>

<content>

Deliver a comprehensive expansion analysis:Executive Summary- Go / No-Go / Conditional recommendation

- 3 key findings supporting the recommendation

- Critical risks and mitigation strategies

- Estimated investment required vs. potential returnMarket Size Analysis- TAM: Total companies fitting broad criteria

- SAM: Companies we could realistically reach

- SOM: Realistic 3-year capture estimate

- Methodology and assumptions (be explicit)

- Data sources and confidence levelMarket Dynamics- Growth rate and trajectory

- Key trends shaping the market

- Regulatory or compliance considerations

- Technology adoption maturity

- Consolidation/fragmentation trendsCompetitive Landscape- Established players in this vertical

- Their positioning and market share

- Recent entrants and their traction

- White space and underserved segments

- Barriers to entry for new players

- Our potential differentiationBuyer AnalysisPrimary Buyer Persona:

- Title and function

- Key responsibilities and KPIs

- Pain points our product addresses

- Current solutions they use

- Buying process and committee

- Budget cycles and authority levels

Secondary Personas:

- [Repeat structure for each]Value Proposition Translation- How our current value prop applies (or doesn't)

- Messaging adjustments needed

- New proof points required

- Features gaps we'd need to address

- Partnerships that could accelerate entryGo-to-Market Feasibility- Channel strategy (direct, partner, PLG)

- Marketing channels that reach this audience

- Sales motion alignment (current vs. required)

- Content and thought leadership requirements

- Events and community presence neededFinancial Model Inputs- Expected ACV in this segment

- Estimated sales cycle length

- Win rate assumptions (with rationale)

- CAC expectations

- Churn/expansion assumptionsCompetitive Response Risk- How will incumbents respond?

- Switching costs for prospects

- Lock-in mechanisms we'd faceImplementation Roadmap (if Go)- Phase 1 (0-6 months): [Specific actions]

- Phase 2 (6-12 months): [Specific actions]

- Phase 3 (12-18 months): [Specific actions]

- Key milestones and decision points

- Resource requirements by phaseRisk Assessment| Risk | Likelihood | Impact | Mitigation |

[Table format for key risks]Appendix- List of target accounts in this vertical

- Competitive feature matrix

- Source documentation with links

</content>

<style>

Use the Pyramid Principle—lead with recommendation. Include executive summary that stands alone. Use tables for comparisons and data. Visualize the TAM/SAM/SOM if possible. Clearly distinguish facts from estimates.

</style>

<sources>

Prioritize: industry analyst reports, government/census data, trade association data, industry publications, competitor investor materials, job posting trends, industry event agendas, customer review platforms, funding databases. For TAM, use multiple methodologies and triangulate. Cite all sources with dates.

</sources>

<instructions>

Before researching, share your methodology for TAM calculation. Be skeptical—we want realistic assessment, not optimistic projections. Where data is uncertain, provide ranges rather than point estimates. Clearly label assumptions that need validation.

</instructions>

<goal>

Develop a comprehensive persona research document that will inform highly personalized outbound email sequences. I need to understand this persona deeply enough to write messages that feel custom-written for each recipient.

</goal>

<context>

Our Company: [Your company]

Our Product: [What you sell]

Our Value Proposition: [Primary benefit]

Target Company Type: [Industry, size, stage]

Persona to Research:

- Title: [e.g., "VP of Operations"]

- Function: [e.g., "Operations / Supply Chain"]

- Company Stage: [e.g., "Series B-D, 100-500 employees"]

- Industry: [e.g., "Freight & Logistics"]

Our current assumptions about this persona:

- Pain points we think they have: [List]

- Value props we lead with: [List]

- Objections we typically hear: [List]

Current outbound performance:

- Open rate: [X%]

- Reply rate: [X%]

- Positive reply rate: [X%]

What's not working: [Any specific feedback or patterns]

</context>

<content>

Research and deliver:Day-in-the-Life Analysis- Typical daily/weekly responsibilities

- Meetings they attend and run

- Reports they create and consume

- Systems they interact with

- People they collaborate with

- Decisions they make and influenceGoals and KPIs- What they're measured on

- What their boss cares about

- Career trajectory aspirations

- How they define success in their role

- Timeframes they think in (quarterly, annual)Pain Points (Validated)- Primary frustrations (with evidence from interviews, posts, forums)

- Specific quotes from people in this role

- Problems they've publicly discussed

- Challenges unique to their industry/stage

- Rank by severity and frequencyCurrent Solutions Landscape- Tools they typically use

- Manual processes they rely on

- Workarounds they've built

- Budget they control

- Vendors they currently work withInformation Diet- Publications and newsletters they read

- Podcasts they listen to

- Communities they participate in

- Events they attend

- Influencers they follow

- LinkedIn content they engage withLanguage and Terminology- Industry jargon they use

- Terms they avoid or find off-putting

- Acronyms common in their world

- How they describe their challenges (verbatim quotes)

- Words that signal "vendor marketing" (to avoid)Buying Behavior- How they evaluate new solutions

- Who else is involved in decisions

- What triggers them to look for new tools

- Preferred first touch (email, LinkedIn, phone, referral)

- Length of consideration process

- Deal breakers and must-havesObjection Mapping| Likely Objection | Root Cause | Response Framework |Trigger Events- Company events that create urgency

- Personal events that create openness

- Industry events that drive action

- Signals we can monitor for timingMessaging FrameworkFor each of 3 email angles, provide:

- Subject line options (3-5 each)

- Opening hook (addressing specific pain)

- Value proposition (in their language)

- Proof point (relevant case study type)

- CTA (appropriate ask for cold outreach)Personalization Variables- Company-specific elements to research

- Role-specific elements to incorporate

- Timing-specific elements to reference

- Template for rapid personalizationWhat NOT to Say- Messages that will get ignored

- Claims that lack credibility

- Approaches that feel too salesy

- Competitive comparisons to avoid

</content>

<style>

Make this immediately actionable for SDRs. Include actual email copy they can adapt, not just frameworks. Use real quotes from people in this persona where possible. Organize for easy reference when writing sequences.

</style>

<sources>

Research: LinkedIn posts and comments from people in this role, Reddit discussions (industry-specific subreddits), industry forums and Slack communities, podcast interviews with this persona, conference talk recordings, industry surveys and research reports, job postings (reveal priorities), Glassdoor reviews from this function. Cite sources for all claims.

</sources>

<instructions>

Focus on direct quotes and first-person perspectives wherever possible. I want to hear how this persona actually talks, not how vendors think they talk. Flag where you're inferring vs. citing. If certain information isn't findable, tell me what validation interviews I should conduct.

</instructions>

<goal>

Design a revenue attribution model appropriate for our GTM motion and tech stack. I need a practical implementation plan, not theoretical frameworks.

</goal>

<context>

Company Profile:

- Stage: [Seed / Series A / Series B / etc.]

- ARR: [Current revenue]

- GTM Motion: [PLG / Sales-Led / Hybrid - describe]

- Sales Cycle: [Average length]

- ACV: [Average deal size]

- Team Size: [Marketing, SDR, AE, CS headcount]

Current Tech Stack:

- CRM: [e.g., Salesforce, HubSpot]

- Marketing Automation: [e.g., Marketo, HubSpot, Pardot]

- Website Analytics: [e.g., GA4, Amplitude]

- Product Analytics: [e.g., Mixpanel, Amplitude, Heap]

- Data Warehouse: [e.g., Snowflake, BigQuery, none]

- BI Tool: [e.g., Looker, Tableau, none]

- Other relevant tools: [List]

Current State of Attribution:

- What we track now: [Describe current approach]

- What's broken: [Specific problems]

- Questions we can't answer: [List]

Marketing Channels We Use:

- [List all channels: paid search, LinkedIn ads, content, events, etc.]

Sales Motions:

- [Describe: inbound, outbound, partner, PLG conversion, etc.]

Resources for Implementation:

- RevOps capacity: [Who would implement]

- Budget for tools: [If any]

- Timeline expectations: [When we need this working]

</context>

<content>

Deliver a complete attribution design:Attribution Model Recommendation- Recommended model type (first-touch, last-touch, linear, W-shaped, custom)

- Why this model fits our motion

- Trade-offs vs. alternatives

- How this model handles our specific channels and motionsAttribution Taxonomy- Channel definitions (exactly what counts as what)

- Source/medium naming conventions

- Campaign hierarchy structure

- UTM parameter standards

- Lead source categorization

- Touch type definitionsData Architecture- Required data sources and integrations

- Data model design (objects, fields, relationships)

- Identity resolution approach (how we tie touches to accounts/opportunities)

- Data quality requirements

- Historical data handlingTechnical ImplementationFor each tool in our stack:

- Configuration requirements

- Fields to create

- Automation/workflows needed

- Integration points

If data warehouse exists:

- Table structure

- Transformation logic

- Key joinsReporting FrameworkWhat reports to build:

| Report | Audience | Frequency | Key Metrics |

Dashboard mockups:

- Executive dashboard (what metrics, what views)

- Marketing dashboard

- Sales dashboardKey Metrics DefinitionsFor each metric, provide:

- Precise definition

- Calculation formula

- Data sources

- Caveats/limitationsEdge Cases and Exceptions- How we handle offline touches

- How we handle dark social

- How we handle multi-product

- How we handle partner-sourced

- How we handle expansion revenue

- What we're knowingly NOT trackingGovernance Model- Who owns what data

- Data quality monitoring

- Regular review cadence

- Model refinement triggersImplementation RoadmapPhase 1 (Days 1-30):

- [Specific tasks with owner and effort estimate]

Phase 2 (Days 30-60):

- [Specific tasks]

Phase 3 (Days 60-90):

- [Specific tasks]Change Management- How to communicate to teams

- Training requirements

- Transition from old to new

- Expected timeline to reliable dataKnown Limitations- What this model won't tell us

- Complementary analyses to run

- When to revisit the modelAppendix: Examples from Similar Companies- How comparable companies approach attribution

- Lessons learned from their implementations

</content>

<style>

Be extremely specific and technical. Include actual field names, formulas, and configuration steps. I need to be able to hand this to RevOps and have them implement it. Use diagrams/flowcharts where helpful.

</style>

<sources>

Research: attribution best practices from RevOps communities, technical documentation for our tools, case studies from similar-stage B2B companies, industry benchmarks for attribution, common mistakes and anti-patterns. Prioritize practitioner perspectives over vendor marketing.

</sources>

<instructions>

Before starting, confirm you understand our tech stack and can provide specific technical guidance for it. If you need clarification on any tool or integration, ask first. Focus on practical implementation over theoretical purity.

</instructions>

<goal>

Build a comprehensive sales compensation benchmark to ensure our hiring offers and existing comp plans are market-competitive. This will inform both immediate hiring decisions and annual comp planning.

</goal>

<context>

Our Company:

- Stage: [Series A / B / C / Public]

- Industry: [Your industry]

- Location: [HQ and where roles are based]

- ARR: [Current revenue]

- ACV: [Average deal size]

- Sales Cycle: [Average length]

- Current team size: [Number of AEs, SDRs, etc.]

- Funding status: [Recent raise? Runway?]

Role(s) to Benchmark:[Role title, e.g., "Account Executive - Mid-Market"]- Quota expectation: [Target]

- Deal complexity: [Simple / Complex / Enterprise]

- Inbound vs. outbound: [Mix %]

- Territory: [Geographic or vertical focus][Additional roles if needed]Current Comp Structure:

- Base: [Range]

- OTE: [Range]

- Split: [e.g., 50/50, 60/40]

- Commission structure: [Brief description]

- Equity: [Range in basis points or shares]

- Other: [Benefits, accelerators, etc.]

Hiring Context:

- Competing with companies like: [List competitor employers]

- Candidate profiles we target: [Years experience, background]

- Hiring challenges we've faced: [Losing on comp? Quality issues?]

</context>

<content>

Deliver comprehensive compensation benchmarks:Executive Summary- Are we paying competitively? (Under / At / Above market)

- Key adjustments recommended

- Risk of current approach (attrition, hiring difficulty)Base Salary Benchmarks| Segment | 25th Percentile | 50th | 75th | 90th |

Segmented by:

- Company stage

- Geography

- Industry

- Role levelOTE Benchmarks[Same table structure]

Include:

- OTE ranges by attainment level

- Typical OTE:Base ratios

- How OTE varies by deal size and complexityCommission Structure Patterns- Common structures for our deal profile

- Accelerator designs

- Decelerator/clawback patterns

- SPIFs and bonuses

- Multi-year deal handling

- Expansion/renewal creditEquity Compensation- Expected equity by stage and role level

- Vesting schedules

- Refresh grant patterns

- How to present equity value to candidatesBenefits and Perks- Standard benefits expectations

- Differentiated perks that matter

- What candidates ask about mostRamp and Quota- Standard ramp periods

- Ramp quotas and ramp commission

- Quota-setting methodologies

- Realistic attainment expectationsTotal Compensation ComparisonModel scenarios:

- At 100% attainment

- At 120% attainment (top performer)

- At 80% attainment (ramp or tough quarter)

Compare us vs. [Competitor employers]Market Trends- How has sales comp evolved in past 12-24 months?

- What's changing going forward?

- Hot roles commanding premiums

- Roles seeing compressionRecommendations| Element | Current | Recommended | Rationale |

Prioritized by impact on hiring and retentionImplementation Considerations- Budget impact of changes

- How to adjust existing team

- Communication approach

- TimelineAppendix: Data Sources- Source, date, sample size, methodology

- Confidence level for each benchmark

- Where data conflicts and our interpretation

</content>

<style>

Heavy use of tables for easy comparison. Include ranges, not just averages. Clearly distinguish between hard data and estimates. Make recommendations specific and actionable.

</style>

<sources>

Research: compensation surveys (Pave, Carta, Radford if accessible), job postings with comp listed (Levels.fyi, Glassdoor, LinkedIn), recruiting community discussions, comp consultancy blogs and reports, startup compensation databases, industry-specific surveys, Reddit r/sales and r/salesforce discussions. Note sample sizes and dates for all data.

</sources>

<instructions>

Focus on data from the past 12 months—compensation changes rapidly. Triangulate across sources and flag where sources conflict. If data for our exact profile is sparse, note that and explain your extrapolation logic.

</instructions>

<goal>

Design a customer health scoring system and churn prevention framework specific to our product and customer base. I need both the strategic framework and tactical implementation guidance.

</goal>

<context>

Our Business:

- Product: [What you sell]

- Business Model: [Subscription, usage-based, hybrid]

- Customer Segment: [SMB / Mid-Market / Enterprise]

- ACV: [Average contract value]

- Contract Terms: [Monthly / Annual / Multi-year]

- Current Churn Rate: [Monthly or annual]

- Logo vs. Revenue Churn: [If different]

- NDR: [Net dollar retention]

Customer Profile:

- Typical customer size: [Employee count / revenue]

- Primary user persona: [Who uses the product]

- Buyer persona: [Who pays/decides on renewal]

- Implementation complexity: [How hard to get live]

- Time to value: [How long to see results]

Current CS Structure:

- CS team size: [Headcount]

- CS:Customer ratio: [e.g., 1:50]

- Current engagement model: [High-touch / Low-touch / Hybrid]

- Tools used: [Gainsight, ChurnZero, etc.]

Known Churn Factors:

- Why we think customers leave: [List hypotheses]

- Customers who churned recently: [Brief description of patterns]

- What we tried that didn't work: [List]

</context>

<content>

Deliver a complete churn prevention framework:Churn Pattern Analysis- Common churn reasons in our industry/segment

- Typical churn timing patterns (when in lifecycle)

- Leading indicators research from similar companies

- Comparison of our stated churn rate to benchmarksHealth Score DesignComponent scores (for each, define):

- What we're measuring

- Data source

- Calculation method

- Weight in overall score

- Thresholds (Red / Yellow / Green)

Recommended components:

- Product usage/engagement

- Adoption depth (features used)

- Relationship strength (contacts, engagement)

- Support experience (tickets, sentiment)

- Business outcomes (are they seeing ROI)

- Expansion signals

- Contract/commercial factors

- Risk signals (champion left, budget cut)Scoring Model- How to combine components into overall health

- How to handle missing data

- How to weight recency

- Segmentation adjustments (SMB vs. Enterprise)

- Confidence intervalsLeading Indicators Matrix| Indicator | Data Source | Warning Threshold | Typical Lead Time | Accuracy |

Prioritized by predictive powerIntervention PlaybooksFor each risk level (Red / Yellow / Early Warning):

- Trigger criteria

- Owner (CSM, Manager, Executive)

- Response timeline

- Intervention options

- Talk track/messaging

- Escalation path

- Documentation requirementsProactive Engagement Calendar- Milestone-based touches (onboarding, QBRs, renewal)

- Usage-triggered touches

- Relationship-building touches

- Executive engagement triggersSave StrategiesWhen customer indicates intent to churn:

- Discovery framework (understand real reason)

- Common root causes and responses

- Concession framework (what we can offer)

- Walk-away criteria (when to let them go)

- Off-boarding for future win-backExpansion Integration- How health score informs expansion timing

- Signals that indicate expansion readiness

- Handoff to expansion/salesImplementation RoadmapPhase 1: Foundation (Month 1)

- Data requirements

- Tool configuration

- Initial scoring model

Phase 2: Calibration (Months 2-3)

- Backtesting against historical churn

- Adjustments based on results

- Team training

Phase 3: Automation (Months 3-4)

- Automated alerts

- Playbook integration

- Reporting/dashboardsGovernance- Score review cadence

- Model refinement triggers

- Edge case handling

- Appeals processMetrics and Reporting| Metric | Definition | Target | Current |

Dashboard requirements for:

- CS leadership

- CSM daily management

- Executive reportingAppendix: Benchmark Data- Retention benchmarks for our segment

- Health score approaches from similar companies

- Industry research on churn causes

</content>

<style>

Balance strategic framework with tactical specifics. Include enough detail that this could be implemented in 30 days. Use tables for scoring models. Be prescriptive with recommendations.

</style>

<sources>

Research: CS and retention best practices (Gainsight community, CSM Practice, Totango resources), benchmark reports (Gainsight Pulse data, ChartMogul benchmarks), practitioner case studies, industry-specific retention research, SaaS finance resources (David Skok, Tomasz Tunguz). Cite sources.

</sources>

<instructions>

Before starting, confirm you understand our customer profile and engagement model. Focus on practical metrics we can actually track, not theoretical ideals. Where you're uncertain about our specific context, offer options rather than single recommendations.

</instructions>

<goal>

Audit our GTM tech stack and provide optimization recommendations. I need to understand where we have gaps, redundancies, and integration issues—plus a prioritized roadmap for improvements.

</goal>

<context>

Company Profile:

- Stage: [Seed / Series A / B / C]

- ARR: [Revenue]

- Team Size: [Sales, Marketing, CS, RevOps headcount]

- GTM Motion: [PLG / Sales-Led / Hybrid]

- Annual Tech Budget: [Approximate spend on tools]

Current Tech Stack (with approximate costs):

CRM & Sales:

- [Tool 1]: [Annual cost] - [Primary use]

- [Tool 2]: [Annual cost] - [Primary use]

[List all tools]

Marketing:

- [Tool 1]: [Annual cost] - [Primary use]

[List all tools]

Customer Success:

- [Tool 1]: [Annual cost] - [Primary use]

[List all tools]

RevOps & Data:

- [Tool 1]: [Annual cost] - [Primary use]

[List all tools]

Known Issues:

- Integrations that are broken/clunky: [List]

- Manual processes that should be automated: [List]

- Data quality issues: [List]

- Tools we're not using fully: [List]

- Gaps we're aware of: [List]

Constraints:

- Budget for changes: [Available budget]

- RevOps capacity: [Who would implement]

- Contract renewal dates: [Any tools up for renewal soon]

- Non-negotiables: [Tools that must stay]

</context>

<content>

Deliver a comprehensive tech stack audit:Executive Summary- Overall assessment (Optimized / Needs Work / Major Issues)

- Top 3 urgent changes

- Estimated annual savings opportunity

- Critical gaps to addressStack Assessment by CategoryFor each category (CRM, Marketing, CS, Data):

- Current tools and their health (Well-Used / Underused / Overpriced / Wrong Fit)

- Redundancies (overlapping capabilities)

- Gaps (missing capabilities)

- Integration quality

- Recommendation: Keep / Consolidate / Replace / AddIntegration Architecture- Map of how data flows between tools

- Integration gaps causing issues

- Data quality problems from integrations

- Recommended integration improvementsTool-by-Tool AnalysisFor each tool:

| Aspect | Assessment |

- Primary use case

- % of capabilities used

- Cost vs. value

- Alternatives to consider

- RecommendationGap Analysis| Capability | Current State | Gap Impact | Recommended Solution |

Priority capabilities missing:

- [Capability 1]

- [Capability 2]Consolidation Opportunities- Tools with overlapping features

- Potential consolidation paths

- Savings estimate

- Migration complexityBest-in-Class BenchmarkWhat does a comparable company's stack look like?

- Reference stack for our stage/motion

- How we compare

- Capabilities they have that we don'tVendor AlternativesFor tools flagged as Replace:

| Category | Current | Alternatives | Key Differences | Est. Cost |

Include pricing insights and negotiation leverageImplementation RoadmapImmediate (30 days):

- [Change 1]: Effort, owner, expected impact

- [Change 2]

Near-term (90 days):

- [Changes]

Medium-term (6 months):

- [Changes]Budget Impact AnalysisCurrent annual spend: $X

Proposed Changes:

| Change | Current Cost | New Cost | Savings | Investment |

Net impact: [Savings or investment required]Change Management- Stakeholders affected by each change

- Training requirements

- Risk mitigation

- Rollback plansFuture State Architecture- Recommended stack for 12 months out

- Integration diagram

- Key automation flows

- Data flow architecture

</content>

<style>

Be opinionated—don't just describe, recommend. Include specific product suggestions where appropriate. Use cost estimates where possible. Create clear before/after visualization.

</style>

<sources>

Research: G2 Grid rankings for each category, pricing databases (Vendr, Spendflo), tech stack case studies from similar companies, integration marketplace reviews, RevOps community discussions, vendor comparison content from neutral sources. Avoid vendor-produced "vs" content.

</sources>

<instructions>

Before researching, confirm you have our full tool list. For each tool, check actual capabilities against what we said we use it for. Be direct about tools we're overpaying for or shouldn't have.

</instructions>

<goal>

Build the market context section of our board deck. This should provide the competitive and market backdrop that helps the board evaluate our performance and strategy.

</goal>

<context>

Company Profile:

- What we do: [Brief description]

- Stage: [Seed / Series A / B / C]

- ARR: [Current revenue]

- Growth rate: [YoY or QoQ]

- Primary market: [Industry/vertical]

- Key competitors: [Top 3-5]

Board Composition:

- [List investor firms and any independent directors]

- What they typically ask about: [Common questions/areas of focus]

Recent Company Developments:

- [Significant launches, wins, changes since last board meeting]

Strategic Questions on the Table:

- [Any specific strategic decisions being discussed]

- [Market questions the board has asked]

Last Board Meeting Date: [When]

Time Period to Cover: [e.g., "Q4 2024" or "Since our last meeting on X date"]

</context>

<content>

Prepare board-ready market context:Executive Summary (1 slide worth of content)- 3-5 bullet market headlines

- Net assessment: Is the market backdrop favorable, neutral, or challenging?

- Key strategic implicationsMarket Size and Growth- Current TAM/SAM estimate (with methodology)

- Growth rate and trajectory

- How this compares to last quarter's view

- Forward-looking projectionsCompetitive Landscape UpdateFor each major competitor:

- Recent developments (funding, product, leadership, M&A)

- Positioning changes

- Market share movement (if discernible)

- Strategic implications for us

Summary: Competitive position strengthening / stable / weakening?Industry Trends- Major trends affecting our market (with evidence)

- Emerging trends to watch

- Technology shifts relevant to our product

- Regulatory developmentsCustomer/Buyer Environment- Changes in buyer behavior or priorities

- Budget environment (expanding, contracting, shifting)

- Buying process changes

- What customers are asking for that they weren't beforeMacro Factors- Economic conditions affecting our market

- Funding environment for our customers

- Relevant policy or regulatory changes

- Industry-specific macro factorsBenchmark DataFor each of our key metrics, provide market context:

| Our Metric | Our Performance | Market Benchmark | Assessment |

Include: Growth rate, retention, CAC, LTV, sales efficiencyRisk Factors- Market risks that could affect our trajectory

- Competitive risks emerging

- Technology or disruption risks

- Mitigation considerationsOpportunities- Market tailwinds we could capitalize on

- Competitor missteps creating opportunity

- Emerging segments or use cases

- Strategic options worth consideringAppendix: Source Documentation| Claim | Source | Date | Link |

All key facts with citationsQuestions This Raises- Strategic questions the board might ask

- Data we need but don't have

- Decisions this context informs

</content>

<style>

Write for board consumption—concise, backed by data, executive-level. Use the Pyramid Principle. Include specific numbers, not just directional statements. Every claim should be cited. Format in a way that translates directly to slides.

</style>

<sources>

Prioritize: industry analyst reports (Gartner, Forrester, IDC), investor presentations from public comps, credible news sources, earnings transcripts, industry associations, government data, funding databases. Avoid vendor marketing content and outdated reports.

</sources>

<instructions>

Before starting, confirm you understand our competitive set and the specific context items I've provided. For each major claim, include the source and assess confidence level. If information is sparse for any section, note that explicitly—don't pad with filler content.

</instructions>