flowchart LR A[Lead] --> B[Qualified<br/>Opportunity] B --> C[Solution<br/>Designed] C --> D[Proposal<br/>Submitted] D --> E[Negotiation] E --> F[Won<br/>Closed Booked] E --> G[Lost] style F fill:#E6F4EA,stroke:#137333 style G fill:#FCE8E6,stroke:#D93025
53 Sales Analytics: Pipeline, Territory, and Pricing
53.1 Why Sales Analytics Matters
Public-company guidance is largely a sales-forecast exercise; private-company financing rounds depend on a defensible pipeline.
Sales is the function where the gap between forecast and outcome moves the share price. Sales analytics is the discipline that converts the noisy reality of a sales force — hundreds of conversations, dozens of stages, weekly slippage and acceleration — into a number leadership can stand behind.
For a BI analyst, sales clusters into three jobs. Pipeline analytics answers what is in the funnel, what is moving, and what will close? Territory and quota analytics answers is the field organised right and aimed at the right opportunities? Pricing and discount analytics answers are we leaving money on the table or destroying it through over-discounting? Andris A. Zoltners et al. (2009) argue that sales analytics has shifted from a back-office function to the steering wheel of revenue management — but only when the dashboards are designed for the field, not for the executive suite. Michael V. Marn & Robert L. Rosiello (1992), in the original Managing Price, Gaining Profit HBR article, computed that a 1 percent improvement in average price drops 11 percent to operating profit for the average company — making pricing analytics arithmetically the highest-leverage activity in the function.
TipThe sales-dashboard contract
Three rules separate sales dashboards from every other kind:
- The rep must see themselves. A sales dashboard that does not give the rep a clear view of their own pipeline, attainment, and ranking will not be opened.
- Forecast over snapshot. Stage and stage-weighted pipeline are interesting; the bigger question is what will close. The dashboard must produce a defensible commit number.
- Price is the second number. Volume gets the headlines; realised price quietly eats half the variance. Always show both.
53.2 Pipeline Analytics: From Lead to Booked
The pipeline is the spine of sales analytics. It is the same funnel idea introduced in marketing (Chapter 49), but in B2B and complex-product B2C contexts the funnel has more stages, longer cycle times, and richer per-stage data.
TipThe stage funnel and conversion ratios
The pipeline funnel chart sets sequenced bars at each stage. Stage-to-stage conversion percentages are labelled on the bars; the absolute counts are in the bar labels. The win rate — the conversion from Lead to Won — is the headline number, but it is rarely the most actionable. The middle conversions, especially Qualified Opportunity → Proposal, are usually where the real leakage happens, and that is where coaching budgets land.
TipPipeline coverage and the 3x rule
Pipeline coverage is the ratio of open pipeline to quota for the period. The rule of thumb in many B2B contexts is that pipeline coverage should be at least 3x quota for the current quarter, with sales-cycle-adjusted ratios for longer ones. The visualisation is a stacked bar by sales rep or territory: stacked segments show pipeline weighted by stage, with a target line drawn at 3x quota. Reps below the line are flagged for pipeline-build activity; reps far above the line may be padding.
TipPipeline Coverage Ranges and the Action They Trigger
| Coverage | Interpretation | Manager action |
|---|---|---|
| Below 1.5x | Severely under-pipelined; quota at risk. | Joint prospecting plan; consider re-allocation. |
| 1.5x to 3x | Light; needs immediate prospecting. | Pipeline-build sprint; coaching. |
| 3x to 5x | Healthy for most B2B sales cycles. | Maintain discipline; focus on stage progression. |
| Above 5x | Heavy; possibly inflated or low-conversion. | Audit for stale records; trim the pipeline. |
TipSlip rate and the rolling forecast
Slip rate is the percentage of opportunities that move from one quarter’s commit to the next without closing. A slip-rate trend chart by territory is the single most useful diagnostic for unrealistic forecasting. Combined with a rolling commit line — last week’s commit, this week’s, next week’s — the chart reveals whether forecasts are firming up as the quarter progresses or fragmenting.
WarningThe two-number commit
A commit number is more useful when it has two parts: committed (the rep stakes their credibility on these closing) and upside (these might close with help). Visualised as a stacked bar with committed in one colour and upside in another, the commit becomes a conversation, not a single number under pressure. Andris A. Zoltners et al. (2009) note that two-number commits are a hallmark of sales organisations that consistently land within 5 percent of their forecast.
TipWin/loss analytics
Every closed opportunity is a learning event. A win/loss dashboard tracks reasons (recorded by the rep at close), competitor (when applicable), price-difference-to-quote, decision cycle length, and the role of the BI dashboard’s qualifying field. A simple bar chart of win and loss reasons, with stacked bars showing the distribution by competitor, is enough to drive the quarterly sales-strategy review.
53.3 Territory and Quota Analytics
A territory is a unit of accountability — a geography, an industry vertical, a named-account list, or a hybrid. Territory design is one of the highest-leverage decisions in sales because it determines the opportunity each rep is asked to deliver against.
TipFive Territory-Design Metrics, Each With a Canonical Visualisation
| Metric | What it surfaces | Visualisation lens |
|---|---|---|
| Territory potential (TAM) | Whether the territory has enough opportunity for one rep. | Choropleth or hexbin map coloured by potential. |
| Account count and tier mix | Whether the rep has the right tier mix to hit quota. | Stacked bar per territory by tier. |
| Travel time and density | Whether time is wasted in transit vs in front of customers. | Drive-time isochrone overlays on territory maps. |
| Workload balance | Whether territories are sized for a manageable workload. | Box plot of accounts-per-rep by region. |
| Quota-to-potential ratio | Whether quota is calibrated to potential. | Scatter of quota vs potential per territory. |
The quota-to-potential scatter is the most consequential visual. Each point is a territory; the x-axis is potential; the y-axis is quota. A regression line shows the average mapping. Territories far above the line are over-quoted (rep cannot win); territories far below the line are under-quoted (rep wins easily, the company under-monetises). Both kinds of mis-mapping destroy morale or revenue, and the chart is built specifically to find them.
TipQuota attainment and the rep distribution
A histogram of quota attainment across the rep population is the diagnostic Andris A. Zoltners et al. (2009) call the attainment curve. Healthy organisations show a normal-ish distribution centred slightly above 100 percent with a long right tail. Pathological patterns include:
- Bimodal — many at 60-80 percent, many at 120+, few in between. Indicates two unequal segments of the rep population.
- Bunched at 100 — almost everyone exactly at quota. Indicates either gaming or unrealistic quotas being adjusted.
- Front-loaded — most reps hit quota by mid-quarter, then coast. Indicates quota set too low.
- Back-loaded — most attainment in the last two weeks. Indicates pipeline-quality problems.
The visualisation is a histogram with bins of 10 percent attainment width and reference lines at 80 percent (warning), 100 percent (target), and 120 percent (over-target).
TipSpan of control and manager loading
A bar chart of direct reports per first-line manager across the field organisation reveals whether managers can actually coach. Spans of 8-12 are typical for transactional sales, 4-6 for complex enterprise. Outliers — a manager with 18 reports in an enterprise org — show up immediately.
53.4 Pricing and Discount Analytics
Michael V. Marn & Robert L. Rosiello (1992)’s central observation — that a 1 percent price improvement drops 11 percent to operating profit — is what makes pricing analytics the highest-leverage exercise in the function. Yet pricing dashboards are the least common of the three sales-analytics families because the data is hard to assemble, requires joining quote, order, and finance systems, and forces the function to confront the gap between list price and what the company actually realises.
TipThe price waterfall
The price waterfall is the canonical pricing visual. It walks from list price down through every discount layer to net realised price.
flowchart LR A[List Price] --> B[On-Invoice<br/>Discounts] B --> C[Volume<br/>Rebates] C --> D[Cash<br/>Discounts] D --> E[Promotional<br/>Allowances] E --> F[Distributor<br/>Margins] F --> G[Co-op and<br/>Marketing] G --> H[Net Realised<br/>Price] style A fill:#E8F0FE,stroke:#1A73E8 style H fill:#E6F4EA,stroke:#137333
Each step is a downward bar; the cumulative loss is the pocket-margin gap. The chart is best built per product family or per customer tier so that variance across the portfolio is visible.
TipRealised-price scatter and the discount audit
A realised-price scatter plots, for every line item over a quarter, the net realised price (y-axis) against the order quantity (x-axis), with each point a transaction. A theoretical price-volume curve (a downward-sloping band reflecting agreed volume discounts) overlays the scatter. Points above the band are wins; points below the band — orders that sold for less than the volume schedule allowed — are leaks. The dashboard adds a slicer for Sales Rep and Customer Tier, and the conversation about the leak becomes specific in seconds.
TipCustomer-level profitability
The customer-level profitability chart sorts customers from most to least profitable (after all discounts, rebates, and serving costs) and plots a Pareto. The familiar finding — the top decile of customers contributes more than 100 percent of profit and the bottom decile is loss-making — is repeated in industry after industry. The visualisation is a horizontal bar chart with the Pareto line overlaid; the bottom-decile customers are flagged in red and become the subject of a focused remediation conversation.
WarningDiscount creep is invisible without the waterfall
Most companies discover discount creep three quarters too late, after gross margin has dropped 200 basis points. The price waterfall, run weekly with a pocket-margin variance vs prior quarter annotation, is the cheapest insurance available against this kind of slow-bleed loss. Build it before the quarter goes wrong.
53.5 Common Pitfalls
CautionWhat goes wrong
- Pipeline value reported without stage weighting. Raw pipeline is fantasy; stage-weighted pipeline is a number you can defend.
- Win rate without segmentation. A company-wide win rate of 22 percent hides the inside-sales team at 35 percent and the field team at 12 percent. The decision is in the segmentation.
- Forecast as a single number. Without committed and upside split, the forecast is a hostage to the most aggressive rep.
- Stale opportunities never closed. Pipeline coverage looks healthy because nothing has been removed. A days-in-stage heatmap surfaces the deadwood.
- Quota equal across territories. Ignores territory potential entirely. The quota-to-potential scatter is the corrective.
- Top-rep celebration without examining quota gaming. A 240-percent attainment rep may be a star, or the territory may be massively under-quoted.
- Pricing dashboards in absolute INR only. Without comparing pocket margin percentage to the prior period, list creep and discount creep cancel and the gross margin rot is invisible.
- Customer profitability sorted only by revenue. Top revenue customers are not always top profit customers; the dashboards must show both rankings.
- No reps allowed below the territory line. Some sales organisations censor underperformer data from the dashboard, which kills its credibility.
- Single-page mega-dashboards. Pipeline, territory, pricing, and incentive analytics each have different audiences and update cadences. Build them as separate pages or apps.
53.6 Illustrative Cases
NoteThree case sketches
Yuvijen Forge Components Ltd. enterprise pipeline cleanup. The B2B sales team builds a Tableau pipeline dashboard with a days-in-stage heatmap. Within two weeks, 31 percent of the reported pipeline turns out to be stale opportunities older than 180 days and not progressed. After the cleanup the headline pipeline drops by 41 crore, but coverage on real opportunities improves and forecast accuracy moves from ±15 percent to ±6 percent in the following quarter.
Yuvijen Telecom territory redesign. Field analytics team builds a Power BI quota-to-potential scatter using third-party market-share data joined to internal performance. Six territories show up well above the regression line — chronically over-quoted, with attainment under 60 percent for three quarters running. The CRO redesigns those territories before the next planning cycle. Attainment in the redesigned territories rises from 56 percent to 92 percent within two quarters; rep voluntary attrition halves.
Yuvijen Stores private-label discount waterfall. Pricing team builds an Excel-and-Power-BI hybrid waterfall on the private-label range. Across the portfolio, average list-to-net realised price has compressed by 4.2 percentage points over 12 months — invisible in the gross-margin report because volume growth had absorbed it. The chart triggers a structured renegotiation with the top three retailers and adds 18 crore to operating profit in the following quarter.
53.7 Hands-On Exercise: Build a Sales Operations Dashboard
NoteThree-page sales dashboard
Aim. Build a three-page sales-analytics dashboard in Power BI that ties pipeline, territory, and pricing to the same opportunities, with rep-level and manager-level views. Tableau equivalents are noted.
Scenario. You are the BI lead in sales operations at Yuvijen Forge Components Ltd. The CRO has asked for a dashboard that lets her see, in the Monday morning ops review, what is in the pipeline and what will close, which territories are over- or under-quoted, and where price is bleeding.
Deliverable. A three-page Power BI report — Pipeline, Territory, Pricing — with rep-level RLS, a manager rollup view, and a CRO summary that consolidates the highest-impact items from each page.
53.7.1 Step 1 — Load and model the data
Use Get Data to load five CSVs:
-
opportunities.csv— OppID, AccountID, RepID, TerritoryID, Stage, Amount, ExpectedClose, CreatedDate, LastStageChange, ProbabilityWeight. -
bookings.csv— BookingID, OppID, RepID, BookedDate, BookedAmount, ProductFamily, NetRealisedPrice, ListPrice. -
quotas.csv— RepID, Period, Quota, AttainmentPct. -
territories.csv— TerritoryID, Region, RepID, Potential, AccountCount, TierMix. -
customers.csv— AccountID, Tier, Industry, Region, GrossProfit_TTM.
Type the columns. Build a DimDate calendar; mark it. Build a DimRep table with RepID, ManagerID, RegionUPN. Build a RepSecurity mapping table for RLS.
53.7.2 Step 2 — Page 1: Pipeline
Build five visuals.
Stage funnel. A funnel visual with stages from Lead through Won, with stage-to-stage conversion labels. A slicer for RepID lets the rep see only their own; the manager sees their rollup.
Coverage ratio bar. A horizontal bar per rep with stage-weighted pipeline, with a reference line at 3x quota for the current quarter.
Days-in-stage heatmap. A matrix with Stage on rows and Days-in-Stage Bucket (0-30, 31-60, 61-90, 90+) on columns. Cell colour: count of opportunities. Old opportunities in late stages light up.
Slip-rate trend. A line chart of percent of last-quarter commit that did not close over the last six quarters per region.
Two-number commit. A stacked bar by region: committed (heavy colour) and upside (light colour), with a target line at quota.
DAX measures:
StageWeightedPipeline =
SUMX(
opportunities,
opportunities[Amount] * opportunities[ProbabilityWeight]
)
CoverageRatio =
DIVIDE(
[StageWeightedPipeline],
SUM(quotas[Quota])
)
SlipRate =
DIVIDE(
CALCULATE(COUNTROWS(opportunities),
opportunities[ExpectedClose] < TODAY()
&& opportunities[Stage] <> "Won"
&& opportunities[Stage] <> "Lost"),
CALCULATE(COUNTROWS(opportunities),
opportunities[ExpectedClose] < TODAY())
)Tableau alternative: funnel as a sorted bar; coverage as a bar with a reference line; days-in-stage heatmap native; slip rate as a line; two-number commit as a stacked bar.
53.7.3 Step 3 — Page 2: Territory and quota
Build three visuals.
Quota-to-potential scatter. Scatter plot with Potential on x-axis, Quota on y-axis, points coloured by Region, sized by RepCount. Fit a regression line; conditionally flag territories more than ±25 percent off the line in red. This is the chart that reveals territory mis-mapping.
Attainment histogram. A histogram of rep attainment percentage with reference lines at 80, 100, and 120. Pattern of distribution (normal, bimodal, bunched) reveals quota health.
Span-of-control table. A table per first-line manager with RepCount, Average Attainment, Voluntary Attrition, sorted by reps-per-manager. Conditional formatting flags spans above 12 in enterprise.
Tableau alternative: scatter native with trend line; histogram via binned dimension; table native.
53.7.4 Step 4 — Page 3: Pricing
Build three visuals.
Price waterfall. Power BI’s native Waterfall visual with stages from List Price through every discount layer to Net Realised Price. Per ProductFamily slicer; the chart redraws to that family.
Realised-price scatter. Scatter with Quantity on x-axis, NetRealisedPrice on y-axis, with the agreed volume-discount band as a calculated overlay. Points below the band coloured red; the count is shown in a card above the chart.
Customer profitability Pareto. A horizontal bar chart of customers sorted by GrossProfit_TTM descending, with a cumulative percentage line. The bottom-decile customers (negative or near-zero profit) are highlighted in red.
Tableau alternative: waterfall via Gantt marks; scatter native; Pareto via dual-axis with running sum line.
53.7.5 Step 5 — CRO summary
Build a fourth page that consolidates the highest-impact items from each of the three pages: top three pipeline risks, top three over-quoted territories, top three pricing leaks, all with one-sentence callouts written by the analyst. This page is the slide the CRO actually uses on Monday — the three operational pages are the evidence behind it.
53.7.6 Step 6 — Row-Level Security
Implement Power BI RLS:
- Rep role. Rep sees only their own opportunities, bookings, quota, attainment.
- Manager role. Manager sees their direct reports’ rollup.
- Regional VP role. Sees their region.
- CRO role. Sees everything.
Test by viewing as each role to confirm scope; enable workspace audit logs.
53.7.7 Step 7 — Cadence and forecasting protocol
Set a Monday 6 a.m. refresh on the dataset and an automated email digest to the manager population at 7 a.m. with the previous Friday’s commit, the change since last Friday, and the three biggest movers. The forecasting protocol is:
- Reps update opportunities by 5 p.m. Friday.
- Managers commit by 5 p.m. Friday.
- BI snapshots the dataset Saturday 6 a.m.
- CRO summary lands by Monday 7 a.m.
Without the cadence the dashboard becomes a museum exhibit; with it, it becomes the operating heartbeat of the function.
TipConnect to the Visualisation Layer
Sales analytics relies on the visualisation grammar that has been the spine of this book. Funnels (Chapter 49) carry pipeline. Heatmaps (Chapter 12) surface days-in-stage. Histograms with reference lines (Chapter 21) carry attainment distributions. Scatterplots with regression lines (Chapter 22) reveal territory mis-mapping and pricing leaks. Waterfalls (Chapter 12, Chapter 50) carry the price walk-down. Pareto charts (Chapter 11, Chapter 51) order customers by profit. Mobile design (Chapter 47) puts the rep view on a phone. The storytelling discipline (Chapter 48) is what turns a stage-weighted pipeline number into the one sentence that frames the Monday operations review.
TipFiles and Screen Recordings
Power BI three-page sales operations dashboard with RLS (yuvijen-forge-sales-ops.pbix), Tableau equivalent (yuvijen-forge-sales-ops.twbx), workshop dataset (yuvijen-forge-sales-data.xlsx), sample weekly CRO summary export (yuvijen-forge-cro-summary.pdf), and a screen recording of the dashboard tour (yuvijen-forge-sales-ops-walkthrough.mp4) will be embedded here.
Summary
| Concept | Description |
|---|---|
| Sales-Dashboard Contract | |
| Rep Sees Themselves | Sales dashboard not opened by the rep gives no rep view of pipeline and attainment |
| Forecast over Snapshot | Stage and stage-weighted pipeline matter; commit number matters more |
| Price Is the Second Number | Volume gets headlines; realised price quietly eats half the variance |
| Three Sales Jobs | |
| Pipeline Analytics | What is in the funnel, what is moving, what will close? |
| Territory and Quota Analytics | Is the field organised right and aimed at the right opportunities? |
| Pricing and Discount Analytics | Are we leaving money on the table or destroying it through over-discounting? |
| Pipeline Visuals | |
| Stage Funnel | Sequenced bars per stage with conversion percentages labelled |
| Coverage Ratio Bar | Stage-weighted pipeline as bars with target line at 3x quota |
| Days-in-Stage Heatmap | Old opportunities in late stages light up — the pipeline cleanup view |
| Slip-Rate Trend | Slipped-from-commit percentage trended over six quarters per region |
| Two-Number Commit | Committed plus upside split makes the forecast a conversation |
| Win-Loss Reasons | Bar of win and loss reasons, stacked by competitor, drives strategy |
| Territory Metrics | |
| Territory Potential | TAM by territory; choropleth or hexbin coloured by potential |
| Account Count and Tier Mix | Stacked bars of accounts per territory by customer tier |
| Travel Time and Density | Drive-time isochrones overlaid on territory maps |
| Workload Balance | Box plot of accounts-per-rep by region |
| Quota-to-Potential Scatter | Most consequential territory view — reveals over- and under-quoted territories |
| Quota Attainment Patterns | |
| Healthy Distribution | Normal-ish distribution centred slightly above 100 percent with a long right tail |
| Bimodal Distribution | Many at 60-80 and many at 120+ — two unequal rep segments |
| Bunched at 100 | Almost everyone at 100 — gaming or unrealistic quotas being adjusted |
| Front-Loaded Attainment | Most reps hit quota by mid-quarter then coast — quota set too low |
| Back-Loaded Attainment | Most attainment in the last two weeks — pipeline-quality problem |
| Pricing Visuals | |
| Price Waterfall | Walks list price down through every discount layer to net realised price |
| Realised-Price Scatter | Quantity vs net realised price with agreed volume-discount band |
| Customer Profitability Pareto | Sort customers by profit; Pareto reveals loss-making bottom decile |
| Pocket-Margin Variance | Compare pocket margin percentage to prior quarter weekly |
| Price-Profit Leverage | 1 percent price improvement drops 11 percent to operating profit (Marn-Rosiello) |
| Common Pitfalls | |
| Pitfall: Unweighted Pipeline | Raw pipeline is fantasy; stage-weighted pipeline is defensible |
| Pitfall: Unsegmented Win Rate | Company-wide win rate of 22 hides inside-sales 35 and field 12 |
| Pitfall: Single-Number Forecast | Without committed and upside split the forecast is hostage to one rep |
| Pitfall: Stale Opportunities | Pipeline coverage looks healthy because nothing is removed |
| Pitfall: Equal Quotas | Quota equal across territories ignores territory potential |
| Pitfall: Pricing in INR Only | Without pocket-margin percentage versus prior, list and discount creep cancel |
| Pitfall: Customer Sort by Revenue | Top-revenue customers are not always top-profit customers |
| Pitfall: Mega-Dashboards | Pipeline, territory, pricing have different audiences — separate pages |
| Hands-On Sales Ops Dashboard | |
| Page 1 — Pipeline | Stage funnel, coverage bar, days-in-stage heatmap, slip-rate, two-number commit |
| Page 2 — Territory | Quota-to-potential scatter, attainment histogram, span-of-control table |
| Page 3 — Pricing | Price waterfall, realised-price scatter, customer profitability Pareto |
| Page 4 — CRO Summary | Top three pipeline risks, over-quoted territories, pricing leaks consolidated |
| RLS Roles | Rep, Manager, RVP, CRO roles with separate scopes |
| Monday Cadence | Friday-update, Saturday-snapshot, Monday-CRO-summary protocol |