Benchmark Learnings: Emailing HR

HR isn't ignoring your email. They're ignoring your tone.

The single biggest pattern in the data is this: HR buyers respond to warmth. They punish anything that feels transactional.

This makes sense when you think about what HR leaders do all day. They deal in people. Their job is culture, engagement, belonging, experience. When you land in their inbox sounding like you're reading from a script — or worse, a product spec sheet — you're speaking a language that's fundamentally at odds with how they process the world.

Here's a summary from what the data shows is working and not working when emailing HR:

What works: Warm, respectful tone with human-centered language. Specific pain points. Brevity with clear benefit framing. A simple CTA.

What doesn't: Overly transactional tone. Generic templates. Getting too technical too early. An unclear ask.

If you're selling into HR and your emails sound like they could just as easily be sent to a CFO or a CTO, that's the problem.

But tone is only one dimension. What you say — and how you frame it — also depends on who you're talking to inside HR. A CHRO and an HR coordinator don't think about the same things. So let's break it down by seniority.

Selling to HR Executives (CHRO, VP of People, Head of HR)

Titles you're targeting: CHRO, Chief People Officer, VP of People, VP of HR, VP of Talent, Head of People, Head of People Operations, Head of Talent Acquisition

What the data says about executives: C-Suite buyers reply at 4.8%, VPs at 3.4%, and Heads at 4.4%. But the real story is in the A-email lift — Heads of departments see a 42% jump in reply rates when emails are well-written using Lavender. That's the highest lift across the executive tier. This is likely because Heads typically operate in smaller companies or hold a more execution oriented role in a larger company.

What this means for HR execs specifically: They want outcome-first value props tied to the highest levels of strategy: revenue, cost, or risk. But,  they want those outcomes framed through a people-first lens. A CFO cares about the time it takes to get to a cost reduction number. A CHRO cares about cost reduction as a byproduct of better retention or more efficient processes that free their team up.

The tone still needs to be warm. But the altitude of how you frame the value needs to be strategic.

What to do

Lead with a company-level observation. Connect it to a people challenge that shows up at their stage or scale. Frame the outcome in terms of what it means for their people team and the organization, not your product's feature set. Keep it short. Keep it human. Encourage them to delegate the work to folks lower in the organization.

What not to do

Don't lead with product features. Don't get technical about integrations or platform capabilities, that's a conversation for a lower seniority. Don't use hyped-up language. And don't ask vague questions like "is this on your radar?" A CHRO always has 15 things on their radar. Be specific about which one you're solving.

Example: You're an AE at Lattice, emailing a VP of People

You noticed their company just crossed 500 employees and recently shared a post about building a new manager enablement program.

Michelle,

The manager enablement work you've been sharing is really thoughtful (especially at 500+, where the gap between "good manager" and "winging it" gets a lot more visible)

Usually at this stage manager quality starts to vary a lot across teams. But, people teams don't have a consistent way to see where the gaps are until review season. Too late to stop folks from leaving.

Worth seeing how other 500-person cos (ex. Slack and Postmates) are tackling this with Lattice? Let me know if this would be a better convo for someone else on your team.

Why it works:

The Opener: using terms like really thoughtful related to their writing creates warm familiarity.

The Problem: While the specifics of problems faced at their size are clear, the problem ties back to a big cost (people leaving)

The Solution: There isn't an overly technical explaination of how Lattice solves this. The tone says "want perspectives on how others are solving this?" instead of pitching a solution. Collaborative > transactional.

The Ask: In addition to the invite to the collaborate, there's also an invitation for the executive to delegate.

Selling to HR Directors and Senior Leaders

Titles you're targeting: Director of People Operations, Director of HR, Director of Talent Acquisition, Director of Employee Experience, Senior HR Business Partner, Senior Director of People

What the data says about this tier: Directors reply at 3.4% overall, one of the lowest across all seniority levels. Senior-level buyers are even more responsive to quality: their overall reply rate jumps to 8.4% on A emails, the biggest absolute lift in the dataset.

This group is underserved by good outbound. That's your opportunity.

What this means for HR directors specifically: Directors and senior leaders care about functional priorities. They're less interested in company-wide strategy (that's their VP's job) and more interested in specific use cases that map to what they own. If you can show you understand the program or process they're running and where it's breaking, you win.

What to do

Anchor on a specific & relevant use case instead of a broad platform pitch. Connect your observation to something they're functionally responsible for: onboarding, performance cycles, engagement surveys, talent reviews. Show proof from a similar company or stage. Keep the CTA simple and relevant to their world.

What not to do

Don't pitch at the "transform your HR function" altitude, that's not their decision. Don't use broad or multiple value props. Don't write long intros. And don't use overly salesy language. This group, more than most, will disengage the moment your email starts sounding like a pitch instead of a conversation.

Example: You're an SDR at Lattice, emailing a Director of People Operations

You noticed their company recently posted several roles for the same team, suggesting a reorg or team build-out.

Priya,

Looks like the product team is growing fast! Betting your crews been busy with the 6 new openings I saw on LinkedIn this week. How's the prep for that growth going for you?

Seems like a big stress test for the onboarding processes. People ops tends to fly blind on whether managers are actually running it consistently.

If you could flag what managers are behind on their onboarding milestones, would that help you out?

One of our customers in a similar growth phase cut their "time to full productivity" from 90 days to 45.

Worth a quick look at how they set it up?

Why it works:

The Opener: Asks how the growth pressure is affecting them personally. This creates immediate warmth that is accentuated by the informal tonality of the writing.

The Problem: The problem is specific to the workflows people ops owns.

The Solution: The solution isn't presented as a pitch. Instead its positioned as a question to see if they'd find a solution helpful.

