AI prompts and skills that write text (2026)

Use case: Product teaser (template 1)

| Element | Value |
|---|---|
| Subject | A matte black ceramic pour-over coffee dripper with a thin polished copper rim, sitting on a clear glass carafe |
| Action | 1) A thin stream of dark coffee trickles from the dripper into the carafe while soft steam curls up from the rim; 2) the dripper and carafe turn a slow quarter turn; 3) the final second holds still on the dripper's front, copper rim catching the light |
| Scene | A walnut kitchen counter by a window, early morning just after sunrise, a faint haze of steam in the air, uncluttered background |
| Angle / Move | Vertical close-up at counter height, slightly above eye level / slow dolly in |
| Lens | 85mm-style telephoto feel, shallow depth of field, kitchen background in soft bokeh |
| Light / Palette / Mood | Soft low-angle morning sunlight from a window on the left with gentle fill and a warm rim on the copper / matte black, warm copper, honey-brown walnut, soft cream highlights / calm, quiet, unhurried |
| Style / Time | Premium commercial look, photorealistic / real-time pace, steady trickle throughout, still hold in the last second |
| Audio | Close, clear coffee trickling into glass, a faint soft drip, quiet low morning room tone, no music |
| Negative | text, logos, letters, labels, hands, people, clutter, reflections of people, plastic look |

Final prompt (paste into Veo / Gemini / Flow):

Premium commercial look, photorealistic, vertical close-up at counter height of a matte black ceramic pour-over coffee dripper with a thin polished copper rim, sitting on a clear glass carafe on a walnut kitchen counter by a window in the early morning just after sunrise. A thin stream of dark coffee trickles from the dripper into the carafe while soft steam curls up from the rim, and the dripper and carafe turn a slow quarter turn. Slow dolly in, 85mm-style telephoto feel, shallow depth of field with the kitchen background in soft bokeh. Soft low-angle morning sunlight from a window on the left with gentle fill and a warm rim light catching the copper, palette of matte black, warm copper, honey-brown walnut and soft cream highlights, calm and quiet mood. Real-time pace; the final second holds still on the dripper's front.
Audio: close, clear sound of coffee trickling into a glass carafe, a faint soft drip, quiet low morning room tone, no music.
Negative prompt: text, logos, letters, labels, hands, people, clutter, reflections of people, plastic look

Settings: 9:16, 8 seconds, audio on.

Beat sheet

| Beat | Purpose | What the viewer must get | Seconds |
|---|---|---|---|
| 1 | Hook | A reporter in the rain, recording a source who is trusting him with something | 4 |
| 2 | Problem / stakes | The recording is precious and private; the small device in his wet hand is what holds it | 4 |
| 3 | Reveal | Later that night, at home, he sets Fieldnote down and starts it working | 4 |
| 4 | Proof | The words appear on its own e-ink screen: transcribed on the device, no laptop, no cloud | 8 |
| 5 | Payoff + CTA | He has every word, privately; music enters; end line | 4 |

Storyboard table (shots 1–3 of 6)

| # | Sec (gen → use) | Framing | Camera move | Subject action | Dialogue / on-screen text | Audio / ambience | Continuity notes |
|---|---|---|---|---|---|---|---|
| 1 | 4 → 4 | Medium shot, eye level, over the source's shoulder (her back soft in frame-left foreground); he stands under the awning facing screen left | Slow handheld push-in | Holds Fieldnote out toward her at chest height; listens; gives one small nod | Source (on camera, from behind): "They said it would stay between us." | Location A bed; her voice close; rain on the awning | Location A. Faces screen left. Recorder in his right hand, red light on. Jacket zipped halfway, wet shoulders. |
| 2 | 4 → 4 | Extreme close-up on his right hand holding Fieldnote, the source's coat a soft blur beyond | Static | Rain beads on the graphite body; the red light glows steadily; his thumb shifts once on the edge | VO: "What they tell me stays with me." | Location A bed, close rain ticks on the device | Location A. Recorder points screen left. Screen pale grey and blank. Ends with recorder centred, for a match cut. |
| 3 | 4 → 4 | Medium close-up on the kitchen table under the pendant lamp | Static | His right hand enters from frame right and sets Fieldnote down, centred; his thumb presses the round button; hand withdraws | none | Location B bed; soft tap of the recorder on wood; one button click | Location and lighting change (B). Match cut from shot 2 on recorder position. Device dry now, red light off. |

