Gong vs Outreach Kaia for Teams Already on Outreach (2026)

A free Kaia pilot tests whether Outreach's conversation intelligence holds up on about 15 seats for 30 days. Your Gong renewal forces a bigger decision. After renewal, who can reach your call data, where does it land in Salesforce, what does it cost at full headcount, and what happens to years of Gong history?

Here's our answer up front:

• Gong is the defensible pick if you want the deepest conversation analytics and you'll fund Foundation plus the applications on top.
• Outreach Kaia wins if one vendor is the overriding constraint and your whole motion lives inside Outreach.
• The third shape is the one the renewal hides. You keep Outreach for sequencing and dialing, and you put Weflow Conversation Intelligence and AI Field Updates into Salesforce.

Weflow is the Revenue AI Orchestration platform for sales, customer success, and RevOps teams. It's built for Salesforce teams, runs alongside Outreach, and publishes its price: the Revenue AI Foundation bundle is $49 per user per month.

Weflow, Gong and Outreach Kaia compared across nine capabilities

All three tools record and transcribe calls well. They split on where the call data lands, who can reach it, and how the AI gets charged.

The sections below walk each tool through the same capabilities in the same order.

Why your Gong renewal turned into a Gong vs Kaia decision

Your renewal became a choice because Gong and Outreach grew toward each other from opposite ends. Gong moved out from conversation intelligence into sales engagement. Outreach moved from sequencing into conversation intelligence, deal management and forecasting, and now markets itself as an all-in-one agentic revenue platform.

Outreach also has a distribution advantage you're already paying for. It cross-sells Kaia into its installed Engage base, and we've seen it hand an existing customer 14 or 15 free Kaia licenses for a 30-day pilot, with a heavily discounted add-on at contract. Free and already in the stack is a strong pull before anyone compares features.

Meanwhile, Gong's pricing got harder to defend on value:

• You buy a mandatory Foundation license first.
• Coaching, forecasting, engagement and data export are separate applications on top.
• Automated AI is now metered in credits.

Teams we talk to aren't leaving Gong because it's broken. They're asking whether the output still justifies the price.

So the article compares three stack shapes: stay on Gong, consolidate into Outreach with Kaia, or keep Outreach for sequencing and add Weflow as the intelligence layer that writes to Salesforce.

What Weflow gives a team that keeps Outreach

Weflow does no sequencing or dialing, and we're not building any. Nothing below competes with what you keep Outreach for. Weflow covers conversation intelligence across your whole revenue team, including the Outreach dialer, and writes what it finds into Salesforce.

Weflow records Outreach dialer calls and computer softphone calls

Your reps' Outreach dialer calls come into Weflow automatically. Each one arrives labeled as an outbound call with the person's name, audio, speaker separation, transcript, summary and coaching. You connect your Outreach account yourself from Weflow's Setup and Integrations page.

Here's what happens to each kind of call:

• Outreach dialer: the dialer records, and Weflow pulls the recording in and processes it like any meeting. Summaries, field updates, scorecards and search all work on it. There's no video.
• Desktop softphone: the Weflow desktop app records any softphone whose audio runs through the computer, such as Aircall or RingCentral, without a provider integration. The rep starts each recording.
• Mobile carrier line: Weflow doesn't capture calls a rep makes from their own mobile number. Those reach Salesforce only if the rep logs them by hand.

Weflow AI Field Updates write call data into Salesforce fields

Weflow AI Field Updates turn what was said on a call into values in Salesforce fields you can group, filter and chart. A summary in a text box can't feed a dashboard. A picklist value can.

• Field types: picklists, numbers, dates, multi-selects and text, on standard objects (Account, Contact, Opportunity, Lead) and custom objects.
• Per-field control: each field is set to write automatically or to wait for the rep's review. A website field can update itself while a champion field waits for a human.
• Methodology: over 250 pre-built prompts cover MEDDIC, MEDDPICC, SPICED, BANT and custom methodologies.
• Limits: lookup fields are excluded, and custom objects need setup by Weflow support. Validation rules still apply.

In automatic mode, a field update writes over the existing value with what the latest call produced. For fields that should get richer as a deal progresses, use review mode or tell the prompt to leave the field alone when the call adds nothing new.

Weflow scores every recorded call against your coaching templates

Weflow scores every recorded call automatically against the coaching template assigned to that team: MEDDIC, MEDDPICC, Challenger or your own. Managers can override any score.