Credibility: The customer story is directly tied back to the problem and solution. While it doesn't drop a specific name, the outcomes are directly tied to KPIs they'd care about.

CTA: The ask is a call to gain perspective on how folks use Lattice to solve the problem. This avoids a transactional tone.

Selling to HR Managers

Titles you're targeting: HR Manager, People Operations Manager, Talent Acquisition Manager, HR Business Partner, Benefits Manager, L&D Manager, Compensation Manager

What the data says about managers: Managers across all departments reply at 4.3%, but A emails lift that to 6.3% — a 49% improvement. Managers are highly responsive to quality, but they need a very different email than what works for their VP.

What this means for HR managers specifically: Managers live in the tactical layer. They're running the processes, not designing the strategy. They care about practical usefulness: how does this make the thing I do every day easier? Abstract strategy language without tactical relevance is the fastest way to lose them.

They also respond to a friendly but professional tone. This adds emphasis to the need to create a warm friendly tone with this persona. Think: a helpful colleague who gets it.

What to do

Focus on a specific workflow they own and show you understand where the friction is. Be clear about what problem you're solving and how. Offer a concrete next step — not "thoughts?" but something they can say yes or no to. Structure the email so it's easy to scan. Short paragraphs. Clear benefit.

What not to do

Don't talk about company-wide transformation. Don't use vague value props. Don't write walls of text. And especially for HR managers: don't lead with technical details or product jargon. They don't want to evaluate your tech stack — they want to know if their Tuesdays are about to get easier.

Example: You're an SDR at Lattice, emailing an HR Manager

You noticed their company's Glassdoor reviews mention inconsistent feedback across teams.

Kevin, I was looking at Glassdoor.

A few recent reviews mentioned inconsistent feedback across teams. Has that created any blowback internally?

(Can only imagine the team's been getting pressure to figure out a fix)

You and I both know, managers probably want to give good feedback. It's a bandwidth issue. No system to do it consistently.

Our tool's lightweight framework keeps "feedback" from piling up at review time. We got an HR team's feedback from once a quarter to twice a month. No manager pushback.

Would a 15-minute walkthrough be useful to see how they set it up?

Why it works:

Opener: Glassdoor can be a touchy subject. Asking if it's created blowback and sympathizing that you understand they might be under pressure creates warmth and an "I'm on your side" vibe.

The problem: The "you and I both know" language builds credibility again through warmth. It shows good intention, disarming a potentially touchy subject.

The solution: The solution is a specific workflow for giving feedback. This wouldn't resonate with a director or a VP. But, it speaks to the work relevant to a manager.

The CTA: The ask is specific. to how others are having success with the workflow.

Formatting: The message breaks up paragraphs into easier to skim sections (great for managers).

Selling to Individual Contributors in HR

Titles you're targeting: HR Generalist, People Partner, HR Coordinator, Recruiter, Talent Acquisition Specialist, HR Analyst, People Programs Coordinator, Onboarding Specialist

What the data says about ICs: Individual contributors across all departments have a 5.3% reply rate — higher than most seniority levels. When they receive A-level emails, that jumps to 8.0% — a 49% lift. ICs are one of the most responsive groups in the dataset.

What this means for HR ICs specifically: ICs care about outcomes tied directly to their work. Not the department's strategy, not the company's vision — their day-to-day. They want brevity, clarity, and relevance. If you can name the exact thing they're spending too much time on and show them a way out, they'll reply.

The tone should be the warmest in the entire seniority ladder. HR ICs process information through a people-first lens, and they respond to emails that feel like a real person wrote them — not a sequence tool.

What to do

Keep it short. Really short. Name the specific task or workflow you think they're dealing with. Make your outcome tangible and immediate — not "strategic" or "transformational" but "this saves you 3 hours a week." Frame the CTA as something low-stakes.

What not to do

Don't talk about ROI, strategic priorities, or organizational outcomes — that's not their world. Don't write long emails. Don't use dense paragraphs. Don't use salesy language or unclear next steps. And don't assume they have buying authority — your goal is a conversation, not a close.

Example: You're an SDR at Lattice, emailing a People Partner

You noticed their company recently promoted several managers internally and announced it in a Slack community.

Alex,

Saw a few new manager promotions announced — congrats to the team!

New managers usually mean new questions. Am I off in thinking your stepping in as an unoffical coach for those first time managers?

If we can give you some playbooks to make this easier would it help?

Why it works:

Length: This email is shorter than the rest

Personalization: This level in the organization doesn't typically see personalized emails. This creates reciprocity to respond.

Tone: Congrats, am I off, these are both examples of informal additions that bring warmth to the message.

CTA: The ask is a call to be helpful so they can drive better outcomes specific to the challenge they face. There's no pitch. Instead they get value from responding to the email.

The throughline

HR is a department that rewards warmth and punishes templates. That's true across every seniority level in the data.

But what changes as you move up and down the ladder is the altitude of the problem you're solving.

For a CHRO, it's about organizational patterns at scale — retention, manager quality, culture consistency.

For a director, it's about programs they own — onboarding, performance cycles, talent reviews.

For a manager, it's about making a specific process less painful.

For an IC, it's about making their Tuesday afternoon easier.

The tone stays warm throughout. But the frame shifts. And most sellers don't shift it. They write one email and send it to everyone in the department. The data says that's why 87.7% of emails to HR don't earn an A.

The fix isn't complicated. It's just specific:

Match the warmth they expect. Match the altitude to the seniority. And give them a reason to believe you've done the work to understand their world — not just their title.

If you want to see the full benchmarking data across all departments, seniority levels, and industries, the Cold Email Benchmark Report is live.

And if you want to write emails like these — with real-time coaching adapted to your buyer — see what Lavender can do for you.

‍