Google vs Outlook for cold email and why matching matters

Google or Outlook for cold email? Wrong question. I’ve watched teams argue over which provider sends better, pick one, and ignore the only variable that actually moves replies: what their prospects use.

Here’s what I mean. A cold email crosses more than an inbox. It crosses an ecosystem. Google’s filters trust Google traffic more, Microsoft’s filters trust Microsoft traffic more, and the moment you cross providers, you lose some of that trust before your prospect even sees the subject line.

In this article, I’ll walk you through the google vs outlook for cold email debate using lemlist’s own data on 46.1M leads, broken down by all four sender-to-recipient routes. I’ll show you where replies peak, where bounces spike, and why matching your sending provider to your prospect’s provider matters more than picking a favorite.

By the end, you’ll know how to check which provider your leads run on, how to split your sending infrastructure without doubling your workload, and how to set this up inside lemlist in one afternoon.

Why the provider question matters

The best email provider for cold email is the one your prospects already use. When sender and recipient sit on the same provider, replies go up and bounces go down.

Here is why. Every mailbox provider runs its own filtering stack. Google’s filters know what normal Google-to-Google traffic looks like, and Microsoft’s filters know what normal Microsoft-to-Microsoft traffic looks like. When an email crosses from one ecosystem to the other, the receiving side has less history to draw on and applies stricter checks. The result shows up in two places: your reply rate and your bounce rate.

That sender-to-recipient pairing is one of the first things to audit when you review your email deliverability. Authentication, content, and list quality still matter. But if you get all of those right and still send from the wrong provider, you leave replies on the table before a single prospect opens your email.

The four routes an email can take

We looked at 46.1M leads in lemlist internal data and broke performance down by the four possible sender-to-recipient provider combinations.

Google to Google is the top-performing route. It has the highest reply rate and the lowest bounce rate of any combination. Microsoft to Microsoft comes second, with a meaningful gap in both metrics.

The two cross-provider routes sit at the bottom. Google to Microsoft is the weakest at 2.5% replies and 6.4% bounces.

The pattern is clear: same-provider routes outperform cross-provider routes on every metric.

Match the provider to your prospects

When sender and prospect use the same provider, replies average 3.5% compared to 2.7% for cross-provider sends (lemlist internal data). That is roughly a 30% lift just from matching. Bounces drop too, from 6.3% on cross-provider routes to 5.5% on same-provider routes.

Microsoft inboxes are stricter with everyone. Both cross-provider routes that touch Microsoft show higher bounce rates than the Google-to-Google baseline. So if your list skews toward Microsoft 365 domains, matching matters even more. Sending from Google into a Microsoft-heavy list is the worst-case scenario in the data.

The takeaway is simple. Before you pick a provider, look at your list. If most of your prospects are on Google Workspace, your primary sending inboxes should be on Google. If the split is closer to even, you need both.

How to know which provider your prospects use

Every domain’s email provider is visible in its MX record. The MX record is a DNS entry that names the servers accepting inbound mail for that domain. Google Workspace domains point to servers ending in google.com or googlemail.com. Microsoft 365 domains point to servers ending in outlook.com or mail.protection.outlook.com.

Here is the workflow:

• •

  Pull the list of unique domains from your lead list.

• •

  Run an MX lookup on each domain. You can do this with a command-line tool like nslookup -type=MX domain.com, a free web tool like MXToolbox, or a bulk lookup script.

• •

  Tag each domain as Google, Microsoft, or Other based on the MX hostname.

• •

  Split your lead list into segments by provider tag.

• •

  Assign each segment to sending inboxes on the matching provider.

If you are unfamiliar with how MX records work or want to make sure yours are configured correctly on the sending side, the guide on how to set up MX records walks through the full process.

Google Workspace and Microsoft 365 setup differences

Running cold email infrastructure on both providers means managing two admin environments. They are not identical.

Google Workspace uses a single Admin console. You add users, verify domains, and configure DNS records in one place. Creating a new inbox is straightforward: add a user in the console, and the mailbox is live within minutes. Google’s guided setup flow writes SPF, DKIM, and DMARC records for you when your registrar supports it.

Microsoft 365 spreads administration across several portals. User management lives in the Microsoft 365 admin center, but identity and conditional access sit in Entra, and mail flow rules live in the Exchange admin center. Creating a mailbox means assigning a license to a user, then verifying that DNS records are published correctly. Microsoft provides setup wizards, but the number of surfaces you touch is higher.

For email authentication, both providers support SPF, DKIM, and DMARC. Google tends to enable DKIM signing with fewer steps. Microsoft requires you to generate DKIM keys in the Defender portal and publish two CNAME records per domain, then manually enable signing.

The practical difference: Google is faster to set up if you are adding a handful of inboxes across a few domains. Microsoft takes more clicks per inbox but gives you more granular control over mail flow policies. For cold email, you rarely need that granular control. You need correctly authenticated inboxes that are ready to warm up.

Run both providers without doubling the work

You do not need a massive infrastructure on each side. A split setup works well: a few Google Workspace inboxes for your Google-provider prospects, a few Microsoft 365 inboxes for your Microsoft-provider prospects.

The volume rules are the same on both sides. Stay under 50 emails a day per inbox, ideally 30 to 40 (lemlist internal data). Spreading volume across more inboxes at lower daily caps protects your sender reputation better than pushing a small number of inboxes to their limits.

Buy dedicated cold email domains for each provider. Keep your primary business domain off the sending infrastructure entirely. A few domains per provider, with a few inboxes per domain, gives you enough rotation without overcomplicating management.

Warm-up is where the real advantage sits. In lemlist internal data, inboxes with warm-up turned on show a 6.2% bounce rate in the US compared to 9.4% with warm-up off. That is roughly a third lower. The guide on how to warm up an email account covers the full process. Apply the same warm-up discipline to both your Google and Microsoft inboxes. Same ramp schedule, same daily caps, same monitoring. If you send from Google Workspace and notice inbox placement issues, the guide on how to prevent emails from going to spam in Gmail covers the most common fixes.

The work does not double because the rules are identical. The only thing that changes is which admin console you log into when you add a new inbox.

How to set up Google and Microsoft inboxes in lemlist

lemlist lets you buy domains and mailboxes directly inside the platform. When you create a new mailbox, you choose Google, Outlook, or SMTP as the provider. Authentication records (SPF, DKIM, DMARC) are set up automatically, so you skip the manual DNS configuration.

New mailboxes appear in lemwarm as soon as they are created, ready to start warming up. You control the warm-up pace and monitor reputation from the same dashboard.

When you build a campaign, you can add several sending inboxes and lemlist rotates across them. Set your sending schedule and daily pacing per inbox to stay within the 30 to 40 emails per day range. If you have tagged your lead list by provider, you create two campaigns (or two segments within a campaign): one using your Google inboxes for Google-provider leads, one using your Microsoft inboxes for Microsoft-provider leads.

The result is provider-matched sending at scale, managed from one platform.

Final takeaway

The Google vs Outlook debate misses the point. What matters is whether your sending provider matches your prospect’s provider. Same-provider routes reply about 30% more and bounce less, and you can run both sides from one platform without extra complexity.

Build your first signal-based sequence in lemlist.