Cold outreach implementation guide for agencies

TL;DR: For an agency running 100 cold email inboxes, Google Workspace Business Starter costs $700-840/month. Inframail's Unlimited Plan at $129/month plus domain costs comes to roughly $196/month on the same basis, and it stays at $129/month in platform fees as inbox count grows. Two constraints decide whether that trade works. New domains need 14 days of warmup before any cold send, and the platform is Microsoft-only, so agencies whose clients require Google Workspace IP reputation are out of scope. Setup runs about 180 seconds per domain, with new domain purchases capped at 5 every 24 hours.

Every professional cold email operation runs on five core assets: sending domains, mailboxes, DNS authentication records (SPF, or Sender Policy Framework, DKIM, or DomainKeys Identified Mail, and DMARC, or Domain-based Message Authentication, Reporting, and Conformance), an inbox warmup tool, and a sending platform. Managing each manually is where most agencies lose the operational hours that should go toward closing new clients.

For a growing agency, DNS configuration is the primary bottleneck. Logging into DNS panels, creating TXT records for SPF, generating and copying DKIM public keys, adding DMARC policy records, waiting for propagation, then testing each domain individually adds up fast. Inframail estimates that configuring 50 domains by hand takes more than 12 hours of focused work, and that time compounds with every new client onboarded.

Deliverability performance: Inframail publishes a 98%+ deliverability rate and a 68.3% blacklist delisting success rate on dedicated US-based IPs built on Microsoft's cloud platform.

Cold email infrastructure costs

Before the first domain is purchased, three numbers decide whether the setup is viable: what infrastructure costs at the agency's real inbox count, what has to be true before sending starts, and how many domains the target send volume actually requires.

Budgeting for faster campaign rollouts

Per-inbox pricing erodes agency margins silently as client count climbs. Google Workspace Business Starter list pricing is $7.00 per user per month on annual billing and $8.40 on monthly billing, so cost scales directly with inbox count. Inframail's flat-rate Unlimited Plan charges $129/month whether an agency runs 50 or 300 inboxes.

Assumptions for the table below: one domain per inbox at $8/year average, which sits inside Inframail's published $5-16 range and is the conservative case. At the 3 inboxes per domain Inframail recommends, domain costs fall to roughly a third of the figures shown. Warmup tools and the $12.41/month monitoring add-on are excluded from both sides.

Inbox count	Google Workspace (annual)	Google Workspace (monthly)	Inframail (platform + domains)	Monthly savings
50 inboxes	$350/mo	$420/mo	~$163/mo	$187-$257/mo
100 inboxes	$700/mo	$840/mo	~$196/mo	$504-$644/mo
200 inboxes	$1,400/mo	$1,680/mo	~$262/mo	$1,138-$1,418/mo

Warmup is a real line item on both sides and belongs in any full comparison. Per-inbox warmup tools run $19-49 per inbox per month, while flat-rate warmup tools cover unlimited inboxes for $29-199/month total, which is dramatically cheaper past a few dozen inboxes. Agencies that already own domains can connect them to Inframail for $5 per domain as a one-time setup fee, which removes the annual domain line entirely.

Annual savings for 50 inboxes run $2,244-$3,084 on the $163/month all-in basis, as Inframail's cost comparison analysis documents.

Mailscale prices in tiers, at $119/month up to 50 accounts and $249/month up to 200, plus $1/month per account beyond a plan limit and domain costs on top. The bill steps up at each tier rather than staying flat, and at 50 accounts Mailscale sits below Inframail's platform fee.

Infraforge charges $4/mailbox/month on annual billing with a 10-slot minimum, and its dedicated IP is a separate $99/month add-on billed quarterly, so matched like for like against Inframail's Unlimited Plan it is already more expensive at its own 10-mailbox minimum. For agencies scaling past 100 domains, Inframail's Agency Pack ($327/month) provides 3 dedicated IPs to distribute sending reputation across multiple ranges.

Pre-launch infrastructure checklist

Before sending the first cold email, confirm every item below is complete.

