Bottom up budget: how to build one from scratch in 2026

A bottom-up budget is built by collecting granular cost and revenue estimates from individual departments or cost centres, then consolidating them into a company-wide plan. It delivers higher accuracy and stronger team buy-in than top-down approaches, but requires careful reconciliation against leadership targets to prevent overspending. The seven steps below show exactly how to do it, and the process works the same way regardless of the year you are planning for.

A structured bottom-up process puts the people closest to the numbers in charge of building them, which reduces the manual reconciliation work that plagues disconnected spreadsheet-based approaches.

What is a bottom-up budget?#

A bottom-up budget starts at the lowest level of the organisation and works upward. Each team or department produces its own detailed cost and revenue estimates, which are then consolidated into a single company-wide plan.

This is the opposite of top-down budgeting, where senior leadership sets an overall spending target and pushes it down to departments to divide among themselves. A top-down example might look like this: the board decides the business will spend a fixed total next year, then splits that figure across sales, product, and other teams. It is fast and keeps spending within a firm ceiling, but the numbers are often disconnected from operational reality. Teams who had no input tend to treat the targets as someone else's problem.

Zero-based budgeting is related but distinct. It requires every department to justify each line of spending from zero rather than adjusting last year's figures. You can apply zero-based thinking inside a bottom-up process, but the two are not the same thing. Bottom-up budgeting describes how numbers are built. Zero-based budgeting describes the standard of justification each line must meet.

Bottom-up budgeting advantages and disadvantages#

Bottom-up budgeting is more accurate than top-down, but it costs more time to produce. Neither fact cancels the other out. The right question is whether the accuracy gain is worth the effort for your organisation at its current stage.

The advantages are real. Estimates come from the people who actually run the costs, which means fewer surprises mid-year. Teams who build their own budgets are more likely to manage against them. The detail also makes variance analysis straightforward: when actuals diverge from plan, you can see exactly which line moved and why.

The disadvantages are equally real. The process is slow. Collecting, reviewing, and reconciling submissions from every department takes weeks in spreadsheets. Departments also have an incentive to pad their requests, building in slack in case leadership cuts the numbers. Left unchecked, that padding compounds across every team and produces a budget the business cannot actually afford.

Top-down is faster and keeps total spend within a hard boundary. Bottom-up produces more reliable figures and stronger ownership. Many businesses use a hybrid: leadership sets a revenue and margin target, then departments build upward within that constraint. That combination captures the main advantages of bottom-up budgeting while limiting the risk of unchecked padding.

How to build a bottom-up budget in 7 steps#

Work through these steps in order. Skipping the early ones, particularly the standards-setting and driver-identification stages, creates reconciliation problems later that are slow to unpick.

