Docs

GTM Priority Briefing

Question it answers: Across every living GTM doc, what are the few things that will move the needle most right now — ranked, synthesized, and filterable to what matters for me? Cadence: Weekly GTM owner: Rev Ops (distribution) / all GTM

This is the meta-doc: it points at the other living GTM docs (any subset, all by default), reads their current findings, and synthesizes one ranked answer to "what should we actually do this week." Where the Weekly GTM Digest is a radar sweep of what moved, this is a prioritizer — it scores every surfaced insight and recommendation by how much it will move the needle, dedups across docs, and ranks. The reader can filter the ranking down to their persona and context so they see their highest-value items first.

Data sources

Internal (primary): the current (promoted) versions of the other living GTM docs in the knowledge base — read via knowledge_base search/get, collapsed to the current version per document group. Each source doc contributes its findings, recommendations, confidence signals, and evidence. The set of source docs is a parameter: default is all of #1–#18; a run can be pointed at any subset (e.g. just the PMM docs, or just pipeline + qualification).

Internal (scoring signal): a thin layer of live data:read reads to freshness-weight and score candidates — deal_qualification outcome_band movement, interactions volume/recency delta, clusters velocity/recency_strength (rising themes weigh up), social.get_portfolio_summary, and — for market context — industry.get_divergence / industry.list_themes. All on the read-only floor, so the run needs no elevated scope.

External: None directly. Like the Weekly GTM Digest, this synthesizes the other docs (which already fused external sources where relevant) rather than re-pulling raw external data.

Living Document

The weekly "what matters most" briefing. One document a GTM leader (or any function lead) reads to know where to spend attention — built by ranking, not by listing. Sections:

  • Scope this run — which source docs were included and how fresh each is (last promoted version date), so the reader knows the basis. Stale or empty source docs are flagged, not silently dropped.
  • Top priorities (ranked) — the N highest needle-movers across every source doc. Each: the insight in one line, its priority score, the source doc it came from, why it matters now, the supporting evidence (carried through from the source doc, with its quote/metric), and the recommended action + owner. Deduplicated — the same signal surfacing in three docs becomes one priority with three corroborating sources, ranked higher for it.
  • How these were scored — the rubric, stated transparently: priority = impact × confidence × urgency ÷ effort, where impact = revenue/pipeline consequence, confidence = strength of evidence in the source doc, urgency = how time-sensitive (a closing deal, a rising theme, a competitor move), effort = how hard to act. Cross-doc corroboration boosts confidence.
  • By function — the single most important item for each GTM function (PMM / Rev Ops / Demand Gen / Content), so each leader finds their headline fast.
  • By persona — what matters most to each role/persona represented in the data (e.g. what an AE should act on vs. what a content lead should). This is the slice that lets a reader jump to their priorities.
  • What changed since last briefing — priorities that rose, fell, were resolved, or newly appeared, with the signal that drove the move. The week-over-week delta is often the most actionable part.
  • Watchlist — 3 things to monitor next week that aren't yet top priorities but are trending toward it.

Versioned weekly. Rev Ops reviews and promotes. Because it cites its source docs by name and version, every priority is traceable back to the underlying analysis.

Page

A live priority command-center — a ranked, filterable view of everything that matters, with the reader's own slice one filter away.

Filters (the personalization layer): persona/role selector, plus filters for function, source doc, impact band, and timeframe — so a viewer narrows the ranking to what's most valuable to them. (These viewer-facing controls depend on the planned Pages input-component work; until then the page renders the full ranked view and persona/function slices are precomputed sections — see docs/living-gtm-docs-feasibility.md §6.)

Stats row:

  • Number of priorities surfaced this run
  • Top priority score (and its one-line title)
  • Net-new priorities vs. last run

Bar chart — Priority ranking: Priority score by item (top 15), sorted descending — the at-a-glance "what's hot."

Table — Priority queue: One row per priority — rank, title, score, function, owner, source doc, impact, confidence, effort, persona tags, recommended action. Sortable and (once input components land) filterable by every column. The core working surface.

Bar chart — Signal concentration: Priorities grouped by source doc — shows where this week's needle-movers are concentrating (all pipeline? all messaging? spread?).

Table — By persona: Top 3 priorities per persona/role, so a viewer scans straight to their lane.

Treemap — Impact × effort: Priorities sized by impact and grouped by effort band — surfaces the high-impact / low-effort quadrant (the "do these first" set).