• Domains purchased through Inframail or connected in from an outside registrar
• SPF record configured and propagated
• DKIM record generated and active
• DMARC record set to v=DMARC1; p=none; minimum
• Inboxes provisioned, with IMAP (Internet Message Access Protocol) and SMTP (Simple Mail Transfer Protocol) credentials exported to CSV
• Warmup tool connected and running for a minimum of 14 days before first send
• CSV imported into a sending platform (Instantly, Smartlead, ReachInbox, Woodpecker, Saleshandy, Salesforge, or any platform supporting custom SMTP and IMAP)
• SPF, DKIM, and DMARC records verified in MXToolbox

Step 1: Prepare domains for cold email

Domains purchased for cold outreach should be separate from the company's primary domain. Using the main domain for cold outreach risks permanent reputation damage if a campaign triggers spam complaints.

How many domains an agency needs

Inframail publishes the sizing formula that turns a daily send target into an inbox and domain count. Each inbox tops out at 50 emails per day, with 40 recommended, split 70% warmup and 30% campaign, which leaves 12 campaign emails per inbox per day. Total inboxes equals daily campaign volume divided by 12, and total domains equals inboxes divided by 3.

An agency sending 2,000 cold emails per day therefore needs approximately 167 inboxes across 56 domains. That volume still fits the Unlimited Plan, which the pricing card rates at 80,000 cold emails per month, and 167 inboxes sits well inside the 300-400 inboxes per dedicated IP the platform supports. Run this calculation before any domain purchase, not after.

Where to buy domains

Domains bought at an outside registrar have to be pointed and configured after purchase. Domains bought through Inframail are configured automatically, and domains an agency already owns can be connected for $5 each as a one-time fee.

New domain purchases through the platform are capped at 5 per 24 hours, and migrated domains at 5 in the first 24 hours then 20 every 24 hours after that. Domain setup itself is unlimited. For a walkthrough of the full domain setup process in under four minutes, the Inframail setup demo video shows purchasing five domains and configuring ten inboxes from start to finish.

Step 2: Secure sending domains with SPF, DKIM, and DMARC

Three DNS authentication records determine whether cold email lands in the inbox or the spam folder: SPF, DKIM, and DMARC. A fourth record, MX, routes incoming mail to the correct server so replies reach the inbox. Inframail configures all four automatically during domain setup.

"The setup is ridiculously fast. SPF, DKIM, DMARC, forwarding - all handled in literally seconds without me having to dig through docs or guess what records to add. Unlimited inboxes on a flat price? That alone saves me hundreds every month compared to Google Workspace or similar." - Verified user review of Inframail

Configuring SPF for domain deliverability

SPF authorizes which mail servers can send on behalf of a domain, published as a TXT record in the format v=spf1 include:[provider] ~all. Without a valid SPF record, receiving mail servers treat the sending IP as unauthorized and route messages to spam. Inframail generates and applies the correct SPF record automatically during domain setup.

Signing outbound mail with DKIM

DKIM signs each message with a cryptographic signature, proving the message was not modified in transit. The signature relies on a key pair, with the public half published as a DNS TXT record so receiving servers can verify it. Inframail handles DKIM key generation and publication automatically as part of domain provisioning, so no key management is required on the agency side.

Setting your DMARC policy for new domains

DMARC tells receiving servers how to handle messages that fail SPF or DKIM checks. For new cold email domains, start with v=DMARC1; p=none; which monitors failures without rejecting messages and satisfies the mailbox providers that require a valid published policy. After 30+ days of clean sending history, tightening to p=quarantine adds a layer of protection against spoofing. Moving directly to p=reject on a new domain blocks legitimate emails before sender reputation is established.

The SPF, DKIM, and DMARC setup video shows the automated configuration completing in 2 minutes. A second walkthrough covering cold email SPF and DKIM setup runs the same process across 10+ inboxes.

Avoiding common DNS setup errors

Manual DNS entry is the source of most silent deliverability failures.

• Duplicate SPF records (two v=spf1 TXT records on the same domain) produce a permanent error, so neither record validates.
• Typos in DKIM keys break signature verification entirely.
• A DMARC policy set to p=reject on a new domain with no established reputation blocks legitimate emails before the domain builds sender history.

Inframail's automated configuration eliminates all three failure points.

DNS propagation and validation

Propagation time is governed by the TTL, or Time to Live, on each record, and commonly runs up to 48 hours. Inframail takes a domain from purchase to ready-to-send inboxes in approximately 180 seconds, which starts the propagation clock immediately rather than after a manual configuration session.

