Quick check: your current forecast picture

• How would you describe your current process for producing the sales forecast?
• Which metric does your leadership focus on most in forecast reviews? Options: Committed bookings by period, Weighted pipeline total, Best case vs commit, Forecast confidence score, Deal stage counts, Other
• When was the last time you revised your forecast methodology and what prompted that change?
• Tell me about a recent forecast miss that surprised leadership, what unfolded and why it mattered?
• How often do managers augment CRM numbers with spreadsheets or separate reports before presenting a forecast? Options: Always, Often, Sometimes, Rarely, Never

Where forecasts break and who notices first

• What single forecasting failure would make you walk away from a vendor or decide to build this internally?
• Walk me through the last quarter's top three deals that turned into forecast misses and why each changed.
• Who on your team typically spots a deal going off plan first, and what do they do next? Options: Account executive, Sales manager, RevOps / Sales operations, Finance, Customer success, Other
• By how much did those missed deals affect bookings or revenue recognition that quarter? Options: >20%, 10-20%, 5-10%, <5%, Not sure
• If forecast confidence improved by a measurable amount in one quarter, what immediate business decisions would that unlock?

Who signs off and who quietly resists

• Who would block a change to how forecasts are produced, and why would they do that? Options: VP of Sales, CRO/CEO, CFO/Finance, Head of RevOps, IT/Security, Sales managers, Other
• Which stakeholders must see identical numbers between your CRM and finance systems before you trust a forecast? Options: Sales leadership, Finance, RevOps / Sales operations, Board / CEO, Sales managers, Other
• Describe how incentives or commission rules change what reps record in the CRM.
• When conflicts arise between sales and finance over a number, who adjudicates and what criteria decide the outcome?
• What single decision by any stakeholder would stop a pilot from progressing to a go or no-go?

Why reps do or do not keep the CRM honest

• If your reps could be honest, what would they say they dislike most about logging deals in your current tools?
• On average, how many reps complete required CRM fields before manager review? Options: Nearly all reps, Most reps, About half, A few, Almost none, Not tracked
• Tell me the common triggers that lead managers to prioritize data-quality coaching over pipeline development coaching.
• Imagine the CRM reduced clicks and manual steps by about 30 percent, would reps be more likely to log activity without prompting? Options: Yes, Maybe, depends on training, No
• Name the one barrier that, if removed, would cause most reps to adopt the platform within 30 days.

Data, systems, and the hidden gates

• Imagine your CRM data were trusted across teams tomorrow, what would change in your planning meetings?
• List the external systems that must be connected for a pilot to prove value and who owns each connection.
• Identify who on your team is the day to day owner of the CRM and who owns API or integration access.
• Estimate the percentage of opportunity records that have accurate close dates and stage history today. Options: >90%, 70 to 90%, 50 to 70%, <50%, Not sure
• Are there legal, security, or compliance reviews that would prevent API access or data export during a pilot? Options: Yes, No, Not sure
• Identify the integration or data gap that would prevent running a 30 day pilot with three reps.

The pilot that will prove whether this sticks

• Suppose the 30 day pilot shows rep adoption but not immediate forecast accuracy improvement, would you still consider proceeding to purchase? Options: Yes, if adoption is high, Depends on reasons for accuracy gap, No, accuracy must improve first, Unsure
• List the acceptance criteria that would convince finance and sales leadership to sign after the pilot.
• Please name who will select the three to five reps for the pilot and the desired mix of ACV, tenure, and territory.
• Describe which metrics and thresholds you will use to measure rep adoption during the pilot.
• Should the pilot reach targets early, can contracting be accelerated and who would approve that? Options: Yes, Sales leadership, Yes, Finance, Yes, RevOps, No, needs full procurement, Not sure
• Name the final signoff authority if the pilot meets agreed success signals and the target signing window.

Who else is on your short list and why

