Free Guide: Getting started with Bottom-up Forecasting
We created this free bottom-up forecasting guide to help you run an effective process and get accurate forecasts. The guide covers four parts with practical tips and examples:
- Forecast meetings
- Data & Methods
- Data collection
- Roll-ups

"With Weflow, we’re now capturing all relevant activities and have full transparency into the performance of each sales rep. It’s a game changer."

"Weflow gives us better visibility and predictability of our business."

"Weflow eliminated the need for our VP to ask, ‘Did you follow up with that deal?’. It tracks customer interactions automatically, creating a framework that drives accountability across the team."


"None of the other tools gave us a solution like Weflow. From the beginning, we had a really smooth process."
.webp)
"I had a first introductory call with Weflow. I think I was sold after 15 minutes. There’s no question that the people at Weflow understood the problems that we were trying to solve."

"I’ve worked with Gong before, but Weflow’s simplicity and real-time sync are game-changing."
.webp)


"We use Weflow to auto-capture activity data, run deal reviews, and analyze our pipeline to inform our forecast. Being able to spot deal risks early has improved win rates and pipeline health."

What's Inside
Forecasting meeting cadence
- The full operating rhythm across weekly forecast calls, monthly roll-ups, quarterly business reviews, and the annual review
- Who attends each cadence, from reps and managers up to executives and the CEO at the annual review
- The purpose of each meeting, from deal-by-deal inspection on weekly calls to best-practice sharing in QBRs
Deal evaluation framework
- Why pipeline health inputs at the deal level matter more than ARR or MRR outputs when judging forecast quality
- How to standardize rep inspection using MEDDIC as the default, with MEDDPIC, BANT, SPIN, and Challenger as alternatives
- The deal signals to track per opportunity: time in stage, age, email reply rate, velocity, close date and amount changes, activity volume, CRM score
Data collection and roll-up
- What to automate versus capture manually, covering call logging, email logging, transcripts, and recurring deal signals
- Which manual inputs still need operator discipline, including forecast calls, roll-ups, and AI-generated notes that require review
- The 5-step roll-up process: unify forecasts, segment by geo or product, share with leadership, gather cross-functional feedback, refine

Janis Zech
Janis Zech is the co-founder and CEO of Weflow, the modular Revenue AI Orchestration platform. He co-hosts the RevOps Lab podcast, where he sits down with RevOps leaders and sales operators to unpack how they run revenue teams, forecast pipeline, and use AI to get more out of Salesforce. At Weflow, Janis focuses on helping revenue leaders turn messy CRM data into reliable forecasts and better sales execution. His angle on the podcast and blog is always practical: what's actually working inside high-performing revenue orgs, and what's just noise.
Go Deeper
Bottom-Up Sales Forecasting: A 4-Step Process for Accurate Roll-Ups
#21 Creating an effective forecasting process
Free Sales Forecasting Cheat Sheet
Frequently asked questions
What is bottom-up forecasting and how is it different from top-down forecasting?
Bottom-up forecasting builds the number from individual rep pipeline submissions, rolled up through managers and leadership into a unified model. Top-down starts with a revenue target and works backward to assign quotas. The difference matters because bottom-up gives you deal-level visibility and accountability — you can inspect why a number is what it is, not just accept it.
Do I need a dedicated forecasting tool or can I run this process in a spreadsheet?
You can start with a spreadsheet, but the guide specifically calls out automated data collection — call logging, email logging, deal signals like time in stage and close date changes — as critical to accuracy. A spreadsheet won't capture those signals automatically, which means reps are doing manual entry and your data quality will drift. A CRM with some automation layer is the practical minimum for this to work at scale.
Which parts of the data collection process should stay human-led versus automated?
Automate everything you can — call logs, email logs, deal signal tracking, and forecast snapshots. Keep humans in the loop for forecast call submissions, roll-up reviews, and meeting notes (the guide flags AI-generated notes as useful but worth checking for false entries). The goal is to reduce rep data entry burden while keeping manager judgment in the process where it actually matters.
What data and CRM hygiene do I need in place before this process will actually work?
At minimum, you need defined pipeline stages, a sales methodology applied to deals (the guide recommends starting with MEDDIC), and consistent opportunity fields that reps understand and can calculate themselves. If your stage definitions are fuzzy or reps are skipping fields, the roll-up in Step 4 will just aggregate bad data faster.
How do I know if my bottom-up forecast is actually accurate and not just a number reps are gaming?
The guide points to historical snapshots as the key quality check — if you're capturing weekly or monthly roll-up snapshots, you can compare forecast submissions against actual closes over time and spot patterns in rep sandbagging or over-calling. Deal signals like number of close date changes and opportunity age also give managers concrete data points to push back on during the weekly Thursday or Friday forecast meeting.
How often should I run the full roll-up, and when does the cadence actually need to change?
The guide lays out a four-layer cadence: weekly forecast meetings with reps, monthly roll-ups with leadership, quarterly business reviews with the full team, and an annual review. Start with monthly roll-ups if weekly feels like too much overhead, but move to weekly once your data collection is clean enough to make it worth the time. The cadence should tighten as your pipeline volume and deal complexity grow.