Engineering Budget Fundamentals
An engineering budget is the financial translation of your strategy. If you can't map your roadmap to dollars, you're not managing -- you're hoping.
Key Dimensions
| Dimension | Description | Typical % of Eng Budget |
|---|---|---|
| People (Compensation) | Salaries, bonuses, benefits, social contributions | 65-80% |
| Cloud & Infrastructure | AWS/GCP/Azure, on-prem hosting, CDN, monitoring | 10-20% |
| Software Licenses | SaaS tools, IDE licenses, DevOps tooling | 3-8% |
| Contractors & Consulting | External staff augmentation, specialized consultants | 5-15% |
| Hardware & Equipment | Laptops, monitors, peripherals | 1-3% |
| Training & Events | Conferences, certifications, learning platforms | 1-2% |
| Travel | On-site meetings, offsites, team events | 1-3% |
CapEx vs OpEx – Why Engineering Leaders Must Care
Definitions
| CapEx (Capital Expenditure) | OpEx (Operating Expenditure) | |
|---|---|---|
| What | Spend that creates a long-lived asset (>1 year useful life) | Ongoing costs to run the business |
| Accounting | Capitalized on balance sheet, depreciated over 3-5 years | Expensed immediately on income statement |
| Cash flow | Large upfront outflow, smoothed P&L impact | Steady outflow, immediate P&L hit |
| Examples | New product development, major platform builds, on-prem hardware | Maintenance, bug fixes, SaaS subscriptions, cloud consumption |
| Tax treatment | Depreciated (slower deduction) | Deducted in full in current period |
Why This Matters to You
Most engineering managers treat CapEx/OpEx as “finance’s problem.” It’s not. Here’s what happens when you don’t understand the distinction:
-
Your CFO reclassifies your project mid-year. You planned a major platform build as CapEx (spread over 3 years on the P&L). Finance decides it’s actually maintenance (OpEx). Suddenly your team just “cost” the company 3x more this quarter on paper. Your VP gets angry calls.
-
You lose budget flexibility. CapEx budgets are typically approved annually with board involvement. OpEx budgets have more flexibility but hit the P&L harder. Knowing which lever you’re pulling matters for timing requests.
-
Cloud migration changes the math. Moving from on-prem (CapEx: buy servers) to cloud (OpEx: pay monthly) fundamentally shifts your financial profile. Some CFOs love this (no big upfront). Others hate it (can’t capitalize, immediate P&L hit). Know your CFO’s preference.
Software Capitalization Rules (ASC 350-40 / IAS 38)
Under both US GAAP and IFRS, software development costs follow a three-phase model:
| Phase | Can Capitalize? | What Counts |
|---|---|---|
| Preliminary project stage | No – expense immediately | Requirements gathering, vendor evaluation, feasibility studies |
| Application development stage | Yes – capitalize | Coding, configuration, testing of new features, direct labor costs |
| Post-implementation stage | No – expense immediately | Bug fixes, maintenance, minor enhancements, training |
Practical implications for your team:
- Time tracking matters. If your team logs 60% of sprint effort to new feature development and 40% to bug fixes, only the 60% can be capitalized. Many companies require engineering time tracking for this reason – it’s not micromanagement, it’s accounting compliance.
- The threshold for “new feature” vs “enhancement” vs “maintenance” is a gray area. Work with your finance partner to define clear criteria before the work starts, not after.
Budget Cycles – How the Year Actually Works
The Annual Cycle (Typical Large Enterprise)
| Month | Activity | Your Role |
|---|---|---|
| Jul-Aug | Finance sends budget templates & guidelines | Review last year’s actuals, identify gaps |
| Sep-Oct | Bottom-up budget build | Build your budget proposal, justify headcount, negotiate with your VP |
| Oct-Nov | Leadership review & negotiation | Defend your budget, make trade-offs, align with strategy |
| Nov-Dec | Board approval | Usually no action – wait for final numbers |
| Jan | Budget finalized & distributed | Receive your approved budget, plan allocation |
| Monthly | Actuals vs plan review | Track spend, explain variances, adjust forecasts |
| Quarterly | Reforecast (some companies) | Update year-end projections based on actuals |
| Jun-Jul | Mid-year review | Major course corrections if needed |
Building Your Budget – Bottom-Up Template
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
ENGINEERING BUDGET — [Team Name] — FY[Year]
1. PEOPLE COSTS
├── FTE Salaries (existing) EUR ___________
├── New Hires (planned) EUR ___________
│ └── Start dates: Q1: __, Q2: __, Q3: __, Q4: __
├── Backfills (attrition assumption) EUR ___________
│ └── Assumed attrition rate: ___%
├── Employer Social Contributions EUR ___________
│ └── Rate: ___% of gross salary
├── Bonuses & Variable Pay EUR ___________
├── Contractors / Staff Aug EUR ___________
│ └── # contractors × daily rate × days
└── SUBTOTAL PEOPLE EUR ___________
2. CLOUD & INFRASTRUCTURE
├── Cloud Consumption (AWS/GCP/Azure) EUR ___________
│ └── Baseline + growth %: ___
├── On-prem / Data Center EUR ___________
├── CDN / Edge EUR ___________
├── Monitoring & Observability EUR ___________
└── SUBTOTAL INFRA EUR ___________
3. SOFTWARE & TOOLS
├── IDE & Developer Tools EUR ___________
├── CI/CD Platform EUR ___________
├── SaaS (Jira, Confluence, etc.) EUR ___________
├── Security Tools EUR ___________
└── SUBTOTAL SOFTWARE EUR ___________
4. OTHER
├── Training & Conferences EUR ___________
├── Hardware & Equipment EUR ___________
├── Travel EUR ___________
└── SUBTOTAL OTHER EUR ___________
TOTAL BUDGET EUR ___________
Cost Centers & Allocation
How Cost Centers Work
A cost center is an organizational unit that incurs costs but doesn’t directly generate revenue. Engineering is almost always a cost center (unless you sell your platform as a product).
Why this matters: As a cost center manager, you will always be asked to justify costs against business value. You can’t just say “we need 5 more engineers.” You need to say “5 engineers will deliver X capability that drives Y revenue / saves Z cost.”
Cost Allocation Models
| Model | How It Works | Pros | Cons |
|---|---|---|---|
| Direct allocation | Costs charged directly to the team that incurred them | Simple, transparent | Shared services hard to allocate |
| Proportional allocation | Shared costs split by headcount, revenue, or usage | Fair distribution | Can penalize high-usage teams |
| Activity-based costing | Costs allocated based on actual consumption (e.g., API calls, compute hours) | Most accurate | Complex to implement and maintain |
| Fixed allocation | Predetermined split agreed at start of year | Predictable | Doesn’t reflect actual usage |
Recommendation for engineering: Push for activity-based costing for cloud (use cost allocation tags) and proportional allocation for shared services (platform teams, SRE). Avoid fixed allocation – it creates perverse incentives where teams don’t care about efficiency because “it’s not their budget.”
Forecasting – Predicting Where You’ll Land
Forecasting Methods
| Method | When to Use | How |
|---|---|---|
| Run-rate | Stable, predictable costs (salaries) | (YTD Spend / months elapsed) x 12 |
| Bottom-up build | New initiatives, variable costs | Sum of individual line items with assumptions |
| Trend-based | Cloud costs with growth patterns | Historical trend + growth rate adjustment |
| Driver-based | Costs tied to business metrics | Cost per transaction x projected transactions |
Forecast Accuracy Template
1
2
3
4
5
6
7
8
9
10
MONTHLY FORECAST UPDATE — [Month]
Budget Forecast Variance Variance % Explanation
People €XXX,XXX €XXX,XXX €(XX,XXX) -X.X% 1 hire delayed to Q3
Cloud €XXX,XXX €XXX,XXX €XX,XXX +X.X% Traffic spike from campaign
Software €XXX,XXX €XXX,XXX €0 0.0% On track
Contractors €XXX,XXX €XXX,XXX €(XX,XXX) -X.X% Ended 2 contracts early
Other €XXX,XXX €XXX,XXX €(X,XXX) -X.X% Cancelled conference travel
─────────────────────────────────────────────────────────────────────────────────
TOTAL €X,XXX,XXX €X,XXX,XXX €(XX,XXX) -X.X%
Actuals vs Plan – What Finance Cares About
Finance teams track two key metrics:
- Budget variance = (Actuals - Budget) / Budget
- Under 5%: You’re doing fine
- 5-10%: Explain it
- Over 10%: You have a problem
- Forecast accuracy = How close your latest forecast was to actual
- This is about YOUR credibility. A manager who consistently forecasts accurately gets more trust (and more budget) than one who’s always surprised.
The golden rule: No surprises. If you know you’ll be over budget, tell finance early. If you’ll be under, tell them too (they may want to reallocate). Surprises destroy trust.
Anti-Patterns and Common Mistakes
1. “Use It or Lose It” Spending
The mistake: Rushing to spend remaining budget in Q4 to avoid getting cut next year. Why it’s wrong: Finance sees through this. It signals you over-budgeted, not that you’re a good steward. Instead: Return unused budget with a clear explanation. “We saved €50K because we optimized cloud spend” is a stronger position than “we bought random tools in December.”
2. Sandbagging
The mistake: Inflating your budget request by 20-30% expecting it to be cut. Why it’s wrong: If finance doesn’t cut it, you’re stuck justifying spend you don’t need. It also erodes trust when your actuals consistently come in 20% under budget. Instead: Submit a realistic budget with a clear “investment tier” – base budget vs. stretch investments that are explicitly optional.
3. Ignoring Employer Costs
The mistake: Budgeting only base salary when planning headcount. Why it’s wrong: In Germany, employer costs add 25-35% on top of gross salary (social security, health insurance, pension contributions, employer liability insurance). A €100K salary costs the company €125-135K. Instead: Always use fully loaded cost. See Headcount Planning & Cost Modeling.
4. Not Partnering with Finance
The mistake: Treating the finance business partner as an adversary or bureaucrat. Why it’s wrong: Your finance partner controls budget releases, approves headcount requisitions, and reports your numbers to the CFO. They are your most important non-engineering stakeholder. Instead: Meet with your finance partner monthly. Share context about your roadmap. Ask them to explain what metrics their leadership cares about.
5. Annual-Only Budgeting
The mistake: Setting the budget in October and not touching it until next October. Why it’s wrong: Business conditions change. A competitor launches, a key hire falls through, cloud costs spike. Static budgets become fiction by Q2. Instead: Reforecast quarterly. Maintain a rolling forecast that updates assumptions based on actuals.
Frameworks
Zero-Based Budgeting (ZBB)
Instead of starting from last year’s budget and adding a percentage, ZBB starts from zero and requires every line item to be justified from scratch. Useful when:
- The company is in cost-cutting mode
- You inherited a team with unclear spending
- You want to challenge legacy vendor contracts
How to apply: For each budget line, answer: “If we were starting this team today, would we spend this money?” If not, cut it or reallocate.
Beyond Budgeting
A management philosophy that replaces fixed annual budgets with adaptive, rolling forecasts. Popularized by the Beyond Budgeting Round Table (BBRT). Key principles:
- Set relative targets (top quartile performance) not fixed targets
- Use rolling forecasts not annual budgets
- Allocate resources dynamically based on need
- Separate target-setting from forecasting (targets motivate, forecasts inform)
Most relevant for companies moving to agile at scale – the fixed annual budget cycle conflicts with adaptive planning.
Real-World Application
Budget Conversation with Your VP – A Script
When presenting your budget, structure it as:
- Strategy link: “Our roadmap delivers X, Y, Z business outcomes”
- People ask: “This requires N engineers, costing €X fully loaded”
- Infrastructure ask: “Cloud and tools cost €Y, growing Z% due to [reason]”
- Trade-offs: “If we get 80% of this budget, here’s what we cut and the business impact”
- Risks: “Key assumptions that could change: attrition, cloud costs, vendor pricing”
German-Specific Considerations (MMS Context)
- Betriebsrat (Works Council): Headcount changes may require Works Council consultation, which adds lead time to hiring and restructuring plans. Budget for the delay.
- Kurzarbeit: In downturns, German companies can reduce hours (and costs) with government subsidies rather than laying off. Factor this into contingency planning.
- 13th month salary: Common in German employment contracts. Budget 13 monthly payments, not 12.
- Tariff agreements: If your engineers are under a collective agreement (Tarifvertrag), salary bands are fixed. Budget accordingly.
References
- Financial Intelligence for Entrepreneurs – Karen Berman & Joe Knight (2013) – Best intro to finance for non-finance managers
- The Art of Business Value – Mark Schwartz (2016) – Connecting IT spend to business outcomes
- ASC 350-40: Internal-Use Software – US GAAP software capitalization rules
- IAS 38: Intangible Assets – IFRS software capitalization rules
- Beyond Budgeting Round Table – Adaptive management framework
- An Elegant Puzzle – Will Larson (2019) – Chapter on organizational design and resource allocation
- Engineering Budget 101 – LeadDev – Practical talks on engineering financial management