# The IT Function: From Service Provider to Business Partner

Author: Marin Niehues, Niehues Consulting · Published: 2026-04-02 · Updated: 2026-11-16 · Organizational Design
Source: https://www.niehuesconsulting.com/blog/it-function-business-partner/

An IT function becomes a partner to the business when it takes responsibility for business outcomes and aligns funding and metrics accordingly. The shift is an organizational undertaking: it changes who prioritizes, how initiatives are funded and how performance is measured. This article describes four role models for IT and shows which obstacles slow the transition and which levers make it steerable.

The literature calls the goal business-IT alignment: business strategy and IT strategy are matched so that technology investment pays measurably into business objectives. The Strategic Alignment Model by Henderson and Venkatraman shaped the term in the early 1990s. This article translates it into decision rights and budgets as well as roles, the variables an executive team can actually steer.

**The role of IT follows decision rights and funding: where the business unit orders and IT executes, IT remains a service provider.**

## Four role models for the IT function

Executive expectations of IT differ considerably from one company to the next. A maturity model with four role models helps to determine where you stand.

- Contractor: IT implements requirements that the business unit orders by ticket or commission. The yardstick is fulfillment of the order.
- Service provider: IT delivers defined services with agreed service levels. The yardstick is availability and response time.
- Partner: IT, together with the business unit, is accountable for products and their results. The yardstick is business benefit.
- Shaper: IT contributes to the offering and the business model, for example in digital products and data-based services. The yardstick is the contribution to revenue and competitive position.

Many IT functions in mid-sized companies and corporations sit between service provider and partner. They deliver reliably what is ordered, yet have no influence on whether the order addresses the right lever. The transition to partner therefore changes decision rights and funding on both sides of the interface, and it cannot be decided from within IT alone.

For most companies the target is the partner. The shaper fits where digital services earn a distinct share of revenue, as in platform businesses or software products. For an industrial company with a physical core product, the partner model is sufficient, provided IT has a say in the business units' roadmap.

With AI, the question gains weight. According to the German Federal Statistical Office, 26 percent of companies with ten or more employees used AI in 2025, rising to 57 percent among companies with 250 or more. Applications arise in the business unit but need a platform and data access as well as operations. An IT that works through orders readily becomes a bottleneck in AI initiatives. An IT with product responsibility provides platform and operations at the pace of the business units, and the benefit of the applications becomes a shared target.

## Why does IT remain a service provider?

IT remains a service provider as long as budgets flow per project, priorities emerge through escalation and reports show only operations. Four obstacles recur in practice, and they are linked.

The first obstacle is project funding. Budgets are approved per project, the team dissolves after acceptance, and nobody is accountable for later use. The result is a stock of solutions without owners. How budgets can be tied to value streams is described in the article [Portfolio Management: Linking Budgets to Value Streams](/blog/portfolio-management-value-stream-budgets/).

The second obstacle is prioritization. Business units submit requests, IT sorts them by urgency and volume, and conflicts travel up to executive management. Without shared criteria, escalation ultimately decides.

The third obstacle lies in the metrics. Availability and ticket cycle times measure operations. Whether a product raises revenue or lowers cost, they do not show. As long as IT reports show only operational figures, its contribution to the business remains invisible.

The fourth obstacle concerns roles. The interface between business unit and IT is often staffed by coordinators who hold neither decision rights nor budget. Business units bypass them and procure their own tools. Shadow IT emerges with consequences for security and operations, and with AI tools it emerges particularly fast.

**Signs that IT still operates as a service provider**
- Budget is approved per project, and there is no standing team after acceptance.
- The backlog of requirements is longer than capacity, and nobody prioritizes it jointly.
- IT reports show availability but no business benefit.
- Business units procure their own tools without coordination with IT.
- IT learns of new initiatives only once the decision has been taken.

## Four levers for the shift

The transition follows four levers that act together. Each one remains incomplete without the others.

- Joint prioritization: a forum of business-unit heads and the head of IT decides at a fixed rhythm on value and effort. Decision rights are set in advance.
- Funding along products: stable teams receive continuing budgets and are accountable for use and further development.
- Roles with outcome responsibility: a product owner, usually from the business unit, is accountable for benefit, and a delivery manager is accountable for the route to delivery.
- Metrics with a link to impact: delivery capability and business usage join availability.

The second lever changes the logic of the organization most strongly. Whoever moves from projects to products shifts responsibility from acceptance to continuing impact. The article [Product Organization: From Projects to Products](/blog/product-organisation-projects-to-products/) describes the changeover. How the four levers fit into an operating model for the whole organization is shown in the article [Operating Model](/blog/operating-model-before-structure/).

**Service-provider model and partner model compared**
Criterion | Service-provider model | Partner model | With Niehues Consulting
Steered by | Orders and service levels | Products and outcomes | Delivery management with impact targets per product
Funding | Project budgets | Product budgets | Stepwise changeover with a business case per product
Prioritization | IT's backlog of requirements | Joint roadmap | Decision rights set in advance, rhythm rehearsed
Role at the interface | Coordinator without budget | Product owner and business relationship manager with a mandate | Role profiles and mandates agreed in writing
Metrics | Availability and ticket times | Delivery capability and benefit | Metric set linked to impact, with continuous reporting

