Revenue Leakage Detection

Revenue leakage occurs when deals that should close successfully instead slip, stall, or disappear from your pipeline without a clear resolution. In most sales organizations, 20-40% of qualified pipeline is lost not to competitors, but to inaction -- deals that simply fade away due to missed follow-ups, declining engagement, or lack of urgency. SalesOS Revenue Leakage Detection uses AI to identify these at-risk deals early, quantify the dollar value at stake, and recommend specific remediation actions to recover revenue before it is permanently lost.

Unlike reactive reporting that tells you what already leaked, this system operates proactively -- detecting early warning signs and alerting your team while there is still time to intervene.

---

Revenue Leakage Dashboard

Navigate to Analytics > Revenue Leakage from the main navigation to access the leakage dashboard. The dashboard provides a unified view of pipeline risk, active leakage signals, and recovery performance.

Dashboard Summary Cards

Four cards at the top provide an at-a-glance view of your leakage posture:

• Revenue at Risk -- Total dollar value of deals currently exhibiting leakage signals. This is the aggregate amount that could be lost if no action is taken.
• Active Leakage Signals -- The number of deals currently flagged with one or more leakage indicators.
• Recovery Rate -- Percentage of previously at-risk deals that were successfully recovered (moved back to healthy progression) over the trailing 90 days.
• Avg Days to Recover -- The average number of days between a deal being flagged and being restored to healthy status, for deals that were successfully recovered.

Leakage Breakdown

Below the summary cards, a segmented bar chart shows revenue at risk broken down by:

• Leakage type -- Which detection signals are triggering (stalled deals, declining engagement, missed follow-ups, etc.).
• Pipeline stage -- Which stages have the most at-risk revenue.
• Owner -- Which reps have the highest concentration of leaking deals.
• Deal size -- Distribution of at-risk revenue by deal value tier.

Click any segment to filter the deal list below to that specific breakdown.

---

Detection Signals

SalesOS monitors every open deal continuously and evaluates it against multiple leakage detection signals. A deal is flagged as "leaking" when one or more of these signals is triggered. The more signals triggered simultaneously, the higher the urgency.

Stalled Deals

A deal is classified as stalled when it has not progressed to the next pipeline stage within the expected timeframe. The system calculates expected stage duration based on:

• Historical average time-in-stage for won deals in the same pipeline.
• Deal size normalization (larger deals are allowed more time before being flagged).
• Industry and segment adjustments based on your historical data.

Threshold: A deal is flagged as stalled when it exceeds 1.5x the expected stage duration with no stage change. At 2x, the signal escalates to critical priority.

Declining Engagement

The engagement detection signal monitors the pattern of interactions between your team and the buyer. It triggers when:

• Email response rate drops -- The buyer's reply rate falls below 30% over the past 14 days when it was previously above 50%.
• Meeting cancellations -- Two or more scheduled meetings are cancelled or rescheduled by the buyer without rebooking.
• Communication gaps -- No inbound communication from the buyer in 10+ business days when the historical cadence was more frequent.
• Shortened responses -- AI detects that buyer emails have become significantly shorter and less substantive (indicating declining interest).

Missed Follow-Ups

This signal detects when your team has failed to execute on planned next steps:

• Overdue tasks -- Tasks associated with the deal are past their due date.
• No follow-up after meeting -- A meeting occurred but no follow-up email or next step was logged within 48 hours.
• Unanswered buyer messages -- An inbound email from the buyer has gone unanswered for 3+ business days.
• Expired proposals -- A quote or proposal sent to the buyer has passed its validity date without acceptance or renewal.

Champion Departure

SalesOS monitors contact changes and organizational signals to detect when a deal's champion or key contact leaves the buyer organization:

• LinkedIn integration detects job changes for contacts associated with open deals.
• Email bounce detection on previously active contacts.
• Buyer-side organizational announcements mentioning restructuring.

Close Date Slippage

Repeated close date pushbacks are a strong predictor of eventual deal loss:

• A deal's close date has been moved out two or more times.
• The cumulative slippage exceeds 30 days beyond the original expected close date.
• The close date has passed without the deal being updated (either closed or date extended).

Budget and Priority Signals

Detected through communication analysis and deal field changes:

• Mentions of budget freezes, reprioritization, or organizational changes in email threads.
• Reduction in the deal amount without corresponding scope change.
• Buyer requests to "revisit next quarter" or similar deferral language.

---

At-Risk Deal Identification

When one or more detection signals is triggered, the deal appears in the At-Risk Deals list on the Revenue Leakage dashboard. Each entry includes:

• Deal name and account -- Linked to the deal detail page.
• Amount -- The revenue at stake.
• Active signals -- Icons and labels for each triggered signal.
• Signal severity -- A composite risk score (Low, Medium, High, Critical) based on the number and type of active signals.
• Days flagged -- How long the deal has been in at-risk status.
• Owner -- The assigned sales rep.
• Recommended action -- The primary AI-suggested remediation step.

Filtering and Sorting

The at-risk deals list supports:

• Sort by: Revenue at risk (highest first), severity, days flagged, close date.
• Filter by: Signal type, severity level, owner, pipeline stage, deal size range.
• Search: Find specific deals or accounts by name.

Priority Scoring

Not all leaking deals are equal. SalesOS assigns a priority score that factors in:

• Deal value -- Higher-value deals receive higher priority.
• Signal count -- Deals with multiple active signals are prioritized over single-signal deals.
• Signal severity -- Critical signals (champion departure, budget freeze) weight more heavily than moderate signals (slight engagement decline).
• Recovery probability -- Based on historical patterns, what is the likelihood this deal can be recovered given its current signal profile?

---

Leakage Quantification

Revenue leakage is quantified in dollar terms to help you understand the financial impact and prioritize resources.

Dollar Value at Risk

For each at-risk deal, the system calculates a risk-adjusted value:

Risk-Adjusted Value = Deal Amount x Loss Probability

Where loss probability is derived from the deal's active signals and historical outcomes of similar deals with the same signal profile. A deal worth $100,000 with a 60% loss probability contributes $60,000 to the "Revenue at Risk" total.

Aggregate Metrics

The dashboard provides aggregate leakage metrics:

• Total revenue at risk -- Sum of risk-adjusted values across all flagged deals.
• Revenue at risk as % of pipeline -- How much of your total open pipeline is currently at risk.
• Projected quarterly leakage -- Based on current at-risk deals and historical recovery rates, the estimated revenue that will be lost this quarter without intervention.
• Recovered revenue (trailing 90 days) -- Dollar value of deals that were flagged as at-risk but were subsequently recovered and closed-won.

Leakage by Category

A breakdown showing which types of leakage represent the most revenue risk:

This breakdown helps you identify systemic issues. If "Missed follow-ups" consistently accounts for the largest share of leakage, it points to a process or capacity problem that needs structural intervention, not just deal-level remediation.

---

Remediation Recommendations

For every at-risk deal, SalesOS generates specific remediation recommendations based on the active signals, deal context, and historical recovery patterns.

AI-Generated Action Plans

Each flagged deal receives a prioritized list of recommended actions. Examples include:

• For stalled deals: "Schedule a value reinforcement call with the economic buyer. Deals at this stage that recovered did so within 5 days of executive re-engagement."
• For declining engagement: "Send a brief check-in email referencing the specific business outcome discussed in your last meeting. Keep it under 3 sentences. If no response in 48 hours, try a different channel."
• For missed follow-ups: "You have 2 overdue tasks on this deal. Complete the proposal revision (due 3 days ago) and send the ROI analysis the buyer requested."
• For champion departure: "Identify an alternate sponsor within the buying committee. Consider reaching out to [contact name] who attended the demo last month."

Action Execution

Recommended actions can be executed directly from the leakage dashboard:

• Schedule meeting -- Opens the meeting scheduler with the deal's contacts pre-populated.
• Send email -- Opens an email compose window with a suggested template based on the recommendation.
• Create task -- Creates a task assigned to the deal owner with the recommended action as the description.
• Reassign deal -- If the current owner is unable to act (capacity, out of office), reassign to another team member.

Tracking Action Completion

Once you take a recommended action, mark it as completed on the deal's leakage card. SalesOS tracks:

• Which recommendations were followed.
• Time from recommendation to action.
• Whether the action resulted in signal resolution (e.g., engagement recovered after sending the email).

This data feeds back into the AI to improve future recommendations.

---

Automated Alerts and Notifications

Revenue leakage alerts ensure the right people are notified at the right time, without requiring constant dashboard monitoring.

Alert Types

• New leakage signal -- Sent when a deal first triggers a detection signal. Delivered to the deal owner.
• Escalation alert -- Sent when a deal's severity increases (e.g., moves from Medium to High or a second signal activates). Delivered to the deal owner and their manager.
• Unresolved reminder -- Sent if a flagged deal has no recorded remediation action within 48 hours. Delivered to the deal owner.
• Weekly leakage summary -- A digest email sent to managers summarizing their team's at-risk pipeline, actions taken, and recovery performance.

Notification Channels

Alerts are delivered via:

• In-app notifications -- Bell icon in the top navigation with a badge count.
• Email -- Detailed alert with deal context, active signals, and recommended actions.
• Slack/Teams -- If integrated, leakage alerts are posted to configured channels or sent as direct messages.

Configuring Alerts

Administrators can configure alert behavior under Settings > Revenue Leakage > Alerts:

• Enable or disable specific alert types.
• Set severity thresholds (e.g., only notify on High and Critical severity).
• Configure escalation timing (e.g., escalate to manager after 24 hours of no action instead of the default 48).
• Set quiet hours to suppress non-critical notifications outside business hours.
• Choose notification channels per alert type.

---

Tracking Recovery

The Recovery section of the dashboard tracks the outcomes of deals that were previously flagged as at-risk. This provides accountability and validates the effectiveness of your remediation efforts.

Recovery Metrics