MXToolbox provides free lookups to verify SPF, DKIM, and DMARC records are active and correctly formatted before any warmup begins. Run a check on every new domain after setup. A passing result on all three records confirms the domain is ready for inbox provisioning.

Dedicated IPs versus shared pools

Shared and rotating IP models carry a specific risk. Maildoso, for example, rotates campaigns across changing IPs rather than assigning a dedicated one. Any pooled or rotating IP model means a sender's reputation depends partly on the other senders sharing that space.

Dedicated IPs work differently, and the agency's own sending behavior is the only factor that determines ESP (email service provider) trust. Inframail's Unlimited Plan includes 1 dedicated US-based IP and the Agency Pack includes 3, both built on Microsoft's cloud platform under an enterprise partnership announced in January 2024.

Step 3: Bulk create and link mailboxes

With domains authenticated, the next step is provisioning inboxes on them and getting the credentials into a sending platform. The complete cold email infrastructure setup playbook covers scaling this workflow across larger domain counts.

Automating Microsoft 365 inbox setup

Inframail automates Microsoft 365 inbox creation under dedicated IP addresses. Because the platform is built on Microsoft's cloud infrastructure with an enterprise partnership, agencies get the credibility of Microsoft-based sending without the per-seat costs or manual provisioning work. Each inbox provisions with IMAP and SMTP credentials generated automatically. For a full demo of creating unlimited inboxes instantly, the Inframail 3.5 demo video shows the complete bulk creation and Instantly integration workflow.

Optimal inbox density for cold outreach

Keep inbox density to 3-5 inboxes per domain. The platform allows up to 10, but density above 5 concentrates more of the agency's sending on a single domain reputation.

Reputation problems tend to affect the whole domain rather than a single inbox. If one inbox on a domain gets flagged for spam, every other inbox on that domain suffers. At 3-5 inboxes per domain, one flagged inbox pulls the domain's reputation down for 2-4 others rather than the 9 a fully packed domain would expose.

Export credentials for platform integration

Inframail generates the CSV from the Update tab. Select the target platform and the file downloads pre-formatted for it, containing SMTP settings, sender names, passwords, and email addresses for every inbox in one file. No Microsoft admin access is needed at any point, since Inframail manages the underlying tenant.

The Inframail to Smartlead integration guide covers the exact CSV import process in detail. Inframail mailboxes are also compatible with Instantly, Apollo, and other sending platforms that support custom SMTP and IMAP settings.

Step 4: Warm up inboxes before the first send

Skipping warmup is the most common cause of domain blacklisting. The warmup period builds sender reputation with ESPs like Gmail, Outlook, and Yahoo before any cold outreach begins. The Inframail inbox warmup guide covers the full process after migration or initial provisioning.

How long to warm up new domains

New domains need 14 days of warmup only, with no campaign sending during that window. Domains that were already warmed before migrating to Inframail can reduce warmup to 7 days, which matters for agencies moving live campaigns rather than starting fresh.

Daily sending limits for new inboxes

Warmup volume rises by a 1 email increase per day rather than in weekly jumps. After the initial 14 days, run 80% warmup and 20% campaign email for the first 2-3 weeks, then shift to 20% warmup and 80% campaign permanently.

Hold every inbox to the 40 emails per day the platform recommends, against a hard ceiling of 50. Volume above that should come from additional inboxes across additional domains, not from pushing existing inboxes harder.

Step 5: Sync infrastructure with the sending platform

This step covers importing provisioned inboxes into a sending platform, running pre-launch deliverability checks, and configuring send schedules for healthy ramp-up.

Connecting your sending accounts

Import the CSV file exported from Inframail into Smartlead, Instantly, ReachInbox, or the agency's preferred sending platform. SMTP and IMAP settings connect using the credentials in the CSV. The Inframail setup tutorial video shows the full integration from CSV export to connected account in a single walkthrough.

Running pre-launch deliverability checks

MXToolbox and a test send check two different things. MXToolbox confirms the SPF, DKIM, and DMARC records exist and parse correctly, which is the check to run right after domain setup. A test send through a tool like Mail-Tester checks how a real message behaves, which is the check to run after warmup and before the first campaign.

