The Handoff Test: Does Your Cold Email Target a Department or the Person Who Inherits the Mess?

Most cold email pitches a department, not a person, because a department is easier to research than someone's actual problem. You can tell which one you're looking at in under a minute, using a test I run on every sequence I write, including my own.

The Handoff, Not the Department

I didn't invent this angle. I first ran into it in Alan Ruchtein's cold email writing, and the core move is simple: stop anchoring an email to an industry or a department ("we help sales teams," "built for HR leaders") and anchor it instead to the crack between two functions, the seam where work crosses from one team to another and something gets lost on the way through. Context. Accountability. Data quality. Speed. SDR to AE. Marketing to sales. Sales to customer success. For a lot of the mid-size companies I work with in Israel, it's IT to procurement, or HR to finance.

Not every company has a clean handoff like that. Plenty of the businesses I work with are closer to traditional Israeli SMB than multi-team enterprise orgs, and forcing a handoff where none exists produces the same generic email you started with, just dressed up. Use this where a real one is identifiable, not everywhere.

The Test, Three Steps

1. Find the handoff. Not the department that owns the process, the seam where the work actually moves and something breaks crossing it. If you can't name what specifically gets lost, context, accountability, data quality, or speed, you haven't found a handoff yet. You've found an org chart.

2. Write to the person who inherits the mess, not the person who owns the process. IT picks the equipment. IT isn't the one who has to defend a budget line that ran over, or explain to finance why the cheaper option means a refresh in eighteen months instead of three years. Procurement inherits that tension. Write to procurement, not to "the IT department."

3. Close on a two-path question, not a meeting ask. Take the two real tensions you named in step 2, and ask which one they're actually fighting right now. It's a specific question a busy person can answer from their phone, not a request to find fifteen minutes on a calendar.

Before and After

Here's what step 1 alone gets you wrong, using a company selling IT hardware into mid-size organizations as the shape of the example (no client names, this is illustrative):

Before, department-level, generic:

Subject: Better procurement for your IT team

Hi [Name], I noticed your company is growing and will likely need to upgrade its IT infrastructure soon. We help IT departments source better equipment at lower cost. Would you be open to a quick call this week to talk about how we could help your team save time and money?

Nothing here is wrong exactly. It's also addressed to nobody. "IT departments" isn't a person with a specific tension, and "save time and money" is true of every vendor pitch ever written.

After, applying the test:

Subject: Who's actually defending the number, IT or you?

Hi [Name], IT usually picks the spec. You're the one who has to defend the number when it comes in 15% over budget, or explain to IT why the cheaper option means a refresh in eighteen months instead of three years. Curious which side of that you're fighting more right now: the flexibility IT wants, or the number you have to sign off on. If it's useful, happy to send over what a locked-in versus open licensing structure actually costs a company your size over three years. No meeting needed, just say the word.

Same product, same sender. The second version names the actual seam (IT selects, procurement pays and defends), addresses the person who lives with that tension, and closes with a real either/or instead of a generic ask. It also offers to send something rather than drop a link, because that's the other rule I hold cold email to: no catalog or PDF links before a reply, offer and send.

Run This on Any Agency's Copy, Mine Included

Ask three things of any sample email an agency shows you, before you sign anything:

Does it name a real handoff, the specific place where work crosses functions and something breaks, or does it just describe a department?

Does it address the person who inherits the resulting pain, or the person who merely owns the process?

Does the close ask a real question tied to what the email just said, or does it default to "do you have 15 minutes"?

If a sample fails on any of the three, you're paying for volume, not judgment. Run the test on my copy before you sign anything. I'll walk you through exactly which handoff every pitch was built around.