Scores roll up per call, per opportunity and per rep over months. A manager can see that one seller is consistently strong on metrics and weak on champion identification, and coach that specific gap instead of reviewing calls at random.

Criteria are rated 1 to 5 or as free text. When several reps join the same meeting, Weflow doesn't score each seller individually.

Weflow deal warnings run on rules you define

Weflow ships 50+ deal signals and lets you build your own warnings with AND/OR rules. Rules can use any opportunity field except text fields, and computed fields such as days inactive, close-date pushes and time in stage.

That matters because slippage looks different in every motion. A team with a 60-day cycle can flag 14 days of silence, while a team with a 12-month cycle wouldn't. Warnings also show up on the forecast submission screen, at the moment a rep decides what to commit.

Deal warnings are Weflow fields, so they don't appear in Salesforce reports or your BI tool.

Weflow forecast submissions roll up the hierarchy, outside Salesforce

In Weflow, each rep submits a baseline and a best case, either as a total or by selecting the opportunities behind each number. Calls roll up to manager, VP and executive automatically.

• Managers override at the deal or total level, and each override is timestamped, attributed and logged with its rationale.
• Every version is kept, so you can see whether a rep's call moved during the quarter.
• Separate forecasts for new logo, renewal and expansion run on their own cadence.

Submissions happen in the web app, not from a phone or chat tool. They aren't written to any Salesforce field. You can read them over the MCP connector.

Weflow sends conversation data out through API and MCP

Weflow gives the people and AI tools that read your transcripts three routes to the data:

• Integrations: Weflow connects natively to Salesforce, Gmail, Google Calendar, Outlook, Zoom, Teams, Meet, Slack and the Outreach dialer. The list is narrower than Gong's, and Weflow isn't an integration platform with a connector catalogue.
• MCP: the official read-only connector gives Claude, ChatGPT and other assistants transcripts, summaries, playbooks, forecast calls and pipeline metrics. An admin switches it on per workspace, and a separate toggle decides whether assistants read full transcripts or only summaries.
• Raw data: the REST API bulk-exports transcripts, metadata, scores and signals as JSON or CSV into BI tools such as Tableau and Looker. There's no native Snowflake, Databricks or BigQuery connector, so teams use the API to load a warehouse.

What Gong gives a team that keeps Outreach

Gong invented this category and still has the deepest conversation analytics. Its telephony and integration reach is the widest of the three. The tradeoff is that Salesforce write-back, warnings and coaching are capped or gated behind extra licenses, and much of the value lives in Gong's own interface.

Gong's call page shows that analytical depth well, including an AI topic track that segments the whole recording by subject.

Gong imports calls from about thirty dialers, plus its own

Gong's phone coverage is the broadest here. It imports recordings by API from about 30 telephony systems, including Outreach, Aircall, Dialpad, Five9, RingCentral, Talkdesk and Zoom Phone.

Gong also has its own Twilio-powered dialer:

• An Engage seat gets the web and mobile dialer, inbound and outbound.
• A Foundation seat gets the mobile dialer only, calling out from a verified personal number.

Gong AI Data Extractor fills up to 20 existing CRM fields

Gong's AI Data Extractor writes answers from calls into CRM fields without the rep doing anything. It's a real capability, with four constraints:

• A workspace can publish at most 20 extractors, and only a business admin creates them.
• Extractors write only into fields that already exist in the CRM and are imported into Gong.
• Each run overwrites the previous value when newer information appears, so earlier answers aren't kept.
• Field updates cost extra on top of a recording-only license, and they do less for teams not running the full Gong suite.

Gong deal boards can also fill one text field, such as next steps, with AI-suggested updates.

Gong scorecards need the Enable license and setup time

Gong offers configurable scorecards from six templates, scored by a manager or automatically by AI Call Reviewer. Three conditions come with it:

• Scorecards and call scoring require the paid Enable Essentials or Enable license.
• Scorecards need setup and tuning before managers trust them.
• When more than three team members join a call, at most three get an automatic scorecard.

Gong's Agent Studio lists AI Call Reviewer as one agent in a fixed catalogue, grouped by the package each agent requires.

Gong deal warnings come as eight fixed types

Gong's AI Deal Monitor offers eight warnings, all defined by Gong: no activity, ghosted, overdue, not enough contacts, no power, pricing not mentioned, red flag, and stalled in stage.