Note that a high test score confirms technical record configuration but does not guarantee inbox placement, since sender reputation, domain age, and ESP-specific filtering also affect where messages land. Any alignment failure at this stage is faster to fix before a campaign starts than after it generates spam complaints.

Spacing sends across the day

Configure sending schedules in the outreach tool to distribute emails evenly across business hours rather than in bulk windows. Sending 50 emails in 3 hours looks like a spam burst to receiving systems, which weigh consistency of volume heavily when forming sender reputation. The same 50 emails sent across 8 hours with randomized intervals reads as normal human sending behavior. The cold email infrastructure monitoring guide covers ongoing health checks and alerts once campaigns are live.

Timeline from domain setup to live sending

The phases below map the full setup sequence from day one to first live campaign, with milestones at each stage.

Day 1-2: Purchase domains through Inframail. SPF, DKIM, and DMARC records configure automatically, and each domain reaches ready-to-send inboxes in roughly 180 seconds. Remember the cap of 5 new domain purchases every 24 hours when planning a large batch. For agencies migrating from Maildoso, the Maildoso to Inframail migration guide covers the transfer process without disrupting active campaigns.

Day 3-7: Provision inboxes in bulk, export the CSV, and connect warmup tools immediately. Begin warmup as soon as inboxes are provisioned. While inboxes warm passively, the agency focuses on lead list building and copywriting.

Week 2-3: The passive warming phase requires no daily management beyond monitoring inbox placement rates in the warmup tool. This window is the right time to finalize campaign sequences, verify lead list quality, and prepare sending platform settings.

Week 3+: After 14 days of warmup, start campaign sending at 20% of each inbox's daily volume, holding 80% warmup, then shift toward the 20% warmup and 80% campaign split over the following 2-3 weeks. The bulletproof B2B cold email infrastructure guide covers the go-live phase, and a full cold email infrastructure walkthrough covers volume scaling after it.

"InfraMail makes it remarkably easy to purchase domains, configure them correctly, create inboxes, and initiate warm-up immediately. The level of automation is exceptional and clearly designed for serious operators; it removes friction and allows you to focus on execution rather than setup." - Verified user review of Inframail

Common infrastructure scaling mistakes

Rushing domain warmup: Sending full campaign volume on day 3 with no warmup history is the most common cause of permanent domain blacklisting. Receiving systems weigh the ratio of sent mail to spam complaints, and mailbox providers publish a 0.3% spam rate threshold that applies to every sender. A new domain that suddenly sends 100 cold emails presents exactly the kind of volume fluctuation that damages a forming reputation.

Incorrect DNS record configuration: Duplicate SPF records, DKIM key typos, and missing DMARC records all produce silent deliverability failures, covered in Step 2. The email sends, the tool shows it as delivered, but it lands in spam on the receiving end. The spam deliverability fix tutorial covers the technical debugging process when DNS errors cause these problems.

Early deliverability burnout: Sending 100+ emails per inbox per day pushes well above the 40 per inbox per day the platform recommends and the hard ceiling of 50. Volume above that ceiling should come from additional inboxes across additional domains, not from pushing existing inboxes harder.

Preventing silent deliverability drops

Inframail's blacklist monitoring add-on ($12.41/month) tracks domain and IP health continuously. When a domain is flagged, the recovery workflow is:

1. Identify the flagged domain in the Inframail dashboard.
2. Pause active campaigns on that domain immediately.
3. Inframail auto-submits delisting requests to major blacklists, at a 68.3% success rate.
4. Resume campaigns at reduced volume (10-15 emails per inbox per day) once delisting confirms.

For Microsoft-specific blacklist issues, the Microsoft blacklist removal guide covers the direct delisting process with Microsoft's postmaster team. The complete blacklist monitoring guide details how to check and remove IPs from major blacklists. The ultimate cold email infrastructure guide covers ongoing deliverability management for agencies running high-volume outbound, and a sending cold emails that inbox video covers the campaign side of the same problem.

Next steps

The sequence is fixed: size the inbox count from the daily send target, buy and authenticate domains, provision inboxes, warm for 14 days, then connect a sending platform. The parts an agency controls are the sizing math at the front and the discipline to hold sending volume at 40 per inbox per day once campaigns are live. Everything between those two points is automated configuration.

