Try Valley
Put your outbound workflow to work.
Saniya Sood
Published:
Updated:
Published October 8, 2026 · Updated October 8, 2026
The answer in 60 words: companies stuck on aging tools leave artifacts in public, and the clearest one is a job req asking for experience with the old system. This play fingerprints the legacy tools from those reqs and docs, finds the modernization owner, often a newer leader brought in to fix exactly this, and sends a message that sells the upgrade path rather than insulting the stack. One run, LinkedIn only.
This article describes the play exactly as published on joinvalley.co/playbooks on October 8, 2026. Valley makes the product, so read it as the maker's own guide, not a review.
Valley is an AI outbound platform that finds the people most likely to buy from you - from live buying signals, natural-language search, or your own lists - qualifies them against your ICP, researches each one, and sends personalized messages across email and LinkedIn that get 15-45% reply rates, against a category average of about 2%.
► Run this play on your own ICP: 7 days free, every feature on
Give your sales team
an unfair advantage.
Who this play finds, and why they reply
A company does not announce that its sales engagement platform is ten years old. It posts a job asking for three years' experience with it, and that is the tell, in the play's words. Legacy systems modernization is a budget line at most companies that have grown past their first tools, and the person who owns it is usually new and motivated.
The example on the play: companies still running sales engagement on legacy platforms, showing in job posts and docs. Scout builds the fingerprint from the tools your product replaces.
How the play runs
The flow, as the product shows it: Deep Search › Find buyers › Research › LinkedIn.
Scout fingerprints the legacy tools (AI step). Job reqs asking for experience with them are the tell.
Finds the modernization owner (AI step). Often a newer leader brought in to fix exactly this.
Messages sell the upgrade path. Not "your stack is old." Rather "here’s what the switch looks like."
Before you launch
Describe your target market so Scout can find the right starting point.
Setting | Value |
|---|---|
Audience | High + medium fit |
Cadence | One-time |
Cadence tag | One-time |
Sending channel | LinkedIn only |
Example search
Companies still running sales engagement on legacy platforms, showing in job posts and docs
Review the audience, message and sending settings before starting. The channel shown is the sending channel for this play, not the source of its prospects.
Give your sales team
an unfair advantage.
What the message says
Not "your stack is old." Rather "here's what the switch looks like." That is the play's rule, and it matters because the reader often inherited the stack and knows its problems better than you do. The message sells the upgrade path: what moving looks like, what it costs in time, what it fixes first.
The research step reads the reqs and docs, so the note can name the specific legacy tool and the specific pain it creates at a company like theirs.
When this is the wrong play
You replace a modern competitor, not a legacy tool. Displace a competitor is the play for a current rival.
The legacy tool leaves no public trace. Internal systems with no job reqs or docs cannot be fingerprinted. Leadership changes catch the leader hired to fix it from the other side.
You want it refreshed. This runs once; re-run it quarterly as reqs change.
Related plays
Displace a competitor: Companies publicly using the tool you replace. The category is sold, the vendor is not.
Using complementary technology: Their stack tells you they are your buyer before they do.
New exec, new budget: A just-hired VP or C-level in your buying seat rethinks the stack in their first 90 days.
Open the play itself: Modernizing off a legacy stack on the Valley playbook library, or browse all 58 plays.
► Want to see this play run on your accounts? Book a demo
FAQ
How do I find companies on legacy software? Scout fingerprints the legacy tools from job reqs asking for experience with them and from public docs. Those are the artifacts aging software leaves.
Who gets the message? The modernization owner, often a newer leader brought in to fix exactly this.
What does the message say? It sells the upgrade path, what the switch looks like, rather than criticising the stack.
Is it one-time? Yes. Run it again as new reqs appear.
Does it work for any category? Any category where the legacy tool shows up in reqs or docs.
How this page was made: the facts were read from the sources named in the text on October 8, 2026; drafted with AI assistance; fact-checked, reviewed and edited by Saniya Sood.
