Cold Email From Your Own Mailbox vs a Shared Warmup Pool

Two tools can both promise to send your cold email and mean opposite things by it. Cold email from your own mailbox means you connect the Google Workspace or Microsoft 365 account you already pay for, and every message leaves under a domain you control. The alternative is rented: the vendor supplies the domains, the inboxes and a shared warmup network, and you use that stack for as long as you keep paying. Both approaches send mail. They fail differently, and the failure usually shows up on the day you try to leave.

We build one of the tools in this category, so read the recommendation with that bias in mind. Renting infrastructure is genuinely the right answer for some teams, and every number here is attributed to whoever published it.

Key takeaways

• Own mailboxes mean you own the asset: the domain, the DNS records, the sending reputation and the reply history. Rented infrastructure means the vendor owns some or all of that.
• A shared warmup pool is a feature, not an ownership model. Pools can help a cold mailbox, and they can also show a healthy score while your real campaign lands in spam.
• The infrastructure math is public: roughly 30 to 50 cold emails a day per warmed inbox, 1 to 3 inboxes per domain, and a reported $200 to $400 a month for 10 inboxes across 3 domains.
• Send caps are a reply-rate decision, not only a safety decision. Reply rates fall sharply as daily volume per mailbox climbs.
• Ask three questions before you sign: whose registrar account holds the domain, who controls the DNS, and what happens to both when you cancel.

What cold email from your own mailbox actually means

The setup has four parts. You register a domain, you create mailboxes on a provider such as Google Workspace, Microsoft 365 or Zoho, you publish SPF, DKIM and DMARC records in that domain's DNS, and you connect the sending tool over SMTP for outbound and IMAP for reading replies. The tool holds credentials. You hold the asset.

Those authentication records are not optional extras. Google's email sender guidelines, which apply to every sender, require SPF or DKIM, a TLS connection, valid forward and reverse DNS for the sending IP, message formatting per RFC 5322, and spam rates below 0.3% in Postmaster Tools.

Ownership also correlates with results. Hunter's State of Cold Email 2026, built on 31 million emails sent by Hunter users in 2025, found a 5.2% reply rate from custom domains against 2.5% from free mail addresses, and 5.9% from Google Workspace against 4.0% from Microsoft 365. If you want the provider comparison in detail, we wrote a separate piece on Google Workspace, Outlook and Zoho for cold email.

The cost of owning the setup is real work: you buy domains, wait out a warmup period, fix DNS when a record is wrong, and replace a mailbox if one gets burned.

What a shared warmup pool is, and what it is not

A warmup pool is a network of mailboxes that email each other on a schedule. They open, reply, mark messages as important and pull them out of spam. The point is to give a cold address a history of engagement before real prospects ever see it.

Warmup itself is supported by data. Sales.co's analysis of more than 2 million cold emails found that properly warmed accounts reached 94% inbox placement by day 21, against 61% for accounts that skipped warmup, and recommends keeping 5 to 10 warmup emails a day running indefinitely.

The argument is about what pool traffic is worth. In the r/coldemail thread "Is Email Warmup BS?" practitioners split three ways: some say that at 3 to 5 emails a day you do not need warmup at all, others say skipping it will burn your domain, and one dissent argues that pools are damaging because "the content of these warmup emails is wildly spammy."

The second problem is measurement. TrulyInbox's review roundup reports that Instantly users see inboxes with healthy warm-up scores while campaigns land in spam, with no diagnostic path or alert when placement breaks. A warmup score describes pool behavior. It does not describe where your cold email is landing.

Our reading: run warmup, treat the score as a weak signal, and confirm placement with seed tests. Warmup timing, ramp schedules and how long a new domain needs are covered in our guide to warming up an email domain.

Who owns the domains? Ask before you sign

This question separates the two models and is rarely answered on a pricing page. Done-for-you infrastructure usually means the vendor registers the domains, configures DNS and creates the mailboxes inside its own account.

TrulyInbox reports that domains bought through Instantly's done-for-you service are retained by Instantly. If that is the arrangement you signed, then months of sending history, a clean reputation and the DNS you tuned all stay behind when you switch tools. You start over on new domains, which means another warmup cycle.

Managed AI SDR products add a second twist: sending is often billed separately from the subscription. 11x's guide to Artisan pricing notes that sending infrastructure is billed on top of the plan, and reviewers there describe credits that do not roll over. On the connection side, a user in an r/sales thread on Artisan and 11x reports that "You can connect only one email account," which caps volume no matter what the plan allows.

Three questions to ask in writing before you pay:

1. Whose registrar account will hold the domains, and can that be mine?
2. Who can change the DNS records, and will I get access?
3. If I cancel, do the domains and mailboxes transfer to me, and at what cost?

The inbox math: how many mailboxes and domains you actually need

