What does a competitive intelligence source refresh actually cost to maintain?
A cost measurement method for competitive source refreshes that counts search, verification, rewriting, and review time.

Define the refresh task
A competitive source refresh is the work required to confirm that a published claim still matches its source. It begins with locating the source and ends with an approved change or a recorded no-change result. The task includes checking the page, comparing the new observation with the stored evidence, and updating any affected card or note. It is not the same as writing a new competitive analysis from scratch.
Write the definition before measuring so the team counts the same steps. Decide whether link checks, screenshot capture, and seller communication belong inside or outside the refresh. A narrow definition produces a smaller cost and a narrower view of maintenance. A broad definition is more realistic for planning because it includes the work that keeps the card usable. State the boundary in the report.
Count the hidden steps
The visible step is often a quick look at a product page. The hidden steps are the search for the current URL, the login to a gated report, the comparison with last quarter's note, and the rewrite of a sentence that no longer fits. List every step in the order the analyst performs it. A step that takes two minutes still consumes capacity when it repeats across twenty sources.
Include the coordination steps as well. A refresh may require a message to a product expert, a wait for a legal review, or a check with a seller who heard a different claim. These steps are easy to omit because they do not look like research. They still extend the cycle and should appear in the cost record. The goal is a complete picture of the maintenance burden.
Time the full cycle
Record the start time when the analyst opens the source and the end time when the result is approved. Keep active work time separate from waiting time. Active time shows the labor cost, while waiting time shows the delay the team should plan around. A refresh that takes thirty minutes of work and five days of waiting needs a different fix than one that takes four hours of work.
Time a sample across source types rather than timing one easy page. Include a public product page, a documentation page, a gated report, and a competitor announcement. Each type has a different search and verification pattern. The average across the sample is more useful than a single stopwatch reading. Record the sample size and the date so the estimate can be repeated.
Separate scheduled from reactive work
Scheduled refreshes happen on the calendar. Reactive refreshes happen when a seller reports a change, a competitor launches, or a buyer raises a new objection. Both consume the same analyst, but they compete with planned work in different ways. Record the trigger beside each refresh so the team can see how much of the week is driven by outside events.
A high reactive share may mean the watch list is too broad or the alerts are too noisy. It may also mean the team is responding to real market changes that deserve attention. The cost report should not treat all reactive work as waste. It should show the split so the manager can decide whether to reduce triggers or reserve capacity for them.
Measure rework and duplicate effort
Count the refreshes that had to be repeated because the first check missed a change or used the wrong page. A duplicate effort can also occur when two people refresh the same source without knowing. Record the cause and the extra time. These costs are often invisible in a simple page-count metric, yet they can dominate the maintenance burden in a poorly coordinated team.
Look for sources that generate repeated rework because they are unstable or hard to verify. A page that changes layout every month may cost more than a stable regulatory page even if both support similar claims. The report should identify the expensive sources and the reason. That evidence supports a decision to replace the source, change the interval, or assign a different verification method.
Compare source types
Group the sample by source type and report the median active time and waiting time for each group. Public pages, gated reports, community posts, and vendor documentation behave differently. A gated report may require an annual download and a manual table extraction. A community post may be quick to read but hard to verify. The comparison shows where the maintenance budget actually goes.
Use the comparison to set realistic refresh intervals. A high-cost source with a low decision value may deserve a longer interval or removal from the watch list. A low-cost source with a high decision value may deserve a tighter check. The point is to match effort to decision risk rather than to refresh every source at the same rhythm.
Build a monthly cost view
Multiply the median time per source type by the number of refreshes in the month. Add the reactive work, the rework, and the review time. Present the result as hours rather than as a dollar figure unless the team has an agreed rate. Hours are easier to compare with the analyst's available capacity and less likely to imply a precision the data does not support.
Show the fixed and variable parts separately. A monthly report on a stable source list is fixed work. A launch season with many competitor announcements is variable work. The manager can plan the fixed load and reserve a buffer for the variable part. A single total hides the part of the cost that the team can actually control.
Report the limits
The estimate depends on how the team records time and what it counts as a refresh. A team that only records completed updates will understate the cost of checks that found nothing. A team that counts every page open will overstate it. State the recording practice beside the result so readers do not compare unlike teams.
The sample may not represent a launch month or a quarter with an unusual number of competitor changes. The cited public sources describe competitive analysis, employment, and security practice. They do not provide a benchmark for this team's refresh cost. Treat the result as a local estimate and repeat it when the source list or the market activity changes.
Set a maintenance budget
Use the monthly hours to set a maintenance budget for the watch list. If the budget is smaller than the current cost, remove low-value sources or lengthen their intervals before reducing the quality of the high-value checks. A budget that assumes every source can be checked at the same frequency will either be broken or quietly ignored. Review the budget with the analyst who performs the checks so the estimate reflects the real steps.
Name the owner of the budget and the date of the next review. Share the source cost list with the person who requests new watch list entries so they understand the tradeoff. A new source is not free just because the first check is quick. It adds a recurring obligation that should be weighed against the decisions it supports.
Review and decide
At the next review, compare the budget with the actual hours and the material changes found. A source that consumed time but produced no decision-relevant change for several cycles is a candidate for a longer interval. A source that produced a change the team missed is a candidate for a tighter check or a better alert. Let the evidence drive the adjustment.
Write one decision for the next cycle and one date to check it. Keep the prior cost report so the comparison is like for like. The purpose is a sustainable watch list that supports real decisions, not a perfect measurement of every minute. A rough but honest cost view is enough to stop a useful intelligence habit from becoming invisible overhead.