How Long Revenue Intelligence Tools Take to Implement: Aviso, People.ai, Avoma, Clari, Gong and Weflow (2026)

Capture and conversation intelligence can be live in about two to four weeks when one admin installs centrally and the vendor runs onboarding. Forecasting takes longer in every tool on this list, ours included. Whether a tool fits your renewal window depends on its architecture and on whose hours the project costs. Feature depth has little to do with it.

Vendor quotes run from 2 to 4 weeks up to 12 to 18 months "to genuinely running". Those figures measure different things: the install, the go-live, or the point where your business actually forecasts in the tool. That's why they don't line up when you put them side by side.

So we split each of the six tools into four phases: install, configuration, rollout, and a forecast you trust. For each phase, we show whose hours it costs.

We're the Weflow team, so read this knowing where we sit. Weflow is the Revenue AI Orchestration platform for sales, customer success, and RevOps teams. We've put our slow parts next to our fast ones, and we say plainly where another tool fits you better. If you want the full picture of what you'd be implementing, here's Weflow's Revenue AI Orchestration platform.

How long each tool takes to implement, side by side

Every figure carries its source. The next section explains the phases behind each one.

Why vendor timelines don't compare, and how we split them

Most of the confusion comes from vendors counting different finish lines. Once you know which line each number counts, the spread from weeks to a year and a half makes sense.

What each vendor's quoted timeline actually measures

One vendor quotes the technical install, another the go-live, another "genuinely running", and some review-site numbers are years old.

Where a figure is dated, we label it and put it next to the vendor's current number instead of dropping it.

The four phases we time, and whose hours each costs

Implementation splits into four phases, and each one has a different owner. Configuration is where the real time goes.

In our experience, the product is rarely what stretches the timeline. Internal alignment is:

• Getting the two admins into the same call. They usually sit on different teams, and that alone can turn a one-hour job into two weeks.
• Agreeing which methodology to score against and which fields to write. That's a change-management conversation, not a configuration task.
• Waiting on IT consent for the mail tenant, which sets your earliest possible go-live on Microsoft.

Five questions that decide if a tool fits your window

These are the root causes of implementation time. Ask each one on a vendor call before you look at a single feature.

Who does the install: one admin, every rep, or the vendor?

There are three install architectures, and they carry different rollout risk:

• A central admin install needs nothing from your reps.
• Per-rep connections depend on rep behavior, and reps don't do setup steps.
• Credential handoffs move the work onto your admins first and then onto the vendor's team.

We hear this on almost every evaluation call:

"A lot of the other ones are like, oh, like get them to like install the thing and do the setup. But I'm like, they're not going to. They're not going to do it. It's just like herding cat."

How to assess it: ask the vendor what a rep has to click before any data reaches Salesforce.

Who owns onboarding, and how many RevOps hours it takes

A tool swap doesn't compete with your incumbent. It competes with your RevOps delivery backlog. It gets approved when it arrives as a managed service with a fixed timeline and a price, and it stalls when it arrives as a co-project that needs your hours in a busy quarter.

The six tools use five onboarding models:

• Vendor-run at no charge: Weflow, with a managed-service option where RevOps only answers questions and unlocks access.
• Paid PS packages with expiring hours: Gong, 8 to 22 hours per package.
• Partner-routed: Gong, for some smaller and mid-sized customers, with a separate implementation fee.
• Vendor implementation team, after customer credential handoffs: Aviso.
• Optional paid expert onboarding: Avoma, at $1,000.

Clari's professional services are estimated at $15,000 to $50,000. Clari publishes no PS pricing.

"I made a deliberate choice to let Weflow own end-to-end onboarding rather than pull my team off revenue-generating work. That's exactly the kind of partnership leverage I was looking for."

Scott Jones, SVP of GTM Revenue Intelligence & Enablement, KORE Wireless

How to assess it: ask for a mutual action plan with named owners on both sides, and count the hours on your side.