• Explain what would have to be true about your current approach for you to stay with it instead of switching to a new platform.
• Provide the vendors or internal options you are actively evaluating or have recently evaluated.
• For each alternative, what is the single strength that makes your team consider it?
• Please name who internally has proposed building a solution instead of buying and an estimate of the resource commitment that would require.
• Pinpoint the single must have that would make you choose one vendor over others.

Readiness, owners, and timeline kill switches

• Point to the one readiness issue most likely to derail the engagement and explain why it would have that effect.
• Provide the integration endpoints required for a pilot to succeed and indicate whether API credentials are available now.
• Indicate who will own SSO and data privacy approvals and the typical length of their review cycles.
• Estimate how much historical data must be migrated for the pilot to be meaningful, expressed as opportunity records and active accounts.
• Are there regulatory or contract clauses that will prevent moving contact or opportunity data into the platform during a pilot? Options: Yes, No, Need legal review
• Should an integration owner refuse API access, what fallback would you accept and who would make that decision?

Agreement signals and next practical steps

• Assuming the pilot proves the numbers, what would stop you from signing that week?
• Indicate the documents, approvals, or procurement steps that must be completed before a PO can be issued.
• Confirm the people who need to be included in a go no go meeting at pilot close to avoid delay.
• Give the expected timeline between pilot completion and enterprise rollout if leadership approves. Options: 2 to 4 weeks, 1 to 2 months, 3 months, 3 to 6 months, Depends on integrations
• Do you have a target budget band or a not to exceed amount for this initiative? Options: Specific amount (enter separately), Range provided by procurement, No set budget yet, Undisclosed
• Finally, what would make you want to pause discussions after the pilot even if the metrics look good?

• Solution Experience: Model Your Deals and Quotes

• Confirm the current state and its cost
• You confirm the demonstrated deal and quote workflows eliminate the spreadsheet reconciliation and manual quote rework described in Discovery.
• Provide the list of 3 to 5 pilot reps and three active deals to run during the 30-day pilot.
• Proof: Model a live multi-stakeholder deal end to end
• You agree that activity capture as shown will materially improve forecast confidence for weekly rollups.
• Provide the integration dependency checklist, including ERP fields required for booking reconciliation and the SSO owner contact.
• Proof: Demonstrate quoting and approval using your sample quote
• Pre-configure the two showcased deals in the platform to match the provided scenarios and deliver the pre-configured demo before the session.
• You accept the proposed pilot entry criteria and agree to provide the pilot reps and sample deals needed to start the 30-day evaluation.
• Run the sample forecast on the provided deals and deliver the accuracy comparison versus your current spreadsheet forecast before the follow-up session.
• Proof: Show activity capture and forecast impact
• Integration and pilot readiness check
• Validate: Is this what you meant when you said you needed reps to adopt the system without being forced?

• Solution Experience: Model Your Deals and Quotes
• Solution Experience Deck
• Solution Brief

• meeting
• slides
• document

• Import and Clean Historical CRM Records
• Configure Pipeline Stages and Exit Criteria
• Build Multi-Stakeholder Opportunity Model
• Configure Quoting and Approval Workflows
• Integrate Email and Calendar Auto-Capture
• Integrate Telephony/Dialer
• Configure Territory and Account Assignment
• Activate Lead Scoring and Routing
• Enable Campaign Attribution and Nurture Sequences
• Configure Forecasting and Pipeline Analytics
• Set Role-Based Permissions and Access Controls
• Integrate ERP for Bookings Sync
• Train Sales Reps and Managers on CRM Workflows

Import and Clean Historical CRM Records

