September is when the 2027 numbers start landing in spreadsheets. Headcount plans. Insurance renewals. Software subscriptions nobody quite remembers approving. Somewhere in that stack is a line for technology, and there is a good chance you will look at it, note that nothing has gone wrong lately, and approve it for another year.
That is a reasonable thing to do. It is also the decision most growing companies make with the least information in front of them.
So start with a question. If someone asked you to name three specific things that make you happy with your current IT contract provider, could you do it in under a minute?
Most leaders cannot. Not because their provider is doing a bad job, but because happy has quietly come to mean nothing is on fire. That is a low bar for a relationship you fund every month, and it is a very low bar for the year you are about to plan.
This post gives you three things you can actually measure, a thirty minute way to gather the answers, and a plan for what to do with them before January.
“We Are Happy With Our IT Contract” Is Not An Answer Yet
Our sales team hears that sentence more than any other. It usually ends the conversation.
It should start one.
Happy is a real feeling and it deserves respect. Nobody wants to change their doctor, their attorney, or the people who keep their technology running. Switching is disruptive, and the fear of a bad transition keeps a lot of companies exactly where they are. That instinct is not wrong.
But happy is not a measurement. It is a summary of a feeling, and when you dig into where the feeling comes from, it is almost always one of two things: the email stayed up, and nobody called you angry this month.
Both of those are good. Neither one tells you whether your technology can carry the company you are becoming.
Here is the test. Pick three data points that define happy for you. Write them down. Then check whether your provider is delivering them, or whether you have just gotten used to their absence.
Below are the three we would use. They are the same three we ask about when a company in Nashville, Chattanooga, Huntsville, or Birmingham first sits down with us, and they work whether you have eighty people or four hundred.
Measure One: How Fast Does A Real Person Answer?
Not how fast a system acknowledges the request. How fast a human being who can solve the problem starts talking to the person who has it.
This is the measure your team feels and you do not. When a payroll clerk cannot get into a system on the Thursday before payroll, she does not experience your technology partner as a strategy. She experiences it as how long she sits there. And the honest number is usually different from the number in the agreement.
Here is how to check it without a formal audit. Ask three people who are not managers, in three different departments, the same question: the last time something with your computer or a program stopped working, how long until someone actually helped you?
Listen for two things.
The first is the number. If the answers cluster around minutes, that is worth something. If they cluster around “I usually just work around it,” you have found something more important than a slow response. You have found that your team stopped asking. People do not stop asking because the process is fast. They stop asking because the effort of asking exceeds the value of the answer, so they build a workaround and carry it quietly. Those workarounds do not show up in any report. They show up as slower closes, slower onboarding, and a finance team that keeps a spreadsheet nobody else can read.
The second is the tone. Do your people describe the person who helped them, or do they describe a process? Companies that answer with a name are getting something companies that answer with a portal are not.
We ask about this first because it is the measure most closely tied to whether your team can do their jobs today. Everything else on this list is about tomorrow.
Nobody Quits Over One Bad Login
Measure Two: What Got Better This Year Without You Asking?
This is the one that separates a vendor from a partner, and it is the question almost nobody asks at renewal.
Go back twelve months. Name one thing about how your company uses technology that improved because your provider brought it to you. Not something you requested. Not something that broke and got fixed. Something they saw, recommended, and implemented while you were busy running the business.
If you can name two or three, that is a partner, and you should probably stop reading and go tell them.
If the list is empty, that is worth sitting with. It does not mean anyone failed. It usually means the relationship settled into maintenance, which is a comfortable place for everyone and a slow place for you. Your systems were built for a company that no longer exists, and nobody has had a reason to revisit them.
Here is a concrete example of what “got better” should look like. Business email compromise, where someone convincingly impersonates a person your team trusts and asks them to move money or share credentials, is now the way most successful attacks against companies your size actually start. Passkeys are the current answer, and they are better than the multi-factor prompts your team has been ignoring for three years, because there is nothing for an attacker to phish. Has anyone brought passkeys to your organization? Has anyone explained them to your team, rolled them out to the people who approve payments first, and reported back on adoption?
If the answer is no, that is not a security failure. Nothing has happened. But it is a clear, specific, checkable example of continuous value that either arrived or did not.
The same question works for anything: how your new hires get set up, how your systems talk to each other, how your reporting gets built. Pick any part of how your company runs and ask whether it works better than it did a year ago, and whether your technology partner had anything to do with that.
How Strong IT Can Help Onboard Faster
Measure Three: Can Anyone Show You The Next Twelve Months?
Ask your provider for the twelve month plan for your technology. Not a proposal. A plan. What is scheduled, what is being retired, what is being upgraded, what it will cost, and what each item is supposed to do for the business.
Then notice what you get back.
Some providers hand you a document. Some hand you a quote. Some ask what you have in mind, which is a polite way of saying the plan is whatever you think of, and that means you are the one doing the technology strategy for your company on top of your actual job.
A twelve month roadmap matters for a reason that has nothing to do with technology. It converts an unpredictable expense into a planned one. Your CFO can budget against a roadmap. Nobody can budget against surprises, and unpredictable technology spending is one of the most common reasons growing companies feel like their systems are working against them even when everything is running.
It also tells you whether anyone is thinking about your business past this quarter. A provider who bills you for hours has a structural reason to be responsive and no structural reason to make you need them less. A provider on a fixed monthly agreement has the opposite incentive. That is not a claim about anyone’s character. It is just how the arrangements work, and it is worth knowing which one you are in.
The ProSafeIT playbook exists specifically so this conversation is not improvised. Every client gets the same operating rhythm, the same reviews, and the same forward plan, because the alternative is that every client gets whatever their account manager remembered to bring up.
The Question Underneath All Three
Keeping the trains running on time is a genuine accomplishment. It stops being the accomplishment once someone invents the airplane.
That is the real question behind this whole exercise. Not whether your provider is doing what they agreed to do, but whether what they agreed to do three or five or eight years ago is still the thing that helps your company win.
Think about what happy meant in 2015. Email stayed up. The server got backed up overnight. Someone came out when a machine died. If your provider is delivering exactly that, and delivering it well, you can accurately say you are happy.
You would also be measuring against a standard the market moved past. Email staying up is not a service level anymore. If you run Microsoft 365, uptime is Microsoft’s problem, and your provider is being credited for something they do not do.
We are not saying your setup is failing. We are saying the definition of good moved, and nobody sends a notice when that happens.
Here is one example of how far it has moved. More than half the companies we work with no longer use internal email. Not less email. None. All internal communication and collaboration moved into Teams, in channels organized around how the business actually works. The people at those companies got hours back every week, decisions stopped living in somebody’s inbox, and institutional knowledge stopped walking out the door when someone left.
Nobody asked for that. It was brought to them, planned, and rolled out. That is what measure two looks like when it is working, and it is the kind of thing that never appears on a ticket report.
How To Run This Audit In Thirty Minutes
You do not need a consultant for this, and you should not wait for a quarterly review. Block thirty minutes this week.
Ask three non-managers, in three different departments, how long it takes to get real help when something stops working, and whether they ask or work around it. Write down what they say in their words.
Then answer measure two yourself. Open your calendar and scroll back twelve months. Find one improvement your provider brought you unprompted. Give yourself a real minute. If nothing surfaces, write “nothing” and move on. That is data.
Then email your provider one sentence: “Can you send me the twelve month technology roadmap for our company?” Note how long the reply takes and what arrives.
That is the whole audit. Three answers, one email, thirty minutes. You will know more about your technology relationship than you learned in the last four quarterly reviews, and you will know it before you sign anything for 2027.
One note on who you ask. Go to the people closest to the work, not the people closest to the vendor. Your office manager and your front line staff have the most accurate picture of what your technology actually feels like, and they are the least likely to be asked. That is where the useful answers live.
What To Do With The Answers Before January
If all three measures came back strong, you have something rare. Renew, and tell your provider specifically what you value so they keep doing it.
If one came back weak, name it out loud with your provider before you renew. Most will fix a specific, named gap. Very few will fix a vague sense that things could be better, because there is nothing to act on.
If two or three came back weak, you have a decision to make in the next ninety days, and September is the right month to make it. Not because anything is wrong today, but because the version of your company that exists in eighteen months will be built on whatever you approve this fall. Changing providers in January while you are also trying to hit a new plan is harder than deciding in September.
And if you are somewhere in the middle, which is where most companies land, the useful next step is simply a conversation with someone who will ask you harder questions than your current provider does. You do not have to switch anything to have it. You will just have a clearer picture of what good looks like in 2027, and you will be able to hold anyone, including us, to it.
That is worth thirty minutes. It might be worth the next three years.
We work with companies across Tennessee, Alabama, and the surrounding region who are growing past the point where the technology setup they started with can carry them. If you want to run these three measures with someone who does this every day, we will bring the questions and you can keep the answers either way.