Which module goes live first, and why forecasting comes last

Revenue tooling adopts in data-foundation order. Rolling it out in reverse is how tools end up unused.

1. Activity capture: it asks nothing of reps, works the day it's enabled, and everything downstream reads from it.
2. Conversation intelligence: it gives reps a personal win in summaries and notes, which drives adoption.
3. Deal intelligence: its signals only mean something once activity sits on the right opportunities.
4. Forecasting: it encodes an operating cadence and needs sales leadership in the room. By the time you've agreed the design, capture has given you weeks of clean data.

How to assess it: ask the vendor which module they switch on first, and why.

Whether day-two changes need a professional services ticket

If adding a quarter target or a forecast column needs professional services, your forecast freezes at whatever was configured at implementation. Every reorg then becomes a project. One RevOps lead described their old setup like this:

"if you want to, you know, create a new quarter target, or you want to create a new forecast call, or you want to change the rollout forecast, right? In the product, you want to adjust the columns here, you have to go via professional services."

We built Weflow's admin console so your team makes those changes. Of everything customers underestimate before buying, self-service admin configurability is the one they mention most once they're live.

How to assess it: in the trial, change a roll-up or a forecast column yourself.

Whether marketing, CS and AI assistants keep transcript access

Your transcript archive is a shared company asset. Marketing, sales and CS all read it, and none of them bought the tool. A switch has to keep every consumer's access path: an MCP connector for assistants, and an API or export for BI and warehouses.

"The gold for us is in the transcript of calls, and we use that across all teams. Marketing figures out why somebody inbounded, sales figures out their next steps after a demo, customer success uses it for feature requests."

How to assess it: ask what an assistant can read (raw transcripts or only summaries), and what bulk export exists.

Weflow: one 45-minute admin session, then a guided rollout

What it is: Weflow automates activity, contact and conversation capture into Salesforce and uses AI for deal intelligence, forecasting, Ask Weflow AI and agents. It's built for Salesforce teams and works only with Salesforce.

Quick specs

• CRM: Salesforce only.
• Timeline: about 2 weeks for capture and conversation intelligence, 2 to 4 weeks typical full rollout, 4 to 6 for a large org (Weflow onboarding records).
• Onboarding: run by our customer success team at no charge, with a managed-service option.
• Trial: 14 days with white-glove implementation included, plus a 3-month paid pilot for forecasting.

The install is two Salesforce managed packages, one integration user with a dedicated permission set, and one mail app installed centrally in Microsoft Entra or Google Workspace. There's no code. Your Salesforce admin and your mail admin sit in one session of about 45 minutes, and one prerequisite applies: IP restrictions on the connected app have to be relaxed for the install.

Where it's strong on implementation

• One admin session connects everything, and reps don't install anything for capture to start.
• We run onboarding ourselves against a mutual action plan, at no charge, instead of selling it as professional services or handing it to a partner.
• Our fastest recorded rollout was three days for a 120-seat conversation intelligence replacement. We don't recommend that pace, but it shows how little of the timeline the product itself takes.

KORE Wireless rolled out in five phases across four regions (Europe, Americas, Brazil and APAC) with zero adoption friction. We ran the live training for the Brazil team with a real-time Portuguese translator.

"It's probably been the most flawless rollout of any product I've ever been involved with."

Scott Jones, SVP of GTM Revenue Intelligence & Enablement, KORE Wireless

Where it falls short

• Forecasting is our slow module. Your existing Salesforce forecast configuration doesn't carry over, so you set it up in Weflow.
• Forecasts built on non-standard Salesforce objects may not be feasible. We test that during the trial.
• There's no sandbox promotion. Production is a fresh connection, though our team copies teams and templates across from the sandbox workspace.
• Each user has to sign in once before the notetaker joins their meetings.
• Weflow has no native Snowflake, Databricks or BigQuery connector. Teams move data to the warehouse through the API.
• Forecast submissions, targets and roll-ups live in Weflow, not in Salesforce. Everything else lands in Salesforce objects.
• At 1,000+ reps, Clari's enterprise roll-ups are more mature than ours.

