Virtus Group • Cloud & automation pilot

Cloud Cost Tidy-Up Pilot

A focused review of selected Azure, AWS or Google Cloud spend so you can see what is driving cost, what may be safe to optimise, and what should happen next.

Virtus Group logo

Find cloud waste before it becomes normal

Cloud bills can grow quietly through unused resources, oversized services, weak tagging, old test environments or unclear ownership.

This pilot gives you a practical, evidence-led starting point without turning the first step into a large FinOps programme or cloud redesign.

What the pilot helps answer

Where is the money going?

Selected billing, inventory and usage data are reviewed so the main cost drivers are easier to see.

What can be cleaned up safely?

Opportunities are ranked so obvious waste can be separated from changes that need more care.

What should we do next?

You get practical priorities, owner notes and a clearer path for cleanup, guardrails or managed cloud care.

Common signs this is worth doing

Cloud spend has increased
but the business is not fully sure what changed.
Tagging is inconsistent
so ownership, cost centres or environments are hard to validate.
Old resources may still be running
but nobody wants to switch them off without evidence.
Cloud ownership is unclear
between IT, finance, projects, vendors or previous providers.

What we look for

The scope is agreed before work begins. The pilot usually focuses on one selected cloud environment, subscription set, account set or project set.

Idle or unused resources

Resources that appear to be unused, forgotten or no longer clearly owned.

Oversized services

Services that may be larger, faster or more expensive than current usage requires.

Tagging and ownership gaps

Missing labels, unclear owners and weak cost allocation signals.

Budgets and alert gaps

Areas where budget visibility, anomaly alerts or guardrails may be missing.

What you get

Ranked opportunities

Clear cost and optimisation items grouped by confidence, impact and risk.

Practical action notes

Owner notes, validation comments and suggested next steps for selected findings.

Close-out summary

A concise summary of priorities, issues and recommended follow-on actions.

How the pilot works

1

Scope

We confirm the cloud platform, accounts, access method and outcome.

2

Review

We analyse agreed billing, inventory and usage information.

3

Prioritise

We separate likely quick wins from items that need business or technical validation.

4

Decide

You choose whether to tidy up, set guardrails, expand the review or move into managed cloud care.

What this is not

Not a full FinOps programme

It is a focused first step, not a long-running governance programme.

Not a cloud redesign

Major re-architecture, migration or landing-zone redesign is scoped separately.

Not blind cost cutting

We do not recommend changes without considering ownership, dependencies and operational risk.

Quick questions

Which cloud platforms can be reviewed?

Azure, AWS or Google Cloud can be considered. The final pilot scope confirms which subscriptions, accounts, projects or billing views are included.

Do you need admin access?

Read-only billing, inventory and usage access is preferred. Guided screenshare, exports or screenshots may also be suitable depending on the scope.

Will you make changes during the pilot?

The default pilot is analysis-first. Any approved optimisation changes must be expressly agreed in scope before they are performed.

Are pilot prices published?

No. We confirm the estimate after scope, access requirements and deliverables are understood.

Want clearer cloud spend visibility?

Start with a short conversation. We will help confirm whether a Cloud Cost Tidy-Up Pilot is the right first step, or whether a broader review, project or managed cloud pathway makes more sense.

No hard sell. Just clarity and next steps.

Start with a free 30-minute IT conversation

hello@services.virtusgroup.biz
0800 847 887 (VIRTUS)
virtusgroup.co.nz