GTM Deployment Win — Slack Message Template
Use this when sharing a new tool or process you’ve built for the GTM team. Copy the sections below into Slack and fill in the placeholders. Always include a recorded demo.
Template (copy into Slack)
Deployment: [Name of tool/process/agent]
📎 Demo: [Link to recorded demo — required]
What this is
[1–2 sentences: what shipped and who it’s for.]
PRD highlights
• [Most important requirement or decision from the PRD — e.g. “Single source of truth: campaign brief; no one-off section types.”]
• [Second key PRD point — e.g. “Output is copy-only; no layout or design notes in the doc.”]
• [Third if needed — e.g. “Case study matching: pull from brainforge-files by ICP.”]
Process this replaces or creates
• [Step or workflow this replaces — e.g. “Replaces: drafting one-pager copy from scratch in Google Docs with no structure.”]
• [Step or workflow this creates — e.g. “Creates: campaign brief → design-ready copy (by archetype) → designer drops copy into layout.”]
• [Optional: another before/after or net-new step.]
Where it lives
[Link to repo/doc — e.g. brief, agent, template, or runbook.]
How this evolves our context graph
• [New entities/relationships — e.g. “Adds design-ready-copy-agent entity; links campaigns → archetypes → assets.”]
• [New process steps — e.g. “Adds traceable step: brief → archetype selection → copy generation → designer handoff.”]
• [Enables trace capture — e.g. “Run log format added so we can track archetype selection and outcomes over time.”]
Invite critical feedback: What’s broken, missing, or annoying? What would make you actually use this (or use it more)? Reply in thread or DM me.
Example (filled) — Design-Ready Copy Agent
Deployment: Design-ready copy agent (campaign one-pagers/2-pagers)
📎 Demo: https://us06web.zoom.us/clips/share/DYdy2F9VRhisd9gBBXjC_g
What this is
Takes a campaign brief + case studies and outputs sectioned, design-ready copy for leave-behinds (one-pagers, 2-pagers). For Hannah/Anne: one markdown with headings and copy only — no layout notes, no “Title: TBD,” so you can plug text into the design in sequence. First run: Insurance Broker Lead Intake 2-pager.
PRD highlights
• Copy from brief; case studies from brainforge-files — match clients to ICP so “Trusted by” and case nuggets fit the campaign.
• Copy-only in sections — no visual suggestions, layout notes, or design direction; wording variations live in a separate section at the bottom so they don’t clutter.
• Archetype-based structure — we don’t invent a new section list per asset. Single service → Service 2-pager. Time-bound offer → Seasonal. Sprint / pilot-first → Sprint. Long strategy doc → Service guide. Partner kit → Partner/VC kit. Brief (or user) picks the archetype; agent fills the sections.
Process this replaces or creates
• Replaces: Drafting one-pager/2-pager copy from scratch in long docs with mixed-in design notes and “Title: TBD.”
• Creates: Campaign brief → pick archetype (from taxonomy) → fill sections from brief + case studies → hand designer one copy doc.
• Creates: Shared taxonomy so every new asset reuses an archetype instead of starting from scratch.
Where it lives
In brainforge-vault (PR for this flow): PRD gtm/agents/PRD-design-ready-copy-agent.md · Taxonomy gtm/agents/DESIGN_READY_COPY_TAXONOMY.md · Example output gtm/marketing-assets/design-ready-copy/insurance-broker-lead-intake-2pager.md · Deployment template gtm/templates/deployment-win-slack.md
How this evolves our context graph
• New entities: design-ready-copy-agent, service_2pager archetype (and 4 others), insurance-broker-lead-intake-2pager.md asset.
• New relationships: Campaign → archetype → asset (traceable via brief metadata and run logs).
• New process step: Brief → pick archetype (from taxonomy) → fill sections → output markdown → designer handoff.
• Enables trace capture: First run logged; future runs can track archetype selection patterns and designer usage.
Invite critical feedback: What’s broken, missing, or annoying? What would make you actually use this (or use it more)? Reply in thread or DM me.