The Back-Office Budget: Pricing Next Year Before It Prices You

Somewhere in the fourth quarter, most founders open a spreadsheet, paste in last year's card statement, add a vague cushion, and call the result next year's operations budget. It feels responsible. It isn't a budget — it's a forecast that last year will repeat, written by someone who knows it won't. The renewals that went up, the tool nobody cancelled, the new hire whose accounts you forgot to price, the hours you personally spent on payroll and ticket triage — none of that is in the paste. And so the year arrives and starts pricing the back office for you, one surprise charge at a time.

The fix is not a finance department. It's one deliberate sitting, sometime before the year turns, with four lists you mostly already have. The goal isn't precision to the dollar. It's that every line in the budget exists because somebody decided it should, rather than because it was there last year.

Four buckets, not one blob

A back-office budget that lives as a single number can't be managed — you can't tell a lean year from a leaky one. Split it into four buckets and each becomes something you can actually steer:

• Tools. Every recurring software charge, with its owner, seat count, and renewal date. If you ran the subscription sprawl audit, this list already exists; if you didn't, this is the week to run it, because you cannot budget the charges you haven't found.
• Services. The outside help: bookkeeper, payroll provider, benefits broker, the fractional anybody. These tend to be the stickiest lines, because nobody reprices a relationship that's working.
• Obligations. The costs you don't get to skip — filings, insurance renewals, required training, the audit you know is coming. These anchor the budget the way compliance dates anchor a training plan.
• Hours. The line nobody writes down: the time you and your team spend running all of the above. It never appears on a statement, which is exactly why it's usually the largest cost in the file.

The renewal calendar is a budget input

The single most useful thing you can do in the Tools bucket is put a date next to every line. A tool line without a renewal date is a number you'll pay; a tool line with a date is a decision you'll get to make. Pull the dates into the same sixty-day renewal calendar you use to avoid auto-renewal ambushes, and the budget and the calendar become the same artifact viewed two ways: the budget tells you what each renewal is worth to you, and the calendar tells you when you have to say so.

While you're there, mark each tool line one of three ways: keep, renegotiate, or replace-or-cut. Don't do the renegotiating now — that happens at each renewal window. What you're doing now is deciding the posture in advance, while nobody is on a sales call trying to close you before quarter-end. Also price the seats you already know are coming. If you plan to hire, each new person arrives with a login to most of your stack; budget the seats at the same time you budget the salary, or the tools line will quietly grow every time headcount does.

Price the hours line honestly

The Hours bucket is where small-company budgets are most dishonest, mostly by omission. Take the admin-time audit — or, if you haven't run it, a rough weekly estimate by function: payroll and HR admin, support triage, onboarding and training, chasing documents and answers. Multiply by a loaded hourly cost for whoever is actually doing the work. For the founder, use what an hour of your time is worth to the business when it's spent on selling or building instead.

You're not going to pay this line to anyone. You're writing it down because it changes the other three. A tool that costs a little more but removes a real block of weekly admin is cheaper than it looks on the card statement. A “free” process that eats every Friday afternoon is the most expensive item in the file. Without the hours line, the budget will always reward the wrong tool.

Leave a decision reserve, and name it

Every year contains a problem you can't see from the fourth quarter: the vendor that gets acquired and sunsets your plan, the regulation that adds a filing, the hire who needs a tool nobody else uses. Rather than padding every line — which makes the whole budget unreadable — hold one explicit reserve, sized as a modest share of the total that your own history says is realistic, labelled as exactly what it is. When it gets spent, write down on what and why. A reserve with a ledger teaches you, by next year, what kind of surprises your business actually has.

The quarterly true-up

A budget built once and never reopened is just last year's paste with better formatting. Put a thirty-minute true-up on the calendar each quarter: actuals against plan by bucket, every renewal coming in the next quarter reviewed against its keep/renegotiate/cut posture, and the hours line re-estimated. The question each time is short: what did we pay for that we didn't decide to? Each answer is either a line to cut, a line to add honestly, or a process to fix. Four of these a year is the whole maintenance cost, and it is dramatically cheaper than the alternative — discovering in next year's fourth quarter that the budget stopped describing the business somewhere around March.

The bottom line

A back-office budget isn't a spreadsheet exercise; it's a list of decisions with prices attached. Split it into tools, services, obligations, and hours. Put a renewal date and a posture next to every tool. Price the hours you'd otherwise pretend are free. Hold one named reserve with a ledger. And true it up every quarter against what you actually paid. One sitting in the fourth quarter, four half-hours a year after that — and next year's back office costs what you decided it should, instead of whatever it turned out to be.

— Tom