How much of a GTM analyst's week goes to reusable research maintenance?
A time-capture protocol for separating reusable research maintenance from request work and planning capacity.

Question and scope
This protocol estimates the share of a GTM analyst's working week spent maintaining research that the team will use again. Maintenance includes source logs, saved searches, competitor pages, segment files, and the notes that keep those assets usable. It excludes one-off request work, live meetings, and administrative tasks that do not preserve a research asset. The estimate matters because maintenance is often invisible in capacity planning.
The unit of analysis is one analyst and one full working week. The protocol can be repeated across analysts, but it should not be combined into a single average without showing the range. A team with one analyst who owns the source library may look very different from a team that distributes the work. The scope is the team's own assets, not the entire market.
Define reusable research maintenance
Write a list of the assets the team actually reuses, such as the competitor tracker, the source log, the segment definitions, and the saved search list. For each asset, name the maintenance activity that keeps it usable. A definition that includes every research task will overstate maintenance and blur the capacity question. Keep the list to assets that another person would notice if they went stale.
Separate maintenance from creation. Creating a new competitor profile is project work, while updating the profile's source links and review date is maintenance. Both are valuable, but they compete for time in different ways. Record the distinction before the time study begins so the analyst does not classify by mood.
Choose a time capture method
Use a simple capture method that the analyst can sustain for a full week. A shared spreadsheet with start time, end time, activity, and asset is usually enough. Avoid a tool that requires a new login or a long taxonomy. The method should add less than a few minutes of overhead per entry.
Capture in blocks rather than in minute-by-minute detail. A block can be fifteen, thirty, or sixty minutes, depending on the work. Record what changed during the block and which asset it affected. The block method is less precise but more likely to survive a busy week. Precision that produces missing data is not useful.
Separate maintenance from request work
Tag each block as request work, maintenance, project work, or internal meeting. Add a short note for blocks that contain more than one type. The analyst should not spend time deciding on a perfect category. A best-fit tag with a note is enough for the estimate.
Review the tags with the analyst at the end of each day and resolve the ambiguous blocks while the memory is fresh. A block that updated a competitor page because a seller asked a question may be request-driven maintenance. Record the driver as well as the category. The driver tells the team whether the work would disappear if the request disappeared.
Sample one full week
Choose a week that represents normal demand rather than a launch week or a holiday. If no week is normal, sample two weeks and report both. The goal is a baseline that the team can compare with future weeks. A single unusual week will produce a misleading share.
Include the time spent waiting for access, sources, or approvals if that wait is part of the maintenance task. Waiting is often the hidden cost of an outsourced or shared research function. Record it separately so the team can decide whether to fix the process or add capacity. Do not bury the wait inside the activity total.
Calculate the share and the cost
Add the maintenance blocks and divide them by the analyst's total working hours for the week. Report the share with the number of hours and the number of assets touched. A percentage without the underlying hours is hard to act on. The team needs to know whether the work is two hours or two days.
Convert the hours into a cost using the analyst's loaded rate, and compare that cost with the value of the assets. If a source log prevents repeated rework, the maintenance may be cheap relative to the alternative. If a tracker is updated but never read, the cost has no return. The comparison should start a conversation about which assets deserve maintenance.
Validate the estimate with a second observer
Ask a second person to review a sample of the tagged blocks. The observer can check whether a block labeled maintenance was actually request work or project work. Resolve disagreements with the written definitions rather than with seniority. A short calibration improves the estimate without requiring a second full week.
Compare the analyst's estimate with the manager's expectation. A large gap is useful evidence, not a failure. It may show that the manager sees only the output and not the upkeep. Use the gap to discuss which assets the team is willing to let go stale. Maintenance is a choice about what the team needs to keep.
Separate maintenance from tool administration
Tool administration includes logins, permissions, vendor invoices, and workspace settings. It is necessary, but it is not the same as keeping a research asset current. Record it separately so the maintenance estimate does not absorb every administrative task. A team that conflates the two may conclude that research upkeep is larger than it is and cut the wrong work.
If tool administration is a large share of the week, treat it as an operations problem rather than a research problem. Assign an owner, simplify the access model, and reduce the number of tools that need separate maintenance. The time study should show the split so the team can act on the right category. Record that split beside the total so the reader can see the difference.
Check the cost against a replacement
Compare the maintenance cost with the cost of replacing the asset. A source log that takes two hours a month may be cheaper than rebuilding the research from scratch after a staff change. A competitor tracker that nobody reads may be more expensive than letting it lapse. The comparison should include the time to recreate the asset, not only the subscription fee.
Write the comparison as a simple range rather than a precise number. The team is making a judgment under uncertainty, and a false precision invites arguments. State the assumptions and the person who owns the decision. The point is to protect the maintenance that prevents larger rework.
Report the result to the capacity owner
Present the hours, the assets touched, and the decisions that depend on those assets. A capacity owner needs to see the tradeoff, not only a percentage. Show what would be delayed if the maintenance block were removed. The conversation should end with a protected block or a deliberate reduction.
Record the decision and the date of the next measurement. If the team chooses to reduce maintenance, name the asset that will lapse and the risk of doing so. A deliberate choice is easier to defend than an unplanned gap. The next time study can then test whether the choice held.
Use the same format for the next measurement so the team can compare one period with another. Record the analyst, the week, the assets in scope, and any unusual demand. A consistent format is more useful than a longer report. The capacity owner should be able to see the trend without opening the raw spreadsheet.
Limits and sources of error
The protocol measures one week and one analyst, so it cannot establish a permanent share. Seasonal demand, a launch, or a staff absence can change the result. Repeat the measurement after a process change or a major shift in the source set. Report the conditions beside the number.
The cited public sources describe occupational work and business survey practice, not a benchmark for this team's maintenance load. They should not be used to claim that a particular share is normal. Treat the result as a local estimate and keep the raw blocks so another person can check the calculation. Keep the original blocks and the calculation so a later reviewer can test the estimate.
Use the result in capacity planning
Add the maintenance hours to the capacity model as a protected block rather than as slack. If the work is real, it should compete with request work for time. Show the team what would be delayed if maintenance were cut. A protected block makes the tradeoff explicit.
Review the asset list each quarter and remove anything that no longer earns its upkeep. A smaller set of current assets is easier to defend than a large library that nobody trusts. Record the decision and the owner. The estimate should lead to a better portfolio, not only a number in a planning deck.
Sources
- Occupational Outlook Handbook: Market research analysts, U.S. Bureau of Labor Statistics. Describes market research analyst work and the tasks that make up the role.
- Business Trends and Outlook Survey, U.S. Census Bureau. Provides business survey context for demand and operating conditions.
- Market research and competitive analysis, U.S. Small Business Administration. Outlines a practical market research process for small teams.
- Cybersecurity Framework 2.0, National Institute of Standards and Technology. Supplies a risk-management framing for information assets and controls.
- Protecting Personal Information: A Guide for Business, Federal Trade Commission. Covers responsible handling of personal information in research records.