Edit Collection

Update the details of your collection here.

Title *

Description

Prompts

No prompts in this collection

How to Use

Markdown Content (optional)

This collection guides you through the process of creating a robust Go-to-Market (GTM) strategy from scratch. By following the prompts in order, you will perform deep market research, map your Total Addressable Market (TAM), validate your Ideal Customer Profile (ICP), and generate targeted messaging.

## Output rules

### Subject Line Rules

- Always 1-3 words.
- Provide exactly 3 variations in split-test format: [Option1|Option2|Option3].
- Variations must include one 1-word, one 2-word, one 3-word line.
- No punctuation. Curiosity- or benefit-driven.

### Script Length & Complexity Variations

- If 1 persona provided -> produce 6 variations for that persona:
  - Lengths: ~30 words, ~45 words, ~60 words
  - For each length, write 3 complexity tiers:
    - Simple: Clear, plain English, universally understandable
    - Niche-aware: Uses light industry knowledge/lexicon
    - Hyper-specific: Deeply tailored to the persona's unique challenges (KPI constraints)
- If 2-3 personas provided -> 3 variations per persona (mix lengths/complexities).
- If 5+ personas provided -> 1 variation per persona that still includes the 3 lengths & complexities inside it.

### Structural Elements (include at least 3 per script)

Choose whichever fit the angle best:

- Personalized Hook (8-12 words)
- Social Proof Bridge (15-20 words)
- Value Proposition (10-12 words)
- Front-End Offer (8-12 words)
- Soft CTA (5-8 words; question-based, never a hard call ask)

### Script Priorities

Focus each variation on either:

- A pain-qualified segment (PQS from context), or
- A strong differentiated value proposition the persona cares about.
- CTAs must scale: e.g., "Would it make sense to...", "Open to exploring...", "Worth a peek?"

### Personalization Ideas Section (after all scripts)

Provide a bullet list of personalization ideas with an example for every idea. If you can't give an example, don't include the idea.

Format examples:

- Use [recent_news]: Reference their new funding round.
  - Example: Saw [company_name] just closed a $40M Series B-congrats on the momentum.
- Use [tech_stack]: Show additive fit with their tools.
  - Example: "Looks like you're running HubSpot-our workflow plugs in without new training."
- Use [hiring_signal]: Tie to open roles.
  - Example: "Hiring 3 SDRs suggests pipeline goals-want the 2-page ramp blueprint we give new teams?"
- Use [competitor_touch]: Neighbor proof without namedropping.
  - Example: "Teams like {[peer_company]} cut reply time 37% with the same playbook."

### Reasoning Summary (2-4 sentences)

Explain:

- Why you chose the angles, complexity tiers, and lengths.
- How each aligns with the persona's likely pains or goals from the research.

### Output Format for Each Script

**Script Metadata**

- Persona: [SPECIFIC_ROLE]
- Industry: [SPECIFIC_SECTOR]
- Pain Point: [PRIMARY_CHALLENGE]
- Complexity: [Simple / Niche-Aware / Hyper-Specific]
- Length: [Approx. word count]

Subject Line (spintext): {OneWord|Two Words|Three Word Line}
Email Body (use {{variables}} as needed):

- Keep under 70 words.
- Include at least 3 structural elements (above).
- Use soft, question-based CTA.
- If ~30 words, prefer a single sharp question + 1 line context.

Word Count: [number]
Clay Variables Needed (list):
{{first_name}}, {{company_name}}, {{persona_role}}, {{industry}}, {{recent_news}}, {{tech_stack}}, {{primary_kpi}}, {{core_system}}, {{peer_company}}, {{pqs_trigger}}
(include only those actually used).

### Quality Standards and Guardrails

- 25-69 words per script (strict).
- All {{variables}} must be valid, consistently named, and Clay-merge-safe.
- Use plain language; avoid jargon unless in Hyper-specific tier where it improves trust.
- Each variation must feel meaningfully different (not light rewrites).
- No emojis. No punctuation in subject lines.
- Proof rigor: Social proof must be adjacent (same role/region/size/stack).
- Pains must be current and role-true.
- Offer clarity: Front-end offers must be specific (format + outcome + time requirement).
- Brevity/clarity rule: If a short line feels stilted or vague, do not ship it-choose the 45- or 60-word band for natural flow.

Notes

Tips

Author