Revenue Execution
Reactivation
The cheapest pipeline you have is the pipeline you already paid for.
- Part of
- Revenue Execution
- Owned at
- Action layer
- Typical effort
- Campaign, 4 to 8 weeks, or recurring
- Runs on
- HubSpot, Salesforce, Zoho, Odoo or Pipedrive
- Part of the discipline
- What is revenue operations
Why it breaks
The operating problem
Most databases hold years of leads that said not now, opportunities lost to timing, and customers who quietly stopped buying. Nobody owns them, so they are re-acquired at full cost or never touched again.
Self-check
Signs you need this
Dormant value is easy to confirm. Sort your database by last activity date and the answer is visible in one screen.
- Leads from two years ago have never been touched again.
- Closed-lost is a graveyard, not a list.
- Customers stop buying and nobody notices.
- You buy new leads while old ones sit unused.
- Nobody owns the dormant database.
Page boundary
Where this capability ends
Reactivation works the existing database. Demand Generation creates new demand. Customer Revenue designs the retention logic that should have prevented the loss.
Customer Revenue
Structure onboarding, retention, renewal, expansion and reactivation.
Lead Management
Define lifecycle, ownership, prioritization, nurture and recycling rules.
Demand Generation
Campaign programs that create and capture buying signals.
Concrete intervention
What Revops delivers
Reactivation runs on segmentation and restraint: who is eligible, who is suppressed, what is offered and where the record goes afterwards.
- ModelDormant segment definition and scoring
- RulesReactivation eligibility and suppression rules
- ModelSequence design per segment
- DefinitionOffer and reason-to-return framework
- RulesRecycling rules back into the lifecycle
- RoutineReactivation campaign calendar
- DashboardRecovered pipeline dashboard
The reasoning model
How ROUTE applies
ROUTE applied backwards. The signal here is silence, and the work is deciding which silence is still worth a conversation.
Recognize
Find the records that went quiet, and the reason they did.
Organize
Segment by loss reason, age, value and fit.
Understand
Decide which segments are worth a touch today.
Trigger
Trigger the right sequence, offer and channel.
Execute
Run it, then return the record to a live lifecycle state.
The operating architecture
Revops OS mapping
Reactivation is an Action capability with an unusual input: it reads history rather than new signal, which makes segmentation the whole game.
- 01
Data
Loss reason, last touch, age, historic value.
- 02
Context
Which dormant records still match the current ICP.
- 03
Workflows
Eligibility, suppression and recycling rules.
- 04
Action primary layer
The reactivation calls, sequences and offers.
- 05
Control
Recovered pipeline, reactivation rate by segment.
Outcomes
What changes
Recovered pipeline is reported separately from new pipeline, because mixing the two hides how cheap recovery actually is.
- Dormant database segmented and owned.
- Loss reason drives which sequence is used.
- Recovered pipeline measured separately from new.
- Every touched record returns to a defined state.
- Suppression rules protect the brand from over-contact.
Questions
Frequently asked
Will this damage our brand?
How old is too old?
Is this the same as a newsletter?
Next step
Where this gets repaired.
Reactivation is a natural first campaign after a data repair, because the records have already been paid for once.