Selling to a CIO

A CIO buys risk reduction first and innovation second. Sellers get this backwards. They pitch the shiny new thing to a person whose job depends on nothing breaking.

Sell to what the CIO is afraid of, and you get a meeting. Sell to what you're excited about, and you get silence.

What a CIO owns

The CIO owns the systems the business runs on. Infrastructure, core applications, security in many companies, the IT budget and the teams and vendors that keep all of it running.

They own a growing list of things nobody else wants. Data platforms. Integration after acquisitions. The legacy system that three departments depend on and nobody understands. The AI pilot the CEO read about.

And they own a vendor list. A long one. Every services firm you compete with is already on it or trying to be.

What they're measured on

A CIO is judged on uptime, security, cost and delivery. Did the systems stay up? Did anything get breached? Did IT spend stay inside budget? Did the big programs land on time?

Increasingly, they're judged on business outcomes too. Did the new platform help sales close faster? Did the data project give finance a better forecast? A CIO who can point to a business result has a stronger seat at the table.

So the best pitch to a CIO connects a technical fix to a business number someone else in the C-suite cares about. That makes the CIO look good in the room that matters.

What they ignore

They ignore pitches about technology for its own sake. "We're experts in cloud-native microservices" means nothing to them. Every firm says that.

They ignore vendors who skip them and go to the business. A seller who sells around the CIO to a business unit leader often wins the first deal and loses the account.

And they ignore generic outreach. A CIO at a mid-size company gets more vendor email than almost anyone in the building. If yours could have been sent to any CIO, it'll be deleted.

Signals that matter

A new CIO is the strongest signal of all. In the first 90 days, a new CIO is assessing the team, the stack and every partner. They're forming a plan, and they're open to outside views. After that, the plan is set.

Business pressure in filings matters a lot. When a 10-K mentions legacy systems, a modernization program or IT cost reduction, the CIO is on the hook for it.

Hiring for the problem is a strong tell. A posting for a head of data engineering or an integration architect says the budget is real and the CIO hasn't solved it in-house yet.

Tech stack signals tell you what they run. A job post that names a specific ERP, CRM or cloud platform tells you where the pain might be. The buying signals guide has the full set.

An example opener

Say a mid-size manufacturer hires a new CIO from outside the industry. A month later, it posts for an ERP integration lead and an enterprise architect. Its 10-K mentions a multi-year effort to consolidate plant systems after two acquisitions.

Saw you started as CIO, and the team's now hiring an ERP integration lead. A new CIO usually owes the leadership team a systems plan in the first quarter. My guess is the plant systems from the two acquisitions still don't talk to the core ERP, so finance and operations are reconciling by hand. Is that accurate, or is the bigger issue something else?

It names the event. It ties to the CIO's first 90 days. It guesses at a specific pain that a CIO would own and feel. And it lets them correct it in one line.

Don't stop at the CIO

The CIO is often the technical lead and sometimes the economic buyer. But they're rarely the only voice.

The CFO controls whether the program gets funded. A director of enterprise applications or a VP of IT is often your real champion, the person who lives with the problem every day. Write to each of them, with a different misery hypothesis for each seat.

A CIO who sees that you've talked to their team, and that you understand the problem from the ground up, takes you more seriously. A CIO who hears about you from the CFO first takes you very seriously.

Show up useful

When you get the meeting, don't pitch. Bring a point of view on their specific problem. What you'd look at first, what usually goes wrong and how you'd reduce the risk.

CIOs have seen plenty of partners promise transformation and deliver chaos. The firm that shows up talking about risk, sequencing and a small first step tends to win. Big promises scare them.

The method works on CIOs for a simple reason. It starts with their situation, not your service. Do the research, name the misery and let them tell you where you're wrong.