Pipeline Simulation

Sales leaders constantly face questions that require forward-looking analysis: What happens to our number if we push three deals to next quarter? How much pipeline do we need to generate this month to hit target? What if our win rate improves by five percentage points? Pipeline Simulation in SalesOS provides a structured environment to answer these questions with data-driven scenario modeling rather than back-of-the-envelope estimates.

What Pipeline Simulation Is

Pipeline Simulation is a what-if analysis tool that lets you create hypothetical versions of your current pipeline and model how changes would affect revenue outcomes. You start with your real pipeline data as the baseline, then adjust variables like close dates, probabilities, deal amounts, stage conversion rates, and team composition to see projected impacts on forecast, revenue, and attainment.

Unlike forecasting (which predicts the most likely outcome based on current data), simulation lets you explore alternative futures. What is the best case? What is the worst case? What levers have the highest impact on the number? These answers inform strategic decisions about where to invest time, when to raise hiring requests, and how aggressively to pursue stretch goals.

---

Accessing the Simulator

Navigate to Analytics > Pipeline Simulation from the main navigation. The simulator opens with your current quarter's pipeline loaded as the baseline scenario.

The interface is divided into three areas:

• Scenario panel (left): Lists your saved scenarios and provides controls for creating new ones.
• Modeling workspace (center): The main area where you adjust parameters and see real-time calculations.
• Results panel (right): Shows projected outcomes, comparisons, and visualizations.

You can also access the simulator contextually from a deal record (simulate changes to that specific deal) or from the forecast page (simulate adjustments to hit a specific target).

---

Creating Scenarios

A scenario is a named set of modifications applied on top of your current pipeline baseline. You can create as many scenarios as needed to explore different strategic options.

Starting a New Scenario

1. Click New Scenario in the scenario panel.
2. Name it descriptively (e.g., "Conservative Q3 - 3 Deals Slip" or "Stretch Target with New Hire").
3. Choose the time horizon (current quarter, next quarter, or next 12 months).
4. The system loads your current pipeline data as the starting point.

Adjusting Individual Deals

Select specific deals and modify their properties within the scenario:

• Close date: Move a deal to a different month or quarter to model slippage or acceleration.
• Amount: Increase or decrease the deal value to model upsell opportunities or scope reductions.
• Probability: Override the stage-based probability with your own assessment.
• Stage: Advance or regress a deal to model stage progression.
• Status: Mark a deal as "removed" to model what happens if it is lost, or add a hypothetical deal to model new pipeline.

Adding Hypothetical Deals

Model pipeline that does not yet exist:

1. Click Add Deal within the scenario workspace.
2. Enter the deal parameters (amount, expected close date, probability, stage).
3. Optionally link it to a campaign or source to model the impact of specific pipeline generation activities.

Hypothetical deals appear in the scenario with a dashed border to visually distinguish them from real deals.

Removing Deals

Model pipeline loss by selecting existing deals and clicking Remove from Scenario. The deal remains in your actual CRM; it is only excluded from this scenario's calculations. This is useful for stress-testing your number against lost deals.

---

Scenario Parameters

Beyond individual deal adjustments, you can apply broad parameter changes that affect multiple deals simultaneously.

Win Rate Changes

Apply a blanket win rate adjustment across all deals or specific segments:

• Global adjustment: "What if our win rate improves from 25% to 30%?" Apply +5 percentage points to all deal probabilities.
• Stage-specific: "What if we improve Proposal-to-Close conversion from 40% to 50%?" Adjust only deals currently in the Proposal stage.
• Segment-specific: "What if enterprise win rates drop by 10%?" Apply a negative adjustment only to deals tagged as Enterprise.

The simulator recalculates the weighted forecast in real time as you adjust win rates.

Deal Velocity

Model changes to how quickly deals move through your pipeline:

• Cycle time compression: "What if we reduce average sales cycle from 60 days to 45 days?" Deals with close dates beyond 45 days from their creation date are pulled forward proportionally.
• Stage duration changes: "What if we shorten the Evaluation stage from 3 weeks to 2 weeks?" Deals currently in Evaluation have their close dates moved earlier.
• Velocity by segment: Apply different velocity assumptions to different deal sizes or customer types.

Stage Conversion Rates

Model the efficiency of your pipeline at each stage transition:

Adjusting conversion rates cascades through the pipeline, showing the compounded effect on final revenue.

---

Comparing Scenarios Side by Side

The comparison view places two or more scenarios next to each other to visualize trade-offs and identify the highest-impact strategies.

