Try Valley
Put your outbound workflow to work.
Saniya Sood
Published:
Updated:
Published October 8, 2026 · Updated November 11, 2026
The answer in 60 words: a company hiring for the role your product automates has budgeted a salary for the problem. This play maps your product to the job description, finds live open reqs with Deep Search and refreshes as new ones appear, finds the hiring manager who owns the headcount, and sends a message that reframes the hire. For Valley, that role is the SDR; for you, it is whatever your product does.
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
Companies hiring SDRs are the clearest example, which is why the keyword is in the title, but the play is general: the job description is your feature list in prose, in the play's words. A req for a role that your product automates or augments is a budget line already approved, a problem already named, and a manager already comparing options.
The timing is tight. A req is open for weeks, not quarters, so the play refills daily and the message goes to the person comparing candidates right now. The example on the play: companies with an open req for the role your product automates or augments.
How the play runs
The flow, as the product shows it: Deep Search › Find buyers › Research › LinkedIn.
Scout maps your product to the req (AI step). The job description is your feature list in prose.
Deep Search finds the open reqs (AI step). Live postings, refreshed as new ones appear.
Finds who owns the headcount (AI step). The hiring manager comparing candidates has a budget line already approved.
Messages reframe the hire. "Before you fill that role" is a first line that gets read.
Before you launch
Describe your target market so Scout can find the right starting point.
Setting | Value |
|---|---|
Audience | High + medium fit |
Cadence | Watch · refills daily |
Cadence tag | Refills daily |
Sending channel | LinkedIn only |
Example search
Companies with an open req for the role your product automates or augments
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
"Before you fill that role" is a first line that gets read. The play says so, and the reason is that it is about the reader's decision this week. The message reframes the hire: the salary they have approved could buy the outcome instead, and the research step says what that looks like at their company.
The recipient is the hiring manager who owns the headcount, not the recruiter running the process. Recruiters fill seats; managers own budgets.
When this is the wrong play
Your product does not replace or augment a role. Then no req maps to it. Hiring signals work from roles that signal the problem, which is a wider net.
You sell to the person being hired. A tool for SDRs should reach the SDR team's leader, not pitch replacing the SDR. Use the hiring-signals play with the manager as the buyer.
The reframe feels adversarial in your market. Some buyers resent being told not to hire. The copy is editable; soften the opener and keep the timing.
Related plays
Hiring for roles that signal your problem: A job post is a company announcing a gap. Catch them while it hurts.
Headcount surge: Companies growing over 20% a year are buying tools this quarter, not someday.
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: Hiring the role you replace on the Valley playbook library, or browse all 58 plays.
Related: Legacy Systems Modernization · Firmographic Data · LinkedIn Ad Library · Valley pricing
See also: How to Reach People Publicly Complaining About a Competitor · LinkedIn Profile Views: How to Message the Viewers Who Fit Your ICP · How to Find Similar Companies to Your Best Customers (Lookalike Prospecting)
► Book a demo: see how Valley would find, research and message your buyers
FAQ
What is the alternative to hiring an SDR? Software that does the repetitive part of the job, finding the right people, researching them and sending the first message, while a person keeps the conversations. That is the pitch this play sends to companies with an open SDR req, and it is how Valley works as an AI outbound platform. The SDR cost comparison sets one SDR's salary and benefits against the software options.
How do you scale outbound without hiring more SDRs? Automate the research and the first touch, keep a person on the replies, and spend effort only on accounts showing a buying signal such as hiring, funding or a job change. Valley runs outreach from those signals on LinkedIn; the LinkedIn outreach automation guide covers the safe setup.
Why target companies hiring SDRs? An open SDR req is an approved budget for pipeline. A product that produces pipeline can be offered against that salary.
Does this only work for SDR roles? No. Scout maps your product to whatever role it automates or augments.
Who gets the message? The hiring manager who owns the headcount.
What does the message say? It opens with 'before you fill that role' and reframes the hire as an outcome your product delivers.
How often does it refresh? Daily, as new reqs appear.
