PolyAPI’s Cold Outreach Playbook: How to Target Enterprise Buyers Without Inbound Marketing

Every founder building enterprise infrastructure hears the same advice: build a community, create content, wait for inbound leads. Product-led growth is the gospel. Cold outreach is dead. Except when it isn’t.

Darko Vukovic built PolyAPI to $22 million in funding using a strategy that sounds almost quaint in 2024: cold emails and cold calls. Lots of them. In a recent episode of Category Visionaries, Darko Vukovic, CEO and Founder of PolyAPI, walked through the outbound framework that landed enterprise deals when nobody had heard of his company or the category it was creating. This isn’t a story about spray-and-pray outreach or LinkedIn automation. It’s about surgical targeting that turns cold outreach into pattern matching.

The Honest Truth About Early-Stage Outbound

Most founders romanticize their go-to-market strategy in retrospect. Darko doesn’t bother. “We did a lot of cold outreach, a lot of cold emails, a lot of cold calls,” he says flatly. This was the strategy—not a temporary measure until inbound kicked in, not a stopgap while they built their content engine. Cold outreach was how PolyAPI found its first customers and validated its market.

The reason is simple: PolyAPI was building infrastructure for a category that didn’t exist yet. Nobody was searching for “API management platform that deploys on-premise.” Nobody was reading comparison articles or downloading whitepapers. The market didn’t know it needed what PolyAPI was building. Waiting for inbound would have meant waiting forever.

But here’s where most cold outreach strategies fail: they cast wide nets hoping to catch anyone. PolyAPI did the opposite. They built a targeting framework so specific that their “cold” emails were actually warm—because they were reaching people who were already suffering from the exact problem PolyAPI solved.

The Spending Signal Framework

The core of PolyAPI’s targeting strategy wasn’t demographic or firmographic—it was behavioral. Specifically, they looked for one signal: current spending on integration tools. “If you are spending this much money on integration tools, you probably have a very deep integration problem,” Darko explains.

This insight is deceptively simple but operationally powerful. PolyAPI wasn’t prospecting to companies that might need their solution someday. They weren’t targeting companies at a certain size or in a certain industry hoping they had integration pain. They targeted organizations that were provably already trying to solve the problem—and spending money on inadequate solutions.

The targeting criteria were precise: companies with 200-2000 employees who were already paying for integration platforms. This wasn’t arbitrary. Companies below 200 employees rarely have integration problems complex enough to justify PolyAPI’s price point. Companies above 2000 employees typically have established vendor relationships and procurement processes that make new vendor adoption prohibitively slow.

But the real genius was focusing on current spending. A company spending $50,000 annually on integration tools has already acknowledged they have an integration problem. They’ve already gotten budget approved. They’ve already convinced their organization that this problem is worth solving. PolyAPI’s job wasn’t to create problem awareness—it was to prove they had a better solution.

The Hidden Tax Message

Surgical targeting only works if your message resonates with the specific pain point you’re targeting. PolyAPI’s message was brutally direct: you’re already losing money, you just don’t realize how much.

“Companies spend 30 to 40% of their engineering time doing integrations,” Darko explains. “That means if you have 100 engineers, you have 30 to 40 engineers that are just doing integration work.” This wasn’t a pitch about future efficiency gains or theoretical ROI. This was a mirror held up to show prospects a problem they were living with but hadn’t quantified.

The framing transformed the conversation. Instead of selling new infrastructure, PolyAPI was offering to give companies back 30-40% of their engineering capacity. The value proposition became obvious: either keep paying your current integration vendors and losing 40% of your engineering capacity, or switch to PolyAPI and reclaim those resources.

This message worked specifically because of how PolyAPI targeted. A company already spending heavily on integration tools would immediately recognize the pain. They’d already experienced the endless integration projects that consumed engineering sprints. They’d already felt the frustration of systems that wouldn’t talk to each other. PolyAPI’s message didn’t need to convince them they had a problem—it just needed to quantify what that problem was costing them.

Targeting Decision-Makers, Not Users

The other critical element of PolyAPI’s outbound strategy was who they targeted within organizations. “We did a lot of cold outreach, a lot of cold emails, a lot of cold calls” to VP and C-level executives—not to developers or individual contributors.

This decision runs counter to most product-led growth wisdom, which says to target users who will adopt your product bottom-up. But PolyAPI was selling infrastructure that required organizational buy-in, budget approval, and architectural decisions. No individual developer could greenlight an API management platform that would sit in the company’s infrastructure.

By targeting executives, PolyAPI ensured they were talking to people who could make purchasing decisions and who cared about the business impact rather than just technical features. A VP of Engineering immediately understands what it means to reclaim 40% of engineering capacity. An individual developer might love the technical elegance but can’t authorize a six-figure infrastructure purchase.

Why This Still Works in 2024

The conventional wisdom says cold outreach is dead because inboxes are flooded and response rates are plummeting. But PolyAPI’s success suggests the problem isn’t with cold outreach—it’s with bad cold outreach.

When your targeting is precise enough that your “cold” email arrives in the inbox of someone actively experiencing the pain you solve, when your message quantifies a cost they’re already paying, when you’re reaching decision-makers who can actually buy—that’s not spam. That’s relevant communication arriving at exactly the right time.

The difference between PolyAPI’s approach and typical cold outreach is the difference between “spray and pray” and “sniper targeting.” Most cold outreach fails because it’s volume-driven: send 10,000 emails and hope for a 0.5% response rate. PolyAPI’s approach was precision-driven: identify the 100 companies most likely to need your solution right now, and craft messages that speak directly to their proven pain.

The Infrastructure Founder’s Dilemma

PolyAPI’s cold outreach strategy solves a specific problem that infrastructure founders face: how do you sell something when the market doesn’t know it needs what you’re building? Content marketing and inbound work beautifully when people are actively searching for solutions. They fail when you’re creating a new category.

Cold outreach—done right—is how you manufacture your own demand. You identify prospects who have the problem even if they don’t have the solution vocabulary. You reach them directly. You make the problem impossible to ignore. And you do it at scale.

Darko’s framework proves that cold outreach isn’t dead. It’s just that most founders are doing it wrong. Target companies already spending money on adjacent problems. Message the hidden cost they’re already paying. Reach decision-makers who can actually buy. Do that, and cold outreach becomes the fastest path to enterprise deals—no inbound required.