You can switch each on or off and change when it triggers. You can't define a new one, so a risk specific to your motion, like a missing partner sign-off, has no way to become a warning.

Gong Forecast rolls up rep submissions by forecast category

In Gong Forecast, reps submit a number per forecast category with notes. Managers see team totals with target and coverage, and move up and down the hierarchy.

A trend chart tracks the team's and manager's forecasts week by week. An accuracy report compares past submissions with actual sales per person. Gong Forecast is a separately priced application, so it needs its own justification at renewal.

Gong connects through about 450 integrations, a capped API and metered MCP

Gong's reach into the rest of your stack is wide, with limits on how data leaves it:

• Integrations: the Gong Collective lists about 450 integrations and partner solutions across CRM, telephony, conferencing, BI, enrichment and workflow tools. That breadth is the widest in this comparison.
• MCP: Gong's server has three tools, each scoped to one account, deal or contact. It returns AI insights rather than transcripts, is read-only, and draws credits on every request.
• Raw data: the API returns transcripts, trackers and scorecards, capped at 3 calls a second and 10,000 a day. Delivery to Snowflake, Databricks, BigQuery or Redshift needs Data Cloud, a separate purchase of about $5,000 a year.

What Outreach Kaia gives a team that keeps Outreach

Outreach is still bought primarily for sequencing, and Kaia has shipped fast through 2026. It's a credible conversation intelligence product for an SDR-to-AE motion that lives in Outreach. Its reach is bounded by Outreach users, Outreach prospects and Outreach's own interface.

Kaia records Outreach Voice calls and imports Orum and Nooks

Kaia records calls made through Outreach Voice, Outreach's own dialer. Since February 2026 it also imports recordings made in Orum and Nooks, with the same post-call analysis.

For meetings, Kaia joins Zoom, Teams, Meet and Webex as a bot. It auto-joins only meetings that have an Outreach prospect on the invite and sit on a calendar synced with Outreach. Kaia can also analyze a recording the meeting platform made, without joining.

Kaia Deal Agent fills opportunity fields on one org-wide methodology

Kaia's Deal Agent writes strong field updates. Each opportunity field updates automatically, only when empty, or only after a rep confirms. It stays silent unless it finds explicit evidence in the transcript.

The limits show up once more than one team uses it:

• Deal Agent runs one org-wide configuration on a single methodology.
• Prompts for the standard methodology fields can't be edited.
• Multi-select picklists aren't supported.
• The Salesforce Event gets the summary and a recording link, not the full transcript.

Kaia can also write a Kaia Recording custom object to Salesforce with the summary, link, account and opportunity, once an admin creates it.

Smart Kaia Coach auto-scores calls with weighted coach cards

Smart Kaia Coach, released in April 2026, scores qualifying calls against coach cards automatically. Weighted questions decide what counts most, so scoring stays consistent across managers.

Kaia can also record only the seller's side of a conversation. That lets you coach on calls where recording the buyer isn't allowed, and none of the three tools here matches it.

Outreach flags deal risk through Deal Health and Deal Alerts

Outreach scores every open deal from 0 to 100 on 15 activity signals, comparing it with deals of similar size and stage. Deal Alerts, configured in Agent Studio, flag risk or opportunity by segment, amount or stage and can create a task for the deal owner.

Outreach forecasting rolls up calls, but only in Amplify Pro

Outreach forecasting is capable. Rep calls roll up the hierarchy, managers submit the roll-up or their own number with notes, and every submission stays in an exportable history. Parallel forecasts such as New ARR and Expansion run as separate tabs.

It sits only in Amplify Pro, the top package. A Kaia add-on alone doesn't include it.

Kaia data reaches other tools through 42 MCP tools and the API

Outreach has built more data access than many buyers expect:

• Integrations: 90+ marketplace integrations, and an MCP client that pulls third-party connectors into Outreach's Omni assistant.
• MCP: a 42-tool server, including search and fetch of Kaia summaries and transcripts. Every connection needs a licensed Outreach user with Amplify.
• Raw data: the API returns structured transcripts, the daily export sends each day's recordings to your SFTP, S3 or Azure storage, and Data Sharing reaches Snowflake. Media files can't be exported through the API, and Kaia reporting can't be opened from Salesforce.

How Weflow, Gong and Outreach Kaia price seats and AI usage

Weflow publishes per-seat prices with AI included. Gong publishes its pricing model but no numbers. Outreach is quote-only, with seats plus AI credits.