Choose it if: you're a mid-market to enterprise Salesforce team that needs capture, conversation intelligence and forecasting live inside a renewal window without spending RevOps hours.

Aviso: your admins build, Aviso's implementation team configures

What it is: Aviso is a forecasting-led enterprise revenue platform. It copies your CRM into its own platform and adds deal scoring, pipeline analytics, conversation intelligence, relationship intelligence, the MIKI assistant and a library of AI agents.

Quick specs

• CRM: Salesforce, HubSpot, Dynamics, Oracle, SAP and Siebel, and it can merge several CRM instances into one view.
• Timeline: 10 weeks (G2 Fall 2023 Report, dated).
• Onboarding: Aviso's implementation team, with white-glove onboarding offered.
• Trial: no trial in our evidence. Every deal is a custom proposal.

Where it's strong on implementation

• Aviso consolidates forecasting across several CRMs, which none of the other tools here do in the same way.
• Aviso offers to buy out your existing vendor contract, migrate you for free and include white-glove onboarding.
• It can backfill Gong call history through Gong's API.

Where it falls short

• Your IT admins build shared mailboxes, routing rules and one app per conferencing platform before Aviso's team can start.
• Assistants, BI tools and warehouses can't reach Aviso data directly, because there's no public API or external MCP.
• The only timeline figure available, 10 weeks, dates from 2023.

Choose it if: you're a large enterprise consolidating forecasting across several CRMs and you're comfortable handing the build to Aviso's team.

Backstory (People.ai): central admin capture, live in 2–4 weeks

What it is: Backstory, which rebranded from People.ai in 2026, is an enterprise revenue intelligence platform built on automatic email, calendar and CRM activity capture for Salesforce. It adds AI deal summaries, forecasting and an MCP server. It doesn't record calls; it ingests transcripts from Zoom, Teams, Meet, Webex and Gong.

Quick specs

• CRM: Salesforce through a managed package. Dynamics 365 and Oracle through API connections Backstory calls compatible rather than native.
• Timeline: 2 to 4 weeks for most teams (Backstory, 2026), against 13 weeks in the G2 Fall 2023 Report.
• Onboarding: central admin configuration, with Backstory support and CSM involved for some steps.
• Trial: none in our evidence.

Where it's strong on implementation

• Capture is central on both Google and Microsoft, so reps don't install or approve anything.
• Backstory analyzes about two years of activity history at onboarding to set engagement benchmarks.
• Its MCP server reaches more assistants than any other tool in this set.

Where it falls short

• Backstory doesn't record calls, so you still need a recorder, and it never backfills meeting transcripts from before the integration date.
• The forecast hierarchy lives in a CSV, so every reorg means a re-import or manual edits.
• Backstory recommends giving its Salesforce integration user the System Administrator profile, which security reviews tend to push back on.

Choose it if: you're an enterprise of roughly 1,000 to 10,000 employees that wants central capture and an MCP context layer for agents, and you already have a call recorder.

Avoma: connects org-wide in minutes, rolls out in weeks

What it is: Avoma is a meeting-first conversation intelligence tool that records, transcribes and summarizes calls. It has added Salesforce sync, coaching, deal and forecasting features on top, and sells mainly to small businesses and solo operators.

Quick specs

• CRM: Salesforce, HubSpot, Pipedrive, Zoho, Copper and Zendesk Sell, one CRM per organization.
• Timeline: capture visibility "within days" (Avoma). Full rollout 4 to 6 weeks (medium-confidence estimate).
• Onboarding: self-serve, with optional expert onboarding at $1,000. Enterprise includes concierge onboarding.
• Trial: 14 days of the Organization plan with all add-ons, no credit card.

