K7 Insights

Virtual CIO Pricing: How Much to Charge for vCIO

By Kyle Christensen · June 23, 2026

Part of Grow Your MSP

How much to charge for vCIO services comes down to one formula: take the fully burdened hourly cost of whoever sits in the seat and multiply by 2.5 to 3, the standard consulting multiple. Then budget the hours each client gets, about 4 per 25 users a month, and package those hours as a priced line: a carve-out inside your agreement or a minimum-hours retainer. Run the numbers and a mid-size client usually lands at $1,000 a month or more. The math is the easy part. The fight is deciding to charge at all, so that’s where we’ll start. If you’re still defining the offering itself, read what a vCIO is first; this piece is the pricing math underneath it, and one lever in the bigger job of growing your MSP.

What does a free vCIO actually cost you?

It costs you the seat itself. A vCIO you give away is a vCIO you’re funding out of your own margin, and when an owner tells me vCIO is included in their stack, I fix the sentence for them: you’re paying your client to be their vCIO.

Run the math on a $2,000-a-month client. At a 65 percent gross margin target, you have $700 a month to deliver everything: help desk, patching, licensing labor, account management, and whatever strategy hours you promised in the sales deck. Now put a tier-3 engineer on an escalation at a loaded $100 an hour. A handful of those touches and the month’s delivery budget is gone. Guess which hours disappear first. The tickets always get done, because tickets scream. The strategy hours have no price tag protecting them, so they’re the slack the budget eats, and it eats them every month.

Free breaks the offering twice more. On the client side, a strategy line with no number on it carries no weight in the client’s head. The advice gets received like small talk, because if it were worth something, it would cost something. On the business side, a seat that produces no revenue can’t fund a second seat. There’s no economy of scale in a free service. You’ll never hire the next vCIO off the back of hours nobody paid for, and the person in the seat ends up dragged toward a quota to justify their cost, which is exactly the posture a client advisor can’t hold.

How do you calculate a vCIO consulting rate?

Salary, plus burden, divided by hours, times 2.5 to 3. That’s the whole formula.

Start with what the person in the seat costs you. Take their salary, add the burden (payroll taxes, benefits, the tool stack they carry), and divide by their annual working hours. That’s your loaded hourly cost. Multiply it by 2.5 at minimum. The multiple covers everything the hourly cost doesn’t: the non-billable half of a consultant’s week, the cost of selling the engagement, and the profit that makes the seat worth staffing. Price at 3 and nobody serious will blink.

I ran this live with one owner I coach. His vCIO penciled out at $78 an hour fully burdened. Times 2.5, the bare minimum multiple for a consultant, and the floor rate is $195 an hour. Round it to $200 and stop apologizing. For context, the fractional CIOs and consulting firms I’ve watched clients bring in bill $400 to $600 an hour for the same class of work, and the good ones stay booked most of the year at it. Your $200 is conservative. I walked this whole model through in a Lifecycle Insights webinar on vCIO KPIs if you’d rather hear it out loud.

The formula matters because it points the right direction. You build the price up from what the seat costs, then defend it. The alternative, working backwards from a number that feels sellable, is how strategy work ends up billed like help desk.

How many vCIO hours should you budget per client?

Plan on about 4 vCIO hours per 25 users per month for a client that actually uses the seat, then tune it by complexity. A compliance-heavy 40-user firm consumes more advisory time than a 60-user shop that wants email to work and nothing else, so tier the budgets instead of averaging them.

The per-client question is blunt. Does this client’s fee carry a budget of vCIO hours every single month? Two hours? Four? Eight? If nobody at your company can answer that, the hours are coming out of margin, and we already covered which hours the margin eats first.

The same ratio makes the fee sanity-check itself. At $200 an hour and 4 hours a month, a 25-user client is an $800 line, which is why working vCIO fees so often cluster around $1,000 a month once clients reach the 30-to-50-user range. If your fee and your hours budget don’t reconcile like that, one of them is made up.

The hours math also tells you when to hire. Treat the vCIO like the billable consultant they are and watch realized utilization. When the seat runs at roughly 90 percent billable, hire the next one. Run the arithmetic and one full-time vCIO tops out somewhere near a thousand users under management. Your exact ceiling will move with client complexity, but the trigger doesn’t.

Should vCIO be bundled in your agreement or billed separately?

Either works. Plenty of MSPs bundle the seat and never show the client a line item, and that’s a legitimate choice too. The rule is simpler than disclosure: the number has to exist in your math. A seat with no number anywhere in the business is the free model wearing a bundle costume. Two packaging models hold up in practice, and both put a number on the hours.

Model one is the intentional carve-out. The vCIO line lives inside your managed-services agreement, but it’s an add-on or a math equation in your price per unit. A vague included benefit doesn’t qualify. If your contract world is per-seat, run the equation per seat: start at a tenth of an advisory hour per user per month, which is the floor for a simple client, and tune it up toward the 4-per-25 planning ratio (about a sixth of an hour per user) as complexity grows. On a 100-user client the floor is a 10-hour monthly budget. Ten hours at a $600 senior rate is $6,000 a month; ten at your $200 rate is $2,000. The client experiences a subscription. You run an hours budget. Both are true at once, and that’s the point. Whether the client ever sees the line is a packaging choice. Whether you see it isn’t.

Model two is the minimum-hours retainer, sold next to the agreement instead of inside it. The client commits to a block of hours a month at your consulting rate, use it or lose it, and the hours expire quickly. The expiry isn’t you being difficult. Hours that bank forever pile up into a liability that wrecks your capacity planning, and a retainer the client can stockpile is a retainer they’ll never treat as a standing cadence.

I watched the carve-out version land at a $50M MSP I coach. vCIO sat in their stack as an included benefit, which meant the support budget and the strategy budget were the same budget, and support ate it, the same cannibalization math from earlier running at scale. The fix was boring: move vCIO to a priced carve-out with its own per-unit math, so nothing upstream could consume it. Their offering, their win. My job was holding up the mirror and the spreadsheet.

If your agreement has strategy hours with no line of their own, that’s a pricing problem with a known fix, and it’s the kind of thing I work through with owners on a call.

Is your vCIO a cost of goods sold or an overhead expense?

Pick one on purpose, because the two models create different disciplines and mixing them creates none.

My default: the vCIO is a billable cost-of-goods resource. Their time lands in time entries against clients, the hours budgets are tiered by client complexity, and the seat gets judged on utilization like any consultant. That framing is what makes everything above work. The rate formula, the hours budgets, the hire-at-90-percent trigger all assume the seat is COGS.

If you genuinely can’t stomach that and insist the vCIO is an expense, fine. Then budget the seat like an expense: a fixed percentage of revenue, chosen deliberately and reviewed like any other line. What you can’t do is mix the models, billable when it’s convenient and overhead when it’s not. Mixed, the seat has no yardstick. Nobody can say whether it pays for itself, utilization means nothing measured against an expense budget, and the role floats around your accountability chart touching sales, account management, and margin without owning any of them. Pick a lane. The lane decides how the seat gets measured, and measurement is its own conversation.

Common vCIO pricing mistakes

The pattern behind all of these is the same: a fee with no hours math underneath it.

• Backwards per-user math. Charging $190 per user per month because the total looked right against a competitor, with no hours budget behind it. When nobody can say how many advisory hours the fee buys, delivery decides, and delivery always decides zero. Hours first, rate second, per-user division last.
• Charging your cost. Billing the seat at its $80-to-$100 loaded cost because the multiple feels greedy. That prices a consultant like an employee and leaves nothing to fund non-billable time, selling, or profit. 2.5x is the floor.
• Hours that never expire. Rollover with no expiry turns sold hours into a growing liability and turns your capacity plan into fiction. Short expiry keeps the engagement honest on both sides.
• One price for every client. A flat vCIO fee across a regulated 40-user firm and a 15-person office ignores that complexity, not headcount, drives the hours. Tier the budgets and the fee tiers itself.

The one number to run this week

The whole article compresses to this: charge for the seat, at 2.5 to 3 times its burdened hourly cost, against a per-client hours budget you can name. Run it tonight. Pick your biggest client, work out what the person doing their strategy work costs per hour, multiply by 2.5, then count the advisory hours that client consumed last quarter. Multiply those two numbers and look at what you’ve been giving away. That figure is your business case, and nobody has to approve it but you.

The fee is half the seat. The other half is proving the seat earns it, so read next: the KPIs that show your vCIO is actually working. Both pieces sit inside the bigger system for growing your MSP.