I spent more than 20 years running MSPs, and in that world everyone can call themselves a technology advisor or a vCIO. I know hundreds of MSP owners, and every one of them has some version of it in their proposals, on their website and in their QBRs. We believed it too. With the benefit of hindsight, it was a delusion we were living in, because a lot of what we called advice was just doing what we sold.
Usually, if a client asked us about their line of business software, we'd say we don't know anything about it, but we can open a ticket with the vendor on your behalf. That's not technology advice, that's just providing IT services.
We made the same mistakes
At TrueIT we made most of the same mistakes. Our QBRs had reports with ticket counts and closed tickets, and generally they ended up being about new laptops, servers, new services and new security. There's nothing wrong with that. Except we sold our clients on the idea that we'd advise them on technology, which is technically true, but it's one of those technicalities we all hate. If I go back in time and look at our marketing, how we positioned it and how we sold it, we sold it as if we were going to give them overall technology advice, and that was not true.
And then there were the clients who just didn't have time for it. We ran into that many times, where you couldn't get the client to meet with you to review the QBR. In hindsight, the reason is that the client didn't see value in it. If you're not providing valuable QBRs and valuable technology advice, they won't waste time meeting with you.
A lot of this is hindsight. I have the benefit of that now, and of being on the client side, and it's a really interesting perspective.
What advising actually is
Technology advising is like consulting. You understand the business, where they're going and what they're trying to accomplish, and you help them figure out what they should do, even if you don't do it. In fact, that's the important part. You should be advising them on things you don't do, because you probably don't do everything. Copiers, physical security, access control, cameras, business applications, CRM, ERP, accounting, it depends on what you do, but you should still guide them.
The advisor doesn't make the decision
I was talking about this with one of my old business partners, and he said, "Well, our clients want me to tell them which line of business software to buy, and I don't know how to do that." In this case it was a manufacturing company. I told him what he was describing is making the decision for them, and advising is something different. Asking your MSP to pick your ERP is a lot like asking your mechanic to pick your next house.
So how do you advise them on it? You ask the questions an MSP is actually good at:
- Is it a good piece of software, and is it secure?
- Is it in the cloud or on-premises, and is it maintainable?
- How does it affect support and the other systems they run?
- Who keeps it up to date, and if it's not the MSP, how does that happen?
- If they need support for it, what's the plan?
Then, when the client says "just tell me which one to buy," you say no, I can't tell you that, but here's what I can tell you. We reviewed it, and from an IT standpoint it's a good decision. Whether it's a good business decision, whether it fits your process and actually makes your business better, Mr. Client, you're the only one who can answer that.
What it looks like from the client side
After I was done working in the MSP, TruNova used the MSP I'd been part of for a while, and eventually we moved to a bigger national provider, thinking we were going to get good stuff. I've learned a lot from that seat, and the chairs are less comfortable on this side.
Their help desk was good, but a good help desk is permission to play. What I was looking for was great security and getting this stuff off my plate, and that's not what we got. They did a pretty poor job of even telling me what was going on. The patching report said everything was great. When we moved on from them, I installed Action1, and it turned out there were tons of patches that had never been applied. They were using a well-known RMM that supposedly does patching properly, and its report said everything was fine when it wasn't. From what I've seen that's extremely common, and it's a very bad thing.
And the conversations were about their service catalog. Every meeting was some version of why we should buy this thing or that thing, and the problem was always security, but every time I asked a question the answer was "oh, that's going to cost extra." That needs to be a much better conversation, and more importantly it needs to be a business conversation, and they absolutely did not have one.
Ask better questions
For me, it's about being curious and asking questions. The problem is people tend to ask too big of a question, like "where is your business going in three years?" A lot of businesses won't know how to answer that. If you ask fluffy questions, you get fluffy answers, or no answer at all. People don't like feeling stupid, so they'll skip the meeting or not answer the email because they don't know what to say.
So you have to figure out how to ask a question that's specific enough, but not too specific. Not the little details, more like what does your hiring look like this year. And you have to connect it to why you're asking. I've had people we work with ask me super fluffy questions like "how's your sales going?" You don't need to know that, it doesn't affect you in any way. If it's not obvious why you're asking, explain it: we're asking because it affects these things, and it helps us plan for them with you.
That's a tricky piece to work out, but that's a form of consulting.
Why most MSPs struggle with it
The numbers back this up. The ScalePad 2026 MSP Trends Report found that only about 29% of MSPs offer vCIO services at all, while back in 2023 TD SYNNEX and Canalys found 65% of MSPs named business consulting and planning as their top investment priority. And of that 29%, I'd bet most aren't doing a great job of it, because who does vCIO at most MSPs? An account manager, sometimes an account manager plus. It should be a consultant, somebody who understands business and can have a real conversation with the CEO, the CFO or the general manager.
That's hard, because those people are expensive. When I moved over to the consulting side, the cost structure was one of the hardest adjustments. A really good advisor (aka Consultant) is going to be expensive. If your vCIO is making a tier two or even a tier three engineer salary, they're probably not the advisor you really want to have. That doesn't mean it's all bad, but maybe don't call it technology advising.
Sell what you actually do
One of my rules, with the benefit of hindsight, is to always do at least what you promise. If you tell clients you're going to do it, you have to back it up, and if you can't, change how you position and sell it.
You don't have to become a consulting company. I've met MSPs doing very, very well that just say we don't do vCIO, we take care of these things for you, and if you need other things, go talk to other people. Nothing wrong with that. Think of yourself as a broker, almost like a general contractor. You do some of the work and do a great job at it, and for the things you don't do, you find partners who can come in and help. In our case that's business applications like ERP, Power Platform, automation and business intelligence. The next few parts of this series are about deciding what you own and what you hand off.
There's no one right way to do it. Just be honest with yourself, and more importantly, be honest with your clients. Always do at least what you promise, and if you can't, change how you sell it.
If you've built an advisor role that works, I'd love to hear how you staffed it.



