Skip to main content

Meet the Newest Profit Center to Join the Enterprise: The IT Department

No Longer Just a Cost Center, IT Must Think Long-Term and Leave a New Legacy of ROI
Tim Flower

For decades IT departments have been regarded as "cost centers" — departments and entire divisions made up of necessary expenses which don't produce any measurable profit but instead help companies avoid losses by ensuring uptime, addressing end-user concerns and implementing C-suite approved technologies. As noted by the Harvard Business Review (HBR), however, this attitude is changing: Companies now recognize the potential of IT departments to drive total ROI and boost the bottom line.

To live up to this new role, however, IT must lose the short-term mindset, which, to be fair, has often been necessitated by one-off and sudden-impact issues. IT managers must adopt a long-term strategy in order to create new revenue, improve profitability, future-proof the corporate technology landscape and leave an ROI legacy.

Changing Conversation

According to a recent Forrester report, companies are coming around to a new way of thinking about IT, especially as applied to end-user experience management. Businesses now recognize the need to obtain ground-floor data about how end-users interact with IT systems "in the wild" instead of relying on pre-designed stress tests or waiting for front-line staff to submit IT tickets. The former method puts tech pros in a reactive rather than proactive position and encourages end-users to seek out their own answers, bypassing IT.

The Forrester data tells the tale: While 28 percent of companies put improved end-user productivity among their top-five goals, cutting the cost of end-user support was similarly prioritized. Leading their priorities was cutting the total cost of end-user operations using active monitoring tools. While not a revenue generator in isolation, this priority speaks to the emerging long view of IT departments: If real-time monitoring tools can reduce the costs of end-user operations by quickly addressing issues and determining root causes, this money can be re-invested into more "profitable" areas of IT such as deep-data analytics or social media tools.

Getting SaaSy

Another key driver of the emerging long-term view is the huge Software-as-a-Service market. As noted by WhaTech, the SaaS market is headed for a $170 billion-dollar value by 2025 as companies leverage the power of off-premise software. But it's not the only game in town — according to Forrester, companies must now bridge cloud-native, SaaS and packaged applications, all of which run on different platforms and may not play nicely together. The result? Thirty-six percent of companies surveyed by Forrester have adopted multiple clouds to ensure their SaaS stable can coexist with cloud-native offerings and in-house applications.

While this might seem short-sighted on the surface, it's a testament to the necessary future of IT: As cloud becomes ubiquitous, it only makes sense for companies to adopt the ideal combination of on-site, public and private clouds to cover all the bases. In effect, this doesn't limit IT potential but rather expands it, giving departments the room and resources they need to develop profitable initiatives rather than remaining locked in by limited network compatibility and outdated views of IT as a cost-center.

The role of IT is making a transition from a cost center that is simply chasing problems, to a profit center that is thinking long-term to implement strategic initiatives that leave a legacy of ROI. In doing so, IT needs to implement innovative tools and technologies, and work in collaboration enterprise-wide to better understand the needs and challenges of end-users to ensure a better business outcome.

Hot Topics

The Latest

Most organizations invest heavily in security tools, policies, and controls. Yet despite these efforts, one reality persists: employees often find ways around them. This isn't always malicious. In many cases, it’s a response to friction, urgency, or misalignment between how work actually happens and how systems are designed to protect it. When employees bypass security, it creates blind spots. Sensitive data may move through unmonitored channels, access controls may be weakened, and risks that security teams intended to mitigate reappear in new forms ...

Enterprise AI projects are often justified with a familiar metric: hours saved. A team automates a manual process, employees spend fewer hours reviewing documents or entering data, and the productivity gain becomes the headline. Time savings matter, but they capture only part of the financial impact AI can have inside an organization ... A more useful way to evaluate enterprise AI is to examine the financial decisions and risks surrounding the workflows it supports ...

We run an internal AI assistant that answers engineering questions in Slack ... Each question kicks off what we call a turn ... We could already audit a single turn after the fact. Every reply carries a short lookup token in its footer, and a slash command pulls up the full receipt for that turn. What we could not do was answer questions about the whole fleet. How long do turns take? What do they cost? Which tools does the agent reach for? Where does the time go inside a single answer? Those are APM questions. So we treated the agent like any other service and instrumented it with OpenTelemetry, end to end. This post covers what we built, the design choices that turned out to matter, and the things that surprised us ...

