DEV Community: Shilika

Token Launch PR Timeline: The 90-Day Pre-TGE Comms Plan

Shilika — Thu, 28 May 2026 18:30:18 +0000

Token Launch PR Timeline: The 90-Day Pre-TGE Comms Plan

If you're 90 days from a token generation event and you don't have a PR plan in writing, you have a problem. Not a marketing problem. A coverage problem. The tier-1 trade desks at CoinDesk, The Block, Cointelegraph, Decrypt, and Blockworks are scheduling embargoed launch stories four to six weeks out. If you walk in at T-14, you're competing against three other protocols that briefed the same reporter a month ago.

This is the timeline I run with founders on a fractional PR retainer. Twelve weeks, broken into four phases, with the founder deliverables and outlet touchpoints for each. I've stripped out the marketing-adjacent work (KOL contracts, exchange BD, market-maker negotiation) because those tracks run in parallel and have their own playbooks. This is the PR-only timeline.

If your TGE is in less than 90 days, you can still run this. You'll compress phases one and two and accept that you'll land two tier-1 placements instead of four to six. Past 60 days out, the math gets harder.

Why the existing token launch checklists fail on PR

I've read most of them. Surgence, Variant, Kraken 360, EAK, TDeFi, LuvKaizen. They're useful for tokenomics, liquidity, audits, and KOL sequencing. On PR, they collapse the entire function into one bullet that says something like "coordinate tier-1 coverage with launch day."

That's not a plan. That's a hope.

The reason PR gets compressed in these guides is that the people writing them run marketing or tokenomics agencies, not press shops. They don't sit on Signal threads with reporters. They don't know that a CoinDesk Layer 2 piece takes a week of back-and-forth on tokenomics fact-checking. They don't know that a Forbes contributor needs the founder on a call by T-30 or the piece doesn't make the launch window.

The other reason: tier-1 coverage is the hardest line item to guarantee, so generalist agencies hedge. I don't hedge. If your story isn't tier-1 worthy, I tell you at T-90 so we can fix the narrative before we start pitching.

The four phases at a glance

Phase	Weeks	Goal	Tier-1 touchpoints
Foundation	T-90 to T-60	Narrative lock, asset prep, target list	0 (research only)
Seeding	T-60 to T-30	Background briefings, relationship warming	4 to 8 background calls
Embargo coordination	T-30 to T-3	Embargo pitches, locked commitments	4 to 6 confirmed embargoes
Launch and amplification	T-72h to T+14	Embargo lift, syndication, follow-on coverage	4 to 6 published, plus tier-2 wave

What follows is the week-by-week breakdown.

Phase 1: Foundation (T-90 to T-60)

The first 30 days are not about pitching. They are about building the asset that gets pitched. Founders who skip this phase end up pitching a half-formed narrative and burn relationships with tier-1 reporters who flag the project as "not ready."

Week 12 (T-90 to T-83): Narrative audit

What I do this week:

Read the whitepaper, tokenomics, and pitch deck end to end.
Pull the last 90 days of competitor coverage in CoinDesk, The Block, Cointelegraph, Decrypt, Blockworks, Bitcoin Magazine, and Unchained.
Map your narrative to one of the three or four story angles trade reporters are actively writing about. If your story doesn't fit, we rewrite it.
Identify the one number, one mechanism, or one named partner that makes the story tier-1 worthy.

Founder deliverable: A 90-minute call where I extract the three things only you can answer. Why now. Why you. What breaks if this doesn't ship.

Week 11 (T-83 to T-76): Messaging document

This is the internal doc that every external comms artifact gets derived from. Token primer, FAQ, founder bio, one-pager, embargoed press release v0. The Variant team is right that a clean messaging doc is the anchor for exec comms. I'd add: it's also the anchor for fact-checking when a Block reporter emails you at 11pm asking about your treasury structure.

Founder deliverable: Sign off on positioning. Approve the one-line description that will appear in every outlet's first paragraph.

Week 10 (T-76 to T-69): Target outlet and reporter map

I build a spreadsheet. Outlet, reporter, last three pieces they wrote, their angle, the hook that fits them. For a typical token launch I target four to six tier-1 outlets and twelve to twenty tier-2 and regional outlets. APAC adds another layer: Korean (The Bell, ChosunBiz), Japanese (CoinPost), Indian (CoinGape, Forbes India), MENA (Forbes Middle East).

Not every reporter who covers crypto covers token launches. The Block has reporters who do infrastructure deep dives and others who do market structure. Pitching the wrong one wastes the relationship.

Week 9 (T-69 to T-62): Asset production

Press kit. Founder headshots. Product screenshots. Tokenomics infographic. A 90-second explainer video if the mechanism is technical. The Kraken 360 team treats communications as infrastructure for a reason: reporters won't write what they can't visualize.

Founder deliverable: One hour to record b-roll and answer the five questions every reporter will ask.

Phase 2: Seeding (T-60 to T-30)

This phase is what separates the launches that land tier-1 from the launches that don't. You are not pitching the story yet. You are getting on reporters' radar so when you do pitch under embargo, they already know who you are.

Week 8 (T-60 to T-53): Background briefings open

I reach out to four to eight tier-1 reporters with a soft intro. Not "we're launching a token." Something like: "My client is shipping a [Layer 2 / DeFi protocol / restaking primitive] and I'd love to give you a background briefing on what they're seeing in [category]. No embargo, no ask, just context."

Reporters take these calls because they need sources. The good ones are constantly building a mental map of who's working on what. A 30-minute background call with your founder, where the founder doesn't pitch and instead talks honestly about the category, is worth more than ten cold press release blasts.

Founder deliverable: Three to five 30-minute background calls. No slides. No pitch. Just talk.

Week 7 (T-53 to T-46): Op-ed placement

I ghostwrite a 900-word op-ed under the founder's byline and place it in CoinDesk, Cointelegraph, Decrypt, or Blockworks. The op-ed is not about the token. It is about the category problem the token solves. This is how you become a quotable source before you have anything to sell.

For AI-token crossover projects, the AI Magazine and Decrypt AI desk also work here. For cybersecurity-adjacent infra, The Block's security desk is the right home.

Founder deliverable: A 1-hour interview with me to draft from. Two rounds of edits.

Week 6 (T-46 to T-39): Podcast tour

The Web3 podcast circuit is fragmented but valuable. Bell Curve, Empire, The Chopping Block, Unchained, Bankless. APAC: Korea Blockchain Week side stages, Token2049 satellite pods. Booking lead time is two to four weeks. If you want a Bankless slot for launch week, you book it now.

Founder deliverable: Three to five podcast recordings. Same talking points each time.

Week 5 (T-39 to T-32): Investor and partner quote collection

Reporters writing launch pieces want third-party validation. I collect on-record quotes from your lead investor, your largest ecosystem partner, and one tier-1 KOL who isn't being paid. These go into the embargoed press release and the reporter's source list.

Founder deliverable: Email intros to three quote sources. I handle the rest.

Phase 3: Embargo coordination (T-30 to T-3)

Now we pitch the launch story under embargo. If phase two was done right, the reporters already know your founder, already covered the category, and already trust the asset. The pitch is a confirmation, not a cold open.

Week 4 (T-30 to T-23): First embargo pitches

I pitch the top three tier-1 outlets first. Exclusive offers go to one reporter at a time, in priority order, with a 48-hour decision window. If the first reporter declines, the exclusive moves to the next. Only after exclusives are placed do I pitch the rest under standard embargo terms.

This sequencing matters. If you pitch all of CoinDesk, The Block, and Decrypt simultaneously and offer the exclusive to whoever bites first, the slowest-but-most-prestigious outlet usually loses. And the reporter you snubbed remembers.

Week 3 (T-23 to T-16): Embargo locks and tier-2 wave

By T-21, I want four to six tier-1 embargoes confirmed in writing. "Confirmed" means: reporter has accepted the embargo time, editor is aware, fact-check questions are in flight. Verbal interest doesn't count.

In parallel, tier-2 and regional outlets get pitched: Decrypt's secondary desks, Bitcoin Magazine, Unchained, CoinGape, Forbes contributors, AI Magazine if relevant, plus the APAC outlets.

Founder deliverable: 60-minute fact-check calls with each tier-1 reporter. Direct access. No agency filtering. Reporters notice when a founder is unavailable, and the story softens.

Week 2 (T-16 to T-9): Press release lock and asset distribution

Final embargoed press release goes to the reporter list with a clear embargo time. I default to T-0 lift coordinated to the New York morning news cycle (8:00am ET) unless your TGE mechanics force a different window. Asset folder shared. Quote sheets shared. FAQ shared.

This is also the week where embargo breaks happen if they're going to happen. I've written about why elsewhere, but the short version: the more outlets on the embargo, the higher the break risk, and the tighter the embargo language has to be.

Week 1 (T-9 to T-3): T-72h rehearsal

Three days out, I run a launch-day rehearsal with the founder and the comms team. Who responds to what. Who has phone numbers for which reporter. What happens if the embargo breaks at T-6 hours. What happens if a competitor announces something at T-12 hours and we have to decide whether to lift early.

Founder deliverable: 90-minute war-room session. Phone on for the next 72 hours.

Phase 4: Launch and amplification (T-0 to T+14)

Launch day (T-0)

