A New CIO’s First 90 Days: Before You Build a Technology Strategy, Understand What You’re Spending

A new technology leader inherits more than an IT budget. They inherit years of technology decisions, competing business priorities, hidden costs, and risks that may not be visible in the numbers. The first 90 days are an opportunity to understand what those investments are actually doing for the business.

You’ve stepped into a technology leadership role with expectations to improve performance, manage costs, reduce risk, and help the organization move forward.

Leadership wants a plan.

The CEO wants to know whether technology is supporting business growth. The CFO wants confidence that spending is justified. Business leaders want systems and resources that help them achieve their goals.

And everyone wants to know what you’re going to change.

The temptation is to act quickly: identify savings, launch new initiatives, reorganize teams, or establish a technology roadmap.

But there’s a more important question to answer first.

How much of your organization’s technology investment is actually helping the business achieve its goals?

The IT budget alone probably won’t tell you.

Technology spending may be distributed across departments, tied to long-standing vendor agreements, or committed to systems whose business value hasn’t been evaluated recently.

Before you can confidently decide what to fund, improve, or eliminate, you need a clearer picture of what the organization is spending, why it’s spending it, and what it’s getting in return.

That’s where the first 90 days should begin.

An IT budget tells you where certain expenses are recorded.

It doesn’t necessarily tell you the total cost of technology across the organization or how effectively that investment supports the business.

Departments may purchase software independently. Teams may subscribe to AI tools using corporate cards. Business units may maintain specialized applications that don’t appear in central technology reporting.

Meanwhile, legacy systems, support contracts, infrastructure, and external development resources can consume substantial funding without a clear connection to current business priorities.

Research from Zylo’s 2026 SaaS Management Index indicates that business units control a significant share of SaaS spending, demonstrating why technology expenses can extend well beyond the traditional IT budget.

That doesn’t mean decentralized technology purchasing is inherently wrong.

Business units often adopt tools to solve legitimate problems and move faster.

The challenge arises when leadership lacks a complete view of those investments.

Without that visibility, it’s difficult to answer fundamental questions:

• Are we paying for multiple tools that accomplish the same thing?
• Which technology investments directly support revenue, efficiency, or customer experience?
• Where are we spending money simply to maintain outdated systems?
• What risks exist in technology that isn’t centrally managed?
• Which investments deserve more funding, and which should be reconsidered?

These are business questions, not simply accounting questions.

A complete view of technology spending is the starting point for making better decisions about business value.

When leaders don’t have a complete understanding of their technology environment, the consequences extend beyond unnecessary expenses.

Three areas are particularly important.

1. Costs increase without a clear connection to value

Software subscriptions renew. Cloud usage expands. Vendors introduce new pricing models. Departments add applications to address immediate needs.

Individually, these decisions may seem reasonable.

Collectively, they can create an expensive technology environment that nobody has evaluated as a whole.

The problem isn’t necessarily that the organization is spending too much.

It’s that leadership may not know whether the spending is producing enough value.

A technology investment that supports a critical business process may justify its cost. Another that duplicates existing capabilities may not.

Without understanding the difference, cost-cutting decisions become guesswork.

2. Growth opportunities compete with the cost of maintaining the past

Every organization needs to maintain the systems that keep operations running.

But when a growing share of the technology budget is committed to maintenance, support, and workarounds, fewer resources may be available for initiatives that improve the business.

That can limit the organization’s ability to modernize operations, improve customer experiences, introduce new capabilities, or respond to market opportunities.

The question isn’t whether existing systems should be maintained.

It’s whether the current balance of spending supports where the business needs to go.

3. Unmanaged technology creates business risk

Technology that operates outside established oversight can introduce security, compliance, financial, and operational risks.

The organization may depend on systems with limited support, outdated software, unclear ownership, or inadequate data controls.

These risks aren’t always visible in a budget review.

They become more significant when the technology supports critical business operations.

For a new technology leader, understanding these exposures is essential before committing to a strategy that assumes the existing environment is stable.

The cost of limited visibility isn’t just wasted spending. It’s the risk of making important business decisions with incomplete information.

New technology leaders are often expected to demonstrate progress quickly.

That can create pressure to make visible changes before the organization has a clear understanding of what needs to change.

But activity isn’t the same as progress.

Consider how a different set of questions can lead to better decisions.

