SHILIKA
EST. 2019000

PLAYBOOKAll posts

Crypto Founder Narrative Positioning: How to Pick the One Story That Lands

Most Web3 founders pitch five narratives at once and land none. Here's Shilika's five-part framework for selecting the single story that CoinDesk or The Block will actually run—plus six real teardowns.

Crypto Founder Narrative Positioning: How to Pick the One Story That Lands
On this page11
  1. Why Multiple Narratives Kill Coverage
  2. The Five-Component Narrative Selection Framework
  3. 1. Market Category Ownership
  4. 2. The Contrarian Angle
  5. 3. The Named Comparable
  6. 4. The Founder Credibility Stack
  7. 5. The Proof Layer
  8. The Editorial Test
  9. Three Narratives That Worked (And Why)
  10. Three Narratives That Didn't (And Why)
  11. The Operational Takeaway

Crypto Founder Narrative Positioning: How to Pick the One Story That Lands Tier-1

Most Web3 founders arrive at their first PR push carrying five narratives. There's the category-creation angle, the protocol differentiator, the founder origin story, the market-timing hook, and the "we're the Stripe of DeFi" comparable. All five are real. All five are defensible. And all five will land nothing.

Narrative dilution is the single most common reason technically strong projects get ignored by tier-1 crypto media. Journalists at CoinDesk and The Block aren't searching for the most complete picture of your project. They're scanning for one story they can tell in 600 to 1,000 words that earns a click, survives their editors, and holds up under follow-up questions. If your pitch gives them five competing angles, they'll close the tab and move on to the next email.

This post walks through the five-component narrative selection framework we use with founders, explains the editorial test that predicts whether a story will actually run, and tears down three narratives that worked and three that didn't.

Why Multiple Narratives Kill Coverage

The failure isn't unique to Web3, but the space makes it worse. In crypto, the pace of product development is fast, the jargon is dense, and founders are often building in three directions simultaneously. That gets internalized as "we have a lot of stories to tell." Which is true. But a journalist covering 20 pitches before lunch doesn't have the attention for complexity. They have attention for one clean thing.

The numbers are instructive. A 20 to 30% pitch success rate at tier-1 outlets is considered strong performance by practitioners. Anything above that usually involves paid placements being counted as earned media. At those odds, every narrative slot you waste on a weak or competing angle is a wasted cycle.

Meanwhile, the editorial standards at the publications that matter most are unforgiving. CoinDesk covers topics like funding, regulation, market trends, infrastructure, and opinions, with priority given to stories with broader impact and context. Minor product updates are seldom featured. The Block is research-led and rewards substance: data, structure, balance-sheet reality. It is, in the words of practitioners, "unforgiving of hype." If your pitch arrives with five angles, neither outlet will do the work of choosing one for you.

The outcome is predictable. The pitch gets filed as "too vague" or "too promotional," and the founder concludes that PR doesn't work. PR works. The story selection doesn't.

The Five-Component Narrative Selection Framework

Before a single journalist gets a pitch, a founder should be able to answer five questions. The answers don't become the pitch. They become the filter that lets you identify which single story is worth pitching.

1. Market Category Ownership

What is the name of the problem category you exist inside, and are you defining it or competing inside a definition someone else made first?

Category definition is the highest-leverage narrative play. A protocol that pitches itself as "a better DEX" is competing on features. A protocol that pitches itself as the first infrastructure layer purpose-built for regulated institutional DeFi is naming something journalists don't already have a word for, which makes them more likely to write about it.

The question isn't whether your category claim is accurate. It's whether a journalist at CoinDesk can use your framing in their headline without being contradicted by their own prior coverage. If they can, you've passed the first filter.

2. The Contrarian Angle

What does your existence imply that most of your market believes is false, unnecessary, or impossible?

This is the engine of most stories that actually land. Journalists are trained to find tension. The best pitches don't say "we built a thing." They say "the conventional wisdom on X is wrong, and here's the evidence." The more specifically you can name what the market believes and why you think that's incorrect, the more you give a journalist something to build a story around.

A custody startup that says "most security narratives in DeFi are backwards. The attack surface isn't the protocol, it's the key management layer" has a contrarian angle. A custody startup that says "we offer enterprise-grade security with best-in-class latency" does not. One gives a journalist a hook. The other gives them marketing copy they can't use.

3. The Named Comparable

What is the one well-known project, company, or model that makes your approach immediately legible to a non-expert reader, and what is the single most important way you diverge from it?

Comparables are editorial shorthand. When a journalist can say "think X but built for Y," they can explain you to their readers in one sentence. That sentence is often what makes the difference between a story that gets filed and a story that gets killed in editing because the editor can't follow it.

The comparable doesn't have to be flattering. "We're what Uniswap should have been for institutional liquidity" works because it positions relative to something readers already understand. "We're a next-generation AMM with novel bonding curves" doesn't, because it requires the reader to already know what a bonding curve is.

Use the comparable to orient, not to subordinate. The divergence matters as much as the reference point.

4. The Founder Credibility Stack

Why are you, specifically, and not a generic founding team, the right person to be making this claim right now?

Editors at tier-1 outlets check credibility before engaging with the substance of a pitch. The credibility stack isn't a biography. It's the intersection of prior domain exposure, observable evidence of insight, and the track record that makes your contrarian claim credible rather than wishful.

