Catalog

HERO HEADLINE VARIANTS — current: "Smart plant care, powered by AI"

1. Pain framing — "Your fiddle leaf is not dying. It is asking for one thing." (lever: pain)
2. After-state — "Know what your plant needs before the next leaf drops." (lever: outcome)
3. Specificity — "Diagnose yellow leaves in 2 minutes from one photo." (lever: specificity)
4. Contrast — "Every blog says something different. Your plant says one thing." (lever: pain)
5. Number — "4 days. That is how long you have after the first leaf drops." (lever: specificity)
6. Confession — "We built this after killing nine plants in one apartment." (lever: proof)
7. Command — "Stop watering on a schedule. Start reading the leaves." (lever: after-state)
8. Reader quote — "I did not do anything wrong — I just was not told." (lever: voice)
9. Question-free curiosity — "The third thing nobody mentions about overwatering." (lever: specificity)
10. Promise — "Your next plant survives. This one might too." (lever: outcome)

Test first: #2 against #3 — same lever family, different specificity; the winner tells you whether the audience wants reassurance or precision.

Validation page — "Stop reinventing your client kickoff every Monday."

Promise bullets:
- 12 Figma templates that map to the briefs clients actually send
- A Notion brief generator: 4 questions in, a fillable scope out
- A 9-question client questionnaire that ends the "can you just tweak this?" loop

Objection handler: "Not a course. Not a community. Just the four files you wish someone had given you in year one."
CTA: "Pre-order for $49 — ships in 14 days. Refund if you don't use it."

Red team (as an investor who watched ten of these fail): the failure mode you are underestimating is not demand, it is the second purchase. Templates sell once; the Notion generator is the only piece with a reason to come back. Measure: of the first 50 buyers, how many open the generator twice in 30 days. If under 20%, the next product is a generator, not more templates.

Milestone 1 — validation page live · acceptance: 25 pre-orders in 7 days from $100 of ads and 20 DMs.

BRAND BRIEF — Northwood Beard Oil

1. Positioning
We help men 28–45 with full beards stop smelling like drugstore musk. We can do this because a third-generation perfumer blends 14 natural notes other beard brands will not pay for.

2. Audience snapshot
- Situation: has worn the same $9 oil for years; wife or colleague has commented on the smell
- Trigger: a wedding, a new job, or the bottle running out
- Tried: "premium" brands that still lean on synthetic musk
- Fears: smelling like a teenager's locker; paying $40 for marketing

3. Promise
A scent people ask about, not one they step away from — within the first week.

4. Voice rules
Do: short declaratives ("Three notes. Zero musk.") / Don't: "elevate your grooming ritual"
...
6. Instruction for future prompts
Use this brief. Never use "elevate", "curated", "ritual". Always name a specific scent note.

Skeptic re-read: "Third-generation perfumer" is doing all the work — if it is not provable on the site, the positioning collapses to "nice smell". Holds only with proof.

Proposal — Loom · AE Onboarding Playbook Pilot

On Tuesday you said the eight incoming AEs have "no shared playbook" and that "ramp is going to kill us by Q2". You put current ramp at "14 weeks if we're honest" and a loaded AE at "about $140k".

Success: first cohort productive — first closed deal — inside 6 weeks instead of 14.

You said → What we do about it
"no shared playbook" → two-week build with your top two reps, delivered as a 5-day onboarding track
"ramp is 14 weeks" → week-1 to week-6 milestones with a manager checklist, so ramp is measured, not felt
"we tried a doc once and nobody read it" → every module ends with a recorded role-play a manager reviews in ten minutes

Timeline: build weeks 1–2; cohort onboarding weeks 3–8; review week 9.

Investment: $18,000. Payback: 8 AEs × 8 weeks saved × ($140k ÷ 52) ≈ $172k of ramp cost recovered. Breakeven at one AE.

Next step: a yes by Friday the 13th to start the build on the 16th.
Risk you raised: "our reps won't do homework" — modules are under 20 minutes and done live with the manager.

PILLAR — "The async standup playbook: how 14 distributed teams dropped the 9 AM call"
Keyword: async standup (~1,900/mo) · Intent: informational, late-stage
Gap in current top results: none give a template by team size; all assume 5–8 people.
H2s: Why the sync standup breaks past 3 time zones / The 3 formats by team size / Slack + Notion templates / What to do when nobody posts / Daily vs weekly / Tools compared honestly

Supporting articles
1. "Async standup template (Slack and Notion versions)" — async standup template (~720) · transactional · links to H2 #3
2. "Why your async standup is being ignored — and the 3-line fix" — async standup not working (~210) · informational · H2 #4
3. "Daily or weekly async standup for a 6-person team?" — daily vs weekly standup (~140) · comparison · H2 #5
4. "Async standup across 5+ time zones: what actually works" — async standup timezone (~95) · informational · H2 #1
...
Publishing order: 1, 2, 4 first (quick wins, low competition), pillar in week 3, remaining support weeks 4–6.

Subject: Launch moves to the 28th — plan attached

Jamie — I am moving the launch from the 14th to the 28th.

Two reasons. The security review surfaced one issue we want to fix properly rather than patch, and the marketing site needs one more full week of build. The rest of the timeline holds; the partner webinar on the 30th is unaffected.