• Deals recovered -- Count of deals that returned to healthy status after being flagged.
• Revenue recovered -- Dollar value of recovered deals that subsequently closed-won.
• Recovery rate -- Percentage of flagged deals that were successfully recovered (vs. those that were eventually lost or remain at-risk).
• Average recovery time -- Days from flag to resolution for recovered deals.
• Action effectiveness -- Which remediation actions correlate most strongly with successful recovery.

Recovery Timeline

A timeline view shows each deal's journey from healthy to at-risk and back:

• Green segments indicate healthy periods.
• Red/orange segments indicate at-risk periods.
• Markers show when remediation actions were taken.
• Final status (recovered and closed-won, recovered and still open, or lost).

Saved vs Lost Analysis

Compare the characteristics of deals that were successfully recovered against those that were ultimately lost:

• Were recovered deals acted on more quickly?
• Did recovered deals have fewer simultaneous signals?
• Were certain signal types more recoverable than others?
• Did specific remediation actions correlate with success?

This analysis helps you refine your response playbook and set realistic expectations for which at-risk deals are worth pursuing aggressively.

---

Leakage Trends Over Time

Track how your organization's leakage performance evolves over weeks, months, and quarters.

Trend Charts

• Revenue at risk over time -- A line chart showing total revenue at risk by week. A declining trend indicates improving pipeline health.
• Signal frequency -- How often each detection signal is triggered over time. Increasing frequency of a specific signal may indicate a systemic issue.
• Recovery rate trend -- Is your team getting better at recovering at-risk deals?
• Leakage as % of pipeline -- Normalizes leakage against total pipeline size to account for pipeline growth.

Benchmarking

SalesOS provides internal benchmarks so you can evaluate performance:

• Team comparison -- Which teams or reps have the best/worst leakage and recovery metrics?
• Period comparison -- How does this quarter compare to last quarter?
• Stage comparison -- Which pipeline stages contribute the most leakage over time?

---

Configuring Detection Thresholds

Administrators can tune the sensitivity of leakage detection to match their sales cycle and organizational norms. Overly sensitive settings create alert fatigue; overly permissive settings miss real risks.

Accessing Configuration

Navigate to Settings > Revenue Leakage > Detection Thresholds to configure:

Threshold Settings

Per-Pipeline Configuration

Different pipelines may have different velocity norms. For example, an enterprise pipeline naturally has longer stage durations than a transactional pipeline. Configure thresholds per pipeline to avoid false positives:

1. Select the pipeline from the dropdown.
2. Adjust thresholds specific to that pipeline.
3. Save. The pipeline-specific settings override global defaults.

Testing Configuration Changes

After adjusting thresholds, use the Preview button to see how many deals would currently be flagged under the new settings without actually changing your live alerts. This prevents inadvertent alert storms when tightening thresholds.

---

Best Practices

• Respond to leakage signals within 24-48 hours. Historical data across SalesOS customers shows that deals acted on within 48 hours of being flagged have a 3x higher recovery rate than deals where action is delayed beyond one week. Speed of response is the single strongest predictor of successful recovery.

• Focus on high-value, high-recovery-probability deals. Not every at-risk deal deserves equal effort. Use the priority scoring to focus your limited time on deals where intervention is most likely to succeed and the revenue impact is meaningful. It is acceptable to let low-value, low-probability deals exit the pipeline.

• Address systemic patterns, not just individual deals. If "missed follow-ups" consistently represents your largest leakage category, the solution is not to remediate each deal individually -- it is to fix the underlying process (better task management, reduced rep workload, or automated follow-up sequences).

• Review leakage trends weekly as a team. Include leakage metrics in your weekly pipeline review meetings. Discussing at-risk deals as a group creates accountability, surfaces coaching opportunities, and allows managers to offer guidance before deals are lost.

• Tune thresholds quarterly. As your team improves its response to leakage signals, you may need to tighten thresholds to continue surfacing meaningful risk. Conversely, if alert fatigue is causing reps to ignore notifications, loosen thresholds to focus only on the highest-severity signals.

• Use recovery data to build playbooks. Analyze which remediation actions work best for each signal type and codify them into repeatable playbooks. If executive re-engagement recovers 60% of stalled enterprise deals, make that a standard response rather than leaving it to individual rep judgment.

• Do not conflate leakage with legitimate losses. A deal lost to a superior competitor is not leakage -- it is a competitive loss. Leakage specifically refers to deals lost to inaction, neglect, or process failure. Keep this distinction clear in your team discussions to avoid misdirecting remediation efforts.

• Connect leakage prevention to forecasting. Revenue leakage directly impacts forecast accuracy. Deals that appear in your commit or best-case categories but are exhibiting leakage signals should be downgraded in your forecast until the signals are resolved. This prevents the surprise of "committed" deals disappearing at quarter end.

• Set minimum deal value thresholds appropriately. Monitoring every $500 deal for leakage creates noise without meaningful revenue impact. Set the minimum deal value threshold high enough that flagged deals represent real financial consequence, but low enough that your mid-market pipeline is still covered.

• Celebrate recoveries. When a rep successfully recovers an at-risk deal, recognize it publicly. This reinforces the behavior of responding to leakage alerts promptly and demonstrates the system's value to the team.