Where it's strong on implementation

• Avoma is fast to connect. One admin links Google or Microsoft, Zoom and the CRM for the whole organization.
• Prices are public and there's no setup or platform fee, so you can size the deal before a sales call.
• You can trial the full product for 14 days on your own data.

Where it falls short

• Avoma is built outward from the meeting, so CRM depth arrived later and the center of gravity stays on the call.
• One forecast configuration per organization won't hold separate new-business and renewal forecasts.
• Deal scoring, email sync and forecasting all sit behind the Revenue Intelligence add-on.

Choose it if: you're a small, meeting-first team that wants a fast org-wide connection and published prices.

Clari: each rep connects separately, and forecasting takes longest

What it is: Clari is a revenue platform built around roll-up forecasting and pipeline inspection, with Clari Copilot for conversation intelligence. Since the Clari–Salesloft merger closed in December 2025, it's sold under the Salesloft brand, and Salesloft supplies activity capture, engagement and deal management.

Quick specs

• CRM: Deals and forecasting run only on Salesforce.
• Timeline: 8 to 12 weeks for the technical install. 12 to 18 months to genuinely running (estimates).
• Onboarding: professional services, estimated at $15,000 to $50,000.
• Trial: none. Pricing is quote-only.

Where it's strong on implementation

• Clari's enterprise roll-ups at 1,000+ reps are the most mature in this set.
• Leaders who've used it for years value seeing and editing the whole forecast inline.
• Warehouse delivery to Snowflake and Databricks comes through the Salesloft data layer.

Where it falls short

• Per-rep connections mean coverage depends on every rep finishing their setup. One team we spoke with found its Clari license usage at about 8%, with many reps' calendars never synced.
• The year-plus gap between install and genuinely running comes from agreeing the hierarchy, building the Salesforce fields the views depend on and getting managers to submit.
• Changing the forecast later is a project rather than a setting, often routed through professional services.

Choose it if: you run roll-up forecasting across 1,000+ reps. If a PE sponsor has standardized Clari across the portfolio, keep it and let Weflow Activity & Contact Capture write clean activity into Salesforce for Clari to read. Just don't run two capture engines at once.

Gong: admin-side capture, rollout sold as professional services

What it is: Gong is a conversation intelligence platform that records and analyzes sales calls in its own cloud. It's sold as a mandatory Foundation core licence with coaching, forecasting, sales engagement and data export applications on top.

Quick specs

• CRM: Salesforce, HubSpot and Dynamics.
• Timeline: about 4 weeks on average, 6 to 12 weeks with significant professional services (estimates).
• Onboarding: fixed-hour PS packages whose hours expire. Some smaller and mid-sized customers go to partners.
• Trial: none in our evidence. Pricing is a custom proposal.

Where it's strong on implementation

• Gong has the deepest conversation analytics in this set, and its deal boards are a genuine favorite with reps and managers.
• Capture connects company-wide from the admin side, with no rep install.
• It's the safe purchase. Few sales leaders expect to be blamed for choosing Gong, and its compliance certifications are extensive.

Where it falls short

• PS hours expire, and the customer staffs the project with five roles. Without a dedicated owner, teams end up using recording and little else.
• Forecasting for several motions often drifts back to spreadsheets.
• Getting data into your warehouse, or into assistants beyond AI insights, costs extra through Data Cloud and credits.

Choose it if: you want the deepest call analytics and the safe choice, and you have the internal staff to run the PS project.

Why the forecast you trust takes longer than go-live

Forecasting encodes an operating cadence: who submits, how often, at deal or manager level, and against which quota and budget. Those are sales-leadership decisions, not tool settings. A vendor that promises a fast forecast is promising those decisions will be quick, and you know your leadership team better than they do.

The second clock is history. An AI projection is only as believable as the history it learns from, so ask any vendor how much history it needs and where that history comes from.

Even a well-resourced team can lose this phase:

