Strategic IT Planning
Most IT problems are budget and planning problems wearing a technical disguise. Every GravIT managed client gets a named account manager and a technical lead who know your business, meet with you regularly to look at what's coming, and give you a plain-English view of what needs replacing, what needs securing and what it will cost, before it becomes urgent.
The same problem, at four different notice periods
Take one server approaching the end of its life. It is the identical piece of hardware and the identical fault in every case below. All that changes is how long you knew.
Eighteen months out
It is a line in a budget. You choose the financial year, you get quotes from more than one supplier, and you can wait for the right moment to buy. Nobody is stressed and nothing is urgent.
Twelve months out
Still comfortable. It goes in next year’s plan alongside everything else, and it can be sequenced around your quiet period rather than your busiest week.
Six months out
Options are narrowing. It is now a project competing for money that has already been allocated, and the timing is starting to choose you rather than the other way round.
The week it fails
There are no options. Whatever can be delivered fastest, at whatever it costs, configured in a hurry, plus the days you were down while it happened, which is usually the largest number and never the one on the invoice.
Nothing about the hardware changed. The difference in cost and disruption between the top of that list and the bottom is entirely the difference between knowing and finding out, and that is all strategic planning actually is.
What you get from strategic IT planning
Included with managed support for every client, not sold separately and not reserved for the large ones. Small businesses arguably need it more. A surprise replacement hurts a ten-person office far more than a hundred-person one.
A named account manager
Your point of contact for planning, budgets and licensing. A person who knows your business, not a rotating queue and not whoever picks up.
A technical lead
One engineer who owns the architecture, the standards and the security posture of your environment, and who remembers why things were built the way they were.
Regular strategic reviews
Monthly or quarterly, and pointed at what is coming rather than what broke. The meeting where nothing is on fire is the one that saves the money.
Reporting you can hand over
What happened, what we fixed and what needs attention, written for a business owner or a board rather than an engineer.
A technology roadmap
What is being replaced and when, far enough ahead that it is a decision rather than a reaction.
Budget forecasting
Next year’s IT spend as a number you can plan around, including the things that are easy to forget until the invoice arrives.
Licensing review
Checked rather than renewed on autopilot: departed staff still licensed, plans that no longer fit, and the renewals that quietly went up.
Lifecycle tracking
What you own, how old it is and when it stops being supported. Unglamorous, and the thing that makes every conversation above possible.
What the year actually looks like
“Strategic planning” is the sort of phrase that can mean nothing at all, so here is the plain version of what happens and when.
A written report
What happened, what we fixed, what is starting to look worrying. Short enough to actually read, and specific enough to act on.
A conversation
Your account manager and technical lead, in front of you, going through what is coming: growth, hires, sites, systems reaching end of life, anything you are planning that IT needs to keep up with.
The long view
A roadmap and a budget for the next twelve to twenty-four months, so the expensive things arrive as decisions you already made rather than as surprises.
It is not complicated, and that is rather the point. The value is not in the sophistication of the process. It is in the fact that it happens at all, on a schedule, whether or not anything is currently going wrong.
Why it matters more than it sounds
The expensive IT decisions are almost never the technical ones. They are the server nobody budgeted to replace, the licensing that quietly doubled, the security work deferred three years running, the migration attempted in the same fortnight as end of financial year. None of those are emergencies until they are.
What they have in common is that each one was visible well in advance to anybody whose job it was to look. That is the entire service: somebody whose job it is to look, on a schedule, and to tell you in plain English while you still have choices.
It is also what turns a support arrangement into something closer to having an IT department (the part that thinks a year ahead) without hiring one. It comes with managed IT support rather than being sold separately.
Frequently asked questions
Is this an extra we have to buy?
It's part of how we run managed IT, not a separate consulting line, and it applies to every managed client rather than only the big ones. Small businesses arguably need the planning more. A surprise server replacement hurts a ten-person office far more than it hurts a hundred-person one.
Do we get reports we actually understand?
That's the point. Short, readable, and written for a business owner or a board rather than an engineer: what happened, what we fixed, what needs attention and what it will cost.
How often do we meet?
Monthly or quarterly depending on what suits, plus ad hoc when something new comes up. The focus is practical planning rather than formal reports for their own sake.
What's the difference between the account manager and the technical lead?
The account manager is your point of contact for planning, budgeting and licensing. The technical lead owns the architecture, standards and security posture of your environment. One for the commercial conversation, one for the technical one.
We already have someone internal. Does this still help?
Often more, not less. An internal IT person with a second set of experienced eyes and a roadmap tends to get further than one carrying the whole thing alone.
Stop making IT decisions in a hurry
That is usually a planning gap rather than a technology one. Let's get ahead of it.