Embargo lifts at the agreed time. Coverage publishes within a 30 to 90 minute window. I monitor for breaks, errors, and missing quotes, and I push corrections fast. The founder is on standby for any reporter who needs a same-day follow-up quote.

The goal at T-0 is not just the launch story. It's the wire pickup. A clean tier-1 story in CoinDesk gets syndicated through CoinMarketCap, CoinGecko, and the broader aggregator network within two hours. That's where the bulk of the impression volume comes from.

T+1 to T+7: Follow-on coverage

The launch story is the headline. The follow-ons are where the long-tail SEO value lives. Tier-2 pieces, podcast episodes that recorded earlier dropping this week, founder op-eds in adjacent verticals (Forbes contributor pieces, The Defiant, Milk Road).

I also pitch reaction stories. "X protocol launched yesterday. Here's what it means for [category]." These are softer pitches with shorter turnaround.

T+8 to T+14: Crisis watch and analyst coverage

The first two weeks post-TGE are when narrative risk is highest. Price action, unlock concerns, community FUD. I keep a daily monitoring rhythm and have crisis comms templates ready. If something goes sideways, the response window is hours, not days.

Analyst coverage (Messari, Delphi, Galaxy research) also pitches well in this window because they're now looking at live on-chain data instead of slide decks.

Common pitfalls I see at T-90

Pitching reporters before the messaging is locked. You only get one first impression. If you pitch at T-75 with a half-formed narrative, the reporter files you as "not serious" and you don't get a callback at T-30.
Treating the embargo list as a numbers game. Twenty embargoed outlets is not better than six. More embargoes means more break risk and weaker per-outlet attention.
Going wire-only. A Chainwire or BTCWire press release distribution gets you baseline visibility but it doesn't get you the CoinDesk feature. Wire is the floor, not the ceiling.
Forgetting APAC. Korean and Japanese trade press cycles run on their own timeline and require local language assets. If your token has APAC exchange listings, you need APAC PR running in parallel from T-60.
No crisis comms prep. Every token launch has at least one minor crisis in the first two weeks. Founders who haven't pre-written holding statements end up tweeting at 2am and making it worse.

What this looks like across different launch shapes

Pre-seed or seed-stage protocol, $50K PR budget, 60 days to TGE. Compressed timeline. Phase one collapses to two weeks. Target three tier-1 outlets, not six. Focus on one founder op-ed plus one CoinDesk or Cointelegraph feature.

Series A protocol with major VC backing, $150K PR budget, 90 days to TGE. Full timeline. Four to six tier-1 embargoes. Two op-eds. Podcast tour. APAC layer if exchange listings are global.

Series B protocol with prior tier-1 coverage, $250K+ PR budget, 120 days to TGE. Extended timeline. The extra 30 days goes into analyst relations (Messari, Delphi pre-briefings) and a multi-region launch with synchronized embargoes across US, EU, Korea, and Japan.

The fractional model vs the agency model

Most token-launch founders I talk to are choosing between a $20K to $30K per month agency retainer with a 6-month minimum or a fractional senior operator on a project-scoped engagement. The agency model gives you an account team. The fractional model gives you the operator who's actually placed the stories.

For a 90-day launch window, the fractional model usually wins on price, speed, and reporter access. The agency model wins if you need ongoing always-on PR for the year after launch.

If you're 60 to 90 days from a TGE and don't have a PR plan in writing, the next move is a 30-minute teardown where I read your messaging, pull your competitors' coverage, and tell you whether your story is tier-1 worthy. If it's not, I'll tell you what to fix before we start pitching.

APAC Web3 PR Playbook: Korea, Japan, Vietnam, India

Shilika — Thu, 28 May 2026 18:30:13 +0000

APAC Web3 PR Playbook: Korea, Japan, Vietnam, India

APAC is not one PR market. It's at least four, each with its own media structure, its own gatekeepers, and its own definition of what counts as credible coverage. If you run the same launch playbook in Seoul that you ran in Ho Chi Minh City, one of the two campaigns will quietly fail and you won't know why for six weeks.

I've spent the last six years running Web3 PR across Korea, Japan, Vietnam, Singapore, India, and the UAE. The single most expensive mistake I see founders make is treating APAC as a region on a global media list. It isn't. It's a set of fundamentally different press economies that happen to share a time zone band.

This is the playbook I use to sequence a launch across the four ecosystems that matter most for early-stage Web3 and AI founders: Korea, Japan, Vietnam, and India. Each section gives you the manual version and the version I run when I'm embedded.

The four ecosystem types you're actually dealing with

Asian crypto media does not move toward one global model. Markets split into three playbooks: venture-media complexes (Vietnam), exchange-anchored ecosystems (China, Hong Kong, Indonesia), and independent media under regulation (Japan, South Korea). I add India as a fourth category, business-press-anchored, because the dominant outlets are general tech and business press rather than crypto-native or exchange-owned.

Here's the cheat sheet:

Market	Ecosystem type	Who actually moves the narrative	Where founders waste budget
Korea	Independent crypto-native, regulated	Tier-1 crypto outlets plus community forums	One-shot pitches to a single "top" outlet
Japan	Independent crypto-native, conservative	Crypto-native publishers plus traditional financial press	Hype-led messaging, English-only assets
Vietnam	Venture-media complexes	Venture-aligned media plus KOL networks	Treating it like a pure paid-media market
India	Business/tech press anchored	Tier-1 business press, founder-led narratives	Pitching India desks of US crypto outlets

The practical implication: you cannot recycle a single press release. You need four positioning angles, four distribution sequences, and four definitions of success.

Korea: portfolio play, not a headline play

Korea is the market founders most often get wrong because the surface looks familiar. Big retail base, active trading, English-speaking founders in the ecosystem. So they pitch one outlet, expect a halo effect, and watch the story die in 48 hours.

Korea isn't a single-outlet market. Korean crypto media is mature yet fragmented: there's no single holding company controlling distribution, and no exchange-owned media mega-network dominating the narrative. Instead, independent outlets like TokenPost, BlockMedia, Coinness, Coin Readers, BloomingBit, and community-heavy destinations each maintain distinct audiences. Each one has loyal direct traffic, which means readers come there on purpose, not from a Google search.

That changes the strategy. You're not trying to land a headline. You're trying to build simultaneous presence across four or five independent outlets so that a Korean investor who checks two of them sees you both times.

Then there's the regulation layer. Planning should begin with a practical understanding of Korea's regulatory direction and user-protection expectations, including how the Financial Services Commission (FSC) approaches market integrity and how the Virtual Asset User Protection Act framework has raised the bar on consumer protection and operational standards. Avoid investment-style language. Don't imply returns, guaranteed outcomes, "profit expectations," or price-driven milestones.

The manual version of Korea PR:

Translate your core narrative into native Korean, not machine-translated English. Korean readers spot AI translation in one paragraph.
Build a target list of 5 to 7 independent crypto outlets plus 2 business desks.
Strip out any investment-implying language before it ever touches a draft.
Pitch a coordinated wave so the story shows up across the portfolio in the same 72-hour window.
Plan a community circulation layer (Telegram, KakaoTalk, Naver Cafe) for the week after.

The embedded version: I run the wave coordination from an embargo timeline I share with each outlet 7 to 10 days out, with Korean-language assets attached. Coverage hits within a 24-hour window. Community partners pick it up the same day. By day 3, the story has moved from earned coverage into the trader forums that actually drive Upbit and Bithumb listing committee attention.

Japan: positioning over pickup

Japan is the market where most founders give up after two weeks because nothing happens. The pitch goes out, the outlet replies politely, and then there's silence for a month.

Japan rewards patience and punishes hype. In Japan and South Korea, stricter financial and media rules demand careful wording, documentation, and long-term positioning over hype. A Japanese crypto reporter will not break their week to cover your seed round. They will cover your protocol if you've been building credibility for six months and you bring them a story tied to a real product milestone, a regulatory shift, or a Japanese partner.

There's also a structural difference worth knowing. Mature markets like Japan exhibit a different trend: traditional financial institutions acquiring or backing crypto media to drive mainstream adoption. That means a placement in a financial-institution-adjacent outlet carries more weight with Japanese investors than a pure crypto-native scoop.

The manual version of Japan PR:

Start with documentation. A clean one-pager in Japanese, a founder bio, a token economics summary if applicable, all polished and conservative in tone.
Get one Japanese advisor or local partner on record before you pitch. Reporters will ask.
Lead with the regulatory and compliance posture, not the trading upside.
Pitch through introductions, not cold email. Cold email gets a 2% reply rate in Tokyo.
Plan for a 6-to-8-week pickup cycle, not a 2-week one.

The Japan stablecoin story is a good example of what reporters there actually want. SBI Holdings unveiling plans to work with blockchain firm Startale on stablecoin issuance and infrastructure. "Japan has watched the yen weaken for years, and it's looking for new ways to keep the currency relevant globally," Tim Sun, senior researcher of HashKey Group, told The Block. "A yen stablecoin gives Japan a chance to rebuild the yen's role in a digital-first economy." Notice the angle: macro, currency policy, institutional. That's the wavelength Japanese coverage operates on. Pitch into that frequency or stay home.

Vietnam: the venture-media funnel

Vietnam is the most misread market in APAC. Founders see the retail enthusiasm, the high adoption numbers, and treat it like a pure KOL play. They drop $30K on Telegram shillers and wonder why nobody at the actual VC funds will take their meeting.

