How Do I Build a Forecast Dashboard in Gong in 2027?

This vs. the common alternatives

Most RevOps teams building a forecast in 2027 are choosing between four real options, and it's worth being honest about what each one actually does before you commit engineering and training hours to Gong.

Native CRM forecasting (Salesforce Collaborative Forecasts or HubSpot's forecast module) is the default because it's already paid for. It rolls up Amount, Close Date, and Stage into a forecast view with almost no setup. The problem is that it trusts rep-entered data completely — a deal sits at "Commit" because a rep typed that, not because any behavioral signal supports it. Native CRM forecasting works fine for simple, short-cycle motions with 3-5 stakeholders and a single decision-maker. It breaks down once cycles stretch past six months and buying committees grow past eight or nine people, because nothing in the CRM captures whether the champion has gone quiet or whether procurement has actually engaged.

Clari is the closest true competitor to a Gong-built dashboard. Clari specializes in aggregate, multi-source predictive forecasting — it pulls from your CRM, email, calendar, and (via integration) Gong itself to produce a rollup forecast with variance analysis across the whole funnel, not just deal-level risk. Clari is usually the stronger choice when your priority is exec-level roll-up accuracy across multiple business units or product lines, and it typically carries a higher per-seat cost than adding a Gong dashboard to an existing Gong Revenue Intelligence subscription. Many RevOps orgs run both: Gong's Deal Health Score and risk flags feed into Clari via API as one input among several, rather than picking one exclusively.

Manual spreadsheet/Excel forecasting is still common at smaller shops and is worth naming honestly: it is flexible, requires no new tooling, and lets a sales leader apply judgment calls that no dashboard can encode. But it's manual-update-dependent, easy to game (a rep can hide a slipping deal for weeks), and has zero connection to what was actually said on a call. Teams using it typically spend 3-6 hours per rep per week reconciling numbers before a forecast call — time a signal-based Gong Dashboard largely eliminates because the numbers refresh from call data automatically.

Other conversation-intelligence platforms (Chorus by ZoomInfo, Clari Copilot, Avoma) compete directly with Gong on the call-analysis layer. The meaningful differences by 2027 are less about whether they can transcribe and score a call — most can — and more about depth of the forecast module itself: how configurable the risk formulas are, how well the tool maps to a specific qualification framework like MEDDPICC or BANT, and how tightly the dashboard integrates back into the CRM object your reps already live in. If your team already has Gong seats for call recording and coaching, building the forecast dashboard inside Gong avoids a second data source and a second login; if you're choosing a platform from scratch purely for forecasting, that decision should weigh price per seat, existing CRM integration depth, and whether your team's sales motion is short and transactional (favoring simpler CRM-native forecasting) or long and multi-threaded (favoring Gong or Clari).

The honest trade-off: Gong wins on capturing *why* a deal is at risk (sentiment, silence gaps, competitor mentions, stakeholder engagement); native CRM wins on simplicity and zero incremental cost; Clari wins on cross-source aggregate accuracy at the portfolio level; spreadsheets win only when deal volume is low enough that a human can hold the whole pipeline in their head.

How to choose between them

The decision usually comes down to five factors: deal cycle length, buying committee size, whether calls are already being recorded in Gong, budget for a second forecasting layer, and how much the team already distrusts stage-based forecasting. Walking through those in order gets you to a defensible answer faster than a feature-by-feature bake-off.

Start with cycle length and committee size, because those two variables predict almost everything else. If your average enterprise deal runs 9-18 months and pulls in 11-14 stakeholders — in line with the buying-committee growth widely reported by Gartner and McKinsey in recent years — stage-based CRM forecasting is structurally unreliable, because a "Stage 4: Proposal" deal can mean completely different things depending on how many of those stakeholders have actually engaged. That's the scenario where a Gong-built Dashboard earns its cost. If instead your motion is transactional, sub-90-day, and single-threaded, the added complexity of call-signal forecasting is usually not worth the build time, and native CRM forecasting stays the right default.

Next, check whether Gong is already your call-recording system of record. If reps are already logging the majority of calls into Gong, building the Forecast dashboard there is close to free — you're reusing data you already paid to collect. If your organization uses a different conversation-intelligence tool for recording, migrating call data just to build a forecast view in Gong rarely justifies the switching cost; build the dashboard in whichever platform already holds the transcripts.

Budget and org maturity decide the Gong-versus-Clari question specifically. If you need one signal-based forecast layer and Gong is your only intelligence platform, build it directly in Gong using the steps below. If you're forecasting across multiple business units, multiple CRMs, or need historical variance modeling that spans quarters, Clari's aggregate model is worth the extra spend, with Gong's Deal Health Score exported into it as one input.

The one scenario that overrides all of this: if your team has run stage-based forecasts for two or more consecutive quarters with accuracy below roughly 70-75%, that alone justifies building a signal-based Gong dashboard even in a shorter-cycle business, because the cost of a missed forecast to leadership planning usually exceeds the build cost within a single quarter.

Costs, timelines, and expected impact

Building a forecast dashboard inside Gong is not a separate purchase if your organization already licenses Gong Revenue Intelligence — the Forecast module, Dashboards, Signals, and predictive risk scoring are configuration work, not new software. The real cost is RevOps time, not license fees. Budget accordingly rather than treating this as a procurement exercise.

Timeline. A first working version — CRM connection, three custom fields, and the four core tiles (KPI bar, deal list, sentiment trend, forecast-vs-actual) — typically takes a RevOps admin one to two weeks of focused work, assuming Salesforce or HubSpot admin access is already available and field mapping doesn't require a change-management approval cycle. Layering in Signals-based custom metrics (budget-hold detection, competitor mentions, stakeholder-diversity flags) adds another one to two weeks, mostly spent tuning formulas so they don't over-flag. Full team adoption — the point where reps and managers trust the dashboard over their own gut feel — realistically takes a full quarter, because trust in a new forecasting method builds through repeated Monday reviews where the signal-based number turns out to be right, not through a single announcement.

Ongoing cost. Beyond the initial build, plan for roughly 2-4 hours per week of RevOps maintenance: tuning risk-flag thresholds, updating the signal glossary as reps learn new terminology to describe deal state, and reviewing the "Forecast Model Optimization" settings each quarter as close patterns shift. This is meaningfully less than the 3-6 hours per rep per week that manual spreadsheet reconciliation tends to consume — the savings compound across a sales team rather than landing on one RevOps person.

Expected impact. Teams that move from manual stage-based forecasting to a Gong-built, signal-based dashboard commonly report two kinds of gains: a reduction in the manual update cycle (fewer "please update your stage before Monday" chases, since much of the data derives from calls automatically) and improved commit accuracy, because deals get flagged before a slipping signal shows up in a CRM stage change weeks later. The size of that gain depends heavily on how disciplined the team already was — a team with strong CRM hygiene sees a smaller lift than one where forecast accuracy was previously driven mostly by rep optimism. Treat any specific percentage improvement as something to measure in your own pipeline over two full quarters rather than assume from a vendor's marketing number.

Where the cost creeps in. The most common overrun isn't the build — it's Signals sprawl. Teams that create a dozen custom risk formulas in the first month usually end up with a dashboard so noisy that reps stop trusting any single flag. Budget time for pruning as much as time for building: start with three or four high-confidence signals (budget-hold mentions, low stakeholder engagement, sentiment decline in Commit-category deals) and add more only once those have proven reliable across a full quarter.

Implementation and handoff details

The build itself follows a fixed sequence, and skipping steps is the single most common reason a Gong forecast dashboard launches and then gets ignored within a month.

Step 1 — connect and map. In Gong's Admin > Integrations panel, authenticate your Salesforce or HubSpot instance via OAuth. Gong auto-maps Amount, Close Date, Stage, and Owner, but you must manually push three custom fields from the CRM: Forecast Category (Commit / Upside / Pipeline / Omitted), Deal Health Score (a 1-10 scale, usually calculated against MEDDPICC or your own qualification framework), and Buying Committee Size. If your CRM doesn't already have a Forecast Category picklist, create one before touching Gong — without it, Gong cannot calculate a commit total.

Step 2 — build the four core tiles. Create a new dashboard named for the reporting cadence (e.g., a weekly forecast review). Add a KPI bar with Total Pipeline, Commit Amount, Upside Amount, and Forecast Accuracy; add a deal-list table with Deal Name, Amount, Stage, Forecast Category, Deal Health Score, and a Gong-calculated risk flag; add a line chart tracking average call-sentiment score over time for Commit-category deals; add a bar chart comparing forecasted amount to actual closed-won amount by week for the past two quarters, pulled from the CRM's Closed Won stage. This four-tile layout is the minimum viable version — resist the urge to add a fifth or sixth tile before the first four have been used in a live review.

Step 3 — layer in signals. Under the Signals tab, configure custom formulas that turn call transcripts into forecast inputs: a budget-hold flag when phrases like "budget freeze" appear, a competitor-mention flag when a named competitor surfaces, and a stakeholder-diversity flag when engagement clusters in a single department. Add these as columns on the deal-list tile rather than as separate dashboards — the goal is one place reps and managers look, not five.

Step 4 — automate the refresh and handoff. Gong dashboards refresh on a rolling basis (commonly every few hours); set up a Scheduled Report to push a PDF snapshot to RevOps and sales leadership on a fixed weekly cadence, and consider a Slack webhook summarizing commit, upside, and at-risk totals so the numbers reach the team before the meeting, not during it. This is also the point to formally hand the dashboard off: document field mappings, signal formulas, and refresh cadence in a runbook so the dashboard survives a RevOps staffing change, and assign explicit ownership for quarterly threshold tuning.

Step 5 — train and validate. Run a two-week parallel period where reps keep their existing forecast method alongside the new Gong dashboard, then compare in the weekly review which one called deal outcomes correctly. Build a one-page signal glossary defining what each metric means in plain language, and set up automated alerts so a Commit-category deal whose Health Score drops below your team's threshold notifies the rep and manager directly rather than waiting to surface in a Monday review.

Handoff is where most builds quietly fail: a dashboard built by one RevOps person with no documented formulas or ownership tends to decay within two quarters as thresholds go stale and nobody notices. Treat the runbook and named owner as part of the build, not an afterthought.

Related questions

How do I set up call sentiment scoring in Gong for commit-stage deals?

Filter the sentiment-trend tile to your Commit forecast category, then track average call-sentiment score over time. A sustained drop across two or more consecutive weeks is a strong early indicator that a deal is at risk of slipping, even before its CRM stage changes.

Which forecast categories should I map between my CRM and Gong's Forecast module?

Map Commit, Upside, Pipeline, and Omitted directly. If your CRM lacks this picklist, create it before connecting Gong — the Forecast module cannot calculate commit totals without a native Forecast Category field to read from.

How does Gong's predictive risk scoring compare to Clari's aggregate forecasting?

Gong scores individual deals from within-call behavioral signals like sentiment and stakeholder engagement. Clari aggregates across CRM, email, and calendar data for portfolio-level rollups. Many teams export Gong's Deal Health Score into Clari as one input rather than choosing exclusively.

Which MEDDPICC signals should feed a Gong Deal Health Score?

Weight Metrics (ROI mentions on calls), Decision Criteria (buyer language about evaluation requirements), and Economic Buyer engagement most heavily, since these are the qualification elements Gong can most reliably detect from transcripts rather than requiring manual rep entry.

Does a Gong forecast dashboard replace the need for manual pipeline reviews?

No — it changes what the review discusses. Instead of reps reciting stage updates, the Monday review becomes a discussion of why specific deals are flagged at risk, using the Deal Health Score and signal flags as the starting point.

FAQ

How do I connect Gong to Salesforce for forecast data? Go to Gong's Admin > Integrations > Salesforce, authenticate via OAuth, then map your Opportunity object fields (Amount, Close Date, Stage, Forecast Category). Gong syncs on a regular refresh cycle by default; check Salesforce's API settings if you need a faster sync interval.

Can Gong replace my existing forecast tool like Clari? Not entirely. Clari specializes in aggregate predictive forecasting across multiple data sources, while Gong's strength is deal-level risk detection from conversation signals. Most teams that use both export Gong's Deal Health Score into Clari via API rather than picking one exclusively.

What if my CRM doesn't have a "Forecast Category" field? Create a custom picklist field (values: Commit, Upside, Pipeline, Omitted) in your CRM first, then map it in Gong's Field Mapping settings. Without this field, Gong cannot calculate accurate commit totals for the KPI tile.

How do I handle deals with no recorded calls in Gong? Gong can't score silence, so these deals will show a "no signal" state on the dashboard. A common practice is requiring at least one recorded call per week for larger deals, and treating any deal with zero recent calls as elevated risk by default.

Why is my forecast accuracy low even with Gong signals in place? Common causes: your Commit category includes deals where the champion hasn't spoken in weeks, your sentiment threshold is too broad to be meaningful, or your CRM close dates are stale relative to Gong's last-activity data. Re-run the Forecast Model Optimization settings and tighten thresholds.

Does Gong integrate with HubSpot for forecasting the same way it does with Salesforce? Yes, though HubSpot's native forecast module is lighter than Salesforce's Collaborative Forecasting, so you'll likely need to create a custom Forecast Category property in HubSpot before Gong has a field to map to.

Sources

• Gong: Revenue Intelligence Platform Overview
• Gartner: Sales Forecasting Insights
• McKinsey: The B2B Buying Committee Is Growing
• Harvard Business Review: Why Sales Forecasts Fail and How to Fix Them
• Clari: Revenue Forecasting Overview
• Salesforce: Collaborative Forecasting Documentation
• HubSpot: Forecasting in HubSpot
• Forrester: Revenue Operations Research

Related on PULSE

• How Many Attendants Should I Schedule Each Day at My Car Wash?
• How Many Sales Reps Do I Need to Hire for My Logistics Company?
• How Many Salespeople Do I Need to Hire for My Car Dealership?
• How Many Producers Do I Need to Hire for My Insurance Agency to Grow My Book?
• How Do I Figure Out How Many People to Schedule Each Day and at What Times for My Single Store?