A founder who spent five years at a prime brokerage, watched institutional clients fail to access on-chain yield due to custody constraints, and built a workaround internally before starting their company has a credibility stack that supports a "regulated institutional DeFi" narrative. A founder who read about the problem and decided to solve it does not, at least not until they've built observable proof.

The credibility stack is also what determines whether a journalist will return to you as a source after the initial story. Publications like CoinDesk and The Block develop ongoing relationships with founders who can explain a niche with clarity under deadline. A single, well-scoped claim of expertise gets you into that rotation. Diffuse positioning keeps you out of it.

5. The Proof Layer

What on-chain data, third-party validation, or independently verifiable metric makes your core claim checkable?

This is where most crypto PR fails. The claim is interesting. The data doesn't exist or isn't shareable. Journalists at serious outlets, and especially The Block, which is research-led and tracks funding rounds and on-chain data in more depth than most, will ask for it. "We're the fastest-growing DeFi protocol" without a verifiable metric is not a pitch for The Block. It's noise.

The proof layer doesn't need to be dramatic. A benchmark, a third-party audit, a disclosed TVL figure, or a partnership term-sheet that's been publicly filed all work. What doesn't work is asking a journalist to take your word for it in a space that has spent three years publishing consequence-of-trust failures.

The Editorial Test

Before pitching, run this question: can a journalist repeat the core of this story to their editor in one sentence, cite one piece of verifiable evidence, and name one reason it's relevant right now?

If you can't answer all three cleanly, the story isn't ready. Not because it isn't true. Because it isn't pitchable.

The timing element is particularly easy to miss. Experienced crypto reporters think in market narratives rather than isolated announcements. Projects that position themselves naturally within developments already unfolding receive more attention because they help journalists explain a larger market movement. The same pitch, timed to land when its theme is already in the editorial conversation, outperforms by a significant margin. A custody infrastructure story carries more weight during a week when a major exchange exploit is driving security coverage than it does in a market dominated by memecoin trading.

Three Narratives That Worked (And Why)

The Compliance-Native Infrastructure Play. A protocol building settlement infrastructure for regulated institutions didn't pitch "we're better than existing settlement rails." They pitched that the U.S. Treasury's tokenization agenda had created a gap between policy intent and execution infrastructure that no existing player was built to fill. They named the specific policy framework that identified the gap. CoinDesk ran it because it had a regulatory hook, verifiable documentation, and a named executive willing to go on record. The pitch was one story, not five.

The Data-Backed Market Counter-Narrative. A DeFi analytics team noticed that conventional coverage was attributing a major drop in protocol TVL to market sentiment. Their on-chain data showed the actual cause was a structural change in liquidity migration patterns that had nothing to do with sentiment. They pitched the data before any competitor had it, framed it as a correction to the dominant narrative, and named two journalists who had covered the original story. Both covered the correction. The story worked because it was contrarian, verifiable, and timely.

The Founder Domain Authority Pitch. An infrastructure founder with a prior background in HFT market-making had a specific view on why current order-flow models in on-chain perpetuals were structurally broken. Rather than pitching their protocol launch, they pitched an op-ed on the mechanics of the structural flaw. The op-ed ran, established the founder as a named expert on that specific topic, and the protocol coverage followed in the next news cycle with built-in editorial credibility. The move was deliberate: they built the credibility stack before asking for the product story.

Three Narratives That Didn't (And Why)

The Everything Protocol. A Layer-1 team with genuine technical differentiation across three dimensions, speed, privacy, and developer tooling, tried to pitch all three simultaneously. The pitch ran to 600 words before reaching the hook. Every journalist who received it responded asking what the company actually did. None covered it. They eventually narrowed to one narrative, privacy infrastructure for institutional data workloads, and coverage followed within two months.

The Unverifiable Superlative. A DeFi protocol claimed the lowest-cost on-chain execution on any EVM chain, but the benchmark wasn't publicly documented or reproducible. The Block passed. CoinDesk passed. One mid-tier outlet ran the claim, attributed to the protocol's own announcement, without validation. The coverage generated no downstream engagement and damaged journalist relationships for future pitches, because the reporters who passed remember who wasted their time.

The Timing Mismatch. A real-world asset tokenization protocol pitched a "digital transformation of global trade finance" narrative during a week dominated by a major exchange hack and subsequent regulatory fallout. The editorial conversation was entirely security and compliance-focused. The story wasn't wrong. It was invisible because it had no point of contact with what journalists were actively covering. Pitching without reading the editorial environment is the fastest way to land in the "review later" pile that never gets reopened.

The Operational Takeaway

Narrative selection is not a marketing exercise. It's a triage exercise. You're not choosing which story is most complete. You're choosing which story is most pitchable right now, to a specific editorial audience, using the proof you currently have.

The five-component framework gives you the filter:

  • Category ownership: Are you naming something new, or competing in someone else's category?
  • Contrarian angle: What does your existence imply that the market currently believes is false?
  • Named comparable: What's the one-sentence orientation for a non-expert reader?
  • Credibility stack: Why you, specifically, and why now?
  • Proof layer: What can a journalist independently verify?

Run every candidate story through all five. The one that answers all five clearly is the story you pitch. The others get held for future cycles, built into a content calendar, or reserved for bylined op-eds where you control the framing. They don't go in the pitch.

One story, pitched well, to the right journalist, at the right moment in the editorial cycle, will outperform five stories scattered across a blast list every time.

All playbooks