The expensive part of a webinar is the thinking that went into it. Repurposing earns its place when that thinking reaches another reader in a form they can use. Cutting the transcript into a pile of similarly worded posts creates more publishing work without necessarily creating more value.
The plays below connect research, writing, and distribution: extract useful arguments, draft from a real point of view, build a competitive brief, and adapt an asset for different channels. Use the shared prompts in a supported assistant. For a reusable skill or connected workflow, follow the tool-specific instructions shown alongside it.
From one source asset to a reviewed post
Extract the useful material
Supply a transcript and the intended audience. Keep the strongest claims, examples, and source references together.
Open the repurposing prompt →Write from a point of view
Choose one argument and support it with the extracted evidence. Set the voice, format, and intended response before drafting.
Open the LinkedIn-post prompt →Plan the rest of the assets
Give each channel a distinct job, edit the drafts, and check attribution before publication. The full playbook names the production tools.
Open the repurposing workflow →
Keep the source and the point of view together
Start with material that contains something worth saying: an interview, a demonstration, a customer question, or a position your team can defend. Identify the argument, its evidence, and the reader who needs it. Keep timestamps or source references close to the extracted points.
Give each derivative asset a separate job. A LinkedIn post can carry one sharp argument; an email can explain why the reader should care; a sales follow-up can answer a specific objection. Adapt the structure and detail to that job instead of shortening the same paragraph three times.
Supply voice rules with examples of what good looks like and what needs editing. Explain the audience, the claims you can make, and the desired response. Read the result as an editor. The assistant can produce a draft; the editorial decision still belongs to someone.
Check attribution, claims, and useful difference
Trace factual claims back to the source. Keep direct quotations exact and distinguish a speaker's opinion from evidence about a market. When research introduces a new fact, open the source and check that it supports the sentence you plan to publish.
Compare the proposed assets with one another. Each should give its intended reader a reason to exist. If two posts repeat the same point with a different opening, combine them or choose the stronger version. Distribution needs a plan, not a quota of generated drafts.
Maintain the approved voice examples and source brief as the work changes. Old positioning can survive for months inside a reusable instruction. Put an owner and review date on shared editorial material, and retire examples that no longer represent the brand.
Use cases for Marketing & Content
Complete workflows with their implementation tools listed below. Follow each playbook's setup and review steps.
Generate LinkedIn Ad Angles, Hooks, and Creative Concepts
Turn your positioning and real customer language into a slate of genuinely distinct LinkedIn ad angles, hooks, and creative concepts ready to test.
Tools: Claude, Claude web search, Google SheetsWeekly Competitor Intel Digest, Run by a Claude Routine
You know the competitive-intel chore: someone is supposed to track what competitors shipped this week, and that someone is slammed. This hands the whole job to a Claude Routine that researches with web search, keeps only the moves that change a deal, and drops a cited digest in Slack every week. Nobody owns the chore, and there is no glue to keep alive.
Tools: Claude web search, Claude Routines, Slack (via MCP)Turn One Webinar Into 15+ Content Assets
Turn a single webinar transcript into 15+ ready-to-edit assets: a blog post, social posts, emails, clip scripts, and a FAQ, from one reviewed outline.
Tools: Fathom, Claude, Google DriveLead Enrichment and Routing with a Claude Agent
Lead enrichment is the other half of speed-to-lead, and most teams lose it in a queue. Fire every form fill into a Claude agent that enriches the lead with web research, scores it against your ICP, writes the record to HubSpot over MCP, and pings the right rep in Slack, in seconds. No n8n workflow, no Zapier, no human triaging a queue.
Tools: Claude web research, Claude Code, HubSpot (via MCP), Slack (via MCP)Automate Google Ads Management with AI
Most Google Ads accounts run on a human exporting a report, then clicking. Wire yours to a Claude agent instead: it reads the account through the Google Ads API, writes its own weekly diagnosis, mines the search-terms report for wasted spend, and executes only the changes you approve by ticking a checkbox, negatives, bids, budgets, and pauses, the same week, not next month.
Tools: Google Ads API (GAQL), Google Analytics 4, Claude Code, Claude Code Routines, Google Ads (mutate API)Automate LinkedIn Ads Management with AI
Most LinkedIn ad accounts run on a human reading a dashboard, then clicking. Wire yours to a Claude agent on a weekly routine instead: every Monday it ranks the changes worth making, and executes the ones you approve, bids, budgets, pauses, launches, and audience edits, the same day you approve them, not days later.
Tools: LinkedIn Marketing API, Claude Code, Claude Code Routines, LinkedIn Campaign ManagerThe RevOps Dashboard That Reconciles: A Claude Agent Builds One Number Set from CRM, Ads, Product, and Billing
Every team has three tools that each report 'pipeline' and none of them agree, so the revops dashboard becomes a weekly argument about whose number is right. This play makes the definitions the product: a metric definitions file names one formula, one source of truth, and one owner per metric, and a Claude agent reads the CRM, ad platforms, product usage, and billing over MCP every Monday, computes each metric exactly as written, shows the delta between what each tool claims and what the definition says, and writes one static page plus a Slack diff. No BI license, no dashboard nobody opens. One number set, with the disagreements on the page instead of in the meeting.
Tools: HubSpot or Salesforce (via MCP), LinkedIn and Google Ads exports, Product usage and billing (Stripe via MCP, or a warehouse), metrics.md (the definitions file), Claude Code, A static HTML page + Slack (via MCP)AI Video Ads from One Point of View: A Claude Code Pipeline That Cuts Ten Variants a Week
Most B2B video ads die in the queue: one script, one edit, three weeks, one variant that nobody wanted to test because it cost too much to make. This play turns AI video ads into a pipeline instead. Claude writes a hook matrix from your point of view and your customers' own words, scripts each hook at 6, 15, and 30 seconds with a caption track, and renders the cuts from HTML scenes you own, so ten named variants ship into a test on Monday and the losers cost nothing to kill.
Tools: Your point of view and customer language, Claude Code, Hyperframes, HeyGen or Tavus (optional), LinkedIn Campaign Manager or Meta Ads Manager, The ads skillsRun Your GTM Automations as Claude Agents with MCP
Most GTM automations are a pile of Zapier zaps and n8n flows nobody maintains. Move the logic onto one Claude agent with MCP connectors to your stack: it reads the context, reasons, decides, and writes, all in a brief you can actually read.
Tools: Trigger (webhook or schedule), Claude Code + MCP, HubSpot / Slack / DrivePut Recurring GTM Work on Autopilot with Claude Routines
Every GTM team has a list of recurring chores that quietly slip: the Monday pipeline-risk read, the competitor check, the CRM-hygiene sweep. A Claude Routine runs each one on a schedule as a cloud agent, so the work shows up whether or not anyone remembered it.
Tools: Claude web search / MCP, Claude Routines, Slack / your CRMTurn Your Best GTM Plays into Claude Skills the Whole Team Runs
Your best account brief, battlecard, and follow-up live in one person's head and one clever prompt nobody else can reproduce. Package them as Claude Skills: the play, the format, and the guardrails, versioned and shared, so every rep runs it at the same quality.
Tools: Your best prompts + docs, Claude Skills, Every rep's ClaudeAI Lead Scoring: Score Your Whole Database with a Claude Agent
Most lead scores are a points system someone built in 2021 and nobody trusts, so reps triage the queue by gut anyway. This play replaces it with a Claude agent that scores every lead in your CRM against a three-part model, fit, intent, and engagement, writes the score and a one-line reason back over MCP, re-scores nightly on a Routine, and routes by rule. The reason line is what makes reps stop ignoring the number.
Tools: HubSpot (via MCP), Claude Code, Claude Routines, Slack (via MCP)CRM Data Cleanup on a Schedule: A Claude Agent That Proposes, You Approve
CRM data cleanup is the job every RevOps team owns and nobody schedules, so it happens as a panicked spreadsheet purge the week before the board deck. This play makes it a weekly run: a Claude agent reads the CRM over MCP, finds duplicates, non-standard values, empty fields, orphan records, and dead deals, proposes every fix as a line in a change list with the evidence beside it, and writes only the lines you tick. The database gets cleaner every week, and nothing merges without a human looking at it.
Tools: HubSpot or Salesforce (via MCP), Claude Code, FullEnrich or Clay, Slack (via MCP)Win-Loss Analysis on Evidence: A Quarterly Claude Agent That Codes Every Closed Deal
Every CRM has a loss-reason field, and in most of them 'price' wins by a mile, because it is the first option and the least embarrassing. The real reasons are on the calls. This play puts a Claude agent on every deal closed in the quarter: it reads the CRM fields, the transcripts, and the buyer interviews, codes each deal against a taxonomy you own with the buyer's quote behind every code, and quantifies the patterns by segment and competitor. The report that lands in the QBR says why you actually lost, in the buyer's words, and how often.
Tools: HubSpot or Salesforce (via MCP), Gong or Fireflies (via MCP), Buyer interview notes, Claude Code, Notion + Slack (via MCP)Skills for Marketing & Content
Reusable procedures for the tool or runtime named on each card. Check the setup before adding one to your workflow.
B2B Cold Email Templates in Your Brand Voice
Writes short, relevance-first B2B cold emails in your voice and gives you the cold email templates to start from. Opens with a real observation, not a generic compliment, and refuses to invent personalization.
Sales Battlecard Template, Built From Live Competitor Intel
Fills an honest, rep-ready sales battlecard template against a named competitor: positioning, where they win, discovery traps, objection handling, and landmines to avoid.
LinkedIn Ads Optimization Skill for Claude
Reads a LinkedIn ad account by layer and format, flags what moved week over week, and returns a ranked, evidence-backed list of changes to approve. It classifies before it counts and proposes, never executes.
Google Ads Optimization Skill for Claude
Reads a Google Ads account through the API, writes a dated diagnosis, mines the search-terms report for negatives, and returns a ranked, evidence-backed list of typed changes to approve. It categorizes before it counts and proposes, never executes.
Competitor Monitoring Skill: Diff a Competitor's Public Surface Every Week
Turns competitor monitoring into a weekly diff: the skill reads one competitor's public pages, compares them with the snapshot it saved last run, and returns each change classified, rated for deal impact, and translated into what it means for your reps. Run it by hand, in a Project, or as the brain of a scheduled Routine.
Prompts for Marketing & Content
Individual tasks with required inputs and example outputs. Each prompt lists the assistants it supports.
Define Your ICP and Buyer Personas
Distill real win/loss evidence into an ICP, a buying-committee map, and a scoring model your whole team can act on, built on disqualifiers, not aspiration.
Works with: Claude, ChatGPT, GeminiLinkedIn Post Generator: Turn a Point of View Into a Post
A LinkedIn post generator that turns a raw opinion or experience into a post with a real hook, one sharp idea, and a concrete moment, in your voice, with the cringe stripped out.
Works with: Claude, ChatGPT, GeminiGenerate Ad Copy Variations for a Campaign
Produce genuinely distinct ad variations across testable angles, on-brand and within character limits, plus a test plan and visual ideas for the top angles.
Works with: Claude, ChatGPT, GeminiBattlecard: Build a Rep-Ready One vs Any Competitor
A prompt that builds a rep-ready, no-spin battlecard against a named competitor: where you win, where you honestly lose, the traps to set, and the landmines to avoid.
Works with: Claude, ChatGPT, Gemini, PerplexityAI Content Repurposing: One Transcript Into a Content Engine
AI content repurposing that turns one transcript into a blog post, social posts, an email, pull-quotes, and clip ideas, keeping the original point of view and grounded in the source.
Works with: Claude, ChatGPT, GeminiGuides for your chosen assistant
Follow the guide for the tool you use. A shared workflow directory does not change the setup requirements of an individual playbook.
Claude
- Prompting Claude: what actually moves the needle →The things that reliably improve Claude's output are mostly structural: paste the real source material instead of describing it, state the goal, audience, constraints, and exact output format, show an example of the shape you want, and put long context first with the instruction last.
- Claude Projects: persistent, context-rich workspaces →A Claude Project is a workspace that holds custom instructions and a set of knowledge files, so every chat you start inside it opens already knowing your business, your ICP, your voice, your rules, instead of you re-explaining all of it every time.
- Claude Artifacts: interactive outputs you can ship →A Claude Artifact is a standalone output, a document, a chunk of code, an interactive page, a diagram, that Claude renders in a panel beside the chat instead of burying it in the conversation.
- Web search in Claude: answers beyond the cutoff →Web search lets Claude pull current information from the live web and cite the sources it used, instead of relying only on what it learned in training.
- Claude vs Gemini for GTM: home-field advantage vs the away game →If your GTM runs inside Google Workspace, Gmail, Sheets, Docs, Meet, Gemini has a real home-field advantage: it is already in the side panel of every app you open, on the Google AI Pro plan.
- Build a shared prompt and skill library your GTM team actually uses →A team prompt library works when it is organized around plays, each with one owner, and split across the two containers Claude gives you: Projects hold the context a role shares (ICP, positioning, tone), and Skills hold the repeatable plays (the pre-call brief, the follow-up note, the weekly digest) as versioned files anyone can invoke.
ChatGPT & Codex
- Writing with ChatGPT: drafts, documents and focused revisions →Use Chat for a short drafting conversation and Work when you need a finished document, presentation or PDF.
- ChatGPT custom instructions and prompting: brief the work clearly →Use custom instructions for stable preferences and task prompts for the specific outcome, sources and checks.
- Custom GPTs: package a focused assistant for your team →A custom GPT packages a focused assistant with instructions and configured capabilities.
Frequently asked questions
How do I keep drafts from sounding generic?
Provide a specific argument, supporting material, and examples of your voice. Edit for meaning and rhythm. A request to sound human gives the assistant much less direction than a real brief.
What should I repurpose first?
Start with an asset that already contains clear explanations or evidence: a useful webinar, an interview, or a detailed customer answer. Choose one audience and one derivative format before planning a whole campaign.
Can the same voice brief work across tools?
The written brief and approved examples can be shared source material. Follow the setup guide for the assistant or skill you use, then inspect its output. Reusing a brief does not remove the need to test the resulting drafts.
How should I use research in published content?
Keep a source trail and check each factual claim before publishing. Use the research guides for your chosen tool, preserve attribution, and give an editor responsibility for the final argument and wording.