The economics only matter at the agency's real scale, so run the numbers at the inbox count actually needed rather than at the headline tier. Sign up to Inframail and run a 10-domain pilot on the Unlimited Plan ($129/month) to validate deliverability before committing full infrastructure. For hands-off onboarding, the Done-For-You setup service ($3,497 one-time or $499/month) includes account setup, free warmup, a dedicated cold email coach, an automated sending platform, and the first batch of 10,000 leads.

FAQs

Can you speed up new inbox warmup cycles?

New domains need a minimum of 14 days of warming to build a baseline sender reputation before any cold outreach begins. The one documented exception is migration, where domains that were already warmed on a previous provider can reduce warmup to 7 days.

Why does DNS propagation take longer on some domains?

Propagation depends on the TTL (Time to Live) value set on each record and on the registrar. Inframail's automated DNS configuration completes record setup as part of the 180-second domain provisioning process, which starts the propagation clock in one session rather than spreading manual work across hours.

When are your domains ready for outreach?

Domains are ready when they have warmed for a minimum of 14 days, hold an 80%+ inbox placement rate in warmup tool reports, and pass SPF, DKIM, and DMARC checks in MXToolbox. Inframail treats 80-100% inbox placement as the band that is ready to send campaigns, and 60-80% as a signal to continue warmup or reduce volume.

How do you migrate active campaigns without disrupting delivery?

Keep existing inboxes running while warming new Inframail inboxes, using the 7-day path if the domains were already warmed on the previous provider. Once new inboxes pass warmup checks, shift sending volume gradually to the new infrastructure and close old accounts only after confirming stable delivery rates. Migrated domains configure at up to 20 per 24 hours after the first day. The Maildoso to Inframail migration guide and the Mailreef to Inframail migration guide both document the parallel migration approach in detail.

Is Microsoft-only infrastructure a problem if some clients prefer Google?

Microsoft-only is a real constraint for agencies whose clients specifically require Google Workspace IP reputation. For high-volume cold outreach where deliverability and cost predictability matter more than native Google IPs, Inframail's flat-rate dedicated Microsoft infrastructure saves $1,138-$1,418/month at 200 inboxes compared to Google Workspace on the platform-plus-domains basis used above.

What happens if a domain gets blacklisted mid-campaign?

The monitoring add-on alerts when a domain is flagged. Pause campaigns on that domain immediately, and Inframail's automated system submits delisting requests at a 68.3% success rate. Resume at lower volume (10-15 emails per inbox per day) for the first week post-delisting to protect the recovery.

Key terms glossary

SPF (Sender Policy Framework): A DNS TXT record that lists which mail servers are authorized to send email on behalf of a domain, defined in RFC 7208. Missing or incorrect SPF causes messages to land in spam.

DKIM (DomainKeys Identified Mail): A cryptographic signature added to outbound emails that proves the message was not altered in transit, defined in RFC 6376. Requires a public key published in DNS.

DMARC (Domain-based Message Authentication, Reporting, and Conformance): A DNS TXT record instructing receiving servers how to handle messages that fail SPF or DKIM, defined in RFC 7489. Start at p=none for new domains.

Dedicated IP: An IP address used exclusively by one sender. Reputation is determined entirely by that sender's behavior, with no risk from other users on the same range.

Shared IP pool: An IP range used by multiple senders simultaneously. One sender's spam behavior can affect deliverability for all others on the same range.

Inbox placement rate: The percentage of sent emails that land in the recipient's inbox rather than spam or promotions folders. Inframail treats 80-100% as ready to send.

Flat-rate pricing: A fixed monthly fee regardless of inbox count. Inframail's Unlimited Plan charges $129/month for unlimited inboxes, meaning infrastructure costs do not scale linearly as client count grows.

DNS propagation: The time it takes for DNS record changes to spread across global name servers, governed by the TTL value on each record.

IMAP (Internet Message Access Protocol): A protocol that allows email clients to access and manage messages stored on a mail server. Required for sending platforms to monitor replies and inbox activity.

SMTP (Simple Mail Transfer Protocol): The protocol used to send outbound email from a client to a mail server or between mail servers. SMTP credentials are required to connect cold email platforms to sending inboxes.

ESP (Email Service Provider): A platform that delivers, receives, and filters email messages. Major ESPs include Gmail, Outlook, Yahoo, and other inbox providers that enforce spam filters and sender reputation rules.