The ninety-day outbound sprint

We build your outbound engine. You keep it.

For sales-led B2B companies past €1M a year, with contracts above €15,000.

Your buyers can be local businesses or tech companies.
Three weeks to first send. Ninety days to a working engine, and every asset stays in your name.

Size my marketThirty minutes. We count your market live, whether or not we work together.
Your outbound engine Running
Step 0101 · Set the right target

Define your exact buyers. Stop spending money on bad accounts.

01The Outbound Breakdown

Cold email fails for six clear reasons.

Each one wastes budget on its own. Together they burn the market.

Tool A TAM: 12,000 Accounts
Tool B TAM: 4,000 Accounts
Variance: 3x
01

A market you never counted

Your addressable market is a guess from one filter in one tool. Ask two tools the same question and the answers differ by three times.

Scraped_List_v1.csv180 days old
0 Intent Signals
02

Old lists, no signal

A scraped list, months old, with no reason to contact this company this week. A merge tag is not a reason.

Primary DomainInvoices & Billing
BouncesCritical
03

Your domain pays

No separate sending setup, no warmup, no bounce watch. Six months later your invoices start landing in spam.

SDR Schedule Today
Manual List Cleaning6 hrs
Active Conversations0 hrs
04

Sellers not selling

You hired someone to be in conversations. They build lists instead. Your most expensive hour does your cheapest work.

5 Subscriptions • 0 Systems
05

Tools, not systems

Each tool is excellent alone and none of them talk to each other. Five subscriptions later you do not have a machine, you have five.

Market Burn
06

Send more, learn nothing

Nobody can say which segment answered, to which message, at what cost. So the only lever left is volume, and the market burns.

02The Difference

You own the engine. That is the difference.

Comparison
Hire an SDR
dealbound
A tool or AI SDR
Another agency
Build it internally
Built in your name, from week one

Yours, but they build it by hand

Yes

Another login, another subscription

Runs on their domains, not yours

Yours, if you have the team

Fixes the data, not just the sending

They inherit whatever list exists

Yes

One layer of it

Campaigns, not plumbing

A six to twelve month project

A reason behind every touch

Depends who you hired

Yes

Volume, at speed

Varies by account manager

You design it yourself

Systems plus human judgment

Human, no system

Yes

System, no human

Varies by team

You build both

What you pay before anything works

Salary, benefits, a ramp

A build fee, then only meetings that happen

A subscription

A retainer from day one

Salaries and tools

What is left at the end

It leaves when they do

A working engine and the playbook behind it

Rented, it stops when you stop paying

The pipeline stops with the contract

Yours, if it ships

dealbound
  • Built in your name, from week one

    Yes

  • Fixes the data, not just the sending

    Yes

  • A reason behind every touch

    Yes

  • Systems plus human judgment

    Yes

  • What you pay before anything works

    A build fee, then only meetings that happen

  • What is left at the end

    A working engine and the playbook behind it

Hire an SDR
  • Built in your name, from week one

    Yours, but they build it by hand

  • Fixes the data, not just the sending

    They inherit whatever list exists

  • A reason behind every touch

    Depends who you hired

  • Systems plus human judgment

    Human, no system

  • What you pay before anything works

    Salary, benefits, a ramp

  • What is left at the end

    It leaves when they do

A tool or AI SDR
  • Built in your name, from week one

    Another login, another subscription

  • Fixes the data, not just the sending

    One layer of it

  • A reason behind every touch

    Volume, at speed

  • Systems plus human judgment

    System, no human

  • What you pay before anything works

    A subscription

  • What is left at the end

    Rented, it stops when you stop paying

Another agency
  • Built in your name, from week one

    Runs on their domains, not yours

  • Fixes the data, not just the sending

    Campaigns, not plumbing

  • A reason behind every touch

    Varies by account manager

  • Systems plus human judgment

    Varies by team

  • What you pay before anything works

    A retainer from day one

  • What is left at the end

    The pipeline stops with the contract

Build it internally
  • Built in your name, from week one

    Yours, if you have the team

  • Fixes the data, not just the sending

    A six to twelve month project

  • A reason behind every touch

    You design it yourself

  • Systems plus human judgment

    You build both

  • What you pay before anything works

    Salaries and tools

  • What is left at the end

    Yours, if it ships

03Outbound Architecture

How the engine is built

Clean data, a reason to write, deliverable sending, and replies routed straight to you.

Built in weeks one to three
TAM sizing
Sales NavigatorApollo
ICP matrix
Clay
Sending infrastructure
Instantly
01Signals
01 · Signals

Signal detection

Find the accounts that just moved. Hiring, funding, a new market, or a stack change.

ApifySerper.devTheirStackRB2BOctoparse
02Sourcing
02 · Sourcing

Sourcing accounts and contacts

Accounts matching the ICP, then the people who matter: decision-maker, champion, and user.

Sales NavigatorApolloOcean.ioStore LeadsAI ArkJungler
03Data
03 · Data

Data waterfall

Find the address, verify it, and decide what happens when there is none. Four providers run in cascade. Catch-all domains are handled separately. No valid email routes to LinkedIn.

ColdIQProspeoHunterFullEnrichNeverBouncePython
04Scoring
04 · Scoring

Scoring and tiering

Not every account deserves the same effort. The score sets the channel mix and research depth.

