FinOps audit
We find out where your cloud money goes and find savings. Every saving is priced in CZK per month, rated for effort and risk, and ranked by impact.
CZK 105,000
3 weeks, 15 person-days, Azure or AWS, up to 3 subscriptions or accounts. Excl. VAT.
Book a consultation
What we offer
We also design a tagging, cost allocation and budget model, so costs have an owner and do not surprise you next time.
The audit is read-only and we change nothing in your environment.
We do not write applications. We work only on infrastructure, cloud and DevOps.
When it makes sense
- Your cloud bill grows faster than your business.
- You do not know what each team or product costs.
- You have no reservations or Savings Plans, or do not know whether they are set up right.
- Finance wants predictable costs and a monthly overview.
What you get
- A cost breakdown by service, environment and team.
- A list of savings priced in CZK per month, with effort and risk.
- A tagging and cost allocation model.
- Budgets and alerts that flag deviations before the invoice does.
- A monthly cost report template.
What exactly we do
We analyse costs in eight areas:
- Cost structure
- Breakdown by service, environment and team, the trend over 3 to 6 months, anomalies.
- Unused resources
- Unattached disks, old snapshots, unused IP addresses, stopped but billed resources, empty plans.
- Resource sizing
- Virtual machines, databases and Kubernetes node pools against their real usage.
- Commitments
- Reserved Instances, Savings Plans, Azure Hybrid Benefit: coverage and recommendations.
- Storage and data
- Storage tiers, lifecycle policies, log retention (Log Analytics ingestion is often a big item).
- Network
- Egress traffic, NAT gateways, cross-region traffic.
- Non-production environments
- Shutdown outside working hours, smaller SKUs.
- Cost management
- Tag coverage, allocation to teams and products, budgets, alerts, ownership.
Who works on it
The audit is 15 person-days and three people work on it.
-
Senior, project lead
3 daysResponsible for
Commitment strategy (reservations, Savings Plans), review of recommendations and risks, the conversation with finance, readout.
What you get from them
Main contact, recommendations, readout
-
Middle
6 daysResponsible for
Cost and usage analysis, resource sizing, tagging and allocation model, budgets and alerts.
What you get from them
Analysis, allocation model, budgets
-
Junior
6 daysResponsible for
Billing data export, inventory, finding unused resources, overviews and the report template.
What you get from them
Data, overviews, report template
We assign work by complexity: juniors do routine work from templates, the middle takes the harder parts, and the senior owns the design, quality control and risk decisions. You do not need to decide who does what. The effort in days is indicative and only explains the price. The price is fixed and does not depend on the days actually worked.
How the project runs
The audit has three phases and takes 3 weeks.
Week 1: data and access
Goal: Get complete cost and usage data.
- Read access to costs and resources.
- Cost export (Cost Management exports or the AWS Cost and Usage Report).
- Inventory of resources and their owners.
- A conversation with finance and IT: budget, who pays, planned growth, contracts with Microsoft or AWS.
Output: Data ready for analysis. Who: junior data, senior the conversation
Week 2: analysis
Goal: Find and price the savings.
- Analysis of cost structure, unused resources, sizing, commitments, storage, network and non-production environments.
- Usage metrics (Azure Monitor, CloudWatch). We take Azure Advisor or AWS Compute Optimizer recommendations as input and verify them by hand.
- Every saving priced in CZK per month.
Output: List of savings (draft). Who: middle analysis, junior unused resources, senior commitments
Week 3: recommendations and cost management
Goal: Prepare the savings plan and set up cost management.
- List of savings with effort, risk and a way to verify each.
- Tagging and cost allocation model.
- Budgets and alerts, if we get the permissions.
- Monthly report template.
- Readout.
Output: Report, savings list, allocation model, budgets, template. Who: whole team, readout by the senior
How we work together
- Main contact
- The project lead (a senior). Accountable for the result, deadlines, risks and decisions. Day to day you can talk to anyone on the team directly.
- Communication
- A shared Slack or Teams channel and a ticketing system of your choice. Every question and change leaves a trail.
- Kick-off
- At the start we confirm the scope, access, contacts and the dates of the key milestones.
- Weekly status
- A short 15 to 30 minute sync: what is done, what is next, what we need from you and which risks we see.
- Final readout
- We present the results to your team and management and go through the next steps.
- Escalation
- Junior → middle → project lead. If a deadline or a major risk is at stake, the project lead contacts you the same day.
- Working hours
- Working days, 8:00 to 17:00 Central European Time. Production changes happen in a window you choose, always through your change management.
What we need from you
The timeline holds if we have the following. If something is delayed, the schedule moves by the same time and we tell you straight away.
- Read access to costs (Cost Management Reader, or Cost Explorer and CUR).
- Read-only access to the resources in scope (up to 3 subscriptions or accounts).
- A contact in finance and in IT.
- Information about plans: new projects, contracts with Microsoft or AWS, planned growth.
Access and security
- Every team member has their own named account. We do not use shared accounts.
- We ask only for the permissions a phase needs. Where read access is enough, we work read-only.
- We do not take data out of your environment. Our documents contain only the summaries the result needs.
- When the project ends, you remove our access, or we remove it on request and confirm it.
- If you wish, we sign an NDA before the kick-off.
What is included and what is not
Included in the price
- 15 person-days, up to 3 subscriptions or accounts
- Analysis in eight areas
- List of savings priced in CZK per month
- Tagging and allocation model
- Budgets and alerts set up (with permissions)
- Monthly report template and readout
Not included: priced separately or on your side
- Carrying out the savings (priced separately, or done by your team)
- Buying reservations and Savings Plans
- Negotiating contracts with Microsoft or AWS
- Licences outside the cloud (for example Microsoft 365)
If we find during the project that reality differs from what we assumed, we tell you before we work outside the scope. We send a short estimate of the impact on price and timeline and continue only once you agree.
Deliverables and acceptance
| Deliverable | Contents | Form |
|---|---|---|
| Report | Cost structure, findings, recommendations | PDF and Word |
| Savings list | Saving in CZK per month, effort, risk, approach | Excel |
| Allocation model | Tags, owners, breakdown by team and product | Document |
| Budgets and alerts | Set up in your cloud | In your environment |
| Report template | Monthly cost overview | Excel or dashboard |
| Readout | Presentation for IT and finance | Meeting and PDF |
The project is done when:
- We have handed over the report and the savings list.
- Budgets and alerts are set up, or their setup is described.
- The readout has taken place.
- We have incorporated one round of your comments.
We hand over the deliverables and go through them with you. We incorporate comments in one round within 5 working days of receiving them.
Risks and how we handle them
| Risk | How we handle it |
|---|---|
| Short data history | We mark commitment recommendations as conditional and say when to re-check them. |
| Downsizing hurts performance | Every recommendation states its risk and how to verify it (non-production first, watching the metrics). |
| Unclear cost owners | We propose owners in the allocation model and have them confirmed. |
Price and terms
CZK 105,000 excl. VAT, fixed price (15 person-days, up to 3 subscriptions or accounts).
- Duration: 3 weeks.
- Prices exclude VAT, invoiced in CZK or EUR.
- Work outside the scope: a separate quote, always in advance.
What can follow
Next steps
- 1A short 30 minute call: we look at your environment and check that the service fits what you need.
- 2We confirm the scope, the start date and the contact people.
- 3We send the contract and the list of access we need to start.
Frequently asked questions
Do you guarantee savings?
No. We price the potential of each saving and its risk. The result depends on which savings you decide to carry out.
Will you change anything?
No, apart from budgets and alerts if we get the permissions. Savings are carried out by your team, or by us under a separate order.
How many subscriptions can you cover?
Up to 3 are included. A larger scope is priced up front.
Tell us what you are working on.
Thirty minutes, free. We reply within one working day.