How to Write for CIO Magazine: 4 Doors In (2026)

“Who better to tell the truth of what’s happening in IT than those living it?”

That line sits at the top of the page Foundry uses to recruit for its Expert Contributor Network, the program that puts outside bylines on CIO, Computerworld, CSO, InfoWorld and Network World. Read it twice, because it tells you who the publication wants and, by omission, who it does not. It wants people living IT. It does not say people selling to IT.

Most of the questions I get about how to write for CIO magazine come from two camps, and it helps to admit that people still say “magazine” when nearly all the action is on cio.com. One is the sitting CIO or VP of engineering who has a story and no idea where to send it. The other is the enterprise software company whose head of marketing wants “a CIO.com placement” by next quarter. Both can get there. They walk through different doors, and the most common failure I see is a vendor trying the door built for practitioners and getting ignored.

So before tactics, a map.

CIO has four doors, and only two are editorial

CIO is owned by Foundry, the media and marketing company that was called IDG Communications until a February 2022 rebrand. Axios reported at the time that Blackstone had bought IDG for $1.3 billion the previous November. In March 2025, IDG announced it had completed the sale of Foundry to the private equity firm Regent. That history explains why one site carries both newsroom journalism and a large marketing business, and why you need to know which side you are talking to.

I call the result the Four Doors Map. Every route onto cio.com falls behind one of four doors, and each door has its own gatekeeper, its own currency and its own label on the finished page.

Door three is editorial in judging and commercial in its events business. Door four is advertising, which is fine as long as nobody on your team mistakes it for the first two. The rest of this post works through the doors in the order most teams should try them.

How does the Expert Contributor Network actually work?

This is the door most people mean when they ask how to write for CIO magazine, and Foundry is specific about it on its own recruiting page. The network is free. Contributors work with an editor who shapes the piece for the audience and the house style. Foundry publishes it on the brand site that fits best and promotes it on social channels, tagging both the writer and the writer’s organization.

The format is spelled out too. Foundry asks for articles of 1,200 to 1,500 words, and it lists core topics that include AI and machine learning, cloud computing, data management, IT leadership, IT strategy, security, software development, the future of work and networking. The page says it wants “a first-person perspective of your lived experience in the trenches as an IT and business decision-maker,” along with the considerations and calculations that go into hard decisions.

The pitch itself is small. According to the page, it doesn’t need to be much more than a working title and a few sentences on the article’s focus. The editor can approve it as is or work with you to shape it. Every contributor signs a Writer Agreement. The page names the network’s editor and gives an email address for joining, so go there for the current contact rather than trusting a list someone scraped in 2023.

Here is where most pitches break.

First, the unit is a decision, not a product. Look at what runs under the network tagline. Krist Davood, described in his bio as a former CIO with more than 35 years in IT, wrote a four-step blueprint for turning technology from a tool into a strategic partner. Dino Velusamy wrote about how vendor influence turns into CIO bias over years. Neither piece is about a product. Both are about judgment.

Second, the disclosure rule applies to you. Foundry’s editorial ethics policy says freelance and other contributors must “clearly disclose within the body of their articles anything that might bias their perspective,” and gives prior employment with a company in the story as an example. If you work for a vendor and you write about the category that vendor sells into, that relationship belongs in the piece. Editors will find it anyway. Put it in yourself.

Third, the AI line is explicit. The same policy says Foundry does “not publish AI-generated articles under the guise of journalism” and treats passing off AI output as your own work as plagiarism. A draft that reads like a model wrote it is a draft an editor stops reading.

A useful test before you send anything: could a CIO at a company that will never buy from you finish the essay and change something on Monday? If yes, you have a contributor piece. If the only useful next step is a demo, you have a sales asset, and it belongs behind door four.

Pitch the reporters, not the masthead

Door one is earned coverage, where you are the source, not the author. It is the most valuable door and the hardest, and any honest answer to how to write for CIO magazine has to admit that the newsroom does not need you. It needs news, data and IT leaders who will talk on the record.

Start with the About Us page on cio.com. It lists the editorial team by role, including news editors, senior writers and the editors for international editions, with contact addresses. Foundry’s own contact page for CSO gives the advice that applies across the group: to submit a story idea, read the site, see who writes what, and contact that person through the link in their byline. That is the whole method. Read twenty recent stories in your area, note whose name is on them, and pitch the one person who has covered your problem three times this year.

Then read the ethics policy, because it sets the rules of engagement. Three points matter most to a PR team. The editorial staff alone decides coverage, and the policy says it gives no preferential treatment to “advertisers, partners, or sources.” Sources and PR reps don’t get to review stories before publication, though sources can check their quotes for accuracy. And sources are assumed to be on the record unless other terms are agreed in advance, which means the casual “just between us” on a briefing call is not between you.

Judging from what runs, three things travel well with CIO reporters.

The first is a named IT leader with a specific story. CIO’s readers are senior technology executives, and the stories that carry are ones where a CIO explains what broke, what it cost, and what changed. If you are a vendor, your best asset is a customer CIO who will talk on the record about the problem, with your product as a supporting detail or not mentioned at all. It is the only version a reporter can use.

The second is original data. A survey of 400 IT leaders with a clean methodology section will get a hearing that a product launch will not. Give the reporter the questionnaire, the sample, the dates and the margin of error. If your numbers can’t survive that, they aren’t ready.

The third is timing. When a cloud provider changes its pricing or a regulation lands, reporters need someone who can explain the budget impact within a day. A short, on-the-record comment sent that morning beats a long pitch sent a week later.

For a vendor, door one works through your customers and your data. Your CTO’s view on AI governance is a contributor essay at best. Your customer’s view, with numbers, is a story.

What vendors get wrong about CIO

I’ll be direct here, because this is where budgets disappear.

The first mistake is treating the contributor network as free advertising. The network’s page describes it as a platform for “IT experts” and “leading IT practitioners.” Vendor executives do get published there; plenty of contributor bios list a company the writer founded or runs. What they publish is practitioner thinking with the commercial interest disclosed and kept out of the argument. When an editor sees three paragraphs of insight and then a turn toward “this is why platforms like ours,” the pitch is done. You will not get a rejection letter. You will get silence.

The second mistake is confusing door two with door four. Foundry runs paid programs, and its contact pages point marketers to the BrandPost program and to sales. There was also a separate CIO Experts Network, announced in 2022, aimed at recruiting B2B experts for Foundry’s custom editorial programs, such as blogging, webcasts and other formats. Those are legitimate channels, but they are not an editor choosing your essay, and the labeling tells readers so. If your board deck says “featured in CIO” and the piece carries sponsor labeling, someone will notice. Report each door by its real name.

The third mistake is entering the CIO 100 with a product. Foundry’s 2026 call for entries said it plainly: technology vendors can apply, “but this is not an award for IT vendors’ products.” The award goes to organizations for IT projects, and the 2026 rules asked that projects be at least in a pilot stage with early results already delivered. A vendor can win for how its own IT team ran a project. A vendor cannot win for what it sells. If your customer’s project used your product, the customer enters, and you help them write a strong submission.

The fourth mistake is asking to see the story first. The ethics policy rules it out, and reporters remember who asked.

None of this means vendors should stay away. It means the vendor’s job is to supply the material that each door accepts: customers and data for door one, disclosed practitioner thinking for door two, customer projects for door three, and budget for door four. Read that way, a vendor has more routes in than a lone CIO does.

Build a 90-day plan around the CIO 100 calendar

The CIO 100 is the spine of CIO’s year, and if you plan around it, the other doors get easier. The 2026 cycle opened for submissions in December 2025 with a January 14, 2026 deadline, and winners were set to be honored at the CIO 100 Symposium and Awards in Frisco, Texas, August 17 to 19, 2026. Foundry also runs a regional CIO 100 Leadership Live series in U.S. cities and separate CIO 100 programs in other regions, including a combined awards and conference for ASEAN and Hong Kong. Check the events page for the current year’s dates, because they move.

Here is how I would sequence a quarter, whether you are an IT leader or a vendor working through customers.

In the first month, read. Pull the last three months of CIO coverage in your area and the full contributor feed. Write down the five reporters and the two or three recurring contributor blogs closest to your topic. Read the ethics policy and the contributor page in full. This takes a few hours and saves you a season of bad pitches.

In the second month, pick one door per person. The CIO or practitioner on your team pitches door two, with a working title and three sentences, built on one decision they made and what it taught them. The communications lead prepares door one material, which means one on-the-record customer and, if you have it, one dataset with a methods note. If an awards cycle is approaching, someone owns the CIO 100 submission and starts collecting project results now, since the judges want evidence of impact, not intent.

In the third month, publish and compound. A contributor piece that runs becomes proof for the next pitch. A reporter who quoted your customer once will take your call again. An award shortlisting becomes a reason for a regional event to put your CIO on a panel. The doors connect, but only when each one is opened with the right key.

If you want a model of how the second door turns into a sustained presence, look at Ritu Jyoti. Her bio on CIO says she was previously the general manager and group vice president of AI and data at IDC, received the James Peacock Memorial Award, IDC’s highest research honor, in 2022, and now runs a stealth AI startup. Her blog, Leading the Agentic Age, runs under the Foundry Expert Contributor Network tagline and its index lists more than 20 articles, covering subjects from AI governance to talent pipelines to the agentic data center. Not one of those headlines is about a product. Every one of them is about a decision a CIO has to make, which is exactly what the recruiting page asked for in its first sentence.