Product
End-to-end use cases
Four real workflows that show how CCO fits into your daily operations.
1. New client onboarding (MSP)#
A new client signs their MSP contract. You need their cloud costs visible in your dashboard within the hour.
1
Connect the Azure tenant
Settings → Cloud Accounts → Connect Account. Enter the client's tenant ID and Service Principal credentials. CCO auto-discovers all subscriptions.
2
Create a data scope group
Create a group scoped to the client's subscriptions. Assign the client's analyst users so they only see their own data.
3
Set up budgets
Analytics → Budget Section. Create monthly budgets per subscription with warning (80%) and critical (100%) thresholds.
4
Generate the first report
Reports → Create Report. Select the client's subscriptions, choose Full Report, and email it to stakeholders.
Tip
White-label branding means the client sees your company's logo and name — not "Cloud Cost Optimizer" — on every page, email, and report.
2. Monthly FinOps review#
It's the first Monday of the month. Time to review last month's cloud spend, act on recommendations, and report savings to leadership.
1
Open Analytics
Review the cross-subscription cost overview. Drill into any subscription that shows a spike.
2
Review recommendations
Recommendations page shows idle resources, right-sizing opportunities, and reserved instance suggestions. Click Generate to refresh.
3
Resolve savings
For each recommendation you've acted on, click Resolve. This creates a permanent SavingsRecord that survives recommendation regeneration.
4
Generate and email the full report
Reports → Full Report (Last Month). The PDF includes alerts summary, budget status, and savings breakdown. Email to the VP of Engineering.
Tip
Cost Reconciliation re-checks archived closed months against the cloud and flags material drift from late charges, credits, and true-ups — so last month's numbers stay trustworthy after you've reported them.
3. Anomaly investigation#
At 2pm an alert lands in your inbox — and in Slack, Teams, or a webhook if you wired those up: a VM's cost tripled overnight.
1
Open the alert
Alerts page shows the triggered anomaly. The card displays baseline cost vs current cost with the deviation percentage.
2
Investigate in Cost Explorer
Click through to Cost Explorer. Group by resource, filter to the subscription. The daily breakdown shows exactly when costs spiked.
3
Fix the root cause
In this case, someone accidentally resized the VM to a premium tier. Downsize it back in the Azure portal.
4
Resolve the alert
Back in CCO, acknowledge the alert, then resolve it once costs normalize. The next 4-hour detection cycle confirms the fix.
4. Multi-cloud cost comparison#
Leadership wants to know: "Are we spending more on Azure or AWS this quarter?"
1
Open Cost Explorer
Group by Provider, set period to Last 3 Months, time breakdown to Monthly.
2
Drill into details
Click any provider bar to open Cost Trend for that provider. See the 12-month history with month-over-month percentage change.
3
Export and share
Export to Excel for the finance team. Or click Email to send the Excel report directly to stakeholders with a pre-filled subject line.