Most organisations that contact us have already tried something. They have run Azure Advisor, AWS recommendations, or their own checks. The problem is not a shortage of output. It is that the output is generic and untranslated, and does not tell them what matters for their specific environment, what to do first, or why. A platform review is a different thing: a structured, human-led assessment that starts with understanding your situation and ends with specific, prioritised recommendations you can act on.
Something has prompted this conversation. Maybe a performance issue that keeps coming back and nobody can find the root cause. Maybe a cloud bill that is higher than it should be and it is not obvious where the spend is going. Perhaps a DBA has left, taking years of knowledge and context with them. Or maybe it’s a platform that was built years ago, added to over time, and nobody is quite sure whether it’s still fit for purpose.
In some cases it is more acute. The platform is unstable. Something is failing regularly. The business is feeling it.
What these situations have in common is not the severity. It is that you have reached the limit of what you can diagnose or resolve with the tools and resource you currently have. That is the moment a platform review becomes useful.
You have probably already run the automated tools
Azure Advisor and the AWS equivalent will give you a list. Security recommendations, cost alerts, configuration flags. Some of that output is useful. A lot of it is generic, untranslated, and not calibrated to your specific environment, workload, or circumstances.
Those tools are designed to give you a view of your infrastructure from the cloud provider’s perspective. They are not designed to tell you whether a recommendation is actually relevant to you, whether there are prerequisites to address first, or whether a suggested configuration change would have unintended consequences in your specific setup.
Most people I speak to have done a first pass over it, found the obvious things, and still have a list of recommendations they are not sure what to do with. That is exactly the point at which a platform review becomes the right next step.
What a platform review is not
It is not a faster version of the automated tools. It is not a consultant running a script and producing a formatted version of output you could have generated yourself. It is not a long list of things you need to investigate further.
Think about taking your car in for a service. If the mechanic tells you that you need to evaluate your brakes, that is not a service. You already knew that. What you need is for someone to actually look at the brakes, tell you what the problem is, and tell you exactly what needs doing and why.
A good platform review works the same way. The output is specific, actionable recommendations. Not broad themes. Not observations. Concrete steps: do this, in this way, for these reasons. If there are two or three viable directions depending on whether your priority is cost, performance, or availability, we will lay out the options, explain the trade-offs, and make a clear recommendation.
The other thing worth saying directly: this is not an AI-generated report. Those tools exist and they have their place. What we bring is decades of working inside complex SQL environments across hundreds of customers, an understanding of your specific business context, and an opinion. A list of recommendations without expert judgment behind it is homework, not a solution.
What actually drives the need
The scenarios we see most often fall into a few categories:
- A performance issue nobody can get to the bottom of. Something is wrong, fixes are applied, the issue returns in a slightly different form. The pattern repeats. Often the cause is buried in the index configuration, query design, or a configuration decision made years ago that has never been revisited.
- A cloud bill that does not add up. Reservations misaligned with actual deployments. Service tiers that made sense when the environment was built but do not reflect current workloads. Instances provisioned for capacity that is no longer needed. These things accumulate quietly and the savings available are often significant.
- A DBA has left. Institutional knowledge has walked out the door. Nobody is certain what the environment contains, what decisions were made and why, or what risks are currently sitting unmanaged.
- A platform that has outgrown its original design. Built three or five years ago, grown organically, never fundamentally reviewed. The business has changed, data volumes have grown, workloads have shifted. The platform may still be running but nobody can say with confidence what the headroom looks like or whether the architecture is still the right one.
- A transition point. A scaling event, a migration, an acquisition, a compliance requirement. A moment where the stakes have changed and the question is whether the current platform is actually ready.
In almost every case the common thread is the same. There is a question the organisation cannot answer with the resource it currently has.
What a platform review actually involves
It starts with a conversation about what you are worried about, what has happened, what you have already tried, and what matters most to your business.
That context shapes everything that follows.
A review where the primary concern is cost reduction looks different from one where the primary concern is availability or a recurring performance issue. The scope is determined by what you actually need to understand.
From there, we work through your environment: performance and query analysis, index health, backup and recovery configuration, security posture, configuration against best practice, cloud architecture and cost optimisation. Where the focus is a specific problem, that gets priority. Everything else is assessed in the context of what is most relevant to your situation.
The output is a written report, prioritised by actual risk and impact. Not everything that could theoretically be improved. The things that matter, in the order they matter, with specific recommendations attached to each.
There is also a follow-up session. Not to sell the next thing. To walk through the document, answer every question, and make sure you are in a position to act on what is in the report: whether you use us to do it, your internal team, or someone else entirely. You are not dependent on us to interpret the output. That is deliberate.
Ready to find out what is actually going on in your environment?
We will give you a clear picture of the risks, the priorities, and what to do next. One fixed price, no obligation to take things further.
Quick answers to common questions
Frequently asked questions
We have already run Azure Advisor. Do we still need a platform review?
The automated tools give you a list of what the cloud provider thinks you should address. A platform review tells you what is actually relevant to your specific environment, what the priority order is, and what each recommendation means in practice for your workload and business context. They are different things.
Our environment seems to be running fine. Is a platform review still relevant?
The most common thing we hear after completing a review is that something significant was found that was not visible from the outside. If there is a specific concern, a transition on the horizon, or simply a platform that has not been reviewed externally in some time, it is likely worth doing.
How long does it take?
Scope varies depending on the size and complexity of the environment. Most reviews are completed within a few weeks of engagement starting.
Will you tell us things we have to fix, or give us options?
Both. Where there is a clear best action, we will say so directly. Where the right answer depends on your priorities, we will give you the options, explain the trade-offs, and make a recommendation.
Is this designed to sell us into a managed service?
Honestly, it often is the start of a longer relationship. But the report stands on its own. You can take it and action the recommendations yourself, find another provider to help, or come back to us. I would rather you had a clear picture of your environment and made the right decision for your business than ended up in a managed service that did not make sense for you.
What makes this different from other providers offering a health check?
Most health checks are a script run against your environment and a formatted list of outputs. What we deliver is a handcrafted assessment that starts with your specific concerns, your environment, and your business context. The recommendations are written for you, not generated for a generic SQL Server environment. And we are accountable for them.
About the Author
Christian Bolton
"We're not a support desk you just log tickets with. We're on calls with our customers 2 or 3 times a week. We know our clients' platforms like we built them ourselves."
