Partner tier
Pipedrive Platinum Partner
Work delivered
150+ implementations, 100+ clients
Global rank
Top 8 partner worldwide, July 2026

Products

Sending at volume without wrecking your domain

If you have run outbound before, you already know the failure mode. Everything works for three weeks, then the reply rate collapses and nobody can say why. Here is what is actually happening, and where the honest ceiling on volume sits.

Spec sheet
Warm up
4 to 8 weeksOn a fresh domain. There is no shortcut.
Required records
SPF, DKIM, DMARCAll three, live, before the first send.
Sending domain
Separate from mainNever the domain your contracts travel on.
Verdict
Volume is not the leverList quality decides the outcome. Volume only scales it.

Start with the arithmetic

Let us be blunt about the numbers, because the plan usually breaks here rather than in the copy. Take a realistic reply rate of two percent and a meeting rate of a third of those replies. To book twenty meetings you need roughly three thousand well targeted contacts. Not three thousand names. Three thousand people who plausibly have the problem.

That single calculation kills most outbound plans on the whiteboard, and it should. If you cannot assemble three thousand qualified contacts, the answer is not to send the same message to nine thousand unqualified ones. That is how you burn a domain and a market at the same time.

Warm up is a reputation you build, not a setting you enable

A new domain has no history with the mailbox providers. To them it is indistinguishable from a domain registered this morning to send phishing. So you build history: small volumes, consistent daily, gradually rising over four to eight weeks.

What matters more than the ramp curve is what happens to the messages. Replies and opens are positive signals. Spam complaints and hard bounces are negative ones, and they are weighted far more heavily. This is why warming a domain by sending to a list you have not verified is worse than not warming at all. You are teaching the receiver exactly the wrong thing about you.

Use a separate sending domain, related to your brand but not the one carrying invoices, contracts and support replies. When something goes wrong, and eventually something does, you want the blast radius contained.

The three records, and the one everyone skips

SPF lists the servers allowed to send for your domain. DKIM signs each message so tampering is detectable. DMARC tells receivers what to do when either check fails, and it is the one that gets left on none because publishing a real policy feels risky.

Publish it anyway, start at none to collect reports, read those reports, then move to quarantine. Since the large providers tightened bulk sender requirements, a missing DMARC record is not a minor gap. It is a filter you are choosing to fail. If any of this is unfamiliar territory, the email sync guide covers how mail and the CRM fit together before you add volume to the picture.

Honest limits

Here is the part vendor pages leave out. Volume has a ceiling and it is lower than the pricing pages suggest. Past a few hundred messages per mailbox per day you are no longer sending email, you are operating infrastructure: multiple mailboxes, rotation, per domain monitoring, per campaign suppression.

Second limit: personalisation does not survive scale linearly. A merge field with a first name is not personalisation, and recipients learned to read that years ago. Genuine relevance costs research minutes per contact, which is exactly the thing volume is trying to avoid. The workable middle is tight segmentation, so one genuinely specific message serves a hundred similar companies.

Third limit: outbound does not fix a positioning problem. If the offer is unclear, more sending produces more silence and a worse domain reputation. Fix the message on twenty contacts before you build the machine for three thousand.

The half everyone forgets: what happens when they reply

Sending is the easy half. The expensive failure is a positive reply landing in a shared inbox on a Friday and being answered on Tuesday. Speed of response beats almost every other variable in outbound, and it is entirely under your control.

So build the intake before the outbound. Every reply needs a record in the CRM, an owner and a response deadline. That is exactly what lead routing and SLA design are for, and the lead inbox is where cold contacts belong until they qualify. Cold contacts do not belong in the pipeline, because they wreck every conversion number you own.

The same applies to the traffic your campaigns push to the website. Surge Forms exists so a submission writes straight into the CRM with the fields validated, complete enough to be assigned by rule. Surge Chat covers the visitor who has a question the form does not ask, and creates the record with the conversation attached. Both close the same gap: a reply with no record is a lead you paid for and then lost.

When you should not do this

Below a few hundred emails a month, do not build any of this. Send from your own mailbox. Your deliverability will be better than any platform can give you, and the messages will be more personal because writing them individually forces that.

Do not start if nobody owns the replies. A campaign without a named responder generates annoyance and nothing else. And do not start if your list is bought rather than built. The bounce rate alone will cost you the domain, and in several EU markets the legal exposure is real.

Last thought, from experience rather than theory. The teams that win at outbound are almost never the ones sending the most. They are the ones with the tightest definition of who they are talking to, and the fastest response when somebody answers. The sending tool only multiplies whatever those two things already are.

Questions

Next step

Not sure whether your setup is ready for this?

Ten questions about process, data, ownership and reporting. You get a readiness score on screen, and the written advice by email.

Built by a Pipedrive Platinum Partner, rated 5.0 from 6 marketplace reviews.