Quick Intro — What Brought Us Here?

• In one sentence, what outcome would make this conversation worth your time today?
• Which role best describes you? Options: Director of Product Marketing, Competitive Intelligence Analyst, Sales Enablement Manager, VP of Sales, Revenue Operations, Other
• How urgent is improving competitive intelligence and battlecard effectiveness for your leadership team right now? Options: Top priority (acting now), Important but not immediate, Nice-to-have this quarter, Not on leadership radar
• Has a competitor recently won deals you expected to close? Options: Yes — frequently (weekly), Yes — occasionally (monthly), Rarely, Not that I know of
• How many direct competitors does your team actively track today? Options: 1-2, 3-5, 6-10, 11-15, 16+
• What would be the single most valuable insight you want us to capture about your competitive situation in this discovery?

Are You Letting Competitors Win Quietly?

• When you lose to a competitor, how often do you truly know the root cause rather than a surface reason? Options: Almost always, Often, Sometimes, Rarely, Never
• Can you describe a recent loss where the real reason surprised you—what happened and why did it matter?
• Roughly what percentage of lost deals are explicitly attributed to a competitor in your CRM or postmortems? Options: >50%, 30-50%, 10-30%, <10%, Unknown
• How long does it typically take between a competitor action (pricing change, feature launch, messaging shift) and your team noticing it? Options: Within 24 hours, 24-72 hours, One week, Several weeks, We often miss it
• When leadership asks for a competitive analysis, how often does product marketing feel overwhelmed by ad-hoc requests? Options: Constantly, Often, Sometimes, Rarely, Never

Where Your Battlecards Fail When Stakes Are High

• Are your battlecards helping reps win deals or quietly collecting dust? Options: Regularly used in opportunities, Occasionally referenced, Rarely used, Not used / unknown
• How do reps usually find competitive info during deal prep today? Options: CRM record/embedded card, Shared drive or wiki, Slack/Teams, Email threads, I don’t know
• Who is responsible for creating and updating your battlecards today? Options: Product marketing, Competitive intelligence team, Sales enablement, Sales reps/AE, No clear owner, Other
• How often are battlecards updated with new product, pricing, or messaging changes? Options: Daily, Weekly, Monthly, Quarterly, Ad-hoc / never
• What sources must any automated intelligence absolutely capture to make a battlecard credible for your reps? Options: Pricing pages, Release notes / changelogs, Public product pages, Customer reviews (G2/Capterra), Job postings / hiring, Funding & press, Field intel from reps, Other
• Tell us about the last time a battlecard directly helped close a deal—what did the card say and how was it used?

Who Really Owns the Battlefield?

• If competitive intelligence were a named program at your company, who would be accountable for results? Options: Director of Product Marketing, VP/Head of Sales Enablement, Competitive Intelligence Lead, Chief Revenue Officer, Cross-functional committee, Not currently owned
• Who currently captures field intelligence (competitive notes from reps) and how often do they submit it? Options: AEs / Sales reps, Customer Success, BDA / SDR, Product Marketing, No one regularly captures it
• How is field intelligence captured today? Options: Direct entry into CRM, Email summaries, Shared docs or forms, Slack/Teams posts, Not captured systematically, Other
• Which CRM or deal tools must this platform integrate with to be used by reps in their workflow? Options: Salesforce, HubSpot, Microsoft Dynamics, Zendesk Sell, Other, No CRM / custom
• What incentives or KPIs (if any) exist to encourage reps to submit competitive notes? Options: Quota credit for intel, Recognition programs, No incentives, Manager coaching, Other
• How often do revenue or product leaders review competitive dashboards or win-loss summaries today? Options: Weekly, Monthly, Quarterly, Rarely, Never

If We Could Freeze Time: What Would Success Look Like?