Vietnam runs on a different logic. In Vietnam and parts of Southeast Asia, ventures and media merge into one funnel. Coin68, Kyros, IVY, and their KOL networks act as a gate to the wider retail audience. The VCs, the media, and the KOL networks are the same people wearing different hats. If you land a venture endorsement, the media coverage follows. If you skip the venture layer and go straight to KOLs, you get paid impressions and zero credibility.

There's an upside to this. In Vietnam's unregulated space, by contrast, a few savvy players (Coin68, IVY) seized the opportunity to build influential platforms without facing compliance barriers. This paradoxically enabled higher-quality content dominance in the absence of regulation. That means the gatekeepers are concentrated, identifiable, and reachable. You don't need 40 outlets in Vietnam. You need 4, plus the right venture relationship.

The manual version of Vietnam PR:

Identify the venture-media node that fits your category (DeFi vs gaming vs infrastructure).
Open the relationship at the VC level, not the editorial level.
Translate to Vietnamese for all retail-facing assets. Keep English for VC-facing decks.
Sequence the KOL push after the venture-aligned media coverage lands, not before.
Expect coverage to be picked up faster than anywhere else in APAC. Vietnam moves in days, not weeks.

India: business press first, crypto press second

India confuses founders because the crypto-native press is thin but the business and tech press is enormous. The default founder reflex is to pitch the India desks of CoinDesk or Cointelegraph. That works for a global story but it does almost nothing for India-specific adoption.

What moves in India is business press coverage with a credible founder profile attached. The reader you're trying to reach is a 28-year-old engineer in Bangalore who reads Inc42, YourStory, MoneyControl, and Economic Times on their phone. They don't read crypto-native outlets first. They read business press, see your founder quoted on a sector trend, and then go look up the protocol.

The manual version of India PR:

Build a founder profile angle that fits Indian business press categories: fintech, AI, deep tech, founder journey.
Lead with the India market opportunity, even if your protocol is global. Indian editors need a local hook.
Op-eds work disproportionately well. Indian business press accepts contributed pieces from credible founders more readily than US press.
Plan the crypto-native coverage as a follow-up wave, not the opener.
Time it around a real event: a partnership, a regulatory comment, a local hire, a venture round with an Indian fund.

India is also the market where I see the most ROI from podcast tours. Indian crypto and startup podcasts have engaged audiences and almost no founders show up on them. You can book 6 to 8 quality podcasts in a month and arrive at a Bangalore meetup as a known name.

The sequencing question: which market goes first

The question I get from every founder running an APAC launch: what order do we do this in?

It depends on the round shape. Three patterns I've run:

Pre-token, equity-funded protocol. Start with Japan because the documentation discipline you need there forces you to clean up your messaging for the other three markets. Then Korea, because Korean coverage signals credibility to Vietnamese VCs. Vietnam third for adoption velocity. India last as the long-tail audience-building play.

Token launch with TGE in 60-90 days. Reverse it. India and Vietnam first to build the retail base and KOL momentum. Korea coordinated wave at T-7 days from TGE. Japan as a post-launch credibility layer at T+30, framed around exchange compliance or institutional adoption.

Exchange listing comms. Korea leads. The Korean coverage feeds directly into the listing committee's diligence process at Upbit and Bithumb. Vietnam follows for trading volume. Japan and India are supporting waves.

Notice what's not in any of those sequences: a single regional press release. That document does not exist in my workflow. There are four parallel campaigns running on four different clocks.

Common pitfalls I see every quarter

The mistakes repeat across founders. Most of them are budget mistakes disguised as strategy mistakes.

Treating APAC as one buy. Agencies that quote you a single APAC retainer are almost always strong in one market and weak in the other three. Ask which markets they have in-language operators in. If the answer is "we have partners," you're paying agency margin on top of partner margin.
English-first content with translation as an afterthought. Korean and Japanese readers can tell within one sentence whether content was written for them or translated to them. Translated content gets discounted automatically.
Pitching the wrong outlet for the angle. A funding announcement does not belong in a Japanese crypto-native publication that prefers technical product stories. A protocol upgrade does not belong on an Indian business desk that wants founder narratives.
Skipping the community circulation layer. Especially in Korea. Don't treat Korea like a "post on X and watch it spread" market. Treat it like a "publish credibility, then let communities circulate it" market.
Booking KOLs before earned coverage. This kills credibility in Korea and Japan. KOL posts that precede earned media get read as pure paid promotion. KOL posts that follow earned media get read as endorsement.
Ignoring regulatory language. This will get your campaign killed in Korea and quietly buried in Japan. Investment-style language is a hard no in both markets.
Assuming Singapore and Hong Kong cover the region. They don't. Singapore press reaches institutional readers across SEA but does almost nothing for Korean retail or Japanese product adoption.

Manual approach vs. embedded operator

If you're running this yourself, budget 15 to 20 hours a week per market for the first eight weeks. That's the realistic time cost of building outlet relationships from cold, translating assets, and coordinating timing. Most founders try to do this on top of fundraising and product and discover after a month that they've sent 40 pitches and landed two pieces.

The embedded version: a senior operator runs all four markets in parallel against a single sequencing plan. Native-language assets prepared in advance. Outlet relationships already warm. Wave coordination on a timeline the founder can see. The cost is a fraction of a multi-market agency contract because there are no account-team layers and no per-market agency partners marking up the work.

Which one is right depends on how fast you need to move and what the round economics look like. A pre-seed protocol with 10 months of runway can absorb the founder time. A Series A with a TGE in 60 days cannot.

What to take away

APAC is four campaigns, not one. The Outset PR analysis got the structural insight right: the region splits into ecosystem types, and each type has its own playbook. Korea is a portfolio play. Japan is a credibility play. Vietnam is a venture-media funnel. India is a business press play with a crypto follow-up.

Sequence them in the order that fits your round shape. Translate properly. Strip investment language for regulated markets. Coordinate the waves. And whatever you do, stop pitching the same press release across four time zones.

If you're running an APAC launch in the next 90 days, the time to map this is now, not the week before TGE.

Forbes Contributor Strategy for Founders After the 2024 Changes

Shilika — Thu, 28 May 2026 17:51:58 +0000

Forbes Contributor Strategy for Founders After the 2024 and 2025 Changes

If you're chasing a Forbes contributor slot in 2026 the way the old guides told you to, you're chasing a program that no longer exists. Open applications closed in 2024. Forbes moved to invite-only / editor-led recruitment. There's no longer a public application form to fill in. And in December 2025, the program got smaller again. The short answer for founders: a contributor byline is still worth pursuing, but only if you treat it as a publishing commitment, not a credential purchase. For most founders, a Forbes Councils seat, an Entrepreneur Leadership Network seat, or a single well-placed op-ed in a tier-1 outlet will deliver more business value with less risk.

I've been ghostwriting op-eds and placing founders into Forbes, CoinDesk, Cointelegraph, Decrypt, AI Magazine and Blockworks for six years. The Forbes question comes up on almost every intro call. So let me walk you through what actually changed, what still works, and where ghostwriting is and isn't safe in the 2026 program.

What actually changed in 2024 and 2025

Three things matter. Everything else is noise.

The pageview revenue-share ended in 2024. The "$50/article + $250 monthly bonus" pay structure described in older guides is gone. Most contributors today are unpaid or on small per-piece fees negotiated case-by-case. If you read a guide that still references that pay model, throw the whole guide out. It hasn't been updated for two program overhauls.

December 2025: Forbes culled dozens of contributors. Existing contributors who weren't publishing at least two "impactful" articles per month were moved to "former contributor" status. The bar to stay on the platform is now meaningfully higher than it was when most older guides on this topic were written. Assistant managing editor Jeffrey Marcus framed the trim as keeping the "contributor model financially sound."

Applications are invite-only. You get in either because an editor sources you, because a current contributor refers you, or through the paid Forbes Councils route. The Josh Steimle and ContentPowered guides describing a Google Form you fill out, or a pitch you fire off to opinion@forbes.com, are describing a door that closed.

If you're a founder and you read all that and think "great, I just won't apply," you're missing the upside. A real contributor byline still compounds. According to Instant Press's 2026 analysis, the slot is now worth less as a standalone credential than it used to be and worth more as part of a coordinated AEO strategy. The reason is simple. LLMs weight Forbes heavily in their training data, which means every piece you publish under your byline becomes part of how future models talk about your category. A contributor who publishes 24 well-reported pieces a year into a specific beat ends up being named by ChatGPT and Perplexity as a credible voice in that beat within twelve months. That compounding is the real prize.

That is the new math. The Google SERP halo is secondary now. The LLM training data is primary.

Forbes Contributor vs Forbes Councils vs BrandVoice

This is where founders lose months of time. The three things look similar from the outside. They are completely different products.

Path	What it is	Cost	Who it's for
Forbes Contributor	Editorial column, editor-led	Unpaid or small per-piece fee	Founders who can write 2+ pieces/month
Forbes Councils	Paid membership network	$600 to $5,000/year	Founders who want a credential without writing 24 pieces/year
Forbes BrandVoice	Sponsored content	High four to five figures per piece	Enterprises buying narrative real estate

Two facts founders almost never know on the intro call:

Forbes Council members are not contributors. And in fact, if you apply for and join a Forbes Council, you can never contribute to Forbes as a regular contributor, per their terms and conditions. This is the single most expensive mistake I see. A founder pays for a Council seat, then six months later wants to be a contributor, and finds out they've disqualified themselves permanently.

