blog

Operating Model Transformation: The PMO Sees Everything Except Margin

By Shivani Kumar

|

Updated: August 21, 2026

|

Read Time: 6–7 minutes

Blog Highlights

  • IT services operating model change most commonly fails at the financial layer. Delivery milestones, resource utilization, and client satisfaction levels pass through to the PMO – but the only number that makes or breaks a service business – margin – is not transparent. SPI Research’s 2026 Benchmark illustrates why with billable utilization slumping to 66.4% – the 10-year low – although revenue still grew this period.
  • The five Financial Mechanics to change: visibility of cost of resource at allocation, timesheet with a billing interface, change order if a change in scope occurs, cost on bench as an actual P & L signal; portfolio-level margins on PMO dashboard.
  • High-performing IT services firms have a 19 per cent advantage in cross-organization visibility. This visibility dividend delivers margin.
  • The reason almost every IT service delivery team hits a wall at SPI level 2 or 3-the single capability that the 2026 benchmark prove is the differentiator of high-performing organizations-is failure to have real-time, integrated visibility to delivery, resources and financials.
  • The combined strength of the Kytes platform integrates delivery execution and project financial management in a single AI powered PSA platform. From a single dashboard, PMO teams gain visibility into both delivery progress & margins. As such, operating model transformation delivers the commercial benefits that it was chartered to deliver.


QUICK ANSWER

IT operating model transformation is the deliberate and organised redevelopment of how a business designs, builds and manages the funding of its project delivery. It rethinks how income is accounted for, how resources are costed and how profit margins are secured from bid to closure. Transformation the does the development redesign without the financial redesign delivers a constant outcome – a PMO that knows all about project but nothing about profit.

The Transformation That Looks Like Progress Until the P&L; Arrives

The PMO director of a 900-person IT engineering business spent fourteen months driving her firm’s operating model change. She implemented stage gates, project templates, moved to a resource planning tool. All key metrics had improved; the board loved the progress.
Then came the quarter’s P+L. The project margin had dropped 6%. The changes were making things clearer without making them more profitable, resource costs were not being tied to billing events, timesheet data fed the resource planning tool but not project accounts, change control forms were being submitted after the scope had already expanded by 3 weeks. The company had better but earned less.
The PMO director could account for the time on every engagement. She could view, for all 47 concurrent projects, milestone completion percentages, utilization and delivery confidence. Margin was missing.

What Is Operating Model Transformation in IT Services?

Operating model transformation is about reshaping how a services organisation goes about designing and managing the way the work is performed to derive positive commercial benefit. The major dimension of change is financial, and there are four interacting changes that constitute successful operating model transformation:

Why Do Most Operating Model Transformations Fail in IT Services?

What Metrics Does AI Resource Planning Track in Real Time?

All but the smallest IT Service organizations hit an SPI maturity wall at Level 2 or 3, because they are not gaining unified, real-time insight across the entire delivery continuum, resources, and financials. That, alone is the single capability that the 2026 benchmark validates as differentiating the high performer from the rest. They fail consistently.

What Financial Mechanics Must Change for Transformation to Succeed?

The 2026 SPI Research benchmarks are clear -utilisation greater than 70%, project overrun less than 10%, project margin greater than 35%, revenue per billable consultant greater than $200,000, and revenue leakage less than 5%. That’s how it differentiates IT services companies that are delivering sustainable profits from those that continue to increase revenue but contract profitability. Five financial mechanisms will need to be retooled.

How Does Project Financial Management Connect to Operating Model Success?

Operating model defines how we structure, governed and execute work. Project financial management defines that work, at the end, is generating the margins it set out to create. In most IT services companies, it’s seen as two functions: a PMO determines delivery plan; a finance group determines the bottom line; and the two come together at month’s end.

But in the transformed operating model both flow from the same systems.

Resource assigned updates the delivery plan and the financial forecast. Milestone achieved triggers the project’s status report and the billing workflow; project closed leads to sign-off and financial reconciliation. Organizations that have integrated project financial management into their operating model see higher project margins, speed revenue, and lower billable rates.

How Does Kytes Support Operating Model Transformation for IT Services?

For the IT services enterprises with which we work, the failed operating model transformations fail at the finance layer. We renovate governance structures. We implement the enterprise project management system.

The PMO realizes they don’t see current by the project margin, cannot follow cost of bench in the current time, cannot associate timesheet with billing except by means of exporting data to finance (manually).

Kytes resolves the situation. Kytes – it is AI-powerful PSA & enterprise project management systems created from the ground up by the company IT-services providers. It associates delivery governance with fiscal governance within a system: here each enterprise-project-driven occurrence revivifies and delivery, and business views.

Frequently Asked Questions

IT Service Operating Model Transformation This is a planned renovation of the way a company plans, executes and funds project delivery. It impacts how revenue is booked, how resource costs are managed and how the margins on projects are protected from bid to close. Business Process Only transformation without remodeling the financials creates better organized activities that deliver a narrowing margin.
This is because enterprise project management software is being chosen for deliverability visibility without any questioning on whether there is real time link-back to project finances. The PMO sees delivery. What they don't see is profitability at the level of delivery. SPI Research's benchmark report 2026 has identified it as the #1 failure mode with executive real-time visibility declining over the year to year despite investment in new software platforms.
The single most common pattern of failure is leaving financial layer late. This means the transformation programmed builds the delivery process, governance structure and the team structure before it works out how project delivery financial will operate (if at all). Margins wither until the quarter ends, the PO and the quarterly P+L materializes. It’s the reason Why IT Services companies get stuck on Level 2/3 of SPI Maturity
5 mechanics need to be reengineered: seeing allocation resource cost rate upfront at allocation; making timesheets aligned to the billable rate closing the revenue leakage delta; have change orders process as scope expands in the front of cost accrual; having a benchmark cost as a live P&L; signal and seeing portfolio level margin for PMO without waiting for F&A closing
Increased project margin by using cost-rate-smart resource assignment, accelerating revenue by automate the process of time entries into bills and reduce overhead costs due to increased visibility into periods of non-activity and early identification of upcoming demands. The target range for high performers according to the SPI 2026 benchmark is Utilization > 70%, project overrun < 10% and project margin > 35%. Operating Model Transformation hits these benchmarks by redesigning the financial layer of the delivery, not only.


Shivani Kumar

linkdin

Shivani Kumar is the Co-founder and Head of Marketing at Kytes, and part of the founding team since day one. She’s helped build the AI-enabled PSA+PPM platform from the ground up—translating customer pain points and market gaps into executable roadmaps. She believes AI creates real value only with strong systems and structured data. She applies that lens across product, GTM, and marketing, and shares practical, real-life insights from her experience in SaaS, AI, and B2B marketing.