Skip to content
SlashClone
DiscoverUse in ClaudeSubmit a link
Sign in
Made by@revopslab

Gtm weekly wrap

@revopslab/gtm-weekly-wrap

Write the Friday GTM wrap: one page across marketing, sales, and customer success with the numbers against plan, wins, misses, risks, and what happens next week. Works from whatever you have: CRM exports, a metrics sheet, last week's wrap, and team notes.

SkillRevOpsv1.0.0 (latest)
Use in Claude Save Like Clone Comment
Activity
New: be the first to try it
  1. 1---
  2. 2name: gtm-weekly-wrap
  3. 3description: Write the Friday go-to-market weekly wrap across marketing, sales, and customer success. Pulls the week's numbers against plan and last week, picks the real wins and misses, names risks, and lists next week's priorities with owners, in one page leaders actually read. Use when the user says "write the weekly wrap", "Friday GTM update", "weekly revenue summary for the exec team", "summarize the week across sales, marketing, and CS", or shares a metrics sheet and team notes.
  4. 4license: MIT
  5. 5---
  6. 6
  7. 7# GTM weekly wrap
  8. 8
  9. 9One 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.
  10. 10
  11. 11## When to use
  12. 12
  13. 13- Friday (or Monday morning) update to the exec team, board observers, or the whole company.
  14. 14- Not for a board deck or a quarterly business review. Those need more context and fewer weekly details.
  15. 15
  16. 16## Inputs
  17. 17
  18. 18Take what the user has. Ask once for anything important that is missing, then work with what you get.
  19. 19
  20. 201. **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`.
  21. 212. **Notes** from each team lead: wins, losses, escalations, launches (`data/notes-*.md` or pasted).
  22. 223. **Last week's wrap** in `out/` if it exists, to follow up on last week's "next week" list.
  23. 234. The audience (exec team, whole company, board) and the plan or targets if not in the sheet.
  24. 24
  25. 25## Steps
  26. 26
  27. 271. 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.
  28. 282. Pick 3 headline numbers that matter most this week (usually bookings, pipeline created, retention). Not every metric goes in the headline.
  29. 293. **Wins**: at most 3, each with a number and a name (deal, campaign, account).
  30. 304. **Misses and risks**: at most 3. Be direct. Each gets a cause if known and an owner for the fix.
  31. 315. **Follow-ups**: check last week's "next week" items. Mark each done, in progress, or dropped.
  32. 326. **Next week**: 3 to 5 priorities, each with an owner (a role or team if no name was given) and a date.
  33. 337. Write `out/gtm-wrap-<YYYY>-w<NN>.md` in the format below. Keep it under 400 words. Show it in chat.
  34. 34
  35. 35## Output format
  36. 36
  37. 37```markdown
  38. 38# GTM weekly wrap, week 45 (Nov 2 to Nov 6)
  39. 39
  40. 40**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.
  41. 41
  42. 42| Area | Metric | This week | WoW | QTD vs plan |
  43. 43| --- | --- | ---: | ---: | --- |
  44. 44| Marketing | Pipeline sourced | $310k | +29% | 33%, behind |
  45. 45| Sales | Bookings | $95k | +138% | 55%, ahead |
  46. 46| CS | Churned ARR | $18k | +$18k | 78% of budget, over pace |
  47. 47
  48. 48**Wins**
  49. 49- Northwind expansion closed, $50k.
  50. 50
  51. 51**Misses and risks**
  52. 52- Contoso ($30k) slipped to January on a procurement freeze. Owner: Sales lead, confirm Q1 timing.
  53. 53
  54. 54**Last week's follow-ups:** 2 done, 1 in progress.
  55. 55
  56. 56**Next week**
  57. 571. Book the two webinar enterprise demos. Owner: SDR team, by Wed.
  58. 58```
  59. 59
  60. 60## Guardrails
  61. 61
  62. 62- Never invent a number, a cause, or an owner. If a cause is unknown, write "cause unknown" and ask.
  63. 63- Use the user's metric names and definitions. If two sources disagree, show both and flag it.
  64. 64- Keep customer names only if the audience is internal. For a board or wide audience, ask before naming customers.
  65. 65- Do not send or post the wrap. The user shares it.
Sign in to comment on a line