taketomarket 2.2.0 → 2.3.0
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/.claude-plugin/marketplace.json +4 -4
- package/.claude-plugin/plugin.json +2 -2
- package/README.md +34 -11
- package/bin/lib/campaign.cjs +12 -8
- package/bin/lib/codebase-scan.cjs +86 -0
- package/bin/lib/config.cjs +129 -0
- package/bin/lib/deploy.cjs +36 -0
- package/bin/lib/deviation.cjs +1 -1
- package/bin/lib/drift-log.cjs +4 -4
- package/bin/lib/health.cjs +32 -31
- package/bin/lib/install-detect.cjs +62 -0
- package/bin/lib/legacy-folder.cjs +100 -0
- package/bin/lib/playwright-check.cjs +26 -0
- package/bin/lib/site-location.cjs +22 -0
- package/bin/lib/state.cjs +3 -3
- package/bin/lib/svg-render.cjs +42 -0
- package/bin/ttm-tools.cjs +136 -4
- package/gates/base-gates.md +8 -8
- package/gates/gate-evaluation.md +8 -8
- package/install.js +37 -3
- package/package.json +10 -6
- package/playbooks/aeo.md +218 -114
- package/playbooks/affiliate.md +225 -160
- package/playbooks/email.md +236 -174
- package/playbooks/events.md +303 -213
- package/playbooks/landing-pages.md +305 -0
- package/playbooks/linkedin.md +264 -142
- package/playbooks/manifesto.md +322 -0
- package/playbooks/paid-ads.md +240 -189
- package/playbooks/positioning.md +340 -0
- package/playbooks/pr-media.md +308 -168
- package/playbooks/pseo.md +426 -0
- package/playbooks/seo.md +251 -158
- package/playbooks/social.md +253 -182
- package/playbooks/youtube.md +286 -181
- package/references/brand-color-theory.md +48 -0
- package/references/codex-image-gen-research.md +58 -0
- package/references/context-loading.md +6 -6
- package/references/humanizer-patterns.md +433 -0
- package/references/inline-education-blurbs.md +461 -0
- package/references/landing-page-anatomy.md +64 -0
- package/references/linkedin-post-patterns.md +174 -0
- package/references/logo-design-principles.md +55 -0
- package/references/meta-gate-evaluation.md +3 -3
- package/references/obra-superpowers-conventions.md +170 -0
- package/references/playbook-leaders.md +472 -0
- package/references/playwright-mcp-setup.md +164 -0
- package/references/positioning-check-report.md +2 -2
- package/references/pseo-page-anatomy.md +56 -0
- package/references/pseo-templates/alternative-anatomy.md +31 -0
- package/references/pseo-templates/alternative-content-playbook.md +32 -0
- package/references/pseo-templates/blog-anatomy.md +28 -0
- package/references/pseo-templates/blog-content-playbook.md +36 -0
- package/references/pseo-templates/comparison-anatomy.md +29 -0
- package/references/pseo-templates/comparison-content-playbook.md +35 -0
- package/references/pseo-templates/use-case-anatomy.md +28 -0
- package/references/pseo-templates/use-case-content-playbook.md +30 -0
- package/skills/ttm-101/SKILL.md +25 -0
- package/skills/ttm-aeo-check/SKILL.md +17 -12
- package/skills/ttm-affiliate-kit/SKILL.md +5 -0
- package/skills/ttm-archive/SKILL.md +5 -0
- package/skills/ttm-brand-refresh/SKILL.md +5 -0
- package/skills/ttm-brief/SKILL.md +5 -0
- package/skills/ttm-competitor-scan/SKILL.md +5 -0
- package/skills/ttm-deploy/SKILL.md +22 -0
- package/skills/ttm-discover/SKILL.md +17 -0
- package/skills/ttm-email-check/SKILL.md +17 -0
- package/skills/ttm-email-preflight/SKILL.md +17 -11
- package/skills/ttm-fix/SKILL.md +5 -0
- package/skills/ttm-health/SKILL.md +6 -1
- package/skills/ttm-humanize/SKILL.md +33 -0
- package/skills/ttm-icp-refresh/SKILL.md +5 -0
- package/skills/ttm-improve-skill/SKILL.md +18 -0
- package/skills/ttm-init/SKILL.md +10 -3
- package/skills/ttm-keyword-map/SKILL.md +17 -11
- package/skills/ttm-landing/SKILL.md +19 -0
- package/skills/ttm-learn/SKILL.md +5 -0
- package/skills/ttm-linkedin-post/SKILL.md +26 -0
- package/skills/ttm-measure/SKILL.md +5 -0
- package/skills/ttm-new-campaign/SKILL.md +5 -0
- package/skills/ttm-next/SKILL.md +5 -0
- package/skills/ttm-playwright-setup/SKILL.md +18 -0
- package/skills/ttm-positioning-check/SKILL.md +5 -0
- package/skills/ttm-positioning-shift/SKILL.md +5 -0
- package/skills/ttm-produce/SKILL.md +5 -0
- package/skills/ttm-pseo/SKILL.md +26 -0
- package/skills/ttm-repurpose/SKILL.md +5 -0
- package/skills/ttm-request-skill/SKILL.md +18 -0
- package/skills/ttm-research/SKILL.md +18 -6
- package/skills/ttm-resume/SKILL.md +5 -0
- package/skills/ttm-review/SKILL.md +5 -0
- package/skills/ttm-seo/SKILL.md +64 -0
- package/skills/ttm-seo-audit/SKILL.md +17 -12
- package/skills/ttm-ship/SKILL.md +5 -0
- package/skills/ttm-state/SKILL.md +5 -0
- package/skills/ttm-update/SKILL.md +152 -4
- package/skills/ttm-verify/SKILL.md +5 -0
- package/templates/agents-md.md +14 -4
- package/templates/campaign-research.md +6 -6
- package/templates/campaign-state.md +1 -1
- package/templates/claude-md.md +14 -4
- package/templates/linkedin-base-template.md +48 -0
- package/templates/next-step-footer.md +13 -0
- package/templates/production-manifest.json +4 -4
- package/templates/pseo/alternative-cms-schema.json +65 -0
- package/templates/pseo/blog-cms-schema.json +55 -0
- package/templates/pseo/comparison-cms-schema.json +56 -0
- package/templates/pseo/use-case-cms-schema.json +62 -0
- package/templates/reference-files/brand.md +51 -0
- package/templates/reference-files/product-dna.md +73 -0
- package/templates/site-scaffold/app/globals.css +2 -0
- package/templates/site-scaffold/app/layout.tsx +17 -0
- package/templates/site-scaffold/app/page.tsx +33 -0
- package/templates/site-scaffold/app/robots.ts +8 -0
- package/templates/site-scaffold/app/sitemap.ts +10 -0
- package/templates/site-scaffold/app/tokens.css +21 -0
- package/templates/site-scaffold/components/Comparison.tsx +14 -0
- package/templates/site-scaffold/components/Faq.tsx +14 -0
- package/templates/site-scaffold/components/Features.tsx +14 -0
- package/templates/site-scaffold/components/FinalCta.tsx +17 -0
- package/templates/site-scaffold/components/Footer.tsx +12 -0
- package/templates/site-scaffold/components/Hero.tsx +22 -0
- package/templates/site-scaffold/components/HowItWorks.tsx +14 -0
- package/templates/site-scaffold/components/PricingTeaser.tsx +14 -0
- package/templates/site-scaffold/components/Problem.tsx +14 -0
- package/templates/site-scaffold/components/SocialProof.tsx +14 -0
- package/templates/site-scaffold/components/Solution.tsx +14 -0
- package/templates/site-scaffold/components/Testimonials.tsx +14 -0
- package/templates/site-scaffold/components/UseCases.tsx +14 -0
- package/templates/site-scaffold/content/.gitkeep +0 -0
- package/templates/site-scaffold/lib/.gitkeep +0 -0
- package/templates/site-scaffold/next.config.mjs +10 -0
- package/templates/site-scaffold/package.json +25 -0
- package/templates/site-scaffold/postcss.config.mjs +3 -0
- package/templates/site-scaffold/public/llms.txt +9 -0
- package/templates/site-scaffold/tsconfig.json +21 -0
- package/templates/verification-report.md +1 -1
- package/workflows/channel/linkedin-post.md +178 -0
- package/workflows/discipline/affiliate-kit.md +65 -6
- package/workflows/discipline/{email-preflight.md → email-check.md} +39 -4
- package/workflows/discipline/repurpose.md +82 -31
- package/workflows/discipline/{aeo-check.md → seo/aeo.md} +13 -6
- package/workflows/discipline/{seo-audit.md → seo/audit.md} +13 -6
- package/workflows/discipline/{keyword-map.md → seo/keyword-map.md} +13 -6
- package/workflows/education/ttm-101.md +114 -0
- package/workflows/lifecycle/brief-positioning-check.md +1 -1
- package/workflows/lifecycle/brief.md +64 -28
- package/workflows/lifecycle/{research.md → discover.md} +61 -19
- package/workflows/lifecycle/fix.md +72 -37
- package/workflows/lifecycle/humanize.md +280 -0
- package/workflows/lifecycle/learn.md +72 -35
- package/workflows/lifecycle/measure.md +54 -18
- package/workflows/lifecycle/produce.md +88 -37
- package/workflows/lifecycle/review.md +71 -25
- package/workflows/lifecycle/ship.md +62 -18
- package/workflows/lifecycle/verify.md +72 -26
- package/workflows/reference-mgmt/brand-refresh.md +50 -13
- package/workflows/reference-mgmt/competitor-scan.md +51 -15
- package/workflows/reference-mgmt/icp-refresh.md +48 -12
- package/workflows/reference-mgmt/positioning-check.md +55 -20
- package/workflows/reference-mgmt/positioning-shift.md +53 -17
- package/workflows/setup/init-brand-colors.md +75 -0
- package/workflows/setup/init-logo.md +113 -0
- package/workflows/setup/init-product-dna.md +83 -0
- package/workflows/setup/init-questions.md +166 -30
- package/workflows/setup/init-validation.md +22 -0
- package/workflows/setup/init.md +144 -39
- package/workflows/setup/new-campaign.md +48 -12
- package/workflows/site/deploy.md +98 -0
- package/workflows/site/landing.md +156 -0
- package/workflows/site/pseo.md +96 -0
- package/workflows/site/quality-gates.md +88 -0
- package/workflows/utility/archive.md +45 -9
- package/workflows/utility/health.md +77 -3
- package/workflows/utility/improve-skill.md +233 -0
- package/workflows/utility/next.md +38 -2
- package/workflows/utility/playwright-setup.md +128 -0
- package/workflows/utility/request-skill.md +218 -0
- package/workflows/utility/resume.md +40 -3
- package/workflows/utility/state.md +42 -7
package/playbooks/pr-media.md
CHANGED
|
@@ -1,160 +1,223 @@
|
|
|
1
1
|
---
|
|
2
2
|
discipline: pr-media
|
|
3
|
-
asset_types: [press-release,
|
|
4
|
-
version: "
|
|
3
|
+
asset_types: [press-release, journalist-pitch, podcast-pitch]
|
|
4
|
+
version: "2.0"
|
|
5
5
|
---
|
|
6
6
|
|
|
7
|
-
# PR/Media
|
|
7
|
+
# PR/Media Playbook
|
|
8
8
|
|
|
9
9
|
This playbook extends the base playbook contract (`base.md`) with PR/media-specific production guidance, discipline gates, and format rules. It is loaded by ttm-producer during content generation and parsed by ttm-verify for gate evaluation.
|
|
10
10
|
|
|
11
|
+
The framework underneath this playbook is **Publication-Specific Founder PR** — the operating model Emilie Gerber (Six Eastern; clients include Perplexity, Ramp, Webflow, ClickUp, Nubank) teaches in her founder-PR masterclasses. Every rule in this playbook collapses to one premise: a reporter does not work for you, they work for their readers. The pitch's only job is to convince one specific reporter that one specific story will land with their specific audience. Anything else is noise.
|
|
12
|
+
|
|
11
13
|
---
|
|
12
14
|
|
|
13
15
|
## Production Guidance
|
|
14
16
|
|
|
15
|
-
###
|
|
17
|
+
### Pitch a story, not a product
|
|
18
|
+
|
|
19
|
+
The first reframe every engineer-founder has to make: reporters are not your distribution channel. They are not "the press." They are individuals with bylines who have to publish something this week that their editor agrees is a story. If your pitch is "we built a thing and the thing has features," you've handed them a product brochure and asked them to do the work of finding the story inside it. They won't. They'll delete the email.
|
|
20
|
+
|
|
21
|
+
A story has three components a reporter can immediately recognize:
|
|
22
|
+
|
|
23
|
+
1. **A news hook.** Something happened: funding closed, a customer signed, a hire was made, a milestone crossed, a product shipped, a regulator ruled. Without a hook, there is no story — just a company that exists. "We've been around for two years and we're doing well" is not a hook. "We hit $1M ARR in 11 months selling to municipal water districts" is.
|
|
24
|
+
2. **A protagonist.** Reporters write about people more reliably than about software. The founder, the customer who used the product to do something specific, the engineer who left Google to build this — name the person and what they did.
|
|
25
|
+
3. **A reason this matters now.** Why this week? What in the world has changed that makes this newsworthy on a Tuesday in May? Funding rounds, regulatory shifts, layoffs at incumbents, public data drops — these are the pegs your story hangs on.
|
|
26
|
+
|
|
27
|
+
If you cannot state the news hook, the protagonist, and the reason-now in one sentence each, do not pitch. Build the story first.
|
|
28
|
+
|
|
29
|
+
### Match the publication
|
|
30
|
+
|
|
31
|
+
The single biggest mistake founders make is treating "the press" as a monolithic blob. It is not. Every publication has a beat, a reader profile, and a pace. A pitch perfectly tuned for TechCrunch will be silently rejected by The Wall Street Journal — and vice versa. The publication-fit map below is non-negotiable: pitch the publication that wants this exact story.
|
|
32
|
+
|
|
33
|
+
| Publication | What they want | What they reject |
|
|
34
|
+
|---|---|---|
|
|
35
|
+
| TechCrunch | Funding rounds, product launches, acquisitions in tech | Pre-launch teasers, no-funding "founder profiles" |
|
|
36
|
+
| Axios Pro Rata / verticals | Fintech, healthcare, M&A, deals with named numbers | Generic SaaS announcements without dollar figures |
|
|
37
|
+
| Business Insider | Founder stories with metrics, pitch deck breakdowns, salary/comp data | Pure product news |
|
|
38
|
+
| WSJ / CNBC / Bloomberg | Substantial business numbers, regulated industries, public-market implications | Sub-$10M ARR companies without an unusual angle |
|
|
39
|
+
| The Information | Insider tech industry reporting, exec moves, strategy leaks | Press-release-shaped news |
|
|
40
|
+
| VentureBeat | AI, machine learning, enterprise infra | Consumer apps without an AI angle |
|
|
41
|
+
| Forbes contributor network | Founder narrative, lessons learned, advice posts | Hard breaking news (handled by staff) |
|
|
42
|
+
| Industry trade press | Vertical-specific applications, customer case studies | Horizontal-platform announcements |
|
|
43
|
+
| Substack newsletters (Lenny's, Stratechery, Platformer, etc.) | Deep operator analysis, contrarian frameworks, behind-the-scenes detail | Press-release language |
|
|
44
|
+
| Podcast hosts | Personal story, specific operator lessons, conversational chemistry | Pre-recorded marketing pitches |
|
|
45
|
+
|
|
46
|
+
Before drafting any pitch, name the publication and the specific section. "TechCrunch" is not enough; "TechCrunch's enterprise vertical, Ron Miller" is the right granularity.
|
|
47
|
+
|
|
48
|
+
### Research the reporter's last five stories
|
|
49
|
+
|
|
50
|
+
Earn the right to pitch. Before you email a reporter, open their author page and read the last five things they published. Note the date. Note what they cover, what they don't, what they're skeptical of, what they're excited by. Bookmark at least one of those five pieces so you can reference it in the first sentence of your pitch.
|
|
51
|
+
|
|
52
|
+
This is not optional flattery. It serves three functions:
|
|
53
|
+
|
|
54
|
+
1. **Filter:** If five recent articles tell you this reporter doesn't cover your space, do not pitch them. You just saved a relationship.
|
|
55
|
+
2. **Hook:** Referencing a specific piece in your first sentence is the strongest signal that you respect the reporter's work. It also tells them the email is not a blast.
|
|
56
|
+
3. **Angle:** Their recent coverage tells you what angle to use. If their last story was skeptical of AI hype, do not pitch yours as "the AI-powered platform for X." Lead with metrics and operator detail.
|
|
57
|
+
|
|
58
|
+
If the reporter has not published anything in the last 90 days, they may have left the outlet. Check their LinkedIn or X bio before pitching.
|
|
59
|
+
|
|
60
|
+
### The three-sentence rule
|
|
61
|
+
|
|
62
|
+
If your pitch is more than three sentences, it's too long. Brevity is the entire pitch craft. The three sentences are:
|
|
16
63
|
|
|
17
|
-
|
|
64
|
+
1. **Sentence one: connection.** Reference the reporter's recent work specifically. ("Your piece last Thursday on Klarna's IPO filing was the only one I saw that flagged the consumer-credit exposure detail.")
|
|
65
|
+
2. **Sentence two: news hook.** State what happened, when, and why it's a story. ("We closed an $11M Series A this morning to build the first underwriting engine specifically for buy-now-pay-later defaults in the under-30 segment.")
|
|
66
|
+
3. **Sentence three: offer.** Make one clear offer with a clear next step. ("Happy to send the round details under embargo until Tuesday 9am ET, or hop on a 15-minute call this week if useful.")
|
|
18
67
|
|
|
19
|
-
-
|
|
20
|
-
- **Tiered organization:** Tier 1 (national/major trade), Tier 2 (regional/niche trade), Tier 3 (blogs/newsletters/podcasts). Allocate effort proportionally -- Tier 1 gets the most customization.
|
|
21
|
-
- **Beat matching:** Only pitch journalists who cover your space. A fintech pitch sent to a healthcare reporter wastes both parties' time and damages future relationships.
|
|
22
|
-
- **Recency check:** Verify each contact is still at the listed outlet and still covering the same beat. Journalist turnover is high -- stale lists produce bounced emails and irrelevant pitches.
|
|
68
|
+
That's the whole pitch. No bullet points. No attachments. No "About [Company]" paragraph. No second offer. No follow-up CTA at the bottom. If the reporter wants the deck, the financial model, the customer reference, or the headshot, they will ask. If they don't ask, none of those documents would have changed their decision.
|
|
23
69
|
|
|
24
|
-
###
|
|
70
|
+
### Founder as source, not spokesperson
|
|
25
71
|
|
|
26
|
-
|
|
72
|
+
The pitch goes out from the founder's email address, signed by the founder, in the founder's voice. Not from the PR person. Not from an agency. Not from a generic info@ inbox.
|
|
27
73
|
|
|
28
|
-
|
|
29
|
-
- **Angle-per-journalist:** The same announcement should be pitched differently to a product reviewer (focus on features/UX), an industry analyst (focus on market impact), and a business reporter (focus on funding/growth).
|
|
30
|
-
- **Subject line discipline:** 6-10 words, specific and newsworthy. Avoid clickbait, ALL CAPS, or exclamation marks. The subject line is the pitch -- if it does not convey the news, the email will not be opened.
|
|
74
|
+
Reporters cover companies but they trust people. A founder's name in the From field tells the reporter: this is the real source, this is who I'll quote, this is who I can fact-check with. A PR person in the From field tells the reporter: this is a managed message, the founder isn't actually available, the quote will be sanitized.
|
|
31
75
|
|
|
32
|
-
|
|
76
|
+
This applies through every stage:
|
|
33
77
|
|
|
34
|
-
|
|
78
|
+
- **First contact:** Founder's email, founder's words.
|
|
79
|
+
- **Reply:** Founder responds personally within 24 hours, even if just to schedule.
|
|
80
|
+
- **Interview:** Founder takes the call. No "PR present on the line." No talking points handed across the table. The reporter wants the unvarnished operator answering operator questions.
|
|
81
|
+
- **Quote:** The quote in the published piece reads like the founder actually said it. If it sounds like it was written by a press release writer, the reporter will either rewrite it or pull a different quote — and the company has lost share-of-voice in its own coverage.
|
|
35
82
|
|
|
36
|
-
|
|
37
|
-
- **NDA when needed:** For sensitive announcements (M&A, funding, partnerships), require a signed NDA before sharing embargoed information.
|
|
38
|
-
- **Break protocol:** Document what happens if an embargo is broken. Typically: immediate release to all other embargoed journalists, note the breaking outlet for future exclusion.
|
|
39
|
-
- **Selective use:** Reserve embargoes for genuinely significant news. Routine product updates do not warrant embargo complexity.
|
|
83
|
+
The PR function — research, list-building, embargo logistics, fact-sheet packaging — runs in the background. The founder is the source.
|
|
40
84
|
|
|
41
|
-
###
|
|
85
|
+
### Exclusives over blasts
|
|
42
86
|
|
|
43
|
-
|
|
87
|
+
Blasting the same press release to 200 reporters is the single most reliably bad PR tactic for founders. Response rates fall below 1%, reporters recognize the blast pattern instantly, and the few who do cover it write a thinner story because they know everyone else has it.
|
|
44
88
|
|
|
45
|
-
|
|
46
|
-
2. **Dateline:** City, State/Country -- Date
|
|
47
|
-
3. **Lead paragraph:** Who, what, when, where, why in 2-3 sentences
|
|
48
|
-
4. **Supporting details:** Context, background, market data (2-3 paragraphs)
|
|
49
|
-
5. **Executive quote:** One quote from a named executive providing perspective
|
|
50
|
-
6. **Product/company details:** Specifics about the product or initiative
|
|
51
|
-
7. **Boilerplate:** Standard company description paragraph (consistent across all releases)
|
|
52
|
-
8. **Media contact:** Name, email, phone number for press inquiries
|
|
89
|
+
The default move is the opposite: pick one reporter, offer the story exclusively, and trade exclusivity for a deeper, more prominent piece.
|
|
53
90
|
|
|
54
|
-
|
|
91
|
+
The exclusive bargain is simple. The reporter gets the story 24-72 hours before anyone else and a guarantee no other outlet will have it on launch day. In exchange, the reporter commits to publish on launch day and typically writes a fuller piece — interview, multiple sources, real reporting — instead of a 200-word post that everyone else has.
|
|
55
92
|
|
|
56
|
-
|
|
93
|
+
Choose the exclusive partner using three criteria:
|
|
57
94
|
|
|
58
|
-
|
|
59
|
-
|
|
60
|
-
|
|
95
|
+
1. **Reader fit:** Does the publication's audience overlap with your ICP? Tier-1 reach is meaningless if their readers don't buy what you sell.
|
|
96
|
+
2. **Reporter fit:** Has this specific reporter covered companies like yours, sympathetically and accurately? Pull their last five pieces and check.
|
|
97
|
+
3. **Cadence:** Will they actually publish on launch day? Some reporters sit on exclusives. Confirm the publish slot in writing before agreeing.
|
|
61
98
|
|
|
62
|
-
|
|
99
|
+
Reserve the broadcast pitch (sent to your tier-2 list 30 minutes after the exclusive goes live) for after the anchor coverage exists. The exclusive piece becomes the proof point the broadcast pitch references.
|
|
63
100
|
|
|
64
|
-
|
|
101
|
+
### News pegs and the embargo calendar
|
|
65
102
|
|
|
66
|
-
|
|
67
|
-
|
|
68
|
-
- **
|
|
103
|
+
Real PR planning is calendar-driven. You don't pitch when you feel ready; you pitch when the news peg lines up. Maintain a rolling 8-week news peg calendar:
|
|
104
|
+
|
|
105
|
+
- **Internal pegs:** Funding close (target announcement date), customer milestones (logo go-live, ARR threshold), product launches (GA date, not beta), hires (start date), and report drops (data you've collected and packaged).
|
|
106
|
+
- **External pegs:** Industry events your launch can ride alongside, competitor moves you can react to with on-record commentary, regulatory deadlines, earnings season for your buyer's parent companies.
|
|
107
|
+
|
|
108
|
+
Embargoes are the lever that aligns your internal pegs with publication production schedules. A 48-hour embargo lets the reporter draft, fact-check, and pre-clear the piece with their editor before publish. A 0-hour "for immediate release" leaves them no production time and typically yields no coverage. Set the embargo clearly: date, time, timezone, and what the embargo applies to. Get written acknowledgment from each reporter who receives embargoed material.
|
|
109
|
+
|
|
110
|
+
### Diversify beyond legacy press
|
|
111
|
+
|
|
112
|
+
A LinkedIn post from a respected investor can outperform a TechCrunch hit for an enterprise SaaS company. A 90-minute podcast appearance on a niche operator show can produce more inbound demos than any major-outlet placement. Treat the press universe as broader than legacy media.
|
|
113
|
+
|
|
114
|
+
The four surfaces every founder-PR plan should map:
|
|
115
|
+
|
|
116
|
+
1. **Legacy press:** TechCrunch, WSJ, Axios, Bloomberg, trade publications. High reach, low conversion per impression, high prestige signal.
|
|
117
|
+
2. **Newsletters and Substacks:** Lenny's, Stratechery, Platformer, The Diff, vertical operator newsletters. Smaller audiences, much higher trust, often a single placement drives more conversions than a Tier-1 hit.
|
|
118
|
+
3. **Podcasts:** Founder podcasts (Acquired, This Week in Startups, 20VC), operator podcasts in your buyer's vertical. Long-form lets the founder narrative breathe.
|
|
119
|
+
4. **Owned distribution amplified by trusted voices:** A founder LinkedIn post, an investor LinkedIn post quoting the founder, a customer LinkedIn post — these are PR. Track them, plan them, brief participants the same way you'd brief a reporter.
|
|
69
120
|
|
|
70
121
|
---
|
|
71
122
|
|
|
72
123
|
## Discipline Gates
|
|
73
124
|
|
|
74
|
-
### DISC-PR-MEDIA-01:
|
|
125
|
+
### DISC-PR-MEDIA-01: Publication Fit -- Tier 1
|
|
75
126
|
|
|
76
|
-
**Checks:**
|
|
77
|
-
**Against:**
|
|
127
|
+
**Checks:** Pitch is targeted to a specific publication whose audience and beat actually match the story
|
|
128
|
+
**Against:** Pitch document, publication identification, and reporter beat history
|
|
78
129
|
|
|
79
130
|
#### Evaluation Criteria
|
|
80
131
|
|
|
81
|
-
1. **
|
|
82
|
-
- PASS:
|
|
83
|
-
- WARN:
|
|
84
|
-
- FAIL:
|
|
132
|
+
1. **Specific publication and reporter named**
|
|
133
|
+
- PASS: Pitch identifies a specific publication, a specific section/vertical within that publication, and a specific reporter (first and last name) whose recent coverage demonstrates beat alignment
|
|
134
|
+
- WARN: Specific reporter named, but their last five articles do not clearly cover this story's vertical or angle
|
|
135
|
+
- FAIL: Pitch addressed to a generic editor (editor@, news@, tips@) or a list of reporters with no per-reporter rationale
|
|
85
136
|
|
|
86
|
-
2. **
|
|
87
|
-
- PASS:
|
|
88
|
-
- WARN:
|
|
89
|
-
- FAIL:
|
|
137
|
+
2. **Reporter's recent work referenced**
|
|
138
|
+
- PASS: Pitch's first sentence cites a specific article the reporter published in the last 90 days and connects it to the pitched story
|
|
139
|
+
- WARN: Pitch references the reporter's beat broadly ("Since you cover fintech...") without citing a specific recent piece
|
|
140
|
+
- FAIL: No reference to the reporter's work, or the cited piece is older than 6 months / written by a different author
|
|
90
141
|
|
|
91
|
-
### DISC-PR-MEDIA-02:
|
|
142
|
+
### DISC-PR-MEDIA-02: Story Angle Specificity -- Tier 1
|
|
92
143
|
|
|
93
|
-
**Checks:**
|
|
94
|
-
**Against:**
|
|
144
|
+
**Checks:** The pitch leads with a real story angle — news hook, protagonist, and reason-now — not a product description
|
|
145
|
+
**Against:** Pitch content compared to news-hook definition
|
|
95
146
|
|
|
96
147
|
#### Evaluation Criteria
|
|
97
148
|
|
|
98
|
-
1. **
|
|
99
|
-
- PASS: Pitch
|
|
100
|
-
- WARN:
|
|
101
|
-
- FAIL:
|
|
149
|
+
1. **Named news hook present**
|
|
150
|
+
- PASS: Pitch states an explicit, datable news hook (funding round with amount and date, named customer go-live, product GA date, hire with start date, data-report release, milestone with number)
|
|
151
|
+
- WARN: News hook present but vague on specifics ("we recently launched" without a date, "we're growing" without a number)
|
|
152
|
+
- FAIL: No news hook — pitch describes the company, the product, or the market without naming what specifically happened this week
|
|
102
153
|
|
|
103
|
-
2. **
|
|
104
|
-
- PASS:
|
|
105
|
-
- WARN:
|
|
106
|
-
- FAIL:
|
|
154
|
+
2. **Story specificity over category claim**
|
|
155
|
+
- PASS: Pitch describes the specific story (named protagonist, specific number, specific moment) without relying on category-novelty language
|
|
156
|
+
- WARN: Pitch makes one generic claim ("first AI-powered ___" or "the leading platform for ___") but otherwise grounds the story in specifics
|
|
157
|
+
- FAIL: Pitch is built around category claims ("disrupting X," "first of its kind," "next-generation") with no specific protagonist, number, or moment
|
|
107
158
|
|
|
108
|
-
### DISC-PR-MEDIA-03:
|
|
159
|
+
### DISC-PR-MEDIA-03: Three-Sentence Discipline -- Tier 1
|
|
109
160
|
|
|
110
|
-
**Checks:**
|
|
111
|
-
**Against:** Pitch
|
|
161
|
+
**Checks:** Pitch email body adheres to the brevity and format rules: pitch length, no attachments, founder-as-sender
|
|
162
|
+
**Against:** Pitch email body and metadata
|
|
112
163
|
|
|
113
164
|
#### Evaluation Criteria
|
|
114
165
|
|
|
115
|
-
1. **
|
|
116
|
-
- PASS:
|
|
117
|
-
- WARN:
|
|
118
|
-
- FAIL:
|
|
166
|
+
1. **Pitch length**
|
|
167
|
+
- PASS: Pitch email body is 3 sentences or fewer (excluding greeting and signature), under 100 words total
|
|
168
|
+
- WARN: Pitch is 4-5 sentences or 100-150 words — still readable but breaks the discipline
|
|
169
|
+
- FAIL: Pitch exceeds 5 sentences or 150 words, or includes bullet lists / multi-paragraph "About [Company]" sections inline
|
|
119
170
|
|
|
120
|
-
2. **
|
|
121
|
-
- PASS:
|
|
122
|
-
- WARN:
|
|
123
|
-
- FAIL:
|
|
171
|
+
2. **Founder-as-sender and no first-contact attachments**
|
|
172
|
+
- PASS: Pitch is sent from the founder's named email address, signed by the founder personally, with no attachments on first contact (no decks, no PDFs, no press releases attached)
|
|
173
|
+
- WARN: Sent from founder address but cc's an agency / PR person, OR sent with an inline media-kit link (acceptable but suboptimal)
|
|
174
|
+
- FAIL: Sent from a PR firm address, a generic info@ inbox, or with one or more attachments on first contact
|
|
124
175
|
|
|
125
|
-
### DISC-PR-MEDIA-04:
|
|
176
|
+
### DISC-PR-MEDIA-04: Founder Quote Substance -- Tier 1
|
|
126
177
|
|
|
127
|
-
**Checks:**
|
|
128
|
-
**Against:**
|
|
178
|
+
**Checks:** Any founder quote in the pitch or press release sounds like a real human said it and contains operator-level specificity
|
|
179
|
+
**Against:** Quote text in the asset
|
|
129
180
|
|
|
130
181
|
#### Evaluation Criteria
|
|
131
182
|
|
|
132
|
-
1. **
|
|
133
|
-
- PASS:
|
|
134
|
-
- WARN:
|
|
135
|
-
- FAIL:
|
|
183
|
+
1. **Non-platitudinous content**
|
|
184
|
+
- PASS: Quote contains at least one specific number, customer detail, contrarian view, or operator observation that a press-release ghostwriter would not produce
|
|
185
|
+
- WARN: Quote contains one specific detail but is wrapped in generic excitement language ("We're thrilled to...")
|
|
186
|
+
- FAIL: Quote is composed entirely of platitudes — "thrilled to announce," "transforming the industry," "empowering customers," "next chapter of growth" — with no specific content
|
|
136
187
|
|
|
137
|
-
2. **
|
|
138
|
-
- PASS:
|
|
139
|
-
- WARN:
|
|
140
|
-
- FAIL:
|
|
188
|
+
2. **Voice authenticity**
|
|
189
|
+
- PASS: Quote reads in a recognizably individual voice; if removed from the release, an informed reader could identify it as written by an operator, not a PR writer
|
|
190
|
+
- WARN: Quote is competent corporate-speak but indistinguishable from any other CEO quote
|
|
191
|
+
- FAIL: Quote uses press-release boilerplate that a reporter would either rewrite or replace with a different source
|
|
141
192
|
|
|
142
|
-
### DISC-PR-MEDIA-05:
|
|
193
|
+
### DISC-PR-MEDIA-05: Exclusive vs Blast Strategy -- Tier 2
|
|
143
194
|
|
|
144
|
-
**Checks:**
|
|
145
|
-
**Against:**
|
|
195
|
+
**Checks:** Distribution strategy is intentional — exclusive offered when justified, blast reserved for post-anchor amplification
|
|
196
|
+
**Against:** Pitch plan and distribution timeline
|
|
146
197
|
|
|
147
198
|
#### Evaluation Criteria
|
|
148
199
|
|
|
149
|
-
1. **
|
|
150
|
-
- PASS:
|
|
151
|
-
- WARN:
|
|
152
|
-
- FAIL:
|
|
200
|
+
1. **Strategy named**
|
|
201
|
+
- PASS: Distribution plan explicitly states whether the launch is exclusive (one outlet, named, with reason for choice), embargoed (multiple outlets, named, with embargo time and timezone), or broadcast (with anchor coverage already secured)
|
|
202
|
+
- WARN: Strategy implied but not documented; embargo terms missing timezone or break protocol
|
|
203
|
+
- FAIL: Pitch goes simultaneously to 20+ outlets with identical content and no exclusive/embargo framing
|
|
204
|
+
|
|
205
|
+
2. **Anchor-then-amplify ordering**
|
|
206
|
+
- PASS: If broadcast is used, an anchor placement (exclusive or embargoed tier-1) is sequenced first; broadcast pitches reference the anchor coverage
|
|
207
|
+
- WARN: Broadcast and anchor pitches go out simultaneously, reducing the value of the anchor
|
|
208
|
+
- FAIL: Broadcast-only with no anchor, or anchor exclusive promised to multiple outlets simultaneously
|
|
209
|
+
|
|
210
|
+
### DISC-PR-MEDIA-06: Surface Diversification -- Tier 2
|
|
153
211
|
|
|
154
|
-
|
|
155
|
-
|
|
156
|
-
|
|
157
|
-
|
|
212
|
+
**Checks:** PR plan includes non-legacy surfaces (newsletters, podcasts, owned distribution amplified by trusted voices)
|
|
213
|
+
**Against:** Overall PR campaign plan, not individual pitch
|
|
214
|
+
|
|
215
|
+
#### Evaluation Criteria
|
|
216
|
+
|
|
217
|
+
1. **Multi-surface coverage**
|
|
218
|
+
- PASS: Campaign plan names at least one target in each of three surfaces: legacy press, newsletter/Substack, and podcast OR investor/customer LinkedIn amplification
|
|
219
|
+
- WARN: Two of three surfaces covered
|
|
220
|
+
- FAIL: Campaign is legacy-press-only, or treats newsletter and podcast pitches as afterthoughts with no named targets
|
|
158
221
|
|
|
159
222
|
---
|
|
160
223
|
|
|
@@ -162,135 +225,212 @@ Plan measurement before pitching, not after:
|
|
|
162
225
|
|
|
163
226
|
| Base Gate ID | Default Tier | Override Tier | Reason |
|
|
164
227
|
|-------------|-------------|---------------|--------|
|
|
165
|
-
| GATE-02 (Claim Accuracy) | Tier 2 | Tier 1 | Press claims are amplified by journalists and become public record;
|
|
228
|
+
| GATE-02 (Claim Accuracy) | Tier 2 | Tier 1 | Press claims are amplified by journalists and become public record once published; corrections require formal retraction and damage future relationships. Every metric, customer name, and superlative in a PR asset must be verifiable on the spot. |
|
|
229
|
+
| GATE-06 (Positioning Invariant) | Tier 1 | Tier 1 | Default Tier 1 retained but called out: PR is the most public channel; positioning drift in a press quote is the hardest drift to retract, since reporters lift quotes verbatim into permanent indexable coverage. |
|
|
166
230
|
|
|
167
231
|
---
|
|
168
232
|
|
|
169
233
|
## Format Rules
|
|
170
234
|
|
|
171
|
-
###
|
|
235
|
+
### Journalist Pitch Email
|
|
172
236
|
|
|
173
|
-
- **
|
|
174
|
-
- **
|
|
175
|
-
- **
|
|
176
|
-
- **
|
|
177
|
-
- **
|
|
178
|
-
- **
|
|
179
|
-
- **Media contact:** Full name, title, email, phone. At the bottom.
|
|
237
|
+
- **Subject line:** The subject line IS the angle. 6-10 words. State the news, name the metric, or pose the contrarian frame. Examples that work: "Series A close: $11M for BNPL underwriting (under embargo to Tues 9am ET)" / "Following your Klarna piece — defaults data from 47k loans". Examples that fail: "Quick question" / "EXCITING ANNOUNCEMENT" / "[Company] Press Release".
|
|
238
|
+
- **Greeting:** "Hi [First name]," — never "Dear Editor," never "Dear [First] [Last]," never "Hello [Last]."
|
|
239
|
+
- **Body:** Exactly 3 sentences. Connection → news hook → offer. Maximum 100 words.
|
|
240
|
+
- **Attachments on first contact:** Zero. No deck. No press release. No fact sheet. No headshot. Inline media-kit link only if useful.
|
|
241
|
+
- **Signature:** Founder's full name, title, company name, one phone number. No corporate footer, no legal disclaimer, no scheduling-link CTA.
|
|
242
|
+
- **Send from:** Founder's named email address (firstname@company.com or firstname.lastname@company.com). Not info@, not press@, not from an agency domain.
|
|
180
243
|
|
|
181
|
-
###
|
|
244
|
+
### Podcast Pitch Email
|
|
182
245
|
|
|
183
|
-
|
|
184
|
-
Subject: [6-10 words, specific news angle -- no clickbait]
|
|
246
|
+
Same three-sentence discipline, adapted to podcast hosts:
|
|
185
247
|
|
|
186
|
-
|
|
248
|
+
- **Sentence one:** Reference a specific recent episode and what stuck with you. Hosts can spot a templated podcast pitch in two seconds — the antidote is showing you actually listened.
|
|
249
|
+
- **Sentence two:** State the operator angle you'd bring (not the company you'd promote). What specific lesson, story, or contrarian take would the host's audience want to hear from you?
|
|
250
|
+
- **Sentence three:** Offer concrete timing and format. ("I'm free for a 60-minute recording any morning ET in the next three weeks if useful.")
|
|
187
251
|
|
|
188
|
-
[
|
|
252
|
+
Never pitch a podcast as "I'd love to come on and talk about [Company]." Pitch the topic the host's audience wants. The company mention happens in the bio at the end of the episode, not in the pitch.
|
|
189
253
|
|
|
190
|
-
|
|
254
|
+
### Press Release
|
|
191
255
|
|
|
192
|
-
|
|
256
|
+
Used as the supporting document a reporter requests AFTER the pitch lands — not as the pitch itself. Inverted pyramid:
|
|
193
257
|
|
|
194
|
-
|
|
258
|
+
- **Headline:** 8-12 words. Factual. Names the news. Title case. No "thrilled," no "proud," no "leading."
|
|
259
|
+
- **Dateline:** CITY, STATE (Month Day, Year) —
|
|
260
|
+
- **Lead paragraph:** 2-3 sentences. Who, what, when, where, why. The lead must answer "what's the news?" in the first sentence.
|
|
261
|
+
- **Body:** 3-5 paragraphs, 400-600 words excluding boilerplate. Each paragraph adds context, not new news.
|
|
262
|
+
- **Founder quote:** Exactly one. Attributed to the founder by name and title. 2-3 sentences. Must pass DISC-PR-MEDIA-04 — operator specificity, not press-release platitudes.
|
|
263
|
+
- **Customer or investor quote (optional, one only):** Same standard. No more than two quotes total in the entire release.
|
|
264
|
+
- **Boilerplate:** 50-75 words. Consistent across all releases. Updated only when company facts change.
|
|
265
|
+
- **Media contact:** Founder's name and direct email — not a PR firm's general inbox — unless the company is large enough to have a dedicated press lead with named ownership.
|
|
266
|
+
|
|
267
|
+
### News Peg Calendar
|
|
268
|
+
|
|
269
|
+
Maintained alongside the campaign, not inside the pitch:
|
|
270
|
+
|
|
271
|
+
- Rolling 8 weeks forward
|
|
272
|
+
- Each entry: peg date, peg type (funding / customer / hire / launch / data / external event), pitch readiness state (story drafted / list built / exclusive identified / embargo set)
|
|
273
|
+
- Updated weekly; nothing gets pitched without a calendar entry
|
|
274
|
+
|
|
275
|
+
---
|
|
276
|
+
|
|
277
|
+
## Examples
|
|
278
|
+
|
|
279
|
+
### Good: Three-sentence journalist pitch
|
|
280
|
+
|
|
281
|
+
```
|
|
282
|
+
Subject: Following your Klarna piece — $11M Series A for BNPL underwriting (embargo Tue 9am ET)
|
|
283
|
+
|
|
284
|
+
Hi Mary,
|
|
285
|
+
|
|
286
|
+
Your piece last Thursday on Klarna's IPO filing was the only one I saw
|
|
287
|
+
that flagged the consumer-credit exposure detail in footnote 14 — that's
|
|
288
|
+
the exact problem we built our company to solve. We're closing an $11M
|
|
289
|
+
Series A on Tuesday led by [Investor], to scale an underwriting engine
|
|
290
|
+
that's reduced default rates by 38% across 47,000 loans for three
|
|
291
|
+
mid-market BNPL lenders we'd be happy to put you in touch with. Open to
|
|
292
|
+
a 20-minute call this Friday or Monday if useful, otherwise the embargoed
|
|
293
|
+
fact sheet is yours on request.
|
|
195
294
|
|
|
196
295
|
Best,
|
|
197
|
-
[
|
|
198
|
-
|
|
296
|
+
[Founder]
|
|
297
|
+
CEO, [Company]
|
|
199
298
|
[Phone]
|
|
200
299
|
```
|
|
201
300
|
|
|
202
|
-
|
|
301
|
+
**Why it works:** Subject line is the angle and signals the embargo. First sentence references a specific recent article with operator-level detail (footnote 14) — proves the founder actually read it. Second sentence has a real news hook (Series A, $11M, named investor, dated for Tuesday) and a substantive metric (38% default reduction across 47k loans). Third sentence makes one concrete offer with one concrete next step. Founder is the sender. No attachments on first contact. Three sentences, under 100 words in the body.
|
|
203
302
|
|
|
204
|
-
###
|
|
303
|
+
### Good: Podcast pitch
|
|
205
304
|
|
|
206
|
-
|
|
207
|
-
|
|
208
|
-
3. **Product screenshots/visuals:** High-resolution, properly licensed, with captions
|
|
209
|
-
4. **Press release archive:** Links to 3-5 most recent releases
|
|
210
|
-
5. **Brand assets:** Logo files (SVG, PNG), brand color codes, usage guidelines
|
|
211
|
-
6. **Media contact:** Dedicated PR contact with direct email and phone
|
|
305
|
+
```
|
|
306
|
+
Subject: Operator angle for the show — when we killed our $2M ARR product line
|
|
212
307
|
|
|
213
|
-
|
|
308
|
+
Hi Lenny,
|
|
214
309
|
|
|
215
|
-
|
|
216
|
-
|
|
217
|
-
|
|
218
|
-
|
|
219
|
-
|
|
220
|
-
|
|
310
|
+
Your episode with the Linear founder on saying-no-to-customer-asks
|
|
311
|
+
genuinely changed how I run our product roadmap — we used the framework
|
|
312
|
+
to kill a $2M ARR product line three months ago that was eating 40% of
|
|
313
|
+
our eng team for 8% of revenue. I think the operator story of how we
|
|
314
|
+
decided, who we lost, and what happened to NRR afterward would be useful
|
|
315
|
+
for your audience of PM- and founder-listeners. Free for a 90-minute
|
|
316
|
+
recording any morning ET in the next three weeks if it's a fit.
|
|
221
317
|
|
|
222
|
-
|
|
318
|
+
Best,
|
|
319
|
+
[Founder]
|
|
320
|
+
```
|
|
223
321
|
|
|
224
|
-
|
|
322
|
+
**Why it works:** Names a specific recent episode and connects it to a specific operator action ("used the framework to kill a $2M ARR product line three months ago"). Pitches the topic, not the company. Quantifies the operator story (40% of eng, 8% of revenue) so the host can see the substance. Offers concrete timing.
|
|
225
323
|
|
|
226
|
-
###
|
|
324
|
+
### Bad: Spray-and-pray blast
|
|
227
325
|
|
|
228
326
|
```
|
|
229
|
-
Subject:
|
|
327
|
+
Subject: EXCITING NEWS FROM [COMPANY] — Revolutionary AI Platform Launches!!!
|
|
230
328
|
|
|
231
|
-
|
|
329
|
+
Dear Editor,
|
|
330
|
+
|
|
331
|
+
[Company] is thrilled to announce the launch of our next-generation
|
|
332
|
+
AI-powered platform that is revolutionizing the way businesses transform
|
|
333
|
+
their digital journey. As the leading provider of innovative solutions
|
|
334
|
+
in the rapidly growing $400B market, we are uniquely positioned to
|
|
335
|
+
empower customers worldwide.
|
|
232
336
|
|
|
233
|
-
|
|
234
|
-
|
|
235
|
-
|
|
236
|
-
|
|
337
|
+
Our platform features include:
|
|
338
|
+
- AI-powered automation
|
|
339
|
+
- Seamless integration
|
|
340
|
+
- Enterprise-grade security
|
|
341
|
+
- Scalable architecture
|
|
342
|
+
- Real-time analytics
|
|
237
343
|
|
|
238
|
-
|
|
239
|
-
|
|
344
|
+
[continues for 500 more words]
|
|
345
|
+
|
|
346
|
+
Attached: Press release, Pitch deck, Logo pack, Founder headshot, FAQ.
|
|
347
|
+
|
|
348
|
+
Please let me know if you would like to cover this exciting news.
|
|
240
349
|
|
|
241
350
|
Best,
|
|
242
|
-
[
|
|
351
|
+
[PR Agency]
|
|
352
|
+
on behalf of [Company]
|
|
243
353
|
```
|
|
244
354
|
|
|
245
|
-
**Why it
|
|
355
|
+
**Why it fails:**
|
|
356
|
+
- **DISC-PR-MEDIA-01 FAIL:** Addressed to "Dear Editor" — no named reporter, no recent-work reference, no publication-fit logic.
|
|
357
|
+
- **DISC-PR-MEDIA-02 FAIL:** No news hook. The "launch" has no date, no metric, no protagonist. Built entirely on category claims ("revolutionary," "next-generation," "leading").
|
|
358
|
+
- **DISC-PR-MEDIA-03 FAIL:** Sent from PR agency, not founder. Five attachments on first contact. Body exceeds 500 words with bullet lists and "About" paragraphs.
|
|
359
|
+
- **DISC-PR-MEDIA-04 FAIL:** Quote (not shown but implied) would be pure platitude.
|
|
360
|
+
- **DISC-PR-MEDIA-05 FAIL:** Subject line and content indicate blast distribution with no anchor outlet.
|
|
246
361
|
|
|
247
|
-
|
|
362
|
+
This pitch will land in a reporter's deleted folder before they finish reading the subject line.
|
|
248
363
|
|
|
249
|
-
|
|
250
|
-
Subject: EXCITING NEWS FROM [COMPANY]!!!
|
|
364
|
+
### Bad: No-hook founder-profile pitch
|
|
251
365
|
|
|
252
|
-
|
|
366
|
+
```
|
|
367
|
+
Subject: Story idea — founder profile
|
|
253
368
|
|
|
254
|
-
|
|
255
|
-
leading provider of innovative solutions that empower businesses to
|
|
256
|
-
transform their digital journey. Our new features include...
|
|
369
|
+
Hi Sarah,
|
|
257
370
|
|
|
258
|
-
|
|
371
|
+
I'm the founder of [Company] and I think my story would make a great
|
|
372
|
+
piece for your publication. I started the company two years ago because
|
|
373
|
+
I saw a gap in the market, and we've been growing steadily ever since.
|
|
374
|
+
Our customers love us and we're really proud of what we've built. Would
|
|
375
|
+
you be open to a conversation about doing a profile?
|
|
259
376
|
|
|
260
|
-
|
|
377
|
+
Best,
|
|
378
|
+
[Founder]
|
|
261
379
|
```
|
|
262
380
|
|
|
263
|
-
**
|
|
381
|
+
**Why it fails:**
|
|
382
|
+
- **DISC-PR-MEDIA-02 FAIL:** No news hook. "I started the company two years ago" is a fact, not news. "Growing steadily" is not a number. There is nothing here that has to be published this week — or any week.
|
|
383
|
+
- **DISC-PR-MEDIA-01 WARN/FAIL:** No reference to the reporter's specific work. The pitch could be sent to anyone.
|
|
384
|
+
- The fundamental error: pitching a profile before earning one. Founder profiles are written about companies the reporter is already tracking, not companies that ask for profiles.
|
|
264
385
|
|
|
265
386
|
---
|
|
266
387
|
|
|
267
388
|
## Anti-Patterns
|
|
268
389
|
|
|
269
|
-
1. **Spray-and-pray pitching
|
|
390
|
+
1. **Spray-and-pray pitching.** Identical pitch BCC'd or mail-merged to 50+ reporters. Response rates fall below 1%, and reporters who recognize the pattern blacklist the sender for future pitches. The discipline is the opposite: fewer pitches, each one researched and tailored.
|
|
391
|
+
|
|
392
|
+
2. **"Disrupting X" with no metrics.** Category-novelty language ("first AI-powered platform for X," "the next generation of Y," "disrupting the legacy Z industry") without a specific number, customer, or operator detail behind it. Reporters parse these phrases as "we have nothing concrete to share." Replace every category claim with a number.
|
|
270
393
|
|
|
271
|
-
|
|
394
|
+
3. **No news hook.** Pitching a "story" about the company existing, or "growing," or "having an interesting vision." Without a datable event that happened (or will happen), there is no story — only an existence announcement. Wait for the hook.
|
|
272
395
|
|
|
273
|
-
|
|
396
|
+
4. **PR firm as sender.** First contact from agency@firm.com signed by an account manager. Reporters know what this signals: the founder isn't actually available, the message has been laundered, the quote will be sanitized. Send from the founder.
|
|
274
397
|
|
|
275
|
-
|
|
398
|
+
5. **Attachments on first contact.** Decks, press releases, fact sheets, headshots attached to the first email. Modern reporters won't open attachments from unknown senders, and large attachments get filtered by spam systems. Pitch in the email body; send supporting documents only when requested.
|
|
276
399
|
|
|
277
|
-
|
|
400
|
+
6. **Following up more than twice.** A polite follow-up 3-5 business days after the initial pitch is acceptable. A second follow-up 7-10 business days later is the absolute ceiling. Beyond that, you are damaging the relationship for every future pitch. Move on.
|
|
278
401
|
|
|
279
|
-
|
|
402
|
+
7. **Embargo as afterthought.** Sharing material with "Don't share until Tuesday, OK?" in passing. Embargoes require date, time, timezone, scope, and break protocol — all in writing, all acknowledged by each reporter. Casual embargoes get broken.
|
|
280
403
|
|
|
281
|
-
|
|
404
|
+
8. **Burying the founder behind talking points.** Putting the founder on the interview call with a PR person on the line, pre-loading them with talking points, asking the reporter to send questions in advance. Reporters notice. The piece reads thinner. Let the founder speak.
|
|
405
|
+
|
|
406
|
+
9. **Treating legacy press as the only surface.** Spending three weeks chasing a TechCrunch hit while ignoring a Substack with 30,000 operator readers who would all be buyers. Distribution surfaces have shifted; the campaign plan should reflect that.
|
|
407
|
+
|
|
408
|
+
10. **Promising exclusivity to multiple outlets.** Telling Reporter A "you have the exclusive" and Reporter B "we're giving you first look" simultaneously. When (not if) they find out, the entire press relationship is over — and reporters talk.
|
|
282
409
|
|
|
283
410
|
---
|
|
284
411
|
|
|
285
412
|
## Metrics
|
|
286
413
|
|
|
287
|
-
Track these indicators for PR/media
|
|
414
|
+
Track these indicators for PR/media work after shipping. Note: the most important metric is not coverage volume — it's coverage quality and the share-of-voice the founder personally captured.
|
|
415
|
+
|
|
416
|
+
- **Placement rate per pitch:** Number of placements divided by number of pitches sent. Healthy founder-PR sits above 15% when the publication-fit and three-sentence disciplines are followed. Below 5% means the list, hook, or pitch is failing.
|
|
417
|
+
- **Tier-1 placements:** Count of placements in publications whose audience overlaps your ICP (not necessarily the most prestigious — the most relevant). One Lenny's Newsletter mention may outweigh five trade-pub mentions.
|
|
418
|
+
- **Journalist response rate:** Percentage of pitched reporters who responded, even if declining. Response rate is a leading indicator of pitch quality; placement rate is a lagging indicator.
|
|
419
|
+
- **Founder share-of-quote:** Percentage of resulting coverage that quotes the founder by name (vs. quoting an investor, a customer, or pulling boilerplate from the press release). Founder share-of-quote >70% indicates the founder is being treated as the source, not the spokesperson.
|
|
420
|
+
- **Quote pull-through:** Percentage of coverage that retains the founder's exact quote vs. the reporter rewriting it. Low pull-through indicates the quote was too platitudinous and got replaced.
|
|
421
|
+
- **Inbound from coverage:** Demos booked, qualified leads, or partnership inquiries traceable to specific pieces of coverage. Set up UTM tracking and ask new sign-ups how they heard about you for 30 days after each major hit.
|
|
422
|
+
- **Exclusive-anchor lift:** When an exclusive is used, measure the lift in follow-on coverage volume vs. comparable broadcast-only launches. The exclusive bargain only works if the anchor outlet's coverage demonstrably catalyzes the rest.
|
|
423
|
+
- **Surface diversification ratio:** Distribution of placements across legacy press, newsletters/Substacks, podcasts, and trusted-voice LinkedIn amplification. A founder PR program that only produces legacy hits is leaving 60-70% of conversions on the table.
|
|
424
|
+
- **Embargo respect rate:** Percentage of embargoed pitches where every recipient honored the embargo. A single break tells you that journalist or outlet should be excluded from future embargoes.
|
|
425
|
+
|
|
426
|
+
---
|
|
427
|
+
|
|
428
|
+
## Sources
|
|
429
|
+
|
|
430
|
+
The Publication-Specific Founder PR framework codified in this playbook is drawn from Emilie Gerber's (Six Eastern) published guidance and operator interviews:
|
|
288
431
|
|
|
289
|
-
-
|
|
290
|
-
-
|
|
291
|
-
-
|
|
292
|
-
-
|
|
293
|
-
-
|
|
294
|
-
- **Pitch-to-placement rate** -- Percentage of pitches sent that resulted in published coverage
|
|
295
|
-
- **Message pull-through** -- Percentage of coverage that includes key messaging points from the pitch
|
|
296
|
-
- **Journalist response rate** -- Percentage of pitched journalists who responded (even if declining), indicating list quality
|
|
432
|
+
- Lenny Rachitsky — "The ultimate guide to PR for startups | Emilie Gerber (Six Eastern, ex-Bospar)" — https://www.lennysnewsletter.com/p/the-ultimate-guide-to-pr-emilie-gerber
|
|
433
|
+
- Open Source CEO — "How to do PR: An interview with Emilie Gerber" — https://www.opensourceceo.com/p/emilie-gerber-interview
|
|
434
|
+
- Six Eastern (Gerber's agency, with public client list and case studies) — https://www.sixeastern.com/
|
|
435
|
+
- Lenny's Podcast — Emilie Gerber episode (founder PR masterclass audio + transcript) — https://www.lennysnewsletter.com/podcast
|
|
436
|
+
- First Round Review — adjacent founder-PR operator guidance referenced for the news-peg-calendar pattern — https://review.firstround.com/
|