← All skills
  • Sales
  • v1.0.0
  • signals

Clay buying signals

Use this skill when setting up signal-based Clay tables, prioritizing outreach triggers, or building intent-based campaigns — 5 buying signals for Clay workflows with performance benchmarks and workflow tips.

SKILL.md

5 Buying Signals for Clay Workflows

1. Recent Job Changes (0-90 days)

Why it works:

  • 3x higher response rate
  • Peak engagement: days 14-45
  • They're actively building their stack

Clay setup:

  • Track LinkedIn job changes
  • Filter by title/seniority
  • Alert within 24 hours of detection

2. Company Hiring for Specific Roles

Why it works:

  • Signals budget allocation
  • Shows growth trajectory
  • Indicates priority areas

Clay setup:

  • Monitor job postings (LinkedIn, Indeed)
  • Filter by relevant roles
  • Track posting volume/velocity

3. Website Visitors

Why it works:

  • 25-30% reply rate (they know you)
  • Highest intent signal
  • Act within 24-48 hours

Clay setup:

  • Integrate RB2B or similar
  • Enrich visitor data
  • Auto-route to outreach sequence

4. Funding Announcements

Why it works:

  • New budget available
  • Mandate for growth spending
  • Reach out 2-4 weeks after

Clay setup:

  • Crunchbase integration
  • Filter by round size
  • Delay outreach 2-4 weeks

5. Technology Changes

Why it works:

  • Active buying window
  • Fresh pain from transition
  • Open to new solutions

Clay setup:

  • BuiltWith integration
  • Track additions/removals
  • Filter by relevant tech

Performance Benchmarks

Outreach Type Reply Rate
Cold outreach 6-8%
Signal-based 18-22%
Multi-signal stacked 35-40%

Signal Workflow Tips

Don't Mention Signal Explicitly

  • Prospects get these constantly
  • Instead, use signal to inform timing and angle
  • Reference the underlying pain, not the trigger

Act Fast

  • Hot signals expire in 3-7 days
  • Job changes: days 14-45 optimal
  • Website visitors: within 24-48 hours

Stack Signals for Heat Scoring

  • 1 signal = Standard priority
  • 2 signals = High priority
  • 3+ signals = Reach out same day

Signal Priority Matrix

Signal Priority Timing Reply Rate
Website visitor Highest <24 hours 25-30%
Job change High Days 14-45 20-25%
Funding Medium-High 2-4 weeks 18-22%
Hiring Medium 1-2 weeks 15-20%
Tech change Medium 1-2 weeks 15-18%

Combines with

Skill Why
buying-signals-6 Strategic view of all signals
clay-enrichment-9step Integrate signals into workflow
gtm-plays-11 Match signals to specific plays
cold-email-templates-34 Get templates for each signal

Example prompts

Set up Clay to detect job changes and auto-route to outreach.
How do I stack multiple signals for heat scoring in Clay?
Create a workflow that detects funding + hiring signals together.

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.

NOTICE1.4 KB
Clay buying signals
Imported from the GTM Skills library by Swan (https://www.gtmskills.com), skills/alex-vacca/clay-buying-signals-5
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.