Quick Warm-Up: Tell Us About Your Revenue Team

• How many people are on your revenue org (AEs + SDRs + CSMs + RevOps)? Options: 1-25, 26-50, 51-100, 101-250, 251-500, 501-2,000
• Which CRM or tracking system are you using right now? Options: HubSpot (free/paid), Salesforce, Zoho, Pipedrive, Custom spreadsheet(s), No formal system, Other
• Roughly what annual recurring revenue (ARR) band best describes you? Options: <$5M, $5M–$25M, $25M–$100M, $100M–$500M, >$500M
• How would you describe current day-to-day CRM adoption among reps? Options: High — reps rely on CRM, Mixed — some teams use it, some don't, Low — CRM used only for required minimum, No adoption — reps use spreadsheets/Slack
• Tell us about one recent forecasting miss that mattered — what happened and who felt the consequences?
• Which sales motion best matches most of your deals? Options: Transactional (short cycle), Named accounts / enterprise-style (multi-stakeholder), Channel / partner-led, Product-led with sales touch, Hybrid

Why Do Forecasts Keep Surprising You?

• When your forecast is wrong, where do you usually trace the breakdown first? Options: Rep input (missing/old data), Deal stage misalignment, Conflicting spreadsheet vs CRM, Lack of activity signals, Opps stuck in approval/quote stage
• How often does a deal that looked healthy at the start of the week disappear by close of week? Options: Multiple times/week, Weekly, Monthly, Quarterly, Rarely
• What downstream impact do these surprises create for finance, operations, or hiring decisions?
• Which source do you (or your leaders) trust most when there’s disagreement — CRM, spreadsheets, or manager judgment? Options: CRM, Spreadsheets, Manager judgment / tribal knowledge, Mixed — no single source
• Walk me through a recent instance where a late surprise changed a quarter's plan — who owned it and how was it discovered?

Where the CRM Was Supposed to Save Us but Didn’t

• What is the single biggest way your CRM has failed your sellers or managers? Options: Too hard to use, Doesn’t model multi-stakeholder deals, Poor activity capture, Rigid quote/configuration, Slow and unreliable, Reporting is inaccurate
• How do reps get their work done instead — what tools or habits replace the CRM? Options: Shared spreadsheets, Slack or chat threads, Personal Google docs, Email threads, Manager-run tracker, Other
• How long has this pattern (CRM promise → low adoption) been affecting your org? Options: <6 months, 6–12 months, 1–2 years, 2+ years
• When past CRM projects failed, what emotional reactions did you see from reps and managers (frustration, apathy, resistance)? Give a specific example.
• Which parts of your sales process feel most impossible to model in the current system? Options: Multi-stakeholder approval, Custom quoting and discounts, Territory-based routing, Complex product bundles, Contract renewals/expansions, Other

Who Really Decides and Who Actually Uses It?

• If the people signing the PO had to live with the system daily, what would change about your buying process?
• Which roles will be most involved in evaluating the pilot? Select all that apply. Options: VP Sales / CRO, Head of RevOps / Sales Ops, Finance, Marketing, IT / Security, Sales Managers, Selected AEs / SDRs
• Who ultimately controls the budget and final go/no-go? Options: VP Sales / CRO, CFO / Finance, CEO, Board / Investors, Other
• Which stakeholder do you expect will be the hardest to convince, and why?
• What sign-off cadence or checkpoints does your leadership expect during a 30-day pilot? Options: Weekly, Bi-weekly, Mid-pilot review + final, Only final review, Other

Imagine Forecasts You Can Trust

• If your forecast was accurate next quarter, what would that allow you to do differently?
• Which measurable outcomes would prove value to you? (pick top 3) Options: Forecast accuracy (%), Rep time saved per week, Pipeline coverage ratio, Win rate improvement, Sales cycle length reduction, Deal slip rate reduction
• How would improved pipeline visibility change conversations between sales and finance?
• What level of forecast accuracy would feel meaningful to leadership this year? Options: >90%, 80–90%, 70–80%, Any measurable improvement is fine
• Describe the behaviors you would expect reps and managers to adopt if the system truly helped close deals.

Minimal Pilot, Maximum Truth