• Count the number of contact and account records to migrate from your current CRM? Options: Less than 1,000, 1,000-10,000, 10,000-50,000, More than 50,000, Unknown / estimate
• Preserve which fields must remain on opportunity records (for example close date, product line, quote ID)?
• Require deduplication by which primary key during import (for example email address, phone number, company domain)? Options: Email address, Company domain, Phone number, Custom key (provide mapping), No deduplication required
• Confirm the acceptable data quality thresholds for migration (for example 95% valid email, 90% complete addresses)? Options: 95%+ valid email and 90%+ completeness, 90% valid email and 80% completeness, Custom threshold (describe), No formal threshold
• Provide a list of legacy custom objects or tables that must be migrated (for example custom quote lines, contract terms).
• List any privacy or regulatory constraints that apply to migrated records (for example GDPR consent flags, data residency, retention periods). Options: GDPR / EU data residency, CCPA / US privacy, Industry-specific (specify), No special constraints

Configure Pipeline Stages and Exit Criteria

• Define how many unique sales pipelines must be configured (for example new business, renewals, expansion). Options: 1, 2-3, 4-6, 7 or more
• Model the exact stage names and current win/loss exit criteria you use today.
• Supply details of any stages that require automated gating or manual approvals before progression. Options: No gating, Single-level approval, Multi-level approval, Custom gating logic (describe)
• Need the exit criteria to reference specific artifacts (for example signed SOW, purchase order number)? Options: Yes - list artifacts, No - stage-based only, Partial - some stages require artifacts
• Assign ownership for stage changes and who will validate stage transitions (for example AE, sales manager).
• Set the aging thresholds that should trigger alerts for deals stuck in a stage (for example 14 days, 30 days). Options: 7 days, 14 days, 30 days, Custom (specify)

Build Multi-Stakeholder Opportunity Model

• Describe the typical stakeholder mix in a deal (for example procurement, technical buyer, economic buyer).
• Detail which relationship types must be tracked on the opportunity (for example decision maker, influencer, blocker). Options: Decision maker, Technical approver, Procurement, Champion, Blocker, Other (specify)
• Map whether you need custom contact roles or multi-contact voting to capture approvals. Options: Standard contact roles, Custom contact roles required, Multi-contact voting required, Not required
• Designate the artifact that proves stakeholder consensus (for example signed technical acceptance, pilot approval email).
• Name which engagement types should be surfaced in the opportunity timeline (for example product demo, POC kickoff, executive briefing). Options: Demos, POC/Trial events, Pricing review, Executive meetings, All of the above, Other (specify)
• State who will maintain contact-role mappings during the pilot and after go-live. Options: RevOps / Sales Ops, Sales Manager, Individual AE, Shared team responsibility, Other (specify)

Configure Quoting and Approval Workflows

• Include the quote templates and required line-item attributes that must be available in the quoting module.
• Exclude any quote types from automation (for example one-off professional services that use manual SOW). Options: No exclusions, Professional services SOWs, Enterprise negotiated deals, Other (specify)
• Store required approval thresholds for discounts and contract values (for example discount >10%, contract > $50k).
• Record how quote revisions should be versioned and where they will be stored on the opportunity record. Options: Auto-version stored on opportunity, Store in external proposal tool, Manual versioning by team, Other (specify)
• Declare the integration endpoints required for quote-to-contract handoff (for example proposal tool ID, e-signature record key).
• Schedule who will own quote template updates and pricing approvals during implementation. Options: Product pricing team, Finance, RevOps, Sales leadership, Other (specify)

Integrate Email and Calendar Auto-Capture

• Plan which email domains and calendar systems should be connected for auto-capture. Options: G Suite / Google Workspace, Microsoft 365 / Outlook, Other (specify), Multiple providers
• Appoint whether capture rules should exclude personal or non-sales activity and give examples. Options: Exclude personal domains, Exclude calendar categories like 'Personal', No exclusions, Custom rules (describe)
• Select any retention or compliance constraints for captured emails and calendar events (for example 7-year retention, legal hold). Options: 7 years, 3 years, Legal hold only, Custom retention (specify)
• Segment the mapping rule to link captured events to opportunities (for example by contact email, meeting subject containing opportunity ID). Options: Match by contact email, Match by calendar event subject (opportunity ID), Manual association by rep, Hybrid rules
• Enable admin access details and consent workflow for mailbox authorizations.
• Surface any shared mailboxes that must be auto-captured and how they map to teams (for example sales@, renewals@).