"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

Weflow's roll-up shows quota, commit, best case and pipeline coverage on one page, so the forecast review runs deal by deal.

Gong's forecast rolls up from VP to manager to rep along the Salesforce hierarchy, which works well when your reporting lines match the CRM.

How your Gong recordings, Clari forecast calls and history move

The archive is often the real reason teams stay. History can arrive in days or a week rather than quarters, but the mechanics and the cost differ by tool.

What each tool costs, including implementation and services

Implementation is part of the price. Free vendor-run onboarding, expiring PS hours, estimated PS fees and optional paid onboarding all change what you actually pay to get live. Four of the six tools publish no seat price.

Which tool fits your renewal window

Best fit by team size, primary need and budget

Each tool has a situation it fits best, and for some readers the answer isn't Weflow.

How we'd plan select, implement and roll out before year end

Prove capture and conversation intelligence on your own org in Q3, implement those first in Q4, and give forecasting its own pilot cycle instead of forcing it into launch week. Here's how that looks with Weflow, and what to ask any vendor at each step.

1. Q3: run the evaluation on your own org. Our 14-day trial includes white-glove implementation and typically covers one team of five to ten people, with a sync-back so you see months of real history on day one. Ask any vendor: does the evaluation run on our Salesforce and our mailboxes, and who does the setup?
2. Book the two-admin session early. Get your Salesforce admin and mail admin into one 45-minute call, and on Microsoft, start the consent from our admin console as soon as you've signed. Ask any vendor: which of our people need to be in the room, and for how long?
3. Q4, first weeks: install and import history. The 24-month activity sync-back runs over up to a week, and a Gong migration takes about one to two weeks. Ask any vendor: how long will our history take to arrive, and what does it cost?
4. Weeks two to four: role-based rollout of capture and CI. We run separate leadership and rep training, against a mutual action plan with named owners. Ask any vendor: who runs training, and who owns each task on our side?
5. Forecasting on its own track. Agree the cadence with sales leadership while capture builds clean data, then run a 3-month paid pilot that's contractually the first three months of a multi-year term, with an opt-out. Ask any vendor: how many forecast cycles before we can judge predicted against actual?
6. Cut over at contract end. Switch off the incumbent's capture the day yours goes live, so two engines never write duplicate activity. Ask any vendor: what's the cutover sequence, and how do you prevent duplicates?

See how Weflow captures activity, updates Salesforce fields from calls, and rolls up your forecast. Book a 30-minute demo.

What changed for these six tools in 2026

Several of these tools changed structurally, so older reviews and timelines may describe products that no longer exist in that form.

• People.ai rebranded to Backstory in 2026. The Salesforce package and fields still carry the peopleai prefix.
• The Clari–Salesloft merger closed in December 2025. Clari, Clari Copilot, Salesloft and Groove now ship one monthly release, and Clari is sold under the Salesloft brand.
• Gong introduced AI credits on top of per-seat pricing, with allocation details sent to customers in late May 2026.
• Backstory MCP moved to Backstory credentials in August 2026, so it no longer needs a Salesforce login.
• Clari launched a Copilot MCP server and a Forecast MCP server in 2026, and Salesloft removed transcript retrieval from its own MCP server.

The G2 Fall 2023 timelines for Aviso and People.ai predate all of this.

How we built this comparison, and where we're biased

We wrote this, and we sell one of the six tools. We've tried to make the bias visible instead of hiding it, by sourcing every figure and putting our own limits in the same table as everyone else's.

• Vendor documentation: help centers and setup guides for who installs what, and where.
• Vendor-stated figures: marked with the vendor's name, such as Backstory's 2 to 4 weeks.
• Third-party reports: the G2 Fall 2023 Report, always labeled with its date.
• Estimates: figures from teams who've run these tools, such as Clari's 12 to 18 months, labeled as estimates. Low-confidence figures say so.
• Our own onboarding records: the source of Weflow's phase timings.

