@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-formats/nurture-sequence.md
ADDED
|
@@ -0,0 +1,143 @@
|
|
|
1
|
+
# Email Format: Lead Nurture — 5 Email Sequence
|
|
2
|
+
|
|
3
|
+
**Format ID:** `nurture-5-email`
|
|
4
|
+
**Campaign type:** Nurture
|
|
5
|
+
**Email count:** 5
|
|
6
|
+
**Duration:** 14 days
|
|
7
|
+
**Entry trigger:** New lead — form fill, ad opt-in, webinar registration, content download
|
|
8
|
+
**Primary pillar fit:** Pillar 1 (Growth System), Pillar 2 (Automation & AI), Pillar 4 (Education & Strategy)
|
|
9
|
+
**Audience:** New leads — problem-aware, have not yet engaged with Growthub directly
|
|
10
|
+
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
## FORMAT PURPOSE
|
|
14
|
+
|
|
15
|
+
Takes a new lead from first touch to booking-ready over 14 days. The arc moves from empathy and problem-naming → insight and education → proof and social validation → direct activation.
|
|
16
|
+
|
|
17
|
+
This format earns trust before asking for anything. The first CTA is always a resource or a soft ask. The direct call booking CTA does not appear until Email 4.
|
|
18
|
+
|
|
19
|
+
---
|
|
20
|
+
|
|
21
|
+
## EMOTIONAL ARC
|
|
22
|
+
|
|
23
|
+
```
|
|
24
|
+
Email 1: Empathy — "You're not alone in this. Here's what we see."
|
|
25
|
+
Email 2: Insight — "Here's the problem most people miss."
|
|
26
|
+
Email 3: Education — "Here's how the system actually works."
|
|
27
|
+
Email 4: Proof — "Here's what happened when someone like you used it."
|
|
28
|
+
Email 5: Activation — "Here's your next step."
|
|
29
|
+
```
|
|
30
|
+
|
|
31
|
+
---
|
|
32
|
+
|
|
33
|
+
## SEQUENCE MAP
|
|
34
|
+
|
|
35
|
+
| # | Send Day | Theme | Body Arc | CTA Type | Subject Type |
|
|
36
|
+
|---|---|---|---|---|---|
|
|
37
|
+
| 1 | Day 0 | Welcome + problem naming | Problem/agitate → soft value reveal | Soft CTA (resource) | Personal or curiosity |
|
|
38
|
+
| 2 | Day +3 | The insight | Value reveal → education block | Soft CTA or reply CTA | Curiosity |
|
|
39
|
+
| 3 | Day +6 | The framework | Education block → mechanism reveal | Soft CTA | Education/curiosity |
|
|
40
|
+
| 4 | Day +10 | The proof | Story bridge → social proof → warm CTA | Primary CTA | Social proof |
|
|
41
|
+
| 5 | Day +14 | The activation | Direct value summary → urgency → primary CTA | Primary CTA | Urgency or direct |
|
|
42
|
+
|
|
43
|
+
---
|
|
44
|
+
|
|
45
|
+
## EMAIL 1 — WELCOME + PROBLEM NAMING
|
|
46
|
+
|
|
47
|
+
**Theme:** You made the right move. Here's what's actually going on.
|
|
48
|
+
**Arc:** Name the tension they signed up because of → validate it → hint at the resolution without giving it away yet
|
|
49
|
+
**Tone:** Warm, direct, operator-to-operator
|
|
50
|
+
**CTA type:** Soft (resource, read more, or reply)
|
|
51
|
+
**Body modules:** `problem-agitate` → `value-reveal` (partial reveal only)
|
|
52
|
+
**Subject type:** Personal ("Hey [First Name]") or curiosity
|
|
53
|
+
|
|
54
|
+
**Sacred elements for Email 1:**
|
|
55
|
+
- Acknowledge the entry trigger (what brought them in)
|
|
56
|
+
- Name the specific pain — not "growth challenges" — the real thing
|
|
57
|
+
- Do NOT ask for a call in Email 1
|
|
58
|
+
- Set up what's coming in the sequence (optional — works well for education-pillar campaigns)
|
|
59
|
+
|
|
60
|
+
---
|
|
61
|
+
|
|
62
|
+
## EMAIL 2 — THE INSIGHT
|
|
63
|
+
|
|
64
|
+
**Theme:** The reason you're stuck isn't what you think
|
|
65
|
+
**Arc:** Challenge the common assumption about the problem → reveal the real constraint
|
|
66
|
+
**Tone:** Confident, slightly provocative, backed by specifics
|
|
67
|
+
**CTA type:** Soft CTA or reply CTA ("Reply and tell me if this lands for you")
|
|
68
|
+
**Body modules:** `value-reveal` → `education-block` (brief)
|
|
69
|
+
**Subject type:** Curiosity ("Why [common belief] is actually the problem")
|
|
70
|
+
|
|
71
|
+
**Sacred elements for Email 2:**
|
|
72
|
+
- Lead with the reframe, not the problem again
|
|
73
|
+
- The insight must be specific to the pillar angle
|
|
74
|
+
- Keep it short — one idea, fully explained
|
|
75
|
+
|
|
76
|
+
---
|
|
77
|
+
|
|
78
|
+
## EMAIL 3 — THE FRAMEWORK
|
|
79
|
+
|
|
80
|
+
**Theme:** Here's exactly how [desired outcome] actually works
|
|
81
|
+
**Arc:** Framework introduction → how it applies to their situation → what changes when you use it
|
|
82
|
+
**Tone:** Educational, generous, credible
|
|
83
|
+
**CTA type:** Soft CTA (case study, resource, watch video)
|
|
84
|
+
**Body modules:** `education-block` → `value-reveal`
|
|
85
|
+
**Subject type:** Curiosity or educational ("The [N]-step [framework name]")
|
|
86
|
+
|
|
87
|
+
**Sacred elements for Email 3:**
|
|
88
|
+
- Teach one thing completely — don't overview multiple topics
|
|
89
|
+
- Numbered framework or clear structure works best here
|
|
90
|
+
- Do not hard sell in Email 3 — build credibility through teaching
|
|
91
|
+
|
|
92
|
+
---
|
|
93
|
+
|
|
94
|
+
## EMAIL 4 — THE PROOF
|
|
95
|
+
|
|
96
|
+
**Theme:** Here's what happened when [persona like them] used this
|
|
97
|
+
**Arc:** Relatable situation → what they tried before → what changed → specific outcome
|
|
98
|
+
**Tone:** Story-forward, peer-level, specific
|
|
99
|
+
**CTA type:** Primary CTA (book call / see how it works)
|
|
100
|
+
**Body modules:** `story-bridge` → `primary-cta`
|
|
101
|
+
**Subject type:** Social proof ("How [brand/persona] went from [X] to [Y]")
|
|
102
|
+
|
|
103
|
+
**Sacred elements for Email 4:**
|
|
104
|
+
- Proof must be specific and approved — never fabricate
|
|
105
|
+
- The story protagonist must match the reader's persona
|
|
106
|
+
- Primary CTA appears for the first time here — do not introduce it before Email 4
|
|
107
|
+
- PS line reinforces the CTA with a secondary angle
|
|
108
|
+
|
|
109
|
+
---
|
|
110
|
+
|
|
111
|
+
## EMAIL 5 — THE ACTIVATION
|
|
112
|
+
|
|
113
|
+
**Theme:** Here's your next step — and why now
|
|
114
|
+
**Arc:** Recap the journey (what they've learned in this sequence) → create mild urgency or scarcity → direct CTA
|
|
115
|
+
**Tone:** Direct, warm, honest about what you're asking
|
|
116
|
+
**CTA type:** Primary CTA — clear and repeated
|
|
117
|
+
**Body modules:** `value-reveal` → `primary-cta`
|
|
118
|
+
**Subject type:** Urgency or direct ("Still [desired outcome]? Here's the thing.")
|
|
119
|
+
|
|
120
|
+
**Sacred elements for Email 5:**
|
|
121
|
+
- This is the activation email — be direct
|
|
122
|
+
- Reference the sequence journey ("Over the past two weeks, we've covered X, Y, Z")
|
|
123
|
+
- Urgency must be genuine — do not manufacture false scarcity
|
|
124
|
+
- CTA is the same as Email 4 — consistency, not novelty
|
|
125
|
+
|
|
126
|
+
---
|
|
127
|
+
|
|
128
|
+
## ADAPTATION RULES
|
|
129
|
+
|
|
130
|
+
**What stays the same regardless of pillar:**
|
|
131
|
+
- 5 emails, 14 days
|
|
132
|
+
- Emotional arc: empathy → insight → education → proof → activation
|
|
133
|
+
- No primary CTA until Email 4
|
|
134
|
+
- Story/proof in Email 4
|
|
135
|
+
- Activation in Email 5
|
|
136
|
+
|
|
137
|
+
**What changes per pillar:**
|
|
138
|
+
- The specific angle and hook for each email
|
|
139
|
+
- The insight in Email 2 (pillar-specific)
|
|
140
|
+
- The framework in Email 3 (pillar-specific)
|
|
141
|
+
- The proof story in Email 4 (relevant to the pillar)
|
|
142
|
+
|
|
143
|
+
**See:** `skills.md → STEP 4 — CONTENT PILLAR → CAMPAIGN ANGLE MAPPING` for pillar-specific angles.
|
|
@@ -0,0 +1,134 @@
|
|
|
1
|
+
# Email Format: Cold Outbound — 4 Email Sequence
|
|
2
|
+
|
|
3
|
+
**Format ID:** `cold-outbound-4-email`
|
|
4
|
+
**Campaign type:** Cold outbound
|
|
5
|
+
**Email count:** 4
|
|
6
|
+
**Duration:** 9 days
|
|
7
|
+
**Entry trigger:** Manual add to list / prospect research / inbound intent signal
|
|
8
|
+
**Primary pillar fit:** Pillar 2 (Automation & AI), Pillar 4 (Education & Strategy), Pillar 5 (Pipeline & Revenue)
|
|
9
|
+
**Audience:** Cold — has not opted in, has not engaged with Growthub yet
|
|
10
|
+
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
## FORMAT PURPOSE
|
|
14
|
+
|
|
15
|
+
Starts a conversation with a cold prospect without pitching. The goal of Email 1 is a reply, not a call. The goal of Email 4 is a call. This sequence earns the right to ask with each email — it does not lead with the ask.
|
|
16
|
+
|
|
17
|
+
The arc is: intrigue → insight → proof → ask. Short emails. One idea each. Every email has one job.
|
|
18
|
+
|
|
19
|
+
---
|
|
20
|
+
|
|
21
|
+
## EMOTIONAL ARC
|
|
22
|
+
|
|
23
|
+
```
|
|
24
|
+
Email 1: Intrigue — open a relevant loop they want to close
|
|
25
|
+
Email 2: Insight — give them something genuinely useful without a big ask
|
|
26
|
+
Email 3: Proof — show them this worked for someone like them
|
|
27
|
+
Email 4: The ask — direct, short, honest
|
|
28
|
+
```
|
|
29
|
+
|
|
30
|
+
---
|
|
31
|
+
|
|
32
|
+
## SEQUENCE MAP
|
|
33
|
+
|
|
34
|
+
| # | Send Day | Theme | Body Arc | CTA Type | Subject Type |
|
|
35
|
+
|---|---|---|---|---|---|
|
|
36
|
+
| 1 | Day 0 | Intrigue — name the problem | Problem name → half-reveal → reply ask | Reply CTA | Personal or curiosity |
|
|
37
|
+
| 2 | Day +2 | The insight | Insight → practical example → soft CTA | Soft CTA | Curiosity |
|
|
38
|
+
| 3 | Day +5 | The proof | Story → result → warm lead-in to ask | Soft CTA → primary CTA setup | Social proof |
|
|
39
|
+
| 4 | Day +9 | The ask | Direct + honest → single question or CTA | Primary CTA or reply CTA | Direct or urgency |
|
|
40
|
+
|
|
41
|
+
---
|
|
42
|
+
|
|
43
|
+
## EMAIL 1 — INTRIGUE
|
|
44
|
+
|
|
45
|
+
**Theme:** Name the exact problem they're experiencing without any pitch
|
|
46
|
+
**Arc:** One sentence hook → name the problem specifically → ask ONE question or offer ONE thing
|
|
47
|
+
**Tone:** Human, peer-level, non-salesy
|
|
48
|
+
**CTA type:** Reply CTA — ("Reply and tell me if this is actually your bottleneck")
|
|
49
|
+
**Body modules:** `problem-agitate` (brief) → `reply-cta`
|
|
50
|
+
**Subject type:** Personal ("Hey [First Name]") or single-idea curiosity
|
|
51
|
+
**Length:** SHORT — 5–8 sentences max
|
|
52
|
+
|
|
53
|
+
**Sacred elements for Email 1:**
|
|
54
|
+
- No pitch in Email 1. Ever.
|
|
55
|
+
- Name a specific problem — not a generic one
|
|
56
|
+
- One question or one idea — not both
|
|
57
|
+
- Reply CTA only — "Reply and tell me X"
|
|
58
|
+
- Under 100 words is often more powerful
|
|
59
|
+
|
|
60
|
+
---
|
|
61
|
+
|
|
62
|
+
## EMAIL 2 — THE INSIGHT
|
|
63
|
+
|
|
64
|
+
**Theme:** Give them something genuinely useful
|
|
65
|
+
**Arc:** Pick up from Email 1 → deliver the insight they need → soft ask (resource or keep the thread going)
|
|
66
|
+
**Tone:** Generous, credible, no strings attached
|
|
67
|
+
**CTA type:** Soft CTA (resource, read, watch) or reply CTA
|
|
68
|
+
**Body modules:** `value-reveal` → `education-block` (brief) → `soft-cta`
|
|
69
|
+
**Subject type:** Curiosity ("The thing most [role] miss about [topic]")
|
|
70
|
+
**Length:** Medium — one complete idea, 8–12 sentences
|
|
71
|
+
|
|
72
|
+
**Sacred elements for Email 2:**
|
|
73
|
+
- Give value before you ask for anything
|
|
74
|
+
- The insight must be specific to their situation and the pillar angle
|
|
75
|
+
- Do not introduce the product in Email 2
|
|
76
|
+
- If they replied to Email 1, reference it
|
|
77
|
+
|
|
78
|
+
---
|
|
79
|
+
|
|
80
|
+
## EMAIL 3 — THE PROOF
|
|
81
|
+
|
|
82
|
+
**Theme:** Show it working for someone like them
|
|
83
|
+
**Arc:** Brief empathy → story → specific result → natural lead-in toward the ask
|
|
84
|
+
**Tone:** Story-forward, peer-level, specific
|
|
85
|
+
**CTA type:** Soft CTA or primary CTA (first appearance of a call ask is acceptable here)
|
|
86
|
+
**Body modules:** `story-bridge` → `primary-cta` or `soft-cta`
|
|
87
|
+
**Subject type:** Social proof ("How [brand type/role] went from [X] to [Y]")
|
|
88
|
+
**Length:** Medium — 10–14 sentences
|
|
89
|
+
|
|
90
|
+
**Sacred elements for Email 3:**
|
|
91
|
+
- Proof must be specific and approved — never fabricate
|
|
92
|
+
- The story protagonist matches the prospect's role and situation
|
|
93
|
+
- The primary CTA can appear here for the first time, but keep it light — "If this sounds like you, happy to show you how we'd approach it"
|
|
94
|
+
|
|
95
|
+
---
|
|
96
|
+
|
|
97
|
+
## EMAIL 4 — THE ASK
|
|
98
|
+
|
|
99
|
+
**Theme:** Be direct and honest about what you're asking
|
|
100
|
+
**Arc:** One sentence reference to the thread → direct ask → short rationale → one CTA
|
|
101
|
+
**Tone:** Direct, honest, no pressure
|
|
102
|
+
**CTA type:** Primary CTA (book a call) or reply CTA ("Yes / No — just let me know")
|
|
103
|
+
**Body modules:** `primary-cta` or `reply-cta`
|
|
104
|
+
**Subject type:** Direct ("Quick question, [First Name]") or urgency ("Last email on this")
|
|
105
|
+
**Length:** SHORT — 4–6 sentences
|
|
106
|
+
|
|
107
|
+
**Sacred elements for Email 4:**
|
|
108
|
+
- Acknowledge this is the last email in the thread (often increases reply rates)
|
|
109
|
+
- Be honest about what you're asking — "I'd like 20 minutes to show you X"
|
|
110
|
+
- No pressure language — "If not, no worries — I won't keep sending"
|
|
111
|
+
- One CTA. Simple. No alternatives.
|
|
112
|
+
|
|
113
|
+
---
|
|
114
|
+
|
|
115
|
+
## ADAPTATION RULES
|
|
116
|
+
|
|
117
|
+
**What stays the same:**
|
|
118
|
+
- 4 emails, 9 days
|
|
119
|
+
- Emotional arc: intrigue → insight → proof → ask
|
|
120
|
+
- No pitch in Email 1
|
|
121
|
+
- Reply CTA in Email 1
|
|
122
|
+
- Short emails — cold sequences reward brevity
|
|
123
|
+
|
|
124
|
+
**What changes per pillar:**
|
|
125
|
+
- The specific insight and hook in Email 2 (pillar-specific)
|
|
126
|
+
- The proof story in Email 3 (relevant to the prospect's role)
|
|
127
|
+
- The ask framing in Email 4 (pillar-specific outcome)
|
|
128
|
+
|
|
129
|
+
**Personalization rules:**
|
|
130
|
+
- First name personalization is appropriate for cold sequences
|
|
131
|
+
- Reference specific company context if available ("I saw [Company] is scaling on Meta")
|
|
132
|
+
- Do not over-personalize — it reads as fake
|
|
133
|
+
|
|
134
|
+
**See:** `skills.md → STEP 4` for pillar-specific angles.
|
|
@@ -0,0 +1,117 @@
|
|
|
1
|
+
# Email Format: Promotional Broadcast — Single Email
|
|
2
|
+
|
|
3
|
+
**Format ID:** `promotional-broadcast`
|
|
4
|
+
**Campaign type:** Promotional broadcast
|
|
5
|
+
**Email count:** 1
|
|
6
|
+
**Duration:** Single send
|
|
7
|
+
**Entry trigger:** Manual send — offer launch, event, announcement, limited-time campaign
|
|
8
|
+
**Primary pillar fit:** Pillar 2 (Automation & AI), Pillar 3 (Client Results), Pillar 5 (Pipeline & Revenue)
|
|
9
|
+
**Audience:** Warm — existing leads, prospects, or clients who have opted in
|
|
10
|
+
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
## FORMAT PURPOSE
|
|
14
|
+
|
|
15
|
+
A single, focused email that drives one action. The offer is clear. The CTA is singular. The value is front-loaded. There is no ambiguity about what you're asking the reader to do.
|
|
16
|
+
|
|
17
|
+
This format is not a newsletter. It is not an update. It is a direct, specific invitation to take one action.
|
|
18
|
+
|
|
19
|
+
---
|
|
20
|
+
|
|
21
|
+
## EMOTIONAL ARC
|
|
22
|
+
|
|
23
|
+
```
|
|
24
|
+
Opening: Intrigue or direct value — earns the open's follow-through
|
|
25
|
+
Body: Specifics — what, why, for whom, for how long
|
|
26
|
+
CTA: One action — clear, verb-first, specific outcome
|
|
27
|
+
PS: Secondary angle or urgency reinforcement
|
|
28
|
+
```
|
|
29
|
+
|
|
30
|
+
---
|
|
31
|
+
|
|
32
|
+
## EMAIL STRUCTURE
|
|
33
|
+
|
|
34
|
+
### SUBJECT LINE
|
|
35
|
+
- Curiosity, social proof, urgency, or direct — based on pillar and audience
|
|
36
|
+
- Write 5+ variants in the subject line matrix before selecting
|
|
37
|
+
- Maximum 50 characters
|
|
38
|
+
|
|
39
|
+
### PREVIEW TEXT
|
|
40
|
+
- Extends or reframes the subject — never repeats it
|
|
41
|
+
- Creates a second hook that rewards the preview read
|
|
42
|
+
|
|
43
|
+
### OPENING HOOK (1–2 sentences)
|
|
44
|
+
- Lead with the most compelling thing: the result, the insight, or the offer
|
|
45
|
+
- Do not open with pleasantries ("Hope you're doing well")
|
|
46
|
+
- Do not bury the lede — state the purpose in the first 2 sentences
|
|
47
|
+
|
|
48
|
+
### BODY BLOCK 1 — WHAT THIS IS
|
|
49
|
+
- State the offer, event, or announcement clearly
|
|
50
|
+
- What is it, specifically?
|
|
51
|
+
- Who is it for?
|
|
52
|
+
|
|
53
|
+
### BODY BLOCK 2 — WHY IT MATTERS
|
|
54
|
+
- Why should the reader care now?
|
|
55
|
+
- What problem does this solve or what opportunity does this create?
|
|
56
|
+
- One proof point or concrete example if available
|
|
57
|
+
|
|
58
|
+
### BODY BLOCK 3 (OPTIONAL) — WHAT'S INCLUDED / HOW IT WORKS
|
|
59
|
+
- Brief specifics of what the reader gets
|
|
60
|
+
- Bullet format is acceptable here (3–5 bullets max)
|
|
61
|
+
- Skip if the offer is self-explanatory
|
|
62
|
+
|
|
63
|
+
### PRIMARY CTA
|
|
64
|
+
- Single action
|
|
65
|
+
- Verb-first, specific outcome
|
|
66
|
+
- Own line — not buried in paragraph
|
|
67
|
+
- Repeat in PS
|
|
68
|
+
|
|
69
|
+
### PS LINE
|
|
70
|
+
- Reinforce urgency or add a secondary angle
|
|
71
|
+
- If there is a deadline or scarcity: name it explicitly here
|
|
72
|
+
- Example: "P.S. This closes [date]. If [qualifying condition], this is for you."
|
|
73
|
+
|
|
74
|
+
### FOOTER
|
|
75
|
+
- Unsubscribe link
|
|
76
|
+
- Physical mailing address
|
|
77
|
+
- CAN-SPAM compliant — non-negotiable
|
|
78
|
+
|
|
79
|
+
---
|
|
80
|
+
|
|
81
|
+
## PROMOTIONAL BROADCAST RULES
|
|
82
|
+
|
|
83
|
+
**One offer. One CTA. Full stop.**
|
|
84
|
+
A promotional broadcast that tries to do two things does neither. Pick the single most important action and design everything around it.
|
|
85
|
+
|
|
86
|
+
**Front-load the value.**
|
|
87
|
+
The reader decides in the first 2 sentences. If the opening hook doesn't earn the scroll, the rest doesn't matter.
|
|
88
|
+
|
|
89
|
+
**Use genuine urgency only.**
|
|
90
|
+
If there's a real deadline, name it explicitly. If there isn't, don't invent one. False urgency erodes trust.
|
|
91
|
+
|
|
92
|
+
**Segment carefully.**
|
|
93
|
+
A promotional email is only effective if it's relevant to the segment receiving it. Confirm the segment in the campaign brief before writing. A "growth call" offer sent to existing paying clients lands very differently than to new leads.
|
|
94
|
+
|
|
95
|
+
**Compliance is mandatory.**
|
|
96
|
+
Every broadcast must have a CAN-SPAM compliant footer. Physical address. Unsubscribe link. No exceptions.
|
|
97
|
+
|
|
98
|
+
---
|
|
99
|
+
|
|
100
|
+
## ADAPTATION RULES
|
|
101
|
+
|
|
102
|
+
**What stays the same:**
|
|
103
|
+
- One offer, one CTA
|
|
104
|
+
- CTA repeated in PS
|
|
105
|
+
- Compliance footer on every broadcast
|
|
106
|
+
|
|
107
|
+
**What changes per pillar:**
|
|
108
|
+
- The angle and hook (Pillar 5 = pipeline/revenue urgency, Pillar 2 = speed/automation angle, Pillar 3 = proof-forward)
|
|
109
|
+
- The body copy framing
|
|
110
|
+
- The subject line type selected
|
|
111
|
+
|
|
112
|
+
**Length guidance:**
|
|
113
|
+
- Short (5–8 sentences): best for warm audiences with high brand trust
|
|
114
|
+
- Medium (10–14 sentences): use when the offer needs context or education
|
|
115
|
+
- Long (15+ sentences): rarely appropriate for a broadcast — use a landing page instead
|
|
116
|
+
|
|
117
|
+
**See:** `skills.md → STEP 4` for pillar-specific angles and language patterns.
|
package/assets/worker-kits/growthub-email-marketing-v1/templates/email-formats/re-engagement.md
ADDED
|
@@ -0,0 +1,108 @@
|
|
|
1
|
+
# Email Format: Re-Engagement — 3 Email Win-Back Sequence
|
|
2
|
+
|
|
3
|
+
**Format ID:** `re-engagement-3-email`
|
|
4
|
+
**Campaign type:** Re-engagement / win-back
|
|
5
|
+
**Email count:** 3
|
|
6
|
+
**Duration:** 15 days
|
|
7
|
+
**Entry trigger:** Contact has gone silent — no opens in 60+ days, stalled pipeline, demo no-show, previously interested but not moved forward
|
|
8
|
+
**Primary pillar fit:** Pillar 3 (Client Results), Pillar 5 (Pipeline & Revenue)
|
|
9
|
+
**Audience:** Cold-warm — previously engaged, now silent
|
|
10
|
+
|
|
11
|
+
---
|
|
12
|
+
|
|
13
|
+
## FORMAT PURPOSE
|
|
14
|
+
|
|
15
|
+
Wakes up stalled or silent contacts without burning the relationship. The arc is: acknowledge the silence → give them a reason to re-engage → make it easy to take a step forward (or gracefully exit).
|
|
16
|
+
|
|
17
|
+
This format does NOT lead with an apology for emailing. It does NOT pretend the silence didn't happen. It acknowledges it directly, which earns more responses than ignoring it.
|
|
18
|
+
|
|
19
|
+
---
|
|
20
|
+
|
|
21
|
+
## EMOTIONAL ARC
|
|
22
|
+
|
|
23
|
+
```
|
|
24
|
+
Email 1: Acknowledgment — "I notice we haven't spoken in a while. Here's something relevant."
|
|
25
|
+
Email 2: Proof/Value — "Here's what's changed / what's working for people like you right now."
|
|
26
|
+
Email 3: The close — "Still relevant? One question."
|
|
27
|
+
```
|
|
28
|
+
|
|
29
|
+
---
|
|
30
|
+
|
|
31
|
+
## SEQUENCE MAP
|
|
32
|
+
|
|
33
|
+
| # | Send Day | Theme | Body Arc | CTA Type | Subject Type |
|
|
34
|
+
|---|---|---|---|---|---|
|
|
35
|
+
| 1 | Day 0 | Re-open the loop | Acknowledge gap → relevant insight or update → soft ask | Soft CTA or reply CTA | Personal or curiosity |
|
|
36
|
+
| 2 | Day +5 | New proof or value | Proof/result relevant to their situation → warm ask | Primary CTA or soft CTA | Social proof |
|
|
37
|
+
| 3 | Day +10 | The close — or let go | Direct question → one CTA or permission to exit | Reply CTA | Direct or urgency |
|
|
38
|
+
|
|
39
|
+
---
|
|
40
|
+
|
|
41
|
+
## EMAIL 1 — ACKNOWLEDGE + RE-OPEN
|
|
42
|
+
|
|
43
|
+
**Theme:** Name the silence. Give them a reason to re-engage.
|
|
44
|
+
**Arc:** Direct acknowledgment → one relevant piece of value or update → low-friction ask
|
|
45
|
+
**Tone:** Direct, human, no-pressure
|
|
46
|
+
**CTA type:** Reply CTA ("Reply with [yes/no]" or "Still relevant?") or soft CTA
|
|
47
|
+
**Body modules:** `value-reveal` → `reply-cta`
|
|
48
|
+
**Subject type:** Personal ("Hey [First Name] — checking in") or curiosity ("Something we should have sent sooner")
|
|
49
|
+
**Length:** SHORT — 6–8 sentences
|
|
50
|
+
|
|
51
|
+
**Sacred elements for Email 1:**
|
|
52
|
+
- Do NOT pretend they haven't gone silent — acknowledge it briefly and move on
|
|
53
|
+
- Do NOT apologize for emailing them — they opted in
|
|
54
|
+
- The value or update must be genuinely relevant to their situation
|
|
55
|
+
- Keep the ask low — a yes/no reply or a soft CTA, not a call request
|
|
56
|
+
|
|
57
|
+
---
|
|
58
|
+
|
|
59
|
+
## EMAIL 2 — PROOF OR NEW VALUE
|
|
60
|
+
|
|
61
|
+
**Theme:** Show them what's working now — for people like them
|
|
62
|
+
**Arc:** Brief callback to Email 1 (if they didn't reply) → proof point or new development → warm ask
|
|
63
|
+
**Tone:** Story-forward, credible, slightly more direct than Email 1
|
|
64
|
+
**CTA type:** Primary CTA (book a call / see how it works) OR soft CTA
|
|
65
|
+
**Body modules:** `story-bridge` → `primary-cta` or `soft-cta`
|
|
66
|
+
**Subject type:** Social proof ("What [persona type] is doing differently right now") or curiosity
|
|
67
|
+
**Length:** Medium — 8–12 sentences
|
|
68
|
+
|
|
69
|
+
**Sacred elements for Email 2:**
|
|
70
|
+
- Proof must match their situation — use the most relevant case or result
|
|
71
|
+
- Transition from re-engagement to the offer feels earned, not forced
|
|
72
|
+
- If they replied to Email 1, reference it — personalize the opening
|
|
73
|
+
|
|
74
|
+
---
|
|
75
|
+
|
|
76
|
+
## EMAIL 3 — THE CLOSE
|
|
77
|
+
|
|
78
|
+
**Theme:** One direct question. Clear options. No pressure.
|
|
79
|
+
**Arc:** Acknowledge this is the last email → ask one honest question → give them an easy out if they're not interested
|
|
80
|
+
**Tone:** Direct, honest, human
|
|
81
|
+
**CTA type:** Reply CTA ("Reply with [yes/no/later]") or primary CTA
|
|
82
|
+
**Body modules:** `reply-cta` or `primary-cta`
|
|
83
|
+
**Subject type:** Direct ("Still [relevant outcome]?") or urgency ("Last one — then I'll stop")
|
|
84
|
+
**Length:** SHORT — 4–6 sentences
|
|
85
|
+
|
|
86
|
+
**Sacred elements for Email 3:**
|
|
87
|
+
- Tell them this is the last email in this sequence — it improves replies
|
|
88
|
+
- Give them clear options: "Yes I'm interested / No thanks / Maybe later — here's when"
|
|
89
|
+
- Do not pressure or guilt them for not responding
|
|
90
|
+
- If they reply "No", remove from sequence — do not re-add for 90 days minimum
|
|
91
|
+
|
|
92
|
+
---
|
|
93
|
+
|
|
94
|
+
## RE-ENGAGEMENT RULES
|
|
95
|
+
|
|
96
|
+
**Acknowledge the silence — don't dance around it.**
|
|
97
|
+
"We haven't heard from you in a while" outperforms pretending they're a fresh contact every time.
|
|
98
|
+
|
|
99
|
+
**Give value before asking.**
|
|
100
|
+
Even in a re-engagement sequence, Email 1 should deliver something useful. If you're just asking for a call with nothing new to offer, you'll get ignored.
|
|
101
|
+
|
|
102
|
+
**Make it easy to say no.**
|
|
103
|
+
A graceful exit ("No thanks" option) in Email 3 keeps your list clean and your sender reputation healthy.
|
|
104
|
+
|
|
105
|
+
**Segment before sending.**
|
|
106
|
+
Contacts who were never qualified should not get the same re-engagement sequence as contacts who had a demo and went silent. Adapt the copy for the segment's history.
|
|
107
|
+
|
|
108
|
+
**See:** `skills.md → STEP 4` for pillar-specific re-engagement angles.
|
|
@@ -0,0 +1,97 @@
|
|
|
1
|
+
# Email Module Library — INDEX
|
|
2
|
+
|
|
3
|
+
> Check this index before writing any copy block.
|
|
4
|
+
> Each module is a reusable, fill-in-the-blank primitive.
|
|
5
|
+
> Mix and match modules to build any email arc.
|
|
6
|
+
> Placeholder schema is universal across all modules.
|
|
7
|
+
|
|
8
|
+
---
|
|
9
|
+
|
|
10
|
+
## SUBJECT LINE MODULES
|
|
11
|
+
|
|
12
|
+
| Module | Type | What it does | File |
|
|
13
|
+
|---|---|---|---|
|
|
14
|
+
| Curiosity | Subject line | Opens a loop — reader must open to close it | `subject-lines/curiosity.md` |
|
|
15
|
+
| Social Proof | Subject line | Anchors credibility with a result or number | `subject-lines/social-proof.md` |
|
|
16
|
+
| Urgency | Subject line | Creates a reason to act now | `subject-lines/urgency.md` |
|
|
17
|
+
| Personal | Subject line | Speaks directly to the individual | `subject-lines/personal.md` |
|
|
18
|
+
|
|
19
|
+
**Selection guide:**
|
|
20
|
+
|
|
21
|
+
| Audience stage | Subject line type to lead with |
|
|
22
|
+
|---|---|
|
|
23
|
+
| Cold / first touch | Personal or Curiosity |
|
|
24
|
+
| Early nurture | Curiosity |
|
|
25
|
+
| Mid nurture | Curiosity or Social Proof |
|
|
26
|
+
| Late nurture / activation | Social Proof or Urgency |
|
|
27
|
+
| Re-engagement | Personal or Curiosity |
|
|
28
|
+
| Promotional | Urgency or Social Proof |
|
|
29
|
+
| Post-demo follow-up | Personal |
|
|
30
|
+
|
|
31
|
+
---
|
|
32
|
+
|
|
33
|
+
## BODY BLOCK MODULES
|
|
34
|
+
|
|
35
|
+
| Module | What it does | Use in | File |
|
|
36
|
+
|---|---|---|---|
|
|
37
|
+
| Problem/Agitate | Names and sharpens the pain | Email 1–2, cold outbound | `body/problem-agitate.md` |
|
|
38
|
+
| Value/Reveal | Introduces the insight or mechanism | Email 2–3, educational | `body/value-reveal.md` |
|
|
39
|
+
| Story/Bridge | Bridges insight to real-world proof | Email 3–4, proof emails | `body/story-bridge.md` |
|
|
40
|
+
| Education Block | Framework, how-to, structured teaching | Email 3, educational campaigns | `body/education-block.md` |
|
|
41
|
+
|
|
42
|
+
**Body arc assembly reference:**
|
|
43
|
+
|
|
44
|
+
| Campaign goal | Block sequence |
|
|
45
|
+
|---|---|
|
|
46
|
+
| Problem-aware cold prospect | Problem/Agitate → Value/Reveal |
|
|
47
|
+
| Early nurture (teach first) | Value/Reveal → Education Block |
|
|
48
|
+
| Proof-forward (warm audience) | Story/Bridge → Value/Reveal |
|
|
49
|
+
| Activation (late nurture) | Value/Reveal → Story/Bridge |
|
|
50
|
+
| Re-engagement | Value/Reveal (new angle) |
|
|
51
|
+
|
|
52
|
+
---
|
|
53
|
+
|
|
54
|
+
## CTA MODULES
|
|
55
|
+
|
|
56
|
+
| Module | What it does | Commitment level | File |
|
|
57
|
+
|---|---|---|---|
|
|
58
|
+
| Primary CTA | Direct ask — book, start, demo | High | `cta/primary-cta.md` |
|
|
59
|
+
| Soft CTA | Lower ask — resource, read, watch | Medium | `cta/soft-cta.md` |
|
|
60
|
+
| Reply CTA | Conversational ask | Low | `cta/reply-cta.md` |
|
|
61
|
+
|
|
62
|
+
**CTA selection guide:**
|
|
63
|
+
|
|
64
|
+
| Email position | CTA type |
|
|
65
|
+
|---|---|
|
|
66
|
+
| Cold Email 1 | Reply CTA |
|
|
67
|
+
| Cold Email 2 | Soft CTA or Reply CTA |
|
|
68
|
+
| Cold Email 3–4 | Soft CTA → Primary CTA |
|
|
69
|
+
| Nurture Email 1–2 | Soft CTA or Reply CTA |
|
|
70
|
+
| Nurture Email 3 | Soft CTA |
|
|
71
|
+
| Nurture Email 4–5 | Primary CTA |
|
|
72
|
+
| Re-engagement Email 1–2 | Reply CTA or Soft CTA |
|
|
73
|
+
| Re-engagement Email 3 | Reply CTA (yes/no/later) |
|
|
74
|
+
| Post-demo Email 1 | Primary CTA or Soft CTA |
|
|
75
|
+
| Post-demo Email 2–3 | Primary CTA |
|
|
76
|
+
| Promotional | Primary CTA |
|
|
77
|
+
|
|
78
|
+
---
|
|
79
|
+
|
|
80
|
+
## UNIVERSAL PLACEHOLDER SCHEMA
|
|
81
|
+
|
|
82
|
+
All modules use these placeholders. Pull values from the active brand kit.
|
|
83
|
+
|
|
84
|
+
| Placeholder | Source | Example |
|
|
85
|
+
|---|---|---|
|
|
86
|
+
| `[BRAND_NAME]` | `brand_kit.client_name` | Growthub |
|
|
87
|
+
| `[PERSONA_ROLE]` | `brand_kit.primary_persona.role` | agency owner, CGO |
|
|
88
|
+
| `[PAIN_POINT]` | `brand_kit.primary_persona.pain_point` | creative bottleneck |
|
|
89
|
+
| `[DESIRED_OUTCOME]` | `brand_kit.primary_persona.desired_outcome` | scale spend without increasing production cost |
|
|
90
|
+
| `[CAMPAIGN_ANGLE]` | Confirmed in CLAUDE.md Step 4 | the bottleneck isn't your team... |
|
|
91
|
+
| `[PROOF_POINT]` | `brand_kit.proof_points` (approved only) | went from 100K to 500K in ad spend |
|
|
92
|
+
| `[PRIMARY_CTA_TEXT]` | `brand_kit.primary_cta_text` | Book your growth call |
|
|
93
|
+
| `[PRIMARY_CTA_URL]` | `brand_kit.primary_cta_url` | [URL] |
|
|
94
|
+
| `[APPROVED_PHRASE]` | `brand_kit.approved_phrases` | creative velocity |
|
|
95
|
+
| `[PILLAR_LANGUAGE]` | `skills.md → STEP 4` language patterns | growth infrastructure |
|
|
96
|
+
| `[SENDER_NAME]` | `brand_kit.email_from_name` | [Name] at Growthub |
|
|
97
|
+
| `[SEGMENT_TAG]` | Confirmed in Step 3 | new-lead, warm-prospect |
|