When the Cloud Savings Stop
Your company tagged everything, shrank the oversized servers, and bought reserved capacity. It found real money.
Then the savings stopped, and the bill kept climbing.
Thursday, November 19, 10am Pacific · 30 minutes · Free on LinkedIn Live
Registration opens soon on LinkedIn. Check back here for the link.
Below the floor
Every team that runs the finance playbook hits a floor. Above it was waste. Below it is something else.
Everything below the floor was set by design decisions. How many services you run. Where your data moves. How fast you need to recover.
In this session you'll see:
- Why tagging, rightsizing and commitments all stop at the same place
- How to read your cloud bill backwards, from a line item to the decision that caused it
- What one small system costs at each recovery target, from $413 to $1,270 a month
- Where finance's job ends and yours begins
- Three things you can do Monday
Who it's for: Architects, senior engineers and engineering leaders who own a cloud cost target.
About your instructor
Lee Atchison spent seven years at Amazon and AWS and eight at New Relic, building and running systems at scale. He wrote Architecting for Scale (O'Reilly), and more than 180,000 learners have taken his courses.
Go deeper: Architecting for Cost
The webinar comes from my course, Architecting for Cost. It works through the decisions that drive the bill, one at a time: multi-tenancy, data movement, recovery targets and AI inference. And it ends with how to make the cost case to the people who fund the fix.
8 modules, 33 short video lessons, and 8 worksheets and templates you use on your own systems.
$495 (regularly $695)
Launch price ends Sunday, November 22, at midnight Pacific.
Get the launch price30-day refund, no questions asked.
Start with your own bill
Not ready for the course? Start with the exercise from the webinar.
The free Cost Attribution Worksheet walks you through your top five cloud costs, and the decision behind each one. Two out of five is a normal answer.
Have a question?
Ask me. I'll get back to you.