Here is a question worth sitting with for a minute.
When was the last time someone looked at your company’s technology and told you the truth about it, with nothing riding on the answer?
Not a proposal. Not a renewal conversation. Not a roadmap that happened to recommend more of what the person presenting it already sells. An actual assessment, from someone with no stake in the outcome.
For most firms, the honest answer is never. And that is not a failure of judgment. It is a structural problem, and it is worth understanding why it happens, because it explains a lot of what feels stuck.
The three people you would normally ask
Start with your MSP. They are competent, they keep the lights on, and they probably do good work. They are also a vendor. When you ask them what you should do next, you are asking a company whose revenue depends on the answer. That does not make them dishonest. It makes their recommendation a proposal, and a proposal is a different thing from an assessment. Every MSP assessment I have ever read ends with a recommendation to buy something from the company that wrote it.
Next, your internal IT person or team. They know your environment better than anyone. They are also heads down on tickets, they are evaluating a set of decisions they made or inherited, and they are being asked to grade their own homework. Even the most honest technologist in the world struggles to tell an owner that the platform they championed three years ago was the wrong call. That is not a character flaw. It is human.
Finally, you. You know the business cold. But you have no basis for comparison. You do not know whether your spend is high, low, or normal for a firm your size. You do not know whether the friction your project managers complain about every week is unavoidable or a solved problem everywhere else. You have never seen the inside of twenty other firms.
So the three parties best positioned to know all have a reason not to give you a straight answer, or no way to know what a straight answer would sound like.
“Backups and DR are fine”
Here is the cleanest example I know of.
Ask your IT team whether your backups and disaster recovery are working. They will tell you yes. They are almost certainly not lying, and the backup jobs are almost certainly reporting success.
Now ask a different question. When did someone last restore from them?
Not a test file. A real restore, of a system the business actually depends on, timed against how long the company could genuinely tolerate being down, documented, with someone other than the person who built the backup checking the result.
For most firms that has either never happened or happened years ago, and in the meantime the environment changed. A server got added and never made it into the job. Credentials expired quietly. Retention was shortened during a storage crunch and never restored. The restore technically works but takes four days, and everyone had assumed four hours.
Nobody discovers any of this on a normal Tuesday. They discover it during the incident, which is the single worst moment to be learning it.
That gap between “it is handled” and “we have verified it” is the whole problem in miniature. The first is an assertion. The second requires someone outside the reporting line to actually look, and at most firms there is nobody whose job that is.
The decisions nobody reviewed
It is not only systems. The same blind spot shows up in policy, and often with more consequence.
AI policy is where I see this most right now. Nearly every firm is writing one. The pattern is that a draft gets produced by a single function, circulated for approval, and adopted without anyone who would actually use the technology ever being in the room. The language reads as prudent. The effect is to foreclose the entire category before anyone has tested whether it would have helped.
There is rarely bad intent in it. These documents are written by people whose job is managing risk, doing that job exactly as they understand it. But if nobody with a stake in the upside is at the table, the document only ever prices one side of the ledger.
That is what policy written by a single function tends to do. Security writes to eliminate risk. Legal writes to eliminate liability. Finance writes to eliminate spend. None of them are wrong on their own terms, and each produces a document that quietly forecloses things the business needed, in language definite enough that nobody afterward feels able to question it.
Once a policy is signed it becomes the ceiling. And the people who would have objected usually find out after it is already the rule.
What that costs, in practice
The rest of the symptoms are mundane, which is exactly why they persist.
Vendor spend that goes up at every renewal, and nobody can articulate what changed to justify it. Contracts nobody has read closely in years. Three overlapping tools that each solve a piece of the same problem, bought by three different people in three different years. A line of business system the whole company depends on, maintained by one person who is retiring. A workflow that adds two days to every project because it was designed around a constraint that stopped existing in 2019.
None of these are emergencies. That is the problem. Emergencies get attention. These get worked around, and the workarounds calcify into how the company operates. Ask a firm why they do something a particular way and often enough the honest answer is that a person who left four years ago set it up that way.
The cost is not a line item. It shows up as capacity, as staff spending hours on things that should take minutes, as project delivery slower than it should be, as a technology budget growing faster than headcount without anyone able to say why.
What an outside look actually produces
I run an engagement called a Technology Alignment Review. It is deliberately unglamorous. I spend time with leadership and with the people who actually use the systems every day. I read the vendor contracts. I look at what you are spending and against what. I look at where real operational risk sits, including the things everyone assumes are handled.
What you get at the end is a written current state assessment, a review of your vendors and contracts including how your MSP is performing against what you are paying, a prioritized roadmap with sequencing, and a direct recommendation about what to do next.
Including, and I mean this, a recommendation to do nothing further if that is the honest answer. Some firms are in better shape than they think and mostly need confirmation and a short list. That is a legitimate outcome and I will tell you so.
The engagement is scoped and capped before any work begins. You know what you are buying and what it will cost before you commit to anything.
Why independence is the whole product
I sell no products. I resell no software. I take no vendor commissions, no referral fees, no kickbacks of any kind. There is no version of this where my recommendation routes revenue back to me.
That constraint is not a marketing position, it is the reason the work has any value. The moment I have something to sell you beyond my own time, you are back to reading a proposal and wondering what is behind it.
It also means I will occasionally tell you your MSP is doing a good job and your systems are fine. That happens. It is worth paying for, because now you know instead of suspecting.
Who this is actually for
Engineering, construction, building services, manufacturing, and other operations heavy businesses. Companies that have grown past the point where one person can hold the whole technology picture in their head, but are not big enough to justify a full time CIO.
That is a specific and very common place to be. It is where technology decisions quietly outrun the people making them, and where nobody in the building has both the perspective and the independence to say so.
If any of this describes your firm, the conversation costs nothing, and I will tell you straight if I do not think there is anything here worth doing.
Start the conversation
If you want to know what an outside look at your technology would actually find, the place to start is a short conversation. No pitch, no products, and no obligation on either side.
Or reach me directly at 484-580-9523.