Tier A · High intent

Email + LinkedIn + manual research per account

Tier B · Signal-based

Email + LinkedIn

Tier C · Firmographic fit

LinkedIn, then email

Claude CodeClayFibbler
05Message
05 · Message

Message

A reason this account, this week. The frame stays fixed while one angle changes.

The frame

Subject
Four words, lowercase, no pitch
Open
A reason this account, this week
Body
Their problem in their words, and what changes
Ask
One easy next step

No deck, no calendar link, no “quick chat?”

One variable changes every two weeks

Problem-ledOffer-ledValue-ledTrigger-led
06Send
06 · Send

Send and route replies

Sequences run across email and LinkedIn. Every reply lands in your inbox, is logged in your CRM, and pings your Slack.

InstantlyLemlistHeyReachHubSpotAttioSlack
07Call prep
07 · Call prep

Sales enrichment and call prep

Before your seller takes the call, the account arrives with context: the company, the trigger, the people, and their words. Your team starts on the second question.

ClayOcean.ioHubSpotAttio
08The loop
08 · The loop

The loop

Your calls get recorded. What buyers said comes back as verbatim and rewrites the targeting and message. Every two weeks.

Fathomtl;dvFireflies
04Onboarding

Three weeks to first send.
Ninety days to a working engine.

01Week 1

Strategy

You end the week knowing exactly who to sell to and what to say to them.

  • Count the addressable market
  • Set the ICP and the buying persona
  • Sharpen the offer and pick the angles
02Weeks 2 to 3

Build

Everything is built before anything sends. You see the list and the messages before they go out.

  • Domains and inboxes opened in your name
  • Account list built and verified
  • Sequences written and approved by you
03From week 4

Live

Sequences run, replies come straight to you, and the message changes based on what actually answered.

  • Campaigns live across email and LinkedIn
  • Every reply routed to your inbox
  • New variant tested every two weeks
04Day 90

Yours

You know which segment answered, to which message, at what cost. And the engine stays with you.

  • Full performance report by segment
  • Every domain, list and sequence handed over
  • Keep it in house, or we keep running it

Keep everything. Every inbox, domain, list and playbook is yours from week one.

Size my market Thirty minutes to find out if your market can carry this.
05Scaling

Build the core. Then multiply the pipeline.

Build the core engine during the three-week sprint. Once the first sequences are running, we layer on the next channel.

Sprint phase

Outbound Engine

Data waterfalls, Claude messaging, domain rotation, and Slack alerts.

Active Baseline
Scaling lever 01

LinkedIn Content

Turn founder posts and warm engagement into outbound target lists.

Higher velocity
Scaling lever 02

LinkedIn Ads

Warm up accounts with native ads prior to direct outreach.

Warmer outreach
The Market Read

We count your market before either of us commits.

Thirty minutes at kickoff, on your ICP, with the counts on screen.

Not an estimate emailed afterwards.

We cross-check two independent sources, because classification systems disagree on the same company and a single filter is always wrong.

We do not guarantee meetings. Anyone who does without looking at your market is selling you volume. If your market cannot carry the engagement, we say so before you sign.
Size my marketThirty minutes. You leave with a number, signed or not.
07The Operator

Who runs this

Four years selling outbound. Two on tech companies, two on local operators. Quota hit every year.

The first version was spray and pray. A bought database, sequences with merge tags, sent to everyone. We spent more time building lists than talking to buyers. It did not work, and it took a while to see that effort was never the problem.

The second was better. Two markets opened from zero, the UK and Canada, run from France, on almost pure outbound. 103% of target. But the stack was still five tools that did not talk to each other, and the results came from working harder rather than from a system that held on its own.

dealbound is the third version. Strategy first, then infrastructure, then AI where it actually removes work instead of adding a subscription. Built by someone who carried a quota, so the systems are designed for closed-won revenue, not for activity.

The full record is on LinkedIn
08Before you book

We screen every engagement against this list

If the left column is you, book the call. If the right column is you, we would tell you on the call anyway.

Best fit

  • Past €1M a year, sales-led
  • Contracts above €15,000
  • A proven offer in your home market
  • Someone who can take a meeting and close
  • Your buyers are local operators or tech companies

Not a fit

  • Self-serve or product-led
  • Contracts under €15,000
  • Pre-product-market fit
  • Nobody free to take the meetings
  • Anyone who wants a meeting number quoted upfront

The founder selling alone counts. What disqualifies is nobody being available, not the team being small.

09The Model

How you pay

Two lines

  • A build fee at signature.

    Your market counted, the ICP set, infrastructure opened in your name, messaging built and tested.

  • Then per qualified meeting held.

    Not per email sent. Not per reply. Not per no-show.

  • No retainer for ninety days.

    After that, keep the engine or we keep running it, month to month.

  • Tools at cost, in your name.

    No margin on the stack. The accounts are yours from week one.

What counts as a qualified meeting

  • The account matches the ICP set at kickoff.
  • The person matches the persona.
  • They have a real problem in scope.
  • They accept a commercial conversation.
  • They show up.
Founding pricing, first three clients. Numbers on the call.
The call

Thirty minutes. We count your market on the call.

On your ICP, with the counts on screen. If your market cannot carry the engagement, we say so there and then. You leave with a number either way.

Size my market
Thirty-minute market readCal.com
Size my market