Gtm weekly wrap

GTM weekly wrap

One page, every Friday, that tells leadership how the week went across the whole funnel: numbers first, then what drove them, then what happens next. Same structure every week so people can compare.

When to use

• Friday (or Monday morning) update to the exec team, board observers, or the whole company.
• Not for a board deck or a quarterly business review. Those need more context and fewer weekly details.

Inputs

Take what the user has. Ask once for anything important that is missing, then work with what you get.

1. Numbers in data/: a metrics sheet export (see the kit's examples/metrics-2026-w45.csv: team, metric, this week, last week, quarter to date, plan for the full quarter), or outputs from other kits such as out/forecast*.json from weekly-forecast-rollup and out/hygiene*.json from pipeline-hygiene.
2. Notes from each team lead: wins, losses, escalations, launches (data/notes-*.md or pasted).
3. Last week's wrap in out/ if it exists, to follow up on last week's "next week" list.
4. The audience (exec team, whole company, board) and the plan or targets if not in the sheet.

Steps

1. Load numbers. For each metric compute the change vs last week, and quarter to date as a percent of the full-quarter plan. Compare that with the share of the quarter that has passed: ahead of pace if higher, behind if lower (for cost and churn metrics, higher is worse). Show your pace math once.
2. Pick 3 headline numbers that matter most this week (usually bookings, pipeline created, retention). Not every metric goes in the headline.
3. Wins: at most 3, each with a number and a name (deal, campaign, account).
4. Misses and risks: at most 3. Be direct. Each gets a cause if known and an owner for the fix.
5. Follow-ups: check last week's "next week" items. Mark each done, in progress, or dropped.
6. Next week: 3 to 5 priorities, each with an owner (a role or team if no name was given) and a date.
7. Write out/gtm-wrap-<YYYY>-w<NN>.md in the format below. Keep it under 400 words. Show it in chat.

Output format

# GTM weekly wrap, week 45 (Nov 2 to Nov 6)

**Headline:** Bookings $95k (+$55k WoW); QTD $610k is 55% of the quarter plan with 40% of the quarter gone, ahead of pace. Marketing-sourced pipeline is behind at 33% of plan.

| Area | Metric | This week | WoW | QTD vs plan |
| --- | --- | ---: | ---: | --- |
| Marketing | Pipeline sourced | $310k | +29% | 33%, behind |
| Sales | Bookings | $95k | +138% | 55%, ahead |
| CS | Churned ARR | $18k | +$18k | 78% of budget, over pace |

**Wins**
- Northwind expansion closed, $50k.

**Misses and risks**
- Contoso ($30k) slipped to January on a procurement freeze. Owner: Sales lead, confirm Q1 timing.

**Last week's follow-ups:** 2 done, 1 in progress.

**Next week**
1. Book the two webinar enterprise demos. Owner: SDR team, by Wed.

Guardrails

• Never invent a number, a cause, or an owner. If a cause is unknown, write "cause unknown" and ask.
• Use the user's metric names and definitions. If two sources disagree, show both and flag it.
• Keep customer names only if the audience is internal. For a board or wide audience, ask before naming customers.
• Do not send or post the wrap. The user shares it.

GTM weekly wrap

Writes the Friday one-pager across marketing, sales, and customer success: the numbers against plan and last week, the real wins and misses, follow-ups from last week, and next week's priorities with owners.

Who it is for

RevOps leads, chiefs of staff, and founders who owe the exec team a weekly revenue update and rebuild it by hand every Friday.

Example

Input: examples/metrics-2026-w45.csv (11 metrics across three teams) and examples/notes-2026-w45.md (team notes).

Output (out/gtm-wrap-2026-w45.md), the top:

Headline: Bookings $95k (+$55k WoW), 55% of the quarter plan with 40% of
the quarter gone. Marketing-sourced pipeline is behind at 33% of plan.
Wins: Northwind expansion closed, $50k.
Risks: Contoso ($30k) slipped to January on a procurement freeze.
Next week: book the two webinar enterprise demos (SDR team, by Wed).

Works even better with the output of the weekly forecast rollup and pipeline hygiene kits.

What it can access

• Reads data/, out/, and the kit's own examples/; writes out/. No scripts, no network.

Setup

None. Drop your metrics export and team notes in data/.