Build and buy: How winning revenue teams make the call
November 4, 2026

TL;DR: A spreadsheet projection is out of date as soon as the next deal moves, and testing a new scenario means rebuilding the model. Sales projections hold up when they run on live deal, engagement and renewal data, with scenarios that update in minutes and new business, expansion and renewal rolled into one number finance can stand behind.
Finance and revenue leaders own the number the board plans around, and for many teams that number still lives in a spreadsheet built on CRM downloads, a renewal list from customer success and a set of assumptions only one person fully understands. The spreadsheet holds up until someone asks a question it was not built to answer, like what happens if two large deals slip a quarter, or how much of next year depends on renewals.
A projection nobody can trace or update quickly turns every board conversation into a defense of the model. You will see what a good sales projection includes, where Excel projections break as the business grows, and what changes when projections run on live revenue data.
A sales projection is an estimate of future revenue built from current pipeline, historical conversion rates and stated assumptions, used to plan hiring, spend and targets. It usually looks a year or more ahead and runs under several scenarios.
A projection and a forecast answer different questions. A sales forecast calls how the current period will land based on the deals in play. A projection asks where revenue could go under a given set of assumptions, such as a higher win rate, a new hiring plan or a change in renewal rates, so it can explore several possible outcomes at once.
Building both on the same pipeline and renewal data means any gap between them comes from a changed assumption, which is exactly what finance wants to discuss.
Whether it lives in a spreadsheet or a platform, a projection holds up when it has these seven inputs.
Each input answers a question the board will eventually ask, so a projection that includes all seven can explain its number as well as produce it.
Excel has earned its place in finance teams, and any honest case for moving projections elsewhere starts with what it does well:
For a young company with one product, a small team and a single revenue stream, that combination is often enough, and a well-built spreadsheet covers what an early-stage team needs before it is ready for dedicated sales forecasting software.
The trouble starts as the business adds reps, segments, products and renewal revenue. Each addition means another export to paste in, another tab to link and another person editing the file, until the spreadsheet is carrying more than it was designed for.
Spreadsheet projections tend to break in five predictable places, and each one gets worse as the business grows.
A projection built from Monday's CRM export misses every deal that moved on Tuesday. Teams refresh weekly or monthly, so the model always describes a pipeline that no longer exists, and the people closest to the deals stop trusting it. The same staleness problem drives most of the cost of spreadsheet forecasting.
Spreadsheets mix data, logic and presentation in one file, so a single bad cell reference or pasted range can change the total without anyone noticing. A familiar version: this week's export has more rows than last week's, the SUM range still stops at the old last row, and the newest deals never reach the projection.
Nothing looks broken, the number is simply lower than it should be, and it goes to the board that way. Sales projections carry that exposure every time someone pastes in a new export.
Finance has one version, sales leadership has another, and the board deck has a third. Reconciling them takes a meeting, and nobody can say with certainty which assumptions changed between the version reviewed last month and the one presented today.
Corpay saw the same pattern before it consolidated on one platform: some sellers tracked activity in Excel, some in email and some in notes, and leaders could not make data-driven decisions from any of it.
Asking what happens if win rates drop five points, or if two large deals slip a quarter, should take minutes. In a spreadsheet, each scenario means copying tabs, re-linking formulas and checking that nothing broke, so teams run fewer scenarios than they should.
New-logo pipeline usually sits in the CRM export, while renewals and expansion live in a customer success tracker or a finance system. Stitching them together by hand makes it hard to see how much of next year depends on retention, which is often the biggest number in the projection.
Spreadsheet projections break where the data goes stale. Outreach builds the forecast on the engagement, conversation and deal data already in the platform, so the number you take to the board stays current.
Moving a projection onto a platform keeps the discipline that makes a good spreadsheet useful, and fixes the five breaks above.
Stages, close dates and deal values update as reps work the deal, and engagement signals show which opportunities have an active buyer behind them. When AI recommends CRM updates from calls and emails and reps approve them, the data feeding the projection stays current without a weekly export.
An AI projection estimates where the period will land based on won business, remaining pipeline and deals likely to pull in. Leaders compare it with the rep and manager commit, and the gap between the two becomes the conversation in the forecast call.
Changing a win rate or a deal amount shows the bear case, the most likely case and the bull case in one view. Finance can answer the board's "what if" in the meeting, instead of promising a revised spreadsheet next week.
For example, a team with $40 million in weighted pipeline and a 25 percent win rate projects $10 million in bookings. Drop the win rate five points and the projection falls to $8 million, and the platform shows which segments and deals account for the difference, so the conversation moves straight to what to do about it.
When every revenue stream sits on the same data, the projection shows how much of the year depends on new business versus the existing base. That view supports retention and expansion planning as much as new-logo targets.
Moving a sales projection off a spreadsheet usually takes one or two quarters, because the old and new versions need to run side by side until finance trusts the new number.
The steps below cover that overlap, from agreeing on definitions before the first comparison to retiring the spreadsheet once the two numbers line up.
Finance will still build budgets, headcount plans and cash models in spreadsheets after the move. What changes is the revenue line feeding those models: it comes from the platform's projection, so it reflects the latest deal data instead of whatever export was pasted in last month.
Outreach, the agentic AI platform for revenue teams, builds projections on the same engagement, conversation and deal data reps work in every day, so finance and revenue leaders plan from one source.
AI Projection estimates where the period will finish based on business already won, the pipeline still open and the deals most likely to pull in from later quarters. That gives finance a number built from deal activity before anyone submits a call, and a check on how optimistic or cautious the team's own forecast is.
Forecast Rollup collects the calls reps, managers and leaders submit and rolls them up the hierarchy. With the AI projection and the rolled-up commit side by side, the gap between them sets the agenda for the forecast meeting: which deals explain the difference, and which assumptions need to change before the number goes to the board.
Scenario Planner models the bear case, the most likely case and the bull case by adjusting inputs like win rate and deal amount. When the board asks what happens if two large deals slip or win rates drop a few points, finance can show the answer in the same meeting, with the deals behind each case visible.
Parallel Forecasting and Multiple Forecasting Goals let teams project new logo, expansion and individual product lines as separate numbers, then see them together. That separation shows how much of the year depends on keeping and growing existing customers, which a single blended spreadsheet total tends to hide.
Line Item Forecasting projects revenue by product, so a quarter that looks healthy overall can still show one product line falling behind plan. Multi-Currency handles deals in different currencies for global teams, and Opportunity Splits credit shared deals correctly across owners.
As the business adds products, regions and team structures, those details keep the projection accurate without new tabs or manual reconciliation.
Spreadsheets will stay useful for modeling; the inputs are what need to move. Start with the number most likely to be challenged at the next board meeting, often the renewal base or next quarter's expansion target, and rebuild it on live deal and engagement data.
Pick that number because it is where the spreadsheet struggles most. A renewal base built from a customer success list cannot show which accounts have gone quiet, and an expansion target built from last year's rates cannot show which customers are already in active buying conversations.
Rebuilt on live data, the same number arrives with the accounts and deals behind it, along with the engagement signals that put it at risk.
Once finance can trace that one number back to the deals behind it, the case for moving the rest of the projection is easy to make. Add the next line the board questions, run each one alongside the spreadsheet until the variance is explained, and within a few quarters the projection that goes to the board is built on the same data the whole revenue team works from.
Start from current recurring revenue or the bookings run rate, add open pipeline by stage weighted by historical conversion rates, then layer in renewals and expansion. Keep assumptions on their own tab with an owner for each, and build base, upside and downside scenarios from the same inputs.
A sales forecast predicts how the current period will land from the deals in play. A sales projection models revenue further out under stated assumptions and scenarios, and it is used to plan hiring, spend and targets. Both should start from the same pipeline data.
Track the variance between projection and actuals every quarter and trace each gap to a deal, an input or an assumption. Accuracy improves fastest when inputs refresh from live data, assumptions are documented, and the team picks forecasting methods that fit its sales cycle and deal volume.
Start with renewals coming due, then apply historical gross retention and expansion rates by segment. Adjust for account signals such as product usage, support activity and stakeholder engagement, since they show renewal risk earlier than the contract date does.
Consider it when several people update the model every week, when the projection covers more than one revenue stream, when it goes into board reporting, or when running a new scenario takes longer than the meeting where someone asks for it.