Best Forecasting Tools for Renewal, Expansion and Churn Forecasts (2026)
Compare Weflow, Clari, Gong, Salesloft, and Aviso for renewal, expansion, and churn forecasts.

If your CSMs and account managers outnumber your new-logo reps, you probably know this setup. New business runs in the forecasting tool. New business runs in the forecasting tool, while renewals still live in Salesforce or a spreadsheet.
That's because most forecasting tools assume one close date, one amount field, one stage weighting, and the Salesforce role hierarchy. Renewals break all four.
So we put five tools through one test: can renewal, expansion and new business each run as its own forecast, with its own date field, amount and churn logic, stage conversion, owners, and targets, and still roll into one net number without a rebuild?
Here's the short answer:
- Weflow Deal Intelligence & Forecasting fits Salesforce mid-market teams that want renewal and expansion as separately configured forecasts, with CSMs in the roll-up and a published seat price.
- Clari fits large enterprises with mature roll-ups that need an account-level view of existing customers.
- Gong fits teams already on Gong Foundation that want a board per motion with a built-in accuracy report.
- Salesloft fits its own engagement customers, especially where existing-customer revenue is variable or consumption-based.
- Aviso fits large enterprises with usage-based revenue or several CRMs.
That said, every one of these tools, ours included, sends you back to a spreadsheet somewhere. Below you get the capability-by-capability comparison, a section per tool, side-by-side pricing, and an answer to "should I just finish my own build?"
How Weflow, Clari, Gong, Salesloft and Aviso compare
We compared the tools on the nine capabilities that decide a renewal forecast, and they differ most on four: whether each motion is a truly separate forecast, whether accuracy is computed in the product, how data reaches BI tools and AI assistants, and whether prices are published.
| Capability | Weflow | Clari | Gong | Salesloft | Aviso |
|---|---|---|---|---|---|
| Multiple forecast types | Parallel setups per motion, each with its own amount field, date field, stages and targets; no consumption forecasting | Account-based forecast for existing customers beside the opportunity forecast; tied to the Salesforce hierarchy | Separate board per motion with its own filters, metrics and targets; formula metrics such as net retention | Segments for new business, renewals and upsells, plus account-based Pace forecasting | Segments of one forecast (new, upsell, renewal) plus consumption forecasting; separate per-motion fields not documented |
| Forecast submissions and roll-ups | Baseline and best case tied to named deals; custom hierarchy where one person sits on several teams | Mature roll-up by opportunity owner; sub-totals need placeholder users; a call is a number with notes | Submissions per forecast category with notes; hierarchy follows Salesforce | Hierarchy from the Salesforce Manager field, eight levels; one quota period active at a time | Commit, best case and most likely on Aviso's own hierarchies |
| AI forecast prediction | Low/mid/high range built per configuration; needs six months of history | Lands close for mature users; useful after 12 to 18 months; looks three months ahead | Transparent projection ("See the math"); needs 400 opportunities and 150 won across four quarters | New business in the current quarter only; needs four quarters of data | AI forecast built from deal WinScores with explained factors |
| Forecast accuracy tracking | Built in per rep, manager and team, no setup | Week-by-week call history; no accuracy measure computed | Built-in per-person accuracy report | Measured outside the product via CSV export to BI | Commit accuracy per AE plus an exportable forecast audit trail |
| Opportunity snapshots | Automatic every few hours; 12 months imported at install | Time Series Data Hub snapshots opportunity, account and activity data | Weekly history from CRM field history; up to five quarters backfilled on request | Week-over-week movement in Inspect; no documented snapshot store | Own time-series copy of the CRM, six to eight quarters |
| Integrations with other tools | Salesforce, Google, Microsoft, Zoom, Slack, Outreach dialer; BI via API; no native warehouse connector | Salesloft data layer syncs Salesforce, Dynamics, Snowflake, Databricks and more | About 450 integrations and partner solutions | Data layer syncs to Snowflake and Databricks; Zoom, Teams, Meet, Webex and five dialers | More than 200 claimed connections |
| Access from AI assistants (MCP) | Read-only connector returns forecast calls, pipeline metrics, transcripts and playbooks | Three narrow servers; the Forecast server has no deal-level data | Three record-scoped tools; insights, not transcripts; metered credits | Read-only beta, paid add-on, no transcripts | No MCP for external assistants |
| Raw data access outside the tool | REST API bulk export in JSON or CSV to warehouses and BI | REST and Export APIs; Snowflake and Databricks via Salesloft | API capped at 3 calls a second and 10,000 a day; Data Cloud sold separately | Self-service REST API including transcripts; Snowflake and Databricks sync | No public API or warehouse feed; file exports only |
| Pricing | Published: $39 per user per month for Deal Intelligence & Forecasting; 10-user minimum | No published seat price; quote-only | No published price; Forecast is an application on top of Foundation | No published seat price; forecasting is an add-on | Custom proposals; agent work at $1 to $1.50 per outcome |
Why your new-business forecast can't carry renewals and churn
Forecasting tools were built for new-logo bookings: one pipeline, close date, stage probability, owner hierarchy. Renewal economics differ on every one of those points.
| What a new-business forecast assumes | What a renewal forecast needs |
|---|---|
| Deals land in the period by close date | Renewals land in the period by renewal or contract date |
| One positive amount field per deal | Churn and contraction as negative numbers, pulled from closed-lost deals and downsells |
| Stage probability rises as a deal advances | Renewals sit in early stages and still close at high rates |
| One rep owns the deal in the role hierarchy | CSMs and AMs own the number, often on two teams at once |
| A one-to-four-quarter horizon fits the cycle | The customer's real decision happens much earlier than the renewal date |
The date problem comes up in almost every conversation we have with renewal teams. As one buyer put it:
When I'm doing the renewal forecast, I don't care what my close date is. What I want to track is renewals that are due in this quarter and how we are doing against those.
Stages cause a similar problem. If you load a year of renewals at stage one, and they close around 95% of the time, a stage probability set for new business underweights them badly. Each motion needs its own conversion history.
When a tool ties the forecast to one amount field and the Salesforce role hierarchy, you get workarounds:
- Placeholder users to create sub-totals
- Helper columns to assemble churn
- No way to separate a renewal and an expansion opportunity on the same account
As a result, renewals often stay "next on the list" for years while new business gets set up first. We hear this on calls all the time:
Some of the teams are using Clari forecasting but when we talk to the renewals team right now it's just in Salesforce again just was never implemented.
There's also one problem no tool fixes: customers on multi-year contracts signal they're leaving one to two years before the renewal, while a forecast looks one to four quarters ahead.
By the time the renewal enters the forecast, the decision is often made. A forecasting tool can model churn, but on its own, it won't warn you early.
The configuration test we ran on every tool
On a feature grid, "supports multiple forecast types" doesn't tell you much, since every vendor ticks that box. What matters is whether each capability works for renewal and expansion without a rebuild.
| Capability | What we checked for renewals and expansion | The demo question |
|---|---|---|
| Multiple forecast types | Separate forecasts per motion, not filters on one | Can the renewal forecast use a different date field and a different amount field from new business? |
| Forecast submissions and roll-ups | CSMs and AMs in the roll-up, with their own targets | Can one CSM carry a renewal and an expansion number, and does it roll into one combined number? |
| AI forecast prediction | A projection trained on renewal history, not new business | How much history does the projection need, and is renewal modeled separately? |
| Forecast accuracy tracking | An accuracy baseline for the renewal number | Is accuracy computed in the product, or exported for me to calculate? |
| Opportunity snapshots | History of how renewals moved, slipped or shrank | Where does pre-rollout history come from? |
| Integrations with other tools | Fit with the stack that already holds renewal data | Which systems connect natively, and which go through the API? |
| Access from AI assistants (MCP) | An assistant can read the submitted renewal forecast | Can Claude or ChatGPT read forecast calls, or only call data? |
| Raw data access outside the tool | BI and warehouse access to the forecast | Is there an API, and what does it cost extra? |
| Pricing | Public seat price and what costs extra | Is the price public, and is forecasting included or an add-on? |
Weflow: Renewal, expansion and new business as separate forecasts
Weflow is the Revenue AI Orchestration platform for sales, customer success, and RevOps teams. Forecasting lives in Weflow Deal Intelligence & Forecasting, alongside pipeline management and deal intelligence.
Quick specs:
- Works exclusively with Salesforce
- Salesforce opportunity history imported at install, 12 months by default
- No implementation fees
How Weflow runs renewal and expansion as their own forecasts
Weflow lets you run several forecast setups in parallel, each with its own amount field, date field, stages, cadence, targets and forecast calls. This matters for renewals because a blended forecast hides whichever motion is actually failing.
Here's what a renewal setup looks like in practice:
- Amount field: Your renewal revenue field. Any opportunity currency field works, not only the standard Amount.
- Date field: Contract start date instead of close date, so the forecast counts the renewals due in the period.
- Permanent filter: Record type or opportunity type set to Renewal, configured once by the admin.
- Churn formula: One condition group over Closed Lost, a second over Omitted, and a formula that adds them into a combined churn-and-contraction figure.
- Retention measures: Net or gross dollar retention and renewals due in the period, built the same way as formula columns.
- Target: The churn target goes into target setup beside the formula column.
Click any formula value to see the opportunities behind it, without stacking helper columns.
| Setting | New business | Renewal | Expansion |
|---|---|---|---|
| Amount field | Your new-business revenue field | Your renewal revenue field | Your expansion revenue field |
| Date field | Close date | Contract start date | Close date |
| Permanent filter | Record type or opportunity type = New Business | Record type or opportunity type = Renewal | Expansion type, excluding deals whose net new ARR is negative |
| Stages | Its own stage path and category mapping | Its own stage path and category mapping | Its own stage path and category mapping |
| Targets | Own target, plus the combined quota | Own target, plus the combined quota | Own target, plus the combined quota |
The expansion filter is more important than it looks. Excluding expansion opportunities with negative net new ARR keeps contraction out of the expansion number, so a downsell doesn't quietly drag down what your account managers sold.

