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.
In this repository32 other files it gives its agents.
- ai-personalization-promptsSkill
- atl-btl-messagingSkill
- bridgebound-firmographic-15Skill
- bridgebound-history-16Skill
- bridgebound-in-market-20Skill
- bridgebound-relationship-39Skill
- bridgebound-symptoms-11Skill
- buying-signals-6Skill
- clay-enrichment-9stepSkill
- cold-call-scriptsSkill
- cold-email-4-sequenceSkill
- cold-email-templates-34Skill
- email-1-variations-7Skill
- email-metrics-benchmarksSkill
- email-writing-frameworksSkill
- frontal-messaging-templatesSkill
- gtm-philosophySkill
- gtm-plays-11Skill
- inbound-triggers-30Skill
- josh-braun-copywritingSkill
- lead-sources-guideSkill
- linkedin-campaign-completeSkill
- linkedin-limits-warmupSkill
- linkedin-success-factorsSkill
- list-building-tipsSkill
- outbound-triggers-6Skill
- outreach-4-categoriesSkill
- personalization-6-bucketsSkill
- personalization-hooksSkill
- personalization-playbooksSkill
- sdr-master-promptsSkill
- sdr-outbound-rulesSkill
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
- Distinctive: line 92
Instead, use signal to inform timing and angle
≈ “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.
Files
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 →
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
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.