Weflow prices at about half of Gong because of when it was built. Gong set its pricing when transcription was expensive. We built after transcription and inference costs collapsed, so the same capability runs on a lower cost base. The proof we offer is a side-by-side trial, not a discount.

Before the free Kaia seats end, get these in writing in the post-pilot quote:

• The price for every seat at full headcount, including AEs and CS, not just the pilot team.
• The Amplify package your scope needs: Essentials, Plus, or Pro if you want forecasting.
• The credit allowance, how fast your usage burns it, and what extra packs cost.
• Credit costs for org-wide backfills, and whether the Gong import's Amplify requirement is covered.

Where Gong and Kaia beat Weflow, and where Weflow stops

Gong and Kaia are each the better pick in specific situations, and Weflow has hard limits you should weigh before choosing it.

Where Gong is genuinely stronger

• Gong has the deepest conversation analytics in the category.
• Gong connects to about 30 dialers, runs its own dialer including mobile, and lists about 450 integrations.
• Gong's deal boards are mature, and managers get attached to them.
• Gong holds SOC 2 Type II plus ISO 27001, 27017, 27018 and 27701 certifications.
• Gong is the no-blame purchase.

"I wasn't going to get fired for buying Gong. It wasn't going to happen, right? So it was a very safe choice."

Chris Nethercote, Head of Sales at Weflow, former Gong enterprise customer

Where Outreach Kaia is genuinely stronger

• Kaia gives you one vendor and one contract for sequencing and conversation intelligence.
• Kaia records only the seller's side on calls where recording the buyer isn't allowed.
• Kaia's 42-tool MCP server returns transcripts and includes write tools.
• Deal Agent's only-when-empty and confirm modes are strong field controls.
• Smart Kaia Coach runs automatic coaching inside the tool your SDRs already live in.

What Weflow won't do for an Outreach team

• Weflow does no sequencing and has no dialer.
• Weflow doesn't record calls made on a rep's mobile carrier line.
• Desktop softphone recording is started by the rep, not scheduled.
• Forecast submissions and deal warnings stay in Weflow, not in Salesforce fields.
• Integration breadth is narrower than Gong's, and there's no native warehouse connector.
• Weflow holds SOC 2 Type II, and ISO 27001 is in progress.
• Your stack stays at two vendors: Outreach plus Weflow.

What a free Kaia pilot won't show you about full rollout

A 30-day pilot on a small outbound team can't show you who loses access, where data lands, whether one methodology fits every team, or which calls go unrecorded. Those four questions decide the stack after renewal, so they're the ones to make RevOps test.

Who sees recorded calls without an Outreach login

Kaia recordings live inside Outreach. A CRO without an Outreach login sees nothing unless someone forwards each recording link by hand. Kaia recordings open from Salesforce, but Kaia reporting doesn't.

That matters because transcripts have readers far beyond sales. We hear this on calls regularly:

"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."

Gong has a free collaborator tier that lets people view calls, though collaborators can't connect over MCP.

"This wasn't just about sales and pipeline. This was also about understanding our market – are we putting the right messages through marketing? Are we attracting the right customers? What product gaps are we hearing in calls? Where are we getting pushback on pricing for different products?"

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

The test to run: list everyone who reads Gong today and check which of them can still reach calls under each option.

Whether call data lands in Salesforce or stays in Outreach

Kaia writes a summary to the Event Description and a recording link to an Event field. The full transcript doesn't sync to Salesforce. Weflow writes structured fields from the call, and transcripts land in Salesforce on the recording object.

The test to run: after a pilot call, open the opportunity in Salesforce and build a report on what each tool wrote.

Whether one methodology works for new business and CS

Kaia's Deal Agent runs one org-wide configuration on a single methodology. That fits a single SDR-to-AE motion. It breaks when your new business team runs MEDDPICC and your CS team needs renewal risk and expansion signals from the same kind of call.

Weflow assigns templates per team. Field updates, summaries and scorecards follow the team, so new business and CS each get their own fields from their own calls.

The test to run: put a CS renewal call through both tools and compare what each writes to the opportunity.

Which calls get recorded beyond Outreach prospects and users

Kaia auto-joins only meetings with an Outreach prospect on an Outreach-synced calendar. Outreach also tells customers to uninstall other conversation intelligence bots before using Kaia. CS check-ins with existing customers, partner calls and AE meetings booked outside Outreach can fall outside that net.

