GMass FAQ: Download, Daily Limits, Email Warmup & AI Writer for RevOps

2026-08-25 · Julian Hartwell

I manage our software stack at a ~50-person B2B company—around 20 subscriptions, roughly $80,000 a year in SaaS spending. When our sales team told me cold email needed fixing, GMass kept surfacing in my research. So I evaluated it the way I'd evaluate any vendor: dig into the docs, test the product, check whether it actually fits our workflow.

This FAQ captures what I learned. I'm covering what GMass is, how to download it, the daily email limit (and there's a catch), how the warmup works, the AI email writer feature, and what RevOps teams should really scrutinize with AI personalization. Bottom line up front: GMass works well for a specific use case, and I'll be honest about where it doesn't fit.

What is GMass?

GMass is a Chrome extension that runs inside Gmail and turns it into a cold email platform. You don't get a separate dashboard or a new interface to learn. Your existing Gmail screen becomes the tool.

The core functions are cold email campaigns, built-in email address verification, email warmup, and LinkedIn automation. The LinkedIn piece connects connection requests with follow-up email sequences, which our SDRs found useful.

The surprise for me wasn't the feature list. It was how little friction our team felt during adoption. Most tools I roll out require me to chase people for weeks. GMass lives in Gmail, so it got used without any pushing from my side. From an operations standpoint, that's worth a lot.

How do I download GMass?

You download GMass from the Chrome Web Store. It's a standard extension install—the actual download takes under a minute, and setup takes maybe 15 minutes once you connect your Gmail account. Or rather, that's how long it took us. Yours might differ if you're navigating unfamiliar Google account permissions.

One setup decision I'd recommend: create a dedicated Google Workspace account for cold outreach. That keeps the sending reputation separate from your team's main inboxes, and it gives you a cleaner way to measure campaign performance. We did that after our first campaign taught us the hard way that mixing outreach with daily business email is messy.

The free plan is worth mentioning here. It caps at 50 emails per day and puts a watermark on outgoing mail. That's too limited for real campaigns, but it's enough to evaluate whether GMass fits your team. And from a purchasing standpoint, they provide proper invoicing, which is more than I can say for some tools we've evaluated.

What is the GMass daily email limit?

I dug into this one because the search results were vague. There are actually two limits to understand.

First, Google's limit. GMass sends through Google's servers, so the sending limits of your Google account apply. Google Workspace accounts can send to roughly 2,000 external recipients per day, per account. Free Gmail accounts get around 500. Those numbers are documented in Google's own support materials.

Second, GMass's plan limit. The free plan stops you at 50 emails per day. Paid plans remove that particular limit, and then Google's limit becomes the ceiling.

But here's what I keep telling our sales team: a daily limit isn't a target to hit on day one. Google watches your sender reputation—bounces, spam complaints, engagement—and adjusts how much you can send. If you push 2,000 cold emails from an un-warmed account, you're asking for deliverability trouble. Which leads directly to the next question.

Does GMass include email warmup?

Yes. GMass has a built-in warmup feature that runs in the background. And honestly, I did not believe warmup mattered until I skipped it. We launched our first campaign from a fresh Gmail account without warming up. The result: most of our emails went straight to spam, and it took weeks to recover the sender reputation. Trust me on this one.

Here's what warmup actually does in GMass, at a high level. Your account joins a network of GMass users who send small volumes of emails to each other. Those test emails get opened, replied to, and marked as "not spam"—which Google reads as positive engagement signals. Over time, the system gradually ramps up your daily send volume. It's like a workout program for your sending reputation.

My practical advice: run warmup for at least 2-3 weeks before a major campaign, especially if your domain is new. And don't treat warmup as a substitute for list hygiene. GMass also has verification built in, so use both together. If you're sending to stale addresses, no amount of warmup saves you.

How does the AI email writer feature work?

The AI email writer feature works inside Gmail's compose window. You type a short instruction—something like "intro email to a marketing VP about our event"—and it generates a complete draft with personalization tokens for name, company, and custom fields.

From my evaluation, a few things stood out:

  • The draft quality is solid. Not perfect, but an excellent starting point. I'd say 80-90% of the work is already done.
  • It rewards specific prompts. The more context you give, the better the output. "Email to a SaaS founder about API integration" produces a much better draft than "cold email about our product."
  • You can adjust tone and length, which helps match your team's voice.

The thing to watch: if you let AI run on autopilot without human review, your emails start to sound like everyone else's AI-generated emails. That creates a pattern that recipients—and spam filters—can pick up on. In practice, our best results came from AI drafting and humans editing before hitting send.

On the compliance side, which is my lane since I report to finance and operations, AI-generated outreach still falls under CAN-SPAM. You need a physical postal address in the footer, a clear opt-out mechanism, and accurate header information. GMass supports this when configured properly. But the sender is the one on the hook.

What should revenue operations teams evaluate in AI personalization?

This is the question I wish we had asked before our early AI tool evaluations. Here's the checklist I'd bring to any vendor conversation.

Data quality and hygiene. AI personalization is a multiplier. If the underlying data is wrong—outdated titles, stale company size, duplicate records—the AI will produce confident emails targeted at nonexistent problems. Ask how the tool cleans and validates data before it reaches the AI stage.

Data security and privacy. When you use an AI writer, your prospect data gets sent to an AI processing layer. In a GDPR or CCPA environment, you need to know exactly what happens to that data. Does the vendor use it for model training? Where is it stored? What retention policies apply? This was a genuine compliance issue for us, not just IT paranoia.

Deliverability infrastructure. The best-written AI email in the world is worthless if it lands in spam. Check whether the tool has verification, warmup, and sending limits designed to protect inbox rates. A vendor can bolt on AI writing without understanding email infrastructure.

Human review workflow. A lot of people assume AI personalization means full automation. In our experience, the highest-performing approach is AI generates + human reviews. That requires a workflow where reviewing is easy. If reviewing means extra clicks and tabs, your team will skip it. That's exactly how spammy patterns emerge.

Avoiding fabricated claims. This one isn't obvious until you see it. An AI model might generate a personalized opening line based on a prospect's LinkedIn post, but it can also hallucinate context or invent an achievement. RevOps teams should ask what guardrails exist to prevent AI from fabricating claims about real people.

A testable reference point. Our approach was simple: take a segment of 50 prospects, send half manual emails and half AI-assisted emails, and compare reply rates. If you can measure that with whatever tool you evaluate, you're ahead of most teams.

When does GMass not make sense?

Every tool has a grey zone, and good vendors tell you about it. So here's mine, based on the evaluation we did.

GMass is built for Gmail and Google Workspace. If your team runs on Outlook or Microsoft 365, it's not for you. Don't try to force it. There are perfectly good alternatives for Microsoft-based stacks.

If your outbound motion involves complex, multi-touch, branch-heavy journeys—enterprise sales with lots of conditional paths—GMass might feel limiting. It's a cold outreach tool, not an enterprise revenue orchestration platform. If you need the latter, don't buy the former and expect it to stretch.

And my experience is based on a ~50-person company running fairly standard B2B outbound. If you're a solo founder sending five hyper-personalized emails a day, or an enterprise pumping out tens of thousands per month, your needs are more specific than mine. Your results may differ.

If you're in GMass's sweet spot—Gmail-native, small to mid-sized team, cold outreach with personalization, built-in verification and warmup—it's worth a test on the free plan. If you're outside that sweet spot, look elsewhere. The most trustworthy recommendation I can give someone is the one that says "this might not be for you."