• What single metric change would convince your VP that a competitive intelligence program is driving revenue? Options: Win-rate lift (percentage points), Deal size increase, Shorter sales cycles, Fewer surprise losses, Improved forecast accuracy, Other
• For a three-competitor pilot, what minimum intelligence freshness SLA do you need to trust alerts and battlecard updates? Options: Within 24 hours, 24-48 hours, Weekly, Not required / unsure
• What adoption rate among targeted reps would you consider a successful pilot? Options: >75%, 50-75%, 25-50%, <25%
• What win-rate improvement (absolute percentage points) would you need from pilot-influenced deals to consider rollout? Options: >10 pp, 5–10 pp, 1–5 pp, No specific numeric target
• Beyond metrics, what observable behaviors would tell you the program is truly embedded in deal cycles?
• What are your non-negotiable acceptance criteria for going from pilot to enterprise rollout?

What Would Make the Team Actually Use It?

• If using a new tool adds steps to a rep’s routine, they'll drop it—what would eliminate friction and make them adopt it instead?
• How important is in-CRM access to battlecards during deal preparation? Options: Critical — must be in CRM, Very important — deep links acceptable, Nice to have, Not important
• Which battlecard formats do reps find most usable today? Options: Embedded CRM component, One-page PDF, Short Slack/Teams snippets, Mobile-friendly card, Interactive Q&A, Other
• What training model historically drives the best adoption in your organization? Options: Live product training + coaching, Short on-demand videos, Role-based playbooks + manager reinforcement, Peer-led demos, None / Unsure
• Who on your team would be the internal champion responsible for driving rep usage during the pilot? Options: Sales Manager, Enablement Lead, Product Marketer, Competitive Intelligence Analyst, VP-level sponsor, No champion identified
• What objections do you expect from reps or managers and how have they been handled in past rollouts?

Next Steps — What Would Make This Pilot Irresistible?

• If you had to say yes to a pilot today, what configuration timeline would feel realistic for you (configuration + initial competitor setup)? Options: 3–4 weeks (preferred), Less than 3 weeks, More than 4 weeks, Unsure / depends on resources
• What pilot length would allow you to observe meaningful impact? Options: One quarter, Two quarters, Custom duration
• How should we choose the three competitors to include in the pilot (criteria you care about)?
• Which external data sources must we include for the pilot to be credible? Options: Pricing pages, Product release notes, Review sites (G2/Capterra), News & press, Job postings/hiring data, Funding & investor news, Customer case studies, Other
• Which internal systems must we integrate with during the pilot? Options: Salesforce, HubSpot, Slack/Teams, Looker/Tableau/BI, Okta/SSO, No integration required, Other
• Who will make the final go/no-go decision after the pilot and what evidence will they require?
• What are the top three risks or blockers that would derail a pilot for you?
• Is there anything else we haven't asked that would change how we design this pilot for you?

• Pre-Session: Current State & Consequence Alignment
• Pilot Kickoff: Scope, Instrumentation & Acceptance
• CRM Workflow Integration & Validation Session
• Battlecard Usability Workshop & Rep Roleplay
• Pilot Review & Go/No-Go Decision

