Growth-Today/claude-skills / gt-gtm-playbook-builder
gt-gtm-playbook-builder
VerifiedGTM Alpha Playbook Generator by Growth Today (growthtoday.co) — builds comprehensive, signal-based GTM playbooks for any target vendor domain using Clay. Use this skill whenever someone provides a company domain and wants to generate a GTM Alpha playbook, signal framework, buying signal analysis, or Clay-powered outbound strategy for that company. Also triggers on: GTM Alpha, GTM playbook, signal-based selling playbook, buying signals for [domain], Clay playbook, build a playbook for [company], signal framework for [domain], GTM Alpha for [prospect], prospect playbook, generate playbook, playbook for [company name], outbound strategy for [domain]. The output is saved as a Google Doc in a GTM playbooks folder. Do NOT use for general Clay questions (use gt-clay-builder), general cold email writing (use gt-cold-email-writer), or general signal sourcing theory (use gt-buying-signal-sourcer).
| File | Kind | Size |
|---|---|---|
| LICENSE | other | 1.0 KB |
| README.md | markdown | 2.3 KB |
| SKILL.md | skill md | 7.7 KB |
| resources/clay-case-studies.md | markdown | 7.0 KB |
| resources/gtm-alpha-concept.md | markdown | 3.6 KB |
| resources/playbook-prompt-framework.md | markdown | 12.2 KB |
resources/playbook-prompt-framework.md
View on GitHub# GTM Alpha Playbook Generator — Full Prompt Framework v5.0
This is the complete prompt framework that powers playbook generation. Follow it exactly.
---
## Role & Context
You are a world-class GTM strategist and AI automation expert. Your task is to build a comprehensive, industry-specific GTM Alpha Playbook for the company identified by {TARGET_DOMAIN}.
- {TARGET_DOMAIN} represents the vendor selling to prospects (Growth Today's client).
- GTM Alpha is a strategic sales approach focused on identifying and targeting prospects based on behavioral and contextual signals that indicate high buying readiness, rather than traditional demographic targeting.
- Clay/Claygent is the AI-powered data toolset that {TARGET_DOMAIN} will use to execute this strategy.
Your primary objective: create an actionable strategy for how {TARGET_DOMAIN} can leverage Clay to transform their sales results through signal-based GTM, specifically tailored to the industry, market position, and context of the company at {TARGET_DOMAIN}.
---
## Initial Domain Research Protocol
Perform comprehensive research on {TARGET_DOMAIN} before creating any content:
- Core product/service offerings
- Target customer segments and industries
- Specific pain points they address
- Competitive landscape
- Business model and pricing structure
- Recent company news, developments, or market position
Clearly articulate what you've learned about {TARGET_DOMAIN} at the beginning of your playbook, including:
- Primary value proposition
- Key differentiators
- Target customer profile
- Current GTM approach (if discernible)
---
## Strategic Objectives
Create the most high-value, immediately actionable playbook possible that:
- Educates go-to-market teams on GTM Alpha with industry-specific relevance to {TARGET_DOMAIN}
- Maps core pains solved by {TARGET_DOMAIN} to 5-10 high-intent buying signals with clear causal logic
- Only share excellent, unique buying signals that are practical
- Specifies concrete Claygent workflows for each signal using specific data sources
- Designs 3-5 outbound GTM plays with precise trigger conditions
- Plans a phased 30/60/90-day rollout
- Quantifies the competitive advantage of implementing GTM Alpha vs. traditional approaches
---
## Industry-Specific Signal Framework
For {TARGET_DOMAIN}'s specific industry, develop a custom signal framework that addresses:
### Industry Dynamics
- Market trends and disruptions
- Regulatory changes and compliance requirements
- Competitive pressures and consolidation patterns
- Technology adoption cycles
### Buyer Journey Analysis
- Typical evaluation and purchase cycle
- Decision-making process and stakeholders
- Common objections and deal roadblocks
- Budget allocation patterns
### Pain Point Identification
- Industry-specific challenges that trigger buying needs
- Operational inefficiencies that {TARGET_DOMAIN} addresses
- Risk factors and compliance concerns
- Cost/revenue impact of identified problems
### Signal Categories
**Organizational State Shifts:** Changes in company size (hiring/layoffs), funding events, M&A activity, significant leadership appointments/departures.
- Insight: Indicate evolving needs, budget shifts, decision-maker changes, or integration challenges where new solutions are required.
**Operational & Technology Triggers:** Adoption or abandonment of key technologies, infrastructure investments/issues, changes in core operational metrics or processes, supply chain events.
- Insight: Point to specific pain points with current systems, capacity constraints, or strategic pivots requiring operational adjustments and supporting tools.
**Strategic & Initiative Focus:** Launch of new products/services/programs, expansion into new markets/geographies, announcement of major strategic initiatives (e.g., digital transformation, sustainability goals).
- Insight: Reveal new organizational priorities, allocated budgets, and specific goals that your solution can directly support.
**External Mandates & Risk Events:** New regulatory requirements, compliance failures, significant competitive moves, major market disruptions, shifts in geopolitical factors impacting operations.
- Insight: Create urgency, expose compliance gaps, or necessitate rapid adaptation, driving a need for solutions that mitigate risk or enable compliance/agility.
**Engagement & Intent Signals:** Specific interactions with your company (website activity on key pages, content downloads, webinar attendance) or third-party indicators of active research (intent data, review site activity, job postings mentioning relevant skills).
- Insight: Directly indicate active interest, problem recognition, and position in the buyer journey, enabling timely and contextually relevant outreach.
---
## Enhanced Email Framework
For each Play's email template, use this strategic structure:
```
{first_name} – {Opening with SPECIFIC signal discovered about their company}
Based on {specifics of what we found}, you're likely facing {precise pain point} which typically costs companies like yours {quantified cost/impact}.
{Poke the Bear question that forces them to confront their pain}
We've helped {competitor or similar company} achieve {specific, impressive metric} by solving this exact challenge using our solution.
{Low-friction CTA with clear next step that promises immediate value}
```
**"Poke the Bear" Guidelines:**
- Target a high-stakes nuance, not a generic pain
- Phrase as "How are you handling…?", "What's your plan when…?", or "Curious how you avoid…?"
- Make it impossible to dismiss — trigger genuine self-reflection
---
## Signal Quality Assessment Criteria
For each proposed signal, evaluate against these criteria:
| Criterion | Definition |
|-----------|-----------|
| Precision | Pinpoints a distinct condition, event, or change? (Evaluates granularity and clarity) |
| Problem/Opportunity Alignment | Directly indicates a need, pain point, or strategic goal {TARGET_DOMAIN} addresses? (Ensures strategic relevance) |
| Temporal Relevance | Signals present need or imminent opportunity? (Focuses on timing for action) |
| Detectability | Reliably detectable & verifiable (esp. via platforms like Clay)? (Confirms operational feasibility) |
| Actionability | Enables specific, tailored GTM actions (targeting/messaging)? (Links signal to execution) |
| Predictive Power | Statistically correlates with future engagement or conversion? (Measures potential for Alpha outcomes) |
| Defensibility | Leveragable for a defensible GTM advantage? (Assesses contribution to unfair advantage) |
---
## High-Intent Signal Examples
Focus on combining multiple signals that together indicate true buying readiness:
### Creative Signal Types
1. **Shadow GTM Shifts** — Look for sudden changes in language on partner or reseller sites (new SKUs, altered descriptions) that hint at GTM realignment. Examples: an implementation partner removing "certified [Competitor] integrator," or a new reseller launching a productized onboarding for your category.
2. **Internal Chaos Markers** — Detect early signs of operational distress: support forums flooded with complaints about tool limitations, Glassdoor reviews from engineers citing legacy infra pain, or execs stepping down from data/compliance roles. Pain often leaks before the press release.
3. **Stakeholder Power Consolidation** — Identify new hires or promotions that consolidate budget authority across previously siloed functions (e.g. VP of "Revenue Systems" owning both GTM tooling + Finance). These org shifts signal an upcoming buying window for platforms that unify workflows.
4. **Externalized Friction Workarounds** — Watch for publicly visible hacks or kludges: Notion pages with manual processes, Zapier-heavy workflows in community showcases, or Airtable templates solving problems your product automates. This signals high motivation to replace janky ops with real infra.
5. **Competitive Framing in Public Messaging** — Track when prospects begin to echo your messaging — even if they don't use your product. If a company starts referencing your category language in job posts or blogs, they're likely influenced by your category narrative and warming up.
### Standard Signal Types
**Business Signals:**
- Funding announcement with headcount surges in aligned teams
- Executive hire with tooling ownership + stated intent to modernize
- Office relocation/expansion citing operational inefficiencies
- Earnings call flagging scaling bottlenecks or cost inefficiencies
- Customer reviews naming process pain or workaround hacks
**Regulatory & Risk Signals:**
- Public breach disclosure tied to a failure point your tech secures
- Regulatory fine or warning mapping to a missing control your solution provides
- DPA inquiry or audit request revealing compliance gaps
- Looming compliance deadline + visible unreadiness
- SEC filing updates showing new language on risk/controls
**Competitive Signals:**
- Competitor tool adoption + public complaints about limitations
- Competitor outage + real-time user churn signals
- Known contract expiration + vendor-switching language in job posts
- Competitor price hikes + procurement friction signals
- Review site comparisons citing specific competitor weakness you dominate
**Tech & Infrastructure:**
- Shifts in tech stack, DNS/hosting changes, open-source activity, public API changes
**Talent & Structure:**
- Job postings detailing challenges, hiring sprees in relevant units, key personnel changes
**Strategy & Investment:**
- Public statements on priorities/budgets, M&A impact, investor day themes
**Market & Operations:**
- Website activity/intent data, changes in pricing/service models, customer feedback analysis, new partnerships
**Product & Innovation:**
- Patent filings, research papers, conference talks on technical hurdles, early product/feature announcements
---
## Required Output Structure
### 1. Executive Summary
- Industry-specific GTM Alpha approach for {TARGET_DOMAIN}
### 2. {TARGET_DOMAIN} Business Analysis
- Company profile and positioning
- Product/service offering analysis
- Current GTM approach assessment
- Target customer persona development
### 3. Signal Intelligence Framework (Table Format)
For each signal include:
- Signal name and description
- Causal logic (why this signal indicates buying intent for {TARGET_DOMAIN}'s solution)
- Clay/Claygent detection workflow (specific data sources, enrichment steps)
- Signal quality score against assessment criteria
- Threshold conditions for triggering outreach
### 4. GTM Playbook (3-5 Plays)
Each play must include:
- Signal trigger combination with threshold conditions
- Custom email template using the enhanced framework
- Personalization strategy with variable mapping
- Multi-channel orchestration plan
### 5. Implementation Validation Framework
- Expected signal volume based on TAM size
- A/B testing framework to validate signal quality
- "Go/No-Go" decision criteria for scaling each play
### 6. Execution Plan
- Week-by-week implementation steps for 30/60/90 days
- Role assignments and responsibilities
### 7. Competitive Intelligence Analysis
- Performance delta between traditional GTM vs. GTM Alpha
- "Left Behind" scenarios: consequences of delay
### 8. Final Recap
- Competitive edge summary
- Why Clay uniquely enables GTM Alpha for {TARGET_DOMAIN}
---
## Quality Control
### DO NOT:
- Attribute Clay's case-study wins to {TARGET_DOMAIN}
- Use vague signals like "fast-growing company"
- Skip causal explanations between signals and buying intent
- Create generic playbooks not tailored to {TARGET_DOMAIN}'s industry
- Suggest illegal or unethical data collection methods
- Propose signals without specific Clay implementation steps
### DO:
- Create highly specific signal thresholds (e.g., "SEC filing mentions 'data security' 3+ times AND CIO changed in last 90 days")
- Develop multi-signal scoring models that increase intent prediction accuracy
- Adapt all recommendations to {TARGET_DOMAIN}'s specific industry and product
- Include practical examples tailored to {TARGET_DOMAIN}'s ideal customer profile
- Create a playbook so valuable that prospects would pay thousands of dollars for it
---
*Created by [Growth Today](https://www.growthtoday.co) — AI-native GTM engineering firm. Maintained and updated by [Brigitta Ruha](https://www.linkedin.com/in/brigittaruha/). More open Claude Skills for go-to-market teams: https://www.growthtoday.co/claude-skills*
Related skills
| Skill | Stars | Updated | Works with | Status | Install |
|---|---|---|---|---|---|
| reverse-engineer-anythingmorluto/reaReverse engineer native, managed, Electron/JavaScript, packaged, firmware, and browser targets with REA, and build agent environments (AgentEnv bundles) of web applications from a live instance or a capture, and of Linux desktop apps with a task from a request. Use shipped-artifact or requested runtime evidence to explain features, compare versions, decompile code, or guide a reconstruction. Skip REA for ordinary source-repository architecture analysis. | Stars: 472k | Updated | Claude CodeCodex | Verified | Install |
| diagnosing-superpowersobra/superpowersUse when a superpowers session went wrong and your human partner wants to know why — repeated work, ignored plans, stumbles, poor results, a skill that didn't fire, "it took too long", "why is it so expensive", "what is it doing" — or wants to build a bug report for the superpowers maintainers, for the current session or a past one identified by id or path, on any harness. | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| dispatching-parallel-agentsobra/superpowersUse when facing 2+ independent tasks that can be worked on without shared state or sequential dependencies | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |
| executing-plansobra/superpowersUse when executing an implementation plan in the current session as the implementer yourself — your human partner chose inline execution, or no subagent tool is available | Stars: 323k | Updated | Claude CodeCodex | Verified | Install |