Cold outreach onboarding checklist for agencies

TL;DR: Onboarding a cold email client runs in three stages: setup across days 1 to 7 (domain purchase, automated DNS configuration, inbox provisioning), warmup across days 8 to 21, and campaign launch from day 22. Two constraints set that timeline: Inframail caps new domain purchases at 5 per 24 hours, and new domains always complete a full 14-day warmup. Size the infrastructure from campaign volume rather than inbox count, at 12 campaign emails per inbox per day and 3 inboxes per domain. Infrastructure runs $163/month all-in for 50 inboxes ($129 platform plus roughly $34 in amortized domains) against $350 to $420 on Google Workspace.

Most agency founders focus on reply rates while the real margin killer compounds in the background. Per-seat Google Workspace bills scale linearly with every new inbox provisioned, and manual DNS configuration burns hours that should go toward closing new clients. This cold outreach onboarding checklist gives you a repeatable, step-by-step workflow to take a client from signed contract to live campaign, while keeping infrastructure costs flat and deliverability protected from day one.

How onboarding friction erodes your net profit

Agency onboarding introduces hidden costs that erode net margins before the first campaign sends. This section covers the time and cost variables that compound during client setup, from manual DNS configuration to per-seat billing that scales linearly with every new inbox.

The hourly cost of manual provisioning

Setting up 50 cold email domains manually means logging into each DNS panel individually, creating SPF (Sender Policy Framework), DKIM (DomainKeys Identified Mail), and DMARC (Domain-based Message Authentication, Reporting and Conformance) records for every domain, and waiting for propagation before warmup can begin. Inframail estimates the process takes 12 or more hours of active configuration work for 50 domains. No independent benchmark for manual DNS setup time at this scale exists, so treat the figure as a vendor estimate rather than a neutral one. The Inframail setup walkthrough demonstrates the contrast: automated provisioning that compresses the manual panel work from hours into minutes.

The monthly cost of per-seat pricing

Per-seat pricing creates a cost structure that works against agency growth. Google Workspace Business Starter charges $7.00 per user per month on the annual plan and $8.40 on flexible billing as of August 2026, so every new inbox adds directly to the infrastructure bill.

Both columns below show platform fees only. Domains and warmup are separate on every platform and are handled further down.

Table 1: Monthly platform fees by inbox count (domains and warmup excluded)

Inbox count	Google Workspace (annual)	Google Workspace (flexible)	Inframail (flat-rate)
50 inboxes	$350/mo	$420/mo	$129/mo
100 inboxes	$700/mo	$840/mo	$129/mo
200 inboxes	$1,400/mo	$1,680/mo	$129/mo

Inframail's flat $129/month plan covers unlimited inboxes regardless of count. At 200 inboxes on flexible billing, that is $1,680/month against $129/month, a difference of $1,551/month on platform fees alone.

Adding domains gives the all-in figure. At 50 inboxes provisioned one domain per inbox, domains amortize to roughly $34/month, putting total infrastructure at $163/month against $350 to $420 on Google Workspace. That one-domain-per-inbox basis is deliberately conservative, since Inframail recommends 3 to 5 inboxes per domain, which would cut the domain line considerably. For a line-item breakdown across seven platforms, the infrastructure cost comparison guide includes editable inputs to model your exact agency scale, and the B2B infrastructure ranking review offers additional context on the provider set.

Maildoso, a common alternative in this category, prices per mailbox on three published monthly tiers: 30 mailboxes at $75, 300 at $225, and 1,000 at $499 as of August 2026. No tier exists between 30 and 300, so a 50-mailbox agency pays the 300-mailbox rate or scales down to 30. Maildoso also rotates sending IPs rather than assigning dedicated ones, which is a different reputation model from the dedicated IPs covered below.

The migration risk when switching mid-campaign

Slow infrastructure onboarding delays results delivery, which creates client anxiety early in the retainer. Switching infrastructure mid-campaign carries real risks worth understanding before committing. Warmup scores and sender reputation built on a previous platform do not transfer, because migrated domains arrive on new infrastructure with no sending history and need a fresh warmup.

The practical approach is to set up new Inframail domains two weeks before cutting over, run warmup in parallel, and shift volume gradually while keeping the old infrastructure active. Inframail's migration guide covers this process for existing infrastructure users.

Pre-launch: contract to infrastructure kickoff

Before domains are purchased or DNS records configured, map client requirements and establish a timeline that protects the warmup clock. This section walks through each phase of the pre-launch workflow, from intake to infrastructure activation.

