Product & Capabilities
Explore Weflow's core capabilities: from automatic activity capture and pipeline inspection to CRM data quality and deal health monitoring.
- FAQs
- Product & Capabilities
What features are included in Weflow's activity capture module?
Weflow Activity Capture is a server-side sync solution that automatically logs emails, calendar events, meetings, and contacts from Google Workspace or Microsoft 365 into Salesforce as native records. No rep action is required. The system runs in the background and captures activity without relying on rep behavior. (Uber, one Weflow customer, reported 99.9% of activities captured, though results vary by org.)
The module covers four core areas:
Email Capture: Logs all inbound and outbound emails as EmailMessage or Task objects, preserving From, To, CC, BCC fields, HTML body, and attachments. Internal emails are excluded when all senders and recipients are from internal domains, and admins can configure custom domain and email-body exclusion rules.
Calendar and Meeting Capture: Syncs calendar events as native Salesforce Events, with one parent Event per meeting and child Events per attendee for clean activity counts and reporting. Each event is mapped to the right account, contact, and opportunity. Weflow also includes a compatibility mode that deduplicates against sequencing tools like Outreach, Salesloft, Clay, and Apollo, so you never get duplicate activity records in Salesforce.
Contact Capture: Auto-creates or updates Contact records with name, email, title, and company when new external contacts appear in email threads or calendar invites. Admins can restrict creation to existing accounts, set domain, email-body, and custom exclusion rules, configure participant thresholds, and have Opportunity Contact Roles assigned automatically.
Activity Matching: Associates every captured activity with the correct Account, Contact, Lead, and Opportunity using email domain matching, participant matching, and configurable rules. By default, Weflow does not log to an Opportunity when multiple open opportunities exist on the same account. When that happens, reps can select the correct opportunity from the Gmail or Outlook extension, and Weflow applies that mapping across the entire email thread.
Every captured record is a standard Salesforce Task or Event. That means it appears in Activity Timeline, works in reports, triggers Flows and Process Builder automations, and respects your sharing rules and validation rules.
If you ever uninstall Weflow, all captured data stays in your Salesforce org permanently.
What's the difference between Weflow's activity capture and conversation intelligence modules?
Activity Capture and Conversation Intelligence are two separate Weflow modules that cover different data sources and write to different Salesforce objects. Activity Capture syncs emails, calendar events, and contacts from Google Workspace or Microsoft 365 into Salesforce as native records. Conversation Intelligence records and transcribes sales calls on Zoom, Google Meet, and Microsoft Teams, then pushes structured insights and field updates into Salesforce.
Activity & Contact Capture runs as a server-side background service with no browser extension or user action required. It includes email open tracking, auto contact creation, and activity matching. Historical backfill of up to 24 months is available as an add-on on the standalone product and on Revenue AI Foundation; it is included in Revenue AI Business and Revenue AI Enterprise. Everything Activity Capture writes lands on standard Salesforce objects (Task, Event, EmailMessage, Contact), so your reports, dashboards, Flows, and automation rules work immediately.
Conversation Intelligence goes beyond recording and transcription. After each call, it generates AI summaries covering action items, objections, competitor mentions, and next steps, then automatically updates Salesforce fields based on configurable extraction rules. Fields updated include MEDDIC/SPICED qualification criteria, close dates, and custom fields.
It also provides coaching metrics, including talk-to-listen ratios, question frequency, and longest monologues. The searchable transcript library is organized by account, opportunity, and rep, with support for 96+ languages and 250+ pre-built AI prompts.
The two modules don't overlap: Activity Capture does not record calls, and Conversation Intelligence does not capture email or calendar data. Pricing for each module is:
Activity Capture: $19/user/month
Conversation Intelligence: $39/user/month
Revenue AI Foundation (both modules bundled, plus Mobile Copilot, Ask Weflow AI Pro, and Agent Builder Free): $49/user/month
Is Weflow a good activity capture solution for mid-market teams?
Yes. Weflow is built for mid-market B2B teams using Salesforce. RevOps leaders and Salesforce admins at Salesforce-using companies with 100+ users are the primary audience.
Weflow runs as a server-side background service with no browser extension, no email plugin, and no action required from reps in its fully automated mode. In hybrid mode, an optional Gmail extension or Outlook add-in lets reps see and adjust how activities are mapped to Salesforce records. Setup takes 20 to 45 minutes with a Salesforce Admin and a Google Workspace or Microsoft 365 Admin. In fully automated mode, reps don't install anything or change their workflow.
Weflow is not a sales engagement platform. It doesn't send sequences or outbound emails. It captures all inbound and outbound emails, calendar events, meetings, and contacts, then writes them to Salesforce as native Task, Event, and Contact records. Those records appear in Activity Timeline, work in standard Salesforce reports, trigger Flows and Process Builder automations, and respect your sharing rules.
Pricing is $19/user/month with no platform fees and no implementation fees, with a minimum of 10 users. Volume discounts are available for larger teams. Every plan includes:
Guided onboarding
Pre-built activity analytics dashboards
No implementation fees
Ask AI
Agent Builder
24-month historical activity sync-back is available as an add-on for the standalone Activity and Contact Capture product. It's included by default in the Revenue AI Business and Revenue AI Enterprise bundles.
For a 50-person team, that's $11,400/year. For 100 users, $22,800/year.
Does Weflow automatically update Salesforce fields after calls and meetings?
Yes, but with an important distinction: Weflow can be configured to suggest field updates after each recorded meeting and let you review them before anything is written to Salesforce, or it can be set to push updates automatically without manual confirmation. Neither mode is the default out of the box; your admin chooses which workflow fits your team.
In the review-and-approve workflow, Weflow's Conversation Intelligence analyzes the transcript, identifies relevant fields based on admin-configured templates, and presents a side-by-side comparison of the current Salesforce value versus the AI-suggested value. You can approve, edit, or reject each suggestion individually or in batch before anything is written to Salesforce.
In fully automatic mode, field updates are pushed to Salesforce without manual confirmation. Both modes are supported, and the right choice depends on how much your team prioritizes speed versus manual oversight.
Field update templates are fully configurable by admins and support any standard or custom Salesforce object and field, with one exception: lookup relationship fields are not supported for AI updates. That covers objects like Account, Contact, Opportunity, and Lead, as well as any custom objects your org uses. Methodology fields like MEDDIC and SPICED stages are supported out of the box, with 250+ pre-built prompts available.
You can create unlimited templates and assign them to different teams, so your AEs and CSMs each get relevant suggestions without stepping on each other's configurations.
AI meeting summaries are also written automatically to the Salesforce Event object's Description field after every recorded meeting, with no user action required.
Does Weflow automatically create contacts in Salesforce?
Yes. Weflow automatically detects email addresses and calendar attendees that don't yet exist in Salesforce and creates them as standard Contact objects. It runs as a server-side background service, so contacts appear in Salesforce without reps doing anything manually. The feature is part of Weflow Activity & Contact Capture, priced at $19 per user per month.
When Weflow creates a contact, it matches the email domain to an existing Account record and associates the contact automatically. It also sets Opportunity Contact Roles where applicable, which solves one of the most common data quality gaps in Salesforce: empty Contact Roles that break stakeholder mapping and deal health scoring.
Auto-creation isn't enabled by default. You turn it on in the Weflow admin console, where you can also choose between fully automated background creation or manual opt-in through the Gmail or Outlook extension.
Restrict creation to contacts whose domain matches an existing Account only, preventing orphan records
Apply domain and custom exclusion rules to skip addresses you don't want captured
Set participant thresholds to avoid creating contacts from large meetings
Enable or disable automatic Opportunity Contact Role assignment
Weflow respects your Salesforce permission structure. If your org requires a parent Account for contact creation, Weflow won't create the record until one exists.
How does Weflow improve CRM data quality and completeness?
Most Salesforce data quality problems trace back to one root cause: reps don't log their work. Weflow fixes this with server-side activity capture that runs in the background with no browser extension, no email plugin, and no rep action required. Emails and meetings are captured automatically and stored permanently in standard Salesforce objects (EmailMessage, Task, Event) where you can report on them, use them in Flows, and feed them into automations. One customer, Uber, reported 99.9% of activities captured after deploying Weflow.
Weflow also fills the gaps that break stakeholder mapping and deal health scoring. When a contact appears in an email thread or calendar event but doesn't exist in Salesforce, Weflow auto-creates the Contact record, associates it with the matching Account, and populates Opportunity Contact Roles.
Weflow's mapping algorithm uses email addresses as unique identifiers and traverses relationships across Contacts, Leads, Accounts, Opportunities, and custom objects to log activities to the correct records. When multiple open opportunities exist on the same account, you can select the right one from the Gmail Extension or Outlook Add-In, and Weflow remembers that selection for the full thread.
Up to 24 months of historical activity backfill from Google Workspace or Microsoft 365
Full respect for your existing validation rules, field dependencies, permissions, and role hierarchy
Compatibility mode to prevent duplication when tools like Outreach, Salesloft, Clay, or Apollo are also syncing
All data persists in native Salesforce objects if you stop using Weflow, with no lock-in
How does Weflow's CRM data quality compare to Einstein Activity Capture?
The core difference is architectural. Einstein Activity Capture (EAC) streams activity data into Salesforce but does not write it to the database. That means EAC activities can't appear in Salesforce reports, can't trigger Flows, and can't feed automations. Weflow writes every captured email, meeting, and contact as a native Salesforce record (EmailMessage, Task, Event, Contact), so your data is immediately queryable, reportable, and available to any downstream process you've built.
Unlike EAC, Weflow gives you control and coverage across several dimensions that directly affect data quality.
Auto-creation of Contact records and Opportunity Contact Roles when new external contacts appear in email threads or calendar invites
Relationship-graph mapping across Contacts, Leads, Accounts, Opportunities, Custom Objects, and Cases, with manual override via Gmail and Outlook extensions
Email open tracking stored in custom Salesforce fields (last open date, open count) usable in Flows
Historical backfill of up to 24 months from Google Workspace or Microsoft 365
Support for multiple contact relations per email or event, a known EAC limitation
Custom exclusion rules by domain, email body content, and other custom rules
EAC is fully automated with no user controls for mapping adjustments. When auto-relating fails, and practitioners report it frequently does, there's no recourse. EAC also requires individual user OAuth connections that frequently disconnect and require manual reconnection, with failures often silent until reps notice.
Unlike EAC, Weflow uses central admin enrollment via Google Workspace Marketplace or Microsoft Entra ID, so connections don't depend on individual reps.
EAC is included in certain Salesforce editions and may work if you have zero reporting or automation requirements. If your RevOps team needs activity counts by account over 30/60/180-day windows, or your CRO wants data they can build reports on, Weflow is the more practical path. If you stop using Weflow, all captured data stays in Salesforce permanently.
View a detailed comparison: Weflow vs Einstein Activity Capture.
How does Weflow's automatic CRM data capture work?
Weflow's automatic CRM data capture runs as a server-side background service that pulls emails, meetings, and contacts from Google Workspace or Microsoft 365 and writes them directly to native Salesforce objects. Setup starts with installing a central application via the Google Workspace Marketplace or Microsoft 365 Entra ID, which grants Weflow server-level access to email and calendar data for enrolled users.
Once connected, Weflow receives a real-time notification for every email sent or received and every calendar event created, modified, or deleted. For each activity, it performs a lookup against Salesforce using the email address as a unique identifier, matching against Contact and Lead records. From there, it maps forward to Accounts, Opportunities, and Custom Objects. Activities are logged to open Opportunities where a Contact Role exists, or where only one open Opportunity sits under the parent Account.
Weflow stores emails as EmailMessage objects, preserving From, To, CC, BCC, HTML body, and attachments, or as Task objects, depending on your configuration. Calendar events are stored in the native Salesforce Event object with parent-child relationships per attendee, including RSVP status updates, reschedules, and cancellations. Internal-only emails and meeting status notifications are automatically filtered out.
Weflow also detects contacts that don't yet exist in Salesforce and can auto-create them, automatically assigning Opportunity Contact Roles in the process. Admins control this with exclusion rules, such as restricting auto-creation to contacts matching existing Account domains or setting a configurable participant threshold for meetings. Everything writes to standard Salesforce objects in real time, so your reports, Flows, and automations work immediately.
How does Weflow prevent data decay in Salesforce over time?
Weflow prevents data decay in Salesforce by attacking the three root causes at the source: reps not logging activities, contacts going missing, and deal fields going stale.
Weflow Activity Capture runs server-side through Google Workspace or Microsoft Entra ID, automatically syncing emails, meetings, and contacts to Salesforce without any rep action required. Centralized deployment via the Google Workspace App or Microsoft Entra ID App means there are no per-user OAuth connections to maintain, so capture runs continuously without individual reconnections. All activities write permanently to native Salesforce objects (Task, Event, EmailMessage, Contact), making them available in reports, Flows, and downstream automations.
In addition to activity logging, Weflow addresses the most common data quality gaps:
Automatic contact creation for people found in email threads or calendar events who don't yet exist in Salesforce, with Opportunity Contact Role population
Historical backfill of up to 24 months of past emails and meetings from Google Workspace or Microsoft 365 to restore incomplete activity baselines (available as an add-on; up to three years for some customers)
AI-generated field updates from Conversation Intelligence that push methodology fields (MEDDPICC, SPICED, BANT) to Opportunity, Account, Contact, and Lead objects after recorded meetings
An editable deal grid where reps update close dates, amounts, stages, and qualification fields without switching to Salesforce
Configurable warnings, such as "single threaded," "no next meetings scheduled," or "inactive for 14 days," that enforce process compliance in real time
Weflow's deal signals, including engagement score, multi-threading count, and last activity date, depend on complete underlying data. The tight coupling between activity capture and pipeline intelligence ensures those signals reflect reality rather than whatever reps remembered to log.
How does Weflow handle Salesforce activity logging?
Weflow Activity Capture is a server-side background service that automatically logs emails, meetings, and contacts from Google Workspace or Microsoft 365 into native Salesforce objects. Activities sync in real time as they occur. No browser extension or manual action is required from reps in fully automated mode. The Gmail Extension and Outlook Add-In are optional for teams that want reps to see and adjust activity mapping directly from their inbox.
Emails (both incoming and outgoing) are stored as EmailMessage or Task objects in Salesforce, preserving From, To, CC, BCC fields, HTML body, and attachments. Internal-only communications are excluded by default.
Admins can configure additional exclusion rules by domain, email body content, or custom criteria. Calendar events sync to the native Salesforce Event object. Weflow creates one parent Event per meeting and Salesforce creates child Events per attendee, keeping activity counts clean for reporting and coaching dashboards.
Weflow's mapping algorithm uses email addresses as unique identifiers, matching them against the following Salesforce objects:
Contacts
Leads
Custom Objects
Cases
Accounts
Opportunities
The algorithm considers whether an Opportunity is open, whether the contact is a Contact Role, and whether it's the only open opportunity under the parent Account. When multiple open opportunities exist for the same account, reps can select the correct one via the Gmail Extension or Outlook Add-In, and Weflow remembers that selection for the entire thread.
All captured data is written permanently to standard Salesforce objects, so it's queryable, reportable, exportable, and available in Flows and automations. If you stop using Weflow, your data stays in Salesforce with no lock-in.
Weflow can also auto-create contacts that appear in email threads or calendar events but don't yet exist in Salesforce, either as a fully automated background process or as a manual opt-in from your inbox.
How does Weflow map activities to opportunities and prevent incorrect attribution?
Weflow maps activities to opportunities using a relationship-graph-based algorithm that starts with email addresses as unique identifiers. It matches each address against Contacts and Leads in Salesforce, then traverses relationships forward to parent Accounts, Opportunities, and custom objects. This goes beyond standard Opportunity Contact Roles.
For Opportunity-level logging, Weflow applies two conditions. It logs to an Opportunity only if the Opportunity is open and the Contact is set as a Contact Role, or if there is exactly one open Opportunity under the parent Account. If multiple open Opportunities exist for the same Account and the algorithm cannot determine the right one, Weflow deliberately does not auto-map. This prevents activities from landing on the wrong deal and breaking pipeline analytics or deal velocity metrics.
When multiple Opportunities are in play, you can select the correct one via the Gmail Extension or Outlook Add-In. Weflow remembers that selection at the thread level, so every future email in that conversation maps to the same Opportunity without further input. If something does get logged incorrectly, you can unlog the activity and re-log it to a different record directly from your inbox.
Admins get additional controls to tighten attribution:
Condition-based logging rules using any Salesforce field (e.g., "if Account Type = Partner, do not log")
Domain, email body, and custom exclusion rules to filter out noise at the org level
Team-specific configurations so AEs, CSMs, and SDRs can have different mapping behaviors
Compatibility mode that detects activity already logged by sequencing tools like Outreach, Salesloft, Apollo, or Clay before logging, avoiding duplicates
Weflow also filters out noise automatically. Internal-only emails are excluded by default, so activities where all recipients and senders share an internal domain are never logged.
What reporting and analytics does Weflow offer?
Weflow offers reporting and analytics across four areas: pipeline intelligence, deal intelligence, activity analytics, and forecasting. All of it is built on your Salesforce data, so the numbers match your Salesforce reports with no discrepancies between systems.
Pipeline Intelligence includes 30+ pre-built metrics and dashboards out of the box. Named analytics include Waterfall (start pipeline, new opps, amount changes, push count, won/lost, and end pipeline), Pipeline Pacing (pipeline development against goals with overlays for AI projection, commit, and other forecast categories), Pipeline Coverage (open opps across stages vs. quota), Deals at Risk, Team Benchmarks (attainment, open opps, opps created), Opportunity Snapshots, and additional metrics including Sales Cycle Length, Win and Close Rate, and Stage Conversion Rate. Every view supports filters by rep, team, record type, and any Salesforce field.
Deal Intelligence generates 50+ signals per deal, including Close Date Pushed, Engagement Score (0 to 100), Multi-threading, Time-in-Stage, and Inactivity. A Deal Health Score auto-calculates from 0 to 100 with risks and suggested actions. You can configure warnings like "Single threaded" or "No next meetings scheduled" using any combination of Salesforce fields, activity data, and Weflow signals.
Activity Analytics tracks meeting volume, email volume, open rate, reply rate, and responsiveness metrics such as response time. Reps see their own metrics against team averages; managers get full team visibility.
Forecasting includes AI prediction based on an ML model trained on historical conversion patterns, shown alongside Team Forecast and Weighted Forecast. It also includes automated roll-ups across your Salesforce role hierarchy, and forecast accuracy tracking with change history on every call and adjustment. Weflow supports multiple independent forecasts (new logo, expansion, renewal) mapped to different Salesforce fields.
Unlike Einstein Activity Capture (EAC), Weflow writes all captured data to native Salesforce objects (Task, Event, EmailMessage). This means you can report on it with standard Salesforce dashboards, Flows, and automations. EAC historically stored activity data outside Salesforce on AWS, making it non-reportable in standard Salesforce reports and inaccessible to Flows and automations. That is the core architectural difference: Weflow data lives in your Salesforce org from day one.
Explore Weflow's detailed comparison with Einstein Activity Capture.
What pipeline visibility and deal inspection features does Weflow offer?
Weflow's pipeline visibility and deal inspection features are built for RevOps leaders, sales managers, and CROs who need to spot deal risk and track pipeline changes without leaving Salesforce data behind.
The core interface is an editable deal grid with a spreadsheet-like layout. You can update stage, amount, close date, next steps, and custom fields inline, and every edit syncs bidirectionally to Salesforce in real time. You can switch between table and Kanban views, add or remove columns, and build custom views using any combination of Salesforce fields and Weflow deal signals. Views can be saved, shared, and assigned to specific teams.
Weflow generates 50+ deal signals and a Deal Health Score (0 to 100) that flags what's going well, active risks, and suggested actions. Signals include Close Date Pushed count, Engagement Score, Multi-threading depth, Time-in-Stage, and Inactivity days. Admins configure warnings based on any combination of Salesforce fields, activity data, and Weflow signals.
Single-threaded: only one contact engaged on the opportunity
No next meeting scheduled
Inactive for 14+ days (configurable threshold)
Close date pushed multiple times
Warnings surface directly in your pipeline views, and deal alerts can trigger email notifications. Weflow includes pre-built dashboards: Waterfall (start-to-end pipeline movement), Pipeline Pacing (development against goals), Coverage (open pipeline vs. quota by stage), Generation (new pipeline creation), and Team Benchmarks (attainment, open and created opportunities).
Pipeline Change Tracking uses opportunity snapshots to show exactly what changed since your last review: new deals, stage advances, slipped deals, and removed deals.
Does Weflow flag stale opportunities and enforce close date hygiene?
Yes. Weflow flags stale opportunities and enforces close date hygiene through deal signals, configurable warnings, and AI deal scoring, all based on what's in your Salesforce data.
Weflow's Deal Intelligence and Forecasting give you access to 50+ deal signals, and several target staleness and close date discipline directly. The Close Date Pushed signal tracks how many times the close date was moved on each opportunity. The Inactivity signal measures the number of days since anything changed on a deal. Time-in-Stage shows how long an opportunity has sat in its current stage. These signals surface in your pipeline views so you can spot problems before your next forecast call, not during it.
Weflow also provides configurable risk alerts that admins can build from any combination of Salesforce fields, activity data, and Weflow signals:
Close date pushed 3+ times on an opportunity
No activity in 14 days (threshold is configurable)
Below average activity for the current deal stage
Missing key fields like champion, decision criteria, or budget at a given stage
Single-threaded deals with only one contact engaged
No next meeting scheduled
Warnings enforce your sales process without requiring reps to remember checklists, and they can trigger email alerts for follow-up. Weflow's pre-built pipeline analytics also include a Deals at Risk view so you can quickly isolate and act on opportunities showing staleness signals across your pipeline.
Weflow's AI Deal Scoring layers on top of all this, analyzing stage duration, activity frequency, field completeness, and close date slip patterns to generate a 0-to-100 deal health score with specific risk callouts and suggested actions.
Does Weflow provide deal-level signals like single-threading and inactivity?
Yes. Weflow surfaces both single-threading and inactivity as named deal signals, along with 50+ other signals calculated from your Salesforce data, activity patterns, and conversation data.
The single-threading signal flags deals where only one contact is engaged. The inactivity signal tracks the number of days since an opportunity last changed, with a default threshold of 14 days that your admin can configure. Multi-threading is also a dedicated signal that counts the number of prospects involved in an opportunity. Weflow auto-captures contacts and analyzes interaction velocity, so the multi-threading count reflects actual engagement rather than what reps remember to log.
In addition to those signals, Weflow's signal engine covers a broad set of deal health indicators:
Close Date Pushed: number of times the close date was moved
Engagement Score: 0 to 100, based on buyer and seller activities
Time-in-Stage: days in current stage
Amount Changes
Last Activity Date and Next Meeting Date
Contact insights showing whether the right stakeholders are engaged
Deal Health Score: 0 to 100, with risks, strengths, and suggested actions
Admins configure warnings based on any combination of Salesforce fields, activity data, and Weflow signals. These warnings surface directly in your pipeline views and can also trigger email alerts so managers catch risk without waiting for the weekly call.
Deal signals and configurable warnings are part of the Deal Intelligence and Forecasting product at $39 per user per month, billed annually.
What forecasting capabilities does Weflow offer?
Weflow's Deal Intelligence & Forecasting module gives RevOps leaders, CROs, and sales managers a single place to submit, review, and roll up forecasts, inspect pipeline health, and track accuracy over time. The forecast chart displays three overlays side by side: AI Projection, Team Forecast, and Weighted Forecast, plotted against Pipeline, Commit, and Closed bars so you can spot gaps to quota at a glance.
The AI Projection is generated by a machine-learning model trained on historical conversion patterns. It also factors in seasonality. Separately, Weflow surfaces 50+ deal signals that feed deal-level inspection: engagement score, multi-threading depth, time-in-stage, close date push count, and amount changes. Opportunity snapshots track how pipeline values shift week over week, giving managers the context to pressure-test rep calls before the forecast meeting, not during it.
Forecast calls roll up automatically across your Salesforce role hierarchy, so managers and leaders see aggregated numbers without spreadsheet consolidation. Admins configure submission cadences with defined time periods, frequency, overwrite logic, and permissions. Automatic email reminders prompt reps to submit on schedule. Weflow tracks week-on-week and month-on-month changes to every forecast call and manager adjustment, then compares forecasted vs. actual outcomes to measure accuracy over time.
You can run multiple independent forecasts, each with its own cadence and roll-up logic. Common configurations include new logo, expansion, and renewal forecasts. Quotas are set at org, team, and individual levels, with annual entry, auto-monthly distribution, and per-month overrides for ramp schedules. Coverage ratios update in real time.
Pre-built analytics views give you pipeline visibility without building reports from scratch:
Waterfall: tracks start pipeline through new opportunities, amount changes, moved in/out, won/lost, to end pipeline
Pacing: pipeline development over time against monthly, quarterly, and annual goals
Pipeline Coverage and Pipeline Generation tracking
Team Benchmarks and Deals at Risk
From any forecast view, you can drill into the underlying deals, each surfacing 50+ signals, activity insights, and contact insights. Setup takes minutes using standard or custom Salesforce forecast categories. Opportunity snapshots track pipeline changes over time, so you always have a historical record of how pipeline developed and where forecast calls shifted.
Does Weflow track slippage and forecast adjustments week over week?
Yes. Weflow tracks both forecast adjustments and deal slippage on a weekly or monthly cadence, depending on your configuration. Every forecast call and manager adjustment is stored as a snapshot, with full track change history showing exactly when a number changed, who changed it, and by how much. This eliminates the "he said / she said" dynamic that derails most forecast reviews.
Weflow tracks forecast changes and manager adjustments over time, giving you a historical view of how forecasts evolved across the quarter. The Pacing view lets you compare AI Projection, Team Forecast, and Weighted Forecast side by side against pipeline, commit, and closed, so you can see how you're tracking against goal at any point in the quarter. Forecast accuracy tracking compares forecasted versus actual by rep and manager, identifying sandbaggers and optimists so you can calibrate future calls based on actual behavior.
For slippage, Weflow captures opportunity snapshots at regular intervals and runs pipeline change analytics across them. The Waterfall view breaks your pipeline into specific categories:
Start pipeline and end pipeline totals
New opportunities added to the period
Amount increases and decreases on existing deals
Deals moved in or out of the period (pushed close dates)
Won and lost outcomes
You can drill into any change and inspect the specific deals driving it. Weflow also tracks deal-level signals like how many times a close date was pushed and when amounts changed.
Weflow supports week-over-week change tracking and pipeline development analytics in a single view via opportunity snapshots and pre-built pipeline analytics.
Are Weflow features like call scoring, coaching, and pipeline health analysis automated or manual?
Weflow's call scoring, coaching, and pipeline health analysis are AI based and automated by default, with optional manual review where it matters.
Call scoring and coaching: After each meeting, Weflow's AI notetaker records, transcribes, and summarizes the conversation, then auto-generates coaching feedback using pre-built methodology templates covering MEDDIC, MEDDPICC, SPICED, BANT, and others. Each call receives an AI-generated rating based on customizable templates. Managers can review and adjust those ratings, and pre-built conversation insights let you analyze team performance across reps and time periods.
AI field updates push methodology fields like MEDDPICC and BANT directly to Opportunity, Account, Contact, and Lead objects in Salesforce without manual entry.
Deal health analysis: Weflow's AI deal scoring auto-calculates a deal health score from 0 to 100 using an ML model and 50+ signals drawn from CRM, activity, and conversation data. Those signals include Engagement Score (0 to 100), multi-threading counts, time-in-stage, close date changes, and inactivity flags.
Pre-built deal signals surface risks such as inactivity, single-threading, no next meeting scheduled, and close-date pushes. Specific warning thresholds are configurable by admins rather than fixed defaults, so your team defines what counts as a risk condition.
Pipeline analytics: Pre-built dashboards for Waterfall, Pipeline Pacing, Coverage, Generation, Team Benchmarks, and Deals at Risk compute automatically from Salesforce data plus Weflow signals. Weflow creates opportunity snapshots automatically to track pipeline changes over time, replacing manual spreadsheet work.
Admins can configure warning conditions tied to any combination of Salesforce fields, activity data, and Weflow signals. Those warnings surface automatically in pipeline views and can trigger alerts. The core intelligence runs without manual effort, but you keep full control over thresholds and review workflows.
Does Weflow support MEDDIC tracking and compliance monitoring?
Yes. Weflow supports MEDDIC, MEDDPICC, SPICED, BANT, and custom methodologies across three product layers: Conversation Intelligence, Deal Intelligence, and Salesforce field automation. Coaching scorecards also align to Challenger and SPIN.
On the conversation side, Weflow includes 250+ pre-built prompts aligned to sales methodologies including MEDDIC and SPICED. After every recorded meeting, AI summaries are generated using configurable methodology templates, and AI field updates extract structured data from transcripts to populate your MEDDIC fields on any standard or custom Salesforce object. You can assign different summary and field update templates per team.
AI field updates work for any standard or custom Salesforce field, except lookup relationships. Updates can run automatically in the background or in a manual confirmation mode where reps review suggestions before pushing to Salesforce.
For coaching, Weflow provides AI coaching scorecards with structured ratings (1 to 5), aligned to methodologies including MEDDIC, SPICED, BANT, Challenger, and SPIN. Pre-built Conversation Insights and analytics let managers track team performance over time. Coaching templates can be conditionally applied based on opportunity stage or other Salesforce field values, so discovery calls get different MEDDIC coaching than late-stage negotiation calls.
In Deal Intelligence, a MEDDIC panel inside the deal inspection view lets you track fields like Metrics, Economic Buyer, Decision Criteria, and Decision Process. Configurable deal warnings use a condition builder to flag compliance gaps, such as missing MEDDIC fields at specific stages.
Weflow provides guided onboarding and configuration support, including 250+ pre-built prompts and unlimited configurable templates for methodologies like MEDDIC. The full platform deploys in two to four weeks, with technical implementation typically taking an hour.
Try before you buy
We get it. You want to make sure you’re getting the right tool to fit your needs. That's why you should try before you buy. Get your 14-day free trial after the demo.




.avif)

.avif)




.avif)
.avif)
.avif)
.avif)
.avif)
.avif)

.avif)
.avif)




.avif)