Comparison Table

Visual Comparison

• Bar chart: Side-by-side bars for each scenario's projected revenue.
• Waterfall chart: Shows what moves the number from one scenario to another (e.g., "+$200K from improved win rate, -$150K from two deal slips, +$300K from new pipeline").
• Timeline view: Month-by-month revenue projection for each scenario overlaid on the same chart.

Sensitivity Analysis

The simulator identifies which variables have the largest impact on outcomes:

• "A 5% improvement in win rate adds $180K to your forecast."
• "Pulling Deal X forward by one month adds $95K to Q3."
• "Losing the top 3 deals by value reduces forecast by 35%."

This helps leaders focus their attention on the highest-leverage actions.

---

Impact on Forecast

Every scenario shows its relationship to your current forecast, making it easy to understand how hypothetical changes translate to attainment.

Scenario vs. Current Forecast

The results panel shows:

• Current forecast: Your existing weighted forecast based on real pipeline data.
• Scenario forecast: The projected forecast if all scenario assumptions hold true.
• Delta: The difference (positive or negative) between scenario and current forecast.
• Attainment projection: What percentage of quota the scenario would achieve.

Gap Analysis

If your current forecast falls short of target, the simulator shows what it would take to close the gap:

• "To hit 100% attainment, you need an additional $400K in weighted pipeline."
• "Improving win rate by 8 percentage points would close the gap entirely."
• "Adding 5 deals at your average deal size of $80K would cover the shortfall."

This gap analysis is particularly valuable during mid-quarter pipeline reviews when the team needs to identify specific actions to get back on track.

Commit and Upside Categories

Scenarios break down projected revenue by forecast category:

• Commit: Deals with 90%+ probability that are virtually certain regardless of scenario assumptions.
• Best Case: Deals that close under moderately optimistic assumptions.
• Upside: Deals that require the scenario's favorable assumptions to close.

---

Team-Level Simulations

Pipeline simulation is not limited to deal-level changes. Model team composition and territory changes to inform hiring, territory planning, and capacity decisions.

Adding a Rep

Model the impact of hiring a new sales representative:

1. Select Team Change > Add Rep in the scenario parameters.
2. Set the ramp period (typically 3-6 months before full productivity).
3. Define expected quota and pipeline generation rate once ramped.
4. The simulator models the new rep's contribution over time, accounting for ramp.

This helps answer questions like "If we hire in June, what is the incremental revenue impact for Q3 and Q4?"

Losing a Territory or Rep

Model attrition or territory changes:

• Rep departure: Remove a rep's pipeline from the scenario and model redistribution. Shows the impact on team quota coverage and which existing reps absorb the load.
• Territory loss: Remove deals from a specific region or segment to model lost market access or strategic de-prioritization.
• Quota redistribution: Model how remaining reps' quotas change and whether they have sufficient pipeline coverage at the new target.

Capacity Planning

The simulator includes a capacity model that estimates:

• Maximum pipeline a team can work based on rep count and average deal load.
• Whether adding pipeline without adding reps would exceed capacity (leading to deal neglect).
• The optimal balance between hiring and pipeline generation investment.

---

Historical Backtesting

Validate your scenario assumptions against historical data to understand how reliable they are.

How Backtesting Works

Select a completed quarter and apply your scenario assumptions retroactively:

1. Choose Backtest and select a historical quarter (e.g., Q4 last year).
2. Apply the same parameter adjustments you are considering for the future quarter.
3. The system shows what would have happened: "If win rates had been 5% higher in Q4, revenue would have been $2.8M instead of $2.5M."

Backtesting Use Cases

• Validate win rate assumptions: Before committing to a scenario that assumes 30% win rates, check whether your team has ever achieved that rate and under what conditions.
• Test velocity improvements: If you are assuming a shorter sales cycle, verify whether past deals at that pace closed at the same rate or if acceleration increased loss rates.
• Calibrate new hire models: Compare your ramp assumptions against the actual ramp curve of recent hires.

Confidence Scoring

Based on backtesting results, the simulator assigns a confidence score to each scenario:

• High confidence (75-100%): Scenario assumptions are within historical norms and have been achieved before.
• Medium confidence (50-74%): Assumptions stretch beyond historical averages but are not unprecedented.
• Low confidence (0-49%): Assumptions exceed anything achieved historically; treat as aspirational.

---

Sharing Scenarios with Managers

Scenarios are collaborative. Share them with managers, peers, or executives to align on strategy and expectations.

Sharing Options

