Your Software Vendor Is Not Your CTO

The people offering to design your technology stack are, almost without exception, the people selling you a piece of it. That is the quiet problem at the center of self-storage technology, and most operators never name it because the help looks free and feels generous. It is not free. You pay for it later, in a stack built around someone else’s product roadmap instead of your operation.

I have spent 24 years operating self-storage, and I have sat on the buying side of enough of these conversations to know how they go. You are growing, the systems are straining, and you do not have a senior technology person on staff because at fifteen sites you cannot justify the salary. So you turn to the one group of people who seem to understand storage technology and are happy to advise: the vendors. They send a solutions consultant. The consultant is sharp, knows the industry, asks good questions, and hands you an architecture. And every arrow on that architecture points back to their platform.

This is not a story about bad vendors. Some of the best technology people in this industry work for the software companies. It is a story about what a vendor is structurally built to do, and why that job is not the same as the job you actually need done.

What a vendor is built to do

A software vendor exists to sell and retain software. That is not cynical, it is just the business. Their revenue is the product. Their roadmap is the product. When they advise you, the advice is honest and also, always, downstream of one fixed conclusion: the answer involves more of their product. A vendor cannot tell you that their own module is the weak point in your stack. They cannot tell you to keep a competitor’s system because it fits your operation better. They cannot recommend building something custom instead of buying their add-on. Not because they are dishonest, but because you are asking a question their business model cannot answer against its own interest.

Think about what you are actually doing when you let the vendor design the stack. You are asking the company whose incentive is to sell you more to decide how much you need. You would never let a contractor who is paid by the square foot decide how big your building should be. You would never take portfolio advice from the broker earning the commission on the trade. But in technology, because the category feels specialized and the vendor feels expert, operators hand over exactly that decision, and then wonder why the recommendation is always to expand the footprint of the platform they are already on.

What the job actually is

The job you need done is different. Somebody has to sit on your side of the table and answer a set of questions that no one selling a product can answer cleanly:

What should we keep, and what is actually holding us back? A straight answer requires being willing to say “this system you already pay for is fine, do not replace it,” which costs a vendor a sale.

Where should we build, and where should we buy? The honest answer is sometimes “build nothing, you are over-engineering,” and sometimes “do not buy their module, it will lock you in.” Neither is available to someone earning on the module.

What does this decision cost us in three years, not three months? Vendors sell on the near-term win. The lock-in, the migration cost, the data you will not own, the integration that only works while you stay on their platform - those are three-years-out problems, and they are exactly the problems the person recommending the purchase is not accountable for.

Who owns the outcome when it breaks? When the stack the vendor designed does not scale, the vendor does not own that. You do. The consequence lands on the operator every time, which means the decision should be made by someone whose only interest is the operator.

That role has a name in every other industry that runs on technology. It is the technology leadership seat - the person who holds the architecture, makes the build-versus-buy calls, manages the vendors rather than being managed by them, and answers to ownership instead of to a sales quota. Growing storage operators need that seat filled long before they can justify hiring it full-time. So it goes unfilled, and the vendors fill the vacuum, and the vacuum is the problem.

The fair version of the other side

To be fair to the vendors: for a lot of operators, most of the time, following the platform’s recommendation works out fine. If your needs are standard and you are early, the bundled path is genuinely easier, and a good vendor’s stack will serve you for years. Independence matters most at the decisions that are expensive to reverse - the source-of-truth system, the data ownership terms, the integration architecture, the platform you will build a decade of process on top of. On the small, reversible calls, take the easy path and do not overthink it. The argument here is not “never trust a vendor.” It is “do not let the vendor make the decisions you cannot take back.”

And the honest objection: an independent advisor costs money, and the vendor’s advice is free. True. But the vendor’s advice is only free the way a “free” stack design is free - the cost is in the purchase it steers you toward and the flexibility it quietly removes. The independent seat is a line item you can see. The vendor-designed stack is a cost you discover later, usually at the worst possible time, which is the day you try to change something and find out you cannot.

The one question to ask

Before you take another architecture recommendation, ask the person giving it one question: what would you tell me to do that costs you money? If the honest answer is “nothing” - if every recommendation they have ever made to you also happened to grow their invoice - then you do not have an advisor. You have a salesperson, and there is nothing wrong with that, as long as you know which one is sitting across from you. The mistake is not listening to vendors. The mistake is confusing the person selling the tools with the person who is supposed to be protecting your operation from buying the wrong ones.