Forbes BrandVoice allows brands to publish sponsored stories. They're clearly marked as "BrandVoice," but they still offer credible exposure. BrandVoice is paid placement. It's clearly labeled. Don't confuse it with editorial.

If you're a Series A or B founder and you want a contributor seat, do not touch the Councils. If you want a credential and you don't want the publishing obligation, the Councils are the right answer. They are not the same thing.

What Forbes editors actually look for in 2026

I've seen the inside of these conversations. The bar is now four things, and editors filter ruthlessly on all of them.

Demonstrated expertise in a specific niche. Not "business" or "leadership." A tighter focus. The editors are filling gaps in coverage, and generalists don't fill gaps.

An audience you bring with you. Forbes wants contributors who can drive their own traffic. An existing newsletter list, a real Twitter following, a podcast audience. Any of these help. This is the biggest change from the pre-2024 program, which didn't care whether you brought readers.

Clean disclosure posture. Editors check whether you have undisclosed financial interests in the companies you'd be writing about. A VC writing about portfolio companies is fine if disclosed. A consultant writing about past clients is fine if disclosed. Hidden conflicts are the fastest way to get an application killed.

And the publishing commitment. Contributors are expected to publish regularly - now codified as at least 2 impactful articles/month. If you can't commit to two real pieces a month for the next twelve months, don't apply. The cull will catch you.

The pitch that actually gets you in

If you have the audience, the niche, and the writing chops, the pitch process is straightforward. Editors recruit. You make yourself easy to recruit.

Step one: identify the right editor. Forbes runs its sections with distinct editors across tech, venture, leadership, retail, SMB, crypto, AI and wealth management. Pitching the wrong editor gets your application buried or redirected with no follow-up. Read the Forbes sections you care about. Note the editor names in the bylines and the contributor footers. That's your list.

Step two: draft three sample angles. Not finished pieces. Angles. Three specific story concepts you would write in your first ninety days as a contributor, with a one-paragraph angle summary for each. This becomes the core of your application. Editors want to see how you think, not what you can already publish.

Step three: write the cold pitch. Two hundred words. First line names the beat you want to cover and the gap you see in current coverage. Second paragraph explains why you specifically are the person to fill it.

The part nobody writes down: warm the editor first. Cite their recent work in a LinkedIn comment. Reply to their tweets with something useful, not flattery. Be a known name in their notifications before the cold pitch lands. The hit rate on a warm cold pitch is roughly 5x a true cold one in my experience.

Decision timing on these applications has stretched. How long does the Forbes Contributor application take? Four to eight weeks from submission to a decision in normal cycles. The review includes a portfolio check, reference review, an editorial interview, and a topic area assessment. Accepted contributors usually publish their first piece within two weeks of onboarding.

Where ghostwriting is and isn't safe now

This is the question I get asked every week, usually on Signal, usually phrased nervously. Let me be direct.

Ghostwriting an op-ed for placement in a tier-1 outlet's editorial section is standard practice and entirely safe. Op-eds in The Wall Street Journal, Financial Times, Fortune, TechCrunch, CoinDesk, Cointelegraph, AI Magazine and dozens of other outlets are routinely drafted by a communications partner and edited by the named author. The byline is the founder's because the ideas, lived experience and final edits are the founder's. The drafting is craft.

Ghostwriting a Forbes Contributor column under a founder's byline, where that founder is a Forbes Contributor of record, is now a different situation. Paid contributor slots are gone. Before 2024, a handful of agencies quietly operated contributor slots as a product. A founder paid a retainer, the agency's contributor published a piece under their own byline, and the founder got the credit without ever writing anything. Forbes ended that. Every contributor now goes through the same vetting process and editors ask pointed questions about anyone whose portfolio looks like it was built by a ghostwriter on retainer.

Any agency or service claiming to sell a Forbes Contributor slot in 2026 is misrepresenting what they can deliver.

The clean line in 2026 is this. A communications partner can:

Help you sharpen the angle on a piece you're publishing under your own Forbes Contributor byline.
Edit and pressure-test the draft you wrote.
Pitch op-eds under your byline to outlets that publish op-eds in their editorial sections.
Coordinate the embargo, the supporting press, and the post-publication amplification.

A communications partner should not be ghostwriting your monthly Forbes Contributor columns from scratch under your name. The risk surface includes the cull list and a quiet conversation with a section editor that ends your tenure.

If you don't want to write the columns yourself, you do not want a contributor seat. You want one of the alternatives below.

The alternatives nobody talks about properly

Three months ago a founder asked me whether they should pay $5,000 for a Forbes Councils seat. I asked what they actually wanted. They wanted to be quotable in their category. They wanted the LLMs to name them when someone asked "who are the leading voices on X." They wanted something to point at on their site.

The Councils seat would have done about 40% of that. Here's the full menu I walked them through.

Entrepreneur Leadership Network. As of November 1, 2022, the cost of a membership to the Entrepreneur Leadership Network is $3,000 per year. There are no monthly options currently available. You can submit up to four articles per month. All contributed articles have nofollow links. Cheaper than the top end of Forbes Councils, with a comparable audience reach for B2B founders. The nofollow links matter if your goal was SEO. They don't matter if your goal was authority and LLM citation.

Inc. Still publishing contributors; application process competitive but open. Inc.'s contributor program is smaller and more editorial than Entrepreneur's. Harder to get into, less paid surface area, but the bylines carry more weight in the founder and operator audience.

Fast Company. Pitches go through editors, no formal contributor program. Treat Fast Company as an op-ed and feature outlet, not a publishing platform. A single placed op-ed in the Fast Company editorial section often outperforms a year of Forbes contributor columns for narrative authority in design, product and tech-adjacent categories.

Business Insider. Still accepts open pitches; running editorial fellowships, though has been through significant editorial restructuring in 2024–2025. The restructuring matters. Editor turnover has been heavy. Confirm your editor is still in seat before you build a relationship.

Harvard Business Review. High bar, but a single placement carries more weight than most Forbes contributor articles. If you have research, original data, or a frame nobody else is using, HBR is the highest-leverage single placement in the founder PR universe. It also moves the slowest.

Substack and your own channel. Substack - Now over 35M active subscribers and 3M+ paid. Top business writers (Lenny Rachitsky, Packy McCormick, etc.) are at audience scales that rival mid-tier business publications. If you can write two pieces a month for the Forbes contributor seat, you can write two pieces a month for your own Substack. The Forbes seat compounds against the Forbes brand. Your Substack compounds against you.

Three founder scenarios

Pre-seed or seed crypto founder. You don't have the audience for a contributor seat and you don't have time to write 24 pieces a year. Skip Forbes for now. Do a CoinDesk or Cointelegraph op-ed under your byline, ghostwritten with a partner, focused on a single sharp argument. That single op-ed gets you cited in LLMs for your category faster than a year of contributor columns nobody reads.

Series A AI founder with a strong technical thesis. You're the right profile for a contributor seat, but only if you genuinely want to publish. Apply through a warm intro from an existing contributor in the AI section. Use the three-angle pitch above. Plan for a four to eight week decision cycle. While you wait, place a foundational op-ed in AI Magazine or TechCrunch to give the editor proof of voice.

Series B founder, enterprise B2B, busy. Don't chase Forbes contributor. Pay for a Councils seat at the tier that matches your category, or pay $3,000 for ELN, and use the slots to publish founder essays your partner edits. Pair it with two earned op-eds a year in the tier-1 of your category. That stack costs less than a single quarter of a traditional agency retainer and produces more durable authority.

Common pitfalls

Founders sign up for Forbes Councils thinking it's the contributor program. Then they can't ever become a contributor. I've already mentioned this. It's the single most expensive mistake. Read the fine print before you swipe the card.

Founders apply, get accepted, publish three pieces, and disappear for two months. December 2025: Forbes culled dozens of contributors. Existing contributors who weren't publishing at least two "impactful" articles per month were moved to "former contributor" status. The cull is real and it's now a documented policy. If you can't sustain the cadence, don't take the seat.

Founders hire an agency that promises a "guaranteed Forbes contributor slot." There is no such thing in 2026. Walk away.

Founders pitch the wrong editor. The crypto editor doesn't want your AI piece. The leadership editor doesn't want your token launch piece. Editor-section fit is the single biggest filter on cold pitches. Get it right.

Founders ghostwrite their contributor columns and don't disclose. Forbes editors now do portfolio reviews specifically looking for the tell. Don't do this.

What I'd actually recommend

If you have a real point of view, the writing chops, and twelve months of patience, pursue a Forbes contributor seat through a warm editor intro and your own three-angle pitch. Publish two real pieces a month. In twelve months, LLMs will name you in your category.

If you don't have the time to write but you have the budget, take an ELN seat for $3,000 a year or a Forbes Councils seat at the tier that matches your category. Pair it with two ghostwritten op-eds a year in the editorial section of the tier-1 that matters most for your beat.

If you're early and you have neither, pick one outlet that matters in your category and place one sharp op-ed. That one piece will move your category narrative more than a year of contributor columns nobody reads.

The Forbes credential still works. It just costs more attention now than it used to, and the path that worked in 2019 will get you nowhere in 2026.

If you want a 30-minute teardown of which path fits your stage, your category, and your bandwidth, book a slot with me. I'll come back with a specific recommendation, not a sales pitch.

