Zero-Based Budgeting for a Ten-Person Team: A Practical Walkthrough

Zero-based budgeting has a reputation as a large-company exercise — something a finance department with its own headcount runs once a year with a consultant in the room. At ten people, that version is overkill. But the core idea underneath it, building next quarter's budget from a blank page instead of last quarter's number plus a percentage, is one of the more useful habits a small team can adopt, and it takes an afternoon, not a quarter.

Why last quarter's number is the wrong starting point

The default budgeting method almost everyone falls into without deciding to is incremental: take what was spent last period, add a bit for growth or inflation, and call it the new number. It feels efficient because it requires no new thinking. The cost is that every line item that was ever justified stays justified forever, simply by having existed before. A software subscription bought for a project that ended eight months ago survives three more budget cycles because nobody's job was to question it — it was already in the base.

Zero-based budgeting inverts the default. Instead of starting from last quarter's total and adjusting, every line starts at zero and has to be rebuilt with a reason attached. Nothing carries over just because it carried over last time. For a ten-person team this is not the multi-week corporate ritual the name suggests — it is a structured conversation that fits in a couple of hours if you walk into it prepared.

Step one: list every current expense with its owner

Pull the full list of recurring costs — software, contractors, subscriptions, recurring services — and next to each one write down who on the team actually uses it or is responsible for the relationship. This step alone is usually where the first real savings surface, because a nontrivial fraction of any small team's recurring spend has no clear owner at all. Nobody can justify a line item they didn't know existed, and a tool with no owner is a tool nobody will miss.

Step two: separate cost from justification

For each line, write one sentence answering a single question: what does this actually produce for the team right now, not what it was bought to do originally. "We use this for design handoff on every release" is a justification. "We started this trial last spring and never canceled it" is not — it is a history, and history is not the same thing as a reason. This step is uncomfortable in a useful way; it is common for a ten-person team to find two or three tools that everyone assumed someone else was using.

Step three: build the budget back up from zero

Now rebuild the spending plan starting from nothing, adding back only the items that survived step two, at the amount actually needed rather than the amount historically spent. This is where zero-based budgeting differs most sharply from a simple cost-cutting pass — the goal is not just to remove waste, it is to size every remaining line correctly. A tool that is genuinely essential might need a higher tier than the team is currently paying for; a contractor relationship that is working well might deserve more hours, not fewer. Zero-based budgeting is neutral on direction. It just refuses to let anything through without a current reason and a current number.

Step four: rank what's left by what it would cost to lose

Once the rebuilt list is in front of you, order it by a different question than cost: if this went away tomorrow, how much would it actually hurt, and how fast. This reordering usually surprises people, because the most expensive line item on a ten-person team's budget is rarely the one that would hurt most to lose — a modestly priced tool wired into daily workflow often ranks above a pricier one used occasionally. That ranking is what actually informs decisions later, when a leaner quarter forces a real cut; you already know which lines to protect and which to touch first.

Making it a quarterly habit, not an annual event

The reason zero-based budgeting has a heavy reputation is that most organizations only attempt it once a year, at a scale where reconstructing everything from scratch really is a slog. At ten people, running the same lightweight version every quarter is both faster and more useful, because the list of expenses has not had time to grow unrecognizable between checks. The second and third time through, step one takes ten minutes instead of an hour, because the owners are already documented and the habit of questioning the base has already displaced the habit of just carrying it forward.

The payoff is not primarily the money recovered from canceled subscriptions, though there is usually some. It is that the team stops accumulating financial sediment — commitments that outlive their reason and just sit there because reviewing them takes more energy than ignoring them. A ten-person team that rebuilds its budget from zero every quarter never has to run the painful, months-long audit that larger companies eventually need, because it never let the pile get large enough to require one.

The most common mistake on a first pass is treating the exercise as a cost-cutting mandate and approaching every line looking for a reason to kill it. That framing produces short-term savings and long-term resentment, because a tool someone genuinely relies on gets threatened every quarter for no reason other than habit. The healthier framing is neutral curiosity: the question is whether the number and the reason still match reality, not whether the number can be made smaller. Some quarters the honest answer is that spending should go up on a line that's clearly earning its keep, and a zero-based process that only ever produces cuts has stopped being honest and started being theater aimed at looking disciplined.

The second common mistake is skipping step one — the ownership mapping — because it feels like the least analytical part of the exercise. It is actually the part that saves the most time on repeat cycles, because once ownership is documented, each subsequent quarter only requires checking in with the same handful of people rather than re-deriving who uses what from scratch. Teams that skip it end up redoing the hardest part of the process every single quarter instead of building on the previous cycle's work.