The project is finished. The invoice is lower. Six weeks later, someone asks for more licenses. What changed?

Bill Van Nort follows a fictional software service after its initial improvement has been verified. This episode separates legitimate growth, an outdated onboarding rule, and overdue temporary-access reviews, then shows how to preserve the result without blocking the service the business needs.

IN THIS EPISODE
• Keep purchased capacity, assignments and business requirements distinct.
• Check the process that creates new assignments as well as the current list.
• Set review triggers early enough to leave time for action.
• Treat missing evidence as unconfirmed.
• Reopen the decision when business needs change.
• Describe restored capacity without inventing another savings claim.

WATCH, LISTEN AND READ
https://www.operationalitam.com/pages/podcast-017-keep-the-result.html

PRACTICAL EXERCISE
Allow about an hour. Choose one completed technology change using authorized records. Record the verified outcome and date, a condition that could undermine it, the evidence that would reveal the change, its owner, the review trigger and the response deadline. Inspect a recent issue to see whether the cause was corrected and the result checked. If no example exists, mark the control untested.

CHAPTERS

• (00:00) - Keep the Result
• (00:53) - The Decision Table
• (02:22) - A fictional software service
• (02:33) - Verify the starting result
• (03:28) - Six weeks later
• (03:53) - Three causes, three responses
• (05:48) - Hand over the operating conditions
• (07:22) - Act before capacity runs out
• (08:41) - Roles and operating cadence
• (09:30) - Correct the assignment path
• (10:40) - Restored capacity, not new savings
• (12:08) - When the decision should change
• (13:20) - What an alert can see
• (14:13) - Ownership and authority
• (15:00) - Keep the review useful
• (16:03) - Beyond software: spare laptops
• (17:20) - A management update that supports action
• (18:51) - Your practical exercise
• (19:50) - Resources and closing
• (20:41) - Credits

Operational ITAM Podcast | Bill Van Nort | An EpicB Media LLC production.
https://www.operationalitam.com

An approved reduction is only the beginning. Bill Van Nort follows a fictional software subscription change from forecast through the signed agreement, implementation, invoices and a delayed credit. See why a $48,000 gross forecast becomes a $27,000 net calendar-year benefit—and how to explain every difference.

IN THIS EPISODE
• Agree the baseline, scope and reporting period.
• Distinguish assigned licenses from purchased commitments.
• Explain delayed implementation and retained capacity.
• Trace billing corrections to the affected service periods.
• Separate forecast, verified result and annualized run rate.
• Check that the service still meets the business requirement.

All case amounts are illustrative USD. The fictional supplier minimum and credit timing are not Microsoft or AWS terms. Finance determines your organization's recognition and accounting treatment.

YOUR NEXT STEP
Pick one completed technology change. Trace its estimate, agreed baseline, effective date, implemented quantity, invoices, credits and implementation costs. Explain material differences. State what is verified and what remains unresolved. Use records you are authorized to access and take the result to your finance partner.

WATCH, LISTEN & READ
https://www.operationalitam.com/pages/podcast-016-where-did-the-saving-go.html
Watch on YouTube: https://www.youtube.com/watch?v=WQgC5BoZD9g

PRACTICAL RESOURCE
F02 — Validate benefits and report business outcomes:
https://www.operationalitam.com/store/index.php?page=product&sku=F02
Bill's paid resource includes an editable procedure, flowchart and adoption/evidence checklist. Purchasing supports the show. The homework requires no purchase.

CHAPTERS

• (00:00) - Where did the saving go?
• (01:43) - The fictional subscription case
• (02:39) - Agree the baseline
• (04:53) - What the signed amendment changes
• (07:36) - Verify implementation
• (09:58) - Operational ITAM Store: F02
• (11:11) - Follow the invoices
• (12:51) - Keep the credit in the right period
• (14:06) - The verified annual result
• (15:38) - Annual result versus run rate
• (16:16) - Cloud commitments and utilization
• (18:11) - Keep the evidence traceable
• (18:43) - Your practical homework
• (20:12) - Closing

PRODUCTION
Written and hosted by Bill Van Nort. Voice production: ElevenLabs. Audio finishing: Adobe Audition. Production assistance: OpenAI Codex. Video assembly: FFmpeg. Show theme: Ten Second Pulse, created with Suno.

Operational ITAM covers practical IT asset management, software licensing, FinOps and evidence-led decisions. Website and resources: https://www.operationalitam.com/
An EpicB Media LLC production.

A renewal can pass through every department and still arrive at its deadline without a decision owner. Bill Van Nort works through a fictional customer-support renewal to show how ITAM, FinOps, procurement, finance, engineering, and the service owner can reach a defensible choice and verify what happens afterward.

The episode examines a lower-priced replacement, transition costs, a revised incumbent offer, and a delay scenario that reverses the cost ranking. Azure Hybrid Benefit and AWS Compute Savings Plans illustrate why licensing rights, consumption forecasts, and commercial commitments need a shared discussion.

The company, prices, and outcome in the central case are illustrative, not a client case study or savings benchmark.

Website and transcripts: https://www.operationalitam.com/ · Operational ITAM Store: https://www.operationalitam.com/store/ · Roles & Operating Cadence: https://www.operationalitam.com/store/index.php?page=product&sku=CP-ROLES

The store contains Bill's paid resources. Today's homework requires no purchase.

Your homework
Choose one renewal. Record the decision, last useful decision date, authorized owner, options, missing evidence and its owners, the condition that would change your recommendation, implementation responsibility, and the post-approval check.

Discussion
Where does your renewal process stall: evidence, authority, migration readiness, or checking the result?

Chapters
00:00 The meeting that cannot decide
01:08 From a better bill to a better decision
02:44 The fictional renewal
04:32 Who comes to the table
06:40 When the evidence disagrees
09:16 A short break
10:24 Two real reasons the disciplines need each other
12:22 The offer changes
15:05 Make the decision executable
16:35 After the signature
18:23 The takeaway and the homework

Transcript
Click here to view the episode transcript.

Primary references

FinOps Framework: https://www.finops.org/framework/
Intersecting Disciplines: https://www.finops.org/framework/capabilities/intersecting-disciplines/
ITAM and FinOps: planning and procurement: https://www.finops.org/wg/finops-itam-practical-scenarios-planning-procurement/
Microsoft SQL Server licensing: https://www.microsoft.com/licensing/guidance/SQL
Azure Hybrid Benefit: https://learn.microsoft.com/en-us/azure/azure-sql/azure-hybrid-benefit?view=azuresql
AWS Savings Plans FAQ: https://aws.amazon.com/savingsplans/faqs/
AWS Savings Plans returns: https://docs.aws.amazon.com/savingsplans/latest/userguide/return-sp.html
An EpicB Media LLC production.