{"id":3072,"date":"2026-11-17T02:20:00","date_gmt":"2026-11-17T02:20:00","guid":{"rendered":"https:\/\/www.surgeryplanet.com\/blog\/?p=3072"},"modified":"2026-11-20T02:20:00","modified_gmt":"2026-11-20T02:20:00","slug":"41-79-finops-explained-travel-software-team","status":"publish","type":"post","link":"https:\/\/www.surgeryplanet.com\/blog\/41-79-finops-explained-travel-software-team\/","title":{"rendered":"FinOps Explained Through One Medical Travel Website Invoice"},"content":{"rendered":"<p>Picture a small team behind a website that helps people compare surgical travel options across borders. They do not provide care; they build the software that organises enquiries, documents and itineraries. Late one Thursday, the person who looks after the servers notices that the monthly cloud charge has nearly doubled, while enquiries are only up a little. Nobody can explain it, and the finance contact, who has been patient for months, finally asks a fair question: what are we paying for? This explainer follows that team as they discover FinOps, in plain language and without jargon. Everything here is about technology costs, an invented scenario meant to illustrate ideas, and not about any medical subject.<\/p>\n<h2>What FinOps means, in everyday words<\/h2>\n<p>The word joins &#8220;finance&#8221; with the culture of building and running software. It is the habit of letting the people who build the system, the people who watch the money and the people who own the product look at the same cost figures and decide together. <a href=\"https:\/\/www.xopsschool.com\/finops\/\">The Ops Atlas page on FinOps<\/a> stresses that this is a way of working across roles, not a piece of software, and that its subject is technology spending which changes with use, such as cloud servers, storage and data transfer.<\/p>\n<p>The team&#8217;s server person had always assumed the bill was something that simply arrived. The notion that it was a shared conversation with a rhythm was new, and rather welcome.<\/p>\n<h2>Three small equations that tell the story<\/h2>\n<p>The Atlas boils the subject down to three sentences you can write on a napkin.<\/p>\n<ul>\n<li><strong>Cost equals usage times rate.<\/strong> If the charge doubled, either they used more or each unit became pricier.<\/li>\n<li><strong>Value equals outcome divided by cost.<\/strong> A higher bill might be fine if the outcome, say completed enquiries, grew faster.<\/li>\n<li><strong>Accountability is data multiplied by decision rights and by cadence.<\/strong> Drop any factor and the product is zero: figures with nobody authorised to act are decoration, and authority with no figures is guesswork.<\/li>\n<\/ul>\n<p>The team sat down with the invoice and applied the first equation. Usage had not doubled, but one item had become a large share of the total: a process that resized every uploaded document image several times and stored every copy. Usage of storage and processing had quietly ballooned. They had their answer in an hour, which would have been impossible without splitting the number into parts.<\/p>\n<h2>Why the second equation protects you from silly cuts<\/h2>\n<p>The finance contact&#8217;s first instinct was to ask for a thirty percent reduction across the board. The server person gently pointed to the second equation. If they cut capacity indiscriminately, the enquiry pages might slow, and the number of completed enquiries, the outcome that matters, would fall faster than the bill. The Atlas calls the practice a form of value management and quotes the Foundation&#8217;s wry advice that anyone who equates it with thrift ought to reconsider.<\/p>\n<p>That one conversation changed the meeting. Instead of &#8220;cut everything&#8221;, the agreed task became &#8220;stop paying for copies we never use&#8221;.<\/p>\n<h2>Who actually decides things?<\/h2>\n<p>The Atlas names six core roles: the practitioner who coordinates, engineering, finance, product, procurement and leadership. In the little team they were few people wearing several hats, yet the idea held. The engineer decided about the image process, the product owner decided how many image sizes the site truly needed, and the finance contact decided how the saving would show up in next quarter&#8217;s plan.<\/p>\n<h2>A lesson from big moves: paying twice for a while<\/h2>\n<p>Later that year the team planned to move from one hosting set-up to another. The Atlas describes an illustrative eighteen-month datacentre migration, a composite and not a real case, in which the organisation pays for the old and new environments at the same time during the move. This dual-running period makes costs rise before they fall. The lesson for a small team is simple: when you plan a move, put the overlap in the budget and name the date on which the old system will be switched off, or the overlap will quietly become permanent.<\/p>\n<h2>Forecasts that learn from launches<\/h2>\n<p>When the team promoted a new country page, traffic jumped for a fortnight. A forecast built only on last year&#8217;s line would not have predicted that. The Atlas cautions that simple trend forecasting misses launches and campaigns, and it describes a ladder of maturity that ends with driver-based forecasts, where known business events adjust the line. The team started writing down every planned promotion in a shared sheet, then asked the engineer what each one would do to the servers.<\/p>\n<p>They also set aside a small holdback in the budget. The Atlas suggests sizing such a reserve roughly to the error you have seen in past forecasts, which is a gentle way to admit nobody predicts perfectly.<\/p>\n<h2>The rhythm that made it stick<\/h2>\n<p>The team adopted three habits. A short look at the cost chart each morning. A weekly fifteen-minute chat between the server person and the product owner. A monthly review with finance, in which they compared actual with plan and explained differences in terms of volume, rate and scope. The Atlas treats this price-and-volume style of explanation as standard variance analysis. Over a few months the surprises got smaller and the conversations got shorter.<\/p>\n<h2>Why tags are helpful but not the whole answer<\/h2>\n<p>One evening the team labelled every server and storage bucket with the name of the feature it served: enquiries, documents, itineraries. It felt tidy, and the monthly chart finally showed colours instead of a grey block. Yet a stubborn slice remained unlabelled. Support fees, taxes and the shared database that all features used could not be pinned on a single label. The Atlas says plainly that tags alone do not settle allocation, and recommends a separate plan for shared charges.<\/p>\n<p>The team&#8217;s plan was modest. Split the shared database by the number of requests each feature made, publish the rule on a single page, and review it every six months. Nobody loved the rule, which is usually a sign it was reasonably fair.<\/p>\n<h2>Small wins worth celebrating<\/h2>\n<p>Three months in, the team could point to a short list of results they could show to anyone who asked.<\/p>\n<ol>\n<li>They knew what share of the bill belonged to each feature and what share was shared.<\/li>\n<li>They had removed the redundant image copies and written down why.<\/li>\n<li>They could explain any monthly change using usage, rate and scope.<\/li>\n<li>They had a calendar of launches feeding the forecast.<\/li>\n<li>They had a dated plan for retiring the old environment after the move.<\/li>\n<\/ol>\n<p>None of these needed a special platform. A spreadsheet, a calendar and a bit of courage were enough to begin.<\/p>\n<h2>What to try this week<\/h2>\n<p>If your own organisation builds travel or healthcare-adjacent software, borrow the team&#8217;s first step. Take last month&#8217;s invoice and divide the change into usage and rate. Ask the person who owns the largest line what drove it. Write down the answer, even if it is &#8220;no idea&#8221;. An honest unknown is the beginning of an owner and a date, and those two things are what turn a mystery on a bill into a decision somebody can make.<\/p>\n<h2>More from our archive<\/h2>\n<p>Should you wonder how cost work relates to other operational disciplines, our overview of <a href=\"https:\/\/www.surgeryplanet.com\/blog\/understanding-xops-the-modern-framework-for-connected-it-operations-learning-paths-and-tools\/\">the connected framework for IT operations, learning paths and tools<\/a> is a gentle starting point, and the article on <a href=\"https:\/\/www.surgeryplanet.com\/blog\/transforming-cloud-operations-for-enterprise-growth\/\">how cloud operations change as enterprises grow<\/a> adds more context.<\/p>\n<p>The story ends where it began, with an invoice. The difference is that the team can now read it like a sentence: this much usage, at this rate, producing this outcome, owned by these people, reviewed on this day. That is all the discipline asks, and it fits comfortably on a napkin.<\/p>\n","protected":false},"excerpt":{"rendered":"<p>A plain-language story about a small team behind a medical-travel website who learn to read their cloud invoice using three simple equations.<\/p>\n","protected":false},"author":13,"featured_media":3073,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[1582],"tags":[],"class_list":["post-3072","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-medical-tourism-tech"],"_links":{"self":[{"href":"https:\/\/www.surgeryplanet.com\/blog\/wp-json\/wp\/v2\/posts\/3072","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.surgeryplanet.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.surgeryplanet.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.surgeryplanet.com\/blog\/wp-json\/wp\/v2\/users\/13"}],"replies":[{"embeddable":true,"href":"https:\/\/www.surgeryplanet.com\/blog\/wp-json\/wp\/v2\/comments?post=3072"}],"version-history":[{"count":1,"href":"https:\/\/www.surgeryplanet.com\/blog\/wp-json\/wp\/v2\/posts\/3072\/revisions"}],"predecessor-version":[{"id":3198,"href":"https:\/\/www.surgeryplanet.com\/blog\/wp-json\/wp\/v2\/posts\/3072\/revisions\/3198"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/www.surgeryplanet.com\/blog\/wp-json\/wp\/v2\/media\/3073"}],"wp:attachment":[{"href":"https:\/\/www.surgeryplanet.com\/blog\/wp-json\/wp\/v2\/media?parent=3072"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.surgeryplanet.com\/blog\/wp-json\/wp\/v2\/categories?post=3072"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.surgeryplanet.com\/blog\/wp-json\/wp\/v2\/tags?post=3072"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}