@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
|
@@ -0,0 +1,131 @@
|
|
|
1
|
+
# Body Module — Education Block
|
|
2
|
+
|
|
3
|
+
**Module type:** Body block
|
|
4
|
+
**Block ID:** `education-block`
|
|
5
|
+
**What it does:** Teaches one thing completely — a framework, a how-to, a structured explanation. Positions Growthub as the most credible and generous resource in the space.
|
|
6
|
+
**Use in:** Nurture Email 3, educational pillar campaigns (Pillar 4), cold outbound Email 2
|
|
7
|
+
**Length:** 4–8 sentences or a short numbered list (3–5 items)
|
|
8
|
+
**Pillar fit:** Pillar 4 (Education & Strategy) is primary; supports Pillars 1, 2
|
|
9
|
+
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
## HOW THIS BLOCK WORKS
|
|
13
|
+
|
|
14
|
+
The education block earns trust by teaching something genuinely useful with no strings attached. The reader should be able to take the insight and use it — even without Growthub.
|
|
15
|
+
|
|
16
|
+
This is the "generous expert" positioning. The counterintuitive truth is: the more completely you teach, the more the reader wants your help to implement.
|
|
17
|
+
|
|
18
|
+
Rules:
|
|
19
|
+
- Teach ONE thing completely. Do not overview multiple topics.
|
|
20
|
+
- Every step or point should be actionable or enlightening on its own
|
|
21
|
+
- Do not pitch the product inside the education block — the CTA comes after
|
|
22
|
+
- Numbered lists (3–5 items max) are acceptable and often cleaner than prose for frameworks
|
|
23
|
+
|
|
24
|
+
---
|
|
25
|
+
|
|
26
|
+
## STRUCTURE — PROSE VERSION
|
|
27
|
+
|
|
28
|
+
```
|
|
29
|
+
[THE FRAMEWORK NAME OR INSIGHT — 1 sentence]
|
|
30
|
+
|
|
31
|
+
[STEP/COMPONENT 1 — 1–2 sentences]
|
|
32
|
+
|
|
33
|
+
[STEP/COMPONENT 2 — 1–2 sentences]
|
|
34
|
+
|
|
35
|
+
[STEP/COMPONENT 3 — 1–2 sentences]
|
|
36
|
+
|
|
37
|
+
[THE IMPLICATION — 1 sentence: what this means for the reader]
|
|
38
|
+
```
|
|
39
|
+
|
|
40
|
+
---
|
|
41
|
+
|
|
42
|
+
## STRUCTURE — LIST VERSION
|
|
43
|
+
|
|
44
|
+
```
|
|
45
|
+
[THE FRAMEWORK NAME OR INSIGHT — 1 sentence]
|
|
46
|
+
|
|
47
|
+
1. [STEP/COMPONENT 1]
|
|
48
|
+
2. [STEP/COMPONENT 2]
|
|
49
|
+
3. [STEP/COMPONENT 3]
|
|
50
|
+
[4. Optional]
|
|
51
|
+
|
|
52
|
+
[THE IMPLICATION — 1 sentence: what happens when you do this]
|
|
53
|
+
```
|
|
54
|
+
|
|
55
|
+
---
|
|
56
|
+
|
|
57
|
+
## TEMPLATE
|
|
58
|
+
|
|
59
|
+
```
|
|
60
|
+
Here's the [N]-step framework we use for [DESIRED_OUTCOME]:
|
|
61
|
+
|
|
62
|
+
1. [STEP 1 — specific action or phase]
|
|
63
|
+
2. [STEP 2 — specific action or phase]
|
|
64
|
+
3. [STEP 3 — specific action or phase]
|
|
65
|
+
|
|
66
|
+
When you have all three in place, [WHAT_BECOMES_POSSIBLE]. Most [PERSONA_ROLE]s have 1 or 2 — the gap is almost always in [MISSING_STEP].
|
|
67
|
+
```
|
|
68
|
+
|
|
69
|
+
---
|
|
70
|
+
|
|
71
|
+
## GROWTHUB-SPECIFIC EXAMPLES
|
|
72
|
+
|
|
73
|
+
### Pillar 4 — The Creative Intelligence Framework
|
|
74
|
+
|
|
75
|
+
```
|
|
76
|
+
Here's the 3-part framework behind every high-win-rate creative program:
|
|
77
|
+
|
|
78
|
+
1. **Production layer** — the ability to generate and produce concepts fast (AI UGC or lean UGC production)
|
|
79
|
+
2. **Intelligence layer** — the process of extracting *why* a concept worked (hook analysis, pain-point extraction, pattern logging)
|
|
80
|
+
3. **Iteration layer** — the system that uses learning from the intelligence layer to brief the next round faster
|
|
81
|
+
|
|
82
|
+
Most brands have a production layer. Very few have an intelligence layer. Almost none have all three working together as a system.
|
|
83
|
+
|
|
84
|
+
When all three are connected, your cost-per-learning drops with every cycle — and your win rate compounds over time.
|
|
85
|
+
```
|
|
86
|
+
|
|
87
|
+
### Pillar 1 — The Growth System Framework
|
|
88
|
+
|
|
89
|
+
```
|
|
90
|
+
There are three components to a growth system that actually scales:
|
|
91
|
+
|
|
92
|
+
1. **Acquisition infrastructure** — the top of the funnel: creative, landing pages, and paid media working as a system (not in silos)
|
|
93
|
+
2. **Conversion infrastructure** — the follow-up, nurture, and sales process that turns acquired leads into closed deals
|
|
94
|
+
3. **Retention infrastructure** — the systems that keep clients, generate referrals, and create repeat revenue
|
|
95
|
+
|
|
96
|
+
Most businesses have pieces of all three. Very few have them connected. The gap between businesses that plateau and businesses that compound is almost always in the connections between these layers, not the layers themselves.
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
### Pillar 2 — The Testing Velocity Framework
|
|
100
|
+
|
|
101
|
+
```
|
|
102
|
+
The simplest way to increase creative win rate is to increase testing speed. Here's how:
|
|
103
|
+
|
|
104
|
+
1. **Shrink the brief cycle** — go from open-ended creative briefs to a structured insight-first template that cuts briefing time by 60%
|
|
105
|
+
2. **Decouple hooks from body** — test 5 hook variations before committing to full production — kill the losers early
|
|
106
|
+
3. **Build a pattern log** — after every winning ad, extract the hook type, the proof structure, and the audience signal. Use it to brief the next batch.
|
|
107
|
+
|
|
108
|
+
Most teams skip step 3 — which means every testing cycle starts from zero. When you have a pattern log, each cycle builds on the last.
|
|
109
|
+
```
|
|
110
|
+
|
|
111
|
+
### Pillar 5 — The Pipeline Re-Engagement Framework
|
|
112
|
+
|
|
113
|
+
```
|
|
114
|
+
Here's a 3-step re-engagement framework that moves stalled pipeline without burning relationships:
|
|
115
|
+
|
|
116
|
+
1. **Acknowledge** — name the gap (they went quiet, you've been quiet) — don't pretend nothing happened
|
|
117
|
+
2. **Add value** — bring something new and relevant: a case study, a relevant insight, or a framework they can use
|
|
118
|
+
3. **Make it easy to respond** — give them a binary option (yes/no/later) and make the "no" an easy, graceful exit
|
|
119
|
+
|
|
120
|
+
The key is step 2. Most re-engagement emails just say "checking in" — which gives the reader nothing to respond to. A new, relevant piece of value gives them a real reason to re-engage.
|
|
121
|
+
```
|
|
122
|
+
|
|
123
|
+
---
|
|
124
|
+
|
|
125
|
+
## ADAPTATION RULES
|
|
126
|
+
|
|
127
|
+
- Framework names should be specific — "The [N]-step [Name] Framework" not "here are some tips"
|
|
128
|
+
- Each step should be specific enough to be actionable on its own
|
|
129
|
+
- The implication sentence ("when you have this") connects to the reader's desired outcome
|
|
130
|
+
- Never pitch the product inside the education block — position it as the tool that implements the framework in the CTA
|
|
131
|
+
- "You can steal this" language (from brand kit approved phrases) works well as the bridge from education to CTA
|
|
@@ -0,0 +1,107 @@
|
|
|
1
|
+
# Body Module — Problem / Agitate
|
|
2
|
+
|
|
3
|
+
**Module type:** Body block
|
|
4
|
+
**Block ID:** `problem-agitate`
|
|
5
|
+
**What it does:** Names the specific pain and sharpens it. Makes the reader feel the weight of the problem before introducing any solution.
|
|
6
|
+
**Use in:** Email 1 (nurture, cold outbound), any email where the opening needs to establish stakes
|
|
7
|
+
**Length:** 2–4 sentences
|
|
8
|
+
**Pillar fit:** All pillars — angle the problem to the specific pillar
|
|
9
|
+
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
## HOW THIS BLOCK WORKS
|
|
13
|
+
|
|
14
|
+
The problem/agitate block does three things in order:
|
|
15
|
+
1. Names the problem specifically — not "growth challenges" but the real, nameable thing
|
|
16
|
+
2. Validates that the reader is experiencing it (makes them feel seen)
|
|
17
|
+
3. Sharpens the pain — names what it's costing them or what the downstream consequence is
|
|
18
|
+
|
|
19
|
+
It does NOT introduce the solution. That is the next block's job. Rushing to the solution before the problem is fully felt produces copy that slides off the reader.
|
|
20
|
+
|
|
21
|
+
---
|
|
22
|
+
|
|
23
|
+
## STRUCTURE
|
|
24
|
+
|
|
25
|
+
```
|
|
26
|
+
[NAME THE PROBLEM — 1 sentence, specific]
|
|
27
|
+
|
|
28
|
+
[VALIDATE — 1 sentence, makes them feel seen]
|
|
29
|
+
|
|
30
|
+
[SHARPEN — 1–2 sentences, the downstream cost or consequence]
|
|
31
|
+
```
|
|
32
|
+
|
|
33
|
+
---
|
|
34
|
+
|
|
35
|
+
## TEMPLATE
|
|
36
|
+
|
|
37
|
+
```
|
|
38
|
+
[SPECIFIC_PAIN_POINT] is [specific description of how it's showing up right now].
|
|
39
|
+
|
|
40
|
+
[VALIDATION — they're not alone / they've tried X / they've spent Y trying to fix it]
|
|
41
|
+
|
|
42
|
+
The real cost isn't [obvious cost]. It's [actual downstream consequence — what this is preventing them from doing].
|
|
43
|
+
```
|
|
44
|
+
|
|
45
|
+
---
|
|
46
|
+
|
|
47
|
+
## GROWTHUB-SPECIFIC EXAMPLES
|
|
48
|
+
|
|
49
|
+
### Pillar 1 — Growth System
|
|
50
|
+
|
|
51
|
+
```
|
|
52
|
+
Most businesses trying to scale don't have a growth problem. They have a systems problem.
|
|
53
|
+
|
|
54
|
+
They have budget. They have team. They even have ideas. What they don't have is the infrastructure that makes all of it work together without constant fire-fighting.
|
|
55
|
+
|
|
56
|
+
The real cost isn't the chaos. It's the growth that doesn't happen because the chaos is consuming all the attention.
|
|
57
|
+
```
|
|
58
|
+
|
|
59
|
+
### Pillar 2 — Automation & AI
|
|
60
|
+
|
|
61
|
+
```
|
|
62
|
+
The bottleneck isn't your budget or your team — it's the gap between having a good idea and getting it in market to test.
|
|
63
|
+
|
|
64
|
+
Most performance teams are sitting on a 2–3 week creative production cycle. By the time the ad is live, the insight that generated it is already stale.
|
|
65
|
+
|
|
66
|
+
The cost isn't the production budget. It's every winning concept that died in the pipeline before it ever ran.
|
|
67
|
+
```
|
|
68
|
+
|
|
69
|
+
### Pillar 3 — Client Results (cold/re-engage angle)
|
|
70
|
+
|
|
71
|
+
```
|
|
72
|
+
You've probably invested time and money into creative production that didn't pay off the way it should have.
|
|
73
|
+
|
|
74
|
+
Maybe it was a batch of ads that looked good but didn't convert. Maybe it was a production process that ate budget without improving your win rate.
|
|
75
|
+
|
|
76
|
+
The frustrating part is never knowing whether the problem was the idea, the execution, or the testing — because the process wasn't built to tell you.
|
|
77
|
+
```
|
|
78
|
+
|
|
79
|
+
### Pillar 4 — Education & Strategy
|
|
80
|
+
|
|
81
|
+
```
|
|
82
|
+
Most brands approach creative testing the same way: produce more, run more, hope one sticks.
|
|
83
|
+
|
|
84
|
+
That approach works at low volumes. At scale, it becomes expensive and slow — because you're producing volume without building learning.
|
|
85
|
+
|
|
86
|
+
The thing most performance teams miss is the intelligence layer: the step between running ads and knowing *why* something won.
|
|
87
|
+
```
|
|
88
|
+
|
|
89
|
+
### Pillar 5 — Pipeline & Revenue
|
|
90
|
+
|
|
91
|
+
```
|
|
92
|
+
Your pipeline isn't dead. It's just quiet.
|
|
93
|
+
|
|
94
|
+
Most of the deals that stall aren't lost to a competitor — they're lost to inertia. The prospect was interested. Life got busy. The follow-up stopped.
|
|
95
|
+
|
|
96
|
+
The cost isn't one deal. It's the cumulative pipeline that's been sitting there, un-worked, for months.
|
|
97
|
+
```
|
|
98
|
+
|
|
99
|
+
---
|
|
100
|
+
|
|
101
|
+
## ADAPTATION RULES
|
|
102
|
+
|
|
103
|
+
- Replace `[SPECIFIC_PAIN_POINT]` with the exact pain from the brand kit (`primary_persona.pain_point`)
|
|
104
|
+
- Replace `[VALIDATION]` with context from the brand kit (`primary_persona.current_stage`)
|
|
105
|
+
- Replace `[COST_FRAMING]` with the downstream consequence most relevant to the pillar angle
|
|
106
|
+
- Never use generic pain language ("growth challenges", "struggling with marketing")
|
|
107
|
+
- The problem named must be specific enough that the reader thinks "that's exactly it" — not "that's kind of right"
|
package/assets/worker-kits/growthub-email-marketing-v1/templates/email-modules/body/story-bridge.md
ADDED
|
@@ -0,0 +1,112 @@
|
|
|
1
|
+
# Body Module — Story / Bridge
|
|
2
|
+
|
|
3
|
+
**Module type:** Body block
|
|
4
|
+
**Block ID:** `story-bridge`
|
|
5
|
+
**What it does:** Bridges the insight to real-world proof. Uses a client story, scenario, or concrete example to make the value tangible and believable.
|
|
6
|
+
**Use in:** Email 3–4 (nurture), cold outbound email 3, re-engagement email 2, post-demo email 2
|
|
7
|
+
**Length:** 3–6 sentences
|
|
8
|
+
**Pillar fit:** Pillar 3 (Client Results) is primary; supports all pillars
|
|
9
|
+
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
## HOW THIS BLOCK WORKS
|
|
13
|
+
|
|
14
|
+
The story/bridge block makes the abstract concrete. After the value-reveal block has introduced the insight, this block shows it working in the real world.
|
|
15
|
+
|
|
16
|
+
The story must:
|
|
17
|
+
- Feature a protagonist who matches the reader's persona (same role, similar situation)
|
|
18
|
+
- Include a specific before-state (the pain they were experiencing)
|
|
19
|
+
- Include a specific after-state or result (what changed)
|
|
20
|
+
- Use only approved proof points — never fabricate
|
|
21
|
+
|
|
22
|
+
The story does NOT need to be long. A 3-sentence story with specific details is more powerful than a 10-sentence story with vague generalities.
|
|
23
|
+
|
|
24
|
+
---
|
|
25
|
+
|
|
26
|
+
## STRUCTURE
|
|
27
|
+
|
|
28
|
+
```
|
|
29
|
+
[PROTAGONIST — who they are, their situation before]
|
|
30
|
+
|
|
31
|
+
[WHAT CHANGED — the decision, the shift, or the system they put in place]
|
|
32
|
+
|
|
33
|
+
[THE RESULT — specific, approved, concrete]
|
|
34
|
+
|
|
35
|
+
[THE BRIDGE — connect this to the reader: "this is available to you"]
|
|
36
|
+
```
|
|
37
|
+
|
|
38
|
+
---
|
|
39
|
+
|
|
40
|
+
## TEMPLATE
|
|
41
|
+
|
|
42
|
+
```
|
|
43
|
+
[PERSONA_MATCH — role + situation before Growthub]
|
|
44
|
+
|
|
45
|
+
[WHAT_THEY_DID — the specific change or decision]
|
|
46
|
+
|
|
47
|
+
[RESULT — approved proof point — specific and attributed]
|
|
48
|
+
|
|
49
|
+
The same [system/approach/framework] is what we do with every client. If [READER_QUALIFICATION], this is directly applicable to your situation.
|
|
50
|
+
```
|
|
51
|
+
|
|
52
|
+
---
|
|
53
|
+
|
|
54
|
+
## GROWTHUB-SPECIFIC EXAMPLES
|
|
55
|
+
|
|
56
|
+
### Pillar 2 — Automation & AI
|
|
57
|
+
|
|
58
|
+
```
|
|
59
|
+
One of our clients — a performance director at a DTC brand spending $150K/month on Meta — was stuck. They had budget to scale. They didn't have creatives that could keep up with the spend.
|
|
60
|
+
|
|
61
|
+
They weren't short on ideas. They were short on throughput. Their production cycle was 3 weeks. By the time an ad went live, the hook that inspired it was already outdated.
|
|
62
|
+
|
|
63
|
+
We rebuilt their creative pipeline around a weekly testing rhythm. Within 60 days, they were running 5x more concepts per month at the same production cost — and their win rate went up because every test was generating usable learning.
|
|
64
|
+
```
|
|
65
|
+
|
|
66
|
+
> Note: Replace with approved client story from brand kit. Never fabricate specifics.
|
|
67
|
+
|
|
68
|
+
### Pillar 1 — Growth System
|
|
69
|
+
|
|
70
|
+
```
|
|
71
|
+
An agency owner we work with had been growing for three years — and felt like they were running harder just to stay in the same place.
|
|
72
|
+
|
|
73
|
+
Revenue was up. Margin was down. Every new client meant hiring another person. The business wasn't scaling — it was just getting bigger.
|
|
74
|
+
|
|
75
|
+
The shift wasn't a new tool or a new hire. It was a structural one: building a growth infrastructure that could handle more volume without proportionally more overhead. Six months in, they'd doubled revenue without adding a single person.
|
|
76
|
+
```
|
|
77
|
+
|
|
78
|
+
> Note: Replace with approved client story. Never fabricate specifics.
|
|
79
|
+
|
|
80
|
+
### Pillar 3 — Client Results
|
|
81
|
+
|
|
82
|
+
```
|
|
83
|
+
A CGO at a funded brand came to us after trying two other creative production partners. Both had delivered volume. Neither had delivered learning.
|
|
84
|
+
|
|
85
|
+
The problem wasn't the creatives. It was that the production process wasn't connected to the performance data — so every new brief started from scratch instead of building on what worked.
|
|
86
|
+
|
|
87
|
+
Three months in with Growthub, they had a pattern library: 12 proven hook types, 6 body structures that consistently outperformed, and a brief process that took hours instead of days. They went from 100K to 350K in monthly spend in that period — not because the creatives got better overnight, but because the system started compounding.
|
|
88
|
+
```
|
|
89
|
+
|
|
90
|
+
> Note: Replace with approved client story. Never fabricate specifics.
|
|
91
|
+
|
|
92
|
+
### Pillar 5 — Pipeline & Revenue (re-engagement angle)
|
|
93
|
+
|
|
94
|
+
```
|
|
95
|
+
A client's sales team had a list of 340 "dead" leads — contacts who had gone through demos but never moved forward.
|
|
96
|
+
|
|
97
|
+
Instead of writing them off, we built a 3-email re-engagement sequence anchored on a new case study that directly matched their situation. No pressure. No artificial urgency. Just a relevant, specific reason to reconsider.
|
|
98
|
+
|
|
99
|
+
27% of those contacts replied. 11 booked calls. 4 became clients. The pipeline wasn't dead — it just needed the right trigger.
|
|
100
|
+
```
|
|
101
|
+
|
|
102
|
+
> Note: Replace with approved results. Never fabricate.
|
|
103
|
+
|
|
104
|
+
---
|
|
105
|
+
|
|
106
|
+
## ADAPTATION RULES
|
|
107
|
+
|
|
108
|
+
- The protagonist MUST match the reader's persona — same role, same situation
|
|
109
|
+
- Results MUST be from the approved proof points in the brand kit — never invent
|
|
110
|
+
- If no approved case study matches the situation, use a scenario-based version: "Imagine a [PERSONA_ROLE] who…" — but flag this in the campaign brief
|
|
111
|
+
- The bridge sentence ("the same system/approach is available to you") connects the story to a CTA setup
|
|
112
|
+
- Keep the story tight — 3–4 sentences of story, 1–2 of bridge. No novellas.
|
package/assets/worker-kits/growthub-email-marketing-v1/templates/email-modules/body/value-reveal.md
ADDED
|
@@ -0,0 +1,107 @@
|
|
|
1
|
+
# Body Module — Value / Reveal
|
|
2
|
+
|
|
3
|
+
**Module type:** Body block
|
|
4
|
+
**Block ID:** `value-reveal`
|
|
5
|
+
**What it does:** Introduces the key insight, mechanism, or reframe that resolves the tension set up in the problem block. This is the "so here's the thing" moment.
|
|
6
|
+
**Use in:** Email 2–3 (nurture), all cold outbound emails, any email that delivers an insight or positions the solution
|
|
7
|
+
**Length:** 3–5 sentences
|
|
8
|
+
**Pillar fit:** All pillars — the insight is always pillar-specific
|
|
9
|
+
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
## HOW THIS BLOCK WORKS
|
|
13
|
+
|
|
14
|
+
The value/reveal block delivers one idea completely. It reframes the problem, introduces a mechanism, or names the thing the reader has been missing.
|
|
15
|
+
|
|
16
|
+
Rules:
|
|
17
|
+
- One idea per block. Do not stack reveals.
|
|
18
|
+
- The insight must be specific to the pillar and the audience's situation
|
|
19
|
+
- The reveal should feel like something the reader didn't already know, but immediately recognizes as true
|
|
20
|
+
- It does NOT pitch the product. It delivers value. The CTA comes later.
|
|
21
|
+
|
|
22
|
+
---
|
|
23
|
+
|
|
24
|
+
## STRUCTURE
|
|
25
|
+
|
|
26
|
+
```
|
|
27
|
+
[THE REFRAME OR INSIGHT — 1 sentence, sharp]
|
|
28
|
+
|
|
29
|
+
[EXPLAIN THE MECHANISM — 2–3 sentences, how it works or why it matters]
|
|
30
|
+
|
|
31
|
+
[WHAT CHANGES — 1 sentence, the implication for the reader]
|
|
32
|
+
```
|
|
33
|
+
|
|
34
|
+
---
|
|
35
|
+
|
|
36
|
+
## TEMPLATE
|
|
37
|
+
|
|
38
|
+
```
|
|
39
|
+
Here's the thing most [PERSONA_ROLE]s miss about [TOPIC]: [INSIGHT IN ONE SENTENCE].
|
|
40
|
+
|
|
41
|
+
[Explanation of the mechanism — how it works, why it matters, what's different when you see it]
|
|
42
|
+
|
|
43
|
+
When [INSIGHT_APPLIED], [WHAT_BECOMES_POSSIBLE].
|
|
44
|
+
```
|
|
45
|
+
|
|
46
|
+
---
|
|
47
|
+
|
|
48
|
+
## GROWTHUB-SPECIFIC EXAMPLES
|
|
49
|
+
|
|
50
|
+
### Pillar 1 — Growth System
|
|
51
|
+
|
|
52
|
+
```
|
|
53
|
+
Here's the thing: your ability to scale isn't limited by your budget. It's limited by your infrastructure.
|
|
54
|
+
|
|
55
|
+
Budget scales in a straight line. Infrastructure scales exponentially — it gets more efficient as you grow, not less. The difference between businesses that compound and businesses that plateau is almost always structural, not financial.
|
|
56
|
+
|
|
57
|
+
When you have the right infrastructure, adding budget stops being a risk and starts being a straightforward lever.
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
### Pillar 2 — Automation & AI (the key insight from brand doc)
|
|
61
|
+
|
|
62
|
+
```
|
|
63
|
+
The real constraint isn't production volume — it's the speed from insight to test.
|
|
64
|
+
|
|
65
|
+
Right now, most brands are moving on a 2–4 week cycle: idea, brief, production, launch, learn. By the time you know what worked, the market has moved. Your competitors with a faster feedback loop are compounding learning faster than you can keep up.
|
|
66
|
+
|
|
67
|
+
When you collapse that cycle, testing becomes cheap and fast — and the win rate goes up because you're making decisions from learning, not guesses.
|
|
68
|
+
```
|
|
69
|
+
|
|
70
|
+
### Pillar 3 — Client Results
|
|
71
|
+
|
|
72
|
+
```
|
|
73
|
+
Here's what we see with the brands that break through: they stopped optimizing individual ads and started optimizing the system that produces ads.
|
|
74
|
+
|
|
75
|
+
The insight is subtle but important. It's not "this ad won" — it's "this type of hook + this type of proof + this audience = winner." That pattern only emerges when the production and testing layer is fast and structured enough to capture it.
|
|
76
|
+
|
|
77
|
+
When the system is built for learning, every ad — win or loss — makes the next one better.
|
|
78
|
+
```
|
|
79
|
+
|
|
80
|
+
### Pillar 4 — Education & Strategy
|
|
81
|
+
|
|
82
|
+
```
|
|
83
|
+
The insight most brands miss is what we call the intelligence layer — the step between "we ran ads" and "we know why it worked."
|
|
84
|
+
|
|
85
|
+
Without an intelligence layer, your creative process is essentially random sampling. Some things win. You don't know why. You produce more. You hope. The cost-per-learning stays high because each test is isolated — it doesn't feed anything.
|
|
86
|
+
|
|
87
|
+
With an intelligence layer, every test is a building block. Win or lose, you extract the pattern. The cost-per-learning drops with every cycle.
|
|
88
|
+
```
|
|
89
|
+
|
|
90
|
+
### Pillar 5 — Pipeline & Revenue
|
|
91
|
+
|
|
92
|
+
```
|
|
93
|
+
Here's the thing about stalled pipeline: most of it isn't lost. It's just been left to go cold.
|
|
94
|
+
|
|
95
|
+
The difference between a deal that closes six months late and one that closes never is almost always the follow-up cadence. Not the pitch. Not the product. The systematic, non-pushy re-engagement that keeps the conversation alive without being annoying.
|
|
96
|
+
|
|
97
|
+
When you have the right follow-up infrastructure in place, you stop losing deals to inertia — because inertia is a systems problem, and systems can be fixed.
|
|
98
|
+
```
|
|
99
|
+
|
|
100
|
+
---
|
|
101
|
+
|
|
102
|
+
## ADAPTATION RULES
|
|
103
|
+
|
|
104
|
+
- The insight must be pillar-specific — pull from `skills.md → STEP 4` language patterns
|
|
105
|
+
- The "what changes" statement should connect directly to the reader's desired outcome
|
|
106
|
+
- Never reveal the product mechanics here — this is the idea layer, not the product pitch
|
|
107
|
+
- If this block feels like it's selling, it's not a value-reveal. It's a product pitch in disguise. Rewrite.
|
package/assets/worker-kits/growthub-email-marketing-v1/templates/email-modules/cta/primary-cta.md
ADDED
|
@@ -0,0 +1,116 @@
|
|
|
1
|
+
# CTA Module — Primary CTA
|
|
2
|
+
|
|
3
|
+
**Module type:** CTA
|
|
4
|
+
**CTA ID:** `primary-cta`
|
|
5
|
+
**What it does:** The direct ask — a specific, high-commitment action (book a call, start a trial, claim an offer). Used when the audience is warm enough to take a real step forward.
|
|
6
|
+
**Use in:** Nurture emails 4–5, cold outbound emails 3–4, post-demo emails 1–3, promotional broadcasts
|
|
7
|
+
**Commitment level:** High
|
|
8
|
+
**Pairs with:** PS line (always reinforce)
|
|
9
|
+
|
|
10
|
+
---
|
|
11
|
+
|
|
12
|
+
## HOW PRIMARY CTAs WORK
|
|
13
|
+
|
|
14
|
+
A primary CTA works when:
|
|
15
|
+
1. The trust and value foundation has been built (at least 2–3 emails in a nurture sequence, or a strong single email for warm audiences)
|
|
16
|
+
2. The CTA text is specific about the outcome, not the action
|
|
17
|
+
3. It appears on its own line — not buried in a paragraph
|
|
18
|
+
4. It is reinforced in the PS line
|
|
19
|
+
|
|
20
|
+
**The biggest CTA mistake:** Using "Learn more" or "Click here." These say nothing about what happens next or why it's worth doing.
|
|
21
|
+
|
|
22
|
+
---
|
|
23
|
+
|
|
24
|
+
## TEMPLATES
|
|
25
|
+
|
|
26
|
+
### Booking / Discovery
|
|
27
|
+
|
|
28
|
+
```
|
|
29
|
+
[CTA text]: [URL]
|
|
30
|
+
```
|
|
31
|
+
|
|
32
|
+
Variants:
|
|
33
|
+
- `Book your growth call → [URL]`
|
|
34
|
+
- `Get your custom growth plan → [URL]`
|
|
35
|
+
- `See how it works for your account → [URL]`
|
|
36
|
+
- `Book a 20-minute walkthrough → [URL]`
|
|
37
|
+
- `Reserve your spot → [URL]`
|
|
38
|
+
|
|
39
|
+
---
|
|
40
|
+
|
|
41
|
+
### Demo / Walkthrough
|
|
42
|
+
|
|
43
|
+
```
|
|
44
|
+
Watch how [BRAND_NAME] [OUTCOME] → [URL]
|
|
45
|
+
```
|
|
46
|
+
|
|
47
|
+
Variants:
|
|
48
|
+
- `See the creative velocity system in action → [URL]`
|
|
49
|
+
- `Watch the 3-minute walkthrough → [URL]`
|
|
50
|
+
- `See what [BRAND_NAME] does differently → [URL]`
|
|
51
|
+
|
|
52
|
+
---
|
|
53
|
+
|
|
54
|
+
### Offer / Claim
|
|
55
|
+
|
|
56
|
+
```
|
|
57
|
+
Claim [OFFER] before [DATE/CONDITION] → [URL]
|
|
58
|
+
```
|
|
59
|
+
|
|
60
|
+
Variants:
|
|
61
|
+
- `Lock in [OFFER] → [URL]`
|
|
62
|
+
- `Claim your spot → [URL]`
|
|
63
|
+
- `Start your [trial/audit/assessment] → [URL]`
|
|
64
|
+
|
|
65
|
+
---
|
|
66
|
+
|
|
67
|
+
## PS LINE PAIRING
|
|
68
|
+
|
|
69
|
+
The primary CTA is always reinforced in a PS line. The PS adds a secondary angle, urgency, or a softer version of the same ask.
|
|
70
|
+
|
|
71
|
+
**PS templates:**
|
|
72
|
+
|
|
73
|
+
```
|
|
74
|
+
P.S. [Secondary angle that gives them one more reason to click.]
|
|
75
|
+
```
|
|
76
|
+
|
|
77
|
+
Variants:
|
|
78
|
+
- `P.S. If you're spending $[X]+ on ads and still hitting the creative ceiling — this is worth 20 minutes. [Book here →]`
|
|
79
|
+
- `P.S. This works best for [QUALIFYING CONDITION]. If that's you, book before [DATE/CONDITION].`
|
|
80
|
+
- `P.S. [CLIENT_TYPE] who've done this call say it was the most useful [TIMEFRAME] they spent on their growth strategy. Worst case: you leave with a clear picture of where the bottleneck actually is.`
|
|
81
|
+
|
|
82
|
+
---
|
|
83
|
+
|
|
84
|
+
## GROWTHUB-SPECIFIC PRIMARY CTA EXAMPLES
|
|
85
|
+
|
|
86
|
+
**For warm nurture / post-demo:**
|
|
87
|
+
```
|
|
88
|
+
Book your growth call → [URL]
|
|
89
|
+
|
|
90
|
+
P.S. If removing the creative bottleneck is the constraint right now, this is the right 20 minutes. [Book here →]
|
|
91
|
+
```
|
|
92
|
+
|
|
93
|
+
**For mid-funnel nurture:**
|
|
94
|
+
```
|
|
95
|
+
See how it works for your account → [URL]
|
|
96
|
+
|
|
97
|
+
P.S. Every brand we work with starts with a look at where their creative process is actually losing time. The call is free and the insight is useful regardless. [Book here →]
|
|
98
|
+
```
|
|
99
|
+
|
|
100
|
+
**For promotional:**
|
|
101
|
+
```
|
|
102
|
+
Claim your spot for [OFFER] → [URL]
|
|
103
|
+
|
|
104
|
+
P.S. This closes [DATE]. After that it goes back to [standard price/process]. If you've been thinking about it — now is the right time.
|
|
105
|
+
```
|
|
106
|
+
|
|
107
|
+
---
|
|
108
|
+
|
|
109
|
+
## RULES
|
|
110
|
+
|
|
111
|
+
- One primary CTA per email — no stacking
|
|
112
|
+
- CTA text is verb-first and outcome-specific — never "click here" or "learn more"
|
|
113
|
+
- CTA is always on its own line
|
|
114
|
+
- CTA URL is always confirmed live before platform handoff
|
|
115
|
+
- PS always reinforces the primary CTA or adds a compelling secondary angle
|
|
116
|
+
- Do not use a primary CTA in Email 1 of nurture or cold sequences — trust must be built first
|