Already handled: the fix is scoped and owned by Priya; the new site copy is in legal review. I need two things from you — approval of the new date, and a release of the email send that is booked for the 14th.

I will post a five-minute pulse in #launch every morning until the 28th.

— Alex

Questions you will get back:
- "Why didn't we catch the security issue earlier?" → It was found by the external review we scheduled for exactly this reason; that is the process working.
- "What else could slip?" → Nothing on the critical path; the only open risk is legal turnaround on copy, which has a Friday deadline.

Subject: Your pricing page is lying to you
Preview: Three founders raised prices last month. Two regret it.

Headline: The pricing change that costs more than it earns

1. The claim — Raising prices 20% sounds like free margin. For two of three founders I spoke to this month it cut net revenue, because the churn arrived three months later and nobody connected it.
2. The mechanism — Annual customers do not leave on day one. They leave at renewal, which is after you have already celebrated.
3. The numbers — Founder A: +20% price, −11% net revenue by month 5. Founder B: +15%, +9% — the difference was a grandfather clause.
4. What I would do — Raise for new customers only. Measure renewal cohorts for two quarters before touching existing plans.

CTA: Reply with your last price change and the month you measured it. I will tell you if you measured too early.

Cuts the author will push back on: the opening anecdote about the coffee shop (300 words, no number); the second example that repeats the first; "I think" ×6.

Voice rules

- Sentence length: 4–10 words. Never a sentence over 14.
- Tone: dry, mildly self-deprecating, never preachy. "Okay, controversial:" / "Weirdly, the most-asked question this month" / "Sorry. Also not sorry."
- Words used often: actually, okay, weirdly, notes inside, for a real face
- Words never used (peers use them): journey, elevate, unlock, glow-up, self-care, ritual, holy grail, obsessed
- Emoji: one at the end, never mid-caption. 🌿 or 😌.
- Hooks: a contrarian observation stated flat, never a question.
- Closes: one short verdict, no CTA.

New captions (launch week)
1. Most niacinamide serums are water with a marketing budget. Ours isn't. 🌿
2. Okay, controversial: your skin does not need 12 steps. It needs 3 that work.
3. Tested the new cleanser on a real face for 6 weeks. Notes inside.
4. Weirdly, the most-asked question this month: "safe during pregnancy?" Yes.
5. Discontinued the toner. It wasn't pulling its weight. Sorry. Also not sorry. 😌
...
Drift check: #7 uses a question hook; #9 runs 16 words. Cut both.

1. Three weeks ago it was perfect. Now it loses a leaf every other day.
2. The plant in the shop window is not the one in your living room.
3. You did not do anything wrong. Nobody told you the one thing it needs.
4. It is not the light. It is not the water. It is the third thing.
5. Day 21: the soil is wet, the leaves are yellow, the blog says "just wait".
6. Confession: I killed four of these before I learned to read the leaves.
7. Your plant has been asking for help for two weeks. You just did not speak the language.
8. 80% of dropped leaves come from the same two mistakes. Both are fixable tonight.
9. Still watering on a schedule? That is the thing killing it.
10. The nursery tag said "easy". The nursery tag lied.

Cold landing page: #2 — the contrast is visual and lands in one read.
Warm email: #3 — removes blame, which is what a subscriber who already feels guilty needs first.

Subject: eight AEs, one playbook

Sam — you posted eight AE roles this month, and the Head of Enablement role is still open from April.
Eight new reps and no owner for onboarding usually means ramp drifts past a quarter while everyone is "about to" write the playbook.
Vanta had the same gap last year; our playbook cut their AE ramp from 14 weeks to 6.
Is ramp time something you are measuring this quarter — yes or no?

— Dana

Backup first line (if the roles are filled by send time): "Saw the eight AEs you hired this spring — congratulations, and sympathies for whoever owns their ramp."

Subject: the 14-week ramp

Sam — on the call you said ramp "is going to kill us by Q2" if the eight new AEs land without a playbook. That line has stayed with me, which is why I am writing rather than waiting.

I know a quiet week usually means priorities moved, not that the problem did.

Two options: A — we start a two-week pilot with the first cohort on Thursday the 19th; B — we park it until the cohort is hired and I check back the first week of July. Reply "A" or "B" and I will handle the rest.

If this is a no, a one-line "not now" is genuinely fine — it lets me stop guessing.

— Dana

LinkedIn version:
Sam — your "ramp will kill us by Q2" line is still on my notepad. Pilot Thursday, or park it till July? A or B is enough.

Edited draft

AI lessons that take 15 minutes a day. Used by 12,000 professionals in 40 countries. Start your free 5-day trial.

Change log
- "a revolutionary AI-powered learning experience" → "AI lessons that take 15 minutes a day" — "revolutionary" is a tell; 15 minutes is a number the reader can picture
- "empowering professionals worldwide to thrive" → "used by 12,000 professionals in 40 countries" — abstraction replaced with proof
- "Begin your transformative journey today" → "Start your free 5-day trial" — the actual offer is more persuasive than the metaphor
- cut "seamlessly", "cutting-edge", "unlock" — adjectives with no referent
- "trusted by teams" → [NEEDS NUMBER] — kept, but it needs a count or a name

Weakest remaining line: "40 countries" is impressive only if the reader is outside the US; consider replacing with a named company.