• What single result in a 30-day, 3–5 rep pilot would make you feel confident to proceed?
• Which scope do you want the pilot to mirror? Choose the closest fit. Options: Full deal lifecycle (lead → close), Opportunity stages + quotes only, Activity capture + forecasting only, Territory routing + quoting, Other
• What technical integrations must be live for the pilot to be meaningful? Options: Email/calendar capture (Gmail/Outlook), SSO (SAML/OAuth), ERP/PSA integration, Dialer/telephony, Proposal/CPQ tool, None required for pilot
• What adoption metrics will you use to judge pilot success? (select all that apply) Options: % of pilot reps logging in weekly, % of deals moved through mapped stages, Activity capture rate (emails/calls logged), Forecast variance reduction, Number of deals won using platform quoting
• Who will give final pilot approval — list role and what their acceptance criteria are.

What Would Make Your Reps Choose This Voluntarily?

• What frustrations would you want the CRM to eliminate from a rep’s typical day? Options: Manual data entry, Chasing approvals, Slow quoting, Missing activity capture, Unclear next steps in deals, Other
• Which features would cause reps to prefer this tool over their spreadsheets right away? Options: Auto-capture email & calendar, Native quoting templates, Territory automation, Mobile ease-of-use, Pipeline risk signals, Commission/forecast transparency
• How do your reps currently feel about change projects—excited, skeptical, exhausted, or something else? Options: Excited, Curious but cautious, Skeptical, Exhausted
• What short enablement approach would you prefer for pilot reps? Options: 1-hour live workshop, Daily short standups first week, Recorded micro-lessons + office hours, One-on-one coaching for each AE, Other
• What incentives (if any) would genuinely motivate reps to adopt during the pilot? Options: Commission credit for pilot deals, Public recognition, Cash bonuses, Manager coaching time, No incentives—product must sell itself

Integration & Security: The Things That Stop Deals

• What security or compliance requirement will kill the deal if unmet? Options: SSO required, Data residency rules, SOC2 / ISO certification, No third-party email capture allowed, Vendor security questionnaire must be approved
• Do you require single sign-on (SSO) for pilot users? Options: Yes — must be enabled before pilot, Yes — but can be deferred for pilot, No
• How strict are your data retention and deletion policies for vendor platforms? Options: Strict — short retention + right to delete, Moderate — vendor controls fine, Flexible — depends on contract
• Which backend systems must integrate for reporting/booking accuracy? Options: ERP/Finance, Billing system, Proposal/CPQ, Marketing automation, None required
• What is your expected timeline for a security review and who runs it? Options: <2 weeks, 2–4 weeks, 1–2 months, Longer than 2 months
• Are there any contract or legal terms (data access, retention, export) that are non-negotiable for you?

Next Steps: Committing to a Pilot That Actually Proves Value

• Given everything we discussed, what is the one non-negotiable outcome you need from the pilot?
• Who will be our day-to-day champion and who will be the escalation contact during the pilot?
• What does a realistic six-week go/no-go timeline look like on your side? Options: Start next week, Start in 2–4 weeks, Start next quarter, Unsure — need internal alignment
• What concerns or blockers should we surface now so we don’t hit them mid-pilot?
• If we could promise one thing to make the pilot low-risk for your team, what should that promise be?

• Pilot Kickoff & Alignment
• Deal Mapping & Workflow Configuration Workshop
• Week 1 Checkpoint — Adoption & Data Capture
• Mid-Pilot Review — Outcome Validation & Optimization
• Pilot Close — Results Review & Go/No-Go Decision