1. Learn the organisation's existing budgeting standards and required formats. Before any department starts building numbers, everyone needs to know the rules. What cost categories does the business use? What level of detail is required? What period does the budget cover, and in what currency? Agreeing this upfront prevents you from receiving 12 submissions in 12 different formats that cannot be compared or consolidated without manual rework.
2. Identify the key business drivers that link operational activities to financial outcomes. A business driver is any metric that causes costs or revenues to move. Headcount drives payroll. Units sold drive direct material costs. Square footage drives rent and utilities. Mapping these relationships before you ask departments to submit numbers means their estimates will be grounded in something real rather than last year's figures plus a percentage.
3. Have individual departments perform a granular cost analysis of projected expenses. Each team lists every cost it expects to incur: salaries, contractor fees, software subscriptions, travel, equipment, training. The instruction to be granular matters. A single line labelled "marketing spend" is not a budget; it is a guess. The line should break out each item separately, for example paid search, agency retainer, and events as distinct figures. That level of detail is what makes the bottom-up method worth the effort.
4. Calculate department budgets by multiplying activity quantities by their corresponding unit rates. This is where the business drivers from step 2 become numbers. If you plan to hire three engineers at a given salary, multiply the headcount by the rate to get the payroll line. If your sales team makes 400 outbound calls per month and each call requires 30 minutes of a rep's time, you can cost that activity directly. Spell out the arithmetic. A number with no workings behind it cannot be challenged or defended.A note on industry-specific multipliers: in architecture and engineering, Monograph's 2026 research reports a standard billing multiple of 3.20 and a breakeven multiple of 2.73. These figures are specific to that sector. If you work in a different industry, derive your billing and breakeven multiples from your own historical data rather than applying these benchmarks directly.
5. Consolidate the individual submissions into a comprehensive company-wide total. Once every department has submitted, you add the lines together by category. Payroll across all teams. Software costs across all teams. Travel across all teams. The result is a draft company budget. At this stage it is almost certainly too high. That is expected and is not a failure of the process.
6. Reconcile the consolidated plan against leadership targets and revenue capacity. This is the step most guides skip, and it is the one that determines whether the budget is actually usable. Take the consolidated total and compare it against the revenue the business can realistically generate. If costs exceed revenue capacity at the target margin, something has to give. Work back through the submissions with department heads, identifying where padding exists and where genuine cuts are needed. The goal is a plan where costs are justified line by line and the business can still hit its margin target.
7. Publish the final approved budget to the relevant stakeholders. Once leadership has signed off, distribute the approved budget to every team that contributed. Include the figures they submitted, the figures that were approved, and a brief explanation of any material changes. Teams that understand why a line was cut are more likely to manage within it than teams who simply receive a revised number with no context.

Bottom-up budget example: a worked illustration#

Take a three-person marketing team at a software business planning for the next financial year.

The team lead starts with headcount. Two full-time employees at a set annual salary, plus one contractor working two days per week at a day rate across 46 working weeks. The salaries and contractor fees are costed separately. Employer's National Insurance and pension contributions add a further percentage to the permanent headcount cost, bringing the total employment cost to a single figure.

Next, the team lists every non-payroll cost line by line: paid search, content agency retainer, marketing automation software, events and sponsorship, travel, and miscellaneous tools and subscriptions. Each line carries its own figure, and the lines are summed to a non-payroll total.

The department budget is the employment cost total plus the non-payroll total, giving a single annual figure for the team.

The same exercise runs across every other department. Each team produces its own total, and those figures are added together into a company-wide draft total.

Leadership's revenue target for the year sets a margin requirement, which means total costs must stay within a defined ceiling. The consolidated draft comes in above that ceiling.

Step 6 begins. The finance lead reviews each submission and identifies where the gap can close. The marketing events line is trimmed to a figure the team agrees is defensible. Sales defers two of four planned international trips. Product moves one contractor start date from January to April, saving a material sum in the first half. Those three changes recover a significant portion of the gap. The remaining difference is worked through line by line until the plan fits within capacity.

Note on industry multipliers: Monograph's 2026 research reports that in architecture and engineering, 23% of total project fees are now allocated to the schematic design phase alone. That kind of phase-level allocation logic is useful if you work in project-based professional services, but the specific percentages apply to that sector only. Use your own historical phase data if your business model differs.

How do you handle the AI subscription tail in your budget?#

The fastest-growing budget leak in 2026 is not a single large cost. It is dozens of small ones. AI writing tools, image generators, coding assistants, research platforms, and meeting summarisers are each cheap enough that individual employees buy them on a card without raising a purchase order. Collectively, they add up to a material and largely invisible cost.

The AI subscription tail makes manual tracking harder, because these costs do not appear in any system until the credit card statement arrives.

Before you consolidate department submissions, run this checklist:

1. Ask every team lead to pull their last three months of card and expense transactions and flag any recurring software charge, however small.
2. Check your company card statements for subscriptions billed monthly rather than annually. These are the ones most likely to have been added without a budget line.
3. List every AI or SaaS tool found, its monthly cost, and whether it duplicates a tool already in the approved stack.
4. Decide which tools survive into the budget year. Cancel the rest before consolidation, so the savings are real rather than aspirational.
5. Add a single "approved SaaS and AI tools" line to each department's submission template, with a requirement to list every tool and its annual cost. Make this a standard part of step 1 for every future budget cycle.

The goal is not to ban small tools. It is to make them visible before the budget is set, not after it has been blown.

Connecting your bottom-up budget to a rolling cash flow forecast#

A bottom-up budget tells you what you plan to spend and earn over a period. A cash flow forecast tells you whether the money will actually be in the account when the payments fall due. The two documents answer different questions, and you need both.

The budget is accruals-based: it records costs when they are incurred. The cash flow forecast is timing-based: it records money when it moves. A large annual software contract signed in January hits the budget spread evenly across months, but it hits the bank account as a single payment on day one. That gap is where businesses run into trouble.

Once your bottom-up budget is approved, feed the monthly cost and revenue lines directly into your cash flow forecast, adjusting for payment terms, VAT timing, and any large upfront commitments. Review both documents together at least monthly. When actuals diverge from plan, update both, not just the one that looks wrong.

When bluprnts makes the process faster#

Manual consolidation is where bottom-up budgeting breaks down. Spreadsheets multiply, versions conflict, and the finance lead spends days reconciling rather than analysing.

bluprnts is a financial modelling tool that lets founders and finance leads enter headcount, pricing, sales, costs, and financing lines directly. It then derives the P&L, balance sheet, cashflow, and runway automatically, with no accounting software required. It's free to start, and subscriptions are priced by last year's revenue, from £49 a month. The live financial picture updates as inputs change, which means reconciliation happens in the model rather than across a chain of spreadsheets.

Prices and plan limits verified as of October 2026.

FAQs#

What is another name for bottom-up budgeting?#

Bottom-up budgeting is also called participative budgeting or build-up budgeting. Both names describe the same process: individual departments or cost centres produce their own estimates, and those figures are consolidated upward into a company-wide plan. The term "participative" emphasises the involvement of department heads, rather than the direction in which numbers travel.

How often should a bottom-up budget be reviewed or updated?#

Review the budget monthly, comparing actuals against the approved plan line by line. A full rebuild from department submissions is typically done annually, but fast-growing businesses often run a mid-year reforecast, particularly if revenue or headcount has moved significantly from the original assumptions. Monthly reviews catch variance early; the annual rebuild resets the baseline.

Can a small business or startup use bottom-up budgeting?#

Yes, and the process is simpler when the team is small. A five-person business can run the full seven steps in a few hours rather than weeks, because there are fewer submissions to collect and consolidate. The method is especially useful for startups that need to show investors a budget built from real operational assumptions rather than a top-line figure divided arbitrarily across departments.

What is the difference between bottom-up budgeting and zero-based budgeting?#

Bottom-up budgeting describes how estimates are built: from the department level upward. Zero-based budgeting describes the standard of justification required: every line starts at zero and must be defended, rather than carried forward from last year. You can apply zero-based thinking inside a bottom-up process by requiring each team to justify every cost from scratch, but the two terms describe different aspects of the budgeting method.

How do you stop departments from padding their budget submissions?#

Ask departments to show the workings behind every line, not just the total. A number with no calculation behind it is easy to inflate; a number derived from headcount multiplied by a unit rate is harder to pad without it being obvious. Comparing submissions against historical actuals and against similar teams surfaces outliers quickly. Telling teams upfront that submissions will be reviewed line by line reduces padding before it starts.

Conclusion#

Start by agreeing your formats and business drivers before a single department opens a spreadsheet. Run the seven steps in order, audit your AI and SaaS subscriptions before consolidation, and feed the approved figures into a rolling cash flow forecast so you can see timing as well as totals. The budget tells you the plan; the forecast tells you whether the cash holds.