In the Software-as-a-Service (SaaS) Scope, the challenges of managing public cloud spending are mirrored in the proliferation of SaaS resources across organizations via decentralized, individual-level procurement and corporate-credit-card-funded purchase orders, resulting in limited organizational visibility into cost and usage. Pricing models vary from license-based SaaS, to variable-spend models such as per user/device, tiered, consumption-based, flat rate, and feature add-ons. By iteratively applying Framework Capabilities, financial transparency and accountability can be established for SaaS spending alongside public cloud spending.
The highlighted Framework elements represent a sample of how to choose the Personas, Domains, and Capabilities that may apply in this FinOps Scope. Greyed areas remain part of the Framework and could be building blocks that are also included in this FinOps Scope depending your FinOps Maturity and situational context.
A FinOps Scope is a segment of technology-related spending to which FinOps Practitioners apply FinOps concepts. Business and technology strategy drives the context that determines which Personas, Domains, Capabilities, KPIs, datasources, and metric thresholds included in the FinOps practice profile.