Gong + Momentum forecast augmentation (L4)

Layer Gong\'s conversation-intelligence sentiment + Momentum\'s structured MEDDPICC autofill into your forecast model. Replace the rep-call-on-Friday with an AI-generated forecast that reps adjust, not author. Forecast accuracy +20-30 points typical.

WORKFLOW1Pipe Gong + Momentum sign…ls into the warehouseSnowflake2Build the augmented score…in dbtdbt3Surface the AI forecast i… the rep's SFDC viewSalesforce4Run forecast as "AI-first… rep adjusts"Manual
4 steps, in order, with the tool that owns each one.
Adoption ladderSix levels from Starter to Rebuilt. This item sits at level 4.L1 StarterOne tool, no workflow changeL2 AssistedAI drafts, humans approveL3 IntegratedWired into CRM and SlackL4 OrchestratedMulti-step, owned, measuredL5 AutonomousAgent runs, human auditsL6 RebuiltThe process itself changes
This playbook belongs at L4 Orchestrated. Running it above your level is how pilots stall.
Measures of successforecast accuracy (commit vs actual); rep forecast-prep time; quarter-end surprises >10%PROVE IT WORKEDforecast accuracy (commit vs actual)rep forecast-prep timequarter-end surprises >10%

The steps

  1. 01

    Pipe Gong + Momentum signals into the warehouse

    Tool: Snowflake

    Use Fivetran/Airbyte to land both Gong (call sentiment, topics, talk-ratio, competitor mentions) and Momentum (MEDDPICC field history, deal updates per call) into Snowflake/BigQuery alongside Salesforce opportunity data. The history matters, you want a snapshot table, not a current-state overwrite. Owner: data eng. Pitfall: only landing current state, you can't train a forecast model on "right now" data. DoD: weekly snapshot table of (deal_id, week, all_signals) running for >12 weeks of history.

  2. 02

    Build the augmented score in dbt

    Tool: dbt

    Write a dbt model: base score = SFDC stage + amount + close date. Augmentations: Gong sentiment trend (last 3 calls), MEDDPICC completeness %, days since last contact decision-maker, # of distinct contacts engaged, competitor mention frequency. Output: a 0,1 "win probability" per open deal. Validate against the last 4 quarters of closed-won/closed-lost data. Owner: analytics eng. Time: 2 weeks for v1. Pitfall: shipping v1 without holdout backtest, you'll surface a worse forecast than the manager's gut. DoD: model beats baseline (SFDC stage alone) on holdout by >15% on F1 score.

  3. 03

    Surface the AI forecast in the rep's SFDC view

    Tool: Salesforce

    Add a custom field on Opportunity: "AI Win Probability" + "Top 2 reasons." Reps see it but can override with a written reason. Track override rates by rep, reps who override a lot become the focus of coaching. Owner: SFDC admin. Pitfall: hiding the AI forecast in a separate tool, reps won't look at it. DoD: every open deal has AI score + reasons visible in the standard opportunity layout.

  4. 04

    Run forecast as "AI-first, rep adjusts"

    Tool: Manual

    New Friday ritual: the AI forecast is the starting number. Reps spend 20 min adjusting (not authoring), documenting each adjustment with a reason. Manager reviews adjustments, not the underlying number. Quarter close: compare AI forecast at week 1, week 6, week 13 vs actuals. Owner: VP Sales. DoD: by quarter 2 of running this, AI forecast at week 6 is within 8% of actual; rep-overridden numbers are tracked and graded.

Tools in this playbook

Next playbooks

Unfamiliar terms are defined in the AI and Revenue Dictionary. Related frameworks live in the framework library.

Share this playbook

Posting to Instagram or TikTok? Copy the link, it carries the title, summary and share image.

Arrives weekly by email. Free. Unsubscribe anytime. By subscribing you agree to our Privacy policy and Terms. We never sell or share the list.