How Founders Should Compare This Month’s Forecast With Last Month’s

May 21, 2026 · 10 min read

Comparing this month’s forecast with last month’s is not a forecasting accuracy exercise.

It is a cash decision exercise.

That distinction matters.

Founders can waste a lot of time asking whether last month’s forecast was right. But a better question is:

What changed, why did it change, and what should we do differently now?

Revenue may have moved later.

Collections may have slipped.

A large receipt may have arrived early.

Hiring may have become committed.

A vendor payment may have moved forward.

A tax payment may now be closer.

A one-time cash item may have made ending cash look better.

A large customer may have become less certain.

Those changes matter only if the company reads them and acts on them.

A forecast comparison should not end with, “cash is higher” or “cash is lower.”

It should help the founder understand whether cash safety improved, whether cost rigidity increased, whether spending direction still makes sense, and whether downside control is stronger or weaker than it looked last month.

Do not overwrite last month’s forecast

The first practical rule is simple:

Do not overwrite last month’s forecast.

This sounds basic. It is still one of the most common mistakes.

A team opens last month’s file, updates actuals, changes revenue, adjusts expenses, refreshes ending cash, and saves the new version.

Now the forecast looks current.

But the comparison is gone.

The founder can no longer see what last month’s team believed would happen. That means it becomes harder to answer important questions:

• Which receipts were expected last month?
• Which receipts actually arrived?
• Which receipts moved later?
• Which costs became fixed?
• Which hiring decisions moved from planned to committed?
• Which assumptions quietly changed?
• Which ending cash movement came from timing rather than real improvement?

If the old forecast disappears, the learning disappears with it.

The first step is to freeze the prior forecast.

Keep last month’s forecast as it was. Then build this month’s actuals and updated forecast next to it.

At minimum, the comparison should show:

• last month’s forecast
• this month’s actual cash movement
• this month’s updated forecast
• variance
• reason for variance
• decision impact

That final column matters.

Without decision impact, the comparison can become a finance explanation instead of a founder tool.

The point is not only to know that cash moved.

The point is to know what the movement means.

Start with the cash path, not the full model

A monthly forecast comparison should not begin by reviewing every line in the file.

Start with the cash path.

The founder should first ask:

Is cash safety stronger or weaker than we thought last month?

That means comparing:

• expected ending cash from last month’s forecast
• actual ending cash for the month
• updated ending cash for future months
• usable cash after committed payments
• months where cash becomes tight
• the assumptions keeping the forecast comfortable

This first read gives the founder the direction of travel.

Cash may be higher than expected, but not necessarily safer.

Maybe a large customer paid early.

Maybe a vendor payment moved to next month.

Maybe hiring was delayed.

Maybe a one-time receipt arrived.

Maybe a planned payment was not made yet.

Cash may also be lower than expected, but not necessarily structurally worse.

Maybe a payment crossed month-end.

Maybe a one-time payment happened earlier.

Maybe inventory was purchased earlier than planned.

Maybe a temporary timing issue reduced cash in one month but not the full cash path.

The point is not to react to the headline number too quickly.

The first job is to understand whether the cash path changed in a way that affects the next decision.

Separate actual variance from future forecast variance

A useful comparison separates two different questions.

The first question is:

Why did actual cash differ from last month’s forecast?

The second question is:

How did the updated forecast for future months change?

These are related, but they are not the same.

For example, suppose a customer payment expected last month did not arrive. The actual variance explains why cash was lower this month.

But the future forecast variance asks a second question:

• Did that missed receipt simply move into next month?
• Did its confidence weaken?
• Did the customer delay approval?
• Did the company lose the opportunity?
• Did the delay create pressure before payroll, tax, or debt repayment?
• Did the company need to change spending because of it?

If the comparison only explains the past month, it misses the operating value.

The useful forecast comparison should show both:

• the difference between last month’s forecast and actual cash movement
• the difference between last month’s future forecast and this month’s updated future forecast

That second comparison is where many important insights appear.

It shows whether the company is only explaining the past, or actually updating its view of the future.

Break the variance into cash in, cash out, and timing

Ending cash is the result.

It is not the explanation.

If ending cash changed, the founder needs to know what caused the change.

A simple structure is to separate variance into three broad areas:

• cash in
• cash out
• timing

Cash in includes customer receipts, financing inflows, refunds, asset sales, owner contributions, or any other money coming into the business.

Cash out includes payroll, contractors, vendors, rent, taxes, debt repayment, inventory, equipment, software, capex, and one-time payments.

Timing explains whether the cash movement happened earlier or later than expected.

This separation matters because different variances require different responses.

If cash is lower because a customer paid late, the next action may be collections follow-up or a change in receipt confidence.

If cash is lower because payroll increased, the issue may be fixed burn.

If cash is lower because inventory was purchased earlier, the question may be whether that purchase was planned, avoidable, or now locked in.

If cash is higher because a vendor payment moved later, the company may not be safer. The payment may still be coming.

A useful comparison should prevent the founder from reading all cash improvements and all cash declines the same way.

Go deeper when the numbers are large or close to cash pressure

Not every variance deserves the same attention.

Some differences are small. Some are timing noise. Some do not affect a decision.

The founder should spend more time on variances that are:

• large
• near-term
• recurring
• tied to fixed spend
• connected to uncertain revenue
• close to a cash pressure month
• caused by an assumption change
• related to debt, tax, payroll, capex, or inventory
• likely to repeat

This helps keep the review practical.

A company does not need a long discussion for every small line item. It needs attention on the differences that change cash safety or the next decision.

A $2,000 timing difference may not matter.

A $200,000 customer payment moving by 45 days might matter a lot.

A small one-time expense may not change the forecast.

A smaller recurring cost that becomes fixed may matter more than its first-month amount suggests.

A forecast comparison should help the founder decide where to look closely and where not to spend time.

Compare by cash category, not only by account line

In practice, a detailed comparison can be hard to read if every account line is treated equally.

A better approach is to group cash movements into practical categories.

One useful structure is:

• operating cash in
• operating cash out
• investing cash in
• investing cash out
• financing cash in
• financing cash out

This is not about making the process complex.

It helps the founder understand what kind of cash movement changed.

Operating cash in may show whether customer collections are weaker or stronger than expected.

Operating cash out may show whether normal burn is changing.

Investing cash out may show capex, equipment, or long-term asset purchases.

Financing cash in may show new borrowing or funding inflows.

Financing cash out may show debt repayment or related cash outflows.

This matters because the same ending cash movement can have very different meanings.

Cash may improve because customer collections improved.

Cash may improve because new borrowing came in.

Cash may improve because capex was delayed.

Cash may improve because a supplier payment was pushed out.

Those are not the same story.

Grouping variances by cash category makes the comparison easier to read and harder to misinterpret.

Use currency-level comparison when the business needs it

Some companies operate in more than one currency.

For them, comparing only the consolidated cash forecast may hide important information.

A practical approach is to compare the forecast by currency first, then consolidate.

For each relevant currency, keep:

• last month’s forecast
• actual cash movement
• this month’s updated forecast
• variance
• reason for variance
• future impact

This helps the team see whether a cash issue is local, timing-based, currency-specific, or consolidated.

A company may look fine in total cash, but one currency may be tight. A foreign currency receipt may be delayed. A local payroll or tax payment may need cash in that currency. A transfer may take time. Exchange movement may also make the consolidated view look different from the operating reality.

The point is not that every small company needs a multi-currency process.

Many do not.

But if the company operates across currencies, currency-level comparison can reveal cash pressure that a single consolidated number hides.

The founder should not only ask:

How much cash do we have in total?

The better question is:

Is the right cash available in the right currency at the right time?

Write comments for the important differences

A variance table without explanations is only half useful.

The important differences need comments.

Not long essays.

Clear operating comments.

For example:

• Customer A payment expected in April moved to May because approval is still pending.
• Payroll was higher because two hires started earlier than expected.
• Capex moved forward because equipment purchase was approved this month.
• Cash improved because vendor payment moved to next month; this is timing, not savings.
• Loan repayment is still planned, but should wait until large receipt is confirmed.
• Future forecast improved because invoiced receipts are now closer to collection.
• Future forecast weakened because pipeline moved later and fixed spend increased.

These comments are where the forecast becomes useful.

Without comments, the founder sees numbers.