Table 2: Launch timeline

Phase	Timeline	Key tasks	Deliverables
Phase 1: Setup	Days 1-7	Purchase domains (5 per 24 hours maximum), auto-configure DNS, provision inboxes, verify propagation	DNS records live, platform-formatted CSV exported
Phase 2: Warmup	Days 8-21	Connect inboxes to the sending platform, run warmup at a 1 email per day increment, monitor placement	Warmup complete, placement monitoring active
Phase 3: Launch	Day 22+	Set campaign limits (12 per inbox per day), confirm tracking domains, get client sign-off	First campaign live, monitoring active

Collecting client requirements before setup

Before purchasing a single domain, collect the client's brand name, target ICP (Ideal Customer Profile), approved sending personas, and daily volume targets. Use a standardized intake form that captures the daily campaign volume, the campaign start date, and the firmographic filters for the lead list. This prevents mid-setup change requests that delay the warmup clock.

Size the infrastructure from campaign volume, not from a guessed inbox count. Inframail's sending capacity formula divides daily campaign volume by 12 to get total inboxes, then divides inboxes by 3 to get total domains. A client targeting 1,000 daily campaign sends needs 84 inboxes across 28 domains. At the 5-domains-per-24-hours purchase cap, acquiring those 28 domains takes 6 days, which is why domain purchasing starts on day 1.

Standardizing your domain naming scheme

Never use a client's primary domain for cold outreach. M3AAWG guidance is to assign a separate domain or subdomain for each sending purpose, reserving the main domain for corporate communication, and receivers may require that different mail streams be separated. Purchase alternative domains using naming patterns like get[brand].com, try[brand].com, or [brand]hq.com.

Name sending inboxes after real people (firstname@getbrandco.com) to match the approved sending personas captured at intake, rather than generic prefixes like info@ or contact@. Generic prefixes route to shared mailboxes that no named person owns, which undercuts the one-to-one framing cold outreach depends on.

Choosing between dedicated and shared IPs

Shared IP pools work like carpool lanes where your reputation is shaped by every other driver on the same range. Spamhaus escalates serious listings to extended ranges of a network, or to an entire network related by ASN, so one bad actor can pull neighbors down with them. Worse, removal requests for a listed IP must be sent by the internet service provider that controls it, not by the sender, so a tenant on shared infrastructure cannot file their own delisting.

Dedicated IPs operate like private lanes: your sending behavior alone determines your ESP (Email Service Provider) trust score, and you control the delisting path. Inframail provides 1 dedicated US-based IP on the Unlimited Plan and 3 dedicated IPs on the Agency Pack, and keeping 300 to 400 inboxes per dedicated IP is the published ceiling.

How to buy and register outreach domains

Acquiring domains is the first infrastructure step, but registrar choice and ownership configuration determine how much manual work onboarding requires. This section covers domain acquisition, registrar selection, and the pre-warmup ownership checks that prevent flagging before the first send.

Buying domains through the platform

Domains purchased through Inframail run $5 to $16 per year, with automated connection to the infrastructure on purchase and no manual DNS panel work required. Domains an agency already owns can be connected for $5 per domain one time. New domain purchases are capped at 5 per 24 hours, while migrations run 5 in the first 24 hours and up to 20 per 24 hours afterward, so plan the acquisition schedule around whichever route applies.

Let new domains age before launching real cold email sends. Spamhaus notes that for the first 30 days after registration most threat intelligence providers flag a newly registered domain, and advises against sending a bulk run from a freshly acquired domain at all. Use this period to configure DNS records and run warmup, which is why the 14-day warmup window sits inside the 30-day flag period rather than after it.

Choosing a domain registrar

Traditional registrars like GoDaddy or Namecheap require manually adding SPF, DKIM, and DMARC records in their DNS panels for each domain. For a 10-domain onboarding that is manageable. For 50 domains it is a half-day of work with significant error risk. Inframail automates the DNS connection on domain purchase, removing the manual step entirely, and applies the same automated configuration to domains migrated in from an external registrar.

Configuring domain ownership and privacy

Enable WHOIS (the public domain registration record) privacy on every cold outreach domain immediately after purchase. ICANN-accredited registrars offer privacy and proxy services that publish alternative contact information in place of the registrant's personal details, or replace the registrant of record entirely. Confirm the following before warmup begins:

• WHOIS privacy is active at the registrar level
• Registrant contact information uses a business address
• No domain is registered under a personal name linked to an existing flagged sender