Applications have long used bounded, deterministic logic to control what happens within their own functions. Process orchestration coordinates activity across people, applications, decisions, and automation tools. Workload orchestration coordinates executable work and dependencies across applications, platforms, and infrastructure. As agentic capabilities enter applications and domain systems, more planning and decision-making will also occur inside those environments. These forms of automation will coexist. Sometimes they will overlap, and they will increasingly need to exchange triggers, state, and results. But they are not becoming interchangeable ...

For many organizations, the AI agenda has landed squarely on the CIO's desk. At first glance, that makes perfect sense. AI depends on data, infrastructure, security, integration, governance and scalable technology platforms — all areas where the CIO plays a central role. But there is a problem with treating AI primarily as an IT initiative: AI is not simply a technology deployment. It’s also a business transformation ...

In MEAN TIME TO INSIGHT Episode 28, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and special guest Sanjay Gidwani, Founder & CEO of Kosmos AI Labs, discuss root cause analysis ... 

A gap is growing between how quickly organizations are putting AI to work and how much autonomy they are prepared to give it, according to The 2026 State of Observability Report from Grafana Labs ...

AI agents and agentic browsers now make up a growing share of the traffic reaching websites and applications. They search, compare, sign up, and increasingly complete purchases on behalf of the people who delegate those tasks. Digital experience monitoring (DEM) was built on the assumption that every session is performed by a person. That assumption no longer holds, and the measurements built on it are shifting without notice ...

Who is watching the watcher? This may not be the first question that comes up when discussing AI observability but sooner or later you start to wonder. Part 12 covers the dilemma of AI monitoring AI ...

Two AI agents got caught in a loop with each other over a weekend and racked up $47,000 in charges, according to John D'Emic, CTO of Revenium. No alert fired because nothing "broke." Stories like this are why cost has become one of the most pressing questions in AI observability. Traditional monitoring was built to catch failures, not wasted spend, and AI systems can burn through budget while every dashboard stays green. Part 11 explores how AI observability relates to AI cost management, and whether they are one discipline or two ...

Meet the Newest Profit Center to Join the Enterprise: The IT Department

No Longer Just a Cost Center, IT Must Think Long-Term and Leave a New Legacy of ROI
Tim Flower

For decades IT departments have been regarded as "cost centers" — departments and entire divisions made up of necessary expenses which don't produce any measurable profit but instead help companies avoid losses by ensuring uptime, addressing end-user concerns and implementing C-suite approved technologies. As noted by the Harvard Business Review (HBR), however, this attitude is changing: Companies now recognize the potential of IT departments to drive total ROI and boost the bottom line.

To live up to this new role, however, IT must lose the short-term mindset, which, to be fair, has often been necessitated by one-off and sudden-impact issues. IT managers must adopt a long-term strategy in order to create new revenue, improve profitability, future-proof the corporate technology landscape and leave an ROI legacy.

Changing Conversation

According to a recent Forrester report, companies are coming around to a new way of thinking about IT, especially as applied to end-user experience management. Businesses now recognize the need to obtain ground-floor data about how end-users interact with IT systems "in the wild" instead of relying on pre-designed stress tests or waiting for front-line staff to submit IT tickets. The former method puts tech pros in a reactive rather than proactive position and encourages end-users to seek out their own answers, bypassing IT.

The Forrester data tells the tale: While 28 percent of companies put improved end-user productivity among their top-five goals, cutting the cost of end-user support was similarly prioritized. Leading their priorities was cutting the total cost of end-user operations using active monitoring tools. While not a revenue generator in isolation, this priority speaks to the emerging long view of IT departments: If real-time monitoring tools can reduce the costs of end-user operations by quickly addressing issues and determining root causes, this money can be re-invested into more "profitable" areas of IT such as deep-data analytics or social media tools.

Getting SaaSy

Another key driver of the emerging long-term view is the huge Software-as-a-Service market. As noted by WhaTech, the SaaS market is headed for a $170 billion-dollar value by 2025 as companies leverage the power of off-premise software. But it's not the only game in town — according to Forrester, companies must now bridge cloud-native, SaaS and packaged applications, all of which run on different platforms and may not play nicely together. The result? Thirty-six percent of companies surveyed by Forrester have adopted multiple clouds to ensure their SaaS stable can coexist with cloud-native offerings and in-house applications.