The Weflow notetaker joins external meetings for any licensed user who has signed in once, wherever the meeting came from. You can add whole teams to recording at once.

The test to run: pick one week of CS and AE meetings and count how many each tool would have recorded.

What happens to your Gong call history under each option

Your Gong history only stays useful if the transcripts come across with their account links. Kaia's Gong import backfills seven days. Weflow migrates your Gong history at no charge with account links restored. If you pick Kaia, plan its exit from day one.

How much Gong history Kaia and Weflow each bring across

Historical calls are what you need for win-loss analysis. A pile of recordings without account links is close to worthless for that, which is why we restore them.

How to secure Gong recordings before the contract ends

1. Map what you actually hold. Gong keeps calls and their transcripts for up to three years by default, and calls saved to the library are kept indefinitely.
2. Start the migration well ahead of the end date, not in the final week.
3. Move transcripts and their metadata first. They carry everything summaries, field updates and search are built on.
4. Treat video as the part you need mainly for clip libraries, such as onboarding examples of objection handling.
5. Fill gaps with exported files. Weflow bulk-imports video files with a CSV of participants, times and titles, and matches them to Salesforce records itself. About 180 calls take roughly a day.

How to plan a Kaia exit before you sign

Kaia media files can't be exported through the API, and the data stays accessible for 60 days after the contract ends. The daily export sends each night's recordings to your storage, so it covers only recordings made after you switch it on.

• Switch on the daily export on day one, to SFTP, S3 or Azure.
• Each recording arrives as an mp4, a transcript and a JSON metadata file.
• Only recordings made by Kaia users are exported.
• If your storage is down, Outreach retries for 48 hours, then delivery isn't guaranteed.

How Weflow runs alongside Outreach without duplicate activity

Weflow's compatibility mode reads Outreach's tracking pattern and skips emails Outreach already logged, so only one system writes each email to Salesforce. The two things to configure are your custom tracking domain and which tool records each meeting.

How compatibility mode skips emails Outreach already logged

Here's what happens to one email a rep sends from an Outreach sequence:

1. The email goes out through the same mailbox Weflow reads.
2. Weflow holds its sync for about ten seconds (configurable from 0 to 60) so Outreach can log it first.
3. Weflow checks the email body for Outreach's tracking links, such as click.outreach.io.
4. Weflow finds the pattern and steps back, so the email lands in Salesforce once.
5. A one-off email the rep writes in Gmail or Outlook has no tracking pattern, so Weflow captures it.

Weflow capture matches on the sender address held in Salesforce. Sequence emails sent from a separate deliverability subdomain stay with Outreach's own logging.

Which settings to check before Weflow goes live next to Outreach

• Add your custom tracking domain to the exclusion patterns if you use one. The default pattern doesn't recognize a branded domain, and you'll find it in Outreach's admin console under custom domain.
• Connect the Outreach dialer from Weflow's Setup and Integrations page so dialer calls flow in.
• Run one meeting recorder per meeting, so the same call doesn't produce two recordings and two activities.
• Have every licensed user sign in to Weflow once. The notetaker doesn't join meetings for a user who hasn't.

"If you record a meeting, it's not another meeting. It's the same meeting."

Janis Zech, CEO & Co-founder of Weflow

How to take two vendors, not one, to your exec

Outreach plus Weflow keeps your stack at two vendors, and we won't pretend otherwise. The case you take upstairs is one tool out and one tool in, with conversation data in Salesforce at a published price. You win rep adoption by sequencing the rollout and showing managers what replaces what they use today.

How to frame one tool out, one tool in for leadership

Expect the optics objection before the economics come up. We've heard it put plainly on calls:

"I am not sure I want to deprecate one tool to bring on two. The optics of that are never going to look good."

Your proposal doesn't add a vendor. Gong leaves, Weflow joins, and Outreach stays where it is. The real choice is between two stack shapes: one vendor across the whole motion, or a sequencing tool paired with an intelligence layer. If your team already wants to keep Outreach's sequencing, you've half-chosen the second shape.

If one-vendor optics is non-negotiable for your exec, Kaia on Amplify wins that argument. Otherwise, here's a summary you can reuse:

• Vendor count holds: Gong out, Weflow in, Outreach stays for sequencing.
• Data reach: call outcomes land in Salesforce fields that leadership, CS and marketing can reach, at a published seat price with AI included.
• History kept: Gong call history migrates at no charge with account links restored.

How to move reps and managers off Gong without a revolt