With comments, the founder sees assumptions.

The comment should explain three things:

• what changed
• why it changed
• what it means for future cash or decisions

This is especially useful when there are many numbers.

A founder or finance lead should not have to stare at a large table and guess what matters. The comparison should surface the important essence from the numbers.

Separate temporary differences from structural differences

A forecast comparison should always separate temporary and structural changes.

This is one of the most important parts of the review.

A temporary difference may include:

• a payment crossing month-end
• a one-time customer catch-up payment
• a delayed vendor payment
• a single unusual expense
• a timing difference in payroll or tax

A structural difference may include:

• customers consistently paying later
• sales cycles becoming longer
• recurring payroll increasing
• contractor spend becoming permanent
• gross margin weakening
• fixed vendor costs increasing
• inventory needs rising
• debt service becoming more burdensome

The same variance can look similar in one month but mean very different things.

If a large receipt moves by a few days, it may be a temporary timing issue.

If large receipts keep moving every month, the company may have a structural collections or sales-cycle issue.

If burn is lower because one hire was delayed, that may not mean the company became more efficient.

If burn is lower because a fixed cost was removed, that is different.

This distinction matters because it affects the future forecast.

Temporary differences may not require changing the long-term cash path. Structural differences should change the assumptions.

A monthly comparison becomes useful when it helps the team decide which type of change they are seeing.

Watch for missed revenue being pushed forward

One common pattern is missed revenue being pushed into future months.

This can make the updated forecast look better than the actual cash reality.

A customer payment expected this month does not arrive. It moves to next month.

A deal expected next month moves to the following month.

A delayed receipt remains in the forecast with the same confidence.

The future months become stronger because the missed cash has been pushed forward.

Sometimes this is reasonable.

Timing issues happen.

But if the same pattern repeats, the founder should pause.

The question is not only:

Did the revenue move?

The better question is:

Did the confidence change?

If a receipt moved because of a small administrative delay, it may still be reliable.

If it moved because the customer has not approved, the contract is not complete, delivery is delayed, or the customer has not confirmed payment timing, then the forecast should not treat it the same way.

A forecast comparison should not let missed revenue quietly hide in future months.

It should force a confidence update.

Look at whether spend became fixed

On the cash-out side, the key question is not only whether spending increased.

It is whether spending became harder to reverse.

A $20,000 one-time payment is different from a $20,000 monthly commitment.

A delayed hire is different from a signed employment offer.

A vendor quote is different from a signed contract.

A planned equipment purchase is different from equipment already ordered.

A discretionary project is different from required implementation spend.

This is cost rigidity.

When comparing this month’s forecast with last month’s, founders should ask:

• Which costs became committed?
• Which costs are still flexible?
• Which costs moved earlier?
• Which costs moved later?
• Which costs will repeat?
• Which costs depend on revenue that is still uncertain?
• Which costs reduce room to act if cash in slips?

This is where forecast comparison becomes practical.

It does not only show that cash out changed.

It shows whether the company has more or less flexibility than it had last month.

Turn the comparison into a decision agenda

Finance should not only prepare the comparison.

Finance should also prepare the decision agenda.

This is where the work becomes valuable.

A large table can be accurate and still be hard to use. If the founder spends the whole meeting trying to understand the numbers, there may be little time left to decide what to do.

A useful forecast comparison should surface the decisions clearly.

For example:

• Should we delay this hire until the large receipt is confirmed?
• Should we proceed with this vendor contract?
• Should we wait on equipment purchase?
• Should collections follow-up become the priority this week?
• Should we update the stakeholder message?
• Should we delay debt repayment until cash is received?
• Should we revise next month’s revenue confidence?
• Should we preserve extra cash instead of adding spend?

This is not about finance taking over the business decision.

The founder still owns the decision.

But finance should translate the numbers into the decisions that need attention.

That is often the highest-value part of the process.

Finance is not only summarizing the past. Finance is helping the company solve the next cash problem.

Keep the small-team version simple

A small team does not need a complex variance process.

It needs a comparison that is simple enough to repeat.

A practical lightweight version can use five lines:

• starting cash
• cash in
• cash out
• ending cash
• key assumptions

For each line, compare:

• last month’s forecast
• actual
• this month’s updated forecast
• variance
• reason
• decision impact

