Operating Expense Forecasting: Stop Treating Every Cost the Same

The expense forecast often looks wonderfully consistent right up until you ask how the lines were forecast.

Rent: prior month.

Software: prior month.

Travel: prior month.

Marketing: prior month plus a little.

Four completely different costs. One forecasting method.

It is tidy. It is also how a lot of expense forecasts become historical reports with future dates.

Operating expenses do not all behave the same way, so I do not think they should all be forecast the same way.

Start by asking what makes the cost move

Before choosing a formula, I want to know what creates the expense.

Payroll moves with people, compensation and timing. Rent moves with leases. Payment processing may move with transaction volume. Cloud infrastructure may move with usage. Travel moves with activity and policy. Marketing programs can move because someone deliberately decides to spend the money.

Those are different forecasting problems.

A driver-based forecast does not mean every GL account needs a sophisticated operational driver. It means the important lines should have logic that resembles the business.

Some costs deserve a schedule

Known contractual expenses are usually the easiest.

Rent, insurance, major software contracts, debt-related fees and other scheduled commitments often have dates and amounts attached to them.

I would rather forecast those from the agreement than apply a percentage growth rate because last year happened to increase 6%.

This is basic, but it matters because known costs create a useful base. Finance can spend its judgment on the lines that are actually uncertain.

Some costs deserve an operating driver

Payroll is the obvious example, which is why the headcount forecast matters so much.

But there are others.

Transaction fees may follow payment volume. Customer-support tools may follow seats. Freight may follow shipments. Hosting may follow usage. Commissions may follow bookings or revenue depending on the plan.

The driver does not need to explain every dollar. It needs to explain enough of the movement to make the forecast useful.

And some costs are decisions

This category gets mistreated most often.

Marketing campaigns, outside consultants, conferences, recruiting programs and discretionary projects do not necessarily happen because revenue went up 8%.

They happen because somebody chooses to do them.

Forecasting these lines as a percentage of revenue can create a very smooth model and a very strange management conversation.

I prefer to know what has actually been committed, what is planned, and what can still move.

That distinction becomes especially useful in a downside scenario. Management can see which costs naturally move with the business and which require an explicit decision.

Run rate is useful until it isn’t

I use run rate. I just do not worship it.

For stable, low-materiality expenses, recent actuals can be a perfectly reasonable forecasting method.

The problem is when run rate becomes the default because it is easy.

December includes an annual renewal. March includes a conference. June has a legal settlement. A vacant role lowers software seats for two months. Last month is full of things that may not belong next month.

Before annualizing an expense, I want to know whether the recent period represents normal activity.

Sometimes the most valuable forecast adjustment is simply refusing to repeat an anomaly twelve times.

Do not make every department forecast every account

This is where expense planning can become a small administrative state.

Finance sends managers a template with 80 accounts. Managers stare at it. Someone copies last year’s numbers. Finance consolidates the fiction.

Business leaders should own the assumptions they can actually influence.

They usually know hiring plans, major vendors, projects, campaigns and changes in operating activity. They may not have a useful opinion about every accounting classification.

Finance can translate business assumptions into the financial structure without asking managers to become part-time accountants.

Watch timing, not just the annual total

A department can be exactly on its annual expense plan and still create a meaningful cash or earnings surprise by moving spend between quarters.

Timing matters.

A $600,000 implementation that moves from Q2 to Q4 changes the near-term outlook even if the annual budget remains untouched.

This is one reason I prefer a rolling forecast that updates the timing of real activity instead of forcing the budget calendar to remain true forever.

The expense review should sound like the business

If an expense forecast review consists entirely of account numbers and percentages, I usually think we are one level too low.

The useful conversation sounds more like this:

The hiring class moved six weeks. The product team added a contractor. The trade show was canceled. Cloud usage is running above the customer forecast. The insurance renewal came in higher than expected.

Those sentences explain why the financial statement is changing.

Then the model can do its job.

It can turn the business into numbers instead of turning last month’s numbers into next month’s numbers.