ai
How a Cold Pitch With No Reply Turned Into 250K Views 30 Days Later
A no-reply cold pitch to Fast Company turned into a founder quote, 250K+ views on X, and a follow from Garry Tan 30 days later.
Key results: 1 cold pitch · 30 days later · 250K+ views on x · 1 garry tan follow
"A cold pitch does not need an immediate reply to work. Sometimes it just needs to put you on the right reporter's radar before the story breaks."
— Elvis Sun, founder of Medialyst
The Result
One cold pitch with no reply turned into a Fast Company feature, 250K+ views on X, a follow from Garry Tan, and a warmer relationship with Mark Sullivan for the next story.
Read the Fast Company article →
The Spark
In early March, my essay on building an AI agent swarm crossed 5M views on X. That gave me a simple PR angle: the essay already had proof of demand, so now I needed the right journalists before the conversation moved on.
I built a Medialyst workflow table of reporters covering AI, developer tools, and startup culture, then sent a cold pitch to 10 journalists including Mark Sullivan at Fast Company.
The hook was straightforward:
- the essay had already crossed millions of views,
- the topic sat at the intersection of AI agents and software engineering,
- and there were multiple editorial angles depending on where the debate went next.
Mark did not reply.
That usually looks like the end of the story. It was not.
The Timing Shift
About 30 days later, the AI coding debate exploded. Garry Tan's vibe-coded site was getting audited in public. Developers were arguing about whether AI-assisted software development was legitimate. The exact topic I had pitched earlier was suddenly live.
Because Mark had already seen my name and the angle once, I was not a stranger when he needed a founder and developer perspective for the story.
That is the part most people miss. A cold pitch can create familiarity even when it does not create an immediate reply.
The Quote And The Distribution
When Mark reached out, I gave him a clear point of view: the backlash was not really about code quality. It was about traditional developers reacting to a new workflow that compresses iteration speed.
He used the quote, and the article went live the same day.
Instead of posting a generic "honored to be featured" follow-up, I turned the coverage into a sharper public stance on X and let the debate compound.
That post reached 250K+ views, generated 194 replies, and kept the Fast Company story circulating far beyond the initial publication window.
The Outcome
The distribution loop did not stop at pageviews. Garry Tan followed me after the post took off, Mark said he would be in touch, and another tier-1 AI reporter followed as well.
What started as a no-reply cold pitch became:
- press coverage,
- social reach,
- proof of relevance with people who matter,
- and a stronger starting point for the next story.
The Lesson
Most founders treat media coverage like a trophy. They post the link once, say thanks, and move on. That throws away most of the upside.
The better sequence is:
- Earn journalist attention before the topic peaks.
- Be useful when the story becomes urgent.
- Turn the placement into a stronger public point of view.
- Let the debate create the second wave of distribution.
I wrote more about that compounding dynamic in The Game of Attention. The article is the credibility layer. The real leverage comes from how you frame it afterward.
Want The Same Workflow?
If you want to build journalist lists before a story gets crowded, start with Medialyst.