What’s inside the guide
The scope in your current agreement came from an estimate. At the time there was no other way to size it, because nothing had run yet. Someone listed the integrations planned for the year, added a margin for growth, and picked the tier that covered both.
Since then the workloads changed, consumption models changed, and agents arrived. The one thing you have now that you did not have then is a record of what actually ran.
This guide is the method for turning that record into a scope. Five steps, ten fields per workload, and two or three days of work for most companies. It ends with the five numbers to take into the renewal conversation and three questions that make a quote checkable.
How this guide helps
- Build the inventory in two or three days: Five steps, ten fields per workload, and a clear split between what the admin console can tell you and what only people can.
- Sort every workload into one of four places: Correctly scoped, outgrew its scope, dormant, or left the platform. Each one carries a different instruction for the next term.
- Count the work that appears in no usage log: Applications built with AI coding assistants consume no tasks and trigger no jobs, so no console lists them. Three questions surface them, and they are usually the largest gap in a current agreement.
- Walk in with five numbers instead of a spreadsheet: What to bring, what each number establishes, and why opening with the count of workloads running correctly changes the conversation.
- Make a quote checkable: Three questions to ask every vendor, including the incumbent, that turn a single number into something you can compare against your own measured consumption.
