Embedded-finance API: reaching CTOs without pitching the API

The situation

The client was a Series B embedded-finance API company. Their product allowed B2B platforms to embed banking, payments, and card-issuing capabilities into their own products. Target buyers: CTOs and VPs of Engineering at platforms that were considering adding financial services to their offering.

Problem: the buying process was long (9–14 months on average), the stakes were high (platforms were taking on significant financial and regulatory risk), and the buyers were sophisticated technical leaders who had strong filters on cold outreach. The client’s existing outbound — SDR-driven, demo-ask CTAs, value-prop emails focused on “reduce time to launch financial features” — wasn’t working. Positive reply rate was running at 0.4%. Most months produced 2–3 meetings.

The revenue team had started pushing for a “switch to LinkedIn DMs” strategy. The CEO, before committing to that, asked a question: “is there a version of outbound that actually works on CTOs?”

The brief was open-ended. Find out.

Why traditional cold email fails on CTOs in this segment

The audit surfaced three things:

1. The email pattern CTOs have already filtered out

CTOs at platforms in the embedded-finance buyer pool get 10–30 vendor emails per week. They’ve been trained by the market to filter on specific patterns:

Subject lines with “quick question” → ignored.
Openers that compliment the company → ignored.
Second paragraphs that say “we help companies like yours launch X faster” → ignored.
CTAs that ask for a demo → ignored.
Any email that could plausibly be from 20 other vendors → ignored.

The existing outbound was hitting every one of these. Not because the SDR was lazy — because that’s what best-practice outbound copy looks like. Best practices become filtering patterns when enough vendors use them.

2. The audience expects substance, not sales motion

CTOs evaluate embedded-finance vendors on technical depth. Can this company actually reason about the risk of BaaS partner banks? Do they understand the Card Association fee structures? Have they seen what happens when an embedded-issuer launch hits operational edge cases at scale?

An SDR cannot credibly convey any of this. A CTO reading a sales email written by someone who couldn’t pass an API design review can tell within 30 seconds. The email gets archived with prejudice.

3. The product isn’t what CTOs are primarily evaluating

Weirdly, CTOs at the buyer companies aren’t usually shopping for “an embedded-finance API.” They’re shopping for answers to specific pre-launch questions: “if we do this ourselves, what do we not know? What have other platforms gotten wrong? How do I evaluate partner banks?” The API is the solution to a later question. The earlier question is: how do we navigate this space responsibly.

Vendors pitching the API too early were talking past the actual decision-making conversation the CTO was having internally.

The rebuild

The new positioning

We reframed cold outbound not as “introduce the product” but as “be useful on the question the CTO is actually asking.”

Concretely: what if every cold email taught the CTO something specific and useful about embedded-finance architecture, operational risk, or partner-bank evaluation — without mentioning the product?

This was a big operational shift. It required:

Actual substantive content. Not blog posts. Technical writing that would pass peer review.
Founder and senior-engineer involvement in the outbound process. Not an SDR operation.
Patience on conversion. The first reply wasn’t “want a demo?” It was “interesting take — can you elaborate?”

Who sent the emails

Two senders, alternating based on segment:

Founder (the CEO, himself ex-eng). Sent to CTOs at platforms with 200–2,000 engineers.
Head of Platform Engineering. Sent to VPs of Engineering and senior architects at the same companies, and to CTOs at smaller platforms (50–200 engineers).

Both senders were technically credible on LinkedIn. Both had published talks or blog posts on embedded-finance architecture. Both had real reputational stakes in what the email said.

What the emails contained

Three recurring patterns, tested and tuned over 2 months:

Pattern A — The specific operational war story

[First name] — quick note on something we saw at [named peer company]
last year that I suspect is relevant to [recipient's company] as you
consider [signal-inferred thing, e.g. rolling out embedded cards].

Short version: they launched embedded issuing with [partner bank X],
and during the first chargeback cycle discovered [specific operational
edge case]. The fix turned out to be [specific architectural choice].
Happy to share the longer writeup if useful.

Not pitching — just saw [signal] and thought you'd want the cautionary
detail in advance.

— [founder name], [founder title]

What’s specific: a named peer, a named partner bank, a named edge case, a named fix. None of this can be mocked up by an SDR who doesn’t understand the space. Every detail is something the CTO could ask a follow-up question about.

Pattern B — The framework

[First name] — we've been thinking about how platforms should evaluate
sponsor banks for embedded BaaS, because I kept seeing the same three
mistakes in companies' RFPs. Short framework here: [link to a 1,200-word
technical writeup by the founder].

If you're in this conversation internally, the mistakes on page 2 are
the expensive ones. Happy to go deeper by reply.

— [founder name]

The writeup is the value. The email is a distribution mechanism for it.

Pattern C — The question

