Clipper DefenseClipper DefenseDefense Tech Business Development

From zero outbound to 20+ opportunities generated a month

How a lean defense-tech growth accelerator got a map of its market and an outbound engine to work it.

Client since
July 2025
Location
United States
Engagement
Outbound Campaigns
TAM / MAP
Headline result
20+
opportunities generated a month
from zero outbound
Deals
5+
deals closed
sourced from the outbound engine
Service lines
2
new service lines
launched off the pipeline
Starting point
Zero
where we started
no database, no TAM mapping, no outbound
Services
Outbound CampaignsICP TargetingTAM Mapping
01The problem

The situation

Clipper Defense is a federal growth accelerator. It connects VC-backed dual-use and defense-tech startups with COCOMs, PEOs and prime contractors. A small team runs it, and Kevin Ross, the CEO, is the face of every conversation.

Defense is a relationship market with heavy compliance, so new business usually comes from who you already know. Clipper had no outbound motion at all: no database of target companies, no map of the market, and no steady way to reach the founders who needed what Clipper brokers. Each defense niche is also small, so the work is precision, not volume.

Segments, each with its own message
Drones and counter-UAS, including European makersDefense data and cyberRobotics and embodied AIRecent government contract winners
02The build

What we built

A market map, an outbound engine and a reply process, built for a team that does not have time to run them.

01 · Data

A defense-tech market map, from nothing

We built the TAM database from scratch and ranked it against Clipper's ICP, using scraping and enrichment tuned to defense tech instead of a bought list. Then we split it into segments, and each one gets its own message.

02 · Distribution

Outbound that runs every week

Sequences, sending infrastructure and deliverability, built and run for Clipper. We drop segments that do not produce and copy the angles that do.

03 · Automations

Replies triaged and routed

Every positive reply lands in a shared Slack channel with Kevin tagged and a draft answer in the thread. He can approve and send, so nothing sits in an inbox and his time goes to conversations instead of admin.

Output: ICP-fit opportunities on Clipper's calendar, every month.
03Results

The result

The engine now generates 20+ opportunities a month. Pipeline sourced directly from it has closed 5+ deals, and Clipper launched 2 new service lines off that pipeline.

Before
  • No TAM database
  • No outbound motion
  • New business depended on who Clipper already knew
After
  • A defense-tech TAM database mapped to Clipper's ICP
  • 20+ opportunities generated a month
  • 5+ deals closed and 2 new service lines
  1. July 2025

    Engagement starts

    No database, no map of the market and no outbound motion to build on.

  2. The build

    A TAM database, from nothing

    Target accounts and buyers built from scratch with custom scraping and enrichment, then split into segments.

  3. The motion

    20+ opportunities generated a month

    ICP-fit buyers across the defense-tech ecosystem, from an engine that runs on its own.

  4. To date

    5+ deals closed, 2 new service lines

    Pipeline sourced directly from the engine.

  5. What's next

    Wider segments

    Clipper and Astra are looking at larger companies and more European buyers next.

Dude. This is insane. Never thought it would be that successful.
Kevin RossCo-Founder @ Clipper Defense
04Stack

Stack used

What we built and ran
TAM databaseCustom scrapingEnrichmentSequencesDeliverability infrastructureSlack reply routing

Want an engine like this for your market?

We have worked with 150+ teams, been a Clay partner since we started, and been Clay power users for over 4 years.

All case studies →