• Implement the top 3 template edits identified and refresh the battlecards for pilot deployment.
• CRM admin creates a sandbox deal and grant access; CustomerNode deploys the capture integration to that sandbox for verification.
• Set weekly pilot check-ins on the calendar and assign the decision owner for go/no-go.
• Recap CRM Mapping & Test Cases
• Prove that reps can submit field intelligence without leaving their deal workflow.
• Confirm captured data is indexed and visible in the platform within the agreed SLA.
• Identify and prioritize any CRM mapping gaps or UX friction to be resolved before pilot start.
• Fix any mapping errors identified (field mappings, object links) and redeploy integration in sandbox.
• Update in-CRM guidance text or CTAs to improve discoverability if reps struggled to find the capture point.
• Instrument analytics events that count successful captures and link them to pilot acceptance metrics.
• Brief on Success Signals & Roleplay Scenarios
• Measure time-to-find and rep confidence using battlecards in realistic deal conversations.
• Capture concrete edits to battlecard content and structure to improve mid-deal usability.
• Validate that battlecards reference the right competitor signals customers care about.
• Introductions & Objective
• Create a short 'how-to' card for reps showing exactly where to access battlecards in the CRM workflow.
• Record roleplay sessions and extract 2–3 exemplar rebuttals to seed the battlecard phrasing library.
• Recap Agreed Success Criteria
• Determine whether the pilot meets the agreed acceptance criteria for freshness, usability, and CRM fit.
• Surface documented evidence of business impact to justify rollout or identify gaps requiring further work.
• Agree concrete next steps, owners, and timeline for rollout or remediation.
• If Go: Draft enterprise rollout plan with phased adoption, training, and SLA commitments.
• If No-Go: Produce a remediation backlog with priority fixes, owners, and revalidation plan for a second pilot.
• Capture a one-page Executive Summary of pilot outcomes and circulate to stakeholders for sign-off.
• Produce a single-sentence current-state that everyone signs off on.
• Quantify the business consequence in agreed metrics to create urgency.
• Agree the future-state outcome and measurable success signals for the pilot.
• Establish immediate prework items and owners to enable the pilot kickoff.
• Customer provides three representative active deals (deal IDs, stage, stakeholders) for pilot validation.
• Customer shares the three competitors to include and any public/private data sources to prioritize.
• Admin grants read/write CRM sandbox access and sample pipeline view to the CustomerNode pilot team.
• Product marketing names 2–3 reps for roleplay and ongoing feedback during pilot.
• Confirm Pilot Scope & Competitor List
• Convert scope decisions into a shared, time-bound pilot plan with owners.
• Agree measurable acceptance tests for freshness, battlecard relevance, and CRM fit.
• Ensure CRM mapping and instrumentation are detailed enough to run tests without rework.
• Establish a communication and escalation plan for the pilot period.
• CustomerNode configures competitor feeds and battlecard templates for the three selected competitors.
• Engineering runs a one-off freshness test: inject or identify a known competitor change and confirm system updates battlecards within 24 hours.
• Freshness & Signal Coverage Report
• Instrumentation Plan
• Rep Roleplay: Preparation Phase
• Current State Statement
• Live Walkthrough in CRM Sandbox
• Backend Flow Verification
• Consequence Quantification
• Battlecard Usage & Usability Metrics
• Rep Roleplay: Live Objection Handling
• Battlecard Template & Acceptance
• CRM Capture & Attribution Analysis
• CRM Workflow Mapping
• Edge Case Tests
• Collect Structured Feedback
• Future-State Definition
• Win-rate & Business Impact Evidence
• Validation Criteria & Success Signals
• Refinement & Quick Fix Prioritization
• Pilot Timeline, Roles & Escalation
• Iterate & Quick Update Plan
• Prework & Data/Access Checklist

• Create Structured Competitor Profiles
• Deploy Product Launch Monitoring and Alerts
• Activate Pricing and Packaging Change Detection
• Produce Sales Battlecards for Target Competitors
• Install In‑Deal CRM Battlecard Widget
• Integrate Field Intelligence Capture into CRM
• Enable 24‑Hour Automated Battlecard Updates
• Deploy Win‑Rate Attribution and Usage Analytics
• Monitor Review Sentiment and Public Feedback
• Track Competitor Hiring and Funding Events
• Publish Executive Competitive Briefing Packs
• Export Intelligence Feeds to BI and Slack

Create Structured Competitor Profiles

• Which competitors should be included in the profile set for the pilot (list up to 3 for pilot, note enterprise rollout may include 3–15)?
• What profile fields are required (select all that apply)? Options: Product summary, Key differentiators, Pricing overview, Customer references / logos, Market positioning / messaging, Technical stack, Support model, Regulatory/compliance notes
• How frequently do you want core profile fields reviewed or refreshed? Options: Weekly, Bi-weekly, Monthly, On-change only
• What internal or proprietary sources should augment public data (e.g., internal win/loss notes, customer interviews, product spec docs)?
• Who owns profile validation and sign-off in your organization? Options: Product Marketing, Competitive Intelligence, Sales Enablement, Sales Ops, Other
• Are there any compliance, IP, or NDA constraints on what can be stored in competitor profiles? Options: Yes, No

Deploy Product Launch Monitoring and Alerts

