A team says they 'do FinOps' because they run Cost Explorer and Compute Optimizer. What does the FinOps framework say they're actually missing?

An engineer proposes a tagging-and-rightsizing project that will take two sprints and is forecast to save a few hundred dollars a month. By what test do you decide whether to greenlight it?

You enable AWS vCPU Optimization on an 8-vCPU instance so SAP only licenses 6 vCPUs. What happens to your EC2 bill?

On-premise SAP IT spend had a natural ceiling. Why does moving to AWS — even with up-to-50% savings potential — tend to make costs snowball instead?

You want an AWS Budget that alerts only on SAP spend, not the whole account. Which template do you pick and what scope do you set — and why won't a standard template do?

How does Cost Explorer's Cost Anomaly Detection decide what to alert on, and how is the trigger different from an AWS Budgets alert?

A team kicking off FinOps wants the fastest dollar win, so they jump straight to right-sizing SAP and buying Compute Savings Plans (the Optimization pillar). Why will that effort largely miss its target until they do something else first?