## Cost center or profit center: which steering model suits IT?

For an IT function that delivers mainly internally, neither the pure cost center nor the profit center fits. The cost center rewards falling costs and turns IT into a savings item, even where an investment would yield the greatest business return. The profit center creates internal transfer prices over which business units and IT negotiate, and shifts attention from impact to billing.

Steering IT as an investment area with product budgets has proven effective: executive management approves budgets per product or value stream and measures the business return. The profit center is the right choice when IT sells services to external customers on a meaningful scale. The cost center remains appropriate for standardized base services such as workplace or data center, where unit cost is the right yardstick.

## How long does the shift to partner take?

A pilot area produces robust results after two to three quarters, and changing over the entire IT function takes two to three years. A transition of this size succeeds in steps. The principle: first make the interface visible, then prove the model in one area.

The first step is the stocktake, over six to eight weeks. It clarifies who decides what at the interface, how budgets flow and which metrics are reported today. This usually shows where lived practice and organization chart diverge.

The second step is a pilot area. One business unit and IT form a stable team for one or two products with a clear division of roles, a product budget and a shared system of objectives. After the first delivery cycles, reliable experience of pace and impact is available.

The third step is the spread to further areas. Roles and forums are standardized, as are the metrics. The people involved are enabled, and executive management steers progress through reporting. With more than five business units, a rollout in waves of two to three units per half-year is advisable.

The article [characteristics and metrics of a high-performing organization](/blog/high-performing-organisation/) describes the relationship between structure and delivery in detail.

## Niehues Consulting as a partner for changing the IT function

[Niehues Consulting](/) works from the delivery perspective: what matters is what actually arrives and works in the organization. In delivery management, Niehues Consulting steers the initiative as delivery manager, project manager or product owner and thereby takes responsibility for delivery itself. Organization design sets structures, roles and decision paths so that the organization delivers reliably, in day-to-day business and in transformation.

The approach follows the Niehues Delivery Model with its phases Understand, Build, Introduce. Three of its review questions matter most for changing the IT function. Who decides, who delivers, who uses? Which roles, decision paths and interfaces does operation require? Who is accountable for operation from day one? The analysis makes the interface between business unit and IT visible, the pilot area proves the new collaboration in the real workflow, and the introduction anchors responsibilities and metrics.

Founder Marin Niehues brings project experience from VC-funded scaleups to DAX 40 corporations, with assignments in 20+ countries on six continents. The entry point is a free initial consultation of 30 minutes: [request an initial consultation](/#kontakt).

**Conclusion for executive management**
IT becomes a partner to the business when prioritization and funding as well as metrics are reordered jointly with the business units. Executive management sets the decision rights for this and names those accountable for outcomes. A pilot area supplies early proof against which the further changeover is aligned.

**Sources**
- Henderson, Venkatraman: Strategic Alignment: Leveraging Information Technology for Transforming Organizations, IBM Systems Journal, 1993
- German Federal Statistical Office (Destatis): Use of information and communication technologies in enterprises, 2025

## Frequently asked questions

### What is business-IT alignment?

Business-IT alignment is the matching of business strategy and IT strategy so that technology investment pays measurably into business objectives. In practice it shows in shared priorities and product budgets, together with metrics that have a business link. Where it is missing, requirement backlogs without ranking and solutions without users emerge.

### What does it mean when IT is a partner to the business?

IT is accountable, together with the business unit, for products and their benefit. It works to a joint roadmap, is funded through product budgets and reports impact instead of purely operational figures. Decision rights between business unit and IT are settled in advance for this purpose.

### What does a business relationship manager in IT do?

A business relationship manager connects one or more business units with IT, understands their business goals and translates them into prioritized initiatives. The role bundles demand, prepares decisions for the prioritization forum and tracks whether delivered solutions bring the expected benefit. Frameworks such as ITIL describe the role in detail. It becomes effective only with a mandate, meaning a voice in prioritization and access to business-unit leadership.

### Should IT be a cost center or a profit center?

For an IT function delivering mainly internally, steering through product budgets with impact targets works better than either pure form. The profit center fits when IT sells to external customers on a meaningful scale. The cost center fits standardized base services whose yardstick is unit cost.

### What percentage of revenue do companies spend on IT?

The share of revenue spent on IT differs between industries by a multiple. Financial services and media sit well above manufacturing and construction, and values also diverge widely within a single industry. As a steering figure the ratio is therefore of limited use. More telling is which share of the budget flows into products with measurable business benefit and which share keeps the existing estate running.

### Which metrics show that IT works as a partner?

Besides availability and ticket times, the report contains lead time and schedule adherence, supplemented by delivery quality, as well as the actual use of products. Added to this is the business effect, such as processing time saved or revenue gained per product. Only these figures show whether delivery arrives in the business.

### How does AI change the role of IT?

AI applications often arise in the business unit and need a platform and data access as well as operations from IT. IT thereby becomes an enabler and the operator of shared platforms. This requires product responsibility and rapid coordination with the business units.

### How long does the shift from service provider to partner take?

A pilot area produces robust results after two to three quarters, and changing over the entire IT function takes two to three years. The preceding stocktake takes six to eight weeks. With more than five business units, the rollout follows in waves of two to three units per half-year.