A few more pieces close the loop on renewals:
- Each motion gets a tab, plus a combined view. You carry one combined quota and per-motion targets at the same time, so when the quarter misses, you can see which motion missed.
- A configurable renewal-kickoff milestone fires ahead of contract end, and renewal opportunities roll up in their own pipeline view.
- A configuration can forecast on opportunity product line items instead of the opportunity, which helps when one renewal carries several products or multi-year terms that book in different periods.
How Weflow rolls CSM and account manager calls into one number
By default, roll-ups follow the Salesforce role hierarchy. If that doesn't match how you forecast, you can switch on a custom hierarchy in Weflow and arrange teams by drag and drop.
One person can sit on several teams, which covers the CSM who carries both a renewal and an expansion number. A team appears as its own line, so a VP sees the account manager sub-total and the account executive sub-total without placeholder users in Salesforce.
For larger orgs, our team builds the teams for you from a spreadsheet.
Here's how submissions work:
- Reps submit a baseline and a best case, as a total or by selecting the specific opportunities behind each number, with a comment.
- A manager submitting for the team can pick deals owned by anyone on the team.
- Managers override at the deal or total level, and each override is timestamped, attributed and logged with its rationale.
- Every submission is versioned, and deadlines can lock the field.
- Reminder emails go out when a call is due, and a missing submission shows as a warning.
Keep in mind that the custom hierarchy only includes people who've signed in to Weflow at least once. Reps typically do that through activity capture or conversation intelligence before forecasting is rolled out.
How Weflow projects the renewal number and tracks its accuracy
Weflow runs three forecast methods side by side, and all three work per configuration:
- Weighted forecast: Recalculates each stage's win rate from a rolling window of recent history, such as the last 90 or 180 days, instead of the fixed probability typed into Salesforce. Because the renewal setup has its own stages, early-stage renewals stop getting new-business weighting.
- Roll-up forecast: The calls your reps, CSMs and managers submit.
- AI projection: A separate model per configuration, so renewals are projected from renewal history. It reads more than fifty deal-level signals over up to two years of history and returns a low, middle and high value.
That range lines up with how most teams already forecast churn, with a best, middle and worst case. As our CEO explains:
"The AI prediction is not one number, it is actually a mid, high, and base case, so you have a corridor, because the reality is it is a corridor and a lot of things can happen."
The projection needs six months of opportunity history, but since that history imports at install, your first projection is ready within 48 to 72 hours. It refreshes nightly, and the range widens when the business is changing, for example, with new products or motions.
The pacing view puts all three methods against target in one chart, per motion.

