Skip to main content
Pipe & Signal

Sending infrastructure

Land outbound in the inbox, not in spam

Gmail requires senders of more than 5,000 messages a day to set up SPF, DKIM and DMARC, and to keep the spam rate below 0.30%. Google advises a spam rate below 0.10%. We set up the domains and inboxes to meet those rules, in your name.

Source: Google Workspace Admin Help, email sender guidelines

Send a scoping brief

Sfrom $3,000 · £2,400

Indicative price. You get a fixed quote after the brief.

Trigger

You start outbound, or replies drop and you suspect deliverability.

How the sending infrastructure workflow runs

  1. 01

    Send

    Domains

    We pick sending domains apart from your main domain. You buy them in your name.

  2. 02

    Send

    DNS

    We set SPF, DKIM and DMARC on each domain and check them.

  3. 03

    Send

    Inboxes

    We create inboxes and start warm-up in your sending tool.

  4. 04

    Report

    Health checks

    A weekly job checks DNS records, bounce rates and spam placement.

Tools

  • Google Workspace or Microsoft 365
  • Instantly or Smartlead
  • Your DNS provider

Data in

  • Your brand name and main domain
  • Your expected send volume

Data out

  • Domains and inboxes in your name
  • Correct DNS records
  • A weekly health report

You own

  • Every domain and inbox
  • The DNS records
  • The health check job

Code or Clay?

Set-up happens in your sending tool and DNS. The health check runs as code.

See the GTM tech stack by layer and Clay vs Claude Code.

Price: size S, from $3,000

Small: One workflow on a stack you already have. One data source, one destination.

From $3,000 · £2,400 as a single build. Indicative price. You get a fixed quote after the brief.

GTM engineering pricing by size

You can buy this workflow alone at size S. It is also part of this larger build:

Seed to Series B B2B SaaS

L

Owned lead machine

All 7 steps, from list to report, built as code in your own repo.

from $12,000£9,600 per build

  • List, enrichment, signals, AI research, routing, sending and reporting.
  • A repo in your GitHub with scheduled jobs and a database.
  • Direct calls to vendor APIs, with no per-row platform fee from us.
  • Tests, a cost log for every run, and a runbook.

Outcome You own a working lead machine and the code that runs it.