Domains purchased through Inframail remain the agency's property after cancellation and can be transferred to another registrar, so this configuration work is not lost if infrastructure changes later.

Setting up SPF, DKIM, and DMARC records

These three DNS records authenticate sending domains and prevent spoofing, but misconfiguration resets warmup timelines and tanks inbox placement. This section covers each DNS authentication record and how to verify they are correctly propagated before warmup begins.

Configuring your SPF records

SPF is a DNS TXT record that tells receiving mail servers which IP addresses are authorized to send email on behalf of your domain. For Microsoft-based infrastructure, a typical SPF record format is: v=spf1 include:spf.protection.outlook.com -all. RFC 7208 sets a hard limit of 10 DNS lookups during SPF evaluation, and exceeding it returns a permerror rather than a pass, so avoid chaining include: statements for services you are not actively using. The correct SPF record is applied automatically during domain setup, as shown in the SPF/DKIM/DMARC setup walkthrough.

Configuring DKIM for domain authenticity

DKIM adds a cryptographic signature to outgoing emails using a private key held by the email provider. The receiving server verifies the signature against a public DNS key, confirming the message was not altered in transit and genuinely came from an authorized sender. Keys are generated and applied automatically during provisioning, so no manual key management is required. The SPF/DKIM/DMARC setup video demonstrates the automated configuration process for multiple inboxes.

Enforcing DMARC to prevent spoofing

DMARC sits on top of SPF and DKIM and instructs receiving servers on what to do with messages that fail authentication. RFC 7489 defines the three policy values: none, quarantine, and reject, and endorses a staged rollout on the basis that an all-or-nothing switch discourages adoption. Start at p=none to monitor results without blocking email flow, then advance to p=quarantine and p=reject as alignment is confirmed.

Publishing a policy is not optional for volume senders. Yahoo requires bulk senders to publish a valid DMARC policy of at least p=none with a working rua reporting tag. Allow 24 to 72 hours after configuring SPF and DKIM before enabling DMARC so those records have time to propagate.

Verifying DNS and blacklist status before warmup

Before warmup begins, verify all three records have propagated correctly. Propagation is governed by the TTL on each record, which RFC 1035 defines as the interval a record may be cached before the source is consulted again, which is why the window varies between 24 and 72 hours rather than being fixed.

Blacklist status is tracked separately. Inframail offers blacklist monitoring as an optional paid add-on at $12.41/month billed annually, covering IP and domain listing status against Spamhaus and other major blacklists. It reports listing status only and does not track spam folder placement, so budget for it as a separate line item rather than assuming it is bundled.

The cold email inbox setup workflow

Inbox provisioning turns purchased domains into working infrastructure, and how accounts are created determines whether onboarding takes hours or minutes. This section covers provisioning, bulk inbox creation, and credential management.

Provisioning Microsoft inboxes

Inframail is built on Microsoft's cloud platform, with a publicly announced enterprise partnership from January 2024. Provisioned inboxes run on native Microsoft infrastructure with full IMAP (Internet Message Access Protocol) and SMTP (Simple Mail Transfer Protocol) access. The flat $129/month Unlimited Plan covers unlimited inboxes, so adding 50 inboxes costs the same as adding 5, with no per-seat charges regardless of campaign activity.

Worth noting for scoping: Inframail is an email infrastructure provider, not a sending platform. Inboxes connect to a separate cold email tool for sequencing, warmup execution, and reporting.

Automating bulk inbox provisioning

Inboxes are provisioned in bulk from the dashboard without manual account creation. Published setup time is approximately 180 seconds per domain from purchase to ready-to-send inboxes. After provisioning, the platform generates IMAP and SMTP credentials for each inbox and packages them into a CSV export for direct import into sending platforms.

"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

Protecting agency and client login data

Use a password manager (1Password, Bitwarden, or equivalent) to store client inbox credentials separately from agency credentials. Never share raw CSV files containing SMTP passwords via email or Slack. For agencies using Smartlead, Inframail's Smartlead integration guide covers the exact field mapping for the CSV import.

Warming up inboxes before the first campaign

Warmup establishes sender reputation before real cold outreach begins, and improper ramp configuration or missing authentication resets the entire timeline. This section covers how warmup runs, the published ramp schedule, and deliverability measurement.

Understanding how warmup runs on Inframail

