Purpose
This pilot is for organisations that suspect cloud waste, want clearer visibility of optimisation opportunities, and prefer a controlled, evidence-based first step rather than a broad architecture or FinOps programme. Intended to rapidly analyse selected Azure, AWS, or GCP spend, identify safe optimisation opportunities, and document the most important cloud-cost priorities before broader FinOps or platform work.
What you get
- Read-only analysis of selected billing, inventory, and usage data across the scoped environment
- Ranked savings and optimisation opportunities with practical owner notes and impact commentary
- Validation notes for selected safe changes or queued actions, depending on the agreed pilot scope
- Close-out summary with priorities, issues, and next-step recommendations
Typical outcomes
- Better visibility of waste, idle resources, over-sized services, and ownership gaps
- Clearer understanding of which optimisations are safe to act on now and which need further analysis
- A practical starting point for guardrails, tagging improvement, and sustained optimisation
Typical pilot scope
A focused cloud-cost review for selected subscriptions, accounts, or projects in one agreed environment. Final scope, access model, assumptions, and any approved changes are confirmed through the intake process and the engagement SoW.
Best fit
- Teams with rising cloud spend and limited confidence in what is driving it
- Environments with patchy tagging, unclear service ownership, or uncertainty around safe optimisation
- Organisations that want an evidence-based clean-up path before wider cloud governance work
Prerequisites
- Read-only billing and inventory access to the scoped Azure, AWS, or GCP environment
- A named owner for cloud operations and a finance or cost-validation contact where relevant
- Agreement on whether the pilot is analysis-only or includes a small set of safe approved optimisations by exception
Assumptions and boundaries
- One agreed cloud environment or a limited set of subscriptions/accounts only
- This pilot does not include major re-architecture, migration, or landing-zone redesign
- The final engagement detail, assumptions, exclusions, and any approved change activity are confirmed in the SoW before work begins
Common risks we look for
- Missing or inconsistent tags that make ownership and savings validation harder
- Services that appear safe to optimise but have hidden operational dependencies
- Savings opportunities that require commercial or architectural decisions outside the pilot scope
- Incomplete billing visibility or fragmented access across multiple environments
What happens after the pilot
If the pilot confirms the right direction, Virtus can help you plan broader clean-up, guardrails, tagging improvement, or an appropriate managed cloud path.
Roll into managed → Managed Cloud
Start pilot scoping
Use the intake form to tell us about your current environment, priorities, 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 pilot scoping
