Explain the spend
Understand which workloads, teams and environments drive costs. Make spending changes easier to investigate and explain.
What is FinOps? FinOps brings engineering, finance and business teams together to understand technology costs and make informed decisions about value. In cloud environments, that means shared visibility, clear ownership and an ongoing practice of improvement.
Explore the FinOps Foundation framework ↗01 / Why it matters
Cloud decisions become financial decisions.
New workloads, changing demand and forgotten resources can all change the bill. When ownership and reporting are unclear, it becomes difficult to explain that change—or decide what to do about it. FinOps gives teams a shared basis for those conversations.
Plan with more confidence
Give application owners and finance a common view of budgets, forecasts and the cost implications of growth or change.
Improve with context
Prioritise waste and inefficiency while considering performance, resilience and the value each workload supports.
02 / How I can help
From cost visibility to a repeatable FinOps practice.
We can start with the areas creating the most friction in your AWS or Azure environment. Each workstream has a practical output that your team can use and maintain.
Cost ownership & tagging
I help define owners, cost centres, projects and environments, review missing allocation data and establish tagging expectations at onboarding.
Useful output: an allocation approach, tagging rules and a prioritised list of gaps.
Reporting & showback
I help shape reports that connect cloud spend to workloads and owners, so teams can see their share of costs and understand changes. Showback makes costs visible without needing an internal billing process.
Useful output: a reporting structure, dashboard requirements and agreed review questions.
Budgets, forecasts & alerts
I help establish budgets, account for planned workload changes, review forecast variance and define who responds to thresholds or unexpected spending.
Useful output: a planning baseline, alert ownership and a recurring forecast review.
Resource efficiency & waste
I work with application owners and engineers to review idle resources, sizing, storage and backup schedules. Recommendations consider business criticality and operational requirements.
Useful output: an optimisation backlog with owners, dependencies and validation steps.
Savings Plans & reservations
I help review usage patterns, existing commitments and their coverage and utilisation. We assess suitability and trade-offs before deciding whether further commitments make sense.
Useful output: a commitment review and decision criteria tied to expected demand.
FinOps governance & collaboration
I help define responsibilities, review routines and the way cost decisions enter onboarding and change processes. Engineering, finance and application owners need a shared way to act.
Useful output: a working rhythm, ownership map and measures to track progress.
03 / Why work with me
I understand the operating reality behind the bill.
I’m a certified FinOps Professional, combining formal FinOps knowledge with practical cloud governance and operations experience.
At Convatec, I defined and implemented cloud governance and FinOps practices across AWS and Azure. My work connected cost visibility, platform operations and decisions made with application owners.
My earlier experience in application development and Agile delivery helps me ask how a workload is used, what it needs and who can act on a recommendation. I bring that perspective to cost reviews and to the way improvements are delivered.
I can support a focused assessment, a defined improvement workstream or an ongoing consulting assignment. We agree responsibilities and expected outputs before starting.
Explore my wider experience →- Allocation and financial guardrailsIntroduced mandatory cost metadata, budgets, alerts and anomaly detection into cloud practices.
- Reporting that supports decisionsLed development of AWS QuickSight dashboards covering cost intelligence, showback, Azure reporting and commitment reviews.
- Recurring optimisation with ownersReviewed utilisation and supported cleanup of idle resources, detached storage and temporary environments, alongside sizing and backup reviews.
Examples from my employment at Convatec, January 2021–May 2026.
04 / How we work
A clear starting point. A practical path forward.
The FinOps cycle of Inform, Optimize and Operate provides a useful structure. We revisit these activities as your workloads and priorities change.
Understand the situation
Discuss your priorities, review available cost data and ownership, and identify reporting or process gaps. Agree the scope and establish a baseline.
Choose the next improvements
Assess opportunities with your team, weigh trade-offs and prioritise a realistic backlog. Document recommendations, responsibilities and next steps.
Make the practice repeatable
Establish review routines, measures and a handover so your teams can follow through, monitor progress and refine the approach.
A focused first engagement: a FinOps assessment with written findings, prioritised recommendations and an agreed roadmap. Scope, required inputs, deliverables and commercial terms are agreed before work starts. I lead the engagement personally; any additional specialists are agreed with you.
About the FinOps phases ↗05 / Common questions
Before we start.
Do we need an established FinOps team?
You can start with a focused problem: unclear cost ownership, limited reporting or a growing bill. I help identify the people who need to be involved and agree a manageable first scope.
What information is useful for an assessment?
Cost and usage reports, the account or subscription structure, tagging practices, current budgets and details of planned workload changes are useful starting points. We agree the necessary access and inputs during scoping.
How will we know the work is helping?
We agree measures against your starting position, such as allocation completeness, forecast variance, resolved optimisation actions or commitment utilisation. Financial outcomes depend on your environment and the changes your team implements.