Cold outreach RFP template for agencies

TL;DR: A cold email infrastructure RFP should force every vendor to answer the same five questions in writing: line-item total cost of ownership at the agency's real inbox count, inbox placement methodology, blacklist delisting success rate, multi-client credential scoping, and contract flexibility. As of August 2026, Google Workspace Business Starter is $8.40 per user per month, so 50 inboxes cost $420 and 200 inboxes cost $1,680. Inframail charges a flat $129 per month regardless of inbox count, while Maildoso and Mailscale price per mailbox in fixed tiers. Warmup tools are extra on all of them. Score the responses, then pilot 2 to 3 vendors on 10 to 20 domains before signing.

When an agency scales from 50 to 200 cold email domains, Google Workspace Business Starter bills at $8.40 per user per month on the flexible plan, putting 50 inboxes at $420 per month and 200 inboxes at $1,680 per month, turning infrastructure into one of the fastest-growing line items on the P&L. Per-inbox competitors like Maildoso and Mailscale scale their pricing with mailbox count, while Inframail's flat-rate $129 monthly fee stays constant regardless of inbox count, protecting the 15 to 20 percent net margins that justify a structured evaluation process.

A cold outreach RFP helps agencies evaluate vendor claims with verifiable numbers. It structures the evaluation around pricing, deliverability, IP architecture, and contract terms so agencies can compare vendors on specifics rather than marketing language before any budget is committed.

Core requirements in a cold email infrastructure RFP

A complete cold email infrastructure RFP should address five operational areas that directly affect agency margins and campaign uptime.

• Pricing transparency: Total cost of ownership across platform fees, domain registration, and warmup tools at the target inbox count.
• Deliverability monitoring: Inbox placement rate methodology, blacklist monitoring frequency, and documented delisting success rates.
• Multi-client scalability: How the vendor organizes and isolates domain assets across client accounts.
• Contract flexibility: Month-to-month availability, pilot terms, and cancellation conditions.
• Automated domain provisioning: End-to-end DNS setup time from domain purchase to first send.

Treat any vendor that cannot answer these five areas with specific numbers during the RFP phase as a scoring deduction before the pilot stage begins.

Calculating your true inbox expenses

The RFP should require vendors to break out every cost variable in line-item format: platform subscription fee, per-domain registration cost, and any external warmup tool requirements. This is the only way to build a real total cost of ownership (TCO) model. Vendors frequently hide warmup costs: external tools like Warmbox or Lemwarm run $15 to $50 per inbox per month, and most infrastructure vendors, including Inframail, require them separately. Any TCO model that omits this line item is incomplete.

Monitoring inbox placement metrics

The RFP must ask vendors to define their deliverability monitoring capabilities in specific terms, not marketing language. Vague deliverability guarantees are the clearest signal to score a vendor down. A vendor that cannot cite specific bounce rates and a documented domain-flagging process is describing an aspiration, not a capability. Real-time monitoring is critical because, as infrastructure monitoring guides note, the first signal of a deliverability problem should come from a dashboard alert, not a client complaint.

Scaling infrastructure across clients

The RFP should ask vendors how they isolate domain and inbox assets across multiple client accounts. A platform comparison analysis shows significant variation in how vendors structure pricing across seven infrastructure providers. Platforms that commingle client assets on shared IP pools create structural reputation risk that no monitoring dashboard can fully mitigate.

Evaluating vendor cancellation policies

The RFP must include direct questions about contract terms: Is month-to-month pricing available? Are there cancellation fees? What happens to domain assets if the contract ends? Agencies in early evaluation phases should not commit to annual contracts before validating real campaign performance on a pilot.

Automating new domain onboarding

The RFP should ask vendors to provide a timed, unedited walkthrough of their domain setup process from purchase to first send. Manual DNS configuration, logging into DNS panels to create SPF, DKIM, and DMARC records across 50 domains, takes 12 or more hours under traditional workflows. Inframail automates the full DNS configuration process, with customer reports of 10 inboxes provisioned in 2 minutes.

Implementing the cold email RFP workflow

The steps below cover how to define minimum performance thresholds using this article's framework and prepare a question set for vendor distribution.

Defining must-have performance metrics

Set hard minimums before sending: inbox placement rate floor, maximum blacklist delisting time, and maximum domain setup time. Eliminate vendor responses below these thresholds before the pilot phase.

Compiling the full RFP question set

Copy the questions below into a document and send to each vendor before scheduling demos. Remove any questions that do not apply to the agency's current scale or evaluation criteria.

Pricing and total cost of ownership

