Purpose
This review is for organisations that want structured clarity on their current IT posture and priorities, but are not looking for remediation or a broad consulting programme on day one. It is intended to provide a fixed-scope current-state review across agreed IT domains, highlight the most important risks and gaps, and produce a practical 90-day action plan before pilots or managed services are chosen.
What you get
- Discovery workshop and structured review of agreed domains
- Current-state findings summary with Top 5 risks and opportunities
- Prioritised 90-day action plan
- Recommended next pilot(s) and managed-service path where relevant
Typical outcomes
- Clearer visibility of current posture, gaps, and priorities
- A more practical shortlist of what to fix first and what can wait
- A cleaner decision path into pilots, managed services, or further discovery
Typical review scope
A focused fixed-scope review using read-only access or guided screenshare across an agreed set of domains, users, and sites. Final scope is confirmed through intake and the engagement SoW.
Best fit
- NZ SMEs that want a structured baseline before deciding where to invest next
- Teams preparing for budget planning, board reporting, or service-provider change
- Environments where risk, drift, or ownership is suspected but not yet clearly documented
Prerequisites
- Read-only admin access or guided screenshare for the agreed review domains
- Named sponsor and operational contact available for discovery and validation
- Basic environment and stakeholder information available before the review starts
Assumptions and boundaries
- Fixed-scope review only; no invasive changes or remediation inside the review
- One agreed environment and agreed user/site bands consistent with the final SoW
- No procurement, licensing resale, or custom integration work in this engagement
- Final engagement detail, scope, assumptions, and exclusions are confirmed in the SoW before work begins
Common risks we look for
- Read-only visibility is weaker than expected and key evidence is missing
- Stakeholders expect remediation to be included inside the review
- The agreed scope expands across too many users, sites, or domains for the base package
- Current documentation is poor, making findings harder to validate quickly
What happens after the review
If the review confirms the right direction, Virtus can help you move into the most suitable pilot(s) to establish a cleaner baseline and then the appropriate managed-service path for ongoing support.
Recommended next step → Explore pilot options
Start review scoping
Use the intake form to tell us about your environment, the questions you want answered, and the outcome you want to achieve. If the scope looks suitable, we will confirm the next step and send the SoW for approval.
Start review scoping