Then ask three questions:

Did cash safety get stronger or weaker?

Was the change caused by cash in, cash out, timing, one-time items, or fixed spend?

What decision should change now?

That is enough to create a useful monthly habit.

If the team has more capacity, add three deeper checks:

• large receipt changes
• fixed spend changes
• next update triggers

The goal is not to build the most detailed comparison.

The goal is to avoid losing the important change inside too many numbers.

A simple review that happens every month is better than a perfect review that no one maintains.

Review after actuals, before new commitments

The timing of the comparison matters.

The best basic rhythm is:

after monthly actuals are available, before the next spending decisions are made.

If the team compares forecasts after new commitments are already made, the comparison becomes a report.

It explains what happened, but it does not protect the next decision.

Reviewing before new commitments gives the founder a chance to adjust.

Maybe hiring should wait.

Maybe a vendor contract should stay flexible.

Maybe a debt repayment should wait until a receipt arrives.

Maybe collections need more attention.

Maybe an investor or lender update should change.

Maybe extra cash should be preserved instead of spent.

Monthly review is usually enough for the standard rhythm.

But the forecast should be compared sooner if a major assumption changes.

That includes:

• a large receipt arriving or slipping
• a major contract closing or moving later
• a hiring decision becoming committed
• fixed spend increasing
• tax, debt, capex, or inventory timing changing
• one-time cash appearing or disappearing
• cash buffer becoming thin
• a funding-related decision moving closer

A forecast comparison is not only a month-end finance exercise.

It is a way to keep the next cash decision close to reality.

A practical example: repayment after receipt

Consider a company that plans to repay part of a loan after a large customer payment arrives.

Last month’s forecast assumed the customer receipt would arrive before the repayment.

This month, the comparison shows that the receipt has not arrived yet. The repayment is still possible later, but if the company repays before the receipt comes in, cash may become tight quickly.

A weak comparison would say:

The receipt is delayed. The repayment is still planned.

A useful comparison says:

The repayment should wait until the receipt is confirmed. Once cash is received, the company can contact the bank and execute the repayment quickly.

That is the practical value of comparing forecasts.

It connects a cash action to a real trigger.

The company is not refusing to repay. It is not ignoring the plan. It is protecting cash safety by waiting for the condition that makes the action safe.

The same logic applies to hiring, capex, inventory, contractors, and other commitments.

The comparison should show when a decision becomes safe, not only whether it appears affordable in the expected forecast.

When forecast comparison goes wrong

Forecast comparison goes wrong when it becomes a backward-looking explanation.

The team says:

Revenue was late.

Collections slipped.

Spend was higher.

Ending cash changed.

But next month should recover.

Then nothing changes.

Hiring continues.

Fixed spend increases.

Uncertain receipts stay in the forecast.

Missed revenue moves forward.

The prior forecast is overwritten.

The same variance appears next month.

This is not a forecast comparison problem on the surface.

It is a decision problem.

The company is seeing the difference but not using it.

A useful comparison should make repeated misses harder to ignore.

If the same receipt keeps moving, confidence should change.

If the same spend keeps increasing, fixed burn should change.

If the same “timing issue” appears every month, the team should ask whether it is structural.

If ending cash depends on one large future receipt, the decision agenda should show that.

The purpose of comparison is not to explain why the past missed.

It is to stop the same assumption from quietly driving the next decision.

The real lesson

Founders should compare this month’s forecast with last month’s to keep cash decisions close to reality.

That is the real lesson.

Do not compare forecasts only to judge whether the prior forecast was right.

Compare them to see:

• what changed
• why it changed
• whether the change affects cash safety
• whether it is temporary or structural
• whether cash in moved
• whether cash out moved
• whether timing moved
• whether fixed spend increased
• whether one-time cash is hiding the real pattern
• whether the next decision should change

The most important output is not the variance table.

It is the decision that comes after the variance.

Should the company wait?

Proceed?

Collect faster?

Delay spend?

Preserve cash?

Update stakeholders?

Change revenue confidence?

Prepare a cash action earlier?

A good comparison makes those questions easier to answer.

Compare forecasts not to judge the past, but to keep the next cash decision close to reality.

← Back to Insights