Launch Comms Embargo Pitch + Media Servicing

Infrastructure Launch: Embargo & Media Strategy

Client and spokesperson names have been removed per NDA. The pitch copy, strategy, and workflow are unchanged from the original.

This sample is from a product launch I ran for a stablecoin infrastructure startup. The company, founded by veterans of Coinbase, Square, and Airbnb, had just closed a $12.5M Series A and was launching a regulated API layer that lets fintechs move money on stablecoin rails without becoming payments companies themselves.

The product was deeply technical: money transmitter licensing, custody infrastructure, KYB/AML compliance. And the launch landed during one of the worst weeks of the year for competing for attention. Policy news and market volatility were dominating every reporter's inbox. Infrastructure stories were getting ignored.

Result: A feature story in American Banker and coverage in CoinTelegraph.

The Embargo Pitch

Below is the pitch as sent, with client details removed.

Subject: Embargo: Ex-Coinbase, Square execs launch fintech stablecoin rails for real payments

Hi [Name],

Stablecoins are everywhere in headlines right now. Visa is scaling stablecoin settlement, SWIFT is planning to orchestrate tokenized transactions across chains and traditional systems, and the Senate is deep in debate over yields.

However, even with regulation in place, most companies still can't use stablecoins in production.

Moving stablecoins means navigating state-by-state money transmitter licenses in the U.S., EMI and CASP authorizations in Europe, plus custody infrastructure, KYB/AML systems, and banking relationships. It's a 12-24 month regulatory and operational lift that most product teams aren't equipped to take on.

That's a gap that veterans of Coinbase, Square, and Airbnb are about to plug.

[Company] (fresh off a $12.5M Series A led by [Lead Investor]) is launching a regulated stablecoin infrastructure layer that lets fintechs and enterprises move money on stablecoin rails via API, without becoming payments companies themselves.

Interested in more information under embargo? Happy to connect you with [CEO] or [Lead Investor CIO] for a deeper conversation.

Media Servicing: How I Closed Two Reporters in a Bad News Week

The pitch got interest from several outlets. But interest and intent to cover are different things, especially during a week when every reporter had three other stories competing for their attention. I triaged responses and identified two reporters showing real intent: one at American Banker and one at CoinTelegraph. I deprioritized the rest and focused on closing these two.

American Banker

Same-day call, same-day quotes

The American Banker reporter came back with specific product questions: who the platform was designed for (banks, fintechs, or both), and how to categorize the company. I drafted written responses in the CEO's voice and sent them over immediately.

Then the reporter wanted the CEO on the phone, and wanted it that evening. The founder was deep in launch prep and my colleague was offline. I coordinated directly with the CEO over Telegram, got him on the call within the hour, and stayed in contact with both sides throughout.

After the call, the reporter needed additional written quotes and context for the feature. I drafted those in the CEO's voice, got his sign-off, and turned them around same day.

"The infrastructure problem isn't going to be solved by another wallet or another on-ramp. Every fintech that wants to move stablecoins today has to go build the same compliance stack from scratch: state-by-state MTLs, custody, KYB, banking relationships. That's an 18-month project before you move a single dollar. We've done that buildout before at [previous company]. We built [Company] so nobody else has to do it again."

Drafted for CEO, approved and submitted to American Banker

CoinTelegraph

Pushing the embargo to close the story

The CoinTelegraph reporter was interested but not committed. He sent a detailed list of technical questions and said coverage would depend on the answers. The questions were dense: licensing structure, what was live vs. coming soon, customer metrics, and the company's positioning around programmable money vs. stablecoin payments.

I got the questions to the CEO immediately and had his written responses back within two hours. But the timing was tight: the embargo was set for the next morning at 8 AM, and the reporter hadn't committed. I made the call to negotiate with the client to push the embargo back by one day. That gave the reporter room to review the answers, pitch the story to his editor, and confirm coverage, which he did the next morning.

When a second set of questions came in from a European reporter on the same team, I coordinated those responses and turned them around within a few hours.

Q: You've positioned [Company] around programmable money rather than just stablecoin payments. In practical terms, what becomes programmable in your model?

"When we say 'programmable money,' we mean that money movement itself becomes software-native. Teams can program when money moves, where it goes, how it's governed, and what happens after it settles. Stablecoins make this possible because they're digital dollars built on programmable infrastructure. That lets money behave like modern software: composable, automatable, and consistent across borders. [Company] abstracts the crypto complexity and delivers this as a familiar, enterprise-grade financial platform."

Q: Which parts of money movement should be programmable by software teams, and which parts still need to remain tightly controlled?

"The right way to think about this is separation of concerns. Software teams should be able to program payment logic, workflows, treasury behavior, and integrations. What shouldn't be reinvented by each team are custody, compliance, licensing, risk controls, and settlement. Those need to remain tightly managed and centralized. [Company] provides that regulated foundation so teams can focus on building business logic, not financial infrastructure."

Written responses drafted and coordinated for CEO, submitted to CoinTelegraph

What Made This Work

This was a story that, on paper, probably shouldn't have landed that week. The product was technical, the launch was one of dozens, and every reporter in fintech and crypto was busy. Four things made the difference:

The pitch reframed the product as the answer to a problem reporters already knew existed. They'd been writing about stablecoin adoption for months. The pitch gave them the "but here's what's actually missing" angle.
I triaged fast and committed. When it became clear only two outlets were going to cover, I stopped spreading effort across the full list and made sure those two reporters had zero friction between interest and published story.
I moved at the reporter's speed, not the client's. When American Banker wanted a call that evening, it happened within the hour. When CoinTelegraph needed more time, I negotiated moving the embargo back a day to give the reporter room to commit. Every set of written responses was turned around same day.
I handled the technical depth. This wasn't a consumer product with a simple narrative. The reporters were asking about money transmitter licensing structures, custody models, and programmable money infrastructure. I had to coordinate and in some cases draft responses that were technically accurate and quotable for a financial services audience.

Both reporters filed on time. The key wasn't just the pitch. It was recognizing which outlets were real, making fast calls on embargo timing, and doing whatever the reporters needed to get across the finish line.