07 / Outbound · Cold email + LinkedIn, run as a discipline

8% reply rate.
On the channel
everyone gave up on.

Cold email isn’t dead, it’s overrun by tools that ship one bad sequence to ten thousand inboxes. We do the opposite warmed domains, persona-tuned copy, paced cadence, and a human reading every reply. The motion most teams have given up on is open ground for the ones who run it like a discipline.

/01
4-8%
positive reply rate, across the booked motion
/02
<0.5%
bounce + spam rate, held under deliverability ceiling
/03
10-30
SQLs per month, per motion, on your calendar
/04
$2
all-in per lead reached, warmup + copy + cadence + reply
Our premise

Outbound dying is a tooling story, not a channel story. The math hasn’t changed, the operators got lazy. Senders who hold deliverability and write like humans still book the most efficient pipeline in B2B SaaS. We just decided to be that operator.

Most outbound is a broadcast.
Ours is a conversation.
That difference is the entire pitch.

Live · 24-second showreel

Outbound that books meetings.

A signal meter at zero, an inbox of real replies highlighted in lime, then six precision meters showing the metrics that actually run the engine.

showreel.signalLIVE LOOP
The four benches

Four benches. One booked motion.

Deliverability, ICP, copy, replies. Four disciplines that have to stay sharp at the same time, or the motion silently degrades and you don’t notice until pipeline shows up empty in week six.

Four-bench outbound operations room: deliverability lab, ICP, copy, reply desk.
the.bench
  • Bench 01

    Deliverability lab

    We don't burn your primary domain. New domains, SPF/DKIM/DMARC, slow warm-up, rotating inboxes, dedicated IP pools per motion. Inbox-placement testing every week, Gmail, Outlook, Apple, GSuite. The 70% of outbound that nobody wants to talk about, run as a discipline.

  • Bench 02

    ICP atomization

    Generic lists are why open rates die. We segment to persona-by-trigger: Series-B PLG ops leads who hired in the last 30 days. Mid-market RevOps who just bought a competitor. Each cohort gets its own copy, its own send-time, its own reply playbook. Nothing batch-and-blasted.

  • Bench 03

    Copy room

    Senior copywriters draft every variant. Founder-voice, problem-first, no AI smell. A/B variants per persona, ruthlessly tightened. We don't ship a sequence until it reads like a human you'd actually meet. The whole motion lives or dies on the first 18 words, we treat them that way.

  • Bench 04

    Reply desk

    Replies are not handled by a chatbot. A trained human reads every response, qualifies, books, or routes. The interesting ones get to a human at your end inside an hour. The not-yet-readys go on a polite re-engagement track. Reply quality is what compounds, not send volume.

The stack, exposed

Six layers. One clean signal.

Most outbound shops sell you a tool license and call it a stack. A real outbound system is six interlocking layers, and skipping any one is the reason your last sequence quietly stopped working in week three.

Exploded view of an outbound stack: domain pool, inbox rotation, copy variants, multichannel cadence, reply triage, CRM attribution.
stack.exposed● 6 layers
  • /01

    Domain pool

    5-15 secondary domains, never the primary, fully warmed.

  • /02

    Inbox rotation

    20-60 mailboxes per motion, sending capped per inbox.

  • /03

    Persona-tuned copy

    Senior-written, A/B variants, no AI tells, no templates.

  • /04

    Multichannel cadence

    Email + LinkedIn, sequenced, paced for the real funnel.

  • /05

    Reply triage

    Every reply read by a human within the hour, qualified, routed.

  • /06

    Pipeline + attribution

    Live CRM sync, source tagged, meeting → opportunity logged.

Pre-send inspection: a deliverability monitor with green-bar inbox-placement readouts and a copy proof under a loupe.pre-send · 5 checks
The pre-send protocol

Five checks. Zero blast.

Every cohort clears five checks before a single inbox is touched. DNS, list, copy, placement, cadence, if any fail, the send goes back to the bench. We will reschedule a Tuesday morning before we’ll burn your reputation score.

human-signed · per cohort
  1. /01

    Domain & DNS check

    SPF / DKIM / DMARC verified, blacklist scrubbed, reverse-DNS clean before a single send.

  2. /02

    List hygiene

    92%+ verified emails, role-inboxes pulled, unsubscribes honoured across every prior motion.

  3. /03

    Copy review

    Senior editor signs off subject + first 18 words. No spam triggers, no template smell, founder-voice held.

  4. /04

    Inbox-placement audit

    Glockapps + manual seed-test across Gmail, Outlook, Apple, primary-tab placement is the floor.

  5. /05

    Cadence calibration

    Send-times tuned to recipient timezone, daily caps held, follow-ups paced like a human, not a sequence.

How a week shapes up

Five days. One booked cohort.

  1. MON

    List build

    Cohort scoped, ICP triggers re-pulled, list cleaned and verified, persona buckets cut.

  2. TUE

    Copy & test

    Variants drafted in founder voice, peer-reviewed, seed-tested into Gmail / Outlook / Apple.

  3. WED

    Send window 1

    First-touch goes out across rotating inboxes; reply desk warm and ready before 9am ET.

  4. THU

    Reply triage

    Every reply read live, qualified, booked or re-engaged; LinkedIn warm-touches queued for the same cohort.

  5. FRI

    Audit & ramp

    Deliverability scorecard reviewed, copy rewritten on what flopped, list expanded for next week's run.