1. Provide a complete monthly cost breakdown for 50, 100, and 200 inboxes, including platform fee, per-domain registration cost, warmup tool requirements, and any overage charges.
2. Are there any one-time setup, onboarding, or activation fees beyond the monthly subscription?
3. What is your domain transfer process, and are there transfer fees?

Deliverability and blacklist management

1. What is your current inbox placement rate, measured with which tool and methodology, and how recently was it tested?
2. What is your documented blacklist delisting success rate, and what is your average time to resolution after a domain is flagged?

Setup and provisioning

1. Provide an unedited screen recording of your full domain setup process from purchase to exported IMAP/SMTP credentials.

Multi-client infrastructure

1. Do you support client-level domain organization, or do all domains live in a single undifferentiated workspace?
2. How are IMAP/SMTP credentials scoped, and can one client's credentials access another client's domain assets?

Contract and pilot terms

1. Do you offer month-to-month pricing for an initial pilot of 10 to 20 domains, and what success metrics do you recommend tracking during the pilot period?

Support

1. What is your maximum first-response time and support availability across the week?

References

1. Provide two or three agency founders at comparable scale (50 to 200 domains, 5 to 15 clients) who are willing to speak candidly about deliverability performance, setup speed, and support quality.

Done-for-you options

1. Do you offer a done-for-you setup service, and what does it include?

Questions to validate vendor performance claims

The most valuable RFP questions are the ones vendors cannot answer with marketing copy. The 2026 platform-wide averages are a 3.43% reply rate and a 27.7% open rate, per Instantly's 2026 Cold Email Benchmark Report. Treat any vendor or case study quoting far above those numbers without stating its methodology as a figure to probe, not accept.

Uncovering hidden per-inbox fees

Sample RFP question: "Provide a complete monthly cost breakdown for 50, 100, and 200 inboxes, including platform fee, per-domain registration cost, warmup tool requirements, and any overage charges."

Per-inbox pricing models hide their true cost at scale. Maildoso's shared-IP infrastructure sells in fixed mailbox tiers on monthly billing. The 30-mailbox tier costs $75 per month and the 300-mailbox tier costs $225 per month, with domains purchased separately on both. Per-mailbox cost decreases as volume rises. Inframail's flat-rate $129 per month covers unlimited inboxes regardless of count. The Maildoso pricing breakdown shows exactly where that scaling cost advantage disappears at higher inbox volumes.

Estimating domain provisioning time

Sample RFP question: "Provide an unedited screen recording of your full domain setup process from purchase to exported IMAP/SMTP credentials."

This setup demonstration video shows what automated provisioning looks like end-to-end. Vendors who claim "minutes" but cannot show it on screen typically mean something closer to hours once DNS propagation delays are factored in.

How to evaluate agency vendor billing models

The billing model question is a math question. The right structure depends on current inbox count and the 12-month growth trajectory.

Avoiding hidden setup fees

The RFP should ask vendors directly: "Are there any one-time setup, onboarding, or activation fees beyond the monthly subscription?" Any such fee is unrecoverable if the pilot underperforms, so it belongs in the TCO model before the pilot starts, not after.

Transferring domains without downtime

The RFP should ask: "What is your domain transfer process, and are there transfer fees?" A Maildoso-to-Inframail migration guide documents that existing domains can be transferred rather than repurchased. Vendors that charge per-transfer fees create switching costs that make the vendor relationship stickier than the agency's actual satisfaction warrants.

Comparing flat-rate and per-inbox pricing models

The table below models monthly infrastructure costs across three inbox scales. Warmup tools are separate on all sides and typically cost $15 to $50 per inbox per month. Domain costs for Inframail are amortized from $5 to $16 per domain annually ($0.42 to $1.33 monthly).

Inbox count	Google Workspace	Maildoso (nearest published tier)	Inframail Unlimited Plan
50 inboxes	$ 420	No tier at this count. Monthly: 30-mailbox tier at $75 + domains separately (nearest tier to 50)	$129 + ~$34 (domains)
100 inboxes	$ 840	Monthly: 300-mailbox tier at $225 + domains separately (nearest tier above 100).	$129 + ~$68 (domains)
200 inboxes	$1, 680	Monthly: 300-mailbox tier at $225 + domains separately (nearest tier to 200).	$129 + ~$136 (domains)

Maildoso sells in fixed mailbox tiers rather than per-inbox increments, so the comparison depends on which tier an agency lands in. 30 mailboxes cost $75 per month and 300 mailboxes cost $225 per month, with domains purchased separately. Per-mailbox cost falls as volume rises, so the flat-rate advantage is largest in the middle of the range and narrows at the top.

