The New-in-Role Buyer Read: Reach Now, Time It, or Pass

You found a newly appointed decision-maker at a target account. The question is not whether role changes matter in general - it is whether this specific person is worth your time, and which week to send the first touch. This guide gives founders, account executives, SDR leads, and partnerships teams a scored, dated read on a single new-in-role contact, built only from public signals.

Most trigger references stop at "a leader changed, so reach out." That leaves the two hardest calls to improvisation: how buyable is this one person, and when. This guide closes both. You will score the strength and remaining life of the buying window, then convert days-since-start into a one-sentence verdict - reach this week, hold for a named week, or pass.

Why a new leader is a buying window at all

A newly appointed decision-maker is buyable because organizational change, not persuasion, drives purchases, and a new leader is the purest form of that change. Gartner's research finds 99% of B2B purchases are driven by organizational change, with a new leader, merger, or funding round starting the buying project. The window is a budget-timing artifact, not a goodwill one.

The mechanism is money and calendar. New executives spend 70% of their budget in their first 100 days, often re-purchasing tools they trusted at a previous company. Across 660K+ prospects, Directors, VPs, and C-level leaders were 2.5X more open to evaluating new tools and services within their first three months than after a year. Both of those headline numbers trace to a single vendor's data, so treat them as vendor-sourced rather than peer-reviewed - but the direction holds across independent context. Per the 6sense 2025 Buyer Experience Report, 94% of buying groups rank their preferred vendors before first contact, and buyers split roughly 60/40 between independent research and engaging sellers.

Read those two facts together and the whole job snaps into focus. If most of the budget commits inside 100 days, and buyers pre-rank vendors before they ever talk to a seller, then being right about the week is worth more than being warm. Waiting a quarter often means missing the stack review entirely.

The dimensions that decide buyability

Buyability is not one thing. It is the product of four dimensions, and a contact that scores high on one can still be a pass if it fails another. Score each one before you let days-since-start drive the decision.

• Mandate scope. Does this title own the category you sell, and does the company's size give it real budget? A new VP of Sales or CRO is under maximum pressure to show early pipeline momentum, has fresh eyes on the stack, and has political capital to change it. Stack ownership sits with ops - the VP of RevOps, Director of Sales Ops, Head of Marketing Ops, or the CRO. For infra, CIOs and CTOs must justify rip-and-replace spend to the board.
• STARS tempo. Michael Watkins's STARS model names five transition situations - Start-up, Turnaround, Accelerated Growth, Realignment, Sustaining Success - each calling for a different pace. A turnaround demands decisive cuts and buys fast; a sustaining-success role rewards evolutionary tweaks and buys slowly or not at all.
• Carried preference. Did this leader bring a vendor relationship with them? Past champions who change jobs convert at 3x normal lead rates. That is the single strongest signal - when you have it.
• Days-since-start. This sets the phase and therefore the timing of the touch. It does not, on its own, decide buyability.

Here is the insight that reorders the stack: when a carried preference is present, it outweighs days-since-start. A prior champion converts at 3x, yet 91% of past champions never came back on their own even 90+ days into a new job. The switch is latent, not self-activating. A strong carried preference means you can reach a day-85 contact that the phase model alone would tell you to pass.

Which roles carry the strongest mandate

The mandate to review and replace vendors concentrates in a short list of titles, and it is uneven across them. For GTM and revenue tooling, revenue leadership and ops hold it. For infrastructure, the CIO and CTO hold it but face more scrutiny per decision.

The counterintuitive part is that a bigger addressable pool does not mean a faster window. In Refolk's index of professional profiles, the US holds roughly 2.3x as many current CTOs and VPs of Engineering as it does CROs and VPs of Sales, yet the infra leader's mandate is weaker per head because board scrutiny on rip-and-replace slows the decision. Volume and buyability move in opposite directions here.

Counts above come from Refolk's index at VP and CXO seniority, with RevOps counted across VP, Head, and Director. The ratio column is derived from those counts. The RevOps pool is a tenth the size of the sales-leadership pool, which matters for how you build a repeatable play: a RevOps-only new-in-role motion runs out of fresh targets fast.

The title caveat is load-bearing. At a 10-person startup a "VP of Sales" may be a solo contributor with no team and no budget authority; at a 5,000-person company the same title is a senior executive with a multi-million-dollar budget. Because these titles are self-reported on LinkedIn, pairing every title with company size is the single highest-yield check you can run.

Reading carried preference without wishful thinking

A carried vendor preference is the highest-value signal you can find, and the easiest to misread. Grade it, because the public record offers signals of very different reliability and only one of them is near-certain.

The high-confidence signal is the one in your own CRM: a named champion who moved. That is the 3x converter. Treat the prior company's stack as a hypothesis worth testing, not a fact. Treat a LinkedIn post praising a category as attention, never budget - a post is aspirational, not committed. The failure here is reading enthusiasm as intent, so grade before you score.