• Introductions & Objectives
• Implement agreed stage mappings, exit criteria, and quoting rules in the pilot environment.
• Enable auto-capture for pilot reps and verify initial activity syncs.
• Document any edge cases discovered during mapping and schedule follow-ups.
• Adoption Snapshot (logins, deal updates)
• Verify pilot reps are actively using the system and real deal activity is captured.
• Resolve or triage high-impact blockers that prevent data capture or flow execution.
• Collect rep feedback to inform minor configuration or enablement adjustments.
• Fix critical blockers (access, integration errors) and confirm resolution.
• Schedule short coaching sessions for reps showing low adoption.
• Update sample deals or configuration based on immediate feedback.
• Adoption & Usage Metrics vs Success Criteria
• Determine whether pilot is trending to meet success criteria and identify corrective actions.
• Demonstrate concrete examples where the platform produced the future-state benefit.
• Agree a short remediation plan and measurement approach for the final two weeks.
• Implement high-priority optimizations (config or enablement) and assign owners.
• Refresh the report/dashboard with final two-week metrics to be used in the close meeting.
• Prepare 2–3 canonical deal narratives (diagnosis → proof → validation) for the pilot close.
• Recap: Current State, Consequence, Future State (one-sentence each)
• Secure an explicit go/no-go decision tied to the documented success criteria.
• Validate that pilot outcomes demonstrably reduce the quantified Consequence and realize the Future State.
• Agree commercial and deployment next steps, owners, and timelines if decision is go.
• Collect executive sign-off on the pilot results and agreed next steps (go/no-go).
• Compile and distribute the pilot summary report including canonical deal stories and metrics.
• If go: draft the mutual-commit document / SOW and schedule kickoff for Deployment stage.
• If no-go: document unresolved gaps and recommended remediation or alternative path.
• Document a single-sentence Current State and its quantified Consequence.
• Agree a one-sentence Future State (operational outcome) the pilot must prove.
• Approve pilot scope, success criteria, pilot reps, and access requirements.
• Establish checkpoints, reporting cadence, and decision forum for go/no-go.
• Author and distribute the single-sentence Current State, Consequence, and Future State statements.
• List and provision pilot reps, sandbox accounts, and sample deals into the pilot environment.
• Confirm integrations needed for the pilot (email/calendar, quoting, ERP) and schedule technical access.
• Publish pilot success criteria and reporting template for checkpoints.
• Pre-work Check & Sample Deal Review
• Have platform stages, exit criteria, and quoting workflow configured for the representative sample deals.
• Demonstrate that the configured flow eliminates a specific manual rework or forecasting gap (tie to consequence).
• Agree outstanding configuration tasks, owners, and deadlines for completion before the first checkpoint.
• Load identified sample deals into the sandbox with complete metadata.
• Review 3 Example Deals
• Confirm Current State (one sentence)
• Map Sales Stages & Exit Criteria
• Final Results vs Success Criteria
• Forecast Confidence / Deal Health Examples
• Configure Quoting Workflow & Approvals
• Blocker Triage & Immediate Fixes
• Surface Consequence (one sentence + quantification)
• Quoting Throughput & Approval Outcomes
• Canonical Deal Stories (Diagnosis → Proof → Validation)
• Risk & IT Review (SSO, Data Retention, Integrations)
• Define Future State (one sentence)
• Gap Analysis & Required Optimizations
• Behavior Coaching & Rep Feedback
• Territory / Ownership & Auto-capture Settings
• Validation Questions & Forced Confirmation
• Confirm Next Steps Before Mid-Pilot
• Pilot Scope & Success Criteria
• Run a Paper/Pilot Walkthrough (Diagnosis → Proof → Validation)
• Decision & Commercial Next Steps
• Plan for Final Two Weeks

• Import and Clean Lead and Contact Data
• Migrate and Reconcile Opportunity History
• Configure Pipeline Stages and Deal Types
• Map Multi-Stakeholder Opportunity Architecture
• Set Role-Based Permissions and Team Hierarchies
• Configure Territory and Account Assignment Rules
• Enable Email and Calendar Auto-Capture
• Integrate Email, Dialer, and Proposal Tools
• Integrate ERP for Bookings and Revenue Sync
• Activate Pipeline Analytics and Forecast Confidence
• Configure Deal Approval and Exit Criteria Workflows
• Deploy Lead Scoring and Campaign Attribution
• Enable Automated Nurture Sequences and Routing
• Train Reps through Guided Live Trial Sessions

Import and Clean Lead and Contact Data

• Do you have lead and contact records to import into the platform? Options: Yes, No
• What primary formats will the import files be in? Options: Spreadsheet (CSV/XLSX), Legacy CRM export, Database export (SQL/CSV), Marketing automation export, Other
• Approximately how many lead/contact records are you planning to import? Options: Less than 1,000, 1,000-10,000, 10,001-50,000, More than 50,000
• Do records require deduplication, normalization (e.g., phone/email format), or enrichment before import? Options: Deduplication, Normalization, Enrichment (firmographic/intent), No cleaning required, Unsure - need assessment
• Are there required custom fields or mappings that must be preserved during import? Options: Yes, No
• If yes, list the critical fields or describe mapping rules that must be retained (e.g., lead source, original owner, import batch id).
• Are there privacy, consent, or compliance constraints (GDPR/CCPA) affecting which contacts we can import or how long to retain them? Options: Yes, No, Partially - need review

