When your champion moves: the pull-in

Your most valuable contact at a customer isn’t the friendly one. It’s the champion. The contact who actively believes in your company. Who would defend you in a procurement meeting you weren’t invited to. Who, when they change companies, takes you with them.

When that contact leaves the customer, most BD teams treat it as a loss. The CRM pings the rep: contact no longer at this account. The rep updates the record, marks the relationship inactive, and moves on. That’s the wrong move. The contact didn’t disappear. They moved to a new account. And if they were a champion at the old one, the strongest predictor of where your next deal comes from is wherever they just landed.

This piece is about the champion pull-in: a recurring, high-ROI pattern that most BD teams miss because their CRM is built to track deals, not portable relationships. Naming the pattern, learning to see it in your own book of business, and acting on it within a week is one of the highest-yield moves in services BD.

A composite pattern

A senior BD leader at an enterprise services firm described the pattern in a stakeholder interview. A contact left one of his customers. Joined a company in a sector the firm wasn’t actively building in. Within 18 months, the contact had hired six other people who knew the firm’s work, and collectively they pulled the firm into a contract in a vertical that hadn’t been on the forecast.

The deal didn’t show up in any pipeline review. It came from a relationship signal that the CRM didn’t track and the BD team didn’t watch for. The contact wasn’t a customer of the firm at the new company. They were a believer who had moved to a new place and brought the firm’s reputation with them. They told the right people. The right people called.

The pattern repeats often enough that any senior BD leader in a relationship-driven business can name two or three versions of it from their own career. It almost never gets credited correctly. The CRM logs the deal as inbound. The actual mechanism (a champion moved, took us along, opened a door we didn’t know existed) is invisible.

Friendly, Supporter, Champion

Most BD teams collapse all “friendly” contacts into one bucket. Three distinct tiers sit inside that bucket, and the differences predict who pulls you into deals at their next company.

Friendly contacts take meetings, respond to your emails, and tell you they like working with your team. They might or might not advocate for you internally. They probably won’t bring you to the next company if they leave. They’re a feature of the current relationship, not a portable asset.

Supporters are positive about your work and see value, but their belief peaks during an active engagement and fades when the project ends. They might advocate when asked. They probably won’t initiate. The Challenger Sale makes a related point about Mobilizers: the friendliest contact is rarely the real champion. The real champion has the will and credibility to move things forward, even when no deal is on the table.

Champions actively believe in your company. They advocate when there’s a deal in front of them and when there isn’t. They mention you in conversations that have nothing to do with your category. They send you opportunities you didn’t know existed. They tell people about you at every job they ever have, and when they change companies, they take you with them. Most BD careers produce three to ten champions total. Their commercial value is enormous and almost completely uncaptured by traditional BD systems.

The Spark Score for a person quantifies the distinction on a 0-100 scale: scores of 80+ indicate belief that travels across years and roles; 60-79 indicate positive-but-unconvinced; below 60 are friendly contacts that decay at the natural rate without active engagement. Champion, Supporter, and Friendly are concepts for thinking about contacts; the score is how the system measures them.

Why most BD teams miss champion moves

Three reasons, all structural.

The CRM models the contact, not the relationship. When a contact moves to a new company, the CRM record at the old company gets marked inactive. The contact at the new company is a new record. The relationship that connects the two records, the relationship your team built over years, doesn’t exist as a first-class object in the schema. It can’t, because the schema was built for pipelines. The portability of the relationship layer (the asset that should follow the person, not the company) is the structural piece CRMs miss.

The notification system is wrong. Most BD teams find out about contact moves through LinkedIn (when the contact updates their profile) or through inbound (when the contact emails them). Both are slow signals. The team learns weeks or months after the move, by which point the champion has been onboarding at the new company without any contact from your team. The window where reaching out is high-impact (within a week of the move) usually closes before the team knows the move happened.

The team doesn’t separate friendly from champion. When the friendliest contact leaves an account, the team’s reaction is often “we lost our champion.” When the champion leaves the same account, the reaction should be “an opportunity just opened at wherever they landed.” Most teams react identically to both moves because the contact list doesn’t carry the distinction. Without the labels, the difference between losing a friendly and gaining a foothold at a new account is invisible.