This is also where sourcing the contact cleanly matters. Finding the day-50 CROs who previously championed your product, across accounts you do not already track, is the part that usually eats an afternoon of manual cross-referencing.

Swap the named product for your own and you have the carried-preference pool pre-filtered. From there, step 5 of the procedure is a grading pass, not a hunt.

Mapping days-since-start to a dated verdict

The timing half of the read runs off one number: days since the detected start date. Three practitioner day-maps disagree only on the front edge and converge in the middle.

All three agree that day 1 to 7 is noise and that days roughly 30 to 60 are prime. The real argument is day 8 versus day 31 for the front edge, and that is exactly the call STARS tempo settles per case. A turnaround leader buys fast, so the teardown camp's day 8 to 21 window fits. A sustaining-success leader is still orienting at day 20, so FirstSales's day 31 start is safer.

Because job moves are typically detected within days to weeks of the actual change, the detected date lags reality. A profile that looks like day 20 may be day 40. When the LinkedIn start month and a press release conflict, treat the contact as later, not earlier - erring late costs you a slightly cooler touch, while erring early costs you the one first impression.

The scoring procedure

Run these eight steps in order on the contact in front of you. The first seven take about an hour total; the eighth, only if you reach, takes another hour because the message is the deliverable.

The output of step 7 is a single sentence you can paste into the account record. Use the template below so the verdict is unambiguous and re-checkable later.

[Name], [Title] at [Company, size band], started ~[date] (day [N]).
Mandate: [owns / does not own] [category]. STARS: [situation].
Carried preference: [flag] (reliability: [high/medium/low]).
VERDICT: [Reach this week] / [Hold until week of [date]] / [Pass; revisit only on fresh trigger].

How this goes wrong

The failure modes below are where a clean-looking read turns into wasted touches or a burned first impression. This is the most valuable part of the standard, so give it weight before you trust any verdict.

• Stale detection date read as fresh. Moves surface days to weeks late, so day 20 may really be day 40. Check the start month against a press release; on conflict, treat as later.
• Interim mistaken for mandated. A caretaker acting head often cannot sign, but an interim with a stated turnaround brief is buyable. People frequently do not flag interim status and just update the title, so read the appointment announcement for a change mandate, not the title string alone.
• Title without budget. A VP at a 12-person startup may own nothing. Pair every title with company size before scoring - this is the quiet disqualifier that sinks the most reads.
• Lateral move scored as a reset. An internal promotion or lateral into the same stack carries no fresh-eyes mandate; they already own the tools. Confirm the prior title was at a different company.
• Blank-page outreach. The most common failure is handing a rep a name and a date and stopping. Without a teardown you have a faster congrats email, and the reply rate proves it.
• Carried-preference wishful reading. A LinkedIn post praising a category is attention, not budget. Only a prior-vendor relationship in your CRM is high-confidence; grade every other signal down.
• Treating 70% and 2.5X as independent fact. Both trace to one vendor's data. Use them to set direction, but label them vendor-sourced if you cite them to a prospect or a leader.
• Reaching in days 1 to 7. You are noise and you spend the one first impression for nothing. Hold to the named week.

Before you call the read done

Run this checklist on every contact before the verdict leaves your hands. It is the difference between a scored decision and a guess with a date stapled to it.

Keeping the read current

A new-in-role read has a short shelf life, so build in a re-check rather than treating the verdict as permanent. The two time-sensitive inputs are days-since-start, which moves every day, and the appointment facts, which can be revised as detection catches up.

Set a recheck for any "hold" verdict on the week you named. When that week arrives, re-run the disqualifier gate - interim status can resolve, budget scope can clarify, and a lateral move can be confirmed - then recompute the phase. For "pass" verdicts caused only by a stale date, keep the record warm and reopen it if a fresh trigger appears: a funding round, a reorg, or a known renewal date. Roughly 20% of CRM contacts change jobs in a year, so your pool of new-in-role targets refreshes continuously without any new sourcing effort - the discipline is catching them in the prime window rather than at day 95.

Two numbers are worth re-deriving from the live record rather than quoting from memory. The pool sizes shift as the market grows, and the geography gap is wide: in Refolk's index, the US revenue-leadership band is about 18x the size of the UK band for the same seniority. A geography-blind new-in-role play starves outside the US, so size the pool for your target market before you commit a quarter to this motion. The framework is universal; the volume is not.

Finally, re-check the day-map sources against your own reply data. The three practitioner maps agree on the middle and argue about the front edge, and your own results on turnaround versus sustaining-success contacts are the tiebreaker. If your day-8 touches to turnaround leaders outperform your day-31 touches, trust your data over any single source.