Gong attachment is real, and it sits mostly with managers. Name it honestly.

"The reason why I stuck with Gong was like the bubbles. You sort of get like addicted to the bubbles."

Chris Nethercote, Head of Sales at Weflow, former Gong enterprise customer

Here's the rollout order we recommend:

1. Make recording coverage the first milestone. Get every rep signed in and the notetaker on every external meeting.
2. Migrate Gong history before the switch, so reps open Weflow and find their own calls.
3. Show managers the deal board: activity timeline, next meeting and methodology scores on every deal.
4. Turn on coaching scorecards second, once most meetings are recorded.
5. Add deal intelligence and forecasting if you're replacing those too.

KORE Wireless evaluated Gong, chose Weflow on value, and rolled out in five phases: Activity Capture, Conversation Intelligence, Coaching, Deal Intelligence, then Forecasting. Weflow ran the onboarding end to end, including live training with a real-time Portuguese translator for the Brazil team.

Choose Gong, Outreach Kaia or Weflow: which fits your team

Each option fits a specific stack shape and constraint.

Choose Weflow if

• You're keeping Outreach for sequencing and dialing, and you want Outreach dialer calls covered.
• You want calls turned into structured Salesforce fields that leadership, CS and marketing can reach without an Outreach login.
• New business and CS need different methodologies, field updates and scorecards.
• You want a published seat price with AI included, and your Gong history brought across.

Choose Gong if

• You want the deepest conversation analytics and the broadest dialer and integration reach.
• Your managers run on Gong deal boards and your coaching culture is mature.
• Procurement requires ISO 27001 today.
• You'll fund Foundation plus the applications and credits your scope needs.

Choose Outreach Kaia if

• One vendor and one contract is the overriding constraint.
• Your motion is SDR-to-AE and lives inside Outreach on a single methodology.
• You need seller-side-only recording on restricted calls.
• You'll fund the Amplify package your scope requires, including Pro if you want forecasting.

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

Gong vs Outreach Kaia vs Weflow: questions buyers ask

Does Weflow record calls made in the Outreach dialer?

Yes. Weflow pulls Outreach dialer calls in automatically as outbound recordings with audio, speaker separation, transcript, summary and coaching, without video. You connect your Outreach account yourself from Weflow's Setup and Integrations page, and it works during a trial.

Can Weflow record Orum, Nooks, Aircall or mobile phone calls?

It depends on the route. The Outreach dialer is an established connection. A dialer without one is connected by Weflow's team during full implementation, which takes hours to days, so it isn't offered in a trial. Any softphone whose audio runs through the computer, such as Aircall or RingCentral, is recorded by the Weflow desktop app when the rep starts it. Calls on a rep's mobile carrier line aren't recorded.

Will Weflow and Kaia send two bots into the same meeting?

Only if both are recording the same users. Outreach tells customers to run Kaia as the only recorder, and we recommend one recorder per meeting too. The Weflow notetaker joins meetings with an external attendee for licensed, signed-in users, so the users you license decide where it goes.

Can new business and customer success run different methodologies?

Yes, in Weflow. Templates for field updates, summaries and coaching scorecards are assigned per team, so new business can run MEDDPICC while CS runs its own renewal framework. Kaia's Deal Agent runs one org-wide methodology.

Does Weflow do sequencing, or replace Outreach?

No. Weflow has no sequencing, cadences or dialer, and they aren't on the 2026 roadmap. Weflow captures email sent through Outreach as ordinary activity, and compatibility mode skips anything Outreach already logged.

What contract terms does Weflow require around a Gong renewal date?

Weflow's standard contract is 12 months, billed annually, with a 10-user minimum per product or bundle. Seats added mid-term are charged pro rata to the end of the term, and multi-year terms carry discounts. There's no contractual right to reduce seats mid-term, though you can reassign seats when someone leaves.

What security certifications does Weflow hold for procurement?

Weflow is SOC 2 Type II certified, and GDPR and HIPAA compliant. AI processing runs with Zero Data Retention, and customer data is never used to train models. You choose your region: Frankfurt, New York or Sydney. ISO 27001 is in progress, while Gong already holds it.

Who implements Weflow, and is onboarding included?

Weflow implements its own product, and there's no implementation fee. Technical setup takes 30 to 45 minutes with your Salesforce admin and Google Workspace or Microsoft admin. Full time to value runs one to three weeks, most of it spent configuring templates, warnings and forecasts with our team.