Find out what you could actually restore, and how long it would take

Everyone has a backup. Far fewer have a restore. The question worth answering is not whether jobs are running, it is when somebody last proved one and how long the business would be down.

Request this assessment
Free45 minutes, plus a written recovery position within three working days
Locked copies, tested restores, and a clean point to rewind to. Plays from YouTube. Nothing is requested from YouTube, and no cookie is set, until you press play. Read the transcript

Who books this

  • Nobody can say when a restore was last tested
  • You are not certain what Microsoft 365 retention actually covers
  • An insurer or auditor has asked about immutable backup
  • You have backups from more than one product and nobody owns the whole picture

What you get

  • What is covered, what is not, and what you may believe is covered and is not
  • A recovery order for the systems that matter, with realistic times
  • A straight answer on whether your backups are immutable and what that means here
  • What to test first, so the next restore is proved rather than assumed

What we need from you

  • What is currently backed up and with which product, however roughly
  • Which systems the business genuinely cannot run without for a day
  • Any recovery time you have been asked to commit to, by an insurer or a contract
When not to book this

If you have tested restores on a schedule this year, hold immutable copies and could state your recovery times from memory, you are ahead of nearly everyone and do not need this.

Other assessments

  • Microsoft estate review: Forty-five minutes and a written summary. What you are licensed for, what is switched on, where the gaps are, and what we would fix first.
  • Security posture review: Most of what we find is not missing products. It is features you already pay for that were never switched on. Forty-five minutes to find out which.
  • Cloud cost review: Non-production running around the clock, orphaned resources nobody decommissioned, and licences still assigned to leavers. Forty-five minutes to quantify yours.
Show all 12 assessmentsShow fewer assessments
  • Cyber Essentials readiness check: The five control themes, checked against what you actually run. Most first-time failures are the same handful of things, and all of them are cheaper to fix before you apply.
  • Application compatibility assessment: Migrations do not stall on operating systems, they stall on a handful of applications nobody can account for. This sorts your estate into the four groups that actually matter, before you commit budget to any of it.
  • Virtual desktop review: Whether you are choosing between Azure Virtual Desktop and Windows 365 or already running one and paying more than you expected, this is the same review: what the estate is doing, what it costs, and what it should cost.
  • Copilot readiness check: Copilot does not grant anyone a single permission they did not already have. It just makes what they already had very easy to find, which is why the permissions work belongs before the licences and not after.
  • Application and reporting discovery: Most bespoke software goes wrong at scoping rather than in the build, and the most valuable thing a first conversation can do is establish whether you should be commissioning software at all.
  • Endpoint and Intune review: Not whether Intune says the estate is compliant, but whether that means what you think it means: what is enrolled, what has gone quiet, which policies are actually winning, and what you could prove if somebody asked.
  • DfE digital standards baseline: Sixty minutes against all twelve DfE digital and technology standards, the six core ones first. You get a governor-ready summary of where you stand and a dated plan for each gap, whether or not anything else follows.
  • RDS health check: Connection Broker, Session Hosts, Gateway, Web Access, licensing, profiles and load balancing, reviewed as one estate. You get an executive summary to take to budget approval, the technical findings with their root causes, and a rectification path in the order we would do it.
  • Kemp LoadMaster health check: Load balancers are the classic forgotten appliance. We review your LoadMaster's configuration backup and logs offline, so nothing connects to or changes the appliance, and you get a written report on its health with the evidence behind every finding.