⟨ BLOGPLAYBOOKSREPORTS & DECKS

Weekly GTM data report: lists, signals, verification rates

Every Monday, the week's GTM data - list growth, signals by type, verification rates, audience sizes and match rates - charted in a Google Doc with the summary posted to #revops.

PlaybookListsChartsGoogle DocsSlackRUN BY THE COMPANY INTELLIGENCE AGENT →

The problem this solves

A revenue team runs on data it rarely measures. Lists grow or stall, signals fire or go quiet, verification pass rates drift as sources age, audiences shrink as customers are suppressed - and none of it is visible until a campaign underperforms and someone goes looking. The numbers exist in the workspace; assembling them into a weekly picture is the report nobody has time to build on a Monday morning.

The Company Intelligence Agent builds it. Each Monday it reads every list, every standing signal mission, every verification run and every audience from the previous week, computes the figures, renders each as a chart and writes a short Google Doc that reads top to bottom in five minutes. The summary goes to #revops so the team sees the headline without opening the Doc, and every figure links back to the list or mission that produced it.

Over weeks the reports become a series, and the charts gain a second line: this week against the average, which is where the drift in a verification rate or the slowdown in a list becomes visible before it matters.

How the mission runs

  1. Read the week's list activity. For every list in the workspace, the agent counts companies and contacts added, removed and refreshed in the last seven days, and notes which lists were untouched, so a list that silently stopped growing is called out rather than omitted.
  2. Count signals by type. Every standing signal mission - hiring, funding, technology change, intent surges, expansion news - contributes the events it fired during the week, grouped by type and by the list it watches, with the accounts that produced the most events named.
  3. Compute verification and enrichment rates. Verification runs are summarized as pass rates by status - deliverable, catch-all, risky, invalid - and enrichment runs as fill rates per field, both compared with the trailing four-week average so a drop stands out.
  4. Read audience sizes and match rates. Every connected audience on LinkedIn, Meta and Reddit is read for its current matched size and, where a refresh ran, the match rate and the size delta, so the media team sees whether its audiences are growing or being suppressed away.
  5. Chart, write and post. The chart capability renders each figure - list growth as columns, signals by type as a stacked bar, verification rates as a line against the average, audience sizes as a bar with deltas - and the Doc is written with one section per figure and a one-paragraph summary at the top, which is also posted to #revops with the Doc linked.

The prompt

This is the exact objective the agent receives. Swap the obvious placeholders for your own domain, segment or channel and run it as-is from the console, Slack, or the API.

⟨ THE MISSION PROMPT · PASTE AND RUN ⟩

Every Monday, build the weekly GTM data report: new companies added per list, signals fired by type, verification pass rates, audience sizes and match rates, all charted, as a Google Doc with the summary posted to #revops.

What comes back

A Google Doc every Monday with the week's GTM data - list growth per list, signals by type, verification pass rates and enrichment fill rates against their four-week averages, audience sizes and match rates with deltas - each as a chart with a short observation, and a summary paragraph posted to #revops with the Doc linked. Every figure links to the list or mission behind it.

Make it yours

  • Add pipeline created from the CRM so the report connects data activity to revenue outcomes.
  • Send the report by email to a distribution list as well as posting the summary.
  • Run it daily during a launch week with a shorter format.
  • Add a cost section showing credits spent by capability against the week's budget.

Frequently asked questions

Which lists and missions are included?

All of them by default; name the ones to include or exclude in the prompt, and the Doc states its scope in the first line.

How is the four-week average computed?

From the previous four reports; the first report shows the week's figures alone and the comparison lines appear as history accumulates.

Can figures be exported for a deck?

Yes. Ask for a CSV of the week's figures and the chart images, and both are saved beside the Doc.

Does the report cost credits to produce?

Reading the workspace's own records costs little; the charts and the Doc are the main spend, and the report states its own cost in the footer.

Go deeper

⟨ RUN IT INSTEAD OF READING IT ⟩

This mission runs minutes after signup.

Open a workspace, paste the prompt, and the Company Intelligence Agent carries it end to end on your plan's monthly credits - evidence attached.

⟨ RELATED PLAYBOOKS ⟩