Why Your IT Department Shouldn't Pick Your Next Platform
3 minute read
Most mid-market companies get this wrong, and they get it wrong in the same direction every time.
By default rather than design, software selection ends up owned by IT. They know technology, the project involves technology, and the hand-off feels logical.
It isn't.
Choosing a business platform is not a technology decision. It is an administrative decision and a financial decision. The person leading it should have line of sight into where the business is going, how it actually operates, and what it will cost if the choice is wrong.
Putting IT in charge is not a knock on their competence. It's a mismatch of scope.
IT is genuinely equipped to answer three questions: Can this system run in our environment? Does it meet our security requirements? Does it integrate with what we already have?
Those matter. They should be satisfied before any vendor makes a shortlist.
But once they are, the questions that remain are different in kind:
Does this platform actually solve the problem that is slowing us down?
Can it support how we need to operate two years from now, not just today?
What does it really cost when you include implementation, training, licensing, and the inevitable mid-course corrections?
What happens if we need to leave it in four years?
Who owns the vendor relationship, and what leverage do we actually have?
IT can have opinions on all of those. They should be in the room.
But their job is to keep things running. That orientation, stable, reliable, controlled, is exactly the wrong orientation for evaluating whether a platform can help a company grow.
The deeper problem is that the person who should be leading this decision often doesn't exist yet in a formal seat.
In a mature enterprise, there is usually someone whose role spans operations, technology, and business strategy. A COO who has been through platform transitions. A CFO who knows the real cost of a bad software decision shows up eighteen months after go-live, not at signing.
In a company doing $20 million or $80 million or even $150 million in revenue, that person is often missing.
The CEO is running the business. The CFO is managing the books. IT is managing the infrastructure. So the selection process flows toward whoever raises their hand, and that is usually IT, because the project looks like theirs.
What follows is a process where vendors get scored on features and demos get judged on functionality. The questions that determine long-term fit, total cost, and vendor accountability never get the same weight as the technical checklist.
By the time that gap becomes visible, the contract is signed.
The price is not paid in the IT budget.
It is paid in lost productivity when the system doesn't do what the business needed. It is paid in re-implementation costs when the platform that checked every technical box turns out to be the wrong operational fit. It is paid when the vendor relationship that looked like a partnership during the sales process becomes something else entirely after go-live.
Those costs land on the CEO's desk. On the CFO's quarterly numbers. On the operations team working around a system selected without them in the room.
If you are a president, CEO, CFO, or COO with a platform decision on the horizon, the most important thing you can do is not delegate ownership of it.
Get the technical requirements from IT. Make sure they're satisfied. Then take the rest of the process back.
The questions about business fit, financial exposure, vendor accountability, and what exit looks like if things go wrong belong to you. Not because you know more about software, but because you know more about what the business needs and what it cannot afford to get wrong.
PlatformIQ was built around exactly that gap. The evaluation framework puts the executive in the driver's seat, asking the questions that protect the business first and validate the technology second.
Because the selection process shapes the outcome.
And the outcome belongs to the people running the company.