How should a GTM team measure the cost of a stale sales asset?
A practical model for estimating the exposure, correction, and trust cost of a sales asset that has fallen out of date.

Question and scope
This protocol estimates the cost of a sales asset that no longer matches the current product, fee, or process. The scope is seller-facing material such as a one-page overview, a comparison sheet, or an objection note. It excludes internal strategy documents that never reach a buyer. The question matters because stale assets rarely announce themselves, and the team often pays for them in corrections and lost trust rather than in a line item.
The unit is one asset version used in a defined period. A version becomes stale when a material fact changes and the asset is not updated. The protocol separates the exposure cost from the correction cost and the trust cost. Each is estimated differently, and combining them without labels produces a number that looks more precise than the evidence supports.
Define asset staleness
Write down what counts as a material change for each asset type. A packaging change is material for a comparison sheet, while a logo update may not be. A product limit change is material for an objection note if sellers rely on the old limit. Define the threshold before the audit so the team does not argue about each file after the fact.
Record the last verified date and the source that confirms the current state. An asset without a verified date is treated as unknown rather than current. Unknown is a useful status because it prompts a check instead of a guess. The audit should count unknown assets separately from confirmed stale ones.
Check the asset against the source of truth rather than against a newer asset. A newer file may repeat the same stale claim, especially when it was copied from an old template. Record the source used for the comparison and its date. The source of truth is what makes the staleness judgment defensible.
Count exposures
Estimate how many times the stale version reached a buyer. Use the channels the team can actually count, such as downloads from the library, links in sent emails, and attachments in scheduled follow-ups. Where exact counts are unavailable, use a documented estimate and label it as such. The exposure count is the multiplier that makes the rest of the model meaningful.
Separate a download from a use. A seller may download an asset and never send it, while an old link in a template may reach many buyers without a new download. Record the channel and the confidence level for each count. A high-confidence count from the library is more useful than a broad guess about seller behavior.
Include the assets attached to automated sequences, because those can reach many buyers without a seller noticing. An old link in a scheduled email is a persistent exposure. Record the sequence name and the last time it was edited. Automated exposure is often the largest and least visible part of the count.
Estimate the correction cost
Count the hours needed to correct the asset and every copy of it. That includes the source file, the saved email template, the shared drive copy, and any training deck that references it. A correction that fixes only one copy leaves the stale claim in circulation. Use the team's actual hourly cost or a clearly stated planning rate.
Add the time spent answering questions caused by the stale asset. A seller who has to check with marketing before sending a claim is paying a cost that never appears in the correction log. Record these questions for one week to estimate the volume. The correction cost should include the rework loop, not only the final edit.
Include the cost of reviewing the corrected asset before it goes back into circulation. A quick edit that introduces a new error is not a fix. Record the reviewer and the review time. The correction cost should cover the full cycle from identifying the stale claim to approving the replacement.
Add the trust cost
The trust cost is the hardest to estimate and the easiest to ignore. A buyer who receives a stale fee or a retired feature may question the rest of the proposal. Record any known instance where a buyer challenged a claim because the asset was out of date. Even one documented case is more useful than a speculative percentage.
Do not convert trust cost into a currency figure unless the team has a defensible method. Instead, report it as a count of incidents and a short description of the effect on the deal. A qualitative note beside a quantitative estimate is more honest than a fabricated dollar amount. The reader can weigh the risk without being misled by false precision.
Build a simple model
Combine the three parts in a way the team can explain in one sentence. A simple model multiplies estimated exposures by the correction hours per exposure, then adds the recorded trust incidents separately. Show the inputs beside the result so the reader can change an assumption. A spreadsheet with five inputs is more useful than a complex formula nobody can audit.
Run the model at a low, middle, and high assumption for exposure. The range shows how much the result depends on the least certain input. If the conclusion changes across the range, the team needs better exposure data before making a large investment. If the conclusion holds, the decision is robust to the uncertainty.
Put the model in a shared file with the inputs on one tab and the result on another. A model that lives in a private spreadsheet cannot be checked or updated by the next owner. Label each input with its source and the date it was collected. The model should be simple enough to rebuild from the labels alone.
Interpret the model
Use the result to rank assets for refresh rather than to produce a single total. An asset with moderate exposure and a high correction cost may deserve attention before an asset with high exposure and a quick fix. The ranking should reflect both the cost and the ease of correction. A short list of five assets is enough to start.
Compare the cost of the stale asset with the cost of preventing it. A monthly review may be cheaper than a large annual cleanup, but only if the review actually catches the changes. The model should inform the review interval, not just the cleanup budget. The best outcome is a lower exposure count next quarter.
Use the ranking to decide what to fix this month and what to retire. A stale asset with low exposure and no owner may be better retired than refreshed. A high-exposure asset with a clear owner is a straightforward fix. The model should lead to a short action list, not a large report.
Limits and sources of error
Exposure counts are usually incomplete because many assets travel through private messages and saved files. The correction time may be underreported when people fix a claim without logging it. The trust cost depends on what buyers say, and most buyers do not report a stale claim directly. Treat the result as a planning estimate with a stated range.
The cited public sources describe market research, business survey practice, and information protection. They do not provide a cost benchmark for this asset or this team. Use the model to compare the team with its own prior periods and to justify a specific review change. Revisit the assumptions when the sales process or the product changes.
Turn the estimate into a review rule
Set the review interval from the asset's change rate and exposure. A high-exposure asset tied to a fast-changing fact needs a shorter interval than a low-exposure background sheet. Write the interval beside the asset and name the owner. The interval should be based on evidence from the audit, not on a general policy.
Review the model after the next cleanup and compare the exposure count with the prior period. If exposure did not fall, the fixes may not have reached the saved templates and sequences. If it fell but trust incidents continued, the problem may be a claim that is hard to verify rather than a stale file. Adjust the rule accordingly.