The fix to all three is the same: make the relationship the first-class object, watch for moves automatically, and segment the people-you-care-about list by belief level. SavvySpark’s contact movement tracking surfaces job changes within days; the Spark Score for a person scores belief on a 0-100 scale, distinguishing high-scoring believers from contacts who are merely friendly; the LinkedIn integration provides the early signal so the rep gets a notification before the inbound email. All of that is product mechanics. The strategic insight (treat champion moves as alert events, not as losses) comes first.

The seven-day champion reactivation playbook

When a champion moves, the playbook is the opposite of the playbook for a cold target. It’s relationship maintenance at the working level, not pursuit. The window is roughly a week.

Day 1-2: Notice the move. Either the contact tells you (rare), they update LinkedIn (common, 1-3 day lag), or your CRM-LinkedIn integration tells you (best, near real-time). The instant you learn, do not assume the contact remembers you uniformly across the years; check the relationship history. When did you last meaningfully engage. What was the last thing they advocated for. What’s the right context to re-enter the relationship.

Day 3-4: Send the no-ask outreach. A short, specific note. Reference something concrete (the project five years ago, the dinner two years ago, the introduction they made in 2023). Congratulate them on the move. Ask one question about the new role that signals you’ve thought about what their job will look like, not just that you noticed they have one. Do not pitch. Do not ask for a meeting at the new company. Do not mention your services at all. The point of the outreach is to confirm you remember them as a person, not as a pipeline opportunity.

The champion will read this as the right gesture if it’s the right gesture. They’ll read it as extractive if it isn’t. The difference is whether the prior relationship was built on generosity. Give and Take makes this point: dormant ties reactivate well for givers and poorly for takers, because the dormant contact remembers what the original interaction was actually about. If you treated the champion as a person before, the seven-day outreach lands. If you treated them as a pipeline ticket before, it doesn’t.

Day 5-21: Do not follow up. This is the part most BD teams get wrong. The champion is in their first weeks at a new company. They are drowning in onboarding, learning their team, figuring out who they need to know. Pestering them in week one is the wrong move. Plant the connection. Let it sit. They will surface when they’re ready to surface, and they will surface specifically because you didn’t push.

Week 4-6: Light, useful, no ask. A relevant article. An introduction to someone who would help them at the new role. A piece of work you did in their new vertical that they could read for context. Each touch is a deposit, not a withdrawal. The compounding effect of three or four well-placed deposits across the first quarter of their new role is that the champion becomes a champion at the new company too. From there, the pull-in pattern starts working.

Month 3-6: Watch for the pull-in. When it comes, it usually doesn’t look like a deal. It looks like an introduction, a meeting invitation, a question. “Hey, can you talk to my colleague Sarah about X?” That’s the pull-in. The deal that follows is downstream, three to six months further out, often credited to whoever fielded the meeting rather than to the years of relationship that produced it.

The compounding effect

A single champion, identified, nurtured, and reactivated correctly across a decade, can pull a firm into multiple deals at multiple companies. Three champions produce a quiet, durable side-pipeline that doesn’t show up in outbound metrics but accounts for a meaningful share of revenue.

The compounding works in two directions. Each pull-in produces a new account where the firm has at least one believer. That believer becomes the seed for new relationships at the new company. Some of those new relationships produce champions of their own. Over five to ten years, a BD leader who systematically tracks champions, watches for moves, and runs the seven-day reactivation playbook builds a personal pull-in pipeline that travels with them.

The compounding fails when the firm doesn’t capture the relationships at the firm level. If the relationship layer is portable for the person but not for the firm, the BD leader’s champions leave with them when they retire. That’s the same pattern from the senior-leaving problem: the asset goes to zero on the day the person walks out. The firm-level fix is the same: make the relationship the first-class object, capture it where the team can see it, and track it across personnel changes.

For the broader case on relationship intelligence as a category, see why your best relationship intelligence lives in someone’s head. For the measurement framework that credits champion reactivation as a leading indicator, see the broken scorecard.

To identify the champions in your own book of business, download the Champion Identification Worksheet (5-signal scoring rubric, applied across your top 50 contacts): download the worksheet. The worksheet is a simplified way to do this. In the app, the same five signals plus several others (email cadence, response patterns, explicit belief ratings, contact movement) feed into each contact’s Spark Score on the same 0-100 scale, computed continuously.

To see how SavvySpark tracks contact movement, scores belief at the person level, and surfaces champion reactivation candidates automatically, look at our solutions or start a free trial.