Not a security quiz — this one is about how the day to day works. Tickets, planning, cost, and what happens when something needs hands on site. You see your score and your priorities before we ask who you are.
Without one, every purchase becomes an emergency and every renewal a surprise.
Planned spend costs less than reactive spend, and it lets you say no to things with confidence.
Requests by text, corridor and direct email are requests that get lost.
One route means nothing gets dropped, and it finally gives you real data on what actually keeps breaking.
Unowned work is the main reason a small issue takes days instead of hours.
Ownership is what turns a queue into accountability, and it is the thing your staff notice first.
Reporting nobody reads is theatre. Reporting nobody produces is worse.
Three numbers you trust beat a forty page dashboard nobody opens.
Unsupported software is a security hole and a compliance problem at the same time.
End of support dates are published years ahead. Being caught out by one is a planning failure, not a technical one.
Manual setup costs hours per starter and drifts out of standard over time.
A new starter’s laptop should arrive configured, secured and ready, without anyone touching it first.
Unpredictable IT cost is usually a symptom of unscoped IT work.
Scope agreed in writing is what makes a bill unsurprising. Ambiguity gets billed eventually.
Most faults never need anyone to travel. The ones that do are the ones that hurt.
Honest geography beats a vague promise: routine where there are offices, scheduled with lead time elsewhere.
You cannot secure, budget for, or retire what you cannot list.
Most businesses are paying for licences nobody uses and running devices nobody owns.
Growth is when IT debt becomes visible, usually at the worst possible moment.
Written once, it turns a three week scramble into a checklist.
Detail
Right now IT reacts to problems instead of preventing them. That costs more than it looks like on any invoice, because most of the bill is paid in your staff’s time and repeated faults nobody ever fixed properly.
The basics function and the lights stay on. What is thin is the management layer above it: planning, ownership and reporting. You are likely paying for IT twice, once for the service and again in the time your team spends absorbing its rough edges.
This is a tidy environment and better than most. The items left are the ones that stop IT becoming the reason you cannot move quickly when you hire, open somewhere new, or take work on at short notice.
Very little to fault. At this level the value is in planning and resilience rather than firefighting, and in a second opinion to confirm nothing has quietly drifted since the last time anyone checked.
We will turn your answers into a short written plan: what to fix first, what it involves, and what it costs. A named engineer writes it, not a template, and it arrives within two business days.
Anything you answer “No” to shows up here straight away, most important first.
Your ten answers put you in one of these. You see which as soon as you finish, along with the specific items that put you there. Most businesses are not at the top, and that is genuinely fine — knowing which rung you are on is the useful part.
Very little to fault. The value now is planning and resilience rather than firefighting, plus a second opinion to confirm nothing has quietly drifted.
A tidy environment, better than most. What is left is what stops IT becoming the reason you cannot move quickly when you hire or open somewhere new.
The lights stay on and the basics function. What is thin is the layer above: planning, ownership and reporting you would actually act on.
IT reacts to problems instead of preventing them. Most of that cost never appears on an invoice, because it is paid in your team’s time and in faults nobody fixed properly.
This one is about how IT is run. The other half is whether you are actually protected — access, backups, monitoring, and what happens at 2am. That is the cyber security check: eight questions, about two minutes.
%20(1).webp){kind=logo}
%201.webp)