• Which competitor product launch signals matter most to you? Options: New product release, Major feature release, Beta programs, Partnerships / integrations, Rebranding / messaging changes
• Which public sources should be monitored for launches (select all that apply)? Options: Company press pages, Product changelogs, Twitter / LinkedIn, Developer forums, App stores / marketplaces, RSS/news feeds
• What alert channels do you prefer for launch notifications? Options: Email, Slack, CRM activity feed, Dashboard alerts, Webhook to SIEM/BI
• What minimum detail must an alert include to be actionable (e.g., feature impact statement, affected modules, link to source)?
• What cadence and SLA do you require between a detected launch and a populated alert in the platform? Options: Within 4 hours, Within 12 hours, Within 24 hours, 48+ hours
• Who should be subscribed to launch alerts and who should receive executive summaries? Options: Product Marketing, Sales Leadership, Account Executives, Customer Success, Other

Activate Pricing and Packaging Change Detection

• Which pricing signals are critical to detect for pilot competitors? Options: List price changes, Discounting patterns, Packaging re-bundles, Introductory offers, Seat-based vs. usage changes
• From which sources should pricing be pulled (select all that apply)? Options: Public pricing pages, Documentation/FAQs, Partner portals, Job postings (indirect signals), Field intelligence submissions
• Do you require historical pricing trend capture for attribution (e.g., capture snapshots daily/weekly)? Options: Yes, No
• How do you want pricing changes surfaced in battlecards and competitor profiles (e.g., summary + delta, full history)? Options: Delta summary, Full historical view, Both
• What tolerance for false positives do you accept (i.e., minor wording edits triggering alerts)? Options: Low (strict filtering), Medium, High (broad capture)
• Who should approve pricing-change alerts before they are pushed to sellers or execs? Options: Product Marketing, Pricing Team, Competitive Intelligence, No approval needed

Produce Sales Battlecards for Target Competitors

• What battlecard templates do you prefer (select all that apply)? Options: One-page quick reference, Deal-stage playbook, Objection-handling flow, Technical comparison matrix, Pricing counter-offer guidance
• What minimum elements must every battlecard include to be considered usable by reps?
• Do you want battlecards tailored by persona (e.g., economic buyer, technical buyer, champion)? Options: Yes, No
• How should battlecards be versioned and dated (e.g., automatic timestamp, manual sign-off)? Options: Automatic timestamp, Manual sign-off + version, Both
• What languages or regional variants are required for battlecards during pilot? Options: English, Spanish, French, Other
• Which metrics define a battlecard as accepted by sales (e.g., rep adoption rate, rep feedback score, usage in closed-won deals)?

Install In‑Deal CRM Battlecard Widget

• Which CRM(s) must the in-deal widget support for the pilot? Options: Salesforce, HubSpot, Dynamics 365, Other
• Where in the deal record should the widget appear (select all that apply)? Options: Top of opportunity page, Related lists / tabs, Activity pane, Mobile view
• Do you require widget visibility to be role-based or stage-based (e.g., only visible to AEs in proposal stage)? Options: Role-based, Stage-based, Both, No restrictions
• What CRM objects or fields should the widget read/write (e.g., competitor field, deal notes, next steps)?
• Are there any security or admin approval processes required for installing custom widgets in your CRM? Options: Yes, No
• Do you require offline/slow-network behavior for the widget (e.g., cached battlecards)? Options: Yes, No

Integrate Field Intelligence Capture into CRM

• What field intelligence types should reps be able to submit directly from the CRM? Options: Win/loss notes, Pricing observed, Feature gaps reported, Competitive positioning used by customer, Customer objections
• Should submissions create structured fields, free-text notes, or both? Options: Structured fields, Free-text notes, Both
• Which CRM events should prompt a capture prompt (select all that apply)? Options: Opportunity created, Stage change, Deal lost, Deal won, Manual 'capture' button
• Who should review and validate incoming field intelligence before it becomes part of the official CI dataset? Options: Sales Ops, Competitive Intelligence, Product Marketing, Auto-validated
• What privacy or PII constraints apply to field submissions (e.g., redact customer names, consent required)? Options: PII allowed, PII redaction required, Customer consent required
• Do you require training materials or in-product guidance to drive consistent rep submissions? Options: Yes, No

