Optimize: the four levers you have

Outcome

By the end of this lesson, you will be able to name the four levers of cloud cost optimization and rank them by typical impact and time-to-value.

1. Concept

Optimize is the second phase. There are exactly four ways to spend less, and every cost programme is some mix of them.

The order you pull them in matters more than which ones you pull. Do them in the wrong order and the early wins cancel the later ones out.

LEVER                  IMPACT (typical)   TIME-TO-VALUE   RISK
─────────────────────────────────────────────────────────────────
1. Eliminate waste     20-40% of bill     Days-weeks       Low
2. Rightsize           10-30% of bill     Weeks            Medium
3. Rate optimize       5-25% of bill      Weeks-months    Medium-High
4. Architect / design  varies (5-50%+)    Quarters         High

Lever 1: Eliminate waste

Stop paying for things nobody is using. Turn off test environments at night. Delete disks that outlived their servers. Clear snapshots nobody will restore. Release reserved addresses nothing points at. This is the list from M0.1 L5.

Why first: it is the lowest risk and the fastest to pay back, and nobody has to agree on a redesign. Turning off a development environment overnight changes nothing about how the system works, and the saving lands on the next bill.

When to stop: once avoidable spend is under 5 to 8 percent of the bill. Below that, what is left is in how the system is built rather than in how it is run, which is lever four.

Lever 2: Rightsize

Run things at the size they actually need. Drop an oversized machine a class or two. Move a database down a tier when its CPU and connection counts stay low. Switch disks from the older gp2 type to gp3, which performs the same and costs less. Lower the resources reserved by Kubernetes workloads that never use them.

Why second: it takes more judgement than deleting waste, but it is still mostly mechanical. A rules engine can produce the candidate list for you. What it cannot decide is how much risk the workload can take.

Where it gets hard: databases, which cannot be resized automatically and need a maintenance window, and anything with spiky traffic, where the size is set by the worst few minutes rather than by the average.

Lever 3: Rate optimize

Pay a lower price for the same thing. This is where commitments live: you promise the provider a year or three of usage and they charge you less per hour. Every provider has its own name for it. There is also interruptible capacity, sold cheap because the provider can reclaim it, and there are negotiated discounts for large accounts.

Why third rather than first: a commitment only pays back on usage you genuinely keep for the whole term. Committing to capacity and then switching it off at night destroys value twice over: you pay for the commitment and lose the saving.

The order is: turn off what you do not need, resize what is left, then commit to the floor that remains.

Where it gets dangerous: committing too much. A one-year commitment on capacity you run for six months loses money outright, and a three-year commitment on the wrong machine family locks the mistake in.

Lever 4: Architect / design

Change the workload to cost less. Replace a 24/7 service with a serverless equivalent that scales to zero. Move an analytics pipeline from EMR to Athena. Re-implement a real-time feature as event-driven. Decompose a monolith so non-critical paths can run on cheaper compute.

Why last: highest impact ceiling, highest risk, longest time-to-value. An architectural change touches code, deployment, on-call, SLOs. The ROI calculation must account for engineering time.

Where it shines: the steady-state floor cost after levers 1-3 have been applied. If you are still spending $200K per month on a workload that could be re-architected to $80K, the prize is there. But sequence it after the easy wins.

The lever ranking is not opinion

   IMPACT ─→
   ┌──────────────────────────────────────────────────────┐
   │ 4 ARCHITECT/DESIGN          (highest ceiling, slowest)│
   │ 3 RATE OPTIMIZE             (mid impact, medium speed)│
   │ 2 RIGHTSIZE                 (mid impact, fast)        │
   │ 1 ELIMINATE WASTE           (consistent, fastest)     │
   └──────────────────────────────────────────────────────┘
   TIME-TO-VALUE →

The diagonal: lever 1 is in the bottom-left (fast, modest), lever 4 is in the top-right (slow, biggest). Most teams should travel up-and-right diagonally over 12 months, not jump straight to lever 4.

The most common sequencing mistake

Buying reservations before scheduling. The reservation locks in capacity you intend to schedule down, destroying the savings on both sides. The fix is mechanical: schedule first, observe the resulting steady-state floor for 60 days, then commit on the floor only.

Where ZopNight focuses

Lever 1 (scheduling) and lever 2 (rightsizing recommendations + autoscaling) are first-class. Lever 3 (commitments) is on the roadmap. Lever 4 (architecture) is out of scope; that is application engineering work, not platform automation.

2. Demo

A real (anonymized) optimization sequence at a mid-size SaaS, applied over 6 months:

Cumulative monthly savings by month 6: $43,494. Total project effort: ~140 engineering hours. Effective rate: $310 saved per engineering hour.

3. Hands-on (8 min)

For your own estate, score yourself on each lever:

LEVER 1: Eliminate waste
[ ] Are non-prod resources scheduled off after hours?
[ ] Is the avoidable-spend KPI below 8% of bill?

LEVER 2: Rightsize
[ ] Are rightsizing recommendations reviewed weekly?
[ ] What's the average gap between "recommendation surfaced" and "remediated"?

LEVER 3: Rate optimize
[ ] What's the current commitment coverage (RI + SP + CUD)?
[ ] Was the most recent commitment purchased on the post-schedule floor?

LEVER 4: Architect/design
[ ] Are there any workloads in active redesign for cost reasons?
[ ] Is engineering time being tracked against cost-driven redesigns?

If lever 1 is incomplete, do not move to levers 2-3. The sequence is not “do all four in parallel.” It is “do 1 first, then 1+2, then 1+2+3, then all four.”

4. Knowledge check

Q1

A team has $200K monthly cloud spend, mostly non-prod always-on, and wants to start optimizing. The first move is:

A. Schedule non-prod off-hours and weekends
B. Buy a 3-year Reserved Instance pool to lock in savings
C. Migrate to Kubernetes
D. Hire a FinOps consultant

Q2

A FinOps team reports: “We applied 30 rightsizing recommendations this month and saved $4,100. We applied 1 schedule and saved $24,000.” Which lever has more headroom to keep finding savings?

A. Lever 2 (rightsizing)
B. Both equally
C. Lever 3 (commitments)
D. Lever 1 (scheduling)

Q3

A CFO proposes locking in a 3-year RI on the current peak compute usage to “guarantee savings.” Best response:

A. Agree, locking in is good
B. Wait one year
C. Push back
D. Use Spot instead

5. Apply

ZopNight is built around levers 1 and 2 because that is where the fast, repeatable savings live for most estates:

• Lever 1 → Schedules (any time you can stop a resource), Recommendations idle/orphan rules
• Lever 2 → Recommendations rightsizing/category rules, VM Autoscaling
• Lever 3 → coverage tracked in Reports → Purchase Type breakdown
• Lever 4 → out of scope; engineering ownership

Related lessons

• L4: Operate: the discipline that beats one-shot wins (next)
• M0.3: Why scheduling beats commitments
• T4.M4.7: Commitments demystified

Glossary terms touched

Optimize · Eliminate waste · Rightsize · Rate optimize · Architect-design lever