Scaling costs: flat-rate vs. per-inbox

For 50 inboxes, Inframail's total infrastructure cost is approximately $163 per month (platform plus amortized domains). Google Workspace at the same scale costs $420 per month, saving agencies $257 per month, or $3,084 annually, before warmup tools. As this cost comparison video demonstrates, the savings compound sharply as inbox count grows. At 200 inboxes, Google Workspace costs $1,680 per month while Inframail's platform fee stays at $129 per month.

Vetting vendor deliverability performance

Deliverability is the variable that connects infrastructure cost to campaign output. The Maildoso deliverability analysis shows how shared IP infrastructure creates placement inconsistency, while Inframail's dedicated IP architecture (1 IP on Unlimited, 3 on Agency Pack) isolates each agency's sending reputation from other users on shared IP pools.

Auditing inbox placement rates

The RFP should ask: "What is your current inbox placement rate, measured with which tool and methodology, and how recently was it tested?" Inframail reports a 98%+ deliverability rate across its Microsoft-based infrastructure.

Auditing blacklist delisting performance

Sample RFP question: "What is your documented blacklist delisting success rate, and what is your average time to resolution after a domain is flagged?"

This question forces vendors to produce a real number with methodology rather than a marketing claim. The RFP should also require vendors to document their automated delisting workflow. Inframail monitors domain and IP health continuously, submits delisting requests automatically when a domain is flagged, and documents a 68.3% blacklist delisting success rate within 48 hours.

Requesting referenceable agency customers

The RFP should include a direct request: "Provide two or three agency founders at comparable scale (50 to 200 domains, 5 to 15 clients) who are willing to speak candidly about deliverability performance, setup speed, and support quality." A vendor ranking video that evaluates vendors across setup, deliverability, and support identifies reference customer quality as a differentiating criterion in any serious evaluation.

Managing inboxes across multiple agency clients

Operational efficiency at the infrastructure layer determines how many clients an agency can manage without proportionally scaling headcount. Customer testimonials report 10 inboxes provisioned in 2 minutes with automated DNS configuration.

Exporting and standardizing credentials across clients

The RFP should ask whether the platform supports client-level domain organization or whether all domains live in a single undifferentiated workspace. A Smartlead integration guide documents the credential export and import workflow, exporting inbox credentials to CSV from Inframail and importing them into Smartlead. Automated DNS configuration standardizes onboarding for every new client regardless of how many domains are being provisioned simultaneously, eliminating the inconsistency that comes from manual panel work across different DNS registrars. The infrastructure setup walkthrough shows this end-to-end.

Comparing dedicated IPs and shared IP pools

Shared IP pools work like carpool lanes where one bad actor's spam complaints affect every other sender on the same range. Dedicated IPs work like private lanes where the agency's own sending behavior alone determines ESP trust. Inframail includes 1 dedicated US-based IP on the Unlimited Plan ($129 per month) and 3 dedicated US-based IPs on the Agency Pack ($327 per month). A Mailreef comparison notes that both platforms isolate sending reputation from other users, with the architecture differing rather than the outcome, so the decision usually turns on pricing structure and setup speed.

Preventing cross-client data leakage

The RFP should ask how IMAP/SMTP credentials are scoped and whether one client's inbox credentials can access another client's domain assets. Inframail generates IMAP/SMTP credentials per inbox and exports them to CSV for import into the sending platform. This matters most for agencies managing 5 or more active clients simultaneously, and credential scoping is worth confirming in writing before onboarding multiple clients onto one account.

How to migrate without disrupting campaigns

Switching infrastructure vendors during active campaigns carries real risk. Authentication record misconfiguration is one common failure mode. Microsoft's authentication troubleshooting guidance documents how SPF, DKIM and DMARC errors cause mail to be junked, quarantined or rejected outright. Premature high-volume sending on a cold IP is the other, and neither is apparent until campaigns are already underperforming.

Migrating existing cold email assets

The table below details what carries over versus what requires reconfiguration during a vendor switch.

Asset type	Can migrate?	Technical action required
Domains	Yes	Transfer registration or update DNS nameservers
DNS records (SPF, DKIM, DMARC)	No	Must be reconfigured (Inframail automates this step)
Warmup history	No	Warmup must restart on new infrastructure
Inbox credentials	No	New IMAP/SMTP credentials generated and exported to sending platform

Reconfiguring DNS during migration

Manual DNS migration across 50 domains under traditional workflows takes 12 or more hours. Automated provisioning eliminates the DKIM key regeneration failure mode by validating DNS records automatically before the first send. A Mailreef-to-Inframail migration guide documents the full steps for agencies switching from a per-inbox infrastructure provider.

