@growthub/cli 0.3.37 → 0.3.39
This diff represents the content of publicly available package versions that have been released to one of the supported registries. The information contained in this diff is provided for informational purposes only and reflects changes between package versions as they appear in their respective public registries.
- package/README.md +26 -2
- package/assets/worker-kits/growthub-email-marketing-v1/brands/_template/brand-kit.md +172 -0
- package/assets/worker-kits/growthub-email-marketing-v1/brands/growthub/VERSION.md +32 -0
- package/assets/worker-kits/growthub-email-marketing-v1/brands/growthub/brand-kit.md +282 -0
- package/assets/worker-kits/growthub-email-marketing-v1/broadcasts/_template/broadcast-vault.md +188 -0
- package/assets/worker-kits/growthub-email-marketing-v1/broadcasts/growthub/broadcast-vault.md +324 -0
- package/assets/worker-kits/growthub-email-marketing-v1/bundles/growthub-email-marketing-v1.json +66 -0
- package/assets/worker-kits/growthub-email-marketing-v1/examples/campaign-brief-sample.md +110 -0
- package/assets/worker-kits/growthub-email-marketing-v1/examples/nurture-sequence-sample.md +265 -0
- package/assets/worker-kits/growthub-email-marketing-v1/examples/subject-line-matrix-sample.md +116 -0
- package/assets/worker-kits/growthub-email-marketing-v1/growthub-meta/README.md +108 -0
- package/assets/worker-kits/growthub-email-marketing-v1/growthub-meta/kit-standard.md +87 -0
- package/assets/worker-kits/growthub-email-marketing-v1/kit.json +101 -0
- package/assets/worker-kits/growthub-email-marketing-v1/output/growthub/showcase-proof-ai-ugc-v1-20260410/Growthub_Broadcast_ShowcaseProof_v1_20260410.md +139 -0
- package/assets/worker-kits/growthub-email-marketing-v1/output/growthub/showcase-proof-ai-ugc-v1-20260410/Growthub_CampaignBrief_ClientResults_v1_20260410.md +115 -0
- package/assets/worker-kits/growthub-email-marketing-v1/output/growthub/showcase-proof-ai-ugc-v1-20260410/Growthub_SubjectLineMatrix_v1_20260410.md +83 -0
- package/assets/worker-kits/growthub-email-marketing-v1/output-standards.md +174 -0
- package/assets/worker-kits/growthub-email-marketing-v1/runtime-assumptions.md +268 -0
- package/assets/worker-kits/growthub-email-marketing-v1/skills.md +490 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/broadcast-formats/INDEX.md +75 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/broadcast-formats/activation-booking.md +156 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/broadcast-formats/engagement-nudge.md +175 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/broadcast-formats/lead-magnet-traffic.md +149 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/broadcast-formats/showcase-proof.md +153 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/broadcast-formats/value-delivery.md +141 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/campaign-brief-template.md +115 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/cta-matrix.md +90 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/email-draft.md +145 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/email-formats/INDEX.md +59 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/email-formats/follow-up-sequence.md +111 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/email-formats/nurture-sequence.md +143 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/email-formats/outbound-cold-sequence.md +134 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/email-formats/promotional-broadcast.md +117 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/email-formats/re-engagement.md +108 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/email-modules/INDEX.md +97 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/email-modules/body/education-block.md +131 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/email-modules/body/problem-agitate.md +107 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/email-modules/body/story-bridge.md +112 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/email-modules/body/value-reveal.md +107 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/email-modules/cta/primary-cta.md +116 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/email-modules/cta/reply-cta.md +131 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/email-modules/cta/soft-cta.md +117 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/email-modules/subject-lines/curiosity.md +112 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/email-modules/subject-lines/personal.md +108 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/email-modules/subject-lines/social-proof.md +109 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/email-modules/subject-lines/urgency.md +112 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/hooks-library/subject-line-patterns.csv +73 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/qa-checklist.md +106 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/sequence-planner.md +94 -0
- package/assets/worker-kits/growthub-email-marketing-v1/templates/subject-line-matrix.md +136 -0
- package/assets/worker-kits/growthub-email-marketing-v1/workers/email-marketing-strategist/CLAUDE.md +294 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/.env.example +9 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/QUICKSTART.md +85 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/brands/NEW-CLIENT.md +46 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/brands/_template/brand-kit.md +89 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/brands/growthub/brand-kit.md +96 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/bundles/growthub-open-higgsfield-studio-v1.json +57 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/docs/open-higgsfield-fork-integration.md +63 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/docs/provider-adapter-layer.md +67 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/examples/platform-ready-handoff-sample.md +24 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/examples/prompt-matrix-sample.md +6 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/examples/shot-plan-sample.md +7 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/examples/visual-campaign-brief-sample.md +22 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/growthub-meta/README.md +67 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/growthub-meta/kit-standard.md +47 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/kit.json +106 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/output/README.md +34 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/output-standards.md +133 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/runtime-assumptions.md +108 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/setup/check-deps.sh +37 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/setup/clone-fork.sh +27 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/setup/verify-env.mjs +72 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/skills.md +257 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/templates/asset-tracking.md +5 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/templates/frame-analysis.md +24 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/templates/generation-batch-plan.md +7 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/templates/model-selection-recommendation.md +23 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/templates/platform-ready-execution-handoff.md +17 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/templates/prompt-matrix.md +7 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/templates/prompt-templates/cinema-generation.md +16 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/templates/prompt-templates/image-generation.md +11 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/templates/prompt-templates/lip-sync-generation.md +14 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/templates/prompt-templates/video-generation.md +11 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/templates/review-qa-checklist.md +26 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/templates/shot-plan.md +11 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/templates/studio-selection-brief.md +18 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/templates/visual-campaign-brief.md +24 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/validation-checklist.md +49 -0
- package/assets/worker-kits/growthub-open-higgsfield-studio-v1/workers/open-higgsfield-studio-operator/CLAUDE.md +264 -0
- package/package.json +1 -1
package/assets/worker-kits/growthub-email-marketing-v1/templates/email-modules/cta/reply-cta.md
ADDED
|
@@ -0,0 +1,131 @@
|
|
|
1
|
+
# CTA Module — Reply CTA
|
|
2
|
+
|
|
3
|
+
**Module type:** CTA
|
|
4
|
+
**CTA ID:** `reply-cta`
|
|
5
|
+
**What it does:** A conversational ask — invites the reader to reply to the email. The lowest-commitment CTA. Creates engagement signals and starts a real 1:1 conversation.
|
|
6
|
+
**Use in:** Cold outbound Email 1, re-engagement emails, sequences where conversation > conversion
|
|
7
|
+
**Commitment level:** Low
|
|
8
|
+
**Pairs with:** PS line (often the CTA itself lives in the PS)
|
|
9
|
+
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
## HOW REPLY CTAs WORK
|
|
13
|
+
|
|
14
|
+
Reply CTAs work because they lower the barrier to engagement to almost zero. There's no link to click, no form to fill, no calendar to navigate. Just a question or a prompt to respond to.
|
|
15
|
+
|
|
16
|
+
They work especially well when:
|
|
17
|
+
- The audience is cold and hasn't engaged with the brand yet
|
|
18
|
+
- The email wants an engagement signal before escalating to a higher-commitment ask
|
|
19
|
+
- The sequence is conversational in tone (cold outbound, re-engagement)
|
|
20
|
+
|
|
21
|
+
**The reply CTA serves two goals:**
|
|
22
|
+
1. Engagement signal — a reply improves sender reputation and signals interest
|
|
23
|
+
2. Conversation starter — the reply initiates a real 1:1 exchange that can move to a call
|
|
24
|
+
|
|
25
|
+
---
|
|
26
|
+
|
|
27
|
+
## TEMPLATES
|
|
28
|
+
|
|
29
|
+
### The Single Question
|
|
30
|
+
|
|
31
|
+
```
|
|
32
|
+
[One specific, easy-to-answer question about their situation]
|
|
33
|
+
```
|
|
34
|
+
|
|
35
|
+
Variants:
|
|
36
|
+
- `Reply and tell me — what's the biggest creative bottleneck right now?`
|
|
37
|
+
- `Quick question: what's stopping you from scaling spend this quarter?`
|
|
38
|
+
- `Reply with a yes/no — is [PAIN_POINT] something you're actively working on?`
|
|
39
|
+
- `One question: if you could fix one thing in your [creative/growth/pipeline] process right now, what would it be?`
|
|
40
|
+
|
|
41
|
+
---
|
|
42
|
+
|
|
43
|
+
### The Yes/No Option
|
|
44
|
+
|
|
45
|
+
```
|
|
46
|
+
Reply with [YES_OPTION] or [NO_OPTION] — and I'll send you [what happens next].
|
|
47
|
+
```
|
|
48
|
+
|
|
49
|
+
Variants:
|
|
50
|
+
- `Reply "yes" if this is relevant and I'll send you [next step].`
|
|
51
|
+
- `Reply "yes" or "not yet" — either answer is useful.`
|
|
52
|
+
- `If this resonates, reply with [Y]. If not, reply with [N] and I won't keep sending.`
|
|
53
|
+
- `Still [RELEVANT_SITUATION]? Reply "yes" and I'll pick this back up.`
|
|
54
|
+
|
|
55
|
+
---
|
|
56
|
+
|
|
57
|
+
### The Re-engagement Ask
|
|
58
|
+
|
|
59
|
+
```
|
|
60
|
+
[Direct, honest question about whether they're still interested]
|
|
61
|
+
```
|
|
62
|
+
|
|
63
|
+
Variants:
|
|
64
|
+
- `Still relevant, [First Name]?`
|
|
65
|
+
- `One quick question — still thinking about [TOPIC]?`
|
|
66
|
+
- `I'll keep this short: still interested in [DESIRED_OUTCOME]? Reply and let me know.`
|
|
67
|
+
- `Is [TOPIC] still on the table for you? Yes, no, or later — any answer works.`
|
|
68
|
+
|
|
69
|
+
---
|
|
70
|
+
|
|
71
|
+
### The "Last Email" Ask
|
|
72
|
+
|
|
73
|
+
```
|
|
74
|
+
[Acknowledge this is the last contact — give them an easy way to respond or exit]
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
Variants:
|
|
78
|
+
- `Last email from me on this — if [SITUATION] is still something you're working on, reply and I'll make this worth your time.`
|
|
79
|
+
- `I'll leave the door open: if this ever becomes relevant, reply to this email and we'll pick it up.`
|
|
80
|
+
- `No hard feelings if the timing isn't right — just reply with "later" and I'll follow up in 90 days.`
|
|
81
|
+
|
|
82
|
+
---
|
|
83
|
+
|
|
84
|
+
## PS LINE AS THE CTA
|
|
85
|
+
|
|
86
|
+
For reply CTA emails, the reply ask often works best in the PS line — the email delivers value and the PS makes the low-commitment ask.
|
|
87
|
+
|
|
88
|
+
**PS template:**
|
|
89
|
+
```
|
|
90
|
+
P.S. [Quick, specific reply ask — 1 sentence.]
|
|
91
|
+
```
|
|
92
|
+
|
|
93
|
+
Examples:
|
|
94
|
+
- `P.S. Reply and tell me — is creative bottleneck the actual constraint, or is it something else? One word is fine.`
|
|
95
|
+
- `P.S. If this sounds like your situation, just reply with "yes" and I'll send you the next thing.`
|
|
96
|
+
- `P.S. This is my last email on this topic — if the timing is ever right, just reply to this and I'll pick it back up.`
|
|
97
|
+
|
|
98
|
+
---
|
|
99
|
+
|
|
100
|
+
## GROWTHUB-SPECIFIC REPLY CTA EXAMPLES
|
|
101
|
+
|
|
102
|
+
**Cold outbound Email 1:**
|
|
103
|
+
```
|
|
104
|
+
Reply and tell me — is creative throughput the bottleneck right now, or is the constraint somewhere else?
|
|
105
|
+
```
|
|
106
|
+
|
|
107
|
+
**Re-engagement Email 1:**
|
|
108
|
+
```
|
|
109
|
+
One question: is this still on your radar, or has the situation changed? Either answer helps me figure out if there's something useful I can send your way.
|
|
110
|
+
```
|
|
111
|
+
|
|
112
|
+
**Re-engagement Email 3 (last email):**
|
|
113
|
+
```
|
|
114
|
+
Last email from me on this, [First Name]. If the timing is ever right — just reply to this. I'll pick it up wherever you are.
|
|
115
|
+
```
|
|
116
|
+
|
|
117
|
+
**Cold outbound — the yes/no version:**
|
|
118
|
+
```
|
|
119
|
+
Reply with "yes" if the creative production speed is something you're actively trying to solve — and I'll send you something that might help. Reply "no" and I'll leave you alone.
|
|
120
|
+
```
|
|
121
|
+
|
|
122
|
+
---
|
|
123
|
+
|
|
124
|
+
## RULES
|
|
125
|
+
|
|
126
|
+
- Reply CTAs require no URL — the ask is to reply to the email
|
|
127
|
+
- Always make it easy to say "no" — a graceful exit option improves both replies AND list hygiene
|
|
128
|
+
- The question must be easy to answer — one word, one sentence, or a binary choice
|
|
129
|
+
- Do not stack a reply CTA on top of another CTA in the same email — one CTA per email
|
|
130
|
+
- Reply CTA emails should be short — a long email followed by "just reply with one word" feels incongruent
|
|
131
|
+
- After a reply, escalate the conversation — route to the primary CTA or book the call
|
package/assets/worker-kits/growthub-email-marketing-v1/templates/email-modules/cta/soft-cta.md
ADDED
|
@@ -0,0 +1,117 @@
|
|
|
1
|
+
# CTA Module — Soft CTA
|
|
2
|
+
|
|
3
|
+
**Module type:** CTA
|
|
4
|
+
**CTA ID:** `soft-cta`
|
|
5
|
+
**What it does:** A lower-commitment ask — read a resource, watch a video, download a framework, or take a small next step. Builds momentum before asking for a call or demo.
|
|
6
|
+
**Use in:** Nurture emails 1–3, cold outbound emails 1–2, educational campaigns, re-engagement email 1–2
|
|
7
|
+
**Commitment level:** Medium
|
|
8
|
+
**Pairs with:** PS line (optional but recommended)
|
|
9
|
+
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
## HOW SOFT CTAs WORK
|
|
13
|
+
|
|
14
|
+
Soft CTAs work in early-stage emails because they give the reader a way to move forward without a high-commitment ask. They're useful when:
|
|
15
|
+
- The audience is not yet warm enough for a call ask
|
|
16
|
+
- The email is educational and the CTA should match the content
|
|
17
|
+
- You want to test engagement signals (clicks on a resource) before escalating to a primary CTA
|
|
18
|
+
|
|
19
|
+
The soft CTA earns the primary CTA in the next email.
|
|
20
|
+
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
## TEMPLATES
|
|
24
|
+
|
|
25
|
+
### Resource / Read
|
|
26
|
+
|
|
27
|
+
```
|
|
28
|
+
[Resource description] → [URL]
|
|
29
|
+
```
|
|
30
|
+
|
|
31
|
+
Variants:
|
|
32
|
+
- `Read the full breakdown → [URL]`
|
|
33
|
+
- `Download the [FRAMEWORK_NAME] framework → [URL]`
|
|
34
|
+
- `See the full case study → [URL]`
|
|
35
|
+
- `Get the [GUIDE/CHECKLIST/PLAYBOOK] → [URL]`
|
|
36
|
+
- `Read: [title of article or resource] → [URL]`
|
|
37
|
+
|
|
38
|
+
---
|
|
39
|
+
|
|
40
|
+
### Watch / Demo
|
|
41
|
+
|
|
42
|
+
```
|
|
43
|
+
Watch: [description] (3 min) → [URL]
|
|
44
|
+
```
|
|
45
|
+
|
|
46
|
+
Variants:
|
|
47
|
+
- `Watch the 3-minute walkthrough → [URL]`
|
|
48
|
+
- `See [OUTCOME] in action → [URL]`
|
|
49
|
+
- `Watch: how [BRAND_TYPE] did [RESULT] → [URL]`
|
|
50
|
+
|
|
51
|
+
---
|
|
52
|
+
|
|
53
|
+
### Micro-commitment
|
|
54
|
+
|
|
55
|
+
```
|
|
56
|
+
[Small, low-friction next step] → [URL or action]
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
Variants:
|
|
60
|
+
- `Take the 2-minute assessment → [URL]`
|
|
61
|
+
- `See if [BRAND_NAME] is a fit for your account → [URL]`
|
|
62
|
+
- `Check if your setup qualifies → [URL]`
|
|
63
|
+
|
|
64
|
+
---
|
|
65
|
+
|
|
66
|
+
## PS LINE PAIRING
|
|
67
|
+
|
|
68
|
+
The PS line for a soft CTA email often does one of two things:
|
|
69
|
+
1. Adds a soft version of the primary CTA (plants the seed for the next email's ask)
|
|
70
|
+
2. Reinforces the resource with a specific reason it's worth consuming
|
|
71
|
+
|
|
72
|
+
**PS templates:**
|
|
73
|
+
|
|
74
|
+
```
|
|
75
|
+
P.S. [Reason the resource is specifically worth reading/watching for this audience.]
|
|
76
|
+
```
|
|
77
|
+
|
|
78
|
+
Or, if planting the seed for the primary CTA:
|
|
79
|
+
|
|
80
|
+
```
|
|
81
|
+
P.S. If after [reading/watching] this you want to see how we'd apply it to [THEIR SITUATION], reply and I'll send you the next step.
|
|
82
|
+
```
|
|
83
|
+
|
|
84
|
+
---
|
|
85
|
+
|
|
86
|
+
## GROWTHUB-SPECIFIC SOFT CTA EXAMPLES
|
|
87
|
+
|
|
88
|
+
**Educational / Pillar 4:**
|
|
89
|
+
```
|
|
90
|
+
Download the creative intelligence framework → [URL]
|
|
91
|
+
|
|
92
|
+
P.S. This is the same framework we use to brief every campaign. Take it and apply it — if you want to see how we'd use it on your account specifically, reply and we can go from there.
|
|
93
|
+
```
|
|
94
|
+
|
|
95
|
+
**Resource in a nurture sequence:**
|
|
96
|
+
```
|
|
97
|
+
Read the full case study → [URL]
|
|
98
|
+
|
|
99
|
+
P.S. The specific part worth reading: how the intelligence layer changed the briefing process. That's the part most people skip — and why most testing programs don't compound.
|
|
100
|
+
```
|
|
101
|
+
|
|
102
|
+
**Mid-sequence engagement check:**
|
|
103
|
+
```
|
|
104
|
+
Watch: how we rebuilt this brand's creative pipeline (3 min) → [URL]
|
|
105
|
+
|
|
106
|
+
P.S. If this looks like your situation, we can walk through what it would look like for your account — no commitment needed. Reply with "show me" and I'll send you the details.
|
|
107
|
+
```
|
|
108
|
+
|
|
109
|
+
---
|
|
110
|
+
|
|
111
|
+
## RULES
|
|
112
|
+
|
|
113
|
+
- Soft CTA is appropriate in emails 1–3 of nurture and cold sequences — do not use primary CTAs too early
|
|
114
|
+
- Resource or content behind the soft CTA must be real, relevant, and available
|
|
115
|
+
- "Download" and "Watch" CTAs require the asset to exist before the email goes live — confirm before platform handoff
|
|
116
|
+
- PS line for soft CTA emails is optional but recommended — plant the seed for the next escalation
|
|
117
|
+
- Soft CTA does not replace the primary CTA in the email — it IS the CTA for this email (one CTA per email)
|
|
@@ -0,0 +1,112 @@
|
|
|
1
|
+
# Subject Line Module — Curiosity
|
|
2
|
+
|
|
3
|
+
**Module type:** Subject line
|
|
4
|
+
**Type tag:** `curiosity`
|
|
5
|
+
**What it does:** Opens a loop the reader must close. Creates a tension or gap between what they know and what they need to know. The answer is in the email.
|
|
6
|
+
**Best used for:** Nurture (emails 1–3), educational pillar campaigns, cold outbound (email 1–2), re-engagement
|
|
7
|
+
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
## HOW CURIOSITY SUBJECT LINES WORK
|
|
11
|
+
|
|
12
|
+
A curiosity subject line creates an open question or an incomplete thought. The reader's brain wants closure. The only way to get it is to open the email.
|
|
13
|
+
|
|
14
|
+
**Three patterns that work:**
|
|
15
|
+
|
|
16
|
+
1. **The knowledge gap** — "The thing most [role] miss about [topic]"
|
|
17
|
+
2. **The unexpected reframe** — "Your [X] problem isn't actually a [X] problem"
|
|
18
|
+
3. **The half-reveal** — "Why [outcome they want] is easier than you think (one thing)"
|
|
19
|
+
|
|
20
|
+
**What kills curiosity subject lines:**
|
|
21
|
+
- Being too vague ("Something interesting for you")
|
|
22
|
+
- Clickbait that the email doesn't deliver on
|
|
23
|
+
- Questions that are too broad ("Are you struggling with growth?")
|
|
24
|
+
- Questions the reader can answer without opening ("Do you want more clients?")
|
|
25
|
+
|
|
26
|
+
---
|
|
27
|
+
|
|
28
|
+
## TEMPLATES
|
|
29
|
+
|
|
30
|
+
### Pattern 1 — The Knowledge Gap
|
|
31
|
+
|
|
32
|
+
**Structure:** `The [adjective] thing most [PERSONA_ROLE] miss about [TOPIC]`
|
|
33
|
+
|
|
34
|
+
Variants:
|
|
35
|
+
- `The thing most [PERSONA_ROLE] miss about [TOPIC]`
|
|
36
|
+
- `What nobody tells [PERSONA_ROLE] about [DESIRED_OUTCOME]`
|
|
37
|
+
- `The [TOPIC] mistake most [PERSONA_ROLE] are making right now`
|
|
38
|
+
- `Why [COMMON_APPROACH] isn't moving the needle for [PERSONA_ROLE]`
|
|
39
|
+
|
|
40
|
+
---
|
|
41
|
+
|
|
42
|
+
### Pattern 2 — The Unexpected Reframe
|
|
43
|
+
|
|
44
|
+
**Structure:** `Your [PAIN_POINT] isn't actually a [PAIN_POINT] problem`
|
|
45
|
+
|
|
46
|
+
Variants:
|
|
47
|
+
- `Your [PAIN_POINT] problem isn't what you think it is`
|
|
48
|
+
- `This isn't a [COMMON_DIAGNOSIS] problem — it's a [REAL_CAUSE] problem`
|
|
49
|
+
- `[Common belief] is wrong. Here's what's actually happening.`
|
|
50
|
+
- `We've been thinking about [TOPIC] backwards`
|
|
51
|
+
|
|
52
|
+
---
|
|
53
|
+
|
|
54
|
+
### Pattern 3 — The Half-Reveal
|
|
55
|
+
|
|
56
|
+
**Structure:** `[DESIRED_OUTCOME] is [easier/faster/simpler] than you think (here's the one thing)`
|
|
57
|
+
|
|
58
|
+
Variants:
|
|
59
|
+
- `[DESIRED_OUTCOME] is closer than you think — one thing`
|
|
60
|
+
- `The fastest path to [DESIRED_OUTCOME] (not what most people do)`
|
|
61
|
+
- `There's a shortcut to [DESIRED_OUTCOME] — here's what it is`
|
|
62
|
+
- `One change that affects [DESIRED_OUTCOME] more than anything else`
|
|
63
|
+
|
|
64
|
+
---
|
|
65
|
+
|
|
66
|
+
## GROWTHUB-SPECIFIC EXAMPLES
|
|
67
|
+
|
|
68
|
+
**Pillar 1 — Growth System:**
|
|
69
|
+
- `The thing most agency owners miss about scaling`
|
|
70
|
+
- `Your growth problem isn't actually a growth problem`
|
|
71
|
+
- `Why systematizing this one thing changes everything`
|
|
72
|
+
|
|
73
|
+
**Pillar 2 — Automation & AI:**
|
|
74
|
+
- `The bottleneck most performance teams don't see coming`
|
|
75
|
+
- `Why your creative process is slower than it looks`
|
|
76
|
+
- `Faster than you think (one thing about creative testing)`
|
|
77
|
+
|
|
78
|
+
**Pillar 4 — Education & Strategy:**
|
|
79
|
+
- `The framework behind every high-win-rate creative program`
|
|
80
|
+
- `What brands scaling to $500K in spend do differently`
|
|
81
|
+
- `Nobody talks about this part of the creative process`
|
|
82
|
+
|
|
83
|
+
**Pillar 5 — Pipeline & Revenue:**
|
|
84
|
+
- `Why your pipeline isn't dead — it's just quiet`
|
|
85
|
+
- `The follow-up mistake that kills more deals than anything`
|
|
86
|
+
- `There is more revenue in your list than you think`
|
|
87
|
+
|
|
88
|
+
---
|
|
89
|
+
|
|
90
|
+
## PREVIEW TEXT PAIRING
|
|
91
|
+
|
|
92
|
+
Curiosity subject lines pair best with preview text that:
|
|
93
|
+
- Extends the loop (adds one more detail that deepens the hook)
|
|
94
|
+
- Teases the resolution without giving it away
|
|
95
|
+
- Confirms this email is for them specifically
|
|
96
|
+
|
|
97
|
+
**Example pairings:**
|
|
98
|
+
|
|
99
|
+
| Subject | Preview |
|
|
100
|
+
|---|---|
|
|
101
|
+
| The thing most agency owners miss about scaling | It's not the budget. It's not the team. It's this. |
|
|
102
|
+
| Your growth problem isn't actually a growth problem | The real constraint is two steps upstream from where you're looking. |
|
|
103
|
+
| Why your creative process is slower than it looks | Most brands find out too late — here's where the delay actually lives. |
|
|
104
|
+
|
|
105
|
+
---
|
|
106
|
+
|
|
107
|
+
## RULES
|
|
108
|
+
|
|
109
|
+
- Subject line must deliver on the curiosity in the email body — never bait-and-switch
|
|
110
|
+
- Keep under 50 characters for mobile (test at 40 if close)
|
|
111
|
+
- Avoid starting with "The" in consecutive emails of the same sequence
|
|
112
|
+
- Do not stack multiple curiosity hooks in the same subject line — pick one
|
|
@@ -0,0 +1,108 @@
|
|
|
1
|
+
# Subject Line Module — Personal
|
|
2
|
+
|
|
3
|
+
**Module type:** Subject line
|
|
4
|
+
**Type tag:** `personal`
|
|
5
|
+
**What it does:** Speaks directly to the individual — their role, situation, or specific context. Feels like a 1:1 message, not a broadcast.
|
|
6
|
+
**Best used for:** Cold outbound (email 1), re-engagement (email 1), post-demo follow-up (email 1), and any email where the segment is small and specific enough to personalize
|
|
7
|
+
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
## HOW PERSONAL SUBJECT LINES WORK
|
|
11
|
+
|
|
12
|
+
Personal subject lines work because they feel like they were written for one person, not a list. The key is specificity — naming the role, the situation, or the context that only applies to this segment.
|
|
13
|
+
|
|
14
|
+
The best personal subject lines do not use hollow personalization ("Hey [First Name], I saw your company"). They use genuine situational relevance — "you're a CGO scaling past $100K/month in spend and you've hit this exact wall."
|
|
15
|
+
|
|
16
|
+
**Three patterns:**
|
|
17
|
+
|
|
18
|
+
1. **Role-specific** — direct address to their role/situation
|
|
19
|
+
2. **Callback** — references a prior interaction or context
|
|
20
|
+
3. **Shared situation** — "you and I both know this feeling"
|
|
21
|
+
|
|
22
|
+
---
|
|
23
|
+
|
|
24
|
+
## TEMPLATES
|
|
25
|
+
|
|
26
|
+
### Pattern 1 — Role-Specific
|
|
27
|
+
|
|
28
|
+
**Structure:** `[PERSONA_ROLE], [direct statement about their situation]`
|
|
29
|
+
|
|
30
|
+
Variants:
|
|
31
|
+
- `[PERSONA_ROLE]: [short observation about their specific situation]`
|
|
32
|
+
- `For [PERSONA_ROLE]s hitting [PAIN_POINT]`
|
|
33
|
+
- `[First Name] — [short observation or question]`
|
|
34
|
+
- `[PERSONA_ROLE], this one's for you`
|
|
35
|
+
|
|
36
|
+
---
|
|
37
|
+
|
|
38
|
+
### Pattern 2 — Callback
|
|
39
|
+
|
|
40
|
+
**Structure:** `Following up on [CONTEXT/PRIOR_INTERACTION]`
|
|
41
|
+
|
|
42
|
+
Variants:
|
|
43
|
+
- `Following up from [CONTEXT], [First Name]`
|
|
44
|
+
- `Re: [topic from prior conversation]`
|
|
45
|
+
- `After [EVENT/TRIGGER] — one thing worth considering`
|
|
46
|
+
- `[First Name] — picking up where we left off`
|
|
47
|
+
|
|
48
|
+
---
|
|
49
|
+
|
|
50
|
+
### Pattern 3 — Shared Situation
|
|
51
|
+
|
|
52
|
+
**Structure:** `You know this feeling: [SHARED_PAIN_OR_EXPERIENCE]`
|
|
53
|
+
|
|
54
|
+
Variants:
|
|
55
|
+
- `You know the feeling: [PAIN_SITUATION]`
|
|
56
|
+
- `If you've ever [SHARED_EXPERIENCE], this is for you`
|
|
57
|
+
- `[First Name], I think this will feel familiar`
|
|
58
|
+
- `This might sound familiar…`
|
|
59
|
+
|
|
60
|
+
---
|
|
61
|
+
|
|
62
|
+
## GROWTHUB-SPECIFIC EXAMPLES
|
|
63
|
+
|
|
64
|
+
**Cold outbound — Pillar 2:**
|
|
65
|
+
- `[First Name] — quick question about your creative pipeline`
|
|
66
|
+
- `For CGOs scaling past $100K/month in ad spend`
|
|
67
|
+
- `[First Name], you know this feeling: creative is the bottleneck again`
|
|
68
|
+
|
|
69
|
+
**Cold outbound — Pillar 4:**
|
|
70
|
+
- `[First Name] — something I think you'll find useful`
|
|
71
|
+
- `For agency owners hitting the production ceiling`
|
|
72
|
+
|
|
73
|
+
**Re-engagement:**
|
|
74
|
+
- `[First Name] — checking in`
|
|
75
|
+
- `Hey [First Name] — still relevant?`
|
|
76
|
+
- `[First Name], something we should have sent sooner`
|
|
77
|
+
|
|
78
|
+
**Post-demo follow-up:**
|
|
79
|
+
- `Following up from our call, [First Name]`
|
|
80
|
+
- `[First Name] — the thing you mentioned that stuck with me`
|
|
81
|
+
- `After our call — one more thing`
|
|
82
|
+
|
|
83
|
+
---
|
|
84
|
+
|
|
85
|
+
## PREVIEW TEXT PAIRING
|
|
86
|
+
|
|
87
|
+
Personal subject lines pair best with preview text that:
|
|
88
|
+
- Adds the specific context that makes it feel even more relevant
|
|
89
|
+
- Answers the unspoken "why are you emailing me?" question
|
|
90
|
+
- Does NOT open with "I hope this finds you well" or any filler
|
|
91
|
+
|
|
92
|
+
**Example pairings:**
|
|
93
|
+
|
|
94
|
+
| Subject | Preview |
|
|
95
|
+
|---|---|
|
|
96
|
+
| [First Name] — quick question about your creative pipeline | If your ability to test new concepts is the bottleneck, I want to show you something. |
|
|
97
|
+
| Following up from our call, [First Name] | You mentioned the production speed issue — I want to address it directly. |
|
|
98
|
+
| Hey [First Name] — still relevant? | We talked a while back. I've got something new that might change the conversation. |
|
|
99
|
+
|
|
100
|
+
---
|
|
101
|
+
|
|
102
|
+
## RULES
|
|
103
|
+
|
|
104
|
+
- First-name personalization (`[First Name]`) is appropriate for cold outbound and re-engagement sequences
|
|
105
|
+
- Do not use first-name personalization for broadcast emails to large lists — it reads as fake
|
|
106
|
+
- The "personal" feel must be backed up by a personal email body — don't use personal subject lines on generic broadcast emails
|
|
107
|
+
- Avoid hollow personalization: "I noticed you work at [Company]" without genuine relevance
|
|
108
|
+
- Keep personal subject lines short — they work better under 40 characters
|
|
@@ -0,0 +1,109 @@
|
|
|
1
|
+
# Subject Line Module — Social Proof
|
|
2
|
+
|
|
3
|
+
**Module type:** Subject line
|
|
4
|
+
**Type tag:** `social-proof`
|
|
5
|
+
**What it does:** Anchors credibility with a specific result, number, or story. Makes the reader believe the outcome is real because someone else already achieved it.
|
|
6
|
+
**Best used for:** Mid-to-late nurture (emails 3–4), re-engagement email 2, post-demo email 2, promotional broadcasts with strong results to cite
|
|
7
|
+
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
## HOW SOCIAL PROOF SUBJECT LINES WORK
|
|
11
|
+
|
|
12
|
+
Social proof subject lines lead with a specific, believable result. The specificity is what makes them work — a precise number is more credible than a vague claim. The reader sees the outcome and wants to know how.
|
|
13
|
+
|
|
14
|
+
**Three patterns that work:**
|
|
15
|
+
|
|
16
|
+
1. **The result story** — "How [persona type] went from [X] to [Y]"
|
|
17
|
+
2. **The number anchor** — "[Number/stat] — here's what it took"
|
|
18
|
+
3. **The peer validation** — "What [comparable person/brand] is doing differently"
|
|
19
|
+
|
|
20
|
+
**What kills social proof subject lines:**
|
|
21
|
+
- Vague claims ("Amazing results from our clients")
|
|
22
|
+
- Unbelievable numbers without context ("10x results overnight")
|
|
23
|
+
- Generic social proof not tied to the reader's specific situation
|
|
24
|
+
- Fabricated or exaggerated proof — always use approved numbers only
|
|
25
|
+
|
|
26
|
+
---
|
|
27
|
+
|
|
28
|
+
## TEMPLATES
|
|
29
|
+
|
|
30
|
+
### Pattern 1 — The Result Story
|
|
31
|
+
|
|
32
|
+
**Structure:** `How [PERSONA_TYPE] went from [PROBLEM_STATE] to [DESIRED_OUTCOME]`
|
|
33
|
+
|
|
34
|
+
Variants:
|
|
35
|
+
- `How [PERSONA_TYPE] went from [X] to [Y] in [TIMEFRAME]`
|
|
36
|
+
- `From [PAIN_STATE] to [OUTCOME]: what changed`
|
|
37
|
+
- `[PERSONA_TYPE] was hitting [PAIN_POINT] — here's what happened next`
|
|
38
|
+
- `What [PERSONA_TYPE] did differently (and why it worked)`
|
|
39
|
+
|
|
40
|
+
---
|
|
41
|
+
|
|
42
|
+
### Pattern 2 — The Number Anchor
|
|
43
|
+
|
|
44
|
+
**Structure:** `[NUMBER/STAT]: here's what it took`
|
|
45
|
+
|
|
46
|
+
Variants:
|
|
47
|
+
- `[NUMBER] — and no increase in headcount`
|
|
48
|
+
- `[RESULT] in [TIMEFRAME] — the system behind it`
|
|
49
|
+
- `[SPECIFIC_METRIC] without [COST_OR_EFFORT]: here's how`
|
|
50
|
+
- `[STAT] of our clients [RESULT] — this is what they did`
|
|
51
|
+
|
|
52
|
+
---
|
|
53
|
+
|
|
54
|
+
### Pattern 3 — The Peer Validation
|
|
55
|
+
|
|
56
|
+
**Structure:** `What [COMPARABLE_PERSONA] is doing differently right now`
|
|
57
|
+
|
|
58
|
+
Variants:
|
|
59
|
+
- `What top [PERSONA_ROLE]s are doing that most people aren't`
|
|
60
|
+
- `The [PERSONA_ROLE]s scaling to [OUTCOME] have this in common`
|
|
61
|
+
- `Why some [PERSONA_TYPE]s are scaling while others are stuck`
|
|
62
|
+
- `What [PERSONA_ROLE]s with [RESULT] did first`
|
|
63
|
+
|
|
64
|
+
---
|
|
65
|
+
|
|
66
|
+
## GROWTHUB-SPECIFIC EXAMPLES
|
|
67
|
+
|
|
68
|
+
**Pillar 1 — Growth System:**
|
|
69
|
+
- `How one agency went from chaos to a systemized growth machine`
|
|
70
|
+
- `What systematized brands have in common (and how they got there)`
|
|
71
|
+
|
|
72
|
+
**Pillar 2 — Automation & AI:**
|
|
73
|
+
- `How [Brand type] tested 3x more concepts without hiring`
|
|
74
|
+
- `5x more creative tests per month — the system behind it`
|
|
75
|
+
|
|
76
|
+
**Pillar 3 — Client Results:**
|
|
77
|
+
- `From 100K to 500K in ad spend — what actually changed`
|
|
78
|
+
- `What brands removing the creative bottleneck have in common`
|
|
79
|
+
|
|
80
|
+
**Pillar 5 — Pipeline & Revenue:**
|
|
81
|
+
- `How [persona type] re-engaged their list and moved pipeline`
|
|
82
|
+
- `[N] deals closed from a list everyone wrote off — here's how`
|
|
83
|
+
|
|
84
|
+
---
|
|
85
|
+
|
|
86
|
+
## PREVIEW TEXT PAIRING
|
|
87
|
+
|
|
88
|
+
Social proof subject lines pair best with preview text that:
|
|
89
|
+
- Adds a detail that makes the result feel even more specific and credible
|
|
90
|
+
- Names the mechanism or system that produced the result
|
|
91
|
+
- Frames the result as something the reader can replicate
|
|
92
|
+
|
|
93
|
+
**Example pairings:**
|
|
94
|
+
|
|
95
|
+
| Subject | Preview |
|
|
96
|
+
|---|---|
|
|
97
|
+
| How one agency went from chaos to a systemized growth machine | It wasn't a new hire. It wasn't a new tool. It was this one structural change. |
|
|
98
|
+
| 5x more creative tests per month — the system behind it | No extra headcount. Same budget. Just a different approach to the production layer. |
|
|
99
|
+
| From 100K to 500K in ad spend — what actually changed | The budget was always there. The creative bottleneck was the constraint. |
|
|
100
|
+
|
|
101
|
+
---
|
|
102
|
+
|
|
103
|
+
## RULES
|
|
104
|
+
|
|
105
|
+
- Only use numbers and results that are approved in the brand kit — never fabricate
|
|
106
|
+
- Specificity is credibility — "5x more tests" beats "dramatically more testing"
|
|
107
|
+
- Pair the result with a timeframe when possible ("in 90 days", "in one quarter")
|
|
108
|
+
- The proof story in the email body must match what the subject line promises
|
|
109
|
+
- Do not use a proof subject line unless the email body delivers the full story
|
|
@@ -0,0 +1,112 @@
|
|
|
1
|
+
# Subject Line Module — Urgency
|
|
2
|
+
|
|
3
|
+
**Module type:** Subject line
|
|
4
|
+
**Type tag:** `urgency`
|
|
5
|
+
**What it does:** Creates a reason to act now — or articulates the cost of not acting. Moves stalled contacts toward a decision.
|
|
6
|
+
**Best used for:** Promotional broadcasts, re-engagement email 3, nurture activation email (email 4–5), post-demo follow-up email 3
|
|
7
|
+
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
## HOW URGENCY SUBJECT LINES WORK
|
|
11
|
+
|
|
12
|
+
Urgency subject lines work when the urgency is real and specific. False scarcity destroys trust — if you say "ends Friday" and it doesn't end Friday, your next email gets ignored.
|
|
13
|
+
|
|
14
|
+
The most powerful urgency in Growthub email is not time-based — it's **cost-of-inaction** urgency: "here's what's happening while you wait."
|
|
15
|
+
|
|
16
|
+
**Three urgency patterns:**
|
|
17
|
+
|
|
18
|
+
1. **Deadline-based** — "This closes [date/day]" — only use when there is a real deadline
|
|
19
|
+
2. **Cost-of-inaction** — "While you're waiting, here's what's happening" — most reliable for B2B
|
|
20
|
+
3. **Last-chance** — "Last email on this" — used in Email 3 of cold/re-engagement sequences
|
|
21
|
+
|
|
22
|
+
---
|
|
23
|
+
|
|
24
|
+
## TEMPLATES
|
|
25
|
+
|
|
26
|
+
### Pattern 1 — Deadline-Based
|
|
27
|
+
|
|
28
|
+
**Structure:** `[OFFER/RESOURCE] closes [DATE/DAY]`
|
|
29
|
+
|
|
30
|
+
Variants:
|
|
31
|
+
- `[OFFER] closes [DAY] — last chance`
|
|
32
|
+
- `Doors close [DATE]: [OFFER]`
|
|
33
|
+
- `[DATE] is the cutoff for [OFFER]`
|
|
34
|
+
- `Spots are limited — [N] left for [OFFER]`
|
|
35
|
+
|
|
36
|
+
> ⚠️ Only use when there is a genuine deadline or limited availability. Never invent urgency.
|
|
37
|
+
|
|
38
|
+
---
|
|
39
|
+
|
|
40
|
+
### Pattern 2 — Cost of Inaction
|
|
41
|
+
|
|
42
|
+
**Structure:** `Every week you wait, [COST_OF_DELAY]`
|
|
43
|
+
|
|
44
|
+
Variants:
|
|
45
|
+
- `The longer [PAIN_POINT] goes unresolved, the more it costs`
|
|
46
|
+
- `While you're [CURRENT_STATE], [COMPETITOR_TYPE] is [OUTCOME]`
|
|
47
|
+
- `Every week without [SOLUTION] is [COST_FRAMING]`
|
|
48
|
+
- `The gap between where you are and [DESIRED_OUTCOME] is growing`
|
|
49
|
+
- `Your competitors are [DOING_THE_THING] — are you?`
|
|
50
|
+
|
|
51
|
+
---
|
|
52
|
+
|
|
53
|
+
### Pattern 3 — Last-Chance
|
|
54
|
+
|
|
55
|
+
**Structure:** `Last [email / message / note] on [TOPIC]`
|
|
56
|
+
|
|
57
|
+
Variants:
|
|
58
|
+
- `Last email on this, [First Name]`
|
|
59
|
+
- `One last thing before I go quiet`
|
|
60
|
+
- `Final note on [TOPIC] — then I'll leave you alone`
|
|
61
|
+
- `Still [RELEVANT_TOPIC]? This is my last ask.`
|
|
62
|
+
|
|
63
|
+
> Used in Email 3 of cold and re-engagement sequences. Honest about being the last contact.
|
|
64
|
+
|
|
65
|
+
---
|
|
66
|
+
|
|
67
|
+
## GROWTHUB-SPECIFIC EXAMPLES
|
|
68
|
+
|
|
69
|
+
**Pillar 2 — Automation & AI:**
|
|
70
|
+
- `Every week without a testing system is a week your competition is ahead`
|
|
71
|
+
- `The creative bottleneck is costing you more than you think (here's the math)`
|
|
72
|
+
- `While you're waiting on production, your ad account is sitting still`
|
|
73
|
+
|
|
74
|
+
**Pillar 5 — Pipeline & Revenue:**
|
|
75
|
+
- `Deals don't come back on their own — here's the window`
|
|
76
|
+
- `The pipeline you wrote off might not be dead yet (but the window closes)`
|
|
77
|
+
- `Last email on this — still want to fix the follow-up gap?`
|
|
78
|
+
|
|
79
|
+
**Promotional:**
|
|
80
|
+
- `This offer closes [DATE] — last chance to lock it in`
|
|
81
|
+
- `[N] spots left for [OFFER] — closing this week`
|
|
82
|
+
|
|
83
|
+
**Re-engagement / cold:**
|
|
84
|
+
- `Last email from me on this, [First Name]`
|
|
85
|
+
- `One last note — still relevant?`
|
|
86
|
+
|
|
87
|
+
---
|
|
88
|
+
|
|
89
|
+
## PREVIEW TEXT PAIRING
|
|
90
|
+
|
|
91
|
+
Urgency subject lines pair best with preview text that:
|
|
92
|
+
- Clarifies the specific cost or deadline
|
|
93
|
+
- Makes the urgency feel real and concrete, not manufactured
|
|
94
|
+
- Gives the reader a clear reason to act now
|
|
95
|
+
|
|
96
|
+
**Example pairings:**
|
|
97
|
+
|
|
98
|
+
| Subject | Preview |
|
|
99
|
+
|---|---|
|
|
100
|
+
| Every week without a testing system is a week your competition is ahead | The gap compounds. The longer the delay, the harder the catch-up. |
|
|
101
|
+
| Last email on this, [First Name] | If this isn't the right time, no problem. But I didn't want to go quiet without asking one last time. |
|
|
102
|
+
| This offer closes [DATE] | After that, the pricing goes back to standard. This is the last window. |
|
|
103
|
+
|
|
104
|
+
---
|
|
105
|
+
|
|
106
|
+
## RULES
|
|
107
|
+
|
|
108
|
+
- Never use false urgency — "This expires Friday" when it doesn't
|
|
109
|
+
- Cost-of-inaction urgency is almost always more credible than manufactured deadlines for B2B
|
|
110
|
+
- "Last email" language must be true — if you say it's the last email, it must be the last email in that sequence
|
|
111
|
+
- Urgency subject lines must be paired with urgency that is real and explained in the email body
|
|
112
|
+
- Do not use urgency in nurture emails 1–3 — it reads as desperate before trust is established
|