New Cold email reply rates, counted per email and per person, with the denominator shown. Read the benchmarks

to move, Enter to open, Esc to close

How we work · Sending

Sending infrastructure that is ready before the first email.

Updated 18 October 2026

  • Never your main domain
  • In your own accounts
  • Volume and warm-up set in writing

Book 30 minutes with Nouman

Sending setup

Illustration of the work, not client work and not a result.

Sending setup · in your accounts

Set up before the first send.

  • A separate secondary domainNever your main domain
  • SPF, DKIM and DMARCAuthenticated before the first send
  • Warm-upA gradual ramp, not a switch
  • Sending volumeSet in writing
  • AccountsThe domains and inboxes are yours

Why sending setup decides what happens next

  • Cause 01

    Reputation is shared

    Everything sent from a domain builds one reputation. Cold outreach from the main domain puts proposals and customer email at risk with it.

  • Cause 02

    New domains look like spam

    A new domain with no history and sudden volume looks like spam because it usually is. History has to be built gradually.

  • Cause 03

    Problems arrive quietly

    By the time replies stop, a domain may already be damaged. Placement has to be checked before that, every week.

The setup, mapped

Your main domain Where customers, invoices and proposals live. Never used for cold email.
  • Domain oneWarming up
    Volume rises slowly over weeks.
  • Domain twoSending
    At the volume written down in advance.
  • Domain threeResting
    Placement slipped, so it rests. Retired if it does not recover.

An illustration of the setup, not a record of any real one.

How sending is set up

Five parts, each one written into the engagement before any message goes out. The longer explanation, with the provider rules behind it, is in the domains and warm-up guide.

  1. 01

    Separate secondary domains

    Cold email carries more risk of spam complaints than ordinary mail, so it never goes out from your main domain. Close variations of your brand keep any damage away from the domain your customers and invoices depend on.

  2. 02

    Authenticated before the first send

    SPF, DKIM and DMARC on every domain, with the From domain aligned to what is signed. We check the result before any campaign message is sent.

  3. 03

    Real inboxes, spread out

    A few inboxes per domain, named after real people on your team, each with a signature and a working reply path. Sending is spread across them instead of pushing one hard.

  4. 04

    Warmed up gradually

    Each new inbox starts with a little mail to people likely to reply, and volume rises slowly. If replies drop or test messages land in spam, we hold or cut back.

  5. 05

    Volume set in writing

    The volume for each inbox and each domain is written down before sending starts, and you can see it. We watch placement every week and rest any domain that starts to slip.

What is yours

Domains and inboxes
Registered and set up in your own accounts, so they stay yours if we stop working together.
Lists and messaging
Everything we build for the campaign is yours from day one, with a written handover at the end.
Approval
You approve every message before it goes out.
Reporting
Every result is reported as “X from Y”, including the misses. See how we report.

The terms are on the page: ownership and handover, §5 and sending and domain practice, §6.

Questions

Will you send from our main domain?

No. Sending runs from separate secondary domains, never your primary domain. This is written into our engagement terms.

Whose accounts are the domains and inboxes in?

Yours. Everything is built in your own accounts and on your own domains, so nothing is lost if you leave.

How do you decide how much to send?

Sending volume and warm-up practice are set in writing for each engagement, before sending starts.

What happens when a domain starts landing in spam?

We check placement every week. A domain that slips is rested, and if it does not recover it is retired. That is the purpose of using secondary domains.