Inframail does not execute warmup itself. Warmup runs through the sending platform the agency already uses, such as Instantly, Smartlead, or ReachInbox, which means most agencies do not need a separate per-inbox warmup subscription on top of their existing stack.

Connect each new inbox to the sending platform after confirming DNS propagation, and verify authentication records before starting the warmup clock. A misconfigured DKIM record discovered after two weeks resets everything. Agencies that want the setup handled for them can use the Done-for-You (DFY) Email Campaign Setup package ($3,497 one-time or $499/month), which includes managed warmup as part of the service.

Configuring warmup for new domains

Warmup runs for 14 days on new domains, at an increment of 1 additional email per day. Domains already warmed before migration can be reduced to 7 days, but new domains always complete the full 14.

1. Warmup days 1-14: Run at an 80% warmup to 20% campaign split, increasing by 1 email per day
2. The following week: Shift gradually toward a 50/50 warmup to campaign split as placement holds
3. After warmup: Move to the steady-state split used for capacity planning, keeping a share of warmup volume running permanently as reputation maintenance

Keep total sending within 40 emails per inbox per day, with 50 as the hard ceiling, across warmup and campaign volume combined.

Measuring deliverability health

Inframail publishes a 98%+ deliverability rate alongside a 68.3% blacklist delisting success rate. Use seed lists and inbox placement testing to establish a baseline before launching, and measure against the published bands: 80 to 100% inbox placement is excellent, 60 to 80% needs improvement, and anything below 30% is critical. Bounce rate should sit between 0 and 1%, with 2% or above treated as critical. Inframail's infrastructure health monitoring guide covers how to set up automated alerts.

Connecting Inframail to your sending platform

Sending platforms require SMTP and IMAP credentials for each inbox, and connection errors discovered after warmup delay campaign launch. This section covers credential export, CSV import, and pre-launch deliverability testing.

Exporting inbox credentials

Credential export happens entirely inside the Inframail dashboard. From the Update page, save any sender name changes, select your sending platform from the dialog, and the CSV downloads pre-formatted for that platform, arriving with a filename like instantly-bulk-import.csv or smartlead-bulk-import.csv.

The only prerequisites are an active subscription, at least one inbox already created, and dashboard access. No Exchange admin permissions, SMTP AUTH toggles, or app-specific passwords are required, because Inframail manages the underlying Microsoft tenant rather than handing it to the agency.

Importing the CSV into your sending platform

Import the platform-formatted CSV directly into your sending tool. Because the file is generated per platform, select the correct one at download rather than reformatting afterward. After import, run a connection test on each inbox within the sending platform before assigning any sequences.

Custom tracking domain configuration is included in the export for Smartlead and SalesHandy, and is not available for Reply.io, Woodpecker, or Plusvibe.co, so confirm your platform is supported before relying on it. For a complete GoHighLevel setup, the INFRAMAIL + GHL setup walkthrough covers integration from domain purchase through first campaign execution, and the Instantly AI setup walkthrough covers importing infrastructure credentials and configuring campaigns once the CSV is exported.

Testing deliverability before launch

Before launching any live sequence, run three pre-flight checks:

1. Send a test email from each new inbox to a personal Gmail and Outlook account. Confirm it lands in the primary inbox, not spam.
2. Check email headers on the received test message to verify SPF and DKIM signatures show PASS.
3. Run the sending domain through a Spamhaus blocklist lookup to confirm it is not pre-listed before the first campaign send.

If any inbox fails the DKIM or SPF check, return to the DNS configuration panel in Inframail and allow another 24 to 72 hours for propagation before retesting.

Executing your first cold outreach campaign launch

Campaign activation requires final checks on DNS, tracking domains, and volume limits to protect sender reputation and meet client expectations. This section covers the final configuration audit, volume settings, and client sign-off steps required before activating a sequence.

Running the pre-launch configuration audit

Run this three-point check immediately before activating any client sequence:

1. DNS propagation status: Confirm SPF, DKIM, and DMARC are passing on every sending domain.
2. Custom tracking domains: Verify that open and click tracking domains are configured under a subdomain of the outreach domain, not the client's primary domain, and that your sending platform supports the feature.
3. Daily sending limits: Confirm each inbox is capped at 12 campaign emails per day within the sending platform's sequence settings, keeping total volume including warmup at or below 40.

Setting safe daily campaign volume

Inframail's published capacity model allows 40 total emails per inbox per day at a 70/30 warmup to campaign split, which works out to 12 campaign emails per inbox per day. For a 50-inbox setup, that is roughly 600 daily campaign sends, well inside the Unlimited Plan's 80,000 cold emails per month ceiling.