Migrate and Reconcile Opportunity History

• Do you want historical opportunities and pipeline history migrated into the trial environment? Options: Yes - full history, Yes - last 12 months, Yes - last 3-6 months, No - only active deals
• What opportunity fields and historical attributes are essential to migrate (e.g., stage history, close dates, products, line items, discount history)?
• How accurate is your existing opportunity data (won/lost reasons, closed dates)? Options: High (>90% accurate), Moderate (60-90%), Low (<60%), Unknown
• Do you need opportunity history reconciled with finance/ERP booking records during migration? Options: Yes - full reconciliation, Yes - sample reconciliation, No
• Are there multiple currency or regional salesbooks that must be normalized? Options: Single currency, Multiple currencies - need mapping, Multi-region pricebooks
• Who will own validation of migrated opportunity history (RevOps, Finance, Sales Manager)? Options: RevOps/Sales Ops, Finance, Sales Manager/AE, Implementation Partner
• What is the acceptable reconciliation tolerance for migrated opportunity amounts and statuses? Options: 0% - exact match, 1-2% variance, 5% variance, Other - specify

Configure Pipeline Stages and Deal Types

• How many distinct pipelines do you need (e.g., new business, renewal, channel)? Options: 1, 2-3, 4-6, More than 6
• Do you require custom stages and stage-specific exit criteria for each pipeline? Options: Yes - custom stages per pipeline, Yes - same stages across pipelines, No - use standard stages
• What deal types must be modeled (select all that apply)? Options: New Sales, Upsell/Cross-sell, Renewal/Subscription, Channel/Partner, Proof of Concept/Pilot, Other
• Do you need probability or forecast category mapping per stage (e.g., commit, best case)? Options: Yes - probability per stage, Yes - custom forecast categories, No - use defaults
• Are there stage transition rules or automation required (e.g., auto-move when quote signed)? Options: Yes - automated transitions, Yes - triggers for reminders/approvals, No
• Who will define stage exit criteria and approve the pipeline configuration? Options: VP Sales/CRO, RevOps/Sales Ops, Sales Managers, Implementation Consultant

Map Multi-Stakeholder Opportunity Architecture

• Do your deals require modeling multiple stakeholders or buying centers (economic buyer, champion, technical approver)? Options: Yes - always, Sometimes, No
• Which contact roles should be tracked on opportunities? Options: Economic Buyer, Champion, Technical Buyer, Procurement, Legal, User/Influencer, Other
• Do you need relationships between accounts (parent/child) and contact role inheritance? Options: Yes - parent/child accounts, Yes - account hierarchies only, No
• Should stakeholder engagement signals (meeting frequency, response time) influence deal health or scoring? Options: Yes - map to health and score, Yes - advisory only, No
• Do you require templates or prompts to capture who the internal owner is for each stakeholder (e.g., technical champion owner)? Options: Yes, No
• Are external partner contacts or VARs part of your opportunity structure and need distinct roles? Options: Yes - partners included, No

Set Role-Based Permissions and Team Hierarchies

• How many distinct user roles should be defined initially (e.g., AE, SDR, Manager, RevOps, Finance)? Options: 1-2, 3-5, 6-10, More than 10
• Do certain roles require restricted access to sensitive fields (pricing, commission, finance fields)? Options: Yes - field-level restrictions, Yes - record-level restrictions, No
• Do you want team or territory-based hierarchies for roll-ups and reporting? Options: Yes - team-based, Yes - territory-based, Both, No
• Will you use SSO and group membership to provision roles automatically? Options: Yes - SSO groups map to roles, Partially - manual provisioning, No
• Is an audit trail or activity log required for changes by role (deal edits, stage moves)? Options: Yes - full audit, Yes - limited audit, No
• Who will own permissions and ongoing user lifecycle management (IT, RevOps, HR)? Options: IT/Security, RevOps/Sales Ops, HR/People Ops, Other

Configure Territory and Account Assignment Rules

