Persona — CIO/IT Leader

The CIO is persona #2 in the Six Personas framework and the technical gatekeeper for any eCommerce initiative. The B2B CIO is a fundamentally different animal from a tech-company CIO — understanding this difference is critical to not losing deals at the technical evaluation stage.

Unknown block type "horizontal-rule", specify a component for it in the `components.types` option

Who They Are

  • Often an ERP lifer — came up through finance, operations, or the warehouse, not software development
  • Became CIO because they learned to keep the ERP running — not because they code
  • Deeply embedded in the operational side of the business
  • Views every new tool through the lens of risk to the existing system
  • Not anti-digital — but has been burned by failed implementations before
“In manufacturing and distribution, the CIO is often an ERP lifer. They didn’t start in tech. They came up through finance… or operations… or the warehouse.”
— C2, Module 2 Lesson 2
Unknown block type "horizontal-rule", specify a component for it in the `components.types` option

What They Care About

  • ERP stability — will this break the system of record?
  • Integration feasibility — can their team actually support this?
  • Risk management — pricing errors, data corruption, customer experience failures
  • Vendor reliability — will the vendor still be there in 3 years?
  • Internal bandwidth — their team is small; they can’t take on a project that requires 24/7 support
Unknown block type "horizontal-rule", specify a component for it in the `components.types` option

What They Fear

  • Another failed implementation (scope creep, ghost project, vendor abandonment)
  • Pricing errors exposed to customers due to bad ERP sync
  • Being blamed when the project goes sideways
  • Losing control of a system they’ve spent years stabilizing
Unknown block type "horizontal-rule", specify a component for it in the `components.types` option

How to Speak Their Language

Do:

  • Lead with integration: “We’re API-first. We’ve done this with Infor, Epicor, SAP.”
  • Emphasize team support: “Your team won’t be left hanging.”
  • Reduce, don’t add: “We reduce complexity, not add to it.”
  • Reference specific ERP integrations by name — generic claims don’t land

Don’t:

  • Use marketing language about “seamless integration” without specifics
  • Minimize the ERP — it’s their world
  • Imply their current setup is wrong or outdated
  • Promise things that require their team to do significant development work

Key framing:

“We integrate cleanly with your ERP. We make your team look good. We reduce complexity — not add to it.”
Unknown block type "horizontal-rule", specify a component for it in the `components.types` option

The CEO–CIO Alignment Problem

The CEO wants acceleration. The CIO wants control. These are not naturally aligned.

Your job as a vendor is to bridge this gap:

  • To the CEO: frame outcomes (less churn, more customers, no added headcount)
  • To the CIO: frame integration and risk reduction (API-first, proven ERP connectors, reduced manual work)
  • To both: “This isn’t disruption. This is evolution — built to fit your business today and scale for tomorrow.”
Unknown block type "horizontal-rule", specify a component for it in the `components.types` option

Technology Connections

  • erp-systems — the ERP is the CIO’s primary concern; must understand ERP landscape
  • technology-integration-challenges — the specific pain points the CIO has lived through
  • b2b-ecommerce-platform — what CIOs need a B2B platform to do (vs. B2C platforms)