While this might seem short-sighted on the surface, it's a testament to the necessary future of IT: As cloud becomes ubiquitous, it only makes sense for companies to adopt the ideal combination of on-site, public and private clouds to cover all the bases. In effect, this doesn't limit IT potential but rather expands it, giving departments the room and resources they need to develop profitable initiatives rather than remaining locked in by limited network compatibility and outdated views of IT as a cost-center.

The role of IT is making a transition from a cost center that is simply chasing problems, to a profit center that is thinking long-term to implement strategic initiatives that leave a legacy of ROI. In doing so, IT needs to implement innovative tools and technologies, and work in collaboration enterprise-wide to better understand the needs and challenges of end-users to ensure a better business outcome.

Hot Topics

The Latest

Most organizations invest heavily in security tools, policies, and controls. Yet despite these efforts, one reality persists: employees often find ways around them. This isn't always malicious. In many cases, it’s a response to friction, urgency, or misalignment between how work actually happens and how systems are designed to protect it. When employees bypass security, it creates blind spots. Sensitive data may move through unmonitored channels, access controls may be weakened, and risks that security teams intended to mitigate reappear in new forms ...

Enterprise AI projects are often justified with a familiar metric: hours saved. A team automates a manual process, employees spend fewer hours reviewing documents or entering data, and the productivity gain becomes the headline. Time savings matter, but they capture only part of the financial impact AI can have inside an organization ... A more useful way to evaluate enterprise AI is to examine the financial decisions and risks surrounding the workflows it supports ...

We run an internal AI assistant that answers engineering questions in Slack ... Each question kicks off what we call a turn ... We could already audit a single turn after the fact. Every reply carries a short lookup token in its footer, and a slash command pulls up the full receipt for that turn. What we could not do was answer questions about the whole fleet. How long do turns take? What do they cost? Which tools does the agent reach for? Where does the time go inside a single answer? Those are APM questions. So we treated the agent like any other service and instrumented it with OpenTelemetry, end to end. This post covers what we built, the design choices that turned out to matter, and the things that surprised us ...

Applications have long used bounded, deterministic logic to control what happens within their own functions. Process orchestration coordinates activity across people, applications, decisions, and automation tools. Workload orchestration coordinates executable work and dependencies across applications, platforms, and infrastructure. As agentic capabilities enter applications and domain systems, more planning and decision-making will also occur inside those environments. These forms of automation will coexist. Sometimes they will overlap, and they will increasingly need to exchange triggers, state, and results. But they are not becoming interchangeable ...

For many organizations, the AI agenda has landed squarely on the CIO's desk. At first glance, that makes perfect sense. AI depends on data, infrastructure, security, integration, governance and scalable technology platforms — all areas where the CIO plays a central role. But there is a problem with treating AI primarily as an IT initiative: AI is not simply a technology deployment. It’s also a business transformation ...

In MEAN TIME TO INSIGHT Episode 28, Shamus McGillicuddy, EMA VP of Research, Network Infrastructure and Operations, and special guest Sanjay Gidwani, Founder & CEO of Kosmos AI Labs, discuss root cause analysis ... 

A gap is growing between how quickly organizations are putting AI to work and how much autonomy they are prepared to give it, according to The 2026 State of Observability Report from Grafana Labs ...

AI agents and agentic browsers now make up a growing share of the traffic reaching websites and applications. They search, compare, sign up, and increasingly complete purchases on behalf of the people who delegate those tasks. Digital experience monitoring (DEM) was built on the assumption that every session is performed by a person. That assumption no longer holds, and the measurements built on it are shifting without notice ...

Who is watching the watcher? This may not be the first question that comes up when discussing AI observability but sooner or later you start to wonder. Part 12 covers the dilemma of AI monitoring AI ...

Two AI agents got caught in a loop with each other over a weekend and racked up $47,000 in charges, according to John D'Emic, CTO of Revenium. No alert fired because nothing "broke." Stories like this are why cost has become one of the most pressing questions in AI observability. Traditional monitoring was built to catch failures, not wasted spend, and AI systems can burn through budget while every dashboard stays green. Part 11 explores how AI observability relates to AI cost management, and whether they are one discipline or two ...