I need to make a platform decision in the next 90 days and every source of information I have is either a vendor trying to sell me something or an analyst report that was written for companies ten times my size.
That sentence was said out loud in a room in July, by someone running a company rather than a town. I recognized it immediately, because I have been on the other side of it with far less money and considerably more scrutiny.
I am the Mayor of Northvale, New Jersey, a borough of roughly 4,800 people. When we make a technology decision it happens in a public meeting, it appears in a public budget, and the people affected are sitting ten feet away in folding chairs.
There is no pilot phase nobody notices. There is no quiet rollback.
Why is analyst research calibrated for organizations ten times larger?
Because analyst research is a product, and products are built for the buyers who can pay for them. That is arithmetic, not conspiracy.
The reference architectures, the cost models, the implementation timelines — every one assumes a dedicated program manager, a change management function, and a budget line able to absorb a surprise. A borough has none of those. Neither does a twelve-million-dollar company.
So the shortage is not information. It is information calibrated to your actual conditions, and only one of those problems can be solved by reading more.
What can a vendor conversation reliably tell a small buyer?
Facts that are checkable. A vendor will not volunteer where the product fails, but will answer narrow questions accurately, because the answers can be verified and their reputation sits behind them.
So ask questions with one possible answer. Who is your smallest customer currently in production, and may I speak with them. What does renewal look like in year three. Which parts of this implementation have you never completed without a partner. What happens to our data if we leave. When did you last lose a customer this size, and why.
You are not asking a vendor to be neutral. You are asking them to be specific, then checking whether the specifics hold. What gets called a vendor problem is usually a question problem, and building the question set is most of the work — it is the part of technology sourcing that rarely gets described honestly.
Who is the right peer to call about a platform decision at small scale?
Somebody your size in an adjacent sector, not the leader in your own. They have nothing to protect from you, and their constraints resemble yours.
Local government has this built in, and it is one of the genuine advantages of public service. Boroughs talk to boroughs. Shared services agreements exist because no small town can carry a full technology function alone. If I want to know how a platform performed for a community of five thousand, I can find three mayors who will tell me before the week is out, and not one of them is selling anything.
Private companies at the same revenue are far more isolated, because the person holding the answer is often a competitor. That is a structural disadvantage, and it explains how many mid-market decisions end up being made from a deck.
What does a ninety-day platform decision timeline require, week by week?
Ninety days is generous, provided the time runs in this order.
- Weeks one and two — write down what failure looks like. Not requirements. Failure. The specific outcome that would make this a mistake in eighteen months. Most decisions go wrong because nobody named that at the start, so nobody recognized it arriving.
- Weeks three to six — talk to operators rather than vendors. Three organizations near your size who have lived with the product at least two years. Two years is the threshold where the honeymoon has ended and renewal has been negotiated once.
- Weeks seven to ten — pressure-test the exit. Data portability, contract terms, what breaks on the way out. If nobody can describe the exit, the decision is not reversible, and irreversible decisions demand a higher standard of proof.
- Weeks eleven and twelve — decide, and record the reasoning. Keep it. When the decision is questioned in year two, and it will be, the written reasoning is the only defense that holds. Public office teaches that quickly, because the questioning is a matter of record.
What should a leader facing a platform decision do first?
Stop waiting for the report. It is not coming.
What exists instead of the report is a handful of people who have already paid for the lesson, and most will share it if asked plainly.
Reliability rarely earns applause. But everyone notices its absence, and in a town of 4,800 people they notice it by name.
