Bad News Email That Leads With the Plan

WEEK 1 (Educate → Entertain → Showcase → Educate → Sell → Behind-the-scenes → Entertain)

Mon · Educate · Hook: "Most niacinamide serums are water with a marketing budget." · Format: carousel, 5 slides · CTA: save this
Tue · Entertain · Hook: "Okay, controversial: your skin does not need 12 steps." · Format: talking-head reel, 20s · CTA: reply with your step count
Wed · Showcase · Hook: "Tested the new cleanser on a real face for 6 weeks. Notes inside." · Format: before/after photo · CTA: link in bio
Thu · Educate · Hook: "Weirdly, the most-asked question this month: safe during pregnancy?" · Format: single image + long caption · CTA: share with someone who asked
Fri · Sell · Hook: "Discontinued the toner. It wasn't pulling its weight." · Format: product photo · CTA: shop the 3 that stayed
Sat · Behind-the-scenes · Hook: "Our lab at 7am looks nothing like the ads." · Format: 15s b-roll · CTA: none
Sun · Entertain · Hook: "Things dermatologists say at dinner parties." · Format: text-on-screen reel · CTA: tag a friend

Never sells twice in a row; each week opens with a save-worthy educate post.

Day 1 — Opener
Subject: eight AEs, one playbook
Sam — you posted eight AE roles this month, and the Head of Enablement seat has been open since April. Eight new reps and no owner for onboarding usually means ramp drifts past a quarter. Vanta had the same gap; our playbook cut their ramp from 14 weeks to 6. Is ramp time something you are measuring this quarter — yes or no?

Day 4 — Follow-up 2 (proof)
Sam — one number from the Vanta work, in case it is useful whether or not we talk: week-3 call volume per new AE doubled once the playbook replaced shadowing. Happy to send the one-page summary. Want it?

Day 8 — Follow-up 3 (question only)
Sam — genuine question, no pitch: when the eight AEs start, who owns their first 30 days?

Day 14 — Breakup
Sam — I will stop here. If ramp becomes the problem in Q3, the playbook summary is one reply away. Good luck with the cohort.

Cadence rule: every message carries something new — proof, a question, or an exit. Never "bumping this".

Mode: rewrite. Context: linkedin. Voice: inferred from the source (upbeat founder launch, first-person plural), kept.

Source (54 words):
> In today's fast-paced world, remote teams face a myriad of challenges. That's why we're thrilled to unveil Standup Bot — a game-changing tool that seamlessly streamlines your daily check-ins. It's not just a bot; it's a catalyst for collaboration. Whether you're a startup or an enterprise, Standup Bot has you covered. Let's dive in!

Issues found
- P1, formulaic opening: "In today's fast-paced world". Broad context before the point.
- P1, Tier 1A vocabulary: "game-changing", "seamlessly"; "Let's dive in!" is a "Let's" opener plus a Tier 1A hit, and nothing follows it.
- P1, template phrase (false breadth): "Whether you're a startup or an enterprise, Standup Bot has you covered".
- P1, "It's not X, it's Y": "It's not just a bot; it's a catalyst for collaboration."
- Tier 2 cluster (three in one paragraph): "myriad", "streamlines", "catalyst".
- Significance inflation: "a catalyst for collaboration" with nothing about what changes.
- Not flagged: one em dash (the linkedin profile allows two); "we're thrilled" is the writer's own launch voice and stays.

Rewrite
> Remote teams have a lot on their plate. That's why we're thrilled to launch Standup Bot, a tool that makes your daily check-ins simpler.

What changed: replaced the opener with a plain statement of the same idea; kept "That's why we're thrilled" and the second-person "your"; "unveil" became "launch"; "game-changing tool that seamlessly streamlines" became "a tool that makes … simpler", the only factual claim the source made; cut the "not just X" line, the false-breadth line and "Let's dive in!". No new dashes, fragments, stakes or claims added.

Gap left for the writer: the post never says what Standup Bot does, who it is for, or what "catalyst for collaboration" means. One concrete sentence from you would do more than anything an editor can add.

Second pass on the rewrite: Tier 1–3 vocabulary none; em dashes 0; templates none; rhythm 8 then 17 words. Remaining risk: brevity.

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.

v1.8.0 — 2026-11-06

New
- Library shows what you own. Prompts and skills you bought or claimed now live under *Library*, with copy and download on each card.
- Trending sort. The catalog can rank by installs in the last 14 days.

Improved
- Product pages load the preview gallery before the long description, so the first frame is the result, not the pitch.
- Search matches taglines as well as titles.

Fixed
- Copying a prompt no longer counts twice toward the daily Pro quota.
- Downloads from Safari keep the `.zip` extension.

Upgrade notes
- Run migrations `0028`–`0029` before deploying the API (new tables, no data changes).
- `LEGACY_WORKERS` defaults to off; set it to `true` only if you still send the recovery drip.

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.