• What basis do you use for territory assignment? Options: Geography, Industry/Vertical, Account Size/ARR, Named accounts, Hybrid rules
• Do you require automated assignment rules (round-robin, predictive, rules-based)? Options: Yes - rules-based, Yes - round-robin, Yes - predictive, No - manual
• How many territories or segments need to be modeled initially? Options: 1-5, 6-20, 21-50, More than 50
• Should account reassignment be automated on owner changes or territory updates? Options: Yes - automated reassignment, No - manual approval required, Conditional
• Do you need rules to prevent account overlap between teams and flag conflicts? Options: Yes - block overlaps, Yes - notify only, No
• Who will manage territory rules going forward (RevOps, Sales Ops, Sales Leadership)? Options: RevOps/Sales Ops, Sales Leadership, IT/Implementation

Enable Email and Calendar Auto-Capture

• Which email/calendar platforms are used by your reps? Options: Gmail/Google Workspace, Outlook/Exchange, Other
• Which activity types should be auto-captured? Options: Emails, Calendar events/meetings, Attachments, Call logs/recordings, Notes
• Do you prefer server-side capture (admin-configured) or per-user plugin/connectors? Options: Server-side (recommended), Per-user connector, Mixed
• Are there privacy or legal constraints on capturing communications (sensitive accounts, GDPR opt-outs)? Options: Yes - restrictions apply, No
• Should captured activities automatically associate to related accounts, opportunities, and contacts or be manually linked? Options: Auto-associate by matching, Manual linking required, Auto with review
• What retention policy should apply to captured emails/meetings (e.g., 1 year, 3 years, indefinite)? Options: 1 year, 3 years, 5 years, Indefinite, Custom - specify

Integrate Email, Dialer, and Proposal Tools

• Which sales engagement and dialer tools do you use today? Options: Salesloft, Outreach, Phone Dialer (RingCentral), Aircall, Other
• Which proposal/CPQ tools are in use (e.g., PandaDoc, Proposify, Conga)? Options: PandaDoc, Proposify, Conga/CPQ, Salesforce CPQ, Other
• Do you require two-way sync (create proposal records in CRM and reflect signed status back) or one-way sync? Options: Two-way sync, One-way sync (tool -> CRM), One-way sync (CRM -> tool)
• Are API keys, admin credentials, or connector access available for these systems? Options: Yes - available, Partially - need help, No - need procurement
• Do you want call recordings and dispositions captured and searchable within opportunities? Options: Yes - recordings and dispositions, Disposition only, No
• Are there latency or uptime SLAs required for these integrations (real-time vs. batch)? Options: Real-time, Near real-time (minutes), Daily batch

Integrate ERP for Bookings and Revenue Sync

• Which ERP or finance systems must be integrated for bookings and revenue data? Options: NetSuite, SAP, Oracle ERP, Microsoft Dynamics, Other
• What data should flow between CRM and ERP (bookings, invoices, revenue recognition, SKU mapping)? Options: Bookings only, Bookings + invoices, Full revenue sync (recognition), SKU/pricebook mapping
• Do you require one-way (ERP -> CRM) or two-way synchronization? Options: ERP -> CRM (one-way), Two-way sync, CRM -> ERP (limited)
• What frequency is acceptable for sync (real-time, hourly, nightly)? Options: Real-time, Near real-time (minutes), Hourly, Nightly
• Are there finance/Compliance rules we must honor (closing periods, SOX controls)? Options: Yes - strict controls, Yes - basic controls, No
• Who is the finance/system owner for ERP integration and validation? Options: Finance/FP&A, RevOps/Sales Ops, IT/Systems

Activate Pipeline Analytics and Forecast Confidence

• Which forecasting model do you prefer to start with? Options: Stage-weighted (traditional), Manager-adjusted, AI-driven probability scoring, Combination/custom model
• What key metrics must be visible in analytics (forecast accuracy, pipeline coverage, velocity, conversion rates)? Options: Forecast accuracy, Pipeline coverage, Deal velocity, Win rate by rep, Custom KPIs
• Do you require confidence scoring at the deal level that incorporates engagement signals? Options: Yes - enable deal confidence scores, No - keep manual scoring
• What forecast horizons are required (weekly, monthly, quarterly, rolling 12)? Options: Weekly, Monthly, Quarterly, Rolling 12 months