[First name] — genuine question for someone who's been closer to this
than I have: at [recipient's company], when you've evaluated [specific
partner bank category], how do you weight [specific technical tradeoff]?

We've been building tools to help platforms evaluate this tradeoff and
I suspect our default weighting is wrong for your kind of company.

— [founder name]

Pattern C inverts the dynamic — rather than claiming expertise, it asks the CTO’s. Done well, this is flattering without being obsequious, and it often produces a reply because technical leaders want to share their reasoning.

Warning: this pattern collapses if the CTO senses the question is rhetorical. The sender has to actually want the answer. We tested it with senders who had a genuine intellectual interest in the responses.

What we stopped doing

Sending anything that could plausibly come from another vendor. Every email had an irreducible specific.
Asking for meetings as the first CTA. Meeting-asks moved to the third message in a thread, after substantive exchange.
Using any opener that complimented the company. Generic praise is dismissed instantly.
Writing subject lines that tried to manufacture urgency (“quick q”). Substantive subjects performed better.
Volume targeting. We capped at 100 emails per week per sender, with the understanding that 100 thoughtful emails beats 1,000 generic ones in this segment.

The supporting content investment

The biggest cost of this motion wasn’t the outbound. It was the content.

Every Pattern B email linked to a real technical writeup. The founder and head of platform eng committed to publishing one substantive piece every 3 weeks — ~1,200 words, peer-reviewed internally, genuinely useful for someone making architectural decisions.

Content pipeline across the 6 months:

“How to evaluate sponsor banks for embedded BaaS” (1,400 words)
“Chargeback architecture for embedded issuers: the patterns that fail at scale” (1,600 words)
“When to stay off card networks and why direct debit is often better for early launches” (1,200 words)
“Partner-bank lock-in: the contractual levers that matter” (1,300 words)
“Three compliance edge cases we only learned about at $50M in annualized volume” (1,500 words)
“Embedded-finance KPIs the CFO will ask about that you haven’t set up yet” (1,100 words)
“Why most embedded-lending launches miss the 90-day loss reserve problem” (1,400 words)
“Evaluating BaaS APIs: five technical tests we’d run before contract” (1,700 words)

Each piece became ammunition for 6–8 weeks of outbound.

Content was published on the client’s engineering blog under the real author’s name. Not gated. Not behind a form. Available to anyone — including competitors. The bet was that the reputational lift from being the team that published openly on this topic was worth more than any lead-gen value from gating.

The bet held.

Numbers across the 6 months

Sends: ~2,400 total (across 26 weeks, ~90/week average)
Positive reply rate: 8.7%
Meetings booked: 52 (~24% of positive replies turned into meetings — lower conversion than typical outbound but higher average quality)
Meetings that progressed to technical review: 31
Meetings that progressed to commercial discussions: 18
Closed contracts: 6
Combined ACV: $2.1M (larger than pre-engagement average deal size — enterprise contracts averaged $350k+)

The 6 closed contracts came from prospects who had exchanged 4–12 emails with the senders before the first meeting. Most had read at least 2 of the published writeups.

Sales cycle from first email to closed contract: averaged 7 months, ranging from 4 to 11. Not faster than prior SDR motions — actually marginally slower — but the conversion rate at each stage was dramatically higher, which produced the net lift.

What was specific to this engagement

Founder and senior engineer had the technical depth and the writing ability. Both. If either had been missing, this wouldn’t have worked.
The buyer segment rewards technical depth specifically. Other buyer segments (marketing leaders, ops leaders, even some CFOs) don’t respond to this pattern as strongly. CTOs in a regulated, high-stakes space do.
The client could afford the content investment. ~8 hours of senior engineering time per published piece, across 8 pieces, plus outbound writing time. That’s meaningful opportunity cost, and the payoff only arrives on 6–9 month cycles.
Pre-existing technical credibility on LinkedIn. The founder and head of platform eng had real profiles. Starting from zero follower count would have reduced reply rates significantly.

What was generalizable

For any vendor selling into sophisticated technical buyers:

Substance is the cold-email currency. Not tone, not personalization, not urgency. Specific, useful, non-pitchy substance.
Founder- or senior-engineer-signed emails outperform SDR-signed emails by orders of magnitude in technical segments. Not because SDRs are bad — because the rapport is built on reputation that SDRs can’t carry.
Content is outbound infrastructure. If you’re not willing to produce the substantive content that the emails link to, you’re not going to land this motion.
Meeting-asks come on message 3 or 4, not message 1. Technical buyers won’t commit a meeting to someone who hasn’t earned it in writing.
Publish openly. Don’t gate. The reputational signal from ungated quality content is worth more than the lead-gen value from forms.

The honest caveats

The content pipeline was hard to maintain. By month 5, the founder was falling behind on the publishing cadence and one writeup slipped by 10 days. The outbound paused during that gap. Content-dependent outbound has a single point of failure.
The 6 closed contracts count is a slightly cherry-picked number. Two additional prospects had signed LOIs at engagement end but hadn’t yet closed (and I don’t know if they did). And two promising conversations died in legal review due to reasons unrelated to the outbound.
The slow sales cycle was sometimes a problem internally. The revenue team wanted to see faster pipeline movement. The CEO held the line, but in a company with less patient leadership this motion would have been canceled in month 3.
This approach produces fewer raw meetings than traditional outbound. Organizations whose KPIs reward meeting volume will find it uncomfortable.

When this approach is right and when it’s not

Right when:

Buyers are technical leaders (CTOs, VPs Eng, senior architects, CISOs, CPOs in deeply technical products).
Your company has the ability to produce genuinely substantive content.
Your sales cycle is long enough that 6–9 month reply-to-close is acceptable.
Deal sizes are large enough that 6 closed contracts in 6 months is materially meaningful (likely $200k+ ACV).

Wrong when:

Buyers are generalist leaders who value efficiency over depth.
Content production is not feasible.
Short sales cycles demand faster conversion signals.
Deal sizes require volume to hit revenue targets.

The approach is narrow. When it fits, it’s one of the highest-converting motions I’ve seen. When it doesn’t fit, it produces exactly the 8.7% reply rate with none of the closed contracts, because the back-end doesn’t convert on a shorter cycle.

A final note on the unusual nature of this engagement

Most outbound engagements I run are about building a system that doesn’t depend on the founder. This one was the opposite: every design choice was optimizing for leverage on the founder and one senior engineer.

This isn’t a general template. It’s the motion for a specific context — technical buyers, complex product, long cycles, high ACV. But inside that context, it consistently outperforms SDR-driven alternatives because it respects the buyer’s actual filter: show me you know what you’re talking about, or stop emailing me.

The vendors that land in this segment long-term are the ones who take that filter seriously.