You approve the technology budget. You can't prove what it bought.
Every other function in the business runs inside a financial accountability framework. Sales has pipeline, margin, customer acquisition cost. Operations has output per dollar. Technology runs on uptime, ticket counts, and "operating well" assertions, and gets funded on faith. The fix is not more diligent budgeting. It is a financial operating model for technology that mirrors how you manage every other capital allocation.
Where you sit today
Three truths from inside your role.
Three patterns recur across CFOs who describe the situation above. Not all three may apply to you, but one or two usually will.
You fund IT without a framework for evaluating return
Every other capital decision has a business case. Technology investments arrive with technical justification. The mismatch is structural.
IT reports to you in technical language
Uptime, incident counts, project delivery rate. These tell you whether IT is functioning. They tell you nothing about whether it is creating value.
You suspect significant overspending and cannot prove it
The shape of vendor contracts, SaaS sprawl, infrastructure scaled for historical peak. The savings are there. The framework to surface them is not.
What changes with Preside
Three structural shifts, not three projects.
A technology P&L by business function
IT spend mapped to the parts of the business it supports. Cost per unit of business output. Vendor and licensing utilization measured against spend.
A capital allocation framework for technology
Every initiative has a business case, projected return, and post-implementation accountability. Same rigor you apply to every other capital decision.
Reporting in your language, not theirs
Quarterly review in P&L format. Risk in dollars. Spend trajectory. Return realized by initiative. One page the board can read and act on.
A sample of the artifact
What your technology P&L view actually looks like
Illustrative figures from a $180M-revenue services firm. Structured against the TBM v4 tower taxonomy (the IT-finance industry standard governed by the TBM Council). Numbers anonymized but representative of the spend pattern at this scale. Every row reconciles; every benchmark is sourced.
Fiscal year forecast, Q3 in-flight
Technology P&L by TBM tower
| TBM tower | FY plan | YTD (Q3) | FY forecast | % of revenue | Avasant 50th pctile, services |
|---|---|---|---|---|---|
| End User Computing | $810K | $608K | $830K | 0.46% | 0.40 – 0.55% |
| Infrastructure & Cloud | $1,350K | $1,000K | $1,395K | 0.78% | 0.70 – 0.90% |
| Business Applications | $1,485K | $1,113K | $1,510K | 0.84% | 0.80 – 1.00% |
| Data & Platform | $324K | $243K | $330K | 0.18% | 0.15 – 0.25% |
| Security, Compliance & DR | $594K | $445K | $620K | 0.34% | 0.30 – 0.50% |
| IT Management & Delivery | $432K | $324K | $440K | 0.24% | 0.20 – 0.30% |
| Telecom & Connectivity | $162K | $122K | $165K | 0.09% | 0.05 – 0.15% |
| Strategic Initiatives | $243K | $182K | $310K | 0.17% | initiative-level ROI tracked separately |
| Total IT | $5,400K | $4,037K | $5,600K | 3.11% | 3.0% (Avasant 50th pctile) |
Analytical notes
- Run / Grow / Transform mix. FY forecast splits as $3.45M Run (62%) / $1.84M Grow (33%) / $0.31M Transform (5%). Strategic Initiatives line carries an additional $310K that splits across Grow and Transform when classified at the initiative level. Healthy mid-market range per Gartner: ≤50% Run / 30 to 50% Grow / 10 to 25% Transform. Run share is elevated; primary driver is Infrastructure & Cloud.
- Vendor concentration. Top 3 software vendors (Microsoft 365, Salesforce, AWS) = 52% of software spend. Industry median ~55% per Vertice SaaS Benchmarks 2025. Acceptable; monitor at next renewal cycle.
- Realized savings, fiscal year to date. $380K recovered through vendor consolidation and license rightsizing. Tracked separately from period spend; results from prior-year Two-week Vendor Rationalization Initiative flowing through this year's P&L.
- Annualization basis. % of revenue uses FY forecast divided by FY revenue ($180M). YTD column reflects three quarters elapsed; FY forecast = YTD actual + Q4 projection.
Decisions surfaced for next quarter
- Vendor X renewal in Q4: 41% seat utilization on a $205K annual contract. Tier reduction projects $84K annual savings.
- Project Atlas: 8 months into a 12-month rollout. Original ROI case projected $1.2M annual benefit. Track-to-date suggests $700K to $900K. Decision required: continue, restructure, or stop.
- Shadow SaaS: 6 net-new tools discovered via expense reports this quarter. None in IT inventory. $112K annualized. Sanction or consolidate.
Sources: TBM Taxonomy v4 (TBM Council), Avasant IT Spending Benchmarks 2024-2025, Chapter 40: IT Services and Consulting, Gartner IT Key Metrics Data 2025, Vertice SaaS Spending Benchmarks 2025.
Your recommended initiative
Three-week Cost Optimization Initiative
The deliverable
A technology P&L with vendor and licensing spend mapped to actual utilization. Identified savings with implementation timeline and confidence range.
See the initiative methodology →What we typically find
CFOs who get this right do not change their IT team. They build the translation layer that lets the existing team produce the financial accountability the function has never been asked to produce. The IT director's work does not change. What gets measured and reported does. That is what makes technology fundable on the same basis as everything else you fund.
What CFOs ask first
The four questions that come up before the engagement.
In writing, because every CFO we've worked with raises some version of these in the first conversation. Better to address them here than to leave them as a reason not to start.
Don't I already get this from my GL?
Your GL tells you what you spent on technology. It does not tell you what business outcome it produced, which initiatives are tracking to their original business case, or which vendors are under-utilized. This view sits on top of your GL data, not in place of it.
How does this differ from a fractional CIO?
A fractional CIO is one experienced operator giving you part-time advisory. This is a small team producing the financial accountability artifact every quarter, plus the discipline behind it. Different output, different price point, different decision basis.
What happens to my existing IT director?
Their role does not change. Their reporting does. We take their operational data and produce the business-facing view. They run IT. We translate IT into the language you and the board fund decisions in.
What's the year-one math?
Most engagements at this scale recover 15 to 25 percent of in-scope IT spend in the first twelve months through vendor consolidation, license rightsizing, and renewal renegotiation. "In-scope" means the vendor, licensing, and managed-service spend categories the engagement covers, typically excluding internal IT labor unless requested. This sits on the conservative end of published industry ranges of 20 to 30 percent for vendor consolidation savings (Forrester, CloudEagle, BetterCloud 2024-2025); verified across our engagements. The Three-week Cost Optimization Initiative sizes the specific opportunity in your environment before any longer commitment.
If you are a CFO at a PE-backed company
Four pressures specific to the PE-portco finance seat.
Generalist enterprise CFO framing does not address the operating constraints of a PE-backed finance seat. Each of these shapes the work and the calendar.
- Quarterly board reads in PE format. Reporting is to a board structured around fund-cycle milestones, not your fiscal year. The Technology P&L view is sized to land in the same package as your other quarterly artifacts.
- Add-on M&A finance integration. Add-ons arrive faster than the finance integration plan. Technology synergies modeled in the LBO are not always captured operationally. The reconciliation has to happen before the next exit conversation.
- Hold-position cost flex. A CFO at month six of a hold has different cost flex than one twelve months from exit. The technology cost framework calibrates to where the company sits in the hold cycle.
- Exit-data-room financial readiness. Buyers’ diligence teams ask for technology spend mapped to outcomes 12 to 18 months ahead of exit. What gets built during the hold is what survives at the bid.
Start with the Tech P&L. Then decide.
Two to three weeks. The artifact lands on your desk. If it does not make every quarterly conversation sharper, you are under no further commitment.