Managing downtime during migrations

A step-by-step checklist for minimizing campaign downtime during a vendor switch:

1. Authorize both platforms in SPF for the full duration of the cutover window, not just after go-live.
2. Run parallel DKIM selectors and keep the retired selector live in DNS for at least 7 days after the new platform is active.
3. Warmup new domains before routing full sending volume through the new infrastructure. New domains need a gradual volume ramp before full campaign volume. Microsoft's warmup guidance puts full deliverability at four to eight weeks depending on target volume and engagement, with a minimum ramp of about two weeks before meaningful sending.
4. Pause high-risk campaigns on the old platform before the MX cutover to avoid split-delivery issues.
5. Export and reimport credentials to the sending platform (Instantly.ai, Smartlead, etc.) after new inbox provisioning is complete.

Reviewing included services for new client setup

The RFP should ask: "Do you offer a done-for-you setup service, and what does it include?" Inframail's DFY Email Campaign Setup covers account setup, free email account warmup, an automated sending platform, one-on-one dedicated cold email coaching, and a first clean batch of 2,500 contacts. It is available at $3,497 one-time or $499 per month for agencies that want onboarding handled rather than managed in-house. A post-migration warmup guide details the step-by-step warmup process for agencies that migrate without the DFY service.

Clarifying your cold outreach RFP strategy

A rigorous RFP process pays off most when agencies treat it as a repeatable procurement system rather than a one-time evaluation.

Defining reasonable vendor response times

The RFP should specify a minimum support SLA: maximum first-response time and hours of availability. Inframail provides 16-hour daily support from real people, 7 days a week. For agencies where a deliverability issue on a Monday morning needs a response before client reporting that afternoon, support availability is a revenue-critical criterion.

Structuring vendor pilot programs

Sample RFP question: "Do you offer month-to-month pricing for an initial pilot of 10 to 20 domains, and what success metrics do you recommend tracking during the pilot period?"

Pilot 2 to 3 vendors simultaneously rather than sequentially. Sequential testing introduces timing variables including seasonality, list quality, and offer changes that make direct comparison unreliable. B2B SaaS pilot research distinguishes paid pilots, which test budget behavior and product value simultaneously, from free trials, which leave evaluation criteria undefined. A paid pilot with defined success metrics produces a cleaner decision. Inframail's standard monthly plan at $129 per month allows agencies to run a real pilot with no annual commitment.

The recommended pilot protocol runs as follows:

1. Provision 10 to 20 domains on each vendor's platform.
2. Run warmup for at least 14 days before active sending.
3. Hold per-inbox daily volume constant across all vendors for the duration of the pilot. The exact number matters less than keeping it identical on every platform, since an uneven send rate makes the placement comparison meaningless. Run this for 2 to 4 weeks of active campaign volume.
4. Track inbox placement rate, bounce rate, reply rate, and blacklist incidents across all vendors simultaneously.
5. Score vendor RFP responses against actual pilot performance and select based on combined evidence.

Applying objective vendor scoring

Score each vendor across five criteria on a 1 to 5 scale, weighted by the priority order below:

Criterion	Weight	Scored on
True cost per inbox at real pilot scale	30%	Line-item TCO comparison
Inbox placement rate with methodology	25%	Pilot data plus documented rate
Setup time from domain purchase to send	20%	Timed screen recording
Contract flexibility (month-to-month)	10%	Published terms
Support SLA and response time	15%	RFP response plus pilot experience

Pre-pilot vendor checklist

Before scheduling vendor demos, use this checklist to prepare evaluation criteria:

• Current inbox count and 12-month growth projection documented
• Minimum acceptable inbox placement rate defined (working band: 85 to 92%, consistent with agency SDR operations at standard campaign volume)
• Maximum acceptable setup time per 10 domains defined (benchmark: under 5 minutes for 10 inboxes, require vendors to demonstrate via timed screen recording before confirming your threshold)
• Minimum blacklist delisting success rate defined (benchmark: Inframail's 68.3%)
• Month-to-month contract requirement confirmed as non-negotiable
• Pilot budget allocated for 2 to 3 vendors at 10 to 20 domains each
• Pilot success metrics defined and weighted before vendor contact
• Done-for-you setup service availability confirmed if in-house onboarding capacity is limited

Get started with Inframail

Inframail is a flat-rate Microsoft email infrastructure platform built for agencies running 50 to 200 cold email domains. It automates SPF, DKIM, and DMARC configuration across every domain, includes dedicated US-based IP addresses (1 on the Unlimited Plan, 3 on the Agency Pack), and charges $129 per month regardless of inbox count. Inframail reports 98%+ deliverability and a 68.3% blacklist delisting success rate, with 16-hour daily support, 7 days a week.

Sign up to Inframail and get started today.

FAQs

How much does Inframail cost compared to Google Workspace?

For 50 inboxes, Google Workspace costs $420 per month at $8.40 per user per month on the flexible plan, while Inframail costs $129 monthly plus approximately $34 in amortized domain costs, saving agencies $257 per month on infrastructure alone. At 200 inboxes, Google Workspace hits $1,680 monthly while Inframail's total infrastructure cost stays at approximately $265 per month (platform plus amortized domains at 200 inboxes), compounding savings to roughly $16,980 annually before warmup tools.

What is the blacklist delisting success rate of Inframail?

Inframail has a documented 68.3% blacklist delisting success rate. The platform automatically monitors domain and IP health and submits delisting requests when issues are detected, before a client reports the problem.

Does Inframail include built-in email warmup tools?

No, Inframail does not include a built-in warmup tool, so agencies need external services like Warmbox or Lemwarm at $15 to $50 per inbox per month. Agencies on the Done-for-You setup package get free domain warmup included as part of that service.

Does Inframail support Google Workspace or only Microsoft 365?

Inframail is Microsoft-only, built on Microsoft's cloud infrastructure with a January 2024 enterprise partnership announcement. Agencies currently using Google Workspace will need to migrate domains to Microsoft 365 infrastructure.

How long does it take to migrate from Google Workspace to Inframail?

Domain transfers carry over immediately, but DNS records (SPF, DKIM, and DMARC) must be reconfigured, warmup history does not transfer, and new IMAP/SMTP credentials must be generated. A standard migration guide covers each step, with new domains typically requiring a minimum ramp of about two weeks before meaningful sending, and four to eight weeks to reach full deliverability per Microsoft's warmup guidance.

How many vendors should an agency pilot before committing to infrastructure?

A practical starting point is running a simultaneous pilot across 2 to 3 vendors, using 10 to 20 domains per vendor, holding per-inbox daily volume constant across all platforms, with 2 to 4 weeks of active sending before scoring results. Pre-scheduled check-ins and defined success metrics before the pilot starts prevent open-ended evaluation cycles that delay the infrastructure decision.

Key terms glossary

SPF (Sender Policy Framework): A DNS record that specifies which mail servers are authorized to send email on behalf of a domain. Missing or misconfigured SPF records cause emails to be rejected before they reach the inbox.

DKIM (DomainKeys Identified Mail): An authentication method that adds a digital signature to outgoing emails, proving the message was not altered in transit. DKIM keys must be regenerated during any infrastructure migration.

DMARC (Domain-based Message Authentication, Reporting, and Conformance): A protocol that uses SPF and DKIM to verify email authenticity and tells receiving servers how to handle authentication failures. DMARC policies must be reconfigured on any new sending domain.

Dedicated IP address: A unique IP address assigned exclusively to one sending account, isolating that account's sending reputation from all other senders on the platform.

Shared IP pool: A group of IP addresses shared among multiple senders, meaning spam complaints or blacklist events from one sender can reduce inbox placement rates for all others on the same range.

TCO (total cost of ownership): The complete monthly cost of running cold email infrastructure, including platform subscription fees, domain registration costs, warmup tool fees, and any sending platform costs. Headline pricing rarely reflects TCO.

Warmup: The process of gradually increasing sending volume on a new domain or IP address to build deliverability trust with email service providers before reaching full campaign volume. New domains typically require a minimum ramp of about two weeks before meaningful sending, with full deliverability taking four to eight weeks depending on target volume and engagement.

P&L (profit and loss statement): A financial report showing a company's revenues, costs, and expenses during a specific period. Infrastructure costs appear as a line item that scales with inbox count under traditional per-seat pricing.

SLA (service level agreement): A contractual commitment between a vendor and customer defining expected service quality, including metrics like response time, uptime, and support availability.

ESP (email service provider): A platform that sends, receives, and manages email on behalf of businesses. ESPs evaluate sender reputation to determine inbox placement rates.

MX (mail exchange record): A DNS record that specifies which mail server is responsible for receiving email on behalf of a domain. MX records must be updated during infrastructure migrations.

IMAP/SMTP: Internet Message Access Protocol (IMAP) allows email clients to retrieve messages from a server, while Simple Mail Transfer Protocol (SMTP) sends outgoing mail. Both require credential configuration when switching infrastructure vendors.