Enable 24‑Hour Automated Battlecard Updates

• Which update classes must be processed within 24 hours (e.g., pricing, feature, messaging, critical incidents)? Options: Pricing, Feature/launch, Messaging/positioning, Security incidents, All of the above
• What verification level do you require before automated updates overwrite existing battlecard content? Options: Automated-only, Automated with human review flag, Human approval required
• How should change alerts be surfaced to stakeholders when a battlecard is updated (select all that apply)? Options: Email digest, Slack ping, In-app notification, CRM alert
• Do you need rollback/version history for battlecards and an easy restore path? Options: Yes, No
• What acceptance tests should be performed on updated battlecards before wider rollout (e.g., spot-check by PMM, rep usability test)?

Deploy Win‑Rate Attribution and Usage Analytics

• Which win-rate attribution model do you prefer for pilot analysis? Options: Last-touch (tool usage), Multi-touch (weighted), Deal-stage correlation, Custom model
• What CRM signals will you map to analytics (select all that apply)? Options: Opportunity stage changes, Closed-won/lost, Deal size, Close date, Competitor field
• What usage metrics should be tracked to measure adoption (select all that apply)? Options: Battlecard views per rep, Time on card, In-deal widget usage, Field intelligence submissions, Search queries
• What time window should analytics evaluate to measure pilot impact on win rate? Options: Quarter (3 months), Monthly, Custom (specify)
• Who should receive analytics reports and at what cadence? Options: Weekly to Sales Leadership, Bi-weekly to PMM, Monthly executive summary, Ad-hoc on request
• Are there external BI tools you want attributed data exported to for deeper analysis? Options: Tableau, Looker, Power BI, Other, None

Monitor Review Sentiment and Public Feedback

• Which review sites and public feedback channels should be monitored for pilot competitors? Options: G2, Capterra, TrustRadius, App stores, Social media
• Do you require sentiment scoring, topic extraction, and example quotes in alerts? Options: Sentiment only, Sentiment + topic, Full excerpts + metadata
• What language coverage is required for sentiment monitoring? Options: English only, English + top regions, Global/multi-language
• What thresholds should trigger high-priority alerts (e.g., sudden drop in rating by 0.5, spike in negative reviews)?
• Who will act on negative sentiment findings (e.g., Customer Success, Product, PR)? Options: Product, Customer Success, PR/Comms, Sales Enablement
• Do you want reviewer identity and company metadata captured where available? Options: Yes, No

Track Competitor Hiring and Funding Events

• Which event types are high priority to track for pilot competitors? Options: Senior hires (exec/engineering), Hiring surges by function, Funding rounds, M&A activity
• Which sources should be used for these signals? Options: LinkedIn, Crunchbase, Press releases, Job boards, SEC filings
• What lead time or frequency is acceptable between event detection and notification? Options: Real-time, Within 24 hours, Within 72 hours
• Do you want these events mapped to playbooks (e.g., hiring -> messaging about talent/scale)? Options: Yes, No
• Should hiring/funding events be surfaced in executive briefs vs. frontline battlecards differently? Options: Differentiate (Yes), Same feed (No)

Publish Executive Competitive Briefing Packs

• What cadence do you want for executive briefings during the pilot? Options: Weekly, Bi-weekly, Monthly, Quarterly
• What format do executives prefer (select all that apply)? Options: Interactive dashboard, PDF executive summary, Slide deck, Short email brief

• Statement of Work (SOW)
• Pilot Agreement
• Timeline & Milestones Schedule
• Roles & Responsibilities Matrix
• Success Metrics & Acceptance Criteria
• Data Processing Agreement (DPA)
• CRM Integration Addendum
• Pricing & Payment Terms
• Escalation & Rollback Plan
• Change Order & Scope Management
• Confidentiality & IP Agreement
• Acceptance & Rollout Decision Document