What leadership sees	Common response	Better strategic question
Technology spending is increasing	Reduce the IT budget	Which investments are creating business value, and which aren’t?
Legacy systems are expensive	Replace outdated technology	What is the business cost and risk of keeping or replacing those systems?
Departments use different software	Consolidate applications	Where does duplication create unnecessary cost, and where do different needs justify different tools?
Business leaders want new capabilities	Launch additional projects	Which initiatives will have the greatest impact on business priorities?
AI spending is expanding	Establish an AI budget	Which AI investments have a credible business case and appropriate governance?
Technology projects aren’t delivering expected results	Change vendors or add resources	Are priorities, accountability, and execution aligned with the intended outcome?

These questions move technology leadership beyond managing systems and budgets.

They connect technology decisions to growth, cost, and risk.

And they help establish a more useful conversation between technology leadership and the rest of the business.

The first 30 days should focus on establishing visibility, building relationships, and understanding the organization’s priorities.

The objective isn’t to identify everything that should be cut.

It’s to create an accurate picture of the technology environment and the business expectations it needs to support.

Establish a complete view of technology spending

Work with finance, procurement, and department leaders to identify technology expenses across the organization.

Look beyond the central IT budget.

Include software subscriptions, cloud infrastructure, external technology partners, development resources, maintenance agreements, and technology purchases made directly by business units.

Review upcoming contract renewals and commitments that could limit future flexibility.

The goal is to understand the full financial picture before making significant investment decisions.

Understand what the business is trying to accomplish

Meet with leaders responsible for the organization’s most important priorities.

Ask what outcomes they need technology to support.

Where are systems slowing growth? What processes create unnecessary costs? Which risks concern leadership? What opportunities are being delayed because the organization lacks the right capabilities?

These conversations provide context that financial reports cannot.

A system that appears expensive may support a critical business function. A relatively inexpensive application may create operational problems that cost far more than its subscription.

Understanding those relationships is essential.

Identify immediate risks and constraints

Look for critical systems with unclear ownership, unsupported technology, significant security concerns, and upcoming contractual commitments.

Also identify major initiatives already underway.

Before making changes, understand what the organization has promised to deliver and what could put those commitments at risk.

By the end of the first 30 days, you should have a clearer view of technology spending, business priorities, and the most important areas requiring attention.

Once you’ve established visibility, the next step is evaluating how technology investment supports the business.

This is where the conversation shifts from what the organization spends to what it receives in return.

Separate operational spending from investments in progress

A useful starting point is the run, grow, and transform model.

Category	What it supports	What leadership needs to understand
Run	Maintaining existing systems, infrastructure, and operations	What does it cost to keep the business operating reliably?
Grow	Improving current capabilities, capacity, and performance	Which investments help the organization operate more effectively or support growth?
Transform	Creating new capabilities, products, or business models	Which investments could materially change future business performance?

This classification helps reveal how resources are allocated.

But it shouldn’t become a simplistic exercise in reducing operational spending.

Some maintenance investments are essential to reliability, compliance, and customer trust.

The objective is to determine whether the balance of spending supports the organization’s current and future priorities.

Identify spending that may not be creating sufficient value

Look for opportunities to improve the return on existing investments.

These may include unused software licenses, overlapping applications, underutilized infrastructure, inefficient vendor agreements, or systems that require disproportionate maintenance.

Evaluate each opportunity in context.

Eliminating a tool may reduce expenses, but it could also disrupt an important business process.

The right question isn’t simply how much can be saved.

It’s whether the organization can reduce cost without creating greater operational risk or losing important capabilities.

Evaluate technology risk alongside cost

Financial efficiency is only part of the picture.

Review whether critical systems have appropriate support, whether technology dependencies are understood, and whether security and governance practices reflect the organization’s risk exposure.

This is particularly important as AI tools and other technology capabilities become more accessible across departments.

A technology investment may appear inexpensive while introducing significant risks that aren’t reflected in its purchase price.

Identify where technology can create greater business value

Not every improvement requires a new system or major investment.

Sometimes better integration, clearer ownership, improved processes, or more effective use of existing technology can create meaningful progress.

Other opportunities may require modernization, specialized expertise, or a different technology approach.

The goal is to identify the decisions most likely to improve business outcomes.

By day 60, leadership should begin to see not just where technology money goes, but where it is helping, where it isn’t, and what deserves closer attention.

AI deserves specific attention during a technology spending review because adoption and purchasing can happen across the organization.

Employees may use AI features included in existing software, subscribe to standalone tools, or experiment with applications outside established procurement processes.

These investments can create value.

They can also introduce unexpected costs, duplicate capabilities, and new questions about data protection and accountability.

A new technology leader should work with business stakeholders to understand where AI is being used, what problems it is intended to solve, and whether results are being measured.

The objective shouldn’t be to centralize every decision or discourage useful experimentation.