[The full answer continues with shots 4–6 and a coverage alternate, the ten-line continuity block pasted word for word into all seven shot prompts, each prompt's first and last frame, and the stitch plan with voice-over script, caption placement and export settings.]

Assumption: no n8n-MCP server is connected in this session, so I took the skill's fallback path: I wrote the workflow JSON directly from the bundled rules and checked it by review (a rule-check script plus a dry run of every expression). The real validator (`validate_workflow`) was not run, and nothing was deployed.

How the skill routed this

| Step | Sub-skill used | What it decided |
|---|---|---|
| Shape | `n8n-workflow-patterns` | Webhook processing pattern: Webhook, then Validate, then Action, then Respond |
| Node parameters | `n8n-node-configuration` | Slack post needs a channel and text. `responseMode: "responseNode"`. `options.responseCode` set on every Respond node. UUID node ids, no placeholder credentials |
| Expressions | `n8n-expression-syntax` | Webhook data lives under `.body`. Use `$('Webhook').item.json.body.*` once past the IF node. `=` prefix on every expression field |
| Error paths | `n8n-error-handling` | Slack gets `onError: "continueErrorOutput"` and its `main[1]` is wired to the 500 responder. `retryOnFail` is on. Bad input is caught upstream and gets a 400 |
| Validation | `n8n-validation-expert` | Runtime-profile checks done by review. Security warnings get fixed (header auth on the webhook) |

```
Webhook ──> Validate Input ──true──> Post to #signups ──success (main[0])──> Respond 200 OK
                        └──false──> Respond 400 Invalid Input
                                     Post to #signups ──error (main[1])────> Respond 500 Slack Failed
```

Validation result (excerpt)

```
PASS  Webhook responseMode is responseNode (Respond nodes control the reply)
PASS  Every branch (success and each error) ends at a Respond to Webhook node: no hanging branch
PASS  'Post to #signups': onError=continueErrorOutput AND main[1] wired
PASS  'Post to #signups': retryOnFail with maxTries <= 5 and waitBetweenTries <= 5000
PASS  Every {{ }} field starts with = (no 'Expression requires = prefix' error)
PASS  Webhook fields read from .body, never $json.name / $json.email / $json.plan
…
43 passed, 0 failed
```

Expression dry run against sample webhook items:

```
valid           IF -> true  (Slack)  Slack text: New signup: Ana Lima (ana@example.com) on pro
missing_plan    IF -> false (400)
bad_email       IF -> false (400)
no_body         IF -> false (400)
500 body:   {"error":"upstream_error","message":"The signup was received but could not be posted to Slack. Please retry later."}
```

Not verified without the server: the node typeVersions (Webhook 2.2, IF 2.3, Slack 2.3, Respond 1.5) and the Slack v2 parameter names; confirm by opening the nodes after import.

[The full answer also holds the six-node list, the importable workflow JSON and the expressions table with the reason behind each one.]

Phase 1: Root cause investigation
Full suite: FAIL test_expired_coupon_rejected_twice (tests/test_checkout.py:16) AssertionError: Coupon(code='OLD50', …expires_at=2020-01-01…) is not None.
In isolation the same test fails at a different line (17): AssertionError: 50.0 != 100.0. So the first lookup in a process is rejected and every later lookup is accepted; in the full suite the first lookup was done by test_expired_coupon_rejected. Cross-test pollution through module-level state.
Cache probe at the boundary: cache before [] → 1st None → cache after ['OLD50'] → 2nd Coupon(OLD50). Docstring says the cache was added in 3f2a1c9 "to cut DB reads": that is the regression point.
Trace (root-cause-tracing.md): apply_coupon → get_coupon → `if code in _CACHE: return _CACHE[code]`. get_coupon writes the coupon to _CACHE before the expiry check, and the cache-hit branch has no expiry check at all.

Phase 2: Pattern analysis
Working path: cache miss → _load → expiry check. Broken path: cache hit. Expiry depends on `now`, passed per call, so it cannot be a cached property; "don't cache expired coupons" alone would still serve a coupon cached while valid after it expires.

Phase 3: Hypothesis
"get_coupon returns cached coupons without re-checking expires_at against the caller's now; the cache was added around the lookup but the validity check stayed only on the miss path." Confirmed by the probe above.

Phase 4: Implementation
Failing test first: test_cached_coupon_rechecked_for_expiry (look up while valid, then after expiry) plus a setUp that clears the module cache. Before the fix: 5 tests, 2 failures, both for the expected reason.
Fix at the source: the cache stores the raw record; the expiry check runs on every lookup, cached or not.

    c = _CACHE.get(code)
    if c is None:
        c = _load(code)
        if c is None:
            return None
        _CACHE[code] = c
    if c.expires_at < now:
        return None
    return c

Verification: python3 -m unittest -v → Ran 5 tests … OK. The originally failing test in isolation, 3 runs: OK, OK, OK. Fix attempts: 1.

Scope: app/dashboard/page.tsx and the modules it imports (components/charts, UsageCard, ProjectList, RichTextEditor, lib/api.ts).

| # | Rule | File:line | Impact | Finding |
|---|---|---|---|---|
| 1 | async-dependencies | app/dashboard/page.tsx:8-10 | CRITICAL | getProjects(user.id) and getUsage(user.id) depend only on `user` but are awaited one after the other: 3 sequential round trips before any HTML is sent, where 2 would do. Promise.all them. |
| 2 | bundle-barrel-imports | components/ProjectList.tsx:3 | CRITICAL | `import _ from 'lodash'` in a 'use client' file ships all of lodash for one sortBy. Use lodash/sortBy, or toSorted / localeCompare. |
| 3 | async-suspense-boundaries | app/dashboard/page.tsx:7-19 | HIGH | The whole page, including the static shell and RichTextEditor, waits for all three fetches. Move usage and projects into async children in <Suspense> so the shell streams first. |
| 4 | server-serialization | app/dashboard/page.tsx:16 | HIGH | The raw projects array goes to client ProjectList, which reads only id, name and status. Map to {id, name, status} on the server. |
| 5 | rerender-no-inline-components | components/ProjectList.tsx:7 | HIGH | `Row` is defined inside ProjectList, so every keystroke in the filter remounts every <li>. Interaction cost, not first load. Hoist Row. |
| 6 | rerender-derived-state-no-effect | components/UsageCard.tsx:4-5 | MEDIUM | percent is kept in state and set in useEffect: server HTML renders "0% of plan used" and the real value appears only after hydration. Compute it during render. |

Score: 62 / 100 (100 − 2×10 CRITICAL − 3×5 HIGH − 1×3 MEDIUM). This counts rule findings; it is not a measured load time.

Checked and not scored: the local charts barrel (five tiny stubs, tree-shakeable); RichTextEditor is a <textarea> today, so no dynamic import yet. Not a performance rule but it blocks the build: components/charts/index.ts re-exports names the chart files do not export, and page.tsx reads `params.id` synchronously though params is a Promise in Next 15.

What makes the first load slow, in order:
1. The server waterfall (rows 1 and 3). Parallelizing projects and usage removes one full round trip; Suspense lets the header paint after only getUser.
2. Client JS weight (row 2). A one-line import change.
3. Payload and first-paint correctness (rows 4 and 6).
Row 5 is an interaction cost; fix it after the others. Fixes were not requested, so no files were changed.

Short answer: ChatGPT can't recommend Ledgerly, because nothing it can retrieve says Ledgerly exists. Even after launch, a single landing page is not enough. A "best X for Y" shortlist comes from web-wide consensus (reviews, roundups, forums, press), not from your own site.

Visibility ladder (retrieved → cited → mentioned → recommended)
| Rung | Ledgerly today | What governs it |
|---|---|---|
| 1. Retrieved | No: not live, not in Bing's index (ChatGPT search draws from a Bing-based index) | Being indexed and crawlable |
| 2. Cited | No | Extractable, factual, fresh pages |
| 3. Mentioned | No | Entity recognition; the web talking about you |
| 4. Recommended | No | Aggregate third-party consensus, largely independent of your own content |

Source pool (one web search for the exact query, 2026-11-07; not a ChatGPT answer): only third-party roundups and affiliate lists (NerdWallet, business.org, Zapier, Fueler, Techjockey, Aspire). The same five apps recur: Wave, Zoho Books, FreshBooks, QuickBooks, Xero. I did not run ChatGPT, so I'm not reporting what ChatGPT says; run the query list yourself.

Extractability check on site/index.html: clear definition in the first paragraph, partial (the H1 is a slogan); self-contained answer blocks, fail; statistics with sources, fail; comparison table for "vs" queries, fail; FAQ, partial (good answers hidden in collapsed <details>, none answers "Is Ledgerly good for freelancers?"); schema markup, fail; author or founder, fail; freshness date, fail; query-shaped headings, fail.

Top fixes, by impact against effort
1. Launch, then get indexed in Bing and Google. robots.txt with a wildcard allow plus explicit allows for OAI-SearchBot, PerplexityBot, Claude-SearchBot and Bingbot; decide training crawlers (GPTBot, ClaudeBot) separately.
2. Seed third-party consensus: G2 and Capterra listings with the first 20–30 real reviews; pitch the roundups that already rank for the query with a specific angle ("$12/month, no per-transaction fees, automatic invoice chasing"). Test: if a model ignored your own domain, would the web still put you on the list? Today, no.
3. Rewrite the hero into an extractable definition (below).
4. Add /vs/freshbooks, then QuickBooks and Wave, in the "fair source" pattern. Do not publish a self-ranked "best bookkeeping apps" listicle: in the skill's data 69% of such citations recommended competitors.
5. Publish /pricing.md and /llms.txt; fix the Studio button ("Talk to us" on a plan with a public price reads as a sales wall to an agent).
6. JSON-LD: Organization, SoftwareApplication with Offer per plan, FAQPage.
7. Buyer-intent FAQs rendered open in the HTML. 8. Named founder, "Last updated", one dated sourced number. 9. Measure monthly: 8 queries, 3–5 runs per engine, log rung and framing.

Hero answer block (57 words, every fact from the existing page):
> Ledgerly is a bookkeeping app for freelancers and two-person studios. It connects to your bank through Plaid or TrueLayer (US, UK, EU), auto-categorises each transaction by category and client, chases unpaid invoices on day 3, 7 and 14, and exports tax-ready P&L, VAT and quarterly estimates. Free plan available; Pro is $12/month with no per-transaction fees. […]

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.

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.