Integrate Telephony/Dialer

• Flag which telephony or dialer providers your reps use that must integrate.
• Note whether call recording metadata and transcripts need to be stored on opportunity timelines. Options: Store metadata only, Store metadata plus transcripts, Do not store recordings, Legal hold only
• Identify the attribution rule for calls (for example match by caller number, by CRM contact phone field). Options: Match by caller phone, Match by contact phone field, Match by meeting/opportunity ID, Manual association
• Choose any regulatory recording requirements for your operating regions (for example consent, retention policies). Options: Consent required (notify), One-party consent, No recording allowed, Other (specify)
• Specify the initial number of user lines that require connector setup for the pilot. Options: 1-3, 4-10, 11-25, 26-50, More than 50
• Establish who will manage dialer credentials and SIP trunk details during integration. Options: IT / Telecom, RevOps, Third-party vendor, Other (specify)

Configure Territory and Account Assignment

• Outline how territories are currently defined (for example geography, vertical, ARR band).
• Document whether account reassignment should be automated when quotas change or reps depart. Options: Automate reassignment, Manual reassignment only, Hybrid - automate with approval
• Indicate priority rules when multiple reps qualify for an account (for example ownership, last touch). Options: Ownership wins, Last touch wins, Weighted scoring, Manager override
• Count the attributes that should drive territory assignment (for example postal codes, industry code, ARR).
• Preserve who will own territory rule changes and the approval workflow. Options: RevOps, Sales Leadership, Regional Managers, Hybrid (specify)
• Require the cadence for account rebalancing (for example quarterly, annually, on-demand). Options: Quarterly, Biannual, Annual, On-demand

Activate Lead Scoring and Routing

• Confirm which lead attributes and behavioral signals should feed the lead scoring model (for example page views, trial signups).
• Provide whether separate scoring profiles are required per lead source or market segment. Options: Single global profile, Separate by source, Separate by market/segment, Mixed approach
• List the routing options for scored leads you prefer (for example round-robin, region-based, rep capacity). Options: Round-robin, Region-based, Capacity-based, First-response, Other (specify)
• Define which lead sources should be excluded from automatic routing (for example internal referrals). Options: Internal referrals, Partner leads, High-touch enterprise leads, No exclusions
• Model how frequently scores should recalculate (for example real-time, hourly, nightly batch). Options: Real-time, Hourly, Nightly batch, Daily summary
• Supply who will approve initial scoring weights and ongoing adjustments. Options: RevOps, Marketing Ops, Sales Leadership, Cross-functional committee

Enable Campaign Attribution and Nurture Sequences

• Need the list of campaign channels and tracking parameters you use for attribution (for example UTM source, paid channel ID).
• Assign which attribution model you require (for example multi-touch, first-touch). Options: Multi-touch, First-touch, Last-touch, Custom model (specify)
• Set the nurture tracks and enrollment triggers you need (for example no response after demo, trial expiration).
• Describe the assets required for nurture sequences (for example email templates, landing pages).
• Detail who will own campaign tagging and UTM conventions. Options: Marketing Ops, Demand Gen, RevOps, Shared responsibility
• Map how campaign-sourced opportunities should be flagged for reporting and finance reconciliation. Options: Tag field on opportunity, Use campaign-opportunity junction, Custom flag on opportunity, Other (specify)

Configure Forecasting and Pipeline Analytics