It should be to establish appropriate visibility, governance, and financial accountability.

For additional perspective, see How Are You Ensuring Your AI Investments Produce Measurable Results?.

By the final 30 days, the objective is to translate your findings into a clear set of priorities that leadership can evaluate and support.

A useful technology strategy doesn’t begin with a list of projects.

It begins with an understanding of what the business needs to achieve and the technology decisions required to support those goals.

Present a clear view of the current environment

Leadership should understand:

1. Total technology investment: What the organization spends across departments, including costs outside the traditional IT budget.
2. Business alignment: How existing technology supports operational needs, growth priorities, and future opportunities.
3. Cost improvement opportunities: Where spending can potentially be reduced or redirected without undermining important capabilities.
4. Risk exposure: Which systems, dependencies, or practices create significant business risk.
5. Investment priorities: Which initiatives deserve attention based on expected business impact, cost, and urgency.

Keep the presentation focused on what leadership needs to decide.

The purpose isn’t to demonstrate how much technology you’ve reviewed.

It’s to establish a shared understanding of where the organization stands and what should happen next.

Prioritize decisions, not just projects

A long list of technology improvements can create the appearance of progress without establishing clear priorities.

Instead, identify the decisions that will have the greatest impact on business performance.

That may include addressing a critical risk, improving a high-cost process, changing a sourcing approach, or redirecting investment toward a more valuable initiative.

For each priority, establish the business rationale, expected outcome, accountability, and next step.

Build alignment before committing to a roadmap

Technology strategy requires support from the business leaders whose operations and priorities it affects.

Review the proposed direction with finance, operations, and other stakeholders responsible for the outcomes.

Confirm that the priorities reflect business needs and that the organization understands the tradeoffs.

A roadmap built without that alignment can quickly become another collection of technology projects competing for resources.

By day 90, the goal isn’t to have every answer. It’s to give leadership a credible basis for deciding what to fund, what to change, and what to address first.

The pressure to demonstrate results can lead to decisions that create more problems than they solve.

Several common mistakes are worth avoiding.

Cutting costs before understanding business dependencies. A quick reduction in spending can create operational disruption when the value of a system or service hasn’t been fully evaluated.

Assuming the inherited IT budget represents total technology spending. Important expenses and risks may sit in other departments.

Treating every legacy system as a problem to replace. Modernization should be evaluated against business value, cost, and risk rather than age alone.

Launching new initiatives before establishing priorities. Adding projects without understanding existing commitments can stretch resources and delay important work.

Building a technology strategy without business alignment. A technically sound roadmap may still fail if it doesn’t address the outcomes business leaders are accountable for.

The common thread is making decisions before establishing sufficient clarity.

Moving quickly matters.

Moving in the right direction matters more.

STG Consulting is a business technology consulting firm that helps leaders understand how technology decisions affect growth, cost, and risk.

For a new CIO or technology leader, one of the greatest challenges is developing an objective understanding of the environment they’ve inherited while also meeting expectations for progress.

That requires more than reviewing the IT budget.

It requires connecting technology investments, business priorities, operational constraints, and risk into a picture leadership can use to make decisions.

This is the perspective STG brings through its strategic technology consulting approach.

The STG Strategic Technology Framework® helps organizations examine technology in the context of business objectives and establish greater clarity about where attention and investment are needed.

The STG Business Technology Assessment provides a starting point for evaluating how technology supports the organization and where opportunities or risks may exist.

Rather than beginning with a predetermined technology solution, the focus is on understanding the business need and identifying an appropriate path forward.

That can help technology and business leaders build alignment around priorities, make more informed investment decisions, and establish a clearer direction for execution.

Because a successful technology strategy isn’t measured by how many projects it includes. It’s measured by how effectively technology supports the business.

[ADD VERIFIED STG EXAMPLE: A strategic technology assessment or leadership advisory engagement in which STG helped clarify technology spending, identify priorities, or establish an actionable roadmap.]

A new technology leader inherits decisions made long before they arrived.

Some investments will be valuable. Others may no longer support the organization’s priorities. And some of the most significant opportunities or risks may not be visible in the inherited budget.

The first 90 days are an opportunity to understand those realities before committing to a new direction.

Start by establishing visibility into technology spending. Connect those investments to business priorities. Identify where cost, risk, and opportunity deserve attention.

Then use that understanding to create alignment around what happens next.

You don’t need to solve every technology problem in 90 days.

You need to establish a clear, credible direction that helps the business move forward.

Take the Business Technology Assessment.

Start with a clearer view of how technology supports your business, where opportunities for improvement may exist, and which decisions deserve attention.

---