• Pilot Results Review (Executive & Cross‑Functional)
• Adoption & Workflow Deep Dive (Sales, Enablement, CS)
• Win-Rate Impact & Attribution Analysis (Sales Leadership & RevOps)
• Product & Data Quality Retrospective (Product, Data Ops, CI Team)
• Rollout Decision, Roadmap & Communications (Executive Sponsors, PMM, Sales, CS, RevOps)

• Opening & Objective
• Schedule targeted follow-up deep-dive sessions (Adoption, Win-rate, Data Quality) as required.
• One-sentence Current State
• Pinpoint exactly why adoption is above/below target and what will change the behavior of reps in the deal workflow.
• Agree on a prioritized set of adoption fixes with owners and timelines to include in rollout plan.
• Collect representative deal artifacts to validate proposed UX/CRM changes.
• Create a prioritized backlog of adoption UX and CRM fixes with owners and delivery dates.
• Produce 3 annotated representative deal walk-throughs demonstrating planned workflow changes for training.
• Develop and schedule brief role-based training sessions and a communications plan for rollout readiness.
• Define Current State & Baseline
• Confirm or revise the attribution approach and the statistical validity of observed win-rate changes.
• Produce clear revenue impact scenarios to inform executive rollout decisions.
• Agree on the rollout success metrics and measurement cadence for post-rollout validation.
• Deliver a validated analytics brief with methodology, confidence intervals, and recommended rollout KPIs.
• If necessary, run an extended analysis on an expanded dataset or longer timeframe to increase confidence.
• Define the measurement cadence and dashboard ownership for post-rollout tracking.
• Current State of Signal Coverage
• Produce a clear, prioritized list of product and data fixes required before enterprise rollout.
• Agree on measurable acceptance criteria for signal freshness and accuracy tied to business outcomes.
• Establish monitoring ownership and escalation procedures for post-rollout data quality assurance.
• Create a prioritized technical backlog with estimated effort, owner, and release milestone for each item.
• Implement or adjust monitoring dashboards and set alert thresholds for critical signal classes.
• Deliver sample-validated battlecard edits for the top 3 missed signals to demonstrate fix effectiveness.
• Synthesis of Prior Meeting Outcomes
• Obtain executive approval for a defined rollout path with conditions, owners, and timeline.
• Establish a clear measurement and governance plan to ensure rollout success and rapid remediation of issues.
• Align communications and enablement to ensure sales adoption from day one of rollout.
• Publish the rollout charter (scope, timeline, owners, KPIs) and distribute to stakeholders within 48 hours.
• Kick off a cross-functional rollout working group with weekly sprints and milestone reviews.
• Prepare and schedule executive and sales communications, plus enablement sessions, timed to rollout start.
• Ensure all stakeholders share a single, evidence-backed view of pilot outcomes vs agreed success signals.
• Obtain an explicit decision (go/no-go/iterate) and assign immediate owners for next steps.
• Surface any critical unknowns requiring follow-up analysis before final rollout approval.
• Document the go/no-go decision and circulate a one-page rationale and required actions within 24 hours.
• Assign owners to unresolved validation gaps and set deadlines for delivering missing evidence.
• Recap of Agreed Success Signals
• Final Decision Framing
• Adoption Metrics Review
• Examples of Misses & False Positives (Proof)
• Data Validation & Cohort Definitions
• Current State Snapshot (Diagnosis)
• Representative Deal Walkthroughs (Proof)
• Presentation of Results (Proof)
• Risk Assessment & Mitigation
• Root-Cause Analysis
• Define Future State for Data Quality
• Sensitivity & Risk Analysis
• Consequence Analysis
• Rollout Scope, Phasing & Timeline
• Rep Feedback & Pain Points (Input Gathering)
• Proof Points & Artifacts
• Success Metrics & Measurement Plan
• Define Future State for Adoption
• Revenue Projection Scenarios
• Prioritize Enhancements
• Validation & Stakeholder Feedback
• Decision Criteria for Rollout Metrics
• Operationalize Monitoring & Escalation
• Rapid Fix Brainstorm & Prioritization
• Communications & Change Management