From AWS build to FinOps practice for a hospitality group

Cloudreason designed and built the client’s AWS infrastructure six years ago and has supported it ever since: first as the engineering partner behind the build, and now running the FinOps practice across the estate.

The problem

For a business whose core operation is hospitality rather than infrastructure, cloud presents a staffing dilemma that never quite resolves. The estate is too important to neglect, because bookings, operations and customer-facing services depend on it, but too small to justify a dedicated cloud team. Senior cloud engineers are expensive to hire, hard to retain when the work is steady-state rather than greenfield, and mostly unnecessary day to day. Yet the moments when you need that expertise (an architectural decision, a commitment renewal, an incident) arrive regardless of whether you’ve hired for them.

The usual answers each have a cost. A managed service provider will run the estate, but MSPs typically price as a percentage of the spend they manage, an incentive that points away from shrinking it. Doing without means the estate is governed by whoever has spare time, which in practice means it isn’t: sizing decisions ossify, commitments lapse or renew on autopilot, and spend creeps upward a few percent at a time, invisible in any single month.

What we did

The engagement covers cost governance, reservation management and ongoing technical guidance, with Cloudreason available to the client’s team as required: the practical shape of a FinOps practice for an organisation of this size.

Cost governance means changes to the estate are assessed for their cost impact before they’re made rather than discovered on an invoice afterwards, and that the numbers are reviewed on a regular rhythm with someone accountable for them. Reservation management means the estate’s commitments are kept continuously matched to what actually runs: bought when the workload has earned them, resized when it changes, never left to expire unnoticed. And because AWS commitment instruments discount steeply against on-demand rates, keeping that coverage current is one of the most reliable savings levers a steady-state estate has.

The technical guidance is the part that came from building the platform in the first place. Because Cloudreason designed the infrastructure, cost efficiency was designed in from the start rather than retrofitted later, and six years of continuity mean every recommendation is made with full knowledge of why the estate is shaped the way it is. There is no annual re-discovery exercise, no consultant learning the environment on the client’s time.

The results

Six years on, the infrastructure Cloudreason built is still the infrastructure running the business, and its cost has been actively governed for the whole of its life, through changes in the business, the workloads and AWS’s own pricing landscape.

The client gets what a much larger organisation would build internally, an accountable FinOps function with senior engineering behind it, at a scale and cost proportionate to the estate it manages. Building the infrastructure and then owning its cost efficiency closes the usual gap between the people whose decisions drive spend and the people accountable for the bill. Here, they are the same people.