The deliverability lab at blue hour, a single operator at a quiet console, inbox-placement readouts on a long monitor.
The lab, after hours

Anyone can press send. We hold the signal, through warm-ups, blacklists, inbox-tab gravity, and twelve weeks of reply behaviour.

The work nobody promotes, domain hygiene, inbox-placement audits, reply triage at 7am. The unglamorous 70% that decides whether the glamorous 30% ever gets read.

The numbers we hold

What the motion actually returns.

Six precision signal-strength meters along a horizon, reply rate, bounce, SQLs, verified, response time, domain pool.
  • /01
    4-8%
    positive-reply target across the engaged motion
  • /02
    <0.5%
    bounce + spam ceiling, held weekly, never crossed
  • /03
    10-30
    qualified meetings on your calendar each month per motion
  • /04
    92%+
    verified email rate before a list ever runs
  • /05
    <1h
    median reply-to-touch on every interesting response
  • /06
    5-15
    secondary domains in rotation, primary domain never burned
Deliverables

Every motion, scoped & shipped.

Fixed scope per motion. Everything below, every cohort, with the bench discipline that lets a weekly cadence book SQLs at consulting-grade reply rates instead of cold-blast noise.

  • 01

    Domain + deliverability infrastructure

    Secondary domains, SPF / DKIM / DMARC, warm-up, IP pool, set up and held.

  • 02

    ICP + persona segmentation

    Cohorts cut by trigger event and persona. Copy and cadence tuned per segment.

  • 03

    Senior-written copy + A/B variants

    Founder voice, no AI smell. First-18-words protocol on every variant.

  • 04

    Multichannel cadence build

    Email + LinkedIn sequenced together. Daily caps held, send-times tuned.

  • 05

    Inbox-placement testing

    Weekly Glockapps + manual seed across Gmail / Outlook / Apple, primary-tab is the floor.

  • 06

    Human reply triage

    Every reply read by a human, qualified, booked or routed inside an hour.

  • 07

    Pipeline + CRM attribution

    Live HubSpot / Pipedrive sync, source-tagged, meeting → opportunity logged for the board deck.

The stack

Quiet tools. Loud signal.

A real outbound stack is a deliverability rig + a copy room + a reply desk, wired together so a single operator can hold the signal across thousands of inbox conversations a week without any of them sounding automated.

  • Sending infraInstantly · Smartlead · domain pool · IP rotation
  • Inbox placementGlockapps · MXToolbox · weekly seed-test
  • List + intelApollo · Crunchbase · Clay · trigger feeds
  • LinkedIn layerSales Nav · HeyReach · paced manual touches
  • Reply deskFront · Slack triage · per-thread human review
  • CRM attributionHubSpot / Pipedrive · per-cohort source tag
Questions we get

What buyers ask on the second call.

01

Won't this burn our primary domain?

No, that's the entire reason we run the deliverability lab. We register and warm secondary domains for outbound, with their own SPF / DKIM / DMARC, and rotate sends across 20-60 inboxes. Your primary domain stays untouched, your sales reps' personal domains stay untouched, and your customer-comms inbox-placement stays untouched.
02

Is this AI-generated copy?

No. AI saves us research time and helps with variant generation, but every line that goes out has been read and tightened by a senior copywriter. AI-only outbound has a tell, the cadence reads cold, the openers all sound the same, and reply rates collapse inside three weeks. We treat AI as a research tool, not a writer.
03

What does 4-8% reply rate actually look like?

On a 1,000-lead cohort, 40-80 humans reply to your sequence. ~30% of those are positive, interested, willing to take a call. So 12-25 booked discovery meetings per 1,000 leads reached. Compare to industry-standard 1-2% reply on cold-email-blast tools, and the math gets very clean very quickly.
04

How fast can we start?

Domain warm-up is non-negotiable: 14-21 days from domain purchase to safe send volume. While that runs, we build the list, write the sequence, and stand up the reply desk. Day-21 is realistic first-send. Anyone promising live-by-Friday is burning a domain to do it; you'll pay for that speed in month two.
05

Can you replace our SDR team?

We replace the prospecting + first-touch + reply-triage layer. We hand off qualified meetings to your AEs. If you don't have AEs, we'll route bookings to your founder's calendar instead. The SDR-as-a-bottleneck problem is real; this is the version of outbound that stops being that bottleneck.
A clean inbox at first light, a single high-priority reply at the top, the rest of the day already booked.
Ready when you are

Warm the domain.
Write the sequence.
Book the meeting.

Day 1: domain warm-up begins. Day 7: list cleaned, copy drafted, reply desk staffed. Day 21: first send into Gmail / Outlook / Apple. Every week after, meetings on your calendar and a deliverability scorecard in your inbox.

Common questions

We’re direct about how we work.

Still something missing? Email hello@markingo.io. You’ll hear back within a business day.

  • Somewhere sharper. Think of us as your embedded growth team. You get the senior velocity of a well-run in-house function, without having to hire 9 specialists. We live in your Slack, your Linear, your calendar.

Want a deliverability + copy audit on your current outbound?

Send your sender domain and current cadence. Audit and a written rebuild plan back inside 48 hours.

Work emails only. By submitting you agree to our privacy policy.
Accepting two new partners this quarter

Ready to compound?

A 30-minute intro. No deck. We’ll ask three questions, diagnose the biggest growth lever on your desk, and tell you if we’re the right people to run it.

Average response time · 4 hrs · M-F