How to message a decision maker who just started a new role

A new hire in a decision making seat is worth reaching early, but the generic version of that message is now as crowded as the funding announcement it copied the idea from.

Published 2026-09-08 by Deberli. About 8 minutes to read.

A new VP of Marketing starts on a Monday. By Wednesday her inbox has eleven LinkedIn messages that all begin the same way: congratulations on the new role. Two mention a mutual connection that does not exist. None of them say anything she could not have guessed a stranger would write the moment her job title changed. She reads the first line of each, and then she stops reading.

New hires in a decision making seat are a real signal, close in spirit to the funding announcement we wrote about last week. Someone new is now responsible for a set of tools and vendors they did not choose, has a stretch of time before anyone expects them to have settled opinions, and is genuinely more open to a new conversation than the person who held the seat for three years. The problem is the same one funding rounds have: everyone with a job change alert already knows this, and the inbox fills before lunch on day one.

What she already deleted

Hi Sarah, congrats on the new role at Northwind! Wishing you the best of luck. If you're ever looking to improve how your team handles outbound, would love to connect and share what we do.

The congratulations is not personalisation, it is a mail merge on a job title change. It requires no more research than watching her name appear in a notification, and she knows that, because she got ten more just like it. Nothing in the message is wrong exactly. It is just proof that nobody read past the headline.

What the move actually changes

The useful question is not that she is new, it is what being new lets her do that the previous person in the seat could not. A new leader can retire a tool nobody liked without defending the original decision to buy it, because it was not their decision. A new leader can also be blamed less for trying something and having it not work out, in the first few months, than for leaving an obvious problem untouched. Both of those are real openings, and neither shows up in a message that only says congratulations.

The other thing worth noticing: a person new to a seat has not yet inherited the vendor relationships as loyalties. They have inherited them as defaults, which is a much weaker attachment, and defaults are what get replaced first.

Hi Sarah, saw you moved into the VP Marketing seat at Northwind. Most people in that spot spend the first month figuring out which of the existing tools they actually want to keep. If outbound tooling is one of the ones you are still deciding on, happy to send over what your predecessor's setup looked like from the outside, no call needed.

That message could not have been sent to someone who had held the role for two years. It also gives her an easy no: she can ignore it, or she can say she already decided, and either answer is more information than silence.

The window closes faster than the role settles

The new-hire signal itself stays technically true for months, a person is new for as long as they are new. But the window where a message about it reads as unusual rather than as one of a pile is much shorter, for the same reason a funding round's window is short: everyone with the same alert fires it in the same first week.

The specific version, built on what being new actually changes rather than the fact of the move, still gets read in month two. The generic version is competing with everyone else's alert by the second week.

None of that is a reason to wait. It is a reason to skip the congratulations and go straight to the thing that is actually true about being new, which almost nobody else writing that week bothers to say.

Where to find the detail that makes it specific

Their own announcement post. People who post about a new role often say what they are excited to build or fix, which is a more honest brief than anything in the job posting.
What the company was doing before the hire. A newly created title, versus a straightforward replacement of someone who left, implies a different mandate and is usually stated somewhere in the announcement or the company's own hiring post.
Public complaints or comments from their previous role, if any exist, about the category you sell into. A person who criticised a workflow publicly two jobs ago rarely changes their mind about it just because the job did.
The size and stage of the new team. A first senior hire into a function that did not have one before behaves differently from someone replacing a predecessor into an established team.

What we don't know

We do not have a measured reply rate for this signal specifically. Our own numbers, 60 campaigns launched and 6,004 prospects sourced and ranked, with 29 percent of invitations accepted and 7 percent of messages getting a positive reply, are blended across all eleven signals we watch, not broken out by trigger type, and job changes are not yet one of the eleven. The reasoning above is a pattern worth testing against your own results, not a statistic we can cite precisely.

How Deberli fits into this, and where it does not yet

Recently changed jobs is a signal we have built but not switched on, the same honest answer we gave in the guide on candidate side signals. What is live today are the profile filters, title, seniority, location, industry and company size, which will surface a person in a new seat if you are already watching that company through funding or growth, but nothing yet flags the move itself the day it happens. If this signal matters to how you prospect, that is useful for us to hear, not a feature we are going to claim already exists.

If you take one thing

Do not congratulate the move. Say what the move changes. Everyone with a job change alert can manage the first sentence. Almost nobody bothers to read past the headline to write the second one, and that is the one she actually reads.