Web3 Founder Podcast Tour: Book 8-12 Tier-1 Shows in 90 Days

Shilika — Thu, 28 May 2026 17:51:53 +0000

Web3 Founder Podcast Tour: How to Book 8 to 12 Tier-1 Crypto Shows in 90 Days

A Web3 founder podcast tour is a 90-day sequence where you book 8 to 12 crypto-native shows back to back, time the recordings around a single narrative beat (raise, launch, mainnet, product release), and turn each episode into 10 to 15 distributable assets. Done right, it's the highest-conversion thought leadership channel in crypto. Done wrong, you get four "thanks but not a fit" replies and three months of silence.

I've run tours for protocol founders, exchange operators, and AI x crypto teams. The pattern that works is not "spray and pray to 50 shows." It's a tiered list, a one-paragraph pitch tied to a real news beat, and a clip distribution loop that runs the day each episode ships. The operating model is below.

Why a podcast tour beats a press tour for most Web3 founders

A press tour gives you a moment. A reporter publishes once, the post lives 36 hours on the homepage, and if you didn't time the embargo around a fundable beat, the piece dies in the archive.

A podcast tour gives you a library. Each episode is 45 to 90 minutes of you, in your own words, indexed on YouTube and Spotify, clippable for a year. Founders who do 10 shows in a quarter end up with roughly 100 to 150 short-form clips, a dozen long-tail Google results for their name, and a stack of credibility signals that show up every time an investor or journalist Googles them.

The conversion math also runs differently. A Forbes hit moves brand. A 60-minute conversation on a crypto-native show moves pipeline. Investors listen. Partner BD listens. Reporters listen, then DM you because they've now heard you reason out loud and they trust you to be quotable.

The three-tier show list

Don't pitch your dream show first. Build credibility on tier 3, sharpen your reps on tier 2, then go for tier 1 with a clean track record.

Tier 1 (dream tier). The shows with the biggest audiences and the hardest gates. Bankless. Unchained with Laura Shin. Empire (Jason Yanowitz and Santiago Santos). The Chopping Block. The Scoop. Lightspeed for Solana-native stories. These bookers turn down 90% of pitches. You get in when you have a real news hook plus a track record they can verify in three minutes of Googling.

Tier 2 (the working tier). Mid-audience crypto-native shows where serious founders go to think out loud. Examples: vertical-specific shows on DeFi, infra, gaming, and L2s. Regional anchors like Blockcast out of Singapore for APAC reach. VC-hosted shows from funds like Outlier Ventures or LongHash. Web3 Talks, hosted by Mac Budkowski, is one of the long-form options where founders share backstage perspective on their work. These are where you do most of your tour. Bookers respond fast, audiences are qualified, and clips perform.

Tier 3 (the warm-up tier). Newer shows, smaller audiences, but high reply rates and founder-friendly hosts. Shows like Web3 with Sam Kamani sit here, with guests ranging from project founders to leaders at protocols like ENS and Kraken. Tier 3 is where you debug your story. The first three recordings of any tour are calibration runs. You'll hear yourself fumble the same answer twice and finally land it on take three. That sharpening is the entire point.

The mistake founders make is starting at tier 1 cold. You waste your one shot at Bankless on a half-formed narrative. Burn tier 3 first.

The 90-day calendar

The timeline compresses fast. Most founders try to run a tour in 30 days and end up with three confirmations and no clips.

Phase	Weeks	What happens
Pre-tour	Weeks 1–2	Tier list, narrative doc, pitch templates, asset prep
Outreach wave 1	Weeks 3–4	Tier 3 and lower tier 2 pitches, calibration recordings
Outreach wave 2	Weeks 5–7	Tier 2 core pitches, first releases drop
Outreach wave 3	Weeks 8–10	Tier 1 pitches with social proof from waves 1 and 2
Distribution loop	Weeks 4–13	Clip cutting, social syndication, paid amplification on top performers

You will not record 12 episodes in 12 weeks. You'll record 8 to 10 and the others slip. That's fine. Plan for slippage.

The pitch template that lands replies

Most founder pitches fail because they sound like a press release. The opener is the company, the middle is the product, the close is "would love to chat." Bookers see 50 of those a week. They reply to none of them.

A pitch that works has four moves in under 150 words:

One sentence that proves you listen to the show. Reference a specific recent episode and the one idea from it you disagreed with or extended. Not "great episode," the actual idea.
One sentence on the news hook. The fundable beat. A raise closing, a mainnet date, a controversial position you can defend with data, a category call you're ready to make on the record.
Two or three bullets on what you'd argue. Not your bio. The hot takes. The booker's job is to imagine the episode. Make that easy.
Logistics close. Calendly link, ideal recording window, prior episode you've done if any.

What you do not include: a deck, a 400-word bio, a list of awards, "passionate about disrupting." The booker is reading on their phone between meetings.