• View-only link: Share a read-only link that shows the scenario results without allowing modifications.
• Collaborative editing: Invite team members to co-edit a scenario (useful for manager-rep planning sessions).
• Presentation mode: A full-screen, chart-focused view designed for meetings and screen sharing.

Approval Workflows

For formal planning processes, attach scenarios to approval workflows:

1. Rep creates a scenario representing their commit for the quarter.
2. Manager reviews the scenario assumptions and either approves or requests adjustments.
3. Approved scenarios become the basis for official forecast submissions.

Comments and Annotations

Add comments to specific scenario parameters explaining your reasoning:

• "Moved Deal X to Q4 because champion is on leave until September."
• "Increased win rate based on new competitive battlecard rollout in June."
• "Removed Deal Y due to budget freeze communicated in last call."

These annotations provide context when reviewing scenarios weeks later or when sharing with stakeholders who were not present during the initial modeling session.

---

Using Simulations in QBRs and Planning Meetings

Pipeline simulation is a powerful tool for quarterly business reviews, annual planning, and weekly pipeline reviews.

QBR Preparation

Before your QBR, create three standard scenarios:

1. Conservative: Remove deals with risk factors, apply lower win rates, model known slippage.
2. Expected: Your honest best estimate based on current data and reasonable assumptions.
3. Stretch: Model what it takes to exceed target, including pipeline not yet generated.

Present all three in the QBR to set realistic expectations while showing the path to upside.

Annual Planning

Use simulation to model next year's targets:

• Reverse-engineer from the revenue target: "To hit $12M next year, we need X pipeline at Y win rate."
• Model the impact of planned hiring: "Two new reps starting in Q1 add $1.5M in capacity for H2."
• Test assumptions about market conditions: "If win rates decline 5% due to increased competition, we need 20% more pipeline."

Weekly Pipeline Reviews

In weekly team meetings, use quick simulations to:

• Model the impact of deals that moved this week (slipped, advanced, or were lost).
• Identify which deals, if closed this week, would have the largest impact on the forecast.
• Set priorities for the coming week based on simulation sensitivity analysis.

---

Exporting Scenario Reports

Export simulation results for offline analysis, inclusion in presentations, or sharing with stakeholders who do not have SalesOS access.

Export Formats

Report Contents

Exported reports include:

• Scenario name, description, and creation date
• Baseline metrics vs. scenario metrics
• Parameter adjustments applied (deal changes, rate adjustments, team changes)
• Visual charts (forecast comparison, waterfall, timeline)
• Sensitivity analysis results
• Confidence scores from backtesting (if applicable)
• Annotations and comments

Scheduled Exports

Configure automatic report generation:

• Weekly scenario refresh: Automatically recalculate saved scenarios against the latest pipeline data and email updated results to stakeholders.
• Variance alerts: Get notified when a saved scenario's projected outcome changes by more than 10% due to pipeline movement.

---

Best Practices

Follow these guidelines to get the most strategic value from Pipeline Simulation.

• Start with the baseline. Always review the current baseline forecast before building scenarios. Understand what the data says today before modeling what it could say tomorrow.
• Name scenarios clearly. Use descriptive names that include the key assumption ("Q3 +5% Win Rate" or "Two Deals Slip to Q4") so you can quickly find and compare them later.
• Limit variables per scenario. Change one or two parameters at a time to understand the isolated impact of each lever. Multi-variable scenarios are useful for planning but make it hard to attribute outcomes.
• Backtest before committing. If a scenario assumes a win rate or velocity your team has never achieved, flag it as aspirational rather than treating it as a reliable plan.
• Update scenarios weekly. Pipeline changes constantly. Refresh your key scenarios weekly to keep them relevant. The scheduled export feature automates this for saved scenarios.
• Use scenarios in 1:1s. Discuss individual rep scenarios in manager-rep 1:1s. "If you close Deal X and Deal Y this month, you hit 90% attainment. What do you need to close them?"
• Model both upside and downside. Optimism bias is common in sales. For every optimistic scenario, create a corresponding conservative one. The truth usually falls between them.
• Share context with annotations. Bare numbers without reasoning are hard to act on. Always annotate why you made specific assumptions so others (and your future self) understand the logic.
• Tie simulations to actions. A scenario is only valuable if it leads to a decision. After modeling, identify the 2-3 concrete actions that would move the real pipeline toward the favorable scenario.
• Archive completed scenarios. After a quarter ends, compare your scenarios against actual results. This calibration exercise improves future scenario accuracy and builds organizational forecasting discipline.