Weflow tracks forecast accuracy per period for every rep, manager and team, out of the box. You choose the field accuracy is measured against, such as Closed Won.

Weflow also snapshots every opportunity every few hours, and that history powers the waterfall, push counts and period-over-period views. For custom fields, history from before rollout depends on Salesforce field history tracking having been on.
A few limits to keep in mind:
- When the projection isn't confident, it shows no range and says why.
- It doesn't yet adjust for ramping reps, so a new CSM's line rests on little history of their own.
- Weflow models churn as a forecast line. It doesn't predict which individual customers will churn.
How Weflow forecast data reaches BI tools and AI assistants
- Integrations: Weflow integrates natively with Salesforce, Gmail, Google Calendar, Google Meet, Outlook, Microsoft Teams, Zoom, Slack and the Outreach dialer. It isn't an integration platform with a connector catalog.
- MCP: The official read-only MCP connector gives Claude, ChatGPT and other assistants forecast calls and pipeline metrics per close-date period, scoped to you or your team, with a per-rep breakdown for up to 25 owners. It also returns playbooks, summaries and transcripts, with a separate admin toggle for transcript access.
- Raw data: The REST API bulk-exports data as JSON or CSV into warehouses and BI tools such as Tableau and Looker. There's no native Snowflake, Databricks or BigQuery connector, so teams use the API.
Submitted forecasts live in the Weflow app, not in Salesforce fields, so a Salesforce connector alone won't see them, but the Weflow connector or API will.
Where Weflow still sends you back to a spreadsheet
- There's no account-level board that rolls renewals up by customer, so "will we lose the whole logo?" isn't a native view. Clari's account module is stronger here.
- Targets are amounts only, so you can't set a goal for the number of logos renewed.
- There's no consumption forecasting. Usage-based teams should look at Aviso or Salesloft's account-based forecasting.
- All configurations share one period type. That means annual renewal periods can't run beside quarterly new business, so you pick one shape for both.
- Dashboards are thinner than Clari's. There's no funnel report and no forecasting dashboard plotting target against trend.
Which teams should choose Weflow for renewal forecasting
Weflow is a good fit for Salesforce mid-market teams that want renewal and expansion as their own configured forecasts: a different date and amount field, churn built from formulas, their own targets, and CSMs in the roll-up the way they actually work.
It also fits if you want a published seat price and an accuracy baseline from day one. But if logo-level churn views or consumption revenue are your main need, look at the alternatives below first.
Clari: Mature enterprise roll-ups bound to the Salesforce hierarchy
Clari, sold under the Salesloft brand since September 2026, is built around roll-up forecasting and pipeline inspection.
Quick specs:
- Forecast tied to the Salesforce hierarchy
- Quote-only pricing, no free trial
- Professional services implementation
How Clari separates renewal and existing-customer forecasts
Clari runs account-based forecasting for existing-customer revenue next to the opportunity forecast, on account segments an admin configures. If your renewal question is "what's this customer worth to us next year?", the account view gives you something Weflow doesn't.
The limits show up once renewals run as opportunities:
- A separate forecast outside the Salesforce hierarchy isn't supported.
- Clari can't tell apart several open opportunities on one account, so a renewal and an expansion on the same customer blur together.
- A forecast column aggregates a single amount field and can't pick the field by condition.
That last limit is where churn gets messy, and teams usually work around it with helper columns:
- Add a column for booked closed-lost churn.
- Add a column for booked downsell churn.
- Add a third column that sums the two.
- Repeat for every other churn source.
Before long, the forecast tab is full of helper columns, and the churn number gets hard to read and maintain.
How Clari rolls up CSM and account manager calls
Clari's roll-up is mature, and its top-down view is the part teams value most: a CRO sees each direct report's commit and best case at a glance and drills down. That holds up well even at 1,000+ reps. The constraints come from how tightly it's bound to the hierarchy:
- Deals roll up by opportunity owner.
- Showing account managers and account executives as separate lines needs an inactive placeholder user in the Salesforce role hierarchy for each group.
- A rep who moves teams either carries their numbers along or, under a new Salesforce user, loses their forecast history.
- A rep who leaves has to stay active until the quarter ends, or their bookings drop out.
- A forecast call is a number with notes, so the deals behind it are free text.
- Leaders see only the level directly below them.
How Clari projects the number and tracks forecast accuracy
Clari's AI projection tends to land close to the quarter's result for mature users. Getting there takes time: RevOps teams find it useful 12 to 18 months after adoption, and it looks only three months ahead. Call data from Clari Copilot doesn't feed the forecast.
Clari Forecast keeps a week-by-week history of every call next to historical CRM totals, and the Time Series Data Hub snapshots opportunity, account and activity data. However, it doesn't compute accuracy, so teams calculate it themselves each month or quarter.
How Clari forecast data reaches BI tools and AI assistants
- Integrations: Salesloft's data layer syncs with Salesforce, Dynamics, Snowflake, Databricks, Gmail, DocuSign, ZoomInfo and LinkedIn.
- MCP: Three servers, each narrow. The Forecast server returns live forecast numbers and historical snapshots but no deal-level opportunity data. The Copilot server reaches call data only. The Salesloft server is read-only and needs a paid add-on.
- Raw data: REST and Export APIs plus a Copilot API, CSV forecast history, and Snowflake and Databricks via Salesloft.
Where Clari sends you back to a spreadsheet
- Churn from several fields needs helper columns
- Forecast accuracy is calculated by hand each period
- A rolling twelve-month forecast gets built outside Clari
- Executive reporting for the CFO and CEO gets rebuilt in a BI tool
Which teams should choose Clari for renewal forecasting
Clari suits large enterprises with mature roll-ups and teams that need an account-based view of existing customers. It also makes sense if your PE sponsor has standardized on Clari across the portfolio. In that case, it's usually smarter to work alongside it than to fight it.
Gong: A forecast board per motion on Gong Foundation
Gong started as a conversation intelligence tool, and Gong Forecast is a paid application bought on top of the Gong Foundation core license.
Quick specs:
- Hierarchy follows Salesforce
- Quote-only pricing
- Seats assigned per application
How Gong Forecast runs separate renewal and retention boards
Gong Forecast runs separate boards for new business, renewals, retention or any other motion, each with its own filters, columns, metrics and targets.
Formula metrics compute values such as net retention, coverage or weighted pipeline. That's a real strength, since you get per-motion boards with retention math and no helper columns.
How Gong Forecast rolls up CSM and account manager calls
Reps submit their number per forecast category with notes. Managers see their team total on top, each person below, and move up and down the hierarchy.

