Scopes and Technology Categories
FinOps scopes
Scope defines where FinOps applies. Common scopes include public cloud, SaaS, data center, and licensing (on-premises or enterprise software). Public cloud is the most familiar, but the same visibility, allocation, optimization, and accountability loop applies to SaaS subscriptions and renewals, data center power, space, hardware depreciation, and software licenses. Each scope has different data sources, owners, and commercial levers.
Technology categories
Within a scope, technology categories organize spend by workload type: compute, storage, networking, databases, analytics, containers and serverless, and AI/ML, among others. Category matters because optimization levers differ. Compute often uses rightsizing and commitments; storage uses tiering and lifecycle policies; networking requires attention to egress and data transfer; databases use instance sizing and reserved capacity; SaaS uses seat management and renewal negotiation.
Traps
A frequent trap is assuming FinOps equals public cloud only. Another is treating SaaS as untouchable because it is owned by a business unit, or ignoring data center costs such as power and depreciation. Questions may describe a scope by its commercial model rather than its location. Also, a technology category is not a vendor or a service name.
Worked example / rule of thumb
A SaaS renewal should follow the same loop: ingest invoice and usage data, allocate seats to teams, identify unused licenses, forecast need, and negotiate. Rule of thumb: scope determines the data source and owner; technology category determines the optimization lever. Identify both before choosing a metric or action.