• Designate how forecast categories should align with your financial buckets (for example commit, best case, upside).
• Name whether weighted pipeline calculations should use historical win rates by stage and product. Options: Yes - by stage, Yes - by product, Yes - combined, No - use manual weights
• State the forecast accuracy acceptance threshold for pilot validation (for example within 5% of finance). Options: Within 2% of finance, Within 5% of finance, Within 10% of finance, Custom (specify)
• Include which pipeline risk signals should surface on deal cards (for example no activity in 14 days, no champion assigned). Options: No activity in 14 days, No champion assigned, Unverified decision criteria, Low engagement score, All of the above
• Exclude any inputs from automated forecast weighting (for example manager overrides) and specify which. Options: Manager overrides, Manual adjustments, Custom exceptions, None
• Store the required manager report cadence and format for forecast rollups (for example weekly dashboard, PDF export). Options: Weekly dashboard, Weekly PDF, Monthly rollup, Ad-hoc exports

• desired_state
• current_state
• stakeholders
• gaps
• success_criteria
• decision_readiness
• desired_state
• decision_readiness
• current_state
• success_criteria
• gaps
• stakeholders
• desired_state
• success_criteria
• stakeholders
• gaps
• current_state
• decision_readiness
• decision_readiness
• decision_readiness
• decision_readiness
• decision_readiness

• Subscription Order Form
• Master Services Agreement (MSA)
• Statement of Work (SOW)
• Pilot Acceptance & Go/No‑Go Agreement
• Data Processing Agreement (DPA)
• Regulatory Compliance Addendum
• Change Order Agreement
• Service Level Agreement (SLA)

• Go-live Health Check (weeks 1-4)
• First Measurement Review (weeks 4-10)
• Acceptance Gate Review (around day 90)
• Monthly Coaching and Enhancement Triage (monthly, first 6 months)
• Quarterly Success Business Review

• Keep the enhancement backlog prioritized and specific with clearly defined next steps.
• Update the training and enablement plan to address identified adoption gaps and circulate to stakeholders.
• Restate acceptance criteria and numeric targets
• Acceptance decision recorded with pass/fail status for each numeric criterion in Live Pilot Evaluation.
• Remediation plan defined for any failed criteria with owners and completion dates.
• Publish the formal acceptance record and the dataset used for the decision to the shared workspace.
• Create a remediation tracker for any failed criteria with owners and delivery deadlines.
• Coaching outcomes review
• Ensure CRM data completeness rate and rep adoption rate improve through targeted coaching and prioritized fixes.
• Re-confirm success criteria and owners
• Add prioritized enhancements to the delivery backlog with target sprint or delivery windows.
• Schedule focused coaching sessions for reps below the agreed adoption threshold.
• Quarterly metric trends
• Confirm whether forecast accuracy % and time-saved on data entry per rep are sustained against targets recorded in Live Pilot Evaluation.
• Resolve or agree escalation paths for any persistent blockers impacting the target metrics.
• Publish a quarterly realization report showing metric trends, enhancements delivered, and outstanding risks.
• Open escalation actions for unresolved integration or data issues with target resolution dates.
• Deployment and a sampled set of migrated records validated as complete or a remediation plan agreed.
• Early adoption signals reviewed and any critical blockers assigned owners with due dates.
• Legacy CRM wind-down path agreed, with archival or read-only timeline recorded.
• Publish a go-live health summary that lists open issues, owners, and target resolution dates.
• Schedule any remaining data extraction or archival windows required to complete legacy system wind-down.
• Present first measurement data
• Identify root causes for any shortfalls in rep adoption rate and CRM data completeness rate and agree corrective actions.
• Confirm timeline and required evidence to proceed to the acceptance gate documented in Live Pilot Evaluation.
• Deliver a remediation plan with clear owners, milestones, and data checkpoints for the next measurement period.
• Diagnose root causes for gaps
• Deployment and migration validation
• Enhancement roadmap and delivery status
• Enhancement backlog triage
• Present outcome data against each criterion
• Early adoption signals and usage patterns
• Agree corrective actions and timelines
• Open issues and ticket burn-down
• Document pass/fail and formal acceptance decision
• Operational risk and integration health
• Agree next quarter sustainment plan
• Legacy system wind-down status
• Agree remediation plan for any failed criteria
• Confirm readiness for acceptance gate
• Short-term remediation and quick wins
• Blockers and immediate remediation actions