FinOps is a cloud financial management discipline that brings engineering, finance, and business teams together around a single source of cost data, so that every dirham spent in the cloud produces measurable value. In practice, it is the craft of cutting your IT bill without cutting capability, by making consumption visible, optimized, and continuously governed.
Quick answer: to optimize IT costs without losing capability, first make spend visible (allocation by project and team), eliminate obvious waste (idle resources, oversized instances, dormant SaaS licenses), then move from on-demand consumption to negotiated commitments (Savings Plans, Reserved Instances, Spot). In Morocco, add two local levers: weighing sovereign cloud against currency exposure, and respecting Office des Changes limits on foreign-currency payments.
What is FinOps and why has IT cost optimization become a board-level priority in 2025-2026?
FinOps is not a one-off budget cut; it is an operating practice that places financial accountability at the heart of technical decisions. The FinOps Foundation's State of FinOps 2025 survey, covering organizations responsible for more than 69 billion dollars in cloud spend, ranks workload optimization and waste reduction as the top priority. The scope is also widening: more than 60 percent of practitioners now manage SaaS within their FinOps practice, and 63 percent include AI spend, double the previous year.
For a Moroccan executive, the stakes are twofold. On one side, regional growth is accelerating: Gartner forecasts MENA IT spending of 230.7 billion dollars in 2025 (up 7.4 percent), with data-center systems the fastest-growing segment (up 14.9 percent). On the other, without discipline that growth mechanically turns into waste. According to Gartner, an organization with no optimization plan can overspend on cloud by up to roughly 70 percent without realizing the value it expected.
How much is your enterprise actually wasting?
Most executives underestimate the share of their bill that produces no value. The available figures, which should be read as directional since many come from vendors, nonetheless converge: cloud waste has held at around 27 to 32 percent of total cloud spend since 2019 (Cast AI), implying on the order of 180 billion dollars wasted globally in 2025.
Harness's FinOps in Focus report projects roughly 44.5 billion dollars of enterprise cloud infrastructure spend wasted in 2025, about 21 percent of the total, on underutilized resources. The root cause is poor visibility: fewer than half of organizations have real-time visibility into idle resources (43 percent), orphaned resources (39 percent), or over/under-provisioned workloads (33 percent).
On the software side, the picture is even starker. According to Zylo's 2025 SaaS Management Index, 51 percent of enterprise SaaS licenses go unused, the highest waste rate ever recorded. By contrast, mature SaaS management programs keep that waste below 10 percent. The lever exists; it simply has to be pulled.
Where does IT waste hide: idle cloud resources, overprovisioning, over-licensing, and shadow IT?
Waste is almost never visible in the headline budget line. It hides in four specific pockets.
First, idle resources: servers running around the clock for workloads that only run a few hours, test environments never switched off at night or on weekends. According to Cast AI, idle compute (around 35 percent) and overprovisioned instances (around 25 percent) together account for nearly 60 percent of all cloud waste.
Next, overprovisioning: out of caution, teams provision two to three times the capacity actually consumed. It feels safe, but it is money locked up every month.
Then SaaS over-licensing: subscriptions sized for a headcount that has since changed, functional duplicates (two video tools, three project-management tools).
Finally, shadow IT: software purchased by business units with no visibility for the IT department. According to Zylo and CloudNuro, business units control up to 70 percent of SaaS spend and shadow IT represents over a third of all applications. That is precisely where the invisible bill is built.
How does the FinOps lifecycle (Inform, Optimize, Operate) and its six principles work?
The FinOps Foundation framework rests on three iterative, non-linear phases. Inform makes spend visible: allocation by team, project, and cost center, with shared reporting. You cannot optimize what you cannot measure. Optimize identifies then acts on savings opportunities: rightsizing, removing the unnecessary, negotiated commitments. Operate installs continuous governance: spend is no longer audited once a year, it is steered every week.
Microsoft Learn documents the same lifecycle and usefully sums up cloud cost as cost = usage x rate. You therefore act on two fronts: usage optimization (rightsizing, eliminating idle resources) and rate optimization (commitment-based discounts).
The FinOps Foundation's six principles revolve around one central idea: shared accountability. Engineering, finance, and business decide together, on data rather than intuition. It is that cultural shift, more than any tool, that makes the savings last.
What are the practical levers to cut cloud spend without cutting capability?
A mature FinOps practice can cut a cloud bill by 20 to 50 percent depending on maturity (a directional figure from French FinOps practitioners). Here are the main levers and their orders of magnitude, to validate against your own context.
| Lever | Mechanism | Indicative saving | |---|---|---| | Rightsizing | Match instance size to real usage | Variable, removes overprovisioning | | Decommissioning idle | Switch off/delete dormant resources and environments | Recovers a large share of the ~60% waste | | Spot Instances | Spare capacity for interruption-tolerant workloads | Up to ~90% vs on-demand (CloudZero) | | Standard RI / EC2 Savings Plans | Commit to a usage type | Up to ~72% vs on-demand (CloudZero) | | Compute Savings Plans / Convertible RIs | More flexible commitment | Up to ~66% vs on-demand (CloudZero) | | 1-year vs 3-year commitment | Commitment duration | ~40% (1 year) vs ~60% (3 years) (CloudZero) | | SaaS license reclaim | Recover unused licenses | Move waste from 51% toward under 10% (Zylo) |
The right reflex: optimize usage before you commit. There is no point reserving three years of capacity you could first halve through rightsizing.
Rightsizing, Reserved Instances, Savings Plans or Spot: which commitment lever should you choose?
The choice depends on how predictable your workload is and how much interruption you can tolerate.
For a stable, predictable workload (a production ERP or database), long commitments are unbeatable: according to CloudZero, a three-year commitment yields around 60 percent off versus roughly 40 percent at one year. Standard Reserved Instances and EC2 Savings Plans can reach up to 72 percent off on-demand, but they tie you to a usage type. Compute Savings Plans and Convertible RIs offer up to 66 percent, with more flexibility if your architecture evolves.
For an interruption-tolerant workload (batch processing, compute, testing, rendering), Spot Instances go up to 90 percent off. The trade-off: that capacity can be reclaimed at any time.
The practical rule for the Moroccan market, where few SMEs have an in-house FinOps function: start with rightsizing (immediate gain, no commitment), then cover your stable baseline with one-year Savings Plans, and reserve Spot for non-critical workloads. To structure this, our digital consulting service frames the trade-offs before any contractual commitment.
How do you regain control of SaaS licenses and shadow IT?
Reclaiming SaaS is often the highest-return lever, because it degrades no technical capability. The first step is the inventory: list every application actually in use, including those bought outside IT. Bank statements and expense reports usually surface forgotten subscriptions.
Next comes rationalization: eliminate functional duplicates, negotiate by volume rather than license by license, and run a quarterly review of inactive accounts. Recall the gap: 51 percent of licenses unused in unmanaged environments versus under 10 percent in mature programs (Zylo). That is where the saving sits.
Finally, governance: a clear purchasing process for business units does not kill agility, it channels it. The goal is not to ban shadow IT but to make it visible, because an invisible application cannot be secured, optimized, or brought into CNDP compliance.
What does a step-by-step IT cost optimization checklist look like?
Here is a pragmatic sequence you can apply quarter by quarter.
- Allocate: tag every cloud resource by team, project, and cost center (Inform phase).
- Switch off: schedule automatic shutdown of test environments outside business hours.
- Rightsize: adjust instances and databases to actual usage observed over 30 days.
- Decommission: remove orphaned resources, unattached volumes, expired backups.
- Inventory SaaS: cross-check paid licenses against real usage, remove dormant accounts.
- Commit: cover the stable baseline with Savings Plans, shift batch workloads to Spot.
- Govern: establish a monthly cost review bringing together IT, finance, and business.
- Measure: track unit cost (cost per customer, per transaction) rather than the total alone.
This discipline mirrors the methodical logic of a structured firm; we detail it in our guide on how to choose an IT consulting firm in Morocco.
Cloud FinOps in Morocco: how the missing hyperscaler region and Office des Changes rules shape your cloud bill?
This is where IT cost optimization takes on a distinctly Moroccan character. As of 2025, no hyperscaler (AWS, Azure, Google Cloud) operates a full data-center region in Morocco: the nearest regions are in Europe (Paris, Marseille, Madrid), and AWS only launched a Casablanca Wavelength Zone in January 2025. As a result, most enterprise cloud is billed in dollars or euros from Europe, adding currency risk and a latency cost on top of list price.
On top of that comes a regulatory dimension: foreign-currency payments to overseas providers (cloud and SaaS included) fall under Office des Changes rules, whose General Instruction on Exchange Operations is being updated for 2026. Depending on your entity's exchange status (whether it holds a foreign-currency or convertible-dirham account), card payments abroad may be subject to annual allowances. Confirm your situation with your bank, because cloud billed in foreign currency and left ungoverned is no longer just a budget problem: it can become a treasury and compliance one.
Sovereign cloud, CNDP, and currency exposure: how should enterprises in Morocco optimize cloud cost?
The most powerful trade-off for a Moroccan enterprise combines cost control with compliance. Local operators (inwi data center, N+ONE, Maroc Telecom, CDG-backed players, and Atlas Cloud Services with IBM watsonx) now offer Tier III/IV certified infrastructure, competitive with European AWS or Azure, and billed in dirhams.
Repatriating part of the workload onto sovereign infrastructure therefore produces a triple effect: reduced currency exposure, compliance with Office des Changes rules, and CNDP compliance (Law 09-08) for sensitive data (customer, HR, accounting) that benefits from staying resident in Morocco.
The winning strategy is not binary. Keep high-value managed services and low-sensitivity workloads with a hyperscaler, in European residency documented with the CNDP; shift regulated data and predictable, MAD-billable workloads to sovereign infrastructure. In an economy made up of roughly 95 percent SMEs (HCP) that often have no CIO, this trade-off fully justifies external support, especially in the context of Maroc Digital 2030's acceleration.
How do you govern IT costs sustainably with ITIL 4 and COBIT 2019?
One-off savings erode; only governance makes them durable. That is Gartner's consistent message: without an optimization plan, overspend can reach roughly 70 percent. Two recognized frameworks structure this governance.
ITIL 4 covers IT financial management with explicit goals: reduce cost, improve efficiency, and bring clarity to decision-makers. COBIT 2019, with its 40 governance and management objectives, aims to optimize resources and the value of IT investments. These are the same frameworks ClaroDigi draws on in its consulting methodology, which gives FinOps a governance foundation rather than leaving it a purely technical optimization exercise.
In practice, FinOps provides the data and the levers; ITIL 4 and COBIT 2019 provide the decision framework that turns a one-time cut into a permanent discipline.
What mistakes should you avoid, and how does ClaroDigi support enterprise IT cost optimization in Morocco?
The most common mistake is to cut first and think later: freezing projects or deleting critical environments degrades capability without installing any discipline. The second mistake is treating optimization as an annual event rather than a routine. The third, specific to Morocco, is ignoring the currency and compliance dimension until the day an Office des Changes rule blocks a payment.
At ClaroDigi, we install the FinOps practice end to end: visibility and allocation, waste reduction, hyperscaler-versus-sovereign trade-offs, and ITIL 4 / COBIT 2019 governance, all quantified in dirhams and aligned with local regulation.
Sources
- FinOps Foundation, State of FinOps 2025: https://data.finops.org/2025-report/
- FinOps Foundation, Framework Phases: https://www.finops.org/framework/phases/
- Microsoft Learn, FinOps Framework overview: https://learn.microsoft.com/en-us/cloud-computing/finops/framework/finops-framework
- Cast AI, Cloud Waste Problem: https://cast.ai/blog/the-cloud-waste-problem-how-to-stop-overprovisioning-resources/
- Harness, FinOps in Focus (PR Newswire): https://www.prnewswire.com/news-releases/44-5-billion-in-infrastructure-cloud-waste-projected-for-2025-due-to-finops-and-developer-disconnect-finds-finops-in-focus-report-from-harness-302385580.html
- Zylo, 2025 SaaS Management Index: https://zylo.com/news/2025-saas-management-index
- CloudZero, Savings Plans vs Reserved Instances: https://www.cloudzero.com/blog/savings-plans-vs-reserved-instances/
- Gartner, MENA IT spending 2025: https://www.gartner.com/en/newsroom/press-releases/2024-11-20-gartner-forecasts-mena-it-spending-to-grow-7-percent-in-2025
- Office des Changes, IGOC 2026 (Industrie du Maroc): https://industries.ma/office-des-changes-nouvelles-regles-plafonds-releves-et-facilites-inedites-a-partir-de-2026/
- ISACA, ITIL 4 and COBIT 2019: https://www.isaca.org/resources/white-papers/using-itil-4-and-cobit-2019-to-create-an-integrated-i-and-t-framework-environment
FAQ
What is FinOps in simple terms? FinOps is a discipline that gives engineering, finance, and business teams a shared, real-time view of cloud spend so they can make cost-aware decisions together. It runs on a three-phase lifecycle, Inform, Optimize, Operate, and its goal is to maximize the business value of every cloud dirham rather than simply spending less.
How much can a company realistically save with FinOps? A mature FinOps practice can cut a cloud bill by 20 to 50 percent depending on maturity, according to French FinOps practitioners. The savings come from rightsizing, decommissioning idle resources, reclaiming unused SaaS licenses, and shifting from on-demand to committed capacity such as Savings Plans and Reserved Instances.
Where is most cloud waste hidden? Mostly in idle and oversized resources. According to Cast AI, idle compute (about 35 percent) and overprovisioned instances (about 25 percent) make up nearly 60 percent of all cloud waste. On the software side, Zylo reports 51 percent of enterprise SaaS licenses go unused, often through shadow IT bought outside the IT department.
How does the Office des Changes affect cloud spending in Morocco? Foreign-currency payments to overseas cloud and SaaS providers fall under Office des Changes rules (the IGOC, updated for 2026). Depending on whether your entity holds a foreign-currency or convertible-dirham account, card payments abroad may be subject to annual allowances, so confirm your situation with your bank. Uncontrolled foreign-billed sprawl can become a treasury and compliance issue, not just a budget one.
Should a Moroccan enterprise use sovereign cloud or a hyperscaler? Both, deliberately. Keep high-value managed services and low-sensitivity workloads with a hyperscaler in European residency documented with the CNDP, and shift regulated data and predictable, MAD-billable workloads to certified local operators. This balances cost, latency, currency exposure, and Law 09-08 compliance.
Last verified: 17 June 2026.
Is your cloud bill growing faster than the value it produces? At ClaroDigi, we install a FinOps practice tailored to the Moroccan context: visibility, waste reduction, sovereign trade-offs, and durable governance, all quantified in dirhams. Let's talk about your IT optimization →