Monday morning. A LinkedIn notification tells you that Priya, the director of platform engineering who championed your deal at her last company eighteen months ago, just started as VP of Engineering at a logo you've been trying to crack for two quarters. New title. New budget. New mandate to prove herself fast. And a vendor she already trusts, because she ran the eval that picked you last time.
That's the signal. The clock started the day she updated her profile, and the window is roughly 14 days before the moment cools.
I'm going to walk through how I'd run this, the same way I run scenario-led outbound at Grafana Labs, because a champion job change is the cleanest buying scenario there is. It's not an inferred intent signal scraped from a third-party data vendor. It's a person you have a real relationship with, landing somewhere you want to be, at the exact moment they have budget and a reason to move fast.
Why the 14-day window is real
A newly promoted or newly hired VP is at the high-water mark of their willingness to make a decision. They were hired to change something. The first 90 days are when they get to bring in the tools and partners they trust without inheriting blame for the existing stack. By month four, they own the stack they walked into, and switching costs start to feel like their problem instead of the previous regime's.
The 14-day number isn't a hard cutoff. It's the window where you get the easiest yes, because you're catching the relationship while the memory of working with you is warm and the urgency of the new role is peaking. Wait a quarter and you're still in a decent spot. Wait two and you're competing with whoever got there in week one.
The playbook, day by day
Here's the sequence I'd run. It assumes you've already confirmed the job change is real and the champion's relationship with you was genuinely positive, not just polite.
Days 1 to 2. Confirm and map. Don't reach out yet. First, figure out what you're walking into. Is Priya inheriting a competitor you'd be replacing, or a greenfield? Who else from her old buying group moved with her, and who's already at the new account? Map the new buying committee before you touch it. This is the part most reps skip, and it's the part that decides whether you show up looking like a partner or like a vendor who set a job-change alert.
Days 3 to 5. The personal note, not the pitch. The first touch is a genuine congratulations with zero ask. You worked together. You're happy for her. One line that signals you remember the specifics of what you built together, not a templated "saw you moved, let's talk." If the relationship is real, this lands as a friend reaching out. If you open with a meeting request, you've told her the relationship was always a pipeline entry.
Days 6 to 9. The warm-path decision. Now the operator question. Do you go direct, or do you route through a stronger super-connector? Sometimes the champion herself is the path. But sometimes there's a better one: a mutual customer she respects, an investor who backs both companies, a partner already inside the new account. If a higher-credibility path exists, use it. A direct note from you says "I remember you." An intro routed through someone you both trust says "people you respect vouch for these people." Pick the path with the most credibility, not the most convenience.
Days 10 to 14. The specific, low-friction ask. By now you've congratulated her, you've mapped the account, and you've chosen your path. The ask is narrow and easy to say yes to. Not "let's do a full eval." Something like a 20-minute conversation about how she's thinking about the problem you both know you solve, given her new scope. The specificity is the tell that you did the homework. The low friction is what gets it on the calendar inside the window.
The framework underneath: Relationship Heat
Cam Wright, who writes the Go To Market Operator newsletter out of his seat at Grafana Labs, has the sharpest public framework for why static account tiering fails. His argument, in Go To Market Operator (https://www.gtmoperator.dev/p/replacing-static-account-tiering), is that you should rank accounts dynamically on live signals instead of freezing them into A, B, and C tiers once a year. He tells a story about a Tier-A rep who missed a Tier-C account that had just raised 500 million dollars, a roughly 250-thousand-dollar ACV slip, because the tiering was static and the signal was dynamic.
He's right. And there's one dynamic factor his framework doesn't name, which is the one most predictive of whether you actually close: Relationship Heat.
Dynamic account ranking usually scores funding, hiring, tech-stack changes, and intent. All useful. All things your competitors can also see, which is Cam's own point: "a signal everyone has access to cannot, by definition, be an advantage." A champion changing jobs is different. It's a dynamic signal, it spikes account priority overnight, and it's proprietary to you, because the relationship that makes it valuable is yours. Nobody else's tiering model knows that Priya trusts you. Relationship Heat is the missing axis in dynamic account ranking: not just is this account heating up, but are my relationships into it heating up, and right now.
That's the extension. Score accounts dynamically, like Cam says. Then add the one dynamic factor that's actually yours.
Why this is a sales motion now, not a customer-success afterthought
Who owns this kind of relationship work has changed, and it's worth naming because it changes who should be running the playbook above.
Norwest Venture Partners' 2025 Business-to-Business Sales and Marketing Benchmark Report (survey of 177 leaders, August 2025) found that account-executive and sales ownership of renewals rose from 33 percent in 2023 to 54 percent in 2025, while customer-success ownership dropped from 56 percent to 29 percent. Renewals used to be relationship management, handled by CS. Now they're a sales motion. The relationship is sales-owned.
Champion job changes are the prospecting-side version of exactly the same shift. The warm path that follows a champion into a new account isn't a nice-to-have that customer success stumbles into. It's net-new pipeline that belongs to the same sales motion now owning renewals. If your org has moved renewals to sales because relationships are a revenue asset, then champion tracking belongs in the same place, for the same reason.
The support-layer problem
Here's the catch, and it's the reason most teams will read this playbook, nod, and never run it.
Catching a champion job change inside a 14-day window, mapping the new committee, finding the strongest warm path, and routing the ask is real work. It requires monitoring every past champion across every target account continuously, which no rep does manually, because reps are running 40 to 60 accounts and a full cold sequence on top.
This is the asymmetry again. The closing side gets sales engineering, deal desk, and a CRO who shows up on the big deals. The prospecting side gets a dashboard and a job-change alert nobody has time to act on. A champion moving to a target account is one of the highest-value prospecting signals that exists, and it usually dies in a notification feed because no part of the support layer is built to catch it and run the 14 days.
That's the gap. The signal is proprietary, the window is short, and the work is continuous. It's exactly the kind of motion that needs to be orchestrated rather than left to whoever happens to notice the LinkedIn update. Notice, map, route, ask, inside two weeks, every time, across every champion. Do that and a job change stops being a thing you missed and becomes the warmest pipeline you'll source all quarter.
.png)