What makes a real news hook (and what doesn't)

A hook is something a host can lead the episode with. "We just shipped X" is not a hook unless X is genuinely first or controversial. "We raised Y" is a hook only if Y is large, from named funds, or signals a category shift.

Real hooks I've seen land on tier 1:

A category position the founder will defend against the consensus. (Not "DeFi is the future." A specific call like "restaking is over-collateralized theater and here's the math.")
An on-record disagreement with a named competitor or thesis. Hosts love this because it produces clippable conflict.
Original data nobody else has. On-chain analysis, internal product metrics, regional adoption numbers from APAC or LATAM that Western shows can't source.
A mainnet or token launch with a specific date, paired with a thesis about why the timing matters.
A regulatory moment that intersects with your category, where you have a real opinion and are willing to be quoted defending it.

What doesn't work: product walkthroughs, "we hit 100K users," partnership announcements, ecosystem grants. Save those for written press.

The clip distribution loop

This is where most founders leave 80% of the value on the table. You did the recording. The host published. Now what?

The default founder behavior is to retweet the host's announcement once and move on. That's a wasted asset. A 60-minute episode contains roughly 12 to 15 social clips if you cut it properly:

3 to 5 vertical clips for TikTok, Reels, Shorts (45 to 90 seconds each, hook in the first 2 seconds)
2 to 3 horizontal clips for X and LinkedIn (60 to 120 seconds)
1 long pull-quote graphic for static feeds
1 transcript-derived essay for LinkedIn or your blog
1 X thread with 6 to 10 key arguments and timestamps
1 newsletter feature linking the episode

Run this loop on a 10-day cadence after each episode drops. Day 1: episode goes live, you boost the host's post. Day 3: first vertical clip. Day 5: thread. Day 7: second clip. Day 10: long-form recap or essay.

If you have an in-house social team, brief them. If you don't, this is exactly where a fractional PR operator pays for themselves in the first month. The clip cutting alone is 6 to 10 hours per episode if you want it done well.

Common pitfalls

I've seen the same five mistakes kill tours over and over.

Pitching all 12 shows in the same week. You haven't recorded any yet, so you have no social proof. Half your tier 1 targets ghost you. Stagger by wave so you can reference recent episodes in later pitches.

Letting the host frame the narrative. A good host will steer you toward what makes a clippable episode for their audience. That's their job. But if you walk in without your own three or four anchor arguments, you'll come out sounding generic. Pre-write your hot takes. Practice them out loud. Bring them back into the conversation when the host drifts.

Skipping the prep call. Bookers will offer a 15-minute pre-recording with the host or producer. Take it every time. That's where you align on the narrative arc and quietly veto the questions that would put you in a bad position.

Ignoring tier 3 because the audience is small. The audience is not the point on tier 3. The reps are the point. You will fumble your founder story in your first two recordings. Don't fumble it on Bankless.

Treating the recording as the deliverable. The deliverable is the clip library and the second-order coverage. If you don't have a distribution plan before the recording, you don't have a tour. You have a hobby.

Pre-seed vs Series B: how the tour shape changes

The tour you run depends on where you are. Stage changes everything.

Pre-seed and seed. You're building credibility from zero. Skip tier 1 entirely. Run 6 to 8 tier 3 and lower tier 2 shows over 60 days. The goal is a Google footprint and a founder story you've told 8 times so it's tight when investors ask. Hooks are vision-led: category thesis, founder origin, market gap.

Series A. This is the sweet spot for a full 90-day, 10-show tour. You have a raise to anchor the narrative, a product in market, and enough traction to be interesting to mid-tier shows. Tier 1 is reachable in wave 3. Hooks blend raise news with category positioning.

Series B and beyond. You're past the "explain what we do" tour. The tour becomes selective: 4 to 6 tier 1 shows per year, paired with a major beat each time (token, expansion, controversial position). You're using the tour to set agenda inside the industry, not to build awareness.

Token launch teams. Special case. The tour has to compress into the pre-TGE window without violating quiet periods. I usually run 4 to 6 shows in the 6 weeks before launch, plus 2 to 3 in the 4 weeks after. Sequencing matters: the post-launch episodes are where you address community questions and reset expectations.

Manual vs operator-led: what each looks like

You can run this yourself. Founders do, and some of them do it well. The honest comparison is below.

Manual. You build the tier list (a weekend). You write the pitch template (a few hours, multiple revisions). You source booker emails (LinkedIn, episode show notes, a few cold replies). You manage the calendar. You cut the clips or pay someone on Upwork to do it. Expect 15 to 25 hours per week for 12 weeks if you want it run right. Most founders manage 4 to 6 shows in 90 days this way, not 10 to 12.

Operator-led. A fractional PR operator already has the relationships at tier 2 and a quarter of the tier 1 shows. The pitch goes from "cold email" to "warm intro from someone the booker trusts." Reply rates roughly triple. Recording calendar gets managed end to end. Clip cutting either runs in-house or through a vendor the operator manages. Founder time drops to 3 to 5 hours per week, almost all of it on the recordings themselves.

The honest take: if you're early stage and have time more than money, run it yourself and use a fractional only for the tier 1 introductions in wave 3. If you're Series A or later and your time is the bottleneck, the math flips fast. The cost of a fractional retainer is less than the cost of you spending 200 hours managing show bookers instead of running the company.

What success actually looks like at day 90

A successful tour ends with measurable artifacts, not vibes:

8 to 12 episodes published, with at least 2 on tier 1 shows
100 to 150 short-form clips in the library, with the top 10 boosted on paid
A first-page Google result for your name that's all founder podcast content, not random aggregator pages
Inbound from at least one investor and one reporter who heard you on a specific episode
A founder story you can now tell in 90 seconds, in 5 minutes, or in 45 minutes depending on the audience

That last one is the underrated outcome. The reps change you. By episode 8 you've stopped explaining your category and started arguing for it. That voice is what investors and journalists end up quoting for the next two years.

If you want to map out your own 90-day tour against your stage, raise timing, and category positioning, that's what the teardown call is for.

Book a 30-min teardown with Shilika. Bring your tier list and the news beat you're working with. You leave with a real plan.

Tier-1 Crypto Media Outreach: How to Build Web3 Journalist Relationships That Actually Land Coverage

Shilika — Thu, 28 May 2026 15:54:08 +0000

Tier-1 Crypto Media Outreach: How to Build Web3 Journalist Relationships That Actually Land Coverage

The fastest path to a Forbes byline is not a press release. It is six months of operating like the founder the Forbes reporter would want to put on the page. The press release is the last step, not the first.

This is the work that founders skip and PR people fake. The fake version produces one mention in CryptoSlate's news roundup, then nothing. The real version produces compounding coverage where one tier-1 placement lifts the next, the reporter starts emailing you when they need a quote, and your inbound becomes the warm version of what your outbound was a year ago.

I have spent six years running this loop across 50+ Web3 and AI protocols. The pattern is consistent enough that I can describe it as a system.

What "tier-1 crypto media" actually means in 2026

Tier-1 in this category is not just "outlets people have heard of." It is outlets with three properties:

Editorial gatekeeping. A real editor decides what runs. Press releases do not auto-publish.
Beat reporters with longevity. Reporters who have covered the same beat for 18+ months and have opinions about the category, not just access to it.
Traffic that converts. A mention in this outlet drives action: investor inbound, exchange interest, KOL pickup, hiring inbound.

By that definition, the tier-1 list in 2026 is:

Global trade: CoinDesk, Cointelegraph, Decrypt, The Block, Blockworks, The Defiant
Mainstream business: Forbes (Crypto / Innovation desks), Bloomberg Crypto, Fortune Crypto, The Information's crypto desk
Long-form / analytical: Wu Blockchain, Crypto Briefing's research arm, On The Brink podcast
Regional tier-1: BloomingBit and TokenPost (Korea), CryptoTimes JP and Coinpost (Japan), ChainCatcher and PANews (China diaspora), Inc42 (India)

Below this list is what I call "credibility tier-2": outlets that count for SEO and signal, do not count for moving the market. CryptoSlate, BeInCrypto, U.Today, AMBCrypto, CoinGape. Useful for volume, not for narrative.

The mistake most founders make is treating these tiers as a target list. They are not a target list. They are a relationship map.

How to build a relationship with a tier-1 reporter

Six steps, executed over four to six months. None of them are optional.

Step 1: read everything they have written in the last 12 months. Their angle, their stylistic preferences, the specific projects they have covered, the projects they have written critically about, the projects they have written about twice. This work takes 4 to 6 hours per reporter. Skip it and your first email reads like every other founder's first email.

Step 2: comment intelligently on three of their stories over six weeks. Twitter quote posts, LinkedIn comments, replies that add information rather than thank the reporter. The objective is for the reporter to see your name three or four times before you ever email them.

Step 3: send a context email with no ask. Specific reference to their work, a piece of useful intel they probably do not have, no pitch, no calendar link, no CTA. The end of the email is "happy to talk if useful, otherwise glad you are covering this beat." 80% of these emails go unanswered. The 20% that get a reply become real relationships.

Step 4: take the background call. When the reporter agrees to a 20-minute call, do not pitch. Brief them on the category, share your point of view, answer their questions, and leave with no commitment from them. This call is the inflection point. If it goes well, the reporter remembers you the next time they have a story in your category.

Step 5: offer help on stories you are not in. Sources, intros, market data, on-the-record commentary on competitors. Reporters keep a mental list of founders who help with stories. You want to be on that list before you ask for one of your own.

Step 6: pitch when you have actual news. Six months in, when you have a fundable announcement, the pitch is short and lands. "We are announcing X next Tuesday. Want the exclusive?" The answer is much more often "yes" than it would have been at month one.

This is slow. It is also the only model that produces compounding coverage. The fast model, mass press release distribution, produces one news roundup mention and zero relationships.

Web3 journalist relationship management as a system

Treating journalist outreach as a system rather than a campaign:

A CRM column per reporter. Last contact, last story they wrote, beat focus, embargo history, relationship temperature.
A weekly cadence of touches. Five reporters per week. Mix of comments, intel shares, intros, no-ask context emails. Five touches per week is 250 per year, which is enough to maintain real coverage of the tier-1 list.
A monthly review. Which reporters are warming, which are cold, which have moved beats. Reporters move beats more often than founders expect. Catching the move within a week is worth more than the journalist relationship that survived for the previous two years.
A quarterly visibility metric. Number of unique reporters who have written about you. Mentions per cycle. Inbound rate from cold reporters. These are the metrics that matter, not impressions.

This is not glamorous work. It also does not show up in any PR proposal deck. It is the work that separates the fractional senior operators from the agency teams that hand the relationship work to a junior account executive who cycles out of the firm before the relationship matures.

AI startup PR and media relations services: same model, different list

The model transfers cleanly to AI. The list is different.

For AI founders, the tier-1 list in 2026:

AI Magazine
Forbes AI / Tech
The Information's AI desk
TechCrunch's AI vertical
Wired AI coverage
VentureBeat AI
Semafor's tech desk
The Verge's AI reporting
Decrypt's AI coverage (the crypto-AI overlap)

The relationship-building work is identical. The angles are different. Forbes AI wants the founder narrative and the product moat. The Information wants the technical architecture and the investor commentary. AI Magazine wants the deployment customer story. TechCrunch wants the funding number and the differentiation.

I run AI startup PR the same way I run Web3 PR: 6-month relationship build, segmented angles per outlet, embargo coordination on the announcement moment, and a 90-day sustained follow-up cycle.

Content writing services for Web3 and blockchain companies

The content writing question is downstream of the journalist relationship question. The right way to think about it:

Op-eds in tier-1 outlets under the founder's byline. CoinDesk Opinion, Cointelegraph Opinion, Decrypt commentary, Forbes Councils. These are the highest leverage placements per word.
Whitepapers that establish category authority. 8 to 12 pages. Published on your domain with a downloadable PDF. Cited by analysts and reporters when the category comes up.
LinkedIn essays under the founder's voice. Lower bar to publish, higher frequency, builds the personal entity Google associates with your work.
X threads as the canonical short form. One thread per major moment, archived to the blog.

The pattern across all four is that the writing is in the founder's voice, not the agency's. Ghostwriting that smells like ghostwriting is worse than no ghostwriting. The work product I ship looks like the founder wrote it on a slightly more disciplined Sunday afternoon than usual.

Content writing for Web3 and AI founders is structured as three productized offers so the cost is predictable: founder essay package, whitepaper sprint, op-ed of the month. The relationship work in the trade press is what makes the op-eds place. The op-eds are what make the founder citable when AI Overview, Perplexity, or ChatGPT generate answers about the category.

Enterprise blockchain media coverage campaigns

Enterprise blockchain is its own category and the playbook diverges from token-launch coverage. The audience is different: CIOs, procurement, compliance, and the analyst community.

The outlets that matter for enterprise blockchain:

Forbes Innovation
CIO.com
ZDNet
VentureBeat Enterprise
IBM Institute for Business Value's analyst pieces
Gartner research notes
Forrester reports
KuppingerCole's quarterly category reviews

The relationship work is similar but the timeline stretches. Analyst relations in enterprise tech runs on a quarterly briefing cycle. Each briefing is a 30 to 45 minute call covering company update, customer wins, product roadmap, and category outlook. Get on the analyst's briefing list and you are part of the next category report.

The mistake enterprise-blockchain founders make is running the campaign on the consumer-crypto cadence. Forbes Innovation does not run "we raised a Series A" the way Decrypt runs "we raised a Series A." Enterprise outlets run customer wins, category trends, and analyst commentary. Tune the calendar to the audience.

The compound effect over 12 months

The teams that run this loop for a full year see the following pattern in month nine onward:

Inbound reporter requests for quote on category stories outpace outbound pitches
The founder gets invited to be on conference panels they did not apply to
Investor inbound increases at the seed-to-Series A transition because investors saw the founder cited three times in trade press they were already reading
AI assistants start citing the founder's commentary in answers about the category, which feeds the search-engine-versus-AI-answer compounding effect described in the embargo strategy playbook

This is what I mean by compounding coverage. The relationship work in months one through six does not show up in metrics. The compounding shows up in months six through twelve and becomes the moat by month eighteen.

Related playbooks

Web3 PR Embargo Strategy 2026: How to Coordinate Tier-1 Press Without Breaking the Story — how the relationship work converts into clean launch coverage
Web3 Crisis Communications Playbook: From Rug Pull Allegations to Community Trust — what the relationship work is worth when something goes wrong
Founder Profiling & Op-Eds — the productized version of the personal entity build described above

If you want a teardown of your current tier-1 outreach plan and a specific reporter shortlist for your stage and category, the booking link below is the fastest path.

Web3 Crisis Communications Playbook: From Rug Pull Allegations to Community Trust

Shilika — Thu, 28 May 2026 15:51:08 +0000

Web3 Crisis Communications Playbook: From Rug Pull Allegations to Community Trust

A Web3 crisis is different from a traditional corporate crisis. The accusations are public. The escalation curve is faster. The audience writing the next chapter is the same audience that bought the token. You cannot wait for the news cycle to move on, because the news cycle is your community, and they are not moving on.

Most founders facing a first crisis make the same three mistakes. They go silent because legal told them to. They post a generic "we are aware of the situation" tweet that does not address the actual claim. Then they wait two days, hope it dies down, and re-emerge with a long-form explanation when the community has already written its own version of the story.

I have run crisis comms for protocols hit with rug pull allegations, smart contract exploit accusations, insider-trading rumors, regulatory threats, and the standard founder-Twitter implosion. The lessons compound. Here is the operating model.

The first 30 minutes decide the next six months

The community is going to form a narrative about what happened with or without you in the room. The half-life on a Web3 crisis tweet is 90 minutes before it is screenshotted and reposted by 40 unrelated accounts. Once the screenshot circulates, your version of events is competing with the screenshot, not with the original tweet.

In the first 30 minutes you need to do four things:

Acknowledge the existence of the claim. Not the claim's validity. Just that you are aware. "We are aware of [specific claim]. We are gathering facts and will share a substantive update by [specific time]."
Set a deadline for the substantive response. Two hours, four hours, six hours, depending on the complexity. Do not say "soon."
Stop the founder's personal account. Founder posts during a live crisis almost always make it worse. Centralize messaging on the project account. The founder can come back in 24 to 48 hours with the prepared statement.
Open the back channel with the loudest accuser. If a single account is driving the allegation, getting on a DM with that account within the first hour changes the trajectory more than any public statement.

The deadline you set in step 2 is non-negotiable. If you say "an update in four hours" and you ship in five, the community treats the delay as proof you are hiding something. Set deadlines you will hit.

Rug pull allegation reputation management

The rug pull accusation is the highest-frequency crisis in Web3. It usually starts with a single Twitter thread asserting that the team has drained liquidity, that the smart contract has a back door, or that the team is anonymous and uncontactable.

The defense is forensic.

On-chain proof. The first response in the public timeline should be a link to an on-chain explorer showing the actual contract state, the liquidity status, and any time-lock or multi-sig that controls it. Etherscan, Solscan, Polygonscan, depending on the chain. The screenshot of a transaction is more credible than 2,000 words of denial.

Independent verification. Within 24 hours, get an independent on-chain analyst to publicly verify your contract state. Names like ZachXBT, Lookonchain, or Arkham analysts move the needle if they will engage. If they will not engage publicly, a smaller verified analyst is still better than self-attestation.

Founder-on-camera. Within 48 hours, the founder needs to appear on Spaces or on a video call hosted by a respected community voice. Doxxed founders have an easier path. Pseudonymous founders need to demonstrate provenance through other vectors: a previous project, on-chain history, or a co-founder willing to vouch publicly.

Documented process. A timeline of what happened, who knew what when, and what the actual cause of the trigger event was. The timeline must be publishable and verifiable.

The rug pull accusation has a long tail. Even after you survive the first cycle, it will resurface every few months in screenshots passed around new community members. The fix is a permanent landing page on your domain with the forensics, the independent verification, the founder appearance recording, and the timeline. This is the page you link to forever when the accusation re-emerges.

Community trust rebuilding after a Web3 crisis

Surviving the initial 72 hours is not the same as recovering. The community has watched you under stress. They have watched what you said, how fast, and whether you stayed visible. Recovery is a 90-day arc.

The work in those 90 days:

Days 1 to 7: presence. The founder posts daily. Not generic updates. Specific work being done, specific decisions being made, specific people on the team being credited. The community needs to see the team is still operating, not in damage control.

Days 8 to 30: explanation. A long-form post-mortem published on your blog, structured the way Cloudflare or Stripe publish theirs. What happened, why, what you are doing about it, what you have already done. The post-mortem becomes the canonical reference point. Every future question on the topic gets a link to this post.

Days 31 to 60: structural changes. Whatever structural change was implied by the crisis. New multi-sig signers, a treasury audit, a bug bounty program, a new advisor. The structural change needs to be visible and verifiable, not announced and then quietly de-prioritized.

Days 61 to 90: forward narrative. A new story that does not reference the crisis. A roadmap update, a partnership, a product launch. The point is to give the community something to talk about that is not the crisis. This is the moment to also re-engage tier-1 trade press with a positive story.

If you skip any of these steps the community treats the recovery as superficial. The teams I have seen recover well over multiple cycles all run a version of this arc.

Crisis communications management for crypto companies, structured

The internal operating model that prevents crisis collisions:

A pre-written response library. Templates for the 8 most common crisis types in Web3: rug pull allegation, smart contract exploit, insider trading rumor, exchange delisting, regulatory inquiry, founder controversy, treasury concern, partnership collapse. Each template has a 30-minute acknowledgment, a 6-hour substantive response, and a 24-hour follow-up.
A spokesperson rotation. The founder is the primary voice for founder-level crises. The CTO for technical crises. A community lead for community-level disputes. The wrong voice on the wrong crisis is itself a crisis amplifier.
A pre-built monitoring dashboard. Tweetdeck, X advanced search, Telegram bots, Discord webhooks. The team needs to see the volume curve in real time. Most teams discover the crisis 90 minutes late because they are watching the wrong feeds.
A relationship with three tier-1 reporters who will run a quote on short notice. The reporters who covered you under embargo last quarter are the same reporters who will help you get a measured story out during a crisis. The embargo relationships compound into crisis assets.
Legal pre-clearance for the most common phrases. "Cooperating with law enforcement," "no evidence of," "an isolated incident." Pre-cleared phrases save 4 hours per crisis.
A 90-day recovery roadmap template for after the immediate response is done. Without the roadmap, the team drifts back to operations and the trust recovery work never ships.

Most founder teams have one or two of these. The teams that survive multiple crises with their brand intact have all six.

What not to do

Common mistakes I have watched destroy projects in real time:

Going legal-first in public. "We are taking legal action against the accuser." Almost always misread by the community as an admission. Take legal action quietly. Do not announce it.
Promising specific compensation under pressure. Anything you promise in a crisis becomes a commitment you have to deliver, often before you have the structural ability to deliver it. Be vague about remediation in the first 48 hours.
Replying to every accusation individually. A single substantive post that addresses the core claim is stronger than 40 individual replies. Replies amplify.
Letting the founder argue with critics on Twitter. Even if the founder is right. Especially if the founder is right.
Treating the crisis as over because Twitter moved on. It is not over until you have run the 90-day recovery arc.

A note on prevention

The best crisis comms strategy is one you never have to execute. The work that prevents crises is the same work that makes you investable: a clear cap table, a multi-sig that is not founder-controlled, doxxed key roles, an audit cadence, a transparent treasury report, and a community manager who knows how to spot a thread turning bad 8 hours before it explodes.

Prevention is unsexy. It is also why the projects that have stayed off the rug pull lists for three or four years all share the same boring operational hygiene.

When to bring in outside crisis comms

Three signals:

The first response did not land and the community is now writing a worse version of the story than the actual one.
A tier-1 outlet is preparing a story and you do not have a relationship with the reporter.
The founder is emotionally compromised and posting on personal channels.

Any of those three, get external counsel inside 12 hours. The cost of an outside operator for two weeks is a fraction of the cost of letting a recoverable crisis become an unrecoverable one.

Related playbooks

Web3 PR Embargo Strategy 2026: How to Coordinate Tier-1 Press Without Breaking the Story — the relationship work you do before the crisis arrives
Tier-1 Crypto Media Outreach: How to Build Web3 Journalist Relationships That Actually Land Coverage — who you call when the crisis needs a measured story
Cybersecurity PR — the protocol overlap when the crisis is a security incident

If you are watching a thread escalate right now, the booking link below routes to a 30-minute teardown call. Same response sequence, faster than email.

Web3 PR Embargo Strategy 2026: How to Coordinate Tier-1 Press Without Breaking the Story

Shilika — Thu, 28 May 2026 15:51:05 +0000

Web3 PR Embargo Strategy 2026: How to Coordinate Tier-1 Press Without Breaking the Story

A bad embargo costs you the announcement. The good ones compound into the next launch. Here's the operating model I use across the 50+ Web3 protocols I've taken to market.

Most founders treat the embargo as a calendar event. Send the press release at T-72h, ask the journalist to "please hold until Tuesday 9am ET," wait, and hope. It works often enough that the failure mode looks like bad luck. It is not bad luck. It is structural.

The Web3 trade press is small. Forbes, CoinDesk, Cointelegraph, Decrypt, The Block, Blockworks, Bitcoin Magazine, plus the regional outlets in Korea, Japan and India that move price action. The reporters at each of those outlets know each other. When an embargo breaks, every other reporter on the list reads it inside 90 seconds. Your exclusive becomes a race to publish a worse version of the story while the angle you wanted is already poisoned.

I have run hundreds of embargoes in this category. The pattern that compounds is not "send earlier" or "be more polite in the email." It is a small set of operational moves that I'll walk through below.

What an embargo actually is in 2026

The textbook definition is a request to delay publication until a specified time. The operating definition is a small piece of trust you and a reporter share for 24 to 96 hours. Trust is the asset. When it works, you both get a clean story. When it fails, the reporter publishes anyway and the trust transfers to whoever the leaker decides to credit next time.

Embargoes work best when:

The story is genuinely newsworthy on its own. Reporters break embargoes most often when they suspect the embargo exists because the story is weak and the founder is trying to game release timing.
The list of outlets is small (3 to 6 for a Series A or token launch, 6 to 12 for a TGE).
Every outlet has a different angle. Two outlets writing the same story from the same press release will race each other.
You have a relationship with the assigning editor, not just the reporter.

Embargoes fail when you are running an unsegmented blast to 30 outlets, or when an outlet's competitive pressure to scoop a story outweighs the value of preserving a relationship with you specifically.

The 4-stage embargo timeline

Working backward from the announcement moment T:

T-10 days: outreach. Send a tight pre-pitch (3 sentences) to the assigning editor, not the reporter. Ask if they want the story under embargo, and confirm the embargo window. Get a yes before the press kit moves.

T-7 days: press kit and exclusive negotiation. Send the full package only to outlets that opted in. Negotiate angle, not embargo. Each tier-1 reporter gets a slightly different angle: Forbes wants the founder story, CoinDesk wants the protocol metrics, The Block wants the funder names and round structure, Decrypt wants the user impact. The angle differentiation is what makes the embargo hold. No two reporters are writing the same article.

T-72h: confirmation pass. Re-confirm the embargo time with each reporter. Send the exact ISO timestamp in your reply, plus the timezone in plain English. This is the moment to also share the asset bundle: hero image at 2400x1260, logo SVG, founder portrait at 1200x1500, and a one-page fact sheet. Reporters are working on deadlines. The cleaner the assets, the cleaner the story.

T-0: lift. Publish your own announcement on your channels at exactly the embargo lift moment. Many founders forget this and end up with the press telling a story before the project's own social accounts have acknowledged it.

The 10-day arc is for funding rounds. For TGE coordination the arc compresses to 5 days with a tighter list and an exchange-listing dependency layered on. For pre-product narrative launches, the arc can stretch to 14 days with one or two embedded reporters who are writing longer features.

Which journalists actually accept crypto news under embargo

Tier-1 crypto reporters who reliably honor embargoes share three traits: they have a beat (DeFi, infrastructure, gaming, RWA), they have been on the beat for at least 18 months, and they have a relationship with you that predates the current story.

A pre-existing relationship is non-negotiable. The first time you email a tier-1 reporter, asking for an embargo is the wrong opening move. The right opening move is to comment intelligently on three of their recent stories over a six-week window. Then ask for a 20-minute background call with no story attached. Then, eight weeks later, when you have actual news, you can pitch under embargo.

This sounds slow. It is. The compounding effect is that by the time you have placed 12 stories with the same reporter, the embargo is almost automatic and the questions shift from "is this real" to "what angle do you want me to take."

The journalists I work with most often, segmented by category:

Macro / capital / structure: Forbes Crypto, Bloomberg Crypto, The Information's crypto desk, Fortune Crypto
Trade: CoinDesk, Cointelegraph, Decrypt, The Block, Blockworks
DeFi-native: The Defiant, Crypto Briefing, Wu Blockchain
Regional: BloomingBit and TokenPost (Korea), CryptoTimes JP and Coinpost (Japan), ChainCatcher and PANews (Greater China), Inc42 and Economic Times (India), Arabian Business and Cointelegraph Arabic (MENA)

The relationship work matters more than the outlet ranking. A Tier-2 outlet reporter who likes you and has covered you twice will hold an embargo better than a Tier-1 reporter you cold-emailed last week.

How to manage multiple outlet embargoes for a token launch

Token launches break the embargo pattern that works for funding rounds. The reasons are price action, exchange listings, and exchange-listed competitors who pay attention to your news cycle.

The model I use for TGE PR:

Three-wave structure. Wave one is the embargoed announcement to 4 to 6 tier-1 trade outlets. Wave two is the broad distribution to 20 to 30 mid-tier and regional outlets. Wave three is the KOL push starting at T+24h.
Wave one writes the canonical narrative. What the project is, why it matters, what the round was, who led. Tier-1 outlets need a 24-hour head start to publish before the broad wave hits.
Wave two amplifies, does not duplicate. Mid-tier outlets get a package that explicitly references the tier-1 stories. This is the difference between distribution and content collision.
Wave three is for sustained coverage. KOLs and regional voices for the 72 hours after launch. This is where you fight off the natural attention decay curve.

The risk in TGE coordination is the exchange angle. CEX listings often arrive with their own embargo timing that may or may not align with your announcement. If Binance is listing the token at 12:00 UTC and your trade press embargo lifts at 09:00 UTC, the trade press has a 3-hour window where the story is live and the token is not tradeable. That is a footgun. Align the windows.

Another footgun is the simultaneous TGE on multiple exchanges. Listing windows often shift by 30 to 90 minutes between exchanges. Your embargo lift should be tuned to the slowest exchange, not the fastest.

When to lift the embargo on a DeFi protocol announcement

The default is to lift on a Tuesday or Wednesday at 09:00 ET. Mondays underperform because reporters are catching up on the weekend's news. Fridays underperform because the engagement curve dies into the weekend. Tuesday at 09:00 ET is when the US trade press is most active, when European trade press has a full afternoon to amplify, and when APAC has the next morning to localize.

There are three exceptions:

Macro news days. If FOMC is announcing the same day, push to the next available Tuesday. Your news will be drowned out.
Competitor news cycles. If a category competitor is publishing the same week, fight for a slot 48 hours apart. Same-day collisions hurt both sides.
Conference adjacency. If your launch ties to Consensus, Token2049, or ETHDenver, lift the embargo on the second morning of the conference. The first morning is crowded; the second morning has hallway-debrief energy.

Time-zone-wise, lifting at 09:00 ET means:

14:00 UK
22:00 JST
21:30 KST
06:00 PT
21:30 IST

The KST and JST numbers matter for APAC localization runs. The regional press has a 5 to 8 hour window to translate, place, and amplify before US morning starts. That window is the difference between an APAC-bolted-on announcement and an APAC-native one.

What good embargo strategy looks like, written down

A working embargo strategy has six visible artifacts:

An outlet list with reporter names, angles, and relationship history. Not a press release distribution list. A relationship map.
A pre-pitch template that runs three sentences and asks for the embargo conversation rather than asking the reporter to commit to anything.
A confirmation sequence at T-72h that re-states the embargo time as an ISO timestamp and asks for an explicit acknowledgment in writing.
A press kit that bundles hero image, logo, founder portrait, fact sheet, and an FAQ that anticipates the questions the reporter is most likely to ask.
A go / no-go protocol for when one outlet breaks embargo early.
A debrief within seven days that catalogs which outlets held, which broke, what the spread of coverage looked like, and what the sentiment markers were.

Most founder-led teams have one or two of these. The teams that compound coverage over multiple cycles have all six.

What to do when an embargo breaks

It will happen. The question is what you do in the next 30 minutes.

Three moves, in order:

Notify the other outlets immediately. "Outlet X has gone live. Embargo is lifted. Your piece can publish whenever you are ready." This is the move that preserves the relationship with everyone who held. Reporters remember who told them first when the embargo broke.
Publish your own channels. Founder X post, project X post, blog, Discord. Within five minutes of the lift you should own the canonical narrative on your own channels.
Do not retaliate against the outlet that broke. Tempting, especially if you suspect it was deliberate. Wrong move. Every other outlet is watching how you handle it. Going cold on the breaker is the right move; going public about it is not.

The cost of one broken embargo is usually one cycle of coverage. The cost of the wrong post-break response is the next twelve months of coverage.

If you are facing a moment where the embargo break also involves an allegation about your project, the playbook shifts into crisis communications territory. The first 30 minutes are the same. The next 72 hours are not.

Related playbooks

Tier-1 Crypto Media Outreach: How to Build Web3 Journalist Relationships That Actually Land Coverage — the relationship work that makes embargoes hold
Web3 Crisis Communications Playbook: From Rug Pull Allegations to Community Trust — what to run when an embargo break is the smallest of your problems
APAC Localisation & Access — how the embargo window gets retuned for Korean, Japanese, and Indian press

If you are about to run an embargoed announcement and want a second set of eyes on the outlet list and the angle map, the booking link below will get you a 30-minute teardown call.