December, budget session. The CTO presents the 2026 plan: “We need 8 new developers, that’s 2.4M PLN”. The CFO responds: “You showed headcount and costs. Where’s the business case? What’s the ROI? What do we get for those 2.4M?”. The CTO tries to improvise: “Faster feature delivery, fewer bugs…”. The CFO interrupts: “Those aren’t numbers. Come back with something concrete.”
Read also: Technical Debt 2026: How to Measure and Pay Down Technical D
This scene repeats in technology companies with frustrating regularity. IT speaks the language of technology (velocity, tech debt, scalability), Finance speaks the language of business (ROI, payback period, TCO). Without translation, budgeting becomes a battle, not a collaboration. The CTO feels that Finance “doesn’t understand”, the CFO feels that IT “can’t justify”. The truth: both sides are right, a common framework is missing.
Why does the standard approach to IT budgeting fail?
Historical budgeting - “give me what I had last year plus inflation” - doesn’t work for development teams. IT is not a static cost center like office space or utilities. Needs change with the product, market, and technology. Copying last year’s budget ignores these changes.
Zero-based budgeting - “justify every dollar from scratch” - is theoretically better but often leads to decision paralysis and political games. Every item is questioned, forcing defensive positioning instead of strategic thinking.
Headcount-driven budgeting - “I need X people” - misses the fundamental question: for what? The CFO doesn’t care how many heads you have - they care what those heads produce and for how much. Headcount is input, not output.
Technology-first budgeting - “we need to modernize the stack” - speaks to technologists, not business. The CFO doesn’t know (and doesn’t need to know) why Kubernetes is better than what we have. They need to know what business problem it solves and what the return is.
Project-based budgeting without portfolio view - a list of projects with costs, without connection to the company’s strategic priorities. Finance sees fragments, not the whole picture. No clarity on how the IT budget maps to business objectives.
How to build a Total Cost of Ownership model for an IT team?
TCO starts with complete cost identification - not just salary. Each person on the IT team generates direct and indirect costs that must be accounted for to get an accurate picture.
Direct costs per person: gross salary, employer contributions (social security, funds - approximately 20% above gross), benefits (medical package, gym membership, insurance - typically 500-1500 PLN/month), training and conferences (annual budget - 5000-15000 PLN), equipment (laptop, monitors, accessories - amortized annually approximately 5000-8000 PLN).
Indirect costs per person: office (space cost, utilities - 1000-2500 PLN/month in a major city), software licenses (IDE, tools, SaaS per seat - 500-2000 PLN/month), HR and administration overhead (recruitment, onboarding, payroll - approximately 5-8% of personnel costs).
Full cost formula: gross salary × 1.45-1.55 for fully-loaded cost. A developer with 25,000 PLN gross actually costs 36,000-39,000 PLN monthly. Annually: 430,000-470,000 PLN. These are the numbers the CFO needs to see - not headline salary.
Contractors and body leasing in the cost model. The invoiced rate already includes most overhead - but consider hidden costs: onboarding time, knowledge transfer, management overhead. For comparison with full-time employment: multiply the rate by 12 and compare with fully-loaded employee cost.
Build vs. buy analysis. Full-time hiring: higher upfront cost (recruitment, onboarding), lower long-term unit cost, risk of fixed commitment. Contractors: lower upfront (immediately available), higher unit cost, flexibility. A hybrid model is often optimal: core team on salary, variable capacity through contractors.
How to present ROI from IT team investment?
Revenue attribution - IT’s direct contribution to revenue. A new feature that generates X new customers × average revenue per customer = attributed revenue. Checkout conversion optimization by 2 percentage points × current traffic = additional revenue. These are numbers the CFO understands and appreciates.
Cost avoidance - preventing costs that would occur without the investment. Modernizing a system that would fail = cost of downtime avoided. Automating a manual process = saved FTEs. Security improvements = risk-adjusted cost of potential breach avoided.
Productivity multiplier - how new people affect the output of the entire team. Not just “8 new devs = 8× more code”. A senior developer mentoring juniors increases their productivity. A DevOps engineer automating pipelines increases everyone’s velocity. Quantify the multiplier effect.
Time-to-market value. Faster feature delivery = earlier revenue. If a new product generates 100,000 PLN monthly and additional resources accelerate launch by 3 months = 300,000 PLN additional revenue. This is a compelling argument.
Opportunity cost lens. “What do we lose by NOT investing?” Delayed projects = lost market share. Overwhelmed team = higher turnover = recruitment and training costs. Technical debt accumulation = future velocity reduction. Frame as risk, not just missed opportunity.
Payback period calculation. Investment of 2.4M PLN in team, expected additional value of 4M PLN annually = payback in 7-8 months. This is a metric the CFO understands. If payback > 24 months - the investment is questionable; < 12 months - compelling.
How to build a capacity planning model?
Demand forecast - how much work do we anticipate? Product roadmap translated into effort. Each epic estimated in story points or person-days. Aggregation gives total demand. Distribute across quarters - demand isn’t flat.
Supply analysis - how much capacity do we have? Number of developers × available working days × productive time (typically 70-80% after subtracting meetings, vacation, sick leave). Current capacity = X story points per quarter.
Gap analysis - demand minus supply. If demand = 2000 story points/Q, supply = 1500 - gap = 500, meaning you need +33% capacity. Translating to headcount: 500 ÷ avg velocity per dev = how many new people.
Buffer planning - don’t plan for 100% utilization. Unexpected work (bugs, urgent requests, production issues) consumes 15-25% of capacity. Ramp-up time for new people (3-6 months to full productivity). Turnover replacement (on average 15% will leave annually). Build in buffer.
Scenario planning - optimistic, realistic, pessimistic. What if demand grows faster? What if slower? What if a key person leaves? A budget with variants gives the CFO confidence that you’re thinking about risks.
Quarterly recalibration - capacity plan isn’t a one-time exercise. Quarterly review: is delivery on track with the plan? Has demand changed? Adjust forward projection. Show the CFO that you monitor and adapt.
How to categorize and prioritize IT spending?
Run vs. Grow vs. Transform framework. Run: maintaining current systems, support, maintenance - must have, but doesn’t generate new value. Grow: developing products, new features, customer-facing improvements - generates revenue. Transform: modernization, new platforms, tech enablement - enables future growth.
Typical distribution: 60-70% Run, 20-30% Grow, 10-15% Transform. If Run dominates (80%+) - organization is stuck, no innovation. If Transform dominates - probably over-engineering before real need.
MoSCoW prioritization for projects. Must have: regulatory compliance, security critical, revenue-blocking fixes. Should have: significant business value, reasonable ROI. Could have: nice improvements, lower ROI. Won’t have: deferrable, low value.
Stack rank all initiatives. Force yourself to order everything: if you can only do 1, which one? If 2? If 5? This eliminates the “everything is a priority” trap. The CFO appreciates clarity.
Investment vs. Expense lens. CapEx (capitalized: product development, new platforms) vs. OpEx (operational: maintenance, support, SaaS). Accounting treatment differs - check with Finance how to classify for optimal presentation.
How to present the IT budget in business language?
Mapping to business objectives. Not “we’re hiring 3 backend devs” - “we’re supporting the goal of increasing customer base by 40% through development of new features”. Every budget line item links to a business goal.
Metrics that matter to CFO: payback period, ROI, cost per transaction, cost per customer acquired, revenue per employee. Translate technical details into these metrics.
Risk language. “Without this investment, we risk: delay of Product X by 6 months (= 2M lost revenue), departure of key developers (= 400k recruitment cost), security breach (= potential 5M liability)”. Risk quantification resonates with Finance.
Benchmarking. “Our IT investment as % of revenue is 12%, the benchmark for our industry is 10-15%, so we’re within norm”. External data legitimizes internal asks.
Visual storytelling. Charts > tables > text. Trend lines showing capacity gap. Pie charts showing budget allocation. Waterfall showing cost buildup. The CFO processes hundreds of pages - make it scannable.
Executive summary upfront. One page: what you’re asking for, why, what return, what risk without it. Details in the appendix for those who want them.
How to manage the IT budget throughout the year?
Monthly cost tracking vs. budget. Variance analysis: why did we spend more/less? One outlier is noise, a trend is signal. Early warning for problems.
Reforecast quarterly. The initial budget was a guess - better than random, but a guess. With data from Q1, update the forecast for Q2-Q4. The CFO appreciates proactive updates, not surprises at year end.
Contingency management. 10-15% of budget as contingency for unexpected needs. Governance on who can use it and for what. Unused contingency isn’t failure - it’s disciplined management.
Savings reinvestment advocacy. If you find savings (e.g., through optimization, renegotiation, attrition not backfilled) - negotiate with the CFO that some returns to IT for priorities. This incentivizes efficiency.
Cost transparency for teams. Every team lead should know how much their team costs. Builds ownership and awareness. “This architectural decision will increase cloud costs by 50k annually” - informed tradeoffs.
How to account for hidden costs and risks in the budget?
Technical debt servicing. Technical debt has an interest rate - time spent on workarounds, slower development, more bugs. Estimate: how much capacity do you lose servicing debt? This is a real cost invisible in the standard budget.
Turnover cost. Average cost of replacing a developer: 50-200% of annual salary (recruitment, onboarding, ramp-up, lost productivity). At 15% turnover and a 30-person team, 4-5 people leave annually = hidden cost of 500k-1M PLN.
Knowledge loss risk. If critical knowledge is in the heads of 2-3 people - what if they leave? Quantify: cost of recreating knowledge, risk to projects. Investment in documentation and knowledge sharing as mitigation.
Burnout and productivity decay. An overloaded team has declining productivity. 60+ hours weekly over an extended period = 20-30% productivity drop. Hiring more people may be cheaper than “squeezing” the current team.
Compliance and security costs. Regulatory changes, audit preparation, security incident response. Often forgotten in baseline budgeting, then surprise expenses.
How to negotiate the IT budget with leadership?
Anchor high, expect negotiation. Don’t ask for exactly what you need minimum - ask for a bit more. Negotiations are expected; the starting point matters.
Trade-offs explicit. “I can do A, B, C with this budget. If the budget is smaller, I must choose: A and B without C, or A and C with delayed B”. Force a decision instead of “give me less and I’ll manage somehow”.
Show your homework. Detailed analysis builds credibility. “I reviewed every line item, optimized what I could, here’s what remains” is stronger than round numbers without backing.
CFO’s concerns anticipation. What will they push back on? Prepare answers. “Why so much on training?” - “Retention and upskilling is cheaper than external hiring”. “Why new people instead of overtime?” - “Sustained overtime leads to burnout and higher turnover, costing more long-term”.
Align with company priorities. If the CEO talks about expansion into a new market - your budget supports that. If priorities are cost reduction - show how IT investments reduce costs elsewhere.
Multi-year perspective. Not just 2026 - show trajectory. “In 2026 we invest in platform, in 2027 and 2028 we reap benefits in lower run costs and faster time to market”.
Table: IT team budget template for CFO
| Category | 2025 Actual | 2026 Budget | Change | Justification |
|---|---|---|---|---|
| PEOPLE | ||||
| Existing headcount (30 FTE) | 13.2M PLN | 14.0M PLN | +6% | Inflation adjustment, merit increases |
| New hires (8 FTE) | - | 3.2M PLN | New | Support growth initiative X (ROI: 18 months) |
| Contractors/Body leasing | 1.5M PLN | 1.8M PLN | +20% | Flex capacity for Y project |
| Training & development | 0.3M PLN | 0.4M PLN | +33% | Upskilling for new stack, retention |
| SUBTOTAL PEOPLE | 15.0M PLN | 19.4M PLN | +29% | |
| TECHNOLOGY | ||||
| Cloud infrastructure | 2.4M PLN | 3.0M PLN | +25% | Scale for user growth 40% |
| Software licenses | 0.8M PLN | 0.9M PLN | +12% | New tools, seat expansion |
| Hardware refresh | 0.3M PLN | 0.4M PLN | +33% | 3-year cycle, new hires |
| SUBTOTAL TECH | 3.5M PLN | 4.3M PLN | +23% | |
| PROJECTS | ||||
| Initiative X (revenue) | - | 1.2M PLN | New | Expected revenue: 4M PLN/year |
| Platform modernization | 0.5M PLN | 0.8M PLN | +60% | Reduce run costs by 20% in 2027 |
| Security & compliance | 0.4M PLN | 0.5M PLN | +25% | Regulatory requirement |
| SUBTOTAL PROJECTS | 0.9M PLN | 2.5M PLN | +178% | |
| CONTINGENCY (10%) | 1.9M PLN | 2.6M PLN | Buffer for unknowns | |
| TOTAL IT BUDGET | 21.3M PLN | 28.8M PLN | +35% |
Key metrics:
- IT spend as % of revenue: 11% (industry benchmark: 10-14%)
- Payback on new investments: 14 months
- Cost per developer (fully loaded): 467k PLN/year
- Run/Grow/Transform split: 55% / 30% / 15%
IT budgeting isn’t a battle with Finance - it’s a collaborative exercise in allocating limited resources for maximum return. A CTO who speaks the language of business, shows ROI, and understands trade-offs isn’t a petitioner asking for money - they’re a partner in company strategy.
Key takeaways:
- TCO, not headcount - show full cost, not headline numbers
- ROI, not technology - translate into business value and metrics
- Capacity planning based on demand - justify needs with numbers
- Run/Grow/Transform categorization - show where the money goes
- Risk quantification - what we avoid through investment
- Executive summary + details - cater to different reading depths
A well-built IT budget builds trust with Finance and facilitates future conversations. A poorly-built one creates cycles of conflict and distrust.
ARDURA Consulting supports organizations in flexible IT team scaling through body leasing and staff augmentation, which provides flexibility in budget planning. Let’s talk about how we can help with optimal IT resource budgeting.