An AI content renewal often starts with a familiar question: did the team use the tool enough?

Usage matters. It does not show whether the tool produced accepted work, reduced review, replaced another cost, or created a new export and access burden. A renewal should answer what became cheaper, what became faster, and what remained unchanged.

Renewal value is the change in the whole process, measured against the work that existed before the tool.

Rebuild the baseline#

Use the period before adoption and the same period after adoption. Compare:

Measure	Before	After
Accepted assets
Published assets
Attempts per accepted asset
Review minutes
Agency or contractor spend
Provider and subscription spend
Unattributed usage
Time from brief to live

Keep the content type and campaign mix visible. A launch quarter is a poor baseline for a quiet quarter, and a new workflow may add output without reducing cash spend.

The savings-proof guide explains why capacity and savings need separate labels. Use both in the renewal document.

Count accepted work#

Ask the vendor for:

requests submitted;
drafts returned or abandoned;
accepted assets;
published assets;
attempts and retries;
review or approval passes;
direct usage and overage;
exports and connector calls.

If the vendor cannot provide every field, mark the gap. Do not fill it with an estimate that makes the tool look better.

The procurement checklist gives evidence and exit questions to ask before the first trial. A renewal is the right time to see whether those answers became actual exports.

Separate three kinds of value#

Value type	Evidence
Cash savings	An invoice, contract, or headcount plan changed
Capacity	The same team accepted more useful work
Quality or risk	Fewer returns, unsupported claims, or late fixes

One outcome can support another, but it should not be counted twice. If a tool let the team avoid an agency expansion, show the avoided scope and the assumption behind it. If the team produced more pages with the same people, label the result as capacity.

Include the cost around the tool#

Add:

seats and usage;
implementation and administration;
source preparation;
review and repair;
exports and version comparison;
access reviews and offboarding;
time spent resolving provider or connector failures;
work that never became useful.

The tool-sprawl guide shows how a tool can create cost at the handoff. Include those minutes even when they do not appear on the vendor invoice.

Make the renewal decision conditional#

A simple renewal table is clearer than a single score:

Condition	Decision
Accepted cost is within target and evidence is usable	Renew at current scope
Quality is strong but review remains high	Renew with a process change and a review target
Adoption is high but accepted output is low	Narrow the use cases or pause
Usage is low because access or setup failed	Fix ownership before expanding
Usage is high but spend has no usable join	Require attribution before renewal
Another tool owns the same step	Consolidate or choose one owner

Write the target and owner into the renewal. A promise to “improve adoption” is not a decision.

Test the exit before signing#

Ask the team to export:

accepted assets;
source references and versions;
attempt and review history;
usage and billing data;
user and access history;
connector configuration;
stable IDs that join to campaigns or finance records.

Then ask someone outside the trial team to find one asset and explain how it was accepted. If the export cannot support that task, the renewal carries a future migration cost.

Review the price change with the process change#

When the vendor raises or changes pricing, show:

the old and new price structure;
the expected volume;
the accepted cost under each structure;
overage or minimum commitment;
the direct and human cost around the tool;
the alternatives and their migration cost.

The lowest annual quote may still be expensive if it lowers acceptance or increases review.

Deixic can show spend by agent, activity, approvals, connected tools, and missing cost proof to support the operational side of this review. Use the product view with the vendor’s billing and export evidence so the renewal reflects the whole process.