Tag resources, build cost reports and show spend per team.
A SaaS company cannot see which team spends what.
The detailed steps, checklists and trainer review open in the SOTT student portal for enrolled students.
SaaS: Cloud bill under control. The cloud bill grew 40 percent in a year and nobody knew why. Tagging, showback per team, rightsizing and commitments. Spend dropped while usage grew.
Retail: Paying for idle test environments. Test servers ran all weekend. Schedules to stop idle resources and budget alerts. Non-production costs fell sharply.
Fintech: Unit costs. Leaders could not see cost per customer. Cost per transaction dashboards from tagged spend. Pricing decisions now use real unit costs.
Yes. Once your trainer approves it, list it under Projects with the tools you used, one line on the problem it solves and a link to your repository and demo video.
About 6 hours of hands-on work, and it fits best after week 2 of the FinOps: Cloud Cost Management course.
Enrolled students get every task with steps, "done when" checks, the submission form and a trainer review in the SOTT student portal.