Introduction
Relationship history becomes useful when new evidence changes the reason a deal was lost. A past champion moving jobs and a closed-lost account reopening are related but distinct plays. Monitor the full closed-lost book for changed decision-makers, incumbent timing, operating changes, and relevant new problems before restarting a conversation.
Relationship signals fix part of that. A relationship signal is a meaningful change in a known contact, account, opportunity, or buying context. It tells a team what to investigate next. It does not authorize automatic outreach.
Buyers often stall rather than refuse. Dixon and McKenna's HBR study of 2.5M recorded sales conversations found 40%-60% of deals ended in indecision, not a clear no.
This article covers two plays: using verified past-champion changes to find opportunities and protect accounts, and using new evidence to decide when a closed-lost account deserves another conversation.
Key Takeaways
- A champion's job change is two events: an opportunity at the new employer, and a risk at the old account.
- Reopen closed-lost deals only when new evidence changes the original loss condition.
- Verify identity, fit, ownership, status, and contact rules before any customer-facing step.
- Judge the program by decision quality and commercial progression, not alert volume.
What Are Relationship Signals in Revenue Operations?
Closed-lost accounts contain relationship history, known requirements, and a recorded reason a deal did not proceed. Reopening is justified when new evidence changes that original reason, not simply when a sequence reaches the next quarter. Keep the lost reason and previous buying group as the baseline.
- Job changes and promotions
- New stakeholders or leadership changes
- Renewed activity from known contacts
- Budget, planning, or technology events
- A shift in the condition that caused a loss
Relationship, intent, and buying signals
These are different things. LinkedIn's own alert taxonomy, per Sales Navigator's help documentation, separates a saved lead's role change and account updates from engagement alerts it labels buyer intent. That is a platform taxonomy, not an industry standard, but the distinction is useful.
A relationship signal gives context and access. Intent or buying signals need separate evidence of an active need or project. A job-change alert alone proves neither.
Classify the evidence
Tag every signal one of three ways:
- Verified fact: a confirmed role change, account status, CRM update, or documented event.
- Supported hypothesis: a reasonable reading that needs validation, such as a former champion gaining influence in a new role.
- Unsupported assumption: calling someone a champion, assigning budget authority, or inferring purchase intent without evidence.
Only verified facts justify action. Hypotheses justify investigation. Assumptions get discarded.
Past Champions: Turn Former Advocates Into New Opportunities
Who actually qualifies as a past champion
A friendly contact is not a champion. Neither is an end user or someone who sat through a demo. MEDDPICC separates a Champion, who has power, influence, and credibility and will actively advance the deal, from a Coach, who helps but lacks one of those traits.
Look for CRM evidence:
- Documented advocacy for your solution
- Internal influence and access to stakeholders
- Ownership of the business problem
- Willingness to push a prior decision forward
If the history is thin, say so in the record. Preserve the uncertainty.
Verify the person and the destination
Before treating a move as actionable, confirm:
- Identity, current employer, title, and timing of the move
- Whether the role is relevant to what you sell
- Whether the new company fits your target-account criteria
- Whether the account already has an owner, open opportunity, customer or partner relationship, exclusion, or live conversation
Separate what is confirmed from what you are guessing about their budget, authority, or priorities.
Run two coordinated plays
Destination play. Prepare a reconnection grounded in the prior relationship, the person's new mandate, and a credible problem you may solve. Don't imply they endorsed your product unless the record supports it.
Origin play. Review the former account for relationship risk:
- Who replaced the champion?
- What opportunities, renewals, or expansions are exposed?
- Which additional contacts do you need?
Gong's analysis of customer sales conversations associates more buyer-side participants with won deals, though that is correlation, not proof of cause.
Assign each play to the right owner so a destination-account effort never collides with the existing account team.
Keep outreach short and restrained
Write a brief, human note. Acknowledge the change, offer something relevant, and ask one focused question. Skip the sequence.
Sometimes the right move is an internal brief, a research task, a warm introduction, or a hold. Stop entirely when:
- The move is unverified or the account is a poor fit
- The person now works for a competitor
- Contact restrictions apply or ownership is unclear
- The history is stale
- Outreach would require disclosing private customer information
Closed-Lost Accounts: Reopen the Right Conversations
Start with the loss reason
Connect the event to the lost reason. A budget objection may need evidence of a funded expansion; an incumbent lock-in may need verified renewal timing; missing executive support may need a changed buying owner. Record the observation, source, date, commercial hypothesis, and what still requires confirmation.
Time passing is not a signal. A valid reactivation thesis ties new evidence to the condition that blocked the deal. Keep closed-lost, no decision, disqualified, inactive, and active records in separate buckets. One re-engagement rule should not cover them all.
Look for evidence that changes the condition
Credible triggers include:
- A new decision-maker or leadership change
- A budget or planning event
- Contract or renewal timing
- Restructuring, funding change, or a new mandate
- Technology replacement
- Renewed engagement from known stakeholders
For each, answer three questions: what changed, why it matters to the original loss, and what evidence would disprove the thesis.
Government contractors have formal events to watch. GSA's Forecast of Contracting Opportunities lists planned procurements with estimated award dates, but GSA states it is for planning only and carries no purchase commitment. Treat a forecast as a lead to investigate, and confirm through SAM.gov.
Prioritize before assigning outreach
Sort records by:
- Account fit
- Relationship strength
- Evidence relevance
- Stakeholder continuity
- Loss-reason quality
- Current ownership
Then pick one of four outcomes:
- Retain closed-lost status
- Investigate further
- Route to a new owner
- Approve a narrowly defined re-engagement
Avoid unsupported predictive scores. If you score, document the fields, evidence, review process, and reason codes.
Write a message that respects history
- Acknowledge the earlier evaluation without treating the contact as a new prospect
- Tie the new evidence to one specific reason to revisit
- Ask whether things have changed, not assume they have
- Include proof that addresses the original objection
- Skip "just checking in"
Set stop rules and ownership first
Pause outreach when:
- The loss reason is unchanged
- An opportunity is already active
- Another team owns the relationship
- The contact opted out
- The record is restricted
- The evidence can't be verified
Define how replies, meetings, objections, and corrections update the CRM and halt other automated touches. Keep "re-engaged," "meeting booked," "qualified opportunity," and "closed-won" as separate outcomes.
Build a Governed Relationship-Signal Workflow
Capture the right context
Recommended CRM fields:
- Contact role and champion confidence
- Prior relationship and last substantive interaction
- Account and opportunity status, loss reason
- Current owner and destination account
- Signal source, timestamp, evidence excerpt, record link
- Review date
- Do-not-contact status, exclusions, active sequences, customer or partner status
A seller should be able to inspect exactly why a signal surfaced.
Resolve before you act
Verification steps:
- Verify identity and deduplicate records
- Confirm current employment
- Check ownership
- Classify the account
Send uncertain cases to an "investigate" state rather than forcing a match or inferring a buying role from a title. Every signal ends in one of four outcomes with a recorded reason: act, investigate, hold, or reject.
Choose the smallest justified action
Escalate in steps:
- Internal research
- Account brief
- Owner notification
- Stakeholder mapping
- One-to-one outreach or a reviewed sequence
Coordinate at the account level so several reps don't hit the same person. Keep executive relationships, customer relationships, unclear identity, and private CRM context behind human approval.
Tie AI to reviewable logic
AI can summarize history, compare the old loss condition with new evidence, flag gaps, and draft internal briefs or message angles. Before anything goes out, humans must review:
- Recipient and relationship claims
- Commercial context and sources
- Timing, channel, and stop conditions
Automation runs configured rules. It doesn't establish customer truth, buying authority, legal permission, or revenue attribution.
Compliance matters here too. The FTC says CAN-SPAM covers B2B commercial email, and opt-outs must be honored within 10 business days.
Close the feedback loop
Log these by signal type:
- False positives and stale data
- Identity corrections and rejected hypotheses
- Duplicate touches and owner overrides
- Replies and outcomes
Watch for sources, rules, or segments that keep producing low-value work. Change one rule at a time so you know what helped.
Measure Relationship-Signal Performance and Operationalize It
Measure evidence to outcome
Track the full path:
- Source quality, freshness, and match quality
- Owner resolution and review completion
- Hold and rejection reasons
- Duplicate touches prevented
- Relevant replies, meetings, qualified opportunities, stage progression
- Revenue under your attribution policy
Keep alert volume, emails sent, meetings, pipeline, and wins as separate measures so activity isn't mistaken for impact.
Compare plays with consistent cohorts
Report destination champion plays, origin retention plays, and closed-lost re-engagement separately. Build internal benchmarks against comparable cold, nurture, or standard reactivation motions. No universal benchmark exists.
UserGems reported that 91% of key contacts at its study vendors hadn't repurchased on their own. That figure is a vendor-reported cohort with no disclosed denominator, so don't treat it as a norm.
Record the bad outcomes too:
- No action
- Bad data
- Opt-outs
- Competitive displacement
- Stalled deals
- Confirmed closed-lost
Where Intellectible fits
Intellectible can be configured into a signal operating system with:
- Visual workflow builder and connected data sources
- Human-review steps and project workspaces
- PostgreSQL databases and published interfaces
Its CRM Engine supports custom record types, fields, relationships, queues, and dashboards for evidence review, ownership routing, and audit trails.
Its Revenue Discovery engine follows a Detect → Gate → Promote → Draft → Approve → Call → Qualified sequence. It includes four human approval gates, drafts everything, and sends nothing automatically. There is no bulk email, no LinkedIn automation, and no auto-CRM writes. You connect your own signal sources; Intellectible doesn't natively supply every external feed.
The aim is to scale the process, not headcount: less repetitive review and coordination, with accountable people still deciding the consequential calls.
Frequently Asked Questions
When should a closed-lost deal be reconsidered?
Closed-lost accounts contain relationship history, known requirements, and a recorded reason a deal did not proceed. Reopening is justified when new evidence changes that original reason, not simply when a sequence reaches the next quarter. Keep the lost reason and previous buying group as the baseline.
Which events can justify a new review?
Look for a new decision-maker, an incumbent contract approaching a documented end, a relevant complaint about the provider, a new location, or a failed audit that could change the need. These are research prompts, not automatic evidence that the account now wants to buy.
How should the event connect to the original loss?
Connect the event to the lost reason. A budget objection may need evidence of a funded expansion; an incumbent lock-in may need verified renewal timing; missing executive support may need a changed buying owner. Record the observation, source, date, commercial hypothesis, and what still requires confirmation.
How are champion changes different from reactivation?
Resolve the current account, parent, contact role, and ownership before contacting a past champion. A former supporter at a new company is a different account play; it does not by itself reopen the original opportunity. Respect previous objections and any outreach restrictions.
How can teams monitor the full closed-lost book?
Monitor every eligible closed-lost account through permitted CRM history and relevant public sources. Use contact-now, research-needed, nurture, and monitor queues, with one owner and a source-backed reactivation brief. Do not create a duplicate opportunity simply because a fresh alert arrived.
How should reactivation performance be measured?
Measure verified reactivation candidates, seller acceptance, reopened opportunities, subsequent sales acceptance, and pipeline without double-counting old deals. Record reasons for staying closed. The goal is a disciplined return to a changed situation, not repeated follow-up on an unchanged loss.
