Fractional CIO questions, answered plainly.

Most fractional CIOs work on a monthly retainer that typically starts around $5,000 a month, or bill advisory work by the hour at about $190 an hour on average. The price depends on hours committed, company complexity, and whether the work is strategy only or strategy plus hands-on execution.

Use a project fee when the deliverable is clearly defined, and a retainer when you need ongoing leadership. Hourly works only for occasional advice.

• Project fee: You know the cost up front. Best for a four to six week IT assessment, due diligence, or an MSP selection.
• Retainer: Predictable budget, and you can pick up the phone without watching a meter. The quick question that prevents a bad decision is often where the most value sits, and hourly billing discourages those calls.
• Hourly: Fine for a one-off review or a second opinion.

A common path is an assessment project first, then a retainer if the findings call for one.

A full-time CIO at a midsize company costs roughly $300,000 a year once salary and benefits are included, plus a recruiting fee. A fractional CIO typically starts around $60,000 a year and can start within weeks.

Full-time makes sense when the business needs a technology leader 40 or more hours a week on a permanent basis. Even then, a fractional CIO can define the role, set the budget, and help you hire the right person.

Typically anywhere from 10 hours a month to 20 hours a week per client, depending on the stage of the engagement. Most engagements are heaviest at the start and step down once things are stable.

Most engagements follow a 90-day arc: assess, stabilize, then build. After that, the work steps down to advisory or hands off to a permanent leader.

1. Weeks 1 to 6, assess: Interview leadership and staff, review systems, security, spend, vendors, and tickets. Deliverable: a written assessment with prioritized risks and quick wins.
2. Weeks 6 to 9, stabilize and plan: Close urgent security and reliability gaps, set vendor expectations, and build a 12 to 18 month roadmap tied to the business plan.
3. Weeks 9 to 13, execute: Start roadmap projects, fix team structure, and put monthly reporting in place.
4. After 90 days: Continue as ongoing fractional leadership, step down to advisory, or hire and onboard a full-time leader.

A fractional CIO is a part-time technology executive who owns IT strategy, budget, vendors, security oversight, and the IT team. You get senior leadership without the cost of a full-time hire.

Typical responsibilities:

• Align technology with the business plan and growth goals
• Own the IT budget and explain spend in financial terms
• Manage the MSP and other technology vendors
• Oversee cybersecurity and compliance
• Structure, hire, and develop the IT team
• Lead major projects such as ERP selection, cloud migration, or office moves
• Report to the CEO, owners, or board

An MSP's vCIO works for the company that sells you managed services, so their recommendations come from inside that relationship. A fractional CIO works for you and can objectively evaluate the MSP itself.

This isn't a knock on MSPs; many vCIOs are capable people. But when the question is whether your MSP is the right fit, or whether you're paying the right amount, you need someone with no stake in the answer.

I don't resell hardware, software, or managed services to my Fractional CIO clients, and I don't take referral fees on what I recommend.

A CIO runs the technology that runs your business. A CTO builds the technology you sell. A CISO focuses on security risk and compliance.

Most growing companies that don't sell software need a CIO first.

An interim CIO works full time for a limited period, usually to fill a vacancy until a permanent hire starts. A fractional CIO works part time on an ongoing basis.

• Interim: Full-time, typically 3 to 12 months, bridges a gap in leadership.
• Fractional: Part-time, ongoing, scaled to what the business actually needs.

Some engagements start at near-interim intensity during a turnaround, then step down to fractional once things are stable.

If three or more of these apply, a fractional CIO is likely worth a conversation:

1. IT is run by the CFO, controller, or office manager as a side job.
2. Your MSP is setting your technology roadmap.
3. The same problems keep coming back and tickets pile up.
4. The company has grown fast and systems and processes haven't kept pace.
5. No one can say clearly what you spend on IT or why.
6. A major project such as an ERP rollout is stalled or over budget.
7. Customers, insurers, or auditors are asking security questions you can't answer.
8. Your IT manager is overwhelmed, or you aren't sure they're the right fit for the role.
9. You're preparing for an acquisition, a sale, or new investors.
10. Critical system knowledge lives in one person's head.

A fractional CIO is the wrong fit when what you need is daily hands-on support, product engineering, or a permanent full-time leader.

• You need someone at the keyboard every day. That's an IT administrator or a good MSP.
• Technology is your product. You need a CTO.
• You need 40 or more hours a week of leadership, permanently. Hire full time; a fractional CIO can help you define and fill the role.
• Leadership isn't ready to act on recommendations. Advice that isn't acted on is expensive.
• You're under $10M in revenue with basic IT needs. A well-run MSP is usually enough.

IT departments usually break down under rapid growth, and fixing them means addressing people, systems, and process at the same time. Fixing only one of the three rarely holds.

1. Listen first: Interview leadership and users and review ticket history.
2. Stabilize: Close urgent security gaps, validate backups, and stop recurring outages.
3. Assess the people: Right roles, right people, and where the gaps are.
4. Fix the process: Ticketing, change management, documentation, and vendor accountability.
5. Rationalize systems and spend: Cut duplicate tools and renegotiate contracts.
6. Build the roadmap: Tie every project to a business outcome.
7. Measure and report: Monthly metrics leadership actually understands.
8. Hand off: Leave a team and a process that run without me.

Translate IT into the financial metrics leadership already uses: spend as a percent of revenue, cost per employee, cost of downtime, project payback, and risk reduction. With a background in strategic finance as well as IT, I report technology the way a CFO reads a P&L.

Many companies spend roughly 3.6% to 5% of revenue on IT, but it varies widely by industry. Manufacturers tend to spend less, while financial services and healthcare tend to spend more because of compliance and data security requirements.

Spending well below your peers usually means growing technical debt and security risk. Spending well above them is worth a review for waste. Either way, the percentage matters less than whether the spending produces measurable results.

Score your MSP on responsiveness, recurring problems, proactive advice, security practices, documentation, and contract terms. If you replace them, secure your admin credentials and documentation before giving notice.

Scorecard questions:

1. Are response and resolution times meeting the contract?
2. Do the same problems keep coming back?
3. Do they bring recommendations, or only react?
4. Do they follow strong security practices on their own tools and access?
5. Do you own and hold your passwords and documentation?
6. Is the invoice clear, and does it match what you use?
7. What are the notice period and exit terms?

To replace an MSP safely:

1. Collect all documentation and admin credentials first
2. Review the contract's notice and exit terms
3. Select the new provider using the scorecard above
4. Plan an overlap period for the transition
5. Rotate every credential once the old provider is off