Core Intelligence
Operating Dashboard
Real-time view of revenue, margin, and pipeline
Margin Intelligence
Know which channels and SKUs make money
Forecast Confidence Engine
Revenue forecasts you can actually trust
Advanced Analytics
Blended ROAS Dashboard
True return on ad spend across every channel
Cohort LTV Tracker
Lifetime value by acquisition cohort and channel
SKU Profitability
Profit and loss at the individual product level
More Features
Pipeline Health Monitor
Spot deal risks before they hit revenue
Weekly Operating Report
Auto-generated briefs for your Monday review
All 14 features
Featured
Data Connection Layer
Connect HubSpot, Stripe, Shopify and 10+ tools in minutes. No code, no CSV uploads.
Learn moreCRM
HubSpot
Sync CRM deals, contacts, and pipeline data
Salesforce
Pull opportunities, accounts, and forecasts
Pipedrive
Connect deals and activity data
Finance & Commerce
Stripe
Revenue, subscriptions, and payment data
Shopify
Orders, products, and store analytics
QuickBooks
P&L, expenses, and accounting data
Marketing
Google Ads
Campaign spend, clicks, and conversions
Meta Ads
Facebook and Instagram ad performance
All 14 integrations
5-minute setup
Connect your first data source
OAuth login, select metrics, and start seeing unified data. No CSV uploads or developer time.
See all integrationsIndustries
eCommerce
Unified margins, ROAS, and LTV for online stores
D2C Brands
True contribution margin across every channel
B2B SaaS
Pipeline-to-revenue visibility for operators
Use Cases
Find Profit Leaks
Spot hidden costs eating your margins
Weekly Operating Review
Run your Monday review in 15 minutes
Replace Manual Reporting
Eliminate 4-6 hours of spreadsheet work
More
True ROAS
Blended return on ad spend across all channels
Revenue Forecast
Data-backed forecasts your board trusts
All industries & use cases
Popular use case
Find Profit Leaks
Most operators discover 8-15% of revenue leaking through hidden costs within the first week.
See how it worksLearn
Blog
Operating insights for founders and COOs
Glossary
Key terms in operating intelligence
What is Operating Intelligence?
The category explained in plain English
Use Cases
Weekly Operating Review
Run your Monday review in 15 minutes
Replace Manual Reporting
Eliminate 4-6 hours of spreadsheet work
Margin Visibility
Know which channels and SKUs make money
New on the blog
How to run a Weekly Operating Review without 3 hours of prep
The exact process operators use to arrive briefed — without touching a spreadsheet.
Read the postSales Forecasting
A bottom-up forecast (also called a pipeline-based forecast or deal-level forecast) is a sales forecasting method that starts with every open opportunity in the CRM, assigns a probability-weighted value to each deal based on its stage, and rolls the numbers up from rep to team to company total. The forecast is grounded in what exists in the pipeline — not in a target divided by territory.
Operators who rely solely on top-down targets set a number and ask reps to hit it. That works for goal-setting but fails for forecasting. A quota of $500K says nothing about whether $500K of pipeline actually exists at a close-able stage. A bottom-up forecast answers that question: given the deals we have, at their current stages, what should we expect to close?
For B2B sales teams with 12+ months of CRM history and consistent stage definitions, a well-calibrated bottom-up forecast lands within 10-15% of actual closed revenue. Below 6 months of history, the stage probabilities are guesses — and the forecast reflects that. The method is only as good as the data underneath it.
A bottom-up forecast differs from a top-down forecast in origin. Top-down starts with a market or segment target and allocates downward. Bottom-up starts with pipeline reality and aggregates upward. Most mature revenue operations teams use both — bottom-up for the current quarter, top-down for the annual plan.
A bottom-up forecast is the closest thing an operator has to ground truth. It doesn't predict what should happen — it predicts what will happen based on the pipeline that exists right now.
The consequence of not having one is specific. A company sets a $1.2M quarterly target based on top-down planning. By week 6, the pipeline contains $1.5M in total value — which looks like enough at a glance. But a bottom-up analysis reveals that $480K of that pipeline is in Stage 1 (discovery), which converts at 8%. The probability-weighted forecast is $740K. The company is heading for a $460K miss, and the top-down target alone didn't surface it.
Operators who run a bottom-up forecast weekly catch these gaps 4-6 weeks earlier than those who rely on rep self-reported commits. The weekly cadence matters because pipeline changes fast. Deals slip, new opportunities enter, and win rates vary by stage. A bottom-up forecast recalculated weekly against the actual pipeline reflects those shifts in near-real-time — giving the operator time to adjust: add pipeline, accelerate deals, or reset expectations before the quarter closes.
A bottom-up forecast follows a four-step process from individual deals to company total.
Step 1: Deal-level data from the CRM
Pull every open opportunity with a close date in the forecast period. Required fields: deal value, current stage, close date, last activity date, deal owner. Missing any of these fields makes the deal un-forecastable — it should be flagged, not estimated.
Step 2: Stage probability assignment
Assign a win probability to each stage based on historical close rates — not assumptions. Example from a real B2B SaaS pipeline:
Stage 1 — Discovery: 8% win rate
Stage 2 — Qualification: 18% win rate
Stage 3 — Demo/Evaluation: 35% win rate
Stage 4 — Proposal: 52% win rate
Stage 5 — Negotiation: 72% win rate
Stage 6 — Verbal commit: 88% win rate
Multiply each deal's value by its stage probability to get the weighted value.
Step 3: Rep-level rollup
Sum the weighted values for each rep. This is the rep's probability-weighted forecast. Compare it against the rep's quota and their historical forecast accuracy. A rep who consistently over-forecasts by 20% needs a haircut applied to their number.
Step 4: Team and company rollup
Sum all rep forecasts to get the team number. Apply any historical adjustment for the team's collective accuracy. Present as a range: committed (deals in Stage 4+), probable (Stage 3+), and total pipeline (all stages). The committed number is what you staff against. The probable number is what you plan for.
The output should look like this:
Company bottom-up forecast — Q2 2026:
- Committed (Stage 4+): $482,000 (72% confidence)
- Probable (Stage 3+): $738,000 (48% confidence)
- Total pipeline weighted: $914,000 (blended)
- Pipeline coverage: 2.9:1 against $520K target
How bottom-up forecast accuracy varies across B2B segments. Accuracy measured as variance from actual closed revenue.
| Segment | Strong Accuracy | Average Accuracy | Below Average | Action if accuracy is low |
|---|---|---|---|---|
| Growth SaaS ($2-10M ARR) | Within 10% | 10-20% variance | 20%+ variance | Calibrate stage probabilities using 12+ months of historical close data |
| Enterprise SaaS ($10M+ ARR) | Within 8% | 8-15% variance | 15%+ variance | Add deal velocity and engagement scoring to stage weights |
| SMB SaaS (high volume) | Within 15% | 15-25% variance | 25%+ variance | High deal volume smooths variance — if still off, stage definitions are inconsistent |
| B2B Services / Consulting | Within 15% | 15-30% variance | 30%+ variance | Services deals have variable scope — build separate probability models for project types |
Sources: Gartner Sales Forecasting Survey 2025, Clari Revenue Intelligence Report 2025, Pavilion COO Survey 2025.
Forecast accuracy improves 12-18% in the first two quarters after switching from rep-committed to probability-weighted bottom-up forecasting (Clari, 2025).
1. Using generic stage probabilities instead of your own close rates
Templates assign 10%, 25%, 50%, 75%, 90% to stages 1 through 5. Your Stage 3 might close at 31%. Your Stage 4 might close at 58%. Using generic percentages introduces systematic error at every level of the rollup. Calculate your own from 4-6 quarters of CRM data.
2. Counting stale deals at full weighted value
A $90K deal in proposal that has had no activity in 28 days should not carry the same weight as one with a demo scheduled for tomorrow. Without an activity-recency filter, bottom-up forecasts include pipeline that has effectively gone cold. Flag deals with no activity beyond 14 days and reduce their weight.
3. Rolling up without a manager adjustment
Reps are structurally optimistic about their own deals. A bottom-up forecast that sums rep pipelines without a documented manager adjustment consistently overforecasts by 10-20%. The adjustment is not pessimism — it accounts for information the CRM cannot capture: competitive risk, budget freezes, champion departures.
4. Forecasting once per quarter instead of weekly
A bottom-up forecast built in week 1 is stale by week 4. Pipeline changes every week as deals progress, stall, slip, or close. Run the full bottom-up rollup weekly. The forecast should be a living number, updated every 7 days.
5. Ignoring close-date accuracy by rep
Reps set close dates optimistically. If 40% of your "close this quarter" deals slip to next quarter, the bottom-up number is overstated by 40% of those deals' weighted value. Track close-date accuracy by rep and discount accordingly — or weight based on deal velocity rather than stated dates.
Fairview's Forecast Confidence Engine connects to your CRM — HubSpot, Salesforce, or Pipedrive — and builds a probability-weighted bottom-up forecast from the live pipeline. Each deal is weighted by your company's historical close rates per stage — not generic probabilities — and rolled up into rep, team, and company views.
The Operating Dashboard shows the bottom-up forecast alongside the quarterly target, with pipeline coverage ratio calculated in real time. When the bottom-up number falls below the target threshold, the Next-Best Action Engine flags the gap: "Bottom-up forecast is $142K below quarterly target. 4 deals in Stage 3 have not progressed in 16 days."
→ See how the Forecast Confidence Engine works
People often use bottom-up and top-down forecasts interchangeably. They start from opposite ends.
| Bottom-Up Forecast | Top-Down Forecast | |
|---|---|---|
| What it measures | Expected revenue from deals currently in the pipeline | Target revenue based on market size, growth rate, or plan allocation |
| Starting point | Individual deals in the CRM | Company or segment-level target |
| Data required | CRM pipeline with stage, value, close date, and activity data | Market data, historical growth rates, capacity models |
| Best for | Current quarter accuracy, weekly pipeline reviews | Annual planning, territory design, headcount modeling |
| Main weakness | Misses revenue from deals not yet in pipeline | Assumes pipeline will materialize to meet the target |
Bottom-up tells you what the pipeline will produce. Top-down tells you what the pipeline needs to produce. Use bottom-up for the current and next quarter. Use top-down for the annual plan. When the gap between them is large — top-down target significantly exceeds bottom-up forecast — that gap is the pipeline generation problem to solve.
A bottom-up forecast builds the revenue prediction from individual deals upward. Each deal in your pipeline gets a probability based on its stage, and those weighted values are summed from rep to team to company. It tells you what your pipeline will actually produce — not what you hope it will produce.
For growth-stage B2B SaaS ($2-10M ARR), landing within 10% of actual closed revenue is considered strong. Early-stage companies should target within 15%. If your bottom-up forecast consistently misses by more than 20%, the stage probabilities need recalibration using historical close data (Gartner, 2025).
Pull every open opportunity from your CRM with a close date in the period. Assign win probabilities by stage using historical close rates. Multiply each deal's value by its probability. Sum by rep, then by team. Present as committed (late-stage), probable (mid-stage+), and total weighted pipeline.
Bottom-up starts with actual pipeline deals and aggregates upward to a revenue number. Top-down starts with a target and allocates downward to territories and reps. Bottom-up reflects pipeline reality. Top-down reflects growth ambition. Mature teams use both — bottom-up for near-term accuracy, top-down for annual planning.
Weekly. Pipeline changes fast — deals enter, slip, stall, and close. A monthly bottom-up forecast is stale within 2 weeks. Weekly recalculation against the live pipeline catches problems early enough to act: accelerate stalled deals, fill coverage gaps, or adjust the committed number before the quarter closes.
The forecast is built from CRM deal data — stage, value, close date, and last activity. If 30% of deals have outdated stages or missing close dates, the forecast is 30% guesswork. Enforcing CRM hygiene rules (mandatory fields, weekly updates) directly improves forecast accuracy. Bad data in means bad forecasts out.
Fairview is an operating intelligence platform that builds bottom-up forecasts automatically from your CRM pipeline — alongside forecast confidence, pipeline coverage ratio, and pipeline health. Start your free trial →
Siddharth Gangal is the founder of Fairview. He built the Forecast Confidence Engine after watching operators present single-number forecasts based on rep self-reports — then discover at quarter-end that 40% of their "committed" pipeline had been sitting in the same stage for 6 weeks.
Ready to see your data clearly?
10 minutes to connect. No SQL. No engineering team. Your first dashboard is built automatically.
No credit card required · Cancel anytime · Setup in under 10 minutes