Assessments
Three ways
to start.
Each assessment has a fixed scope and a fixed price, agreed before we begin. You keep the report whatever you decide next, including if you do the work yourselves.
Assessment 01
VMware Renewal Decision
The question it answers
Should we stay on VMware, move to a hosted platform, re-platform, or go to public cloud, and what will each cost over five years?
Who it is for
Teams facing a VMware renewal, a forced move from a closing provider, or a board asking whether to leave.
What we look at
- Inventory: hosts, CPUs and cores, VMs, vSAN and NSX use, Cloud Director tenancies
- Feature use: what you rely on that is VMware-specific and what you do not
- Licensing: your quote against the per-core rules, and the 16-core minimum per CPU
- Routes: VCF or VVF, hosted VMware, Hyper-V or Azure Local, Proxmox, Nutanix, Azure or AWS
- Risk: migration effort, skills, support and exit costs for each route
What you get
- A core and feature inventory
- A five-year cost comparison of up to four routes
- One recommended route with the reasons
- A phased plan for that route
| Route | Effort | Risk | Fit |
|---|---|---|---|
| Stay on VCF | Low | Low | Costly |
| Hosted VMware | Medium | Low | Good |
| Hyper-V | Medium | Medium | Good |
| Azure | High | Medium | Partial |
Assessment 02
DR Readiness Review
The question it answers
If the primary site or the domain were lost tonight, what would come back, in what order, and how long would it take?
Who it is for
Organisations that have backups and perhaps replication, but have not proved recently that they can recover.
What we look at
- Targets: RPO and RTO per system, agreed with the business owners
- Coverage: what is backed up, replicated, immutable and offsite
- Dependencies: identity, DNS, networking and licensing needed to start anything
- Runbooks: whether written procedures exist and can be followed
- A test: one tier restored into an isolated network, timed
What you get
- A recovery tier table for every system
- A gap list in order of risk
- A timed test of one tier
- A runbook template and a test schedule
| Tier | Systems | RPO | RTO | Status |
|---|---|---|---|---|
| 1 | Finance, identity | 1 min | 1 h | Met |
| 2 | File, intranet | 24 h | 4 h | Missed |
| 3 | Build, test | 7 d | 3 d | Gap |
Assessment 03
Storage Health Check
The question it answers
How healthy is the array, when will it fill, where is latency coming from, and is it worth keeping?
Who it is for
Teams with one or two arrays that are filling up, slowing down, nearing end of support or simply undocumented.
What we look at
- Capacity: trend, snapshot reserve and efficiency, with a 12-month forecast
- Performance: latency and IOPS by volume, hot spots and noisy neighbours
- Resilience: path redundancy, zoning, firmware and support status
- Protection: snapshot schedules and replication against recovery targets
- Lifecycle: end-of-support dates and the options when they arrive
What you get
- A risk-ordered findings report
- A capacity forecast
- Quick fixes made on the day, where agreed
- Options and indicative costs for the next three years
| Finding | Risk | Fix |
|---|---|---|
| SQL volume near full | High | Same day |
| Single path on 2 hosts | Medium | Zoning change |
| Firmware behind | Medium | Planned window |
| Support ends in 14 months | Plan | Decision |
Let’s build what’s next
Not sure which fits?
Describe the problem in a few lines. We will tell you which assessment answers it, or whether you need one at all.