We Almost Rejected Mailshake on a Merge Tag. Here's What RevOps Should Evaluate Instead

Last March, our RevOps lead sent me a message in Slack.

'We need a prospecting tool. I'm looking at Mailshake. Can you run a quality review?'

I do this for a living, sort of. I'm a quality and brand compliance manager at a B2B SaaS company. I review every outreach sequence before it reaches customers—roughly 50 sequences a quarter. In the last year, I've rejected about 30% of first drafts for missing personalization, broken merge tags, or language that sounds like a robot ate a sales script. So when Dana asked, I didn't answer right away. I opened a spreadsheet and started building an evaluation framework.

This is the story of what happened over the next two weeks, and the lessons I think revenue operations teams should keep before they buy any prospecting tool.

The Background: Why We Needed a New Tool

Our outbound setup was messy. We used a generic CRM, a separate email verification service, and copy-pasted LinkedIn messages. Every SDR had their own version of the sequence, so quality control was basically impossible. We needed one place to run cold email and LinkedIn outreach without making the stack even more complicated.

The Task: Email + LinkedIn in One Workflow

The team wanted four things: reliable cold email, email verification, LinkedIn Sales Navigator automation, and reporting that told us what was actually working. Also no black-hat tricks.

I'll be honest: 'automation' made me nervous.

The Process: What I Actually Tested

I started with the obvious: searching for 'Jed Mahrle Mailshake cold email examples' and Reddit threads where people complain. Yes, I read the complaints. They're usually the most honest sales copy.

If you're not familiar with Jed Mahrle—or rather, if you don't obsess over who runs the tools you sell—he's the founder of Mailshake. His cold email examples are all over the internet. One thing struck me: his emails are boring on purpose. They look like regular emails from a tired person, not a marketing campaign. One example I remember (though I might be misremembering the exact wording) was something like:

I've got a thought on your podcast pricing page. Worth 2 minutes?

No 'I hope this email finds you well.' No 'As a leading provider...' No five links. That's it.

That's the quality bar I used for every sequence we wrote during the trial.

The Trial: Free Trial and LinkedIn Automation

Mailshake offers a free trial. I believe it's 14 days, but don't quote me—it might be 30 by the time you read this. The important part: when we tested it in 2025, the trial included access to the LinkedIn automation features. That's rare enough that it was worth taking seriously.

Here's what I expected: magic. What I got: a set of guardrails.

The LinkedIn Sales Navigator automation workflow was more manual than I expected. You build a lead list in Sales Navigator, then use Mailshake to manage the touches—connection request, maybe a follow-up, then an email once someone accepts. It didn't scrape profiles or send mass invites while you sleep. That's probably why it didn't get our account flagged. But I want to be careful here: LinkedIn automation is never a 'set it and forget it' thing. Keep a human in the loop.

The 'free trial LinkedIn automation' search is common because people want to know if they can test this without paying. The answer in our case was yes. But 'can you' and 'should you' are different questions. I'll come back to that.

The Turning Point: A Merge Tag Almost Broke Everything

Two days into the trial, I built a test sequence for our own SDR team. It was a standard cold email: first line references something specific about the prospect, second line states the reason, third line makes one clear ask. I had a custom field for reason_for_demo and I was confident I'd set it up correctly.

I skipped the test send to a small list. Why? I was rushing. We had a RevOps budget meeting that afternoon, and I wanted to show Dana something. I thought, what are the odds a merge tag is wrong? It's just 10 recipients.

The odds were 100%. Every email went out with the literal text {{reason_for_demo}} in the middle of a sentence. If that had been a campaign of 2,000 prospects, our first impression would have been 'we can't even send a proper email.' That's the kind of mistake that costs a $22,000 redo—not to mention the trust.

But here's the thing: Mailshake caught it. The send preview in the campaign builder flagged it? Actually, no. I caught it when I looked at the test emails in my inbox. The lesson is the same whether it's Mailshake or any other tool: always send a test email to yourself first.

That moment changed our evaluation. We stopped asking 'does this tool work?' and started asking 'if we make a mistake, will this tool make it easy for us to catch it?'

What Should Revenue Operations Teams Evaluate in a Prospecting Tool?

'Cold email is spam' thinking comes from an era when you bought a list of 50,000 emails and crossed your fingers. That's changed—but only if you use the right infrastructure. Same with LinkedIn automation: a lot of managers think all automation is dangerous. The reality is more boring. It depends on what the tool does and how you use it.

For revenue operations teams, here's the checklist we ended up with. I use it for every prospecting tool now, not just Mailshake.

1. Deliverability Is a System, Not a Setting

Cold email only works if it lands in the inbox. Look for SPF, DKIM, and DMARC setup, domain warmup, and spam complaint handling. Mailshake's free trial included email verification—even though I almost overlooked it. That's actually a critical feature. If you don't verify emails, a list full of bad addresses can damage your domain.

2. Integration Truth: What Syncing Actually Looks Like

The sales page says 'HubSpot integration.' The real question is: does it sync two-way, or does it just dump leads into the CRM? We needed prospects to move from Mailshake to HubSpot and back. It worked, but 'worked' meant we had to configure it carefully. Budget time for that during your trial.

3. LinkedIn Sales Navigator Automation Needs a Compliance Answer

I'm not going to tell you Mailshake's LinkedIn automation is 100% compliant with LinkedIn's terms. I don't know for sure, and LinkedIn changes rules. What I can tell you is what a quality inspector looks for: no scraping, no mass connection requests, manual controls for pacing, and an easy way to opt out. Bring that checklist when you talk to any vendor.

4. Mailshake Pricing 2025: Total Cost, Not List Price

Mailshake pricing in 2025 for cold email plans, from the public pricing page (mailshake.com/pricing, accessed January 2026), started around $25 per user per month for the entry tier and jumped to somewhere in the $45–$50 range for the full sales engagement tier with email verification and LinkedIn features. But by the time you add Sales Navigator (which is a separate subscription), a domain, a team of SDRs, and time spent configuring, the monthly per-user cost is a small piece. A cheaper tool that makes you assemble three point solutions is not cheaper.

5. Reporting Has to Tie to Pipeline, Not Opens

Open rates are vanity. Reply rates are better, but still not enough. What we needed was: which sequence produced booked meetings, and what did that cost? Mailshake's reporting isn't the fanciest I've seen. But it gave us enough to make decisions. If you're RevOps, don't let a demo seduce you with beautiful dashboards. Ask if the data can be exported to Sheets or BI.

6. Quality Control Has to Be Built In

This is the one I'm most opinionated about. Can you preview every email before it sends? Can you check what merge tags look like? Can you approve a campaign before a junior SDR starts sending to 1,000 people? The tool should make quality checks easy.

The Result and the Honest Bottom Line

We ended up keeping Mailshake. Not because it's the best at any one thing—in a way, that's a relief. It's not the prettiest tool, and it's not the cheapest, and it doesn't have the fanciest AI. What it did was fit our workflow: cold email, email verification, a simple HubSpot sync, and LinkedIn automation that didn't make me want to hide in a compliance meeting.

But more importantly, the evaluation process was the win. We built a repeatable checklist and forced ourselves to test real scenarios, not demo scenarios. I'd rather spend 10 minutes explaining why deliverability matters than deal with a new tool that burns our domain in month one.

If you're evaluating a prospecting tool for your RevOps team, here's my one piece of advice: stop reading feature comparisons first. Start with the workflow you'll actually use, then ask the vendor to show you that workflow in the trial. If it takes more than an afternoon, that's okay. The right tool should feel boringly reliable.

Also: send a test email. Trust me on this one.