When you need press coverage or crisis response, /pr-specialist drafts releases, media pitches, and embargo plans, so you can control the narrative. — Claude Skill
A Claude Skill for Claude Code by Nick Jensen — run /pr-specialist in Claude·Updated
Draft press releases, media pitches, and crisis communication plans.
- Press release drafting with AP style formatting
- Journalist-specific pitch personalization
- Embargo strategy and timeline management
- Crisis communication holding statements and Q&A
- Media list building with outlet-angle matching
Who this is for
What it does
Run /pr-specialist with your announcement details to get an AP-style press release with headline, quote, boilerplate, and a distribution timeline.
Feed /pr-specialist the journalist's beat and recent coverage — it crafts a personalized pitch email with a hook tied to their interests.
Use /pr-specialist to design an embargo timeline with tier-1 exclusives, wider embargo, and public release with media kit preparation.
Paste the crisis scenario into /pr-specialist to get a holding statement, internal talking points, social media response templates, and a press Q&A document.
How it works
Describe the PR need: announcement, pitch target, crisis scenario, or media strategy question.
The skill structures the appropriate PR document following industry conventions and best practices.
It outputs ready-to-send content: press releases, pitch emails, embargo plans, or crisis statements.
Review, customize quotes and company details, and distribute through your media channels.
Example
Series B funding: $25M led by Sequoia, total raised $38M. We're a developer tools company with 5,000 customers. Funds will go to enterprise product and European expansion. CEO quote needed.
FOR IMMEDIATE RELEASE [Company] Raises $25M Series B Led by Sequoia to Expand Developer Platform SAN FRANCISCO -- [Company], the developer tools platform used by 5,000 engineering teams, today announced $25 million in Series B funding led by Sequoia Capital, bringing total funding to $38 million. The funds will accelerate enterprise product development and support expansion into European markets. "Developers deserve tools that work the way they think," said [CEO Name], CEO of [Company]. "This investment lets us bring that experience to enterprise teams worldwide." [Boilerplate]
Day -7: Brief TechCrunch (exclusive). Day -3: Brief 5 tier-2 outlets under embargo. Day 0 (9am ET): Embargo lifts, press release on wire, blog post live, CEO LinkedIn post. Day 0+2hr: Founder tweets thread.
Subject: Exclusive: [Company] $25M Series B led by Sequoia Hi [Reporter], your piece on dev tool consolidation last month resonated with our thesis. We just closed a $25M Series B from Sequoia to bring that consolidation to enterprise. Happy to give you the exclusive with CEO access and customer data. Embargo lifts [date]. Interest?
Metrics this improves
Works with
PR Specialist
Expert public relations guidance for earned media strategy, media relations, and reputation building — from press releases to crisis communication.
Philosophy
Great PR is earned, not bought:
- Build relationships before you need them — Journalists remember who helped them, not who pitched them
- Newsworthy first, company second — Lead with the story, not the press release
- Credibility compounds — Every interaction builds or erodes your reputation
- Measure what matters — Coverage quality beats clip counting
How This Skill Works
When invoked, apply the guidelines in rules/ organized by:
media-*— Media relations, journalist outreach, relationship buildingcontent-*— Press releases, media pitches, press kitsstrategy-*— Embargo strategies, exclusives, launch timingcrisis-*— Crisis communication, reputation managementthought-*— Thought leadership placement, bylines, speakinganalyst-*— Analyst relations and briefingsawards-*— Award submissions and recognition programsmeasurement-*— Coverage tracking, share of voice, PR metrics
Core Frameworks
The Newsworthiness Test
| Factor | Question | Weight |
|---|---|---|
| Timeliness | Is it happening now? | High |
| Impact | Who does this affect and how many? | High |
| Proximity | Is it relevant to this audience? | Medium |
| Prominence | Are notable people/companies involved? | Medium |
| Novelty | Is this a first, biggest, or unexpected? | High |
| Conflict | Does it challenge convention? | Medium |
| Human Interest | Is there an emotional story? | Medium |
The PR Funnel
┌─────────────────────────────────────────────────────────────┐
│ │
│ ┌──────────┐ ┌──────────┐ ┌──────────┐ │
│ │ AWARENESS│───▶│ INTEREST │───▶│ COVERAGE │ │
│ │ (Pitch) │ │ (Story) │ │ (Publish)│ │
│ └──────────┘ └──────────┘ └──────────┘ │
│ ▲ │ │
│ │ ┌──────────┐ │ │
│ └──────────│ AMPLIFY │◀─────────┘ │
│ │ (Share) │ │
│ └──────────┘ │
│ │
└─────────────────────────────────────────────────────────────┘
Media Tier Framework
| Tier | Examples | Characteristics | Approach |
|---|---|---|---|
| Tier 1 | TechCrunch, WSJ, NYT | Highest reach, hardest to get | Exclusives, major news only |
| Tier 2 | VentureBeat, Forbes contributor | Strong reach, more accessible | Embargoes, regular pitching |
| Tier 3 | Industry publications, podcasts | Niche but influential | Consistent relationship building |
| Tier 4 | Blogs, newsletters, substacks | Targeted, often undervalued | Direct relationships, content |
Pitch Response Matrix
| Response | Meaning | Next Action |
|---|---|---|
| No response | Wrong timing, topic, or journalist | Try different angle or wait |
| "Not for me" | Wrong beat or outlet | Ask for referral |
| "Send more info" | Interest, needs validation | Provide what's asked, quickly |
| "Not now, maybe later" | Good relationship, wrong timing | Add to follow-up calendar |
| "Let's talk" | Strong interest | Prepare thoroughly, respond fast |
Relationship Building Principles
The 10:1 Rule
For every pitch, provide 10 value-adds:
- Share their articles
- Send relevant tips (not for you)
- Make introductions
- Respond to their requests
- Engage meaningfully on social
Coverage Quality Hierarchy
| Level | Description | Value |
|---|---|---|
| Feature story | In-depth coverage, multiple sources | Highest |
| News mention | Coverage of your announcement | High |
| Expert quote | Your exec quoted in trend story | Medium-High |
| Product mention | Brief mention in roundup/list | Medium |
| Backlink only | Link without context | Low |
Anti-Patterns
- Spray and pray — Mass emailing the same pitch to 500 journalists
- Pitching your press release — "Please publish our press release" is not news
- Forgetting the journalist — They write for readers, not for your company
- Embargo abuse — Breaking embargoes burns bridges permanently
- Metrics theater — Counting clips instead of measuring impact
- Crisis silence — No comment is a comment (usually bad)
- One-and-done outreach — PR is relationships, not transactions
- Overvaluing Tier 1 — Niche coverage often converts better
Reference documents
title: Section Organization
1. Press Release Writing (content)
Impact: CRITICAL Description: Press release structure, writing style, quotes, boilerplate, and distribution strategy.
2. Media Pitching (media)
Impact: CRITICAL Description: Pitch crafting, journalist targeting, subject lines, follow-up cadence, and personalization.
3. Journalist Relationships (media)
Impact: HIGH Description: Building and maintaining media relationships, providing value, and becoming a trusted source.
4. Embargo & Exclusive Strategy (strategy)
Impact: HIGH Description: When to use embargoes vs exclusives, managing multiple outlets, and launch timing.
5. Crisis Communication (crisis)
Impact: CRITICAL Description: Crisis response frameworks, statement writing, proactive vs reactive communication.
6. Thought Leadership Placement (thought)
Impact: MEDIUM-HIGH Description: Bylined articles, op-eds, speaking opportunities, and expert positioning.
7. Analyst Relations (analyst)
Impact: MEDIUM-HIGH Description: Industry analyst briefings, report inclusion, and analyst advisory programs.
8. Award Submissions (awards)
Impact: MEDIUM Description: Award strategy, submission writing, and recognition program management.
9. PR Measurement (measurement)
Impact: HIGH Description: Coverage tracking, share of voice, sentiment analysis, and PR ROI metrics.
title: Analyst Relations impact: MEDIUM-HIGH tags: analyst-relations, gartner, forrester, industry-analysts
Analyst Relations
Impact: MEDIUM-HIGH
Industry analysts influence enterprise buying decisions. A Gartner Magic Quadrant position or Forrester Wave placement can accelerate (or stall) your sales pipeline.
Major Analyst Firms
| Firm | Focus | Key Outputs | Influence |
|---|---|---|---|
| Gartner | Enterprise tech, broad | Magic Quadrant, Hype Cycle, Market Guide | Highest for enterprise |
| Forrester | Customer-focused tech | Forrester Wave, Total Economic Impact | High, methodology-driven |
| IDC | Market sizing, trends | MarketScape, Market Share reports | Strong for market data |
| 451 Research | Deep tech, emerging | Market Insight, Impact reports | Strong in specific domains |
| Constellation Research | Business strategy | ShortList, research notes | Growing influence |
| Omdia | Telecom, media, tech | Decision Matrix, forecasts | Domain-specific |
The AR Program Structure
Annual AR Program:
Tier 1: Core analysts (6-10)
├── Quarterly briefings minimum
├── Inquiry access (if client)
├── Report participation priority
└── Event/summit attendance
Tier 2: Secondary analysts (10-15)
├── Semi-annual briefings
├── Major announcement updates
├── Opportunistic engagement
└── Track their coverage
Tier 3: Watchlist (15-20+)
├── Annual or opportunistic briefings
├── Monitor their research
├── Engage when relevant
└── Build for future relevance
Analyst Interaction Types
| Type | What It Is | When to Use | Cost |
|---|---|---|---|
| Briefing | You present to them | New product, major news | Free |
| Inquiry | You ask them questions | Strategy validation, market intel | Subscription |
| Advisory | Deep strategic session | Major decisions, positioning | Premium |
| Custom research | Commissioned study | TEI, custom research | $$$ |
| Speaking | Present at their events | Visibility, credibility | Event fee |
Briefing Best Practices
Before the briefing:
- Research the analyst's recent coverage
- Review their vendor coverage methodology
- Prepare questions for them (they expect dialogue)
- Time-box your presentation (leave 50%+ for discussion)
During the briefing:
- Lead with the customer problem, not your product
- Use specific customer examples and metrics
- Be honest about limitations and roadmap
- Ask about market trends they're seeing
- Listen more than you talk
After the briefing:
- Send thank you and follow-up materials
- Ask if they need anything else
- Inquire about upcoming research opportunities
- Log notes and next actions
Good Briefing Structure (30 minutes)
Minutes 1-5: Context
├── Market problem you're solving
├── Why it matters now
└── Your approach (differentiated)
Minutes 5-15: Substance
├── Product/solution overview
├── Customer examples (named if possible)
├── Key metrics and outcomes
└── Roadmap highlights
Minutes 15-25: Discussion
├── Their questions
├── Your questions for them
├── Market dynamics
└── Feedback on positioning
Minutes 25-30: Next steps
├── Upcoming announcements
├── Research participation
└── Follow-up items
Good Briefing Practices
✓ "We're seeing customers struggle with [specific problem]. Here's how
we're approaching it differently, and the results we're seeing."
→ Customer-centric, evidence-based
✓ "What trends are you seeing in this space that we should be aware of?"
→ Shows humility, values their expertise
✓ "Here's where we're strong and where we're still developing. Our
roadmap addresses [gap] in Q3."
→ Honest about limitations
✓ "Could you share how you're thinking about the market segmentation
for your upcoming report?"
→ Strategic question, shows engagement
Bad Briefing Practices
✗ 45-minute PowerPoint with no time for questions
→ Analysts want dialogue, not lectures
✗ "We're the industry leader in [category]" without proof
→ Unsupported claims damage credibility
✗ Refusing to discuss roadmap or limitations
→ Analysts see through evasiveness
✗ "We don't have any competitors"
→ Naive, instantly loses credibility
✗ Reading slides word-for-word
→ Suggests you don't know your own story
Magic Quadrant / Wave Preparation
For major comparative research:
| Phase | Timeline | Actions |
|---|---|---|
| Pre-cycle | 6+ months out | Regular briefings, relationship building |
| RFI received | Response deadline | Complete accurately, provide evidence |
| Demo/briefing | Scheduled slot | Prepare extensively, practice |
| Draft review | Limited window | Check facts, submit corrections |
| Publication | Release date | Amplify appropriately, plan responses |
RFI Best Practices
| Do | Don't |
|---|---|
| Answer exactly what's asked | Provide tangential information |
| Use specific metrics and evidence | Make vague claims |
| Name reference customers (with permission) | Say "many customers" |
| Acknowledge gaps honestly | Overstate capabilities |
| Submit by deadline | Ask for extensions routinely |
| Proofread carefully | Submit rushed, error-filled responses |
Positioning for Analyst Reports
| Position | What It Means | Strategy |
|---|---|---|
| Leader | Strong execution + vision | Maintain, don't get complacent |
| Challenger | Strong execution, evolving vision | Invest in innovation story |
| Visionary | Strong vision, building execution | Focus on proof points |
| Niche Player | Focused, specific segment | Own your niche, expand strategically |
Inquiry Best Practices
When using inquiry time:
Good inquiry questions:
✓ "How should we position against [competitor] for enterprise deals?"
✓ "What's missing from our messaging for [buyer persona]?"
✓ "What objections are you hearing about vendors in our space?"
✓ "How is the market thinking about [emerging trend]?"
Bad inquiry questions:
✗ "Will you include us in the Magic Quadrant?"
✗ "Can you tell us what our competitors are doing?"
✗ "Will you be a reference for us?"
✗ "Can you write about us?"
Building Analyst Relationships
| Action | Frequency | Purpose |
|---|---|---|
| Regular briefings | Quarterly | Stay top of mind |
| Quick updates | As needed | Major news, not everything |
| Event engagement | Annual | Face time, deeper conversation |
| Customer introductions | When relevant | Proof points for their research |
| Thought leadership share | Monthly | Demonstrate expertise |
Measuring AR Success
| Metric | What It Indicates |
|---|---|
| Report inclusion | Market recognition |
| Position improvement | Execution on strategy |
| Inquiry mentions | Consideration in deals |
| Quote requests | Thought leadership recognition |
| Win rate lift | Sales impact |
| Briefing requests (inbound) | Analyst interest |
Working with Sales on AR
| AR Provides Sales | Sales Provides AR |
|---|---|
| Report summaries and talking points | Competitive intel from deals |
| Analyst quotes for proposals | Customer reference candidates |
| Guidance on positioning | Feedback on analyst influence |
| Alert on negative coverage | Win/loss context |
Anti-Patterns
- Spray and brief — Briefing every analyst wastes everyone's time
- Pay to play expectations — Subscriptions don't guarantee coverage
- Arguing with analysts — Disagreement is fine, hostility backfires
- One and done — Single briefing before report won't move position
- Ignoring negative feedback — Analysts remember who listens
- Overselling to analysts — They fact-check, exaggeration hurts
- Treating inquiry as sales pitch — They're advising, not buying
- Silence after reports — Continue relationship regardless of outcome
title: Award Submissions impact: MEDIUM tags: awards, recognition, credibility, social-proof
Award Submissions
Impact: MEDIUM
Awards provide third-party validation, content for marketing, and employee pride. Strategic award participation maximizes return on the effort invested.
Award Categories
| Category | Examples | Value | Effort |
|---|---|---|---|
| Industry awards | SaaS Awards, Cloud 100, Deloitte Fast 500 | High credibility | High |
| Publication awards | Inc 5000, Forbes lists, Fast Company | High visibility | Medium-High |
| Best workplace | Great Place to Work, Glassdoor | Employer brand, recruiting | Medium |
| Product awards | G2 Best Of, Capterra Top, TrustRadius | Sales enablement | Low-Medium |
| Regional/local | Local business awards, tech council | Community presence | Low |
| Executive awards | 40 Under 40, Women in Tech | Personal brand | Medium |
Award Selection Framework
Score each potential award:
| Factor | Weight | Questions |
|---|---|---|
| Relevance | High | Does our target audience recognize this award? |
| Credibility | High | Is this a respected program? |
| Visibility | Medium | How is the award promoted and covered? |
| Effort | Medium | What's required to submit and win? |
| Cost | Low | Entry fees, event attendance, etc. |
| Competition | Low | Who else is competing? |
Annual Award Calendar
Q1 Planning:
├── Identify target awards for the year
├── Map deadlines and requirements
├── Assign owners and reviewers
└── Gather baseline materials
Q2-Q3 Execution:
├── Submit applications on schedule
├── Prepare customer references
├── Track submission status
└── Plan win/loss announcements
Q4 Review:
├── Assess win rate and impact
├── Gather feedback on losses
├── Update materials library
└── Plan next year's targets
Building an Award-Ready Library
Maintain ready-to-use components:
| Asset | Purpose | Update Frequency |
|---|---|---|
| Company boilerplate | Standard description | Quarterly |
| Key metrics | Revenue growth, customer count, etc. | Quarterly |
| Customer quotes | Testimonials by use case | Ongoing |
| Case studies | Detailed success stories | Quarterly |
| Executive bios | For individual awards | Annually |
| Product differentiators | What makes you unique | Semi-annually |
| Awards won | List of past recognition | Ongoing |
Writing Winning Submissions
| Element | Good | Bad |
|---|---|---|
| Opening | Specific hook, immediate differentiation | Generic company description |
| Metrics | "147% YoY growth, 500+ customers" | "Significant growth" |
| Differentiation | Specific, provable claims | "Industry-leading," "best-in-class" |
| Customer impact | Named customers, specific outcomes | "Customers love us" |
| Innovation | What's new, why it matters | "We use AI" |
| Proof points | Third-party validation, data | Unsupported claims |
Good Submission Example
[Opening]
When CircuitBoard launched in 2021, enterprise security teams spent an
average of 47 hours per week manually reviewing access logs. Today, our
500+ customers have reclaimed 2.3 million hours annually—time now spent
on strategic security work instead of log analysis.
[Differentiation]
Unlike traditional SIEM tools that require months of configuration,
CircuitBoard deploys in under an hour and begins surfacing actionable
insights immediately. Our patent-pending behavioral analysis identifies
threats that rule-based systems miss, reducing false positives by 89%
compared to legacy solutions.
[Customer Impact]
"CircuitBoard caught an insider threat that had bypassed our other tools
for six months. The ROI was immediate." — CISO, Fortune 500 Financial
Services Company
[Metrics]
• 147% year-over-year revenue growth
• 500+ enterprise customers including 23 Fortune 500 companies
• $0 spent on paid acquisition (100% organic + referral growth)
• 98% customer retention rate
Bad Submission Example
CircuitBoard is a leading provider of innovative security solutions
for the modern enterprise. Our cutting-edge platform leverages advanced
AI and machine learning to deliver best-in-class threat detection.
We are committed to excellence and customer success. Our team of world-
class engineers has built a revolutionary product that is transforming
the security industry.
Many customers have experienced significant improvements after
implementing our solution. We are proud of our rapid growth and
industry recognition.
What's Wrong With the Bad Example
| Problem | Fix |
|---|---|
| "Leading provider" | Prove it with data |
| "Innovative," "cutting-edge," "revolutionary" | Show, don't tell |
| "Advanced AI" | What does it actually do? |
| "Committed to excellence" | Meaningless |
| "Many customers" | How many? Name them |
| "Significant improvements" | Quantify the improvement |
| No specific metrics | Add numbers everywhere possible |
Customer References for Awards
When requesting customer support:
Template:
"Hi [Name],
We're applying for [Award Name], which recognizes [criteria]. Given the
results you've achieved with [Product], would you be willing to:
[ ] Provide a brief quote (I can draft for your review)
[ ] Be listed as a reference customer
[ ] Participate in a brief judge interview (if we're shortlisted)
The time commitment is minimal—I'd handle all the heavy lifting. This
helps us build credibility that benefits all our customers.
Let me know if you're open to it!
Best,
[Name]"
Award Announcement Strategy
If you win:
| Channel | Content | Timing |
|---|---|---|
| Press release | Formal announcement | Day of or next day |
| Social media | Celebration post with badge | Same day |
| Email to customers | Thank them for contribution | Same week |
| Website | Add logo to homepage, awards page | Same week |
| Sales enablement | Update decks, one-pagers | Same week |
| Internal | Company-wide celebration | Same day |
If you're a finalist (but don't win):
- Still announce finalist status (valuable)
- Engage at awards event
- Network with other finalists
- Note the recognition in marketing
If you lose:
- Request feedback if available
- Note lessons for next submission
- No public mention needed
- Improve and resubmit next cycle
Award ROI Calculation
| Cost Component | Typical Range |
|---|---|
| Entry fee | $0 - $500 |
| Staff time (submission) | 4-20 hours |
| Event attendance | $500 - $5,000 |
| Additional materials | $0 - $1,000 |
| Value Component | How to Measure |
|---|---|
| PR coverage | Media mentions, reach |
| Social proof | Use in sales materials |
| Employee morale | Engagement, pride |
| Recruiting | Employer brand lift |
| Website credibility | Trust signals |
Award Logos and Usage
| Do | Don't |
|---|---|
| Use official provided logos | Modify award logos |
| Follow usage guidelines | Claim awards you didn't win |
| Include the year | Use outdated awards prominently |
| Link to verification | Misrepresent category or level |
| Display appropriately sized | Overshadow your own brand |
Timeline for Major Awards
| Award Type | Typical Timeline |
|---|---|
| Revenue-based lists | Nomination Q4, announced Q1 |
| Product awards | Various, often quarterly cycles |
| Workplace awards | Survey-based, multi-month process |
| Industry awards | Often tied to conferences |
| Publication lists | Annual cycle, varied deadlines |
Anti-Patterns
- Applying to everything — Low-value awards dilute the wins that matter
- Pay-to-play "awards" — Verify legitimacy before entering
- Exaggerating in submissions — Judges fact-check, lies backfire
- Missing deadlines — No extensions, mark calendars early
- No follow-through — Winning without announcing wastes the win
- Ignoring finalist status — Being shortlisted is still valuable
- Same submission everywhere — Tailor to each award's criteria
- Forgetting internal celebration — Awards boost morale when shared
title: Press Release Writing impact: CRITICAL tags: press-release, content, announcements, news
Press Release Writing
Impact: CRITICAL
A press release is a formatted announcement, not a story. Its job is to give journalists the facts they need to decide if there's a story worth writing.
Press Release Structure
| Section | Purpose | Length |
|---|---|---|
| Headline | Capture attention, convey news | 10-15 words |
| Subheadline | Add context or key detail | 15-20 words |
| Dateline | Location and date | City, State — Month Day, Year |
| Lead paragraph | Who, what, when, where, why | 2-3 sentences |
| Body paragraphs | Details, context, significance | 2-4 paragraphs |
| Quote 1 | Executive perspective (vision) | 2-3 sentences |
| Quote 2 | Customer/partner validation | 2-3 sentences |
| Boilerplate | Company description | 3-4 sentences |
| Media contact | PR contact information | Name, email, phone |
The Lead Paragraph Formula
[Company name] today announced [what happened], enabling [who benefits]
to [key benefit]. The [product/partnership/milestone] represents [why
it matters] and will be available [when/how].
Good Press Release Headlines
✓ "Acme Raises $50M Series B to Expand AI-Powered DevOps Platform"
→ Clear news (funding), specific amount, what it enables
✓ "Acme Launches Open-Source Alternative to Terraform, Backed by 10,000 GitHub Stars"
→ News (launch), differentiation (open-source), social proof (stars)
✓ "Acme Partners with AWS to Bring Zero-Trust Security to Enterprise Cloud"
→ Notable partner, specific technology, target market
✓ "Acme Report: 73% of Engineering Teams Lack Visibility Into CI/CD Costs"
→ Data-driven, specific percentage, clear topic
Bad Press Release Headlines
✗ "Acme Announces Exciting New Product"
→ Vague, no news value, "exciting" is opinion
✗ "Acme: Revolutionizing the Future of Work with Innovative Solutions"
→ Buzzword soup, says nothing specific
✗ "Press Release: Acme Inc."
→ Literally no information
✗ "Acme Continues to Lead the Industry"
→ Self-congratulatory, not news
Writing Effective Quotes
Quotes should sound human, not like legal approved them into oblivion.
| Good Quote Characteristics | Bad Quote Characteristics |
|---|---|
| Adds perspective not in body | Repeats what's already written |
| Sounds like spoken words | Reads like a legal document |
| Expresses vision or emotion | Generic corporate platitudes |
| Specific to this announcement | Could apply to any company |
Good Quote Examples
✓ "When we started Acme, developers told us they spent 30% of their time
on infrastructure instead of building products. This funding lets us
finally solve that at scale."
→ Specific, origin story, connects to news
✓ "We evaluated six vendors, and Acme was the only one that could handle
our 10,000+ microservices without requiring a dedicated team."
→ Third-party validation, specific proof point
✓ "This isn't just a product launch—it's our answer to the security
theater we've all been putting up with for a decade."
→ Opinionated, memorable, positions against status quo
Bad Quote Examples
✗ "We are thrilled to announce this exciting partnership that will
deliver tremendous value to our customers."
→ Generic, could be any company, any announcement
✗ "Acme is committed to innovation and excellence in everything we do."
→ Empty platitude, not specific to news
✗ "This strategic initiative aligns with our mission to leverage
synergies and drive digital transformation."
→ Buzzword bingo, meaningless
Boilerplate Template
About [Company Name]
[Company] [what you do in one sentence]. Founded in [year], the company
[key differentiation or approach]. [Company] is trusted by [customer
proof: names, numbers, or categories] and has [notable achievement:
funding, growth, recognition]. [Company] is headquartered in [location]
with [team size or office presence]. For more information, visit
[website] or follow [@handle] on [platform].
News Value Checklist
Before sending a press release, verify:
- Is this actually news? (Something happened, not "we exist")
- Would a journalist's reader care about this?
- Is there a specific number, date, or name?
- Is this timely? (Happening now or very soon)
- Is there a credible third-party voice?
- Does the headline convey the news?
- Can I explain why this matters in one sentence?
Distribution Timing
| Day | Effectiveness | Why |
|---|---|---|
| Tuesday | Best | Journalists past Monday backlog |
| Wednesday | Good | Solid mid-week attention |
| Thursday | Moderate | Friday approaches, attention fades |
| Monday | Low | Inbox overload from weekend |
| Friday | Avoid | Weekend burial unless intentional |
Time: 6-8am ET for business press, allows full news day
Press Release Types
| Type | When to Use | Key Elements |
|---|---|---|
| Product launch | New product or major feature | Demo access, pricing, availability |
| Funding | Investment round closes | Amount, investors, use of funds |
| Partnership | Strategic alliance | Both parties quoted, joint value |
| Executive hire | C-suite addition | Background, why they joined |
| Milestone | Users, revenue, growth metric | Specific numbers, context |
| Research/data | Original findings | Methodology, key stats, full report |
| Acquisition | M&A announcement | Terms (if disclosed), integration |
| Award/recognition | Industry recognition | Criteria, competition, quote from org |
Anti-Patterns
- Burying the lead — News in paragraph 3, fluff in paragraph 1
- Quote-as-announcement — Putting the actual news only in a quote
- Jargon overload — "Leveraging AI-powered blockchain synergies"
- Length without substance — 1,000 words when 400 would do
- Missing the "so what" — What happened, but not why it matters
- Fake exclusivity — "Industry-first" when it's not
- Quote-stuffing — Five executives all saying the same thing
- Embargo-only distribution — No follow-up after embargo lifts
title: Crisis Communication impact: CRITICAL tags: crisis, reputation, response, damage-control
Crisis Communication
Impact: CRITICAL
In a crisis, you have hours—not days—to shape the narrative. How you respond in the first 24 hours determines whether you recover or become a cautionary tale.
Crisis Severity Levels
| Level | Examples | Response Time | Who Leads |
|---|---|---|---|
| Level 1: Low | Minor customer complaint, small factual error | 24-48 hours | PR team |
| Level 2: Medium | Product bug, service outage, employee incident | 4-24 hours | PR + Leadership |
| Level 3: High | Security breach, exec misconduct, legal action | 1-4 hours | C-suite + Legal + PR |
| Level 4: Severe | Death/injury, regulatory action, existential threat | Immediate | CEO + Board + Crisis team |
The First 4 Hours
Hour 1: Assess
├── What happened? (facts only, no speculation)
├── Who is affected?
├── What's the current state?
├── What don't we know yet?
└── Who needs to be in the room?
Hour 2: Align
├── Brief leadership and legal
├── Determine what can be said now
├── Identify spokesperson
├── Draft initial holding statement
└── Prepare for employee communication
Hour 3: Act
├── Publish holding statement
├── Respond to journalist inquiries
├── Activate social monitoring
├── Brief customer-facing teams
└── Document everything
Hour 4: Adjust
├── Gather new information
├── Update statement if needed
├── Track coverage and sentiment
├── Plan next communication cycle
└── Begin root cause investigation
The Holding Statement
When you need to respond but don't have full information:
Template:
"We're aware of [situation] and are actively investigating. [What you're
doing about it]. We take this seriously and will provide updates as we
learn more. [If customers affected: Here's what you should do / how to
reach us.]"
Example:
"We're aware of reports that customer data may have been accessed through
our API. We're actively investigating with our security team. We take
data security extremely seriously and will provide a full update within
24 hours. Affected customers can reach our support team at [contact] for
immediate assistance."
Good Crisis Response
✓ "We made a mistake. Here's what happened, what we're doing to fix it,
and how we're making sure it doesn't happen again."
→ Takes responsibility, shows action, commits to change
✓ "We're aware and investigating. We don't have all the facts yet, but
we'll share what we learn within [timeframe]."
→ Honest about uncertainty, commits to timeline
✓ "To our customers: [Specific apology]. Here's exactly what this means
for you and what we're doing about it."
→ Addresses affected parties directly
Bad Crisis Response
✗ "We can neither confirm nor deny..."
→ Sounds like you're hiding something
✗ "This was an isolated incident"
→ Minimizing before you know the full scope
✗ "We take privacy seriously" [with no specifics]
→ Empty phrase that means nothing
✗ Complete silence hoping it blows over
→ Vacuum fills with speculation
✗ "Our lawyers advised us not to comment"
→ You just commented, and badly
✗ Blaming the victim/customer
→ Never, ever do this
Crisis Communication Principles
| Principle | Application |
|---|---|
| Speed beats perfection | A good statement now beats a perfect one tomorrow |
| Own the narrative | You tell the story, or someone else will |
| Transparency builds trust | Admit what you know and don't know |
| Actions over words | What you do matters more than what you say |
| One voice | Designate spokesperson, align all communications |
| Think long-term | How will this response look in 6 months? |
Statement Structure
| Section | Purpose | Example |
|---|---|---|
| Acknowledgment | Show you're aware | "We're aware that..." |
| Facts | What happened (confirmed only) | "On [date], [specific event]" |
| Impact | Who's affected, how | "[X] customers may be impacted" |
| Response | What you're doing | "We've [actions taken]" |
| Commitment | What happens next | "We will [future actions]" |
| Resources | How to get help/info | "Contact [support] or visit [page]" |
Spokesperson Guidelines
| Do | Don't |
|---|---|
| Speak in first person ("we") | Deflect to "they" or "the company" |
| Acknowledge the human impact | Focus only on business impact |
| Stay calm and measured | Get defensive or emotional |
| Say "I don't know yet" if true | Speculate or guess |
| Commit to follow-up timing | Make promises you can't keep |
| Prepare for tough questions | Wing it |
Media Inquiry Response Matrix
| Inquiry Type | Response Approach |
|---|---|
| Breaking news | Holding statement, promise timeline |
| Follow-up questions | Answer what you can, "investigating" for rest |
| Requests for interview | CEO for Level 3-4, spokesperson for 1-2 |
| Hostile/gotcha | Stick to facts, don't take bait |
| Background request | Help journalists understand context |
Internal vs External Communication
| Audience | Timing | Content |
|---|---|---|
| Employees | Before or same time as external | Full context, what to say if asked |
| Customers | Immediately if affected | Impact, what to do, how to reach you |
| Media | Within hours | Statement, spokesperson availability |
| Investors | Same day for material issues | Business impact, response plan |
| Partners | Same day | How it affects them, what you're doing |
Social Media During Crisis
| Platform | Approach |
|---|---|
| Twitter/X | Monitor constantly, respond to direct questions |
| Post official statement, limit engagement | |
| Comments | Acknowledge, don't argue, point to official statement |
| DMs | Route to official channels |
Crisis Timeline Template
T+0: Incident occurs
├── T+30min: Internal alert, war room assembled
├── T+1hr: Leadership briefed, initial assessment
├── T+2hr: Holding statement published
├── T+4hr: First detailed update (if available)
├── T+24hr: Full statement with root cause (if known)
├── T+48hr: Remediation update
├── T+1wk: Post-mortem or detailed report
└── T+30d: Review and process improvements
Post-Crisis Actions
| Timeframe | Actions |
|---|---|
| Week 1 | Full post-mortem, document learnings |
| Week 2-4 | Implement immediate changes, update processes |
| Month 2-3 | Rebuild affected relationships, proactive outreach |
| Month 6 | Audit changes, assess reputation recovery |
Crisis Preparedness Checklist
Before a crisis happens:
- Crisis communication plan documented
- Spokesperson trained on media interviews
- Holding statement templates ready
- Escalation matrix defined
- Legal review process established
- Social monitoring tools active
- Employee communication channels tested
- Key journalist relationships maintained
- Dark site or status page ready to activate
Anti-Patterns
- No comment — Always reads as guilty
- Deleting evidence — Screenshots exist, it will get worse
- Blame shifting — "The vendor" or "a rogue employee"
- Lawyer-speak — Legal CYA language sounds evasive
- Over-promising — "This will never happen again"
- Under-communicating — One statement, then silence
- Defensive posture — Treating journalists as enemies
- Declaring victory early — "Crisis is over" while it's ongoing
- Forgetting stakeholders — Employees learn from news
- No post-mortem — Missing the learning opportunity
title: PR Measurement and Metrics impact: HIGH tags: measurement, metrics, analytics, roi, coverage-tracking
PR Measurement and Metrics
Impact: HIGH
"You can't manage what you don't measure" applies to PR—but measuring the wrong things leads to the wrong priorities. Focus on metrics that connect to business outcomes.
The PR Measurement Framework
| Level | Metrics | What It Tells You |
|---|---|---|
| Output | Press releases sent, pitches made | Activity (effort) |
| Outtake | Coverage volume, reach | Media response |
| Outcome | Traffic, leads, sentiment | Business impact |
| Impact | Revenue, brand value | Ultimate value |
Coverage Metrics
| Metric | Definition | When It Matters |
|---|---|---|
| Coverage volume | Number of articles/mentions | Awareness campaigns |
| Coverage quality | Tier/reach of outlets | Brand building |
| Share of voice | Your mentions vs competitors | Competitive position |
| Message pull-through | Key messages in coverage | Message strategy |
| Spokesperson quotes | Exec quoted in articles | Thought leadership |
| Sentiment | Positive/neutral/negative tone | Reputation health |
Coverage Quality Scoring
| Quality Factor | Score | Criteria |
|---|---|---|
| Publication tier | 1-5 | Tier 1 = 5, Tier 4 = 1 |
| Article prominence | 1-3 | Feature = 3, Mention = 1 |
| Message inclusion | 1-3 | All key messages = 3 |
| Spokesperson quote | 0-2 | Named quote = 2, No quote = 0 |
| Sentiment | -2 to +2 | Positive = +2, Negative = -2 |
Coverage Quality Score = Sum of factors × Estimated reach weight
Good Metrics Reporting
Q3 PR Report
Coverage Summary:
├── 47 total placements (up 23% QoQ)
├── 12 Tier 1 placements (including TechCrunch, VentureBeat)
├── 89% positive/neutral sentiment
└── 73% message pull-through rate
Share of Voice:
├── Category SOV: 34% (up from 28% in Q2)
├── Competitor A: 29%
├── Competitor B: 22%
└── Others: 15%
Business Impact:
├── 14,200 referral visits from coverage
├── 340 trial signups attributed to PR
├── 3 enterprise opportunities sourced from coverage
└── Estimated media value: $892,000
Key Wins:
├── TechCrunch exclusive on Series B (12k visits)
├── Forbes contributor piece on CEO (thought leadership)
└── WSJ quote in industry trend piece
Bad Metrics Reporting
✗ "We got 50 pieces of coverage this quarter!"
→ Volume without quality is meaningless
✗ "Our AVE (Advertising Value Equivalency) was $5M"
→ Discredited metric, doesn't reflect actual value
✗ "We sent 200 pitches this month"
→ Activity metric, not results metric
✗ "Sentiment was 60% positive"
→ Compared to what? What drove negative?
Share of Voice (SOV) Tracking
SOV Calculation:
Your brand mentions / Total category mentions × 100
Tracking approach:
├── Define competitive set (5-10 companies)
├── Set monitoring keywords (brand names, variations)
├── Choose time period (monthly, quarterly)
├── Filter for relevant coverage (exclude noise)
└── Calculate and trend over time
SOV by segment:
├── Overall SOV: All coverage
├── Tier 1 SOV: Top-tier publications only
├── Topic SOV: Specific themes (e.g., "AI security")
└── Geography SOV: Regional breakdown
Message Pull-Through Analysis
Tracking whether coverage includes your key messages:
| Key Message | Definition | Q3 Pull-Through |
|---|---|---|
| "Zero-trust native" | References our ZT architecture | 67% |
| "Enterprise scale" | Mentions Fortune 500 or enterprise | 54% |
| "Developer-first" | Highlights developer experience | 78% |
| "Fastest deployment" | Mentions speed/time to value | 43% |
Action: "Fastest deployment" underperforming—prioritize in pitches.
Sentiment Tracking
| Sentiment | Indicators | Response |
|---|---|---|
| Positive | Praise, recommendations, success stories | Amplify, repurpose |
| Neutral | Factual coverage, balanced reporting | Acceptable baseline |
| Negative | Criticism, problems, complaints | Investigate, respond |
| Mixed | Both positive and negative elements | Analyze what's driving each |
Attribution: Connecting PR to Business
Attribution methods:
Direct attribution:
├── UTM-tagged links in coverage
├── Dedicated landing pages mentioned in articles
├── "How did you hear about us?" surveys
└── First-touch attribution in CRM
Correlation analysis:
├── Traffic spikes aligned with coverage dates
├── Brand search volume increases
├── Social mention velocity
└── Pipeline creation timing
PR Dashboard Components
| Section | Metrics | Update Frequency |
|---|---|---|
| Coverage overview | Volume, tier breakdown, trend | Weekly |
| Share of voice | SOV vs competitors | Monthly |
| Sentiment summary | Positive/neutral/negative split | Weekly |
| Message pull-through | Key message % in coverage | Monthly |
| Business impact | Traffic, leads, pipeline | Monthly |
| Activity | Pitches sent, briefings held | Weekly |
Tools for PR Measurement
| Category | Tools | Use Case |
|---|---|---|
| Media monitoring | Meltwater, Cision, Mention | Coverage tracking |
| Social listening | Brandwatch, Sprout Social | Sentiment, SOV |
| Web analytics | Google Analytics, Mixpanel | Traffic attribution |
| CRM | Salesforce, HubSpot | Pipeline attribution |
| Custom tracking | UTM + spreadsheets | Low-cost attribution |
Benchmarks for PR Metrics
| Metric | Average | Good | Excellent |
|---|---|---|---|
| Pitch response rate | 5-10% | 15-20% | 25%+ |
| Coverage conversion | 2-5% | 8-12% | 15%+ |
| Positive sentiment | 60-70% | 75-85% | 90%+ |
| Message pull-through | 40-50% | 60-70% | 80%+ |
| Tier 1 coverage | 10-15% | 20-30% | 35%+ |
Monthly PR Report Template
[Month] PR Performance Report
Executive Summary:
[2-3 sentences on key performance and notable coverage]
Coverage Metrics:
• Total placements: [X]
• Tier 1/2/3 breakdown: [X/X/X]
• Share of voice: [X]% (vs [X]% last month)
• Sentiment: [X]% positive
Key Coverage Highlights:
1. [Outlet]: [Headline] - [Why it matters]
2. [Outlet]: [Headline] - [Why it matters]
3. [Outlet]: [Headline] - [Why it matters]
Business Impact:
• Referral traffic from coverage: [X] visits
• PR-attributed signups/leads: [X]
• Pipeline influence: [X opportunities]
Activity Summary:
• Pitches sent: [X]
• Briefings conducted: [X]
• Press releases issued: [X]
Upcoming:
• [Planned announcement/launch]
• [Target coverage opportunities]
What NOT to Measure
| Vanity Metric | Why It's Misleading |
|---|---|
| AVE (Ad Value Equivalency) | Discredited—editorial isn't advertising |
| Raw impression counts | Usually inflated, not meaningful |
| Total potential reach | "Could have" seen, not "did" see |
| Pitch volume | Activity without results |
| Social follower counts | Vanity without engagement context |
Proving PR ROI
For executive reporting:
PR Investment: $X (team + tools + agency)
Measurable Returns:
├── [X] enterprise leads attributed to coverage
├── $[X]M pipeline influenced by PR touchpoints
├── [X]% increase in brand search volume
├── [X]% positive shift in analyst sentiment
└── [X] speaking opportunities generated
Estimated Media Value: $[X] (with caveats about methodology)
Qualitative Value:
├── Market positioning as category leader
├── Competitive differentiation in deals
├── Executive visibility and credibility
└── Recruiting advantage
Anti-Patterns
- Counting clips only — 100 low-quality mentions < 5 Tier 1 features
- AVE obsession — Industry has abandoned this metric
- Ignoring negative coverage — Hiding problems doesn't fix them
- No baseline — Can't show improvement without starting point
- Activity over outcomes — "We pitched 500 journalists" isn't success
- Delayed reporting — Monthly metrics should be ready within a week
- No competitive context — Your numbers only matter relative to market
- Vanity dashboards — Pretty charts that don't drive decisions
title: Journalist Relationship Building impact: HIGH tags: media-relations, relationships, networking, sources
Journalist Relationship Building
Impact: HIGH
The best PR doesn't come from pitching—it comes from being the person journalists call when they need a source. Relationships are built before you need them.
The Relationship Spectrum
| Level | Characteristics | Your Value to Them |
|---|---|---|
| Cold | Never interacted | None yet |
| Warm | Engaged with their content | Audience member |
| Connected | Exchanged messages | Potential source |
| Trusted | Provided useful info/sources | Reliable resource |
| Go-to | They reach out proactively | Expert on speed dial |
The 10:1 Value Ratio
For every pitch you send, provide 10 value-adds:
| Value-Add | Example | Effort |
|---|---|---|
| Share their article | Thoughtful LinkedIn share with commentary | Low |
| Send relevant tip | "Saw this, thought of your beat" | Low |
| Make introduction | Connect them to a source they need | Medium |
| Respond to requests | HARO, Twitter asks, source requests | Medium |
| Provide background | Off-record context for their story | Medium |
| Early access | Let them try products before launch | Medium |
| Exclusive data | Share research before it's public | High |
| Source for others | Connect when you're not the story | High |
Building Relationships Before You Need Them
Timeline: 3-6 months before you have news
Month 1-2:
├── Identify 20-30 journalists covering your space
├── Follow them on Twitter/LinkedIn
├── Read their recent articles (actually read them)
└── Start engaging genuinely with their content
Month 2-3:
├── Share their work with thoughtful commentary
├── Respond to source requests (even if not for you)
├── Send occasional tips without asking for anything
└── Begin light DM/email conversations
Month 3-6:
├── Offer to be a background source
├── Make introductions to people they should know
├── Build genuine rapport around shared interests
└── You're now someone they recognize and might respond to
Good Relationship Building
✓ "Saw your thread on AI governance—this Senate hearing transcript
might be useful for your next piece. No need to credit, just
thought you'd want to see it."
→ Provides value, no ask, shows you pay attention
✓ "Re: your request for CISO sources—I'm not the right fit but my
friend [Name] at [Company] deals with this daily. Want an intro?"
→ Helpful even when you can't benefit
✓ "Your piece on [topic] changed how I think about [X]. Specifically
[detailed observation]. Looking forward to the follow-up you
mentioned."
→ Shows genuine engagement, not just flattery
Bad Relationship Building
✗ "Loved your article! Would you like to write about my company?"
→ Transparent flattery-to-pitch pipeline
✗ "I've been following your work for years..." [first interaction]
→ Obvious lie, credibility destroyed
✗ "Let me know if I can ever be helpful" [no specific offer]
→ Vague, puts burden on them
✗ Liking every tweet without ever adding substance
→ Looks automated, provides no value
Journalist Communication Preferences
| Platform | Best For | Etiquette |
|---|---|---|
| Formal pitches, detailed info | Professional, concise | |
| Twitter/X DM | Quick tips, casual connection | Brief, low pressure |
| Professional connection | Don't pitch immediately | |
| Signal/Text | Breaking news, urgent tips | Only if relationship warrants |
| In-person | Events, conferences | Respect their time |
The Background Source Strategy
Offering to be a "background source" builds trust without requiring coverage.
"I'm not pitching anything—just offering to be a background source
if you ever need context on [topic]. Happy to talk off the record
about industry dynamics, explain technical concepts, or point you
toward the right people to interview."
Benefits:
- Builds relationship without transaction
- Positions you as expert
- Creates natural opportunities for future coverage
- Journalists remember who helped them understand complex topics
Responding to Source Requests
HARO (Help a Reporter Out), Twitter requests, and journalist queries:
| Do | Don't |
|---|---|
| Respond within hours, not days | Wait until it's no longer relevant |
| Answer exactly what's asked | Provide tangential information |
| Be quotable and specific | Give vague, hedge-filled responses |
| Include credentials briefly | Send full bio and company overview |
| Offer to elaborate if helpful | Demand to review quotes |
Good Source Response
Subject: Re: Source needed: DevOps security trends
Hi Alex,
For your DevOps security piece:
Key insight: "The biggest shift we're seeing is secrets management
moving from 'we'll figure it out' to board-level concern. After the
CircleCI breach, every CISO I talk to has it on their 2024 priority
list."
Supporting data: 73% of our enterprise customers implemented secrets
rotation in 2023, up from 31% in 2022.
Happy to elaborate or provide customer references if helpful.
[Name], CEO @ Acme (YC '22, ex-Google Security)
Maintaining Relationships After Coverage
| Timing | Action |
|---|---|
| Same day | Thank them (not effusively, professionally) |
| Same week | Share the article with your audience, tag them |
| Ongoing | Continue providing value unrelated to your company |
| Never | Ask them to change something after publication |
Relationship Tracking
Maintain a simple system:
| Field | Purpose |
|---|---|
| Name | Journalist name |
| Outlet | Current publication |
| Beat | What they cover |
| Last interaction | When you last connected |
| Notes | Personal details, preferences |
| Relationship level | Cold/Warm/Connected/Trusted |
| Next action | What value can you provide? |
When Journalists Move
Journalists change jobs frequently. When they do:
✓ "Congrats on the new role at [outlet]! Looking forward to your
coverage there. Let me know if I can ever be useful on
[relevant topic]."
→ Brief, genuine, maintains relationship
✗ "Now that you're at [bigger outlet], would you be interested in
covering [your company]?"
→ Opportunistic, obvious motive
Anti-Patterns
- Transactional only — Only reaching out when you need something
- Fake familiarity — "It's been too long!" when you've never met
- Guilt tripping — "I've shared so much, can you cover us?"
- Bridging to pitch — Pretending to offer value, then pivoting to ask
- Ignoring their beat — Pitching AI to a healthcare writer
- Public pressure — Tagging journalists asking why they haven't covered you
- Over-communication — More than 1-2 touches per month without reason
- Forgetting the human — Journalists are people with interests beyond their beat
title: Media Pitch Crafting impact: CRITICAL tags: pitching, media-outreach, journalist, email
Media Pitch Crafting
Impact: CRITICAL
Journalists receive 50-200 pitches daily. Most get deleted in seconds. A great pitch earns a response in 3-5 seconds of scanning.
Pitch Anatomy
| Component | Purpose | Character Limit |
|---|---|---|
| Subject line | Earn the open | 50-60 chars |
| Hook | Why you, why now | 1-2 sentences |
| The story | What's newsworthy | 2-3 sentences |
| The ask | What you want | 1 sentence |
| Credentials | Why you're credible | 1-2 sentences |
| Sign-off | Professional close | 1 sentence |
Subject Line Formulas
| Formula | Example | When to Use |
|---|---|---|
| Exclusive offer | "Exclusive: First look at [X]" | Tier 1, breaking news |
| Data hook | "New data: 73% of CISOs say [X]" | Research, trends |
| Timely tie-in | "For your [event] coverage: [angle]" | News cycle, events |
| Contrarian | "The case against [popular thing]" | Opinion, trend pieces |
| Question | "Why are VCs suddenly backing [X]?" | Trend stories |
| Name drop | "[Notable person] joins [company]" | Executive news |
Good Subject Lines
✓ "Exclusive: Stripe-backed startup launches open-source Plaid alternative"
→ Exclusive flag, notable backer, clear differentiation
✓ "For your AI coverage: Why 80% of enterprise AI projects fail (new data)"
→ Beat-relevant, specific stat, fresh data
✓ "Quick question about your secrets management piece"
→ Personal, references their work, low commitment
✓ "Source: Ex-Google engineer on why LLMs can't replace search"
→ Expert source, contrarian angle, timely topic
Bad Subject Lines
✗ "Press Release: Acme Inc. Announces New Product"
→ Screams "mass pitch," no news value
✗ "Following up on my previous email"
→ No reason to open, no new value
✗ "URGENT: Major news from Acme"
→ Fake urgency destroys trust
✗ "Partnership Opportunity"
→ Sounds like spam, vague
The 3-Sentence Pitch
[Hook - why this matters to their readers]
[The story - what's happening, with proof point]
[The ask - specific, easy to say yes to]
Good Pitch Example
Subject: For your fintech beat: YC startup replacing SWIFT for B2B payments
Hi Sarah,
Your recent piece on cross-border payment friction resonated with our
customers—we've heard the same complaints from 200+ finance teams.
We just closed $15M from Andreessen to build SWIFT's replacement for B2B.
Our beta users (including Notion and Linear) are seeing 3-day payments
become same-day at 70% lower fees.
Would our CEO be helpful for your payments infrastructure coverage? Happy
to share customer data and early access.
Best,
[Name]
Bad Pitch Example
Subject: Press Release: Acme Revolutionizes Payments
Dear Journalist,
I hope this email finds you well! I wanted to reach out to share some
exciting news about Acme, the leading provider of innovative payment
solutions for the modern enterprise.
Acme is thrilled to announce the launch of our revolutionary new
platform that leverages cutting-edge technology to transform the
payments landscape. Our solution offers best-in-class features and
unparalleled customer service.
I've attached our press release for your convenience. Please let me
know if you'd like to schedule an interview with our CEO to discuss
this exciting announcement.
Thank you for your time and consideration!
Best regards,
[Name]
What's Wrong With the Bad Example
| Problem | Fix |
|---|---|
| Generic greeting | Use their name |
| "Hope this finds you well" | Delete it |
| No hook to their beat | Reference recent work |
| Buzzwords (revolutionary, innovative) | Specific claims |
| "Leading provider" without proof | Credibility via numbers |
| "Attached press release" | Key info in email body |
| No specific ask | Clear, easy next step |
| No reason to respond now | Timely hook |
Personalization That Works
| Level | Example | Impact |
|---|---|---|
| None | "Dear Journalist" | Deleted immediately |
| Name only | "Hi Sarah" | Still feels mass |
| Beat mention | "For your fintech coverage" | Better, shows research |
| Article reference | "Your piece on [X] resonated" | Shows genuine reading |
| Insight addition | "Building on your [X] thesis..." | High effort, high response |
Follow-Up Cadence
| Touch | Timing | Content |
|---|---|---|
| Initial pitch | Day 0 | Full pitch |
| Follow-up 1 | Day 3-4 | New angle or data point |
| Follow-up 2 | Day 7-8 | Different hook, same story |
| Move on | Day 10+ | Add to nurture, try later |
Good Follow-Up
Subject: Re: For your fintech beat: YC startup replacing SWIFT
Hi Sarah,
Quick update since my last note—we just crossed 500 customers and
processed our millionth transaction.
If the SWIFT angle doesn't fit, I've also got a customer (CFO of
Linear) who can speak to hidden costs of cross-border payments.
Either useful for upcoming coverage?
Best,
[Name]
Bad Follow-Up
✗ "Just checking in to see if you got my email"
→ Provides zero new value
✗ "I know you're busy, but..."
→ Apologetic, wastes words
✗ "Bumping this to the top of your inbox"
→ Presumptuous, annoying
✗ Forwarding original email with "?"
→ Lazy, signals desperation
Pitch Timing Matrix
| Journalist Type | Best Pitch Window | Avoid |
|---|---|---|
| Daily news | 6-9am their time | After noon |
| Weekly publication | Monday-Tuesday | Thursday-Friday |
| Freelance | Varies, test | Mass pitch times |
| Podcast host | Weekday mornings | When recording |
The "Not For Me" Response
When a journalist says it's not for them:
✓ "Totally understand. Anyone on your team who might be a better fit
for dev tools coverage?"
→ Asks for referral politely
✓ "Thanks for letting me know. Is there a different angle on
[topic] that would be more relevant to your readers?"
→ Learns their needs
✗ "But this is really big news that your readers need to know about"
→ Argumentative, burns bridge
Anti-Patterns
- Mass BCC pitches — Obvious, disrespectful, ineffective
- Attaching press release — Key info should be in email body
- "Per my last email" — Passive aggressive, relationship killer
- Pitching the wrong beat — Security story to a fintech writer
- No specific ask — What do you actually want them to do?
- Burying the hook — News in paragraph 3
- Over-following up — More than 2-3 follow-ups is harassment
- Pitch during breaking news — Check the news before hitting send
title: Press Kit and Media Assets impact: MEDIUM-HIGH tags: press-kit, media-assets, newsroom, brand-assets
Press Kit and Media Assets
Impact: MEDIUM-HIGH
A well-organized press kit removes friction from coverage. When journalists can easily find what they need, they're more likely to write about you—and get the details right.
Press Kit Components
| Component | Purpose | Format |
|---|---|---|
| Company overview | Quick background for journalists | PDF, web page |
| Fact sheet | Key stats at a glance | PDF, web page |
| Executive bios | Background on spokespeople | PDF, web page |
| Executive headshots | For article illustrations | High-res JPG/PNG |
| Logos | For publication use | SVG, PNG, various sizes |
| Product screenshots | Visual context | High-res PNG |
| Press releases | Historical announcements | PDF archive |
| Media contact | How to reach PR | Email, phone |
| Brand guidelines | Usage rules (optional) | |
| B-roll/video | For broadcast/video | MP4, downloadable |
Company Overview One-Pager
[COMPANY NAME]
What We Do
[One sentence: Company + what you do + for whom]
Example: "Acme helps enterprise security teams detect and respond to
threats 10x faster using behavioral AI analysis."
The Problem We Solve
[2-3 sentences on the market problem]
Our Approach
[2-3 sentences on how you're different]
Key Facts
• Founded: [Year]
• Headquarters: [Location]
• Employees: [Range or number]
• Funding: [Total raised, key investors]
• Customers: [Number and/or notable names]
Leadership
• [CEO Name], CEO — [One line background]
• [CTO Name], CTO — [One line background]
• [Other notable execs]
Notable Milestones
• [Date]: [Milestone 1]
• [Date]: [Milestone 2]
• [Date]: [Milestone 3]
Media Contact
[Name], [Title]
[Email] | [Phone]
Fact Sheet Template
[COMPANY NAME] FACT SHEET
Last updated: [Date]
Company
├── Founded: [Year]
├── Headquarters: [City, State]
├── Employees: [Number/range]
└── Website: [URL]
Funding
├── Total raised: $[X]M
├── Latest round: Series [X], $[X]M, [Date]
├── Lead investors: [Names]
└── Other investors: [Names]
Product
├── Category: [Market category]
├── Platform: [Cloud/on-prem/hybrid]
├── Key capabilities: [3-5 bullets]
└── Pricing model: [Subscription/usage/etc.]
Customers
├── Total customers: [Number]
├── Enterprise customers: [Number]
├── Notable customers: [Names, with permission]
└── Industries: [Key verticals]
Traction
├── [Growth metric 1]: [Number]
├── [Growth metric 2]: [Number]
├── [Other proof point]: [Number]
└── [Award/recognition]: [Name]
Leadership
├── CEO: [Name] — [Previous company/role]
├── CTO: [Name] — [Previous company/role]
└── [Other exec]: [Name] — [Previous company/role]
Contact
├── Media: [Name], [email], [phone]
├── Analysts: [Name], [email]
└── General: [email]
Executive Bio Structure
[EXECUTIVE NAME]
[Title], [Company]
[Paragraph 1: Current role]
[Name] is the [Title] of [Company], where [he/she/they] [key
responsibility]. [One sentence on notable achievement in role].
[Paragraph 2: Background]
Prior to [Company], [Name] [relevant previous experience]. [Notable
accomplishment from past roles].
[Paragraph 3: Personal/credibility]
[Name] [education, board positions, publications, awards, or relevant
personal details]. [He/she/they] is based in [location].
Social/Contact:
LinkedIn: [URL]
Twitter: [Handle] (if active)
Good Executive Bio
Sarah Chen
CEO, Acme Security
Sarah Chen is the CEO and co-founder of Acme Security, where she leads
the company's mission to make enterprise security accessible to teams
of any size. Under her leadership, Acme has grown from a two-person
startup to serving over 500 enterprise customers including Stripe,
Notion, and three Fortune 100 companies.
Prior to founding Acme, Sarah spent eight years at Google, most recently
as Director of Cloud Security Engineering. She led the team that built
Google's internal secrets management infrastructure, serving over 50,000
engineers.
Sarah holds a BS in Computer Science from MIT and an MBA from Stanford.
She serves on the board of Women in Security and Privacy (WISP) and has
been named to Forbes 30 Under 30 and Fortune's 40 Under 40. She lives
in San Francisco with her family.
LinkedIn: linkedin.com/in/sarahchen
Twitter: @sarahchen
Bad Executive Bio
✗ "John is a visionary leader passionate about innovation"
→ Empty adjectives, no substance
✗ "John has over 20 years of experience in the industry"
→ Vague, doesn't say what experience
✗ Three paragraphs of job title history
→ Resume, not bio
✗ "John enjoys hiking and spending time with family"
→ Unless relevant to their role, skip personal filler
Logo and Asset Guidelines
| Asset | Formats to Provide | Guidelines |
|---|---|---|
| Primary logo | SVG, PNG (light/dark bg) | Minimum size, clear space |
| Logo mark | SVG, PNG | When to use vs full logo |
| Wordmark | SVG, PNG | Text-only version |
| Product screenshots | PNG, 2x resolution | Annotated vs clean |
| Headshots | JPG, minimum 1000px | Consistent style across execs |
Press Kit Page Structure
[Company] Press Kit
[Brief intro and media contact at top]
Quick Links:
├── Download all assets (ZIP)
├── Company overview (PDF)
├── Fact sheet (PDF)
└── Latest press release
Company Overview
[Embedded or linked one-pager]
Executive Team
├── [CEO] — Bio | High-res headshot
├── [CTO] — Bio | High-res headshot
└── [Other execs]
Logos & Brand Assets
├── Logo package (ZIP)
├── Brand guidelines
└── Usage notes
Product Images
├── Screenshot gallery
├── Product demo video
└── Infographics (if applicable)
Press Releases
├── [Date]: [Headline]
├── [Date]: [Headline]
└── View all releases
In the News
├── [Publication]: [Headline]
├── [Publication]: [Headline]
└── View all coverage
Media Contact
[Name]
[Title]
[Email] | [Phone]
Newsroom Best Practices
| Do | Don't |
|---|---|
| Keep assets current | Let headshots become outdated |
| Provide multiple formats | Force journalists to request basics |
| Make downloads easy | Require registration to access |
| Date all materials | Let undated content confuse timelines |
| Include media contact prominently | Bury contact information |
| Offer high-resolution options | Provide only low-res images |
Updating Your Press Kit
| Trigger | Action |
|---|---|
| New funding round | Update fact sheet, boilerplate, milestones |
| Executive hire | Add bio and headshot |
| Executive departure | Remove from press kit, archive bio |
| Major product launch | Add screenshots, update capabilities |
| Quarterly | Verify all facts, links, and images current |
| Rebrand | Replace all brand assets |
Making Assets Journalist-Friendly
✓ Clear file naming
Logo_Acme_Primary_RGB.svg
Headshot_SarahChen_CEO_2024.jpg
✓ Multiple sizes/formats
Logo_Acme_Primary_RGB_1000px.png
Logo_Acme_Primary_RGB_500px.png
Logo_Acme_Primary_CMYK.eps
✓ Easy download options
One-click ZIP of all assets
Individual asset downloads
✓ Clear usage guidance
"Logo minimum size: 100px wide"
"Please don't alter logo colors"
Journalist Resource Requests
Common requests to prepare for:
| Request | Have Ready |
|---|---|
| "Send me your logo" | Logo package link |
| "Do you have a headshot of [exec]?" | Direct download link |
| "What's the correct name/title?" | Fact sheet with spellings |
| "Can I get product screenshots?" | Screenshot gallery link |
| "Who should I contact?" | Media contact info |
| "What's your boilerplate?" | Company overview link |
Anti-Patterns
- Registration walls — Journalists won't fill out forms for assets
- Outdated photos — Exec from 5 years ago creates confusion
- Missing formats — No SVG forces bad logo reproduction
- Hidden contact info — Media contact should be prominent
- PDF-only everything — Web pages are easier to reference
- No ZIP download — Journalists often need multiple assets
- Stale information — Employee count from two years ago
- Generic stock photos — Use real product images
title: Embargo and Exclusive Strategy impact: HIGH tags: embargo, exclusive, launch-strategy, media-strategy
Embargo and Exclusive Strategy
Impact: HIGH
Embargoes and exclusives are powerful tools when used correctly, and relationship-destroying weapons when misused. Understanding when and how to use each is critical PR strategy.
Embargo vs Exclusive: Key Differences
| Aspect | Embargo | Exclusive |
|---|---|---|
| Definition | Multiple outlets, same release time | One outlet, first to publish |
| Journalist commitment | Agree not to publish until lift | Agree to publish by deadline |
| Your commitment | Don't give to non-embargoed outlets | Don't pitch to anyone else |
| Coverage quantity | Multiple stories at once | One story, maybe follow-on |
| Coverage quality | Standard coverage | Often deeper, feature-length |
| Best for | Maximum same-day impact | Major news, deeper story |
When to Use Each
| Strategy | Use When | Don't Use When |
|---|---|---|
| Embargo | Multiple outlets will cover, want coordinated splash | News isn't strong enough for broad coverage |
| Exclusive | Tier 1 outlet, want feature treatment | News is time-sensitive and must go wide |
| Neither | News is moderate, relationship building | You have major news warranting coordination |
| Soft exclusive | "First to publish" but others can follow | You need guaranteed coverage |
The Embargo Process
Timeline: 2-3 weeks before announcement
Week -3 to -2:
├── Draft press release and materials
├── Identify target journalists (usually 5-15)
├── Confirm news warrants embargo
└── Prepare embargo agreement language
Week -2 to -1:
├── Send embargo pitches to Tier 1 first
├── Get explicit confirmation of embargo acceptance
├── Schedule briefings/interviews
└── Send materials to confirmed participants
Week -1:
├── Expand to Tier 2-3 if appropriate
├── Conduct briefings
├── Answer journalist questions
└── Confirm everyone has what they need
Day of lift:
├── Confirm timing with all participants
├── Distribute press release at lift time
└── Be available for day-of questions
└── Monitor coverage, thank journalists
Embargo Pitch Template
Subject: [Exclusive] Embargo opportunity: [Headline]
Hi [Name],
[One sentence on why this is relevant to their beat]
We're announcing [brief description of news] on [date]. Given your
coverage of [beat], I'd like to offer you an embargo briefing.
Embargo lifts: [Day], [Date], [Time] [Timezone]
Key points:
• [Bullet 1]
• [Bullet 2]
• [Bullet 3]
Interested in a briefing? I can also provide [data/demo/exec access].
If this isn't for you, please let me know and I'll remove you from
embargo communications.
Best,
[Name]
Embargo Rules of Engagement
| Rule | Explanation |
|---|---|
| Get explicit acceptance | "Yes, I accept the embargo" in writing |
| Confirm timing precisely | Include timezone, never ambiguous |
| Honor commitments | If you offer exclusive data, deliver it |
| Don't over-invite | 5-15 journalists, not 50 |
| Prepare for breaks | Have a plan if someone publishes early |
| Respect "no" | If they decline, don't share embargo info |
Good Embargo Practices
✓ "Please confirm you accept the embargo before I send materials."
→ Explicit acceptance required
✓ "Embargo lifts Wednesday, March 15 at 6:00am ET / 3:00am PT"
→ No ambiguity on timing
✓ "If this isn't relevant to your coverage, no need to respond—
I'll just remove you from this embargo list."
→ Easy out, no pressure
✓ Sending embargo reminder 24 hours before lift
→ Ensures everyone is aligned
Bad Embargo Practices
✗ "Sending you this under embargo" [without asking for acceptance]
→ They never agreed, not bound
✗ "Embargo lifts Wednesday morning"
→ Morning where? What timezone?
✗ Adding journalists to embargo after some have already published
→ Creates confusion and unfairness
✗ Offering the same "exclusive" to multiple outlets
→ Fastest way to destroy trust
The Exclusive Process
Step 1: Identify the right outlet
├── Is this story big enough for them?
├── Do they cover this beat deeply?
├── What's your relationship with them?
└── Can they publish when you need?
Step 2: Make the offer
├── Clearly state it's an exclusive
├── Define what "exclusive" means (time period, scope)
├── Provide timeline expectations
└── Get commitment before sharing details
Step 3: Deliver exceptional access
├── Full exec interview time
├── Customer references
├── Data and visuals
├── Anything they need for a great story
Step 4: After publication
├── Share and amplify their story
├── Hold off other pitches as agreed
├── Don't undermine with competitive coverage
└── Thank them and maintain relationship
Exclusive Offer Template
Subject: Exclusive for [Outlet]: [One line hook]
Hi [Name],
I have an exclusive I think would fit your [beat] coverage.
[Company] is [one sentence news]. This would give [Outlet] the first
look at [why it matters], including:
• [Unique access point 1]
• [Unique access point 2]
• [Data/customer/exec access]
Timeline: We're hoping to have this publish by [date]. Does that work
for your schedule?
If this is interesting, I can send full details and set up a call with
our [CEO/relevant exec].
Best,
[Name]
Exclusive vs Embargo Decision Matrix
| Factor | Favors Exclusive | Favors Embargo |
|---|---|---|
| Story complexity | High (needs depth) | Low-medium |
| Relationship | Strong with one outlet | Strong with many |
| Desired coverage | One deep feature | Many simultaneous mentions |
| Time sensitivity | Can wait for their schedule | Need specific date |
| News significance | Major (funding, acquisition) | Important but not major |
| Follow-on potential | Want cascade of coverage | Want one big moment |
Timing Considerations
| Announcement Type | Typical Embargo Lead Time |
|---|---|
| Funding round | 1-2 weeks |
| Product launch | 2-3 weeks |
| Partnership | 1-2 weeks |
| Executive hire | 1 week |
| Acquisition | 1-3 weeks (often complex) |
| Research/report | 2-4 weeks |
Handling Embargo Breaks
If someone publishes before the embargo lifts:
Immediate:
├── Confirm the break (is it really your story?)
├── Contact the breaking outlet (may be accidental)
├── Notify all embargoed journalists
└── Release embargo immediately if significant break
Communication to embargoed journalists:
"Unfortunately, [outlet] broke embargo. We're releasing immediately
so you can publish at your discretion. Apologies for the disruption—
we're addressing this with the outlet directly."
Protecting Against Breaks
- Only embargo journalists you trust
- Get explicit written acceptance
- Watermark sensitive documents
- Stagger information sharing (basics first, details closer to lift)
- Have a rapid-release plan ready
After the Embargo Lifts
| Timing | Action |
|---|---|
| Lift time | Wide distribution of press release |
| First hour | Available for journalist questions |
| Same day | Monitor coverage, share/engage |
| Day 2 | Follow up with non-covering journalists |
| Week 1 | Pitch secondary angles to non-covered |
Anti-Patterns
- Fake exclusives — Offering same "exclusive" to competitors
- Infinite embargo — Journalists waiting weeks with no lift date
- Embargo everything — Not all news warrants coordination
- Last-minute additions — Adding journalists day before lift
- No break plan — Scrambling when someone publishes early
- Retaliation — Punishing outlets that couldn't cover
- Scope creep — Expanding story during embargo confuses journalists
- Silent treatment — Not confirming lift or providing updates
title: Launch Timing and News Calendar impact: HIGH tags: timing, launch-strategy, news-cycle, calendar
Launch Timing and News Calendar
Impact: HIGH
The best announcement on the wrong day gets buried. Strategic timing maximizes coverage and impact—understanding the news cycle is as important as the news itself.
News Cycle Fundamentals
| Time Period | Characteristics | Strategy |
|---|---|---|
| Morning (6-10am ET) | Journalists setting daily agenda | Best for breaking news |
| Midday (10am-2pm ET) | Story development, interviews | Good for follow-up availability |
| Afternoon (2-6pm ET) | Deadline crunch, filing stories | Hard to get attention |
| Evening/overnight | Limited coverage, next-day pickup | Avoid unless strategic |
Day of Week Analysis
| Day | Effectiveness | Best For | Avoid |
|---|---|---|---|
| Monday | Low-Medium | Week-long campaigns | Major breaking news |
| Tuesday | High | Most announcements | — |
| Wednesday | High | Product launches, research | — |
| Thursday | Medium | Feature pieces, embargoes | Time-sensitive news |
| Friday | Low | Burying bad news (not recommended) | Anything you want covered |
| Saturday/Sunday | Very Low | Emergency only | Everything else |
Optimal Timing by Announcement Type
| Announcement | Best Day | Best Time | Embargo Lift |
|---|---|---|---|
| Funding | Tuesday-Wednesday | 6am ET | Yes |
| Product launch | Tuesday-Wednesday | 6am ET | Yes |
| Partnership | Tuesday-Thursday | 6am ET | Usually |
| Executive hire | Tuesday-Thursday | 6am ET | Optional |
| Research/report | Wednesday | 6am ET | Yes |
| Acquisition | Tuesday-Wednesday | 6am ET | Sometimes |
| Earnings/results | After market close | 4pm+ ET | No |
Calendar Considerations
Avoid these periods:
| Period | Why |
|---|---|
| Major holidays | Skeleton newsroom crews |
| Between Christmas-New Year | News desert |
| Summer Fridays | Reduced attention |
| Election days | All attention elsewhere |
| Major industry events | Competing for attention |
| Earnings weeks | Financial press distracted |
| Breaking news days | Unpredictable, monitor and delay |
Leverage these periods:
| Period | Opportunity |
|---|---|
| Industry conferences | Concentrated audience, press present |
| Earnings calls (of big players) | Draft off market attention |
| January | Fresh budgets, "year ahead" stories |
| September | Post-summer return, planning season |
Building Your Announcement Calendar
Annual Planning:
Q1:
├── January: New Year trends, predictions
├── February: Post-earnings, budget season
└── March: Q1 launches before quarter end
Q2:
├── April: Spring launches
├── May: Pre-summer pushes
└── June: Early summer (slower)
Q3:
├── July: Slowest month (avoid major news)
├── August: Pre-back-to-business
└── September: Back-to-business surge
Q4:
├── October: Fall campaigns
├── November: Pre-holiday (before Thanksgiving)
└── December: Year-end recaps, avoid major launches
Competitive Timing
Competitor announcement imminent?
Option A: Go before
├── Beat them to market
├── Forces them to respond to you
└── Risk: Rushing, quality suffers
Option B: Go same day (counter-programming)
├── Draft off their attention
├── Provide alternative story
└── Risk: Gets lost in their coverage
Option C: Wait
├── Let their news cycle fade
├── Stand alone with your story
└── Risk: Perception of being second
Decision factors:
├── Newsworthiness of your announcement
├── How directly competitive is the news?
├── Your relationship with key journalists
└── Quality of your announcement readiness
Coordinating with Business Calendar
| Business Event | PR Timing Strategy |
|---|---|
| Product launch | PR embargo lifts at or before GA |
| Conference keynote | Embargo lifts during/after keynote |
| Funding close | Announce within 1-2 weeks of close |
| Executive start date | Announce on or near first day |
| Quarterly earnings | Coordinate with investor relations |
| Major customer win | After contract signed, customer approved |
News Cycle Disruptions
When breaking news dominates the cycle:
Assessment:
├── Is this a 1-hour story or multi-day?
├── Does it compete for same journalists?
├── Is there any connection to your news?
└── Can you delay 24-48 hours?
Options:
├── Delay: Safest if your news can wait
├── Proceed: If news is time-sensitive or unrelated
├── Pivot: If you can connect to breaking story
└── Cancel: If news is no longer relevant
Good Timing Decisions
✓ Funding announcement on Tuesday at 6am ET with 48-hour embargo
→ Peak day, time for west coast, journalist prep time
✓ Delaying launch by one day due to major industry acquisition news
→ Prioritizes coverage over arbitrary date
✓ Aligning product launch with industry conference keynote
→ Captive audience, concentrated press
✓ Scheduling exec interview for 10am ET on announcement day
→ Available when journalists are writing
Bad Timing Decisions
✗ Major product launch on Friday before Labor Day weekend
→ Minimal coverage, lost in holiday news desert
✗ Funding announcement same day as Apple keynote
→ Competing with overwhelming tech coverage
✗ Breaking embargo to beat competitor by 2 hours
→ Damages journalist relationships permanently
✗ Announcing at 5pm ET "to make tomorrow's news"
→ Missed today's cycle, may miss tomorrow's too
Timezone Coordination
| Target Audience | Embargo Lift Time | Rationale |
|---|---|---|
| US national | 6am ET | Full news day coverage |
| US tech | 6am PT (9am ET) | West coast journalist friendly |
| Global | 6am ET | US + Europe afternoon |
| Europe-focused | 6am GMT | European news cycle |
| Asia-focused | 6am local | Regional coverage priority |
Contingency Planning
Build flexibility into your timing:
Primary date: Tuesday, March 15, 6am ET
Backup date: Wednesday, March 16, 6am ET
Fallback date: Monday, March 21, 6am ET
Triggers for backup:
├── Major breaking news dominates cycle
├── Key journalist unavailable
├── Technical/legal delay
├── Competitor timing conflict
└── Customer reference backing out
Communication plan:
├── Pre-draft delay notice to embargoed journalists
├── Internal stakeholder notification process
├── Customer/partner coordination
└── Social/marketing asset flexibility
Announcement Sequencing
For multiple related announcements:
Option A: Single big bang
├── All news in one release
├── Maximum single-day impact
└── Risk: Muddled message, too much to cover
Option B: Staggered announcements
├── Space 1-2 weeks apart
├── Multiple coverage opportunities
└── Risk: Fatigue, later news seems smaller
Option C: Primary + follow-on
├── Major news first, supporting news follows
├── Builds narrative over time
└── Works well for product launch + customer wins
Sequencing factors:
├── How related is the news?
├── Can each piece stand alone?
├── What story arc do you want to tell?
└── What coverage cadence can you sustain?
Real-Time Monitoring
On announcement day:
| Time | Activity |
|---|---|
| -24 hours | Final check, embargo reminder sent |
| -1 hour | Verify release ready, team on standby |
| 0 (embargo lift) | Wire distribution, monitoring begins |
| +1-2 hours | Initial coverage lands, share/engage |
| +4 hours | Assess coverage, thank journalists |
| +24 hours | Follow-up pitches to non-covered outlets |
| +1 week | Second wave pitches, different angles |
Anti-Patterns
- Date worship — Arbitrary dates shouldn't override smart timing
- Friday dumps — Only for news you don't want covered
- Holiday ambition — Nobody's reading on Christmas Day
- Competitor panic — Racing to beat them compromises quality
- Ignoring breaking news — Check the news before hitting send
- One-shot thinking — Good news can have multiple waves
- Timezone blindness — 6am PT is 9am ET, know your audience
- No contingency — Always have a backup date
title: Thought Leadership Placement impact: MEDIUM-HIGH tags: thought-leadership, bylines, op-eds, speaking, expert-positioning
Thought Leadership Placement
Impact: MEDIUM-HIGH
Thought leadership turns executives into recognized experts. It's not about promoting your company—it's about sharing insights that make people want to hear more from you.
Thought Leadership Formats
| Format | Reach | Effort | Best For |
|---|---|---|---|
| Bylined article | High | High | Deep expertise, major publications |
| Op-ed | High | Medium-High | Timely takes, policy/industry issues |
| Guest post | Medium | Medium | Niche audiences, SEO value |
| Podcast guest | Medium | Low | Conversational experts, long-form |
| Conference talk | Medium | High | Networking, demos, presence |
| Webinar | Low-Medium | Medium | Lead generation, deep dives |
| Newsletter feature | Varies | Low | Targeted audiences, relationship |
The Byline Placement Process
Step 1: Identify target publications
├── Where does your audience read?
├── What publications does your industry respect?
├── Who accepts contributed content?
└── What's realistic given your brand recognition?
Step 2: Find the right angle
├── What's your unique perspective?
├── What's timely or trending?
├── What will resonate with that publication's readers?
└── What can only you say (based on experience)?
Step 3: Pitch the editor
├── Subject: Clear topic, not "byline submission"
├── Hook: Why this, why now, why you?
├── Outline: What the piece will cover
├── Credentials: Why you're qualified to write this
Step 4: Write and submit
├── Follow publication guidelines exactly
├── Match their style and tone
├── Provide original value (not company promotion)
└── Be responsive to editor feedback
Step 5: Amplify after publication
├── Share across personal and company channels
├── Thank the editor publicly
├── Repurpose into social content
└── Track performance and pitch follow-ups
Good Byline Topics
✓ "Why the Security Industry's Obsession with 'Zero Trust' Is Missing the Point"
→ Challenges conventional wisdom, offers alternative framework
✓ "I've Interviewed 200 CTOs About AI Adoption—Here's What They're Getting Wrong"
→ Original research, specific number, contrarian insight
✓ "The Hidden Cost of Technical Debt: A CFO's Perspective"
→ Unexpected angle (CFO on tech), business relevance
✓ "What the EU AI Act Actually Means for American Startups"
→ Timely, practical, specific audience
Bad Byline Topics
✗ "Why [Your Company] Is Transforming the Industry"
→ Advertorial, will be rejected
✗ "5 Tips for Better Cybersecurity"
→ Generic, adds nothing new
✗ "The Future of AI" [by non-AI expert]
→ Off-topic, lacks credibility
✗ "How to Choose a [Your Product Category] Vendor"
→ Transparent sales pitch
Byline Pitch Template
Subject: Byline pitch: [Specific topic angle]
Hi [Editor name],
[One sentence on timely hook or why this matters now]
I'd like to propose a piece for [publication]: "[Working title]"
The angle: [2-3 sentences describing your unique take]
Why me: [One sentence on your relevant experience/credentials]
Outline:
• [Section 1]
• [Section 2]
• [Section 3]
• [Key takeaway]
Target length: [X] words. I can deliver within [timeframe].
Happy to adjust the angle based on what would work best for your readers.
Best,
[Name]
[Title, Company]
[Brief credential]
Publication Tiers for Tech B2B
| Tier | Examples | Typical Requirements |
|---|---|---|
| Tier 1 | Harvard Business Review, WSJ, NYT | Major thought leader, unique data |
| Tier 2 | Forbes, Fast Company, Inc | Established exec, strong angle |
| Tier 3 | VentureBeat, TechCrunch guest | Industry relevance, timely take |
| Trade | InfoSecurity, DevOps.com | Domain expertise, practical value |
| Emerging | Substacks, industry newsletters | Relationship, niche expertise |
Podcast Guest Strategy
Finding the right podcasts:
├── Search "top [industry] podcasts"
├── Look at where competitors/peers have guested
├── Check Listen Notes, Chartable for discovery
└── Start niche, work up to larger shows
Pitch approach:
├── Listen to 2-3 episodes first
├── Reference specific episode in pitch
├── Offer 3 potential topics they haven't covered
├── Include speaking sample or previous appearance
Interview preparation:
├── Research host and recent guests
├── Prepare 3-5 stories/anecdotes
├── Have data points ready to cite
├── Test audio setup before recording
Good Podcast Pitch
Subject: Guest pitch: [Specific topic]
Hi [Host name],
Loved your episode with [recent guest]—especially the discussion about
[specific point]. It got me thinking about [related angle].
I'm [Name], [Title] at [Company]. We [one sentence about what you do].
Three topics I could bring to your show:
1. [Topic with unique angle] — I've [relevant experience]
2. [Different topic] — Based on [data/experience]
3. [Third option] — This connects to your recent [theme]
I've previously appeared on [podcast names] and can send clips if helpful.
Worth a conversation?
Best,
[Name]
Conference Speaking Opportunities
| Opportunity Type | How to Get It | Effort to Reward |
|---|---|---|
| Keynote | Industry recognition, invited | Highest |
| Breakout session | CFP submission, relationship | High |
| Panel | Moderator invitation, networking | Medium |
| Fireside chat | Host relationship, relevance | Medium |
| Workshop | CFP, demonstrated expertise | High |
| Lightning talk | Lower barrier CFPs | Low-Medium |
CFP (Call for Papers) Best Practices
| Element | Good | Bad |
|---|---|---|
| Title | "How We Reduced Deploy Time by 90% Without Breaking Production" | "DevOps Best Practices" |
| Abstract | Specific problem, clear takeaways, evidence | Vague promises, buzzwords |
| Bio | Relevant experience, previous talks | Full career history |
| Angle | Specific, data-backed, practical | Generic, theoretical |
Building Speaking Credentials
Path from zero to recognized speaker:
Level 1: Local/virtual
├── Meetups and user groups
├── Company webinars
├── Virtual events
└── Podcasts as guest
Level 2: Regional/niche
├── Regional conferences
├── Industry-specific events
├── Workshop facilitation
└── Panel participation
Level 3: National/major
├── Major industry conferences
├── Keynote opportunities
├── Published speaker with clips
└── Invited by reputation
Key accelerators:
├── Video of previous talks
├── Original research or data
├── Unique perspective or story
├── Social proof (engagement, following)
Thought Leadership Calendar
| Frequency | Activity |
|---|---|
| Weekly | LinkedIn posts, engage with industry content |
| Monthly | Podcast appearance or guest post |
| Quarterly | Major bylined article |
| Semi-annual | Conference speaking |
| Annual | Original research or report |
Measuring Thought Leadership Impact
| Metric | What It Indicates |
|---|---|
| Inbound speaking requests | Market recognition |
| Journalist source requests | Expert credibility |
| Social engagement | Audience resonance |
| Byline acceptance rate | Content quality |
| Pipeline from TL content | Business impact |
| Share of voice | Category ownership |
Anti-Patterns
- Company promotion in bylines — Editors will reject, readers will tune out
- Ghostwriting without voice — Generic content defeats the purpose
- Quantity over quality — 10 weak posts < 1 strong article
- Ignoring editor feedback — Collaboration makes pieces better
- Not amplifying — Publishing without promotion wastes effort
- Mismatched venues — Enterprise exec writing for startup blog
- No original insight — Summarizing what others say
- Inconsistent presence — One article per year doesn't build authority