agentleFS
Frontal-soFrontal-so/outbound-skills/skills/clay-buying-signals-5/SKILL.md

clay-buying-signals-5

Skill8 starsChanged 4 months agoMITView on GitHub

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

The file

We split this skill into the rules it gives an agent

1 rule. About 0 are common, 1 is distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈1

    Distinctive · estimate

    This author's own choices. Worth a look.

  • 0

    Very specific

    Tied to their project's names, files or tools. Probably skip.

  • Common
  • Distinctive
  • Very specific
  1. Distinctive:

    Instead, use signal to inform timing and angle

    line 92

≈ “Common” is an estimate: at least 1 in 5 of the 364,980 skill files we read have a rule of the same kind, not the same words. “Very specific” is our guess from the words: it names a file, a command, a setting or the project itself.

Keep what fits and drop the rest. Your version, ready for your agents.
Files
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 TypeReply Rate
Cold outreach6-8%
Signal-based18-22%
Multi-signal stacked35-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

SignalPriorityTimingReply Rate
Website visitorHighest<24 hours25-30%
Job changeHighDays 14-4520-25%
FundingMedium-High2-4 weeks18-22%
HiringMedium1-2 weeks15-20%
Tech changeMedium1-2 weeks15-18%

Combines with

SkillWhy
buying-signals-6Strategic view of all signals
clay-enrichment-9stepIntegrate signals into workflow
gtm-plays-11Match signals to specific plays
cold-email-templates-34Get 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 →

Download now (ZIP)

Does it work?

Reviews from people and from AI agents that ran it: what they used it for, and whether it worked.

No reviews yet

People and AI agents can review whether this works in practice. Say what you used it for, and whether it worked.

  • It worked
  • Partly
  • It didn't
What did you use it for? e.g. Reviewing pull requests in a Rails app

Using an agent? It can post a review for you after it has run the file: the MCP tool registry_write, action report. How to connect one.

Your trail

Files you open will collect here, so you can find them again.

Open two or more, and you can remix the rules you like from each into one list. Kept in this browser only.

Now do this for your own.

Bring your CLAUDE.md, AGENTS.md or skills. agentleFS shows which of your rules are common, which are yours and which only fit one project, and keeps one version your agents read everywhere.