- Sales
- v1.0.0
- signals
Buying signals ranked by purchase correlation
Use this skill when prioritizing outreach, building signal-based campaigns, or setting up intent tracking — 6 buying signals ranked by purchase correlation: former customers and alumni users, new leadership, high-intent website visits, tech stack changes, expansion, and hiring or downsizing.
SKILL.md
6 Buying Signals (Ranked by Purchase Correlation)
1. Former Customers & Alumni Users (Highest Correlation)
Why it works:
- Trust already established + known playbook
- Faster proof of value
Query: Previous users of your product at new companies
Outreach timing: Immediately upon detection
2. New Leadership ≤90 days
Why it works:
- Mandate for early wins
- Vendor amnesty period
- Budget air cover for new initiatives
Query: LinkedIn job changes, press releases
Outreach timing: Days 14-45 (peak engagement window)
3. High-Intent Website & Content
Why it works:
- BOFU pages: pricing, competitor comparisons, demo, integrations
- Shows active evaluation
Query: Website visitor tracking, content downloads
Outreach timing: Within 24-48 hours (highest intent signal)
Reply rate: 25-30% (they know you)
4. Tech Stack Change
Why it works:
- Active change project indicates openness
- Fresh pain from transition
- New gaps in workflow
Query: BuiltWith, job postings mentioning new tools
Outreach timing: 1-2 weeks after detection
5. Expansion (Raise, New Region/Product)
Why it works:
- Board targets create urgency
- Scale pain emerges
- Standardization moment
Query: Crunchbase, press releases, job postings
Outreach timing: 2-4 weeks after announcement
6. Hiring or Downsizing
Why it works:
- Hiring = ramp pressure, need efficiency
- Downsizing = do-more-with-less mandate
Query: LinkedIn company growth, layoff news
Outreach timing: 1-2 weeks after pattern detected
Signal Performance Benchmarks
| Outreach Type | Reply Rate |
|---|---|
| Cold outreach | 6-8% |
| Signal-based | 18-22% |
| Multi-signal stacked | 35-40% |
Key insight: Signal-based outreach = 3-4x higher contract values
Combines with
| Skill | Why |
|---|---|
clay-buying-signals-5 |
Implement signals in Clay workflows |
gtm-plays-11 |
Match signals to specific GTM plays |
cold-email-4-sequence |
Build sequences around each signal |
bridgebound-in-market-20 |
Deep-dive on in-market triggers |
Example prompts
Which buying signal should I prioritize for a $50K ACV enterprise deal?
Create an outreach strategy combining job change + funding signals for fintech companies.
How do I detect tech stack changes for companies using Salesforce?
Part of Frontal — free, open GTM skills for your AI agent. Browse the library →
Files
1 file ship with this skill. They are installed beside the SKILL.md.
Buying signals ranked by purchase correlation
Imported from the GTM Skills library by Swan (https://www.gtmskills.com), skills/alex-vacca/buying-signals-6
at https://github.com/swan-gtm/gtm-skills/commit/5d786aad0c7b2ca59b1abf1f601f9407ca261996. Written by Alex Vacca (https://linkedin.com/in/alex-vacca).
The skill is shared under the MIT License below; this notice must stay with any copy.
MIT License
Copyright (c) 2026 Swan
Permission is hereby granted, free of charge, to any person obtaining a copy
of this software and associated documentation files (the "Software"), to deal
in the Software without restriction, including without limitation the rights
to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
copies of the Software, and to permit persons to whom the Software is
furnished to do so, subject to the following conditions:
The above copyright notice and this permission notice shall be included in all
copies or substantial portions of the Software.
THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
SOFTWARE.