• Statement of Work (SOW)
• Subscription / Order Form
• Pilot Success Criteria & Acceptance
• Executive Go/No-Go Signoff
• Master Services Agreement (MSA)
• Data Processing Agreement (DPA) & Data Retention Policy
• SSO & Security Requirements Addendum
• Implementation & Deployment Plan
• Historical Data Import & Migration Acceptance
• Training & Enablement Plan
• Service Level Agreement (SLA) & Support Onboarding
• Purchase Order / Billing Authorization
• Change Order / Scope Amendment

• Adoption & Usage Review
• Forecast Accuracy Review
• Customer Retrospective & Learnings
• Operational Handover: Support & Enhancement Channel
• Executive Success Review & Expansion Decision

• Create the shared Slack/Teams channel and invite cross-functional participants (ops, IT, revops, vendor).
• Capture at least one clear success story and two metrics to include in the executive summary.
• Agree on how retro outputs will be communicated to the broader sales organization.
• Publish the retrospective report (issues, root causes, prioritized backlog) to the shared project space.
• Assign engineering/ops owners to the top two product/process requests and schedule scoping sessions.
• Update onboarding and training materials to reflect agreed process changes.
• Draft the one-paragraph success story and get rep sign-off for quoting.
• Roles, Governance & RACI
• Agree on a single shared support channel and documented SLAs for responses and resolutions.
• Put in place an enhancement intake process with scoring criteria and a monthly prioritization cadence.
• Assign operational owners and publish the RACI for day-to-day ops and escalations.
• Schedule the recurring monthly enhancement review and the weekly support triage.
• Opening & Objectives
• Draft and publish the SLA document (response/resolution times and triage guidelines).
• Set up the enhancement board (Jira/Trello) and populate initial backlog items from the retrospective.
• Schedule recurring monthly enhancement prioritization meeting and weekly ops triage.
• Executive Summary & Key Metrics
• Obtain executive sign-off to expand from pilot to production (or a defined next state if not approved).
• Secure budget and executive sponsor commitments for the agreed expansion timeline.
• Align on any contractual changes or procurement steps required to proceed.
• Confirm the high-level rollout plan and milestone owners for the expanded deployment.
• Prepare and circulate the final pilot executive summary and ROI deck within 48 hours.
• If approved, issue change order/contract amendment and schedule the expansion kickoff meeting.
• Assign executive sponsor and confirm weekly sponsor updates until production launch.
• Publish the approved rollout timeline and initial milestone owners to the project workspace.
• Confirm adoption meets the pre-defined threshold for the pilot or identify the shortfall amount.
• Identify and assign owners for the top 3 adoption blockers to be remediated within the next sprint.
• Capture at least two rep success stories to use in internal comms and reinforcement.
• Agree on a follow-up cadence for adoption metrics (weekly check-ins for 30 days).
• Owner assigned to implement top blocker fix (integration/permissions/UX) and report status in 5 business days.
• Schedule two coaching sessions with low-adoption reps and document attendance.
• Publish an internal one-page tip sheet highlighting quick wins and how auto-capture reduces admin time.
• Enable or tune data-completeness alerts and share dashboard link with managers.
• Opening & Metrics to Validate
• Confirm whether forecast accuracy target was met and quantify improvement versus baseline.
• Identify the top 2–4 root causes for forecast variance and assign owners for each.
• Agree on specific calibration or process changes to be implemented within the next 2 weeks.
• Establish the cadence and metrics for ongoing accuracy monitoring (e.g., weekly variance report).
• Apply agreed forecast score threshold adjustments and document expected impact.
• Create a weekly variance report template and schedule automated delivery to managers.
• Assign managers to coach the three reps with largest variance and capture improvement outcomes.
• Log calibration changes in the change register and set reminder to re-evaluate in two cycles.
• Purpose & Ground Rules
• Produce a prioritized backlog of improvements derived from pilot learnings with owners and timelines.
• Assign owners for process changes and product requests and agree on delivery windows.
• What Worked — Evidence & Impact
• Business Impact & ROI Update
• Baseline vs Pilot Comparison
• Support Channels & SLAs
• Adoption Metrics Snapshot
• Risks, Open Items & Mitigations
• Behavior Deep-Dive
• Deal-Level Variance Analysis
• What Didn't Work — Symptoms & Evidence
• Enhancement Intake & Prioritization
• Model / Confidence Score Calibration
• Root Cause Mapping
• Release Cadence & Communication
• Decision & Resourcing Ask
• Qualitative Feedback from Reps