Rotate sends across the full domain pool rather than concentrating volume on a few high-performing domains. Note this is domain rotation, handled in the sending platform. Inframail assigns fixed dedicated IPs and does not rotate them.

Keep the spam complaint rate below 0.1%, which is Inframail's internal target, and treat 0.3% as the hard ceiling, since Yahoo requires bulk senders to keep spam rates below 0.3%. For legal obligations on cold outreach and opt-out handling, the FTC requires that opt-outs be honored within 10 business days, that the opt-out mechanism stay live for at least 30 days, and it sets penalties of up to $53,088 per violating email. Inframail's cold email legality guide covers the practical application alongside GDPR obligations by region.

Finalizing client sign-off

Present a launch-ready report to the client before activating sequences, including deliverability test results, the list of active sending domains, and confirmation that warmup has run for the full 14 days. Get written approval on final copy and targeting criteria before the first send.

Once sign-off is received, activate the sequence below the 12 per inbox ceiling, at roughly 5 to 8 campaign sends per inbox, and scale to full volume over the first week while monitoring bounce rate and spam complaint rate.

Next steps

A repeatable onboarding process is what keeps infrastructure cost per client flat as the roster grows. Run the sizing formula at intake, respect the 5-domains-per-24-hours purchase cap when building the timeline, complete the full 14-day warmup, and hold campaign volume at 12 per inbox per day. Done consistently, a 50-inbox client sits at $163/month all-in against $350 to $420 on per-seat infrastructure, and that gap widens with every client added.

Sign up to Inframail and get started today.

FAQs

How long does cold email onboarding take from start to first campaign?

Setup runs at approximately 180 seconds per domain, but new domain purchases are capped at 5 per 24 hours, so a 28-domain client takes about 6 days to acquire and configure. Warmup then runs a further 14 days on new domains, putting the first real campaign send around day 22.

What happens to warmup scores when switching from Google Workspace to Inframail?

Warmup scores and sender reputation built on a previous platform do not transfer. Migrated domains arrive with no sending history on the new infrastructure, so a fresh warmup is required. Domains that were already warmed before migration can run a shortened 7-day warmup, but newly purchased domains always complete the full 14 days.

How do I troubleshoot delayed DNS updates or blacklist issues?

Pause sending from the affected domain immediately, verify SPF, DKIM, and DMARC records are correctly configured and passing, then submit a delisting request. Note that for IP-level listings, only the provider controlling the IP can request removal, which is one practical argument for dedicated infrastructure. Inframail's automated delisting achieves a 68.3% success rate, and the Microsoft blacklist recovery guide covers the platform-specific process.

How much does Google Workspace cost compared to Inframail for 50 inboxes?

Google Workspace Business Starter costs $350/month (annual) or $420/month (flexible) for 50 inboxes at $7.00 to $8.40 per user per month. Inframail costs $163/month total ($129 platform plus approximately $34 in amortized domain costs at one domain per inbox), saving $187 to $257/month on infrastructure.

When should inbox warmup begin?

Warmup should begin after DNS records are verified and propagation is confirmed, which typically takes 24 to 72 hours after initial configuration. It then runs for a full 14 days on new domains before the first cold outreach email goes to a real prospect.

Key terms glossary

SPF (Sender Policy Framework): DNS TXT record listing which IP addresses can send email for your domain. Limited to 10 DNS lookups during evaluation.

DKIM (DomainKeys Identified Mail): Cryptographic signature added to outgoing emails using a private key. Receiving servers verify the signature against a public DNS key to confirm message authenticity.

DMARC (Domain-based Message Authentication, Reporting and Conformance): Policy instructing receiving servers what to do with emails that fail SPF or DKIM checks. Start at p=none (monitor), then advance to p=quarantine and p=reject.

Dedicated IP: Private IP address where only your sending behavior affects reputation. Contrasts with shared IP pools, where another sender's listing can escalate to the surrounding range.

Inbox placement rate: Percentage of delivered emails reaching the primary inbox versus spam folders. Distinct from delivery rate, which measures whether the server accepted the message at all.

Domain warmup: 14-day sending ramp at an increment of 1 additional email per day, run through the sending platform. Establishes domain reputation with inbox providers before real cold outreach begins.

Cost-per-inbox: Total monthly infrastructure spend divided by the number of active sending inboxes. Key metric for protecting agency net margins as client count scales.