Almost no company of your size knows its true technology spend on the first attempt. The IT budget is only part of it. Subscriptions run through expense reports, departments buy their own tools, and telecom lives somewhere else entirely. The first useful output of this domain is simply an accurate number.
You cannot judge whether you are spending too much until you know the total and how it compares. The more common problem is not the amount but the shape: underinvested where risk lives, overinvested where attention went.
We score against this benchmark, meaning what a well-run company of 50 to 500 employees should reasonably have in place, rather than against theoretical perfection.
Technology spend is visible across every budget line it hides in, including departmental purchases, expense reports, and telecom.
You know how your spend compares as a share of revenue against companies of similar size and industry, and where you sit deliberately above or below.
Overlapping tools are identified and consolidated as a routine, rather than discovered accidentally during a renewal.
Small purchases move quickly; large ones face real scrutiny. Nothing significant is committed without someone empowered to say no.
The business goes back and asks whether completed projects delivered what justified them, and that answer informs the next round of decisions.
Patterns common enough to name. None of them indicate a bad team. They are what happens when a company grows faster than the decisions that shaped its technology.
Software on credit cards, departmental tools, and telecom that never appear in the technology line, and enough to change the total materially once assembled.
Two or three products doing the same job in different departments, each defended by whoever chose it, none of them evaluated against the others.
Seat-based subscriptions that grew with hiring and never contracted with attrition, invoiced quietly every month.
Spend is reasonable in total but concentrated in what got attention, while the controls and foundations that reduce real risk stay underfunded.
Projects are approved with a business case and closed without anyone comparing the outcome to it, so the same optimistic assumptions repeat.
Where a document does not exist, that is itself a finding, and we say so plainly rather than treating the gap as an obstacle.
What do we actually spend on technology, and what should it be?
Where is the waste, and what would cutting it break?
Every domain is scored 0–10 on the same scale, so the scorecard shows you where to look first rather than a single undifferentiated grade.
Something here can hurt the business now. These findings lead the roadmap.
Functioning, but behind where a company of your size and stage should be.
In good shape. Worth maintaining rather than investing further right now.
A genuine strength, and often something to build on elsewhere.