Most founders use the words forecast and projection interchangeably. Their lenders, auditors, and investors do not. The two documents look almost identical — same line items, same time horizon, same dollars at the bottom of each column — but they are governed by different accounting standards, written for different decisions, and read by different audiences with different tolerances for error.
Picking the wrong label can cost you. Submit a projection where a lender expected a forecast and your loan covenant gets renegotiated on bad terms. Submit a forecast where an investor expected a projection and the room concludes you have not stress-tested your model. The numbers might be exactly right; the label decides whether the room trusts them.
This guide explains the technical difference, the situations where each document is the right tool, and how to build both efficiently so you are never caught labeling one as the other.
The accounting definition (and why it matters)
The American Institute of CPAs draws a hard line between the two terms. A financial forecast presents what the company expects to happen given the conditions it expects to exist. A financial projection presents what would happen if a hypothetical set of conditions were true — a "what if" scenario that may or may not be likely.
The difference comes down to one word: expected.
A forecast is your best estimate of the future given current trajectory. If your company is growing 12% month over month and you have no reason to believe that rate will change, a forecast extends 12% growth out twelve months. If you are about to close a known enterprise deal, the forecast bakes in that deal at its expected close date. The forecast is the document where you commit to your most realistic view of what is going to happen.
A projection is a conditional model. "If we close the Series A at $8M and hire fifteen engineers in Q3, this is what our P&L looks like by Q4 next year." The Series A may not close. The hires may not happen. The projection is honest about that — it tells the reader the conditions and then shows the financials those conditions would produce. Projections are tools for evaluating decisions, not for predicting outcomes.
Both documents follow the same formatting standards under AICPA AT-C section 305 when they are formally attested to by a CPA. Both must include the assumptions used, a summary of significant accounting policies, and a clear statement that the future cannot be guaranteed. The difference is the kind of future being described.
The practical difference (and why founders trip over it)
In ordinary conversation, the two words feel like synonyms. Your finance team says "let me run a quick projection on this scenario" when they really mean a forecast adjustment. Your investor asks for "a five-year projection" when what they want is a five-year forecast that incorporates a few key assumptions. The vocabulary drift is harmless inside a team that knows what it actually means.
The drift becomes expensive when the document leaves the room. The minute a number gets attached to a covenant, an investor presentation, an audit, or a tax filing, the label is no longer casual. It signals what the audience can hold you to.
Consider the same set of numbers being shipped two ways. A SaaS company with $2M in current ARR builds a model showing $5M ARR in twelve months. As a forecast, that document says: this is what we believe will happen based on our current pipeline, conversion rates, and hiring plan. The board can hold leadership accountable to that number. Missing it by 30% is a meaningful underperformance.
The same model labeled as a projection says: if we close the deals currently in stage 3+ at our historical close rate, hire on schedule, and maintain net revenue retention at 112%, this is the outcome. The board cannot hold leadership to the $5M number; they can only hold leadership to the assumptions. Missing the assumptions is the failure, not missing the dollar amount.
Same spreadsheet. Same numbers. Two completely different conversations with the board.
When to use a forecast
Use a forecast whenever the audience needs to know what you actually expect to happen. The label says "this is our committed view of the future, based on what we currently know."
Common situations where the right document is a forecast, not a projection:
Bank lending and credit facility renewals. Lenders want to see what you expect cash flow and revenue to look like over the term of the loan. They are pricing risk against your expected outcome, not your aspirational scenario. A 13-week cash flow forecast is the working document during a covenant breach review.
Quarterly board updates. When you put a number in front of the board for next quarter's revenue, that is a forecast. The board uses it to plan capital decisions and assess whether the team is on plan. Calling it a projection invites the question "okay, but what do you actually think will happen?"
Operating budgets. The annual budget that drives departmental spending plans is a forecast. It is the company's expected view of revenue and cost for the year. Variances against budget are reviewed monthly. You cannot build a culture of accountability against a projection, only against a forecast.
Audit-related disclosures. When a public company or a private company preparing for IPO discusses forward-looking financial information in audited materials, those statements are governed by forecast standards. Auditors hold forecasts to a higher standard of supportability than projections.
Executive compensation models. Bonuses tied to revenue or EBITDA are tied to forecast achievement, not projection achievement. Comp committees expect the underlying numbers to reflect what leadership expects, with stretch and threshold bands defined off that expectation.
For our 13-week cash flow forecasting workflow, the forecast is the foundational document — every Friday update, the team revises the forecast based on the prior week's actuals, not on hypothetical scenarios.
When to use a projection
Use a projection whenever the audience needs to evaluate a hypothetical scenario. The label says "if these conditions hold, this is what the financials would look like."
Fundraising decks. A Series A pitch projects what the company can do with the capital it is raising. The capital has not been committed yet. The hires have not happened. The projection lets the investor evaluate the strength of the plan without holding the founder to a forecast they cannot yet make. Most term sheets explicitly cite projections, not forecasts, in their forward-looking sections.
Strategic alternatives analysis. When the board is deciding between launching a new product line, acquiring a competitor, or doubling down on the existing business, each option needs a projection. Each model assumes a different set of conditions, and the comparison is between conditional outcomes. None of them are forecasts because the company has not yet decided which path to take.
Sensitivity analysis and scenario planning. Best-case, base-case, and worst-case modeling is projection work by definition. The base case might match the forecast if conditions hold steady, but the surrounding scenarios are explicitly conditional.
Pre-acquisition due diligence. When a buyer evaluates a target company, the buyer often asks for both — the seller's existing forecast (what the business expects to do under current ownership) and a set of projections (what the business would do under buyer-controlled conditions, with new pricing, new go-to-market motions, or cost synergies). Conflating these in due diligence is a leading cause of failed deals.
New product launches. Before the product ships, you cannot forecast its revenue. You can only project what revenue would look like under various adoption scenarios. After the product ships and you have six months of run rate, the projection becomes a forecast.
A worked example: same numbers, two stories
A 30-person SaaS company with $4.2M in ARR is preparing two documents for the same week.
The first goes to their bank, where they are renewing a $2M revolving credit facility. The bank asks for a 12-month outlook showing how the company will maintain its cash covenant. The team builds a forecast: based on the current pipeline of $1.8M in stage 3+ opportunities, a 38% historical close rate, and the existing hiring plan, ARR reaches $5.6M by month 12, with average cash balance of $1.4M. The bank renews the facility on existing terms because the forecast clearly maintains the covenant.
The second goes to a Series B lead investor that same Friday. The investor asks for a five-year outlook. The team builds a projection using the same starting point but with three explicit assumptions: closing $20M of new capital in Q3, expanding the sales team from 6 to 22 reps over 18 months, and entering one new vertical (financial services) in year 2. Under those conditions, ARR reaches $48M by year 5. The investor evaluates the projection by stress-testing each assumption — close rate, ramp time, vertical-specific conversion — and decides whether to lead the round.
Both documents are correct. They are different documents because they describe different futures. The forecast is what happens with the cards currently on the table. The projection is what happens if we draw three more cards.
If the team had labeled the bank document a "projection," the bank would have asked for a forecast underneath it, slowing the renewal by two weeks. If the team had labeled the investor document a "forecast," the investor would have held the team accountable to $48M of ARR even if the round did not close, which is unfair to leadership and unrealistic to the business.
A decision matrix you can use today
When you are about to send a forward-looking financial document, ask yourself which question the audience is trying to answer:
| Audience question | Right document | |---|---| | What do you expect to happen this year? | Forecast | | What would happen if we did X? | Projection | | Are you on plan to hit your covenant? | Forecast | | Should we approve this strategic option? | Projection | | What is the budget for next quarter? | Forecast | | Walk me through your three scenarios. | Projection (× 3) |
When in doubt, the test is whether the future being described depends on a decision that has not yet been made. If yes, projection. If no, forecast.
How CentSight separates the two
The early users we work with are mostly $1M–$50M SaaS and tech businesses where the founder or operator is also the de facto CFO. They do not have time to maintain two parallel financial models. They need one model that can output both views without re-keying numbers.
The CentSight model is built on the forecast as the source of truth. The forecast pulls live from QuickBooks Online and Plaid, recalculates weekly, and reflects the company's current expected trajectory. From that base, projections layer in scenario assumptions — capital raises, hiring plans, pricing changes, new product launches — without overwriting the forecast. The forecast stays clean. The projections sit alongside it, each one labeled with its assumptions and expected close date for the conditions.
That separation is the discipline. One document represents what the team commits to. The others represent what the team is evaluating. The labels matter, and the model preserves the distinction so the founder does not accidentally send a projection to the bank or a forecast to a board that wanted to debate strategic alternatives.
FAQ
Is a budget the same thing as a forecast? A budget is a forecast that has been formally adopted by the company as its operating plan for a defined period, usually a fiscal year. The budget locks in the expected revenue and cost numbers and becomes the benchmark against which actual performance is measured monthly. A forecast can be revised more freely; a budget typically requires board approval to change mid-year.
Are pro forma financials forecasts or projections? It depends on what they describe. Pro forma financial statements adjusted to show the historical effect of an event (such as an acquisition) are neither — they are restated historicals. Pro forma statements that show the future effect of a planned event are projections, because they describe a conditional future that depends on the event closing.
What is a rolling forecast? A rolling forecast is a forecast that is continuously updated rather than locked at the start of a year. Most modern finance teams run a 13-week or 18-month rolling forecast, refreshed every two to four weeks based on the latest actuals and pipeline. The label is still "forecast" — what changes is the cadence of revision, not the underlying definition.
Do investors prefer forecasts or projections? Investors typically expect projections during fundraising because the capital being raised is itself one of the assumptions. Once the round closes and the company is operating, investors expect forecasts in their board updates, since the company should now have a defensible view of expected outcomes given the capital it has just received.
Can a single document be both a forecast and a projection? No, but a single financial model can produce both as separate output views. The forecast view shows expected outcomes. The projection view layers scenario assumptions on top. Most modern FP&A tools allow you to toggle between views without maintaining two spreadsheets, which is how you avoid the trap of letting your forecast drift into projection territory through unnoticed assumption creep.
What standard governs forecasts and projections in the U.S.? The American Institute of CPAs publishes attestation standards under AT-C section 305 covering the examination, compilation, and agreed-upon procedures for forecasts and projections. If a CPA firm is going to attest to either type of document, those standards govern the format, the disclosure of assumptions, and the qualifying language that has to appear on the document.
How often should we update our forecast? For private companies under $50M in revenue, a monthly forecast refresh is the minimum cadence; weekly cash flow forecasts are increasingly standard. The faster the business moves and the tighter the cash position, the more often the forecast should be revised. Quarterly forecasting is too slow for any business making real-time hiring or pricing decisions.
Related resources
- Cash flow forecasting — the 13-week cash flow forecast is the most common forecast a venture-backed founder will run
- Management reporting — forecasts and projections are inputs to the monthly management reporting package
- Total revenue formula — the top-line number that gets forecasted (or projected) under different scenarios
- SaaS finance — pillar resource on SaaS-specific forecasting drivers
- AI CFO — how an AI CFO automates the boundary between forecast and projection so the founder does not have to maintain two spreadsheets
Stop maintaining two spreadsheets
If you are still maintaining your forecast and your scenario projections in two parallel spreadsheets — one updated weekly, one rebuilt every time an investor asks for a what-if — that is the highest-leverage workflow to fix in your finance stack. The discipline of separating expected outcomes from conditional outcomes is what makes a finance function trustworthy to a board, a lender, or a buyer.
CentSight pulls your live data from QuickBooks and Plaid, maintains a rolling forecast as the source of truth, and lets you spin up labeled projections without breaking the underlying model. Founding members are using it to send the right document to the right audience without re-keying a single number.
Join the waitlist and we will reach out within 48 hours to walk through the model with your specific data.
About the author: Gerald Hetrick is the founder and owner of CentSight, the AI CFO platform for $1M–$50M SaaS and tech businesses.