The hierarchy follows Salesforce. When your reporting lines differ from the CRM manager field, you build a placeholder structure to make the roll-up resolve. Gong also has no deal-by-deal forecast submission.
Where teams tend to struggle is running several motions in one module. Our own Head of Sales ran into this as a Gong customer:
"So we were trying to run forecasting for enterprise, commercial and customer success or post sale, like in one forecasting module, and it was very, very clunky. ... our RevOps team spent too many hours building it out and trying to get it to work super well. So we ended up actually doing most forecasting back in spreadsheets."
— Chris Nethercote, Head of Sales at Weflow, former Gong enterprise customer
How Gong projects the number and tracks forecast accuracy
Gong's projection is transparent: it combines closed-won deals, pipeline weighted by historical stage conversion and expected new or moved deals, and a "See the math" panel shows each part.
Reliable projections need at least 400 created opportunities with 150 closed-won across four quarters, which a renewal motion on its own may not reach.
Gong also has a built-in accuracy report, which divides the forecast submitted in a chosen week by actual sales at period end and shows the result per person.
Pipeline history comes from CRM field history. Gong backfills up to five quarters on request through your customer success manager, which takes 3 to 5 business days.
How Gong data reaches BI tools and AI assistants
- Integrations: About 450 integrations and partner solutions across CRM, telephony, conferencing, BI, enrichment and workflow tools.
- MCP: Three record-scoped tools (ask about an account, ask about a deal, generate a brief). It returns AI insights rather than transcripts, it's read-only, and requests draw metered credits.
- Raw data: The API is capped at 3 calls a second and 10,000 a day. Warehouse delivery needs Data Cloud, a separate purchase of about $5,000 a year.
Where Gong sends you back to a spreadsheet
- Multi-team, multi-motion setups fall back to spreadsheets
- Reporting lines that differ from Salesforce need a placeholder structure
- Pipeline history depends on CRM field tracking and a backfill request
Which teams should choose Gong for renewal forecasting
Gong works best for teams already on Gong Foundation that want a separate board per motion, formula metrics such as net retention, and a built-in accuracy report.
If your renewal motion has thin history, check the projection's volume requirement first.
Salesloft: Forecast segments, with AI forecasting for new business only
Salesloft is engagement-led and now merged with Clari. We still cover Salesloft Forecast separately from Clari Forecast because the two products work differently.
Quick specs:
- Deals and Forecast run only on Salesforce
- No published seat prices
- Forecasting sold as an add-on
How Salesloft Forecast splits new business, renewals and upsells
Salesloft Forecast splits the forecast into segments such as new business, renewals and upsells. Each segment has its own opportunity criteria, forecast types and visible hierarchy.
Alongside it, Salesloft runs account-based forecasting for existing customers. Each account carries a machine-predicted Pace number that sellers adjust with an override and a comment, designed for variable or consumption revenue.
That's a real option for usage-heavy renewals.
It's also fairly new: before the merger, Salesloft forecast bookings only, not churn or renewals.
How Salesloft Forecast rolls up CSM and account manager calls
The hierarchy comes from the Salesforce Manager field and drills eight levels deep. Managers with permission submit on behalf of reps.
Only one quota period can be active at a time. Salesloft is also prospecting-focused, and buyers tell us it gives little insight into a client executive team looking after existing customers.
How Salesloft projects the number and tracks forecast accuracy
Salesloft's AI Forecast predicts only new business closing in the current quarter, so renewals get no AI projection. A team qualifies after an engineering evaluation, with four preceding quarters of data and at least 50 closed opportunities per quarter.
Accuracy is measured outside the product. Admins export two years of submitted forecasts as a CSV and match them against attainment in a BI tool.
Inspect shows week-over-week pipeline movement, but no Salesloft page documents an opportunity snapshot store usable in reports.
How Salesloft data reaches BI tools and AI assistants
- Integrations: The data layer syncs with Salesforce, Dynamics, Snowflake, Databricks, Gmail, DocuSign, ZoomInfo and LinkedIn; recording connects Zoom, Teams, Meet, Webex and five dialers.
- MCP: Read-only, in beta, and sold with a paid agent add-on. It reaches accounts, people, opportunities and conversations, but not transcripts or cadences.
- Raw data: A strong self-service REST API that reads activities, conversations, media and transcripts, with webhooks.
Where Salesloft sends you back to a spreadsheet
- Any AI projection for renewals or future quarters
- Forecast accuracy, measured in BI from a CSV export
- Mixed quota periods, since only one can be active
Which teams should choose Salesloft for renewal forecasting
Salesloft fits its existing engagement customers who want segments for new, renewal and upsell in the tool they already run. Pace forecasting makes it a fit for variable or consumption-based existing-customer revenue.
Aviso: Segmented enterprise forecasts plus consumption revenue
Aviso is an enterprise forecasting-led platform that copies your CRM into its own time-series store.
Quick specs:
- Runs on Salesforce, HubSpot, Dynamics, Oracle, SAP and Siebel
- Rolled out by Aviso's implementation team
- Custom proposals, no published prices
How Aviso segments new business, upsell and renewal forecasts
Aviso splits one forecast and its deal views by segment: total, new business, upsell and renewal. Since separate forecasts with their own fields per motion aren't documented, we scored it as partial.
Where Aviso really stands out is consumption forecasting. It turns account usage into ARR or MRR, flags outlier accounts and runs beside traditional revenue forecasting. It also merges several CRM instances into one forecast.
How Aviso rolls up CSM and account manager calls
Aviso rolls up commit, best case and most likely calls automatically across every rep, category and team. Its hierarchies can differ from Salesforce's, which helps when CS reports differently than sales.
Reps and managers enter calls and plans on the forecast screen, and deals move in and out of commit in one click.
How Aviso projects the number and tracks forecast accuracy
Aviso's AI forecast sits beside the team's most-likely call, built from deal WinScores. A WinScore is a daily probability that a deal closes this quarter, and Aviso explains the factors behind each change.
For accuracy, Aviso shows commit accuracy per account executive and exports a forecast audit trail of past calls to compare with actuals. Its own store keeps six to eight quarters of history.
How Aviso data reaches BI tools and AI assistants
- Integrations: More than 200 claimed connections across conferencing, telephony, engagement, support and marketing tools.
- MCP: No MCP server for Claude, ChatGPT or other external assistants. MCP runs only inside Aviso's own Agent Studio.
- Raw data: No public API and no warehouse feed. Data leaves as spreadsheet and file exports.
Where Aviso sends you back to a spreadsheet
- Any analysis outside the app goes through file exports.
- Separate field logic per motion isn't documented, so different date or amount fields per motion aren't something you can count on.
Which teams should choose Aviso for renewal forecasting
Aviso is built for large enterprises with usage-based revenue or several CRMs that need consumption forecasting beside segmented new, upsell and renewal views.
What each renewal forecasting tool actually costs
Weflow is the only tool here with published seat prices. The other four are quote-only, and several charge for forecasting or AI access on top of a core license.
| Tool | Published price | What costs extra | Minimums and terms |
|---|---|---|---|
| Weflow | Deal Intelligence & Forecasting at $39 per user per month standalone; Revenue AI Enterprise at $79 includes forecasting (Revenue AI Business at $59 includes Deal Intelligence but not forecasting) | Only Agent Builder is consumption-priced beyond its free 25 actions a month; AI summaries, field updates and Ask AI are in the seat; no implementation fees | 10-user minimum per product or bundle; 12-month term, billed annually |
| Clari | No published seat price; our read is roughly $120 to $180 per user per month | Professional services implementation, roughly $15,000 to $50,000 | Quote-only; no free trial or self-serve signup |
| Gong | No published price; per-user licenses plus a platform fee that scales with users | Gong Forecast is an application on top of the mandatory Foundation license; Data Cloud about $5,000 a year; MCP and API AI use draws pooled credits | Custom proposal; seats assigned per application |
| Salesloft | No published seat price; Advanced and Elite packages | Forecasting, AI agents and the dialer are add-ons; MCP comes with the agent add-ons | Pricing via a sales call |
| Aviso | No published license price; custom proposals | Agent work billed at $1 to $1.50 per outcome | Per-user licenses; offers contract buyouts and free migration |
For a sense of scale on Gong: one renewal proposal we saw for 45 licenses came to about $80,000 a year, with forecasting about $10,000 of it.
Often, though, price isn't the biggest budget hurdle. A CFO won't fund two forecasting tools, so if your new-business forecast is locked into an incumbent contract, a second forecasting license is a hard sell.
We built our packaging for that situation. Teams start with activity capture and conversation intelligence, then expand into forecasting for roughly $10 more per user per month instead of a separate contract.
Should you finish your own Salesforce renewal build instead?
Sometimes, yes. With AI coding tools, building a working prototype of a renewal forecast is cheap. Owning and maintaining it is where the cost adds up.
| Area | Your own Salesforce build | A forecasting tool |
|---|---|---|
| Setup cost | Low for a prototype, especially with AI coding tools | License cost, plus services fees with some vendors |
| Snapshot history | Salesforce keeps no record of last month's pipeline, so you build snapshotting, often in a warehouse | Snapshots stored by the tool |
| Accuracy tracking | You store every submission and compute it yourself | Built in with some tools (Weflow, Gong, Aviso); exported with others |
| Hierarchy changes | Changing a Collaborative Forecasting type wipes the quarter's history and quotas | Depends on how tightly the tool binds to the Salesforce hierarchy |
| Executive change requests | Each new view means rebuilding logic you own | A configuration edit, if columns are built from fields and formulas |
| Maintenance owner | You, alongside running the business | The vendor |
If your quarter rests on about ten material renewals, native Salesforce forecasting and a careful deal-by-deal review can carry it.
The case for a tool grows with the number of deals, managers and roll-up layers, and the bar is simple to state: owning the tool has to cost less than owning your build.
Which renewal forecasting tool fits your team
The right tool follows from the renewal problem you're solving, the shape of your team and the contracts you're locked into.
Pick by the renewal problem you most need solved
| Your main need | Best fit |
|---|---|
| Renewal forecast on contract date with its own churn formula and targets | Weflow |
| An account-level view of whether you lose the whole logo | Clari |
| Consumption or usage-based existing-customer revenue | Aviso, or Salesloft's Pace forecasting |
| Already on Gong and want a board per motion | Gong Forecast |
| Already on Salesloft engagement and want segments in the same tool | Salesloft Forecast |
Pick by team size and how many CSMs you run
| Your team shape | Fit |
|---|---|
| Mid-market, CSMs carrying renewal and expansion numbers on two teams | Weflow (10-user minimum per product or bundle) |
| 1,000+ rep enterprise with a mature roll-up | Clari |
| Enterprise on several CRMs | Aviso |
Pick by budget and the contracts you're locked into
| Your situation | Path |
|---|---|
| CFO won't fund a second forecasting tool | Start with capture and conversation intelligence, add forecasting at the incumbent's renewal |
| PE sponsor standardized on your incumbent | Coexist: improve the data the incumbent reads and wait for the political window |
| Incumbent renewal window approaching | Evaluate now, so selection and rollout fit inside the window |
| No budget this year | Finish your Salesforce build and keep it scoped to what you can maintain |
Walk through the product yourself, no call required.
What changed in renewal forecasting tools in 2026
- Clari Copilot began replacing Salesloft Conversations as Salesloft's conversation intelligence layer (June 2026 release notes), with Conversation Intelligence in Salesloft for new implementations from July 2026.
- Clari has been sold under the Salesloft brand since September 2026.
- Salesloft removed transcript retrieval from its MCP server, so assistants now get AI summaries instead (August 2026 release notes).
- The Clari Forecast MCP server launched with live forecast data and historical snapshots, but no deal-level opportunity data (September 2026 release notes).
- Gong meters AI in pooled credits on top of its Foundation-plus-applications model, which it introduced in March 2025. MCP and API AI use draw credits.
- Weflow's MCP connector returns forecast calls and per-rep pipeline metrics, so assistants can read the submitted forecast directly.
How we researched and scored this comparison
We scored each tool on nine capabilities using vendor help documentation, public pages, and what buyers told us during evaluations.
Each capability got one of three verdicts:
- Offers: The capability works as described for the renewal and expansion motion.
- Partial: It exists with a documented limit, such as accuracy measured outside the product.
- Not offered: The tool doesn't provide it.
Since Weflow wrote this comparison, we've listed our own limits as plainly as everyone else's.
FAQ: Questions RevOps asks about renewal and churn forecasting
Can the renewal forecast run on contract date, not close date?
In Weflow, yes. Each forecast configuration maps its own date field, and a renewal configuration can use contract start date instead of close date while new business stays on close date.
Can churn show as a negative line inside net new ARR?
It depends on whether the tool can build a column from conditions. Weflow builds churn and contraction as a formula column over condition groups, and Gong's formula metrics compute net retention. Clari, on the other hand, only allows single-amount columns, which forces you into helper columns. In Weflow, the summary tiles stay fixed to Salesforce forecast categories, so churn lives as a column, not a tile.
Can I see which whole customer logos are at risk?
Not in Weflow. Our forecasting is built on opportunities, and there's no account board that rolls renewals up by customer. Clari's account module is stronger here, and Salesloft and Aviso forecast at account level for existing customers.
Can annual renewals run beside a quarterly new-business forecast?
Not in Weflow: all configurations share one period type. Salesloft allows only one active quota period at a time.
How do you keep renewal and expansion opportunities on one account apart?
In Weflow, you separate them by configuration: filter on opportunity type or record type, with one lane for renewals and another for expansion. The same approach keeps activity mapping clean when both are open on one account. Clari can't distinguish several open opportunities on one account.
Do renewals need to exist as Salesforce opportunities first?
For Weflow, yes, because renewal forecasting runs on renewal opportunities and their contract dates. Account-based forecasting without opportunities is in Clari, Salesloft and Aviso.
How much history does an AI projection need for renewals?
- Weflow: Six months, imported from Salesforce at install, with a separate model for the renewal configuration.
- Gong: 400 created opportunities with 150 closed-won across four quarters.
- Salesloft: Four quarters with at least 50 closed opportunities each, and new business only.
- Clari: 12 to 18 months before RevOps teams find it useful.
Can I start with only the renewal forecast and keep my current tool?
Technically, yes. Weflow sells Deal Intelligence & Forecasting standalone, runs a renewal configuration on its own, and lets RevOps configure the forecast in private before anyone else sees it.
Budget is usually the harder part, since a CFO won't fund two forecasting tools. That's why most teams start with capture and conversation intelligence and add forecasting at the incumbent's renewal.
Can I rebuild my Clari or Gong calculated columns in Weflow?
Yes. Clari calculated columns rebuild as Weflow formula fields: condition groups plus ordinary arithmetic, shown as currency, percentage or number. You can expect high parity, though not perfect parity.
As one Clari customer told us during their evaluation:
I see your solution being able to do at least 80% of what we had with Clari.
Where does the submitted renewal forecast live, and can AI assistants read it?
In the Weflow app, not in Salesforce fields. Claude, ChatGPT and other assistants read forecast calls through Weflow's read-only MCP connector, and the REST API exports them to BI.
How long does renewal forecast setup take, and who does it?
Technical setup takes 30 to 45 minutes with your Salesforce admin, and the first AI projection is ready within 48 to 72 hours.
Since every configuration change re-runs the historical import, views can show partial numbers for a day or two, so it's best to settle the configuration before showing it to CSMs.
There's no implementation fee with Weflow, while Clari charges professional services fees and Aviso rolls out through its implementation team.
Can a forecasting tool tell me which customers will churn?
No forecasting tool does this alone. Multi-year customers signal they're leaving one to two years out, while forecasts look one to four quarters ahead. Weflow models churn as a forecast line with a best, middle, and worst range, not as a per-account prediction.










