Catalog

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.

Walkthrough
Lines 1–8 pull `items` from the cache with no validation. Lines 10–18 loop and sum `item.price * item.qty`. Lines 20–22 return the total as a float.

Assumptions
1. The cache always returns a list → None raises AttributeError at line 10.
2. Every item has `price` and `qty` → legacy rows without `qty` raise KeyError mid-loop; partial sums are lost.
3. `price` is numeric → a string price silently concatenates on some paths. Dangerous.
4. The list is not mutated during iteration → a concurrent cache refresh mutates it; totals come back inconsistent with no error. Dangerous.
5. An empty list means a zero total → returns 0 silently; callers cannot tell "no items" from "free". Dangerous.

Verdict on your concerns: concurrency — unsafe; error handling — none; empty list — silent zero.

Tests
- items = None → a clear 500 with a logged cause
- one item missing qty → validation error naming the item id
- 10k items during a cache refresh → a consistent snapshot or a retry

Confirm the diagnosis and I will propose a patch.

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.

Node list
1. Stripe Trigger — fires on checkout.session.completed — reads nothing upstream.
2. Notion — Create database page in "Customers" — Email ← $json.customer_details.email; Plan ← $json.metadata.plan; Amount ← $json.amount_total / 100; Date ← $json.created.
3. Slack — Post to #revenue — "New paid signup: {email} on {plan} ({amount} USD)" built from the same fields.

Workflow JSON: attached below, importable; credentials referenced as "Stripe account", "Notion workspace", "Slack bot" — create those three in Credentials before activating.

Error path: Error Trigger workflow "Alerts" → Slack #ops with the failing workflow name, the item's customer email, and the error message.

Test plan: in the Stripe Trigger node, click "Listen for test event", then send a test checkout.session.completed from the Stripe dashboard → Notion shows one row with the four fields → Slack shows one message → execution list shows green.

Smallest v1: this is already the smallest version (3 nodes). Add the welcome email as node 4 next week, after you have watched this run for a few days.

Top 5 unmet needs (67 interviews)

1. Onboarding takes too long — 41 customers
   "I gave up before my first usable result." (I-12) · "Two evenings to set up something I wanted to try in ten minutes." (I-38)
   Trigger: trying the product between meetings, on a phone.
2. Sharing with the team is friction — 33
   "I ended up screenshotting the dashboard into Slack." (I-05)
3. Integration with the existing stack — 29
4. Pricing surprise in month two — 24
5. Progress does not sync between devices — 18

Early signals
- Offline mode — I-12, I-38, I-51: "I'd pay for it to just work on the train." Unprompted in three separate interviews; not noise.
- Public API — I-22 only.

Contradictions
- 14 customers want fewer notifications; 9 want a daily nudge. Both groups are under 30 days in.

Say vs. want
- Say: "more features." Want, from behaviour: the three they already use to be faster. (I-07, I-44)

Follow-ups for next round
1. "What did you expect to have working within ten minutes?"
2. "Who else looks at this, and how do they see it today?"

Ranked causes

1. Creative launch pushed spend into a worse-converting audience (fit: HIGH)
Mechanism: three new creatives entered learning Monday; Meta over-delivers early impressions to cheap, low-intent placements.
Supports: spike begins the same day; recovery by Sunday matches a 5–7 day learning window.
Contradicts: nothing in the inputs — but you have not split CAC by creative yet.

2. Competitor promo raised auction prices Tue–Thu (fit: MEDIUM)
Supports: Tuesday start; CPM data would show it.
Contradicts: the spike started Monday, a day before the promo.

3. +30% budget scale on the top campaign reset learning (fit: MEDIUM-LOW)
Supports: scaling same day. Contradicts: a 30% step rarely resets learning on its own.

Next data cut: CAC and CPM by creative, by day, Mon–Sun. If the three new creatives carry a CAC over $90 on Mon–Wed while legacy creatives stay near $48, cause 1 is confirmed.

Not considered: a tracking gap — check whether the pixel fired normally Mon–Wed before trusting any of this.
Do not: pause the new creatives today. You would destroy the data that tells you which of them is fine.

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.

Convergence
1. D2C ed-tech CAC has risen 30–40% over 18 months — McKinsey (n=200 companies), a16z note, Coursiv S-1 excerpt. Representative: "blended CAC up 36% YoY" (McKinsey). Confidence HIGH.
2. Subscription outperforms one-time pricing for content products — all four. Confidence HIGH.
3. Trial length matters less than trial-to-paid messaging — three of four; the fourth is silent. Confidence MEDIUM.

Biggest disagreement
McKinsey: auto-renewal optimisation is the largest revenue lever. a16z: cohort-driven retention beats it. Stronger side: McKinsey — 200-company sample versus a16z's four anecdotes, and McKinsey's data is 2025 while a16z's examples are 2023.

The question none of them answers
What happens to LTV when you send an honest reminder before auto-renewal. Likely gap: no operator has run it at scale, and the consultancies are paid by companies that do not want to.

Read or measure next: your own month-3 retention by acquisition channel — every source above assumes it is uniform, and for your decision it is the number that matters.

VOICE OF CUSTOMER — GrowNest (30 reviews, App Store, 3 competing apps)

Top 5 pains
1. "it was fine in the shop and now it's dropping leaves" (11)
2. "I can't tell if I'm overwatering or underwatering" (9)
3. "every blog says something different" (7)
4. "the reminders nag me but never tell me why" (5)
5. "I've killed three of these already" (4) — EARLY SIGNAL: one reviewer, "I'd honestly given up on plants"

Top 5 dream outcomes
1. "finally know what's wrong before it's too late" (8)
2. "it just told me: less water, more light. done." (6)
3. "my monstera actually grew a new leaf" (5)
...
Recurring words: dropping, yellowing, overwatering, "no idea", nag, finally, survive, confident, "too late", simple
Words to avoid: ecosystem, curated, holistic, "plant parent", elevate

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.

Weekly briefing — AI search and research tools, 29 Apr – 6 May

1. ChatGPT Deep Research extended to 30-minute runs with export (OpenAI release notes, 2 May) — Why: your "research faster" lesson shows a 5-minute run; the screenshots are stale. Do: re-capture by Friday.
2. Perplexity Spaces adds shared instructions for teams (Perplexity blog, 30 Apr) — Why: your team-research module assumes personal Spaces. Do: a one-paragraph update.
3. Google AI Mode expands to 12 countries incl. DE and ES (Google blog, 1 May) — Why: 40% of your traffic is DE/ES; organic click-through will move. Do: watch Search Console for two weeks.
4. Anthropic raises Claude file limits (Anthropic docs, 3 May) — Why: your "upload 400 pages" lesson can cite a bigger number. Do: nothing yet.
5. Perplexity reported raising at $18B (The Information, 5 May) — unverified, single source — affects nothing you ship.

Safe to ignore: the "AI search is dead" essay — opinion, no data.
Quiet item: AI Mode ad formats mentioned in a Google developer note (4 May) — if ads enter AI answers, your CAC assumptions change in Q3.

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.