Questions RevOps teams ask us about implementation timelines

How much does implementation cost, and who pays for professional services?

Weflow doesn't charge for implementation. Our customer success team runs it. Gong sells fixed PS packages of 8 to 22 hours whose hours expire, and Clari's professional services are estimated at $15,000 to $50,000. Avoma's expert onboarding is an optional $1,000, and Aviso includes white-glove onboarding in its proposal.

Who from our team needs to be in the room, and for how long?

For Weflow, a Salesforce admin and a mail or IT admin attend one technical session of about 45 minutes, and RevOps joins the configuration decisions. Gong's PS packages ask you to name a Gong administrator, a project manager, sales process leaders, an executive sponsor and system administrators. With Aviso, your admins build mailboxes and conferencing apps before handing over credentials.

Can the vendor run implementation as a managed service?

Weflow offers a managed-service option where we do the heavy lifting and your RevOps team only answers questions and unlocks access. Aviso's implementation team also does the build, after your admins complete the credential handoffs. Gong's packages put configuration ownership on a named Gong administrator from your team.

Does Google Workspace or Microsoft 365 change the timeline?

Yes. Google environments move faster with Weflow. On Microsoft, the install only completes when a Microsoft admin starts it from the Microsoft section of Weflow's admin console and consents there. A Salesforce admin can't do it for them, and approving the app in the Microsoft 365 admin center alone doesn't connect it. A temporary Salesforce license or a screen-share gives the Microsoft admin access, and IT's approval sets your earliest go-live.

Can we test in a Salesforce sandbox before going live?

Yes. A Weflow sandbox workspace is a separate instance pointed at your sandbox org, with its own packages, integration user and mail connection. Production is a fresh connection rather than a promotion, but our team copies teams and templates across, and sandbox recordings can move to production. You switch off capture and conversation intelligence on the sandbox before production goes live.

Can we run the new tool alongside Gong or Clari during cutover?

Running two capture engines at once writes duplicate activities into Salesforce, so turn the old one off at go-live. Clari reads activity from Salesforce, so Weflow Activity & Contact Capture can feed Clari permanently if Clari stays for forecasting. With Outreach or Salesloft sequencing alongside, Weflow's compatibility mode skips emails the sequencer already logs.

What contract terms apply: minimum term, seats, opt-out pilot?

Weflow's standard contract is 12 months, with a 10-seat minimum and annual billing. Seats added mid-term are charged pro rata, and there's no contractual right to reduce seats mid-term, though you can reassign them when someone leaves. For forecasting, our 3-month paid pilot is the first three months of a multi-year agreement with an opt-out at the end.

What do IT and security need to approve before go-live?

Weflow holds SOC 2 Type II, is GDPR compliant, uses Zero Data Retention for AI processing and never uses customer data to train models. Your Weflow data sits in the same region as your Salesforce instance, and our models run primarily on Google Gemini. We're working toward ISO 27001 with a target date of December 2026; that's a commitment, not a held certification. Gong's certification set, including ISO 27001, is extensive, and new Gong customers choose US or EU storage at onboarding, with US as the default.

How do we get reps and managers to adopt without a fight?

Start with capture that asks nothing of reps. Weflow logs only emails and meetings with external participants and never internal-only threads, which answers the first objection that the company is reading their email. Then train by role, with separate leadership and rep sessions. Reps who like Gong usually want to hear how a team their size made the move, so bring peer proof into the room.

What breaks an implementation timeline: custom objects, validation rules, permissions?

Forecasts built on non-standard Salesforce objects can stall, which is why we test them in the trial. Weflow inherits permission sets, field-level security and role hierarchy, but not visibility enforced through list views or Lightning component visibility. That segregation gets rebuilt as centrally assigned views. Connected-app IP restrictions also have to be relaxed for the install, and validation rules and field dependencies are respected on every write.