Volume per inbox is the number most teams get wrong. The Indie Hackers cold email infrastructure playbook puts the safe ceiling at 30 to 50 cold emails a day per warmed inbox, with 1 to 3 inboxes per domain and 2 to 5 alternate domains, and says flatly that "the send 200/day per inbox advice from 2022 is dead."

Litemail's inbox math guide gives a simple formula: 40 emails per inbox per day, 2 to 3 inboxes per domain, and inboxes needed equals your daily target divided by 40 plus a 20% buffer. A 500 a day target works out to 16 inboxes.

The cost bands published in the Indie Hackers playbook, with the daily ceiling calculated at 40 sends per inbox:

Costs as reported by that playbook in 2026; registrar and mailbox prices move, so price your own providers before you plan. Operator time sits on top of every row. That is the honest cost of owning your sending, and it is also why the rented option exists.

Provider ceilings are much higher than the safe ceiling, which is where people get into trouble. According to MailReach's summary of Google Workspace limits, paid accounts can send 2,000 messages a day and trial accounts 500, with 100 recipients per message through an SMTP client. MailReach still recommends 10 to 30 a day for new mailboxes and 50 to 100 for properly warmed ones.

Why send caps change your reply rate, not just your risk

Caps are sold as protection. The data says they also decide how many replies you get. Sales.co's dataset of more than 2 million cold emails breaks reply rate down by daily sends per mailbox: 2.8% at 20 to 50 sends, 2.5% at 50 to 75, 2.1% at 75 to 100, 1.4% at 100 to 150, 0.8% at 150 to 200 and 0.4% above 200. Mailboxes above 150 a day showed a 43% higher spam rate.

Hunter's 2026 report points the same direction, with 20 to 49 emails a day per account producing the best reply rate at 5.7%. And in the r/coldemail post "I sent 1 million cold emails", the author writes: "We capped sends at 15 per inbox per day on Google Workspace and we never ever went above that. At 15 a day our domains actually lasted nine or ten months."

Owning the mailboxes is what makes those caps yours to set. On a rented pool you inherit whatever policy the vendor runs.

SDRclose rotates up to 12 of your mailboxes per account, enforces daily and hourly caps per mailbox with a minimum gap between sends, runs a progressive warmup ramp, and refuses to cold-send from a mailbox that is still warming. It also monitors each mailbox for SMTP and IMAP connectivity, credential failures and missing or broken SPF, DKIM and DMARC records, and alerts you when something breaks. The deliverability guide covers the settings we recommend, and sequences shows how caps interact with sequence pacing.

When a shared pool or managed infrastructure is the better choice

There are real cases for renting, and pretending otherwise would be dishonest.

• You need to be sending this week. Buying domains, creating mailboxes, publishing DNS and waiting out warmup takes weeks. A managed stack compresses that into an afternoon.
• You do not want to touch DNS. If nobody on the team is comfortable editing records, an outsourced setup removes a category of silent failure.
• You are deliberately using disposable domains. Some senders treat secondary domains as consumable. If a domain is meant to be burned, it is better that it is not yours and not your primary.
• You run many client workspaces. Agencies spinning up and tearing down per-client sending often prefer vendor-managed domains for the operational simplicity.

The compromise most teams land on: own your primary domain and its mailboxes, and use separate secondary domains for volume. Just make sure you know which category each domain is in, and who holds the keys.

What to require from an AI SDR that sends from your own mailbox

If a tool claims to work with your mailboxes, these are the specifics worth confirming before you buy:

1. It connects over standard SMTP and IMAP to the providers you already use, and supports more than one mailbox.
2. It rotates across mailboxes and enforces per-mailbox daily and hourly caps plus a gap between sends.
3. It runs warmup and refuses to send cold mail from a mailbox that has not finished ramping.
4. It reads the inbox often enough to stop a sequence when someone replies.
5. It replies in-thread from the mailbox that sent the original message, so the conversation looks like a conversation.
6. It watches SPF, DKIM and DMARC on your domains and tells you when a record breaks.
7. It supports one-click unsubscribe headers and a permanent do-not-contact list.
8. It supports data export and deletion for the prospect data you put into it.

SDRclose does all eight, and our security page covers how mailbox credentials and data are handled. If you are weighing this against a sending-first platform, the Instantly alternative comparison covers the trade-offs in more detail, and bounce handling is covered in our piece on acceptable cold email bounce rates.

The short version

Rent the infrastructure if speed matters more than ownership, and go in knowing exactly what you are renting. Own the mailboxes if you plan to still be sending in a year: reputation is the one asset in cold email that compounds, and it only compounds on a domain you keep.

If you want to test that with the mailboxes you already have, you can start a free 7-day trial and connect one inbox before you buy a single new domain.