An account manager owns the client relationship: regular meetings, hardware refresh timing, renewals, and new requirements such as cyber insurance. A vCIO works on the client's business plan, running discovery and turning it into a technology roadmap and a budget. Josh Peterson of Bering McKinley gave a one-question test in November 2026: if the person in the role cannot name the client's three most important business initiatives, you have an account manager, not a vCIO. That is fine, as long as you call it that. The distinction pays, too. MSPs that work their accounts on purpose move project and hourly revenue from about 12 to 15 percent of managed services revenue toward 30 percent. This continues our look at what an MSP account manager actually does, and it connects to treating your ideal client profile as a revenue strategy and to the three project indicators of MSP profitability.
Josh and Gary Boyle used this roundtable to get tactical about both roles: what each one does in the room, how to tell which one you have, and where to start with the clients already on your list. The leadership question underneath is whether you know your clients' businesses well enough to earn the title you are using.
The difference is what the conversation is about: an account manager talks with the client about the relationship and the technology, and a vCIO talks with the client about the business. Josh Peterson put the account manager's work plainly. Equipment will eventually break, here is roughly what replacing it will cost, and I will come back and remind you when it is time. There is a new insurance requirement, and here is what it takes to meet it. He called that work super valuable and told owners to do it. The vCIO sits in a different meeting. Gary Boyle described it as the C-level seat at the client's conference table, mapping what the business looks like in a year or longer and deciding what technology has to do to get it there. One role keeps the account healthy. The other helps set the client's direction.
You have a vCIO if the person in the role can name each client's three most important business initiatives. That is Josh Peterson's test, and he applies it without sentiment: if they cannot, you have an account manager, which he called awesome, and you should stop pretending it is something else. He borrowed a comparison from a conversation with a working CFO. A bookkeeping firm would never bring its lead bookkeeper to a client and present a virtual CFO program. The C in the title means a business role that happens to understand technology at a high level, not a lead technician with a new card. Gary Boyle agreed and went further, saying the industry pushed the title onto every MSP without changing how the work was delivered. A real CIO who sat in on most vCIO meetings would object to the name.
A vCIO runs discovery on the client's business, then builds a technology roadmap and a budget from what it finds. Gary Boyle named those three pieces as the definition and said that an MSP that cannot do them is not doing vCIO work. Discovery means asking what the client plans for the next one, three, and five years, whether a business plan exists, and whether you can see it or sit in when it is written. Josh Peterson gave an example from his own company. When he decided to buy HubSpot, nobody helped him think it through. A vCIO would have asked what he was trying to do, shared what they had seen elsewhere, and told him not to buy it unless he could afford a consultant to configure it. He said he would have paid for that advice. Gary expects AI to pull MSPs further into decisions like that one.
No. Every client needs account management, and only clients with a plan worth working on need a vCIO. Josh Peterson was direct about it: if refreshing hardware and meeting compliance standards is most of what you sell, you do not need a vCIO, because that is account management. He first guessed that perhaps 20 percent of clients do real planning, and Gary Boyle pushed back. In Gary's experience, businesses with 20, 30, or 50 employees and up are usually talking about how to run the company, and the longer an MSP stays out of that conversation, the less it understands the client. They settled on client size as the divider. A base of 10 and 15 user offices will rarely support vCIO work, while clients of 20 to 50 users and above probably plan already, and the MSP's job is to get invited in.
Start by grading every client A through D and putting meetings on their calendars. In Josh Peterson's example, an A client gets four planned meetings a year and a D client gets one, with B and C in between, which summed to 214 meetings across the client list. The only job after that is to send the recurring invites. For the first meeting he suggested taking the owner to lunch, admitting you do not know the business as well as you should, and asking three things: what do you sell, how do you sell it, and what does delivery look like. The payoff shows up in what he calls pull-through. Project and hourly revenue runs 12 to 15 percent of managed services revenue when nobody works the accounts, about 20 percent with some attention, and 30 percent at full clip. His homework was to book one business-only conversation this week.
An account manager owns the client relationship: regular meetings, hardware refresh timing, renewals, and new requirements such as cyber insurance. A vCIO works on the client's business plan, running discovery, building a technology roadmap, and setting a budget against it. The account manager keeps the account healthy, and the vCIO helps the client decide where the business is going.
Use the test Josh Peterson of Bering McKinley gives MSP owners. Ask the person in the role to name the three most important business initiatives at each client. If they can, and they are part of how the client plans, you have a vCIO. If they cannot, you have an account manager, which is still valuable.
No. Every client needs account management, but vCIO work only fits clients that plan their business and want technology tied to that plan. If most of what you sell is hardware refresh and compliance, account management covers it. Clients with roughly 20 to 50 users or more are the likelier candidates for vCIO work.
A vCIO learns the client's goals for the next one, three, and five years, then builds a technology roadmap and budget to support them. The role also advises on software, process, automation, and AI decisions, such as whether a CRM purchase fits what the business is trying to do. It is a business role that understands technology.
Match the cadence to the client's grade. In Josh Peterson's example, an A client gets four planned meetings a year, a D client gets one, and B and C clients fall in between. Add the counts across the client list to get an annual meeting total, then book them as recurring calendar invites.
Start with three: what do you sell, how do you sell it, and what does delivery look like. Then ask what winning looks like for the business this year. Josh Peterson suggests asking over lunch with the owner, and admitting up front that you do not know the business as well as you should.
Gary Boyle is a Partner for Strategy & Business Development at Bering McKinley. With a background spanning network engineering, entrepreneurship, and strategic consulting, Gary brings real-world operator experience to helping MSP owners build stronger, more profitable businesses.
Connect with Gary on LinkedIn →
Josh Peterson is the CEO of Bering McKinley and host of The BMK Vision Podcast. Since 2004, Josh has worked with hundreds of MSP owners to build operationally sound, profitable businesses through consulting, peer teams, and direct coaching.
Connect with Josh Peterson on LinkedIn →
Earning a seat at a client's planning table starts with running your own business from a plan. That is the work Bering McKinley does with MSP owners through Vision.