agentleFS
automatewithudayautomatewithuday/gtm-prospecting-system/skills/buying-signals/SKILL.md

buying-signals

Skill1 starsChanged 59 days agoMITView on GitHub

Use when stage 9 of the prospecting system needs buying signals attached to qualified accounts — funding, hiring, new-in-role, tech changes — each with a source URL and a real event date. Also use standalone to design a signal taxonomy and scoring model.

The file

We split this skill into the rules it gives an agent

5 rules. About 0 are common, 5 are distinctive, and 0 are very specific to this project.

  • ≈0

    Common · estimate

    Many files like this have a rule of this kind.

  • ≈5

    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:

    All intent signals fall into one of four categories, each with different reliability and actionability:

    line 47
  2. Distinctive:

    Not all signals are equal.

    line 110
  3. Distinctive:

    Every signal should map to a specific outreach angle:

    line 219
  4. Distinctive:

    Don't chase every signal. Pick 2-3 signal types that correlate with your highest close rates and build systematic monitoring around just …

    line 264
  5. Distinctive:

    Create a feedback loop: track which signal types lead to the most meetings.

    line 267

≈ “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

Intent Signals

Pipeline contract

Stage 9 of 20. Reads 08-leads.csv. Writes 09-signals.csv (account_domain, signal_type, signal_detail, source_url, event_date, collected_date, confidence).

  • One row per signal, not per account. No signal found = no row. Never write a placeholder signal.
  • event_date is when it happened, collected_date is today. A signal without a source_url does not get written.
  • Verify every signal before it is written — research sub-agents get this wrong more often than they get it right. For each one: fetch source_url and confirm it resolves (not 404, not an unrelated page); confirm the page is about THIS account_domain and not a same-named company (Array the fintech vs Array Technologies the solar firm; hellotilt.com vs tilt.app); confirm event_date is inside the window. A live job post with no posting date is recorded with date_precision=observed. A source that blocks fetching is kept out until a human opens it. Log every drop with its reason.
  • Cheap sources first: GetLeads MCP list_funding_signals / list_acquisition_signals (1 credit per record), then job boards and the company site.
  • Per-signal collection playbooks: references/ (hiring surge, fundraising, new-in-role, tech on website, job-posting language, champion moves). Signal-to-message mapping: references/trigger-mapping.md.

Files live in runs/<run>/. Column definitions: /prospecting-system. Standalone use: ignore this block.

When to Use

  • Building signal-based outbound campaigns (vs. spray-and-pray)
  • Setting up monitoring systems for real-time prospect alerts
  • Prioritizing which accounts to contact first from a large list
  • Training SDRs or AI systems on what qualifies as a meaningful buying signal

Framework

What Intent Signals Are

An intent signal is any observable action or change that suggests a company or person may be ready to buy. It's the difference between "this company matches our ICP" (fit) and "this company matches our ICP AND is actively looking for a solution" (fit + intent).

Fit alone: "They're a 200-person SaaS company in our target industry." Fit + Intent: "They're a 200-person SaaS company that just posted 3 SDR job openings, raised a Series B last month, and their VP Sales is engaging with content about outbound scaling."

Intent signals don't guarantee a sale. They guarantee relevance — which is the single most important factor in cold outreach conversion.


The Intent Signal Taxonomy

All intent signals fall into one of four categories, each with different reliability and actionability:

Category 1: First-Party Signals (Highest Reliability)

Actions the prospect takes that directly involve your brand.

SignalReliabilityUrgencyExample
Visited your website (specific pages)Very HighHighViewed pricing page twice in one week
Downloaded your contentVery HighMedium-HighDownloaded "Outbound Playbook" guide
Attended your webinarVery HighMediumRegistered and attended live
Replied to previous outreach positivelyVery HighVery High"Not now, but reach back out in Q2"
Free trial or demo requestVery HighCritical—
Opened previous emails (multiple times)MediumMediumOpened 3 emails but didn't reply

Challenge: You need website tracking, marketing automation, and CRM data to capture these. Many companies don't have this infrastructure.

Category 2: Third-Party Intent Signals (High Reliability)

Actions the prospect takes on other platforms that suggest buying intent.

SignalReliabilityUrgencyDetection Method
Researching your category on G2/CapterraHighVery HighG2 Buyer Intent, Capterra alerts
Searching for competitor alternativesHighVery HighIntent data providers (Bombora, 6sense)
Consuming content about your problem spaceMedium-HighMediumTopic-based intent providers
Engaging with competitor contentMediumMediumSocial monitoring
Posting questions in relevant communitiesMediumMedium-HighReddit, Slack communities, forums

Challenge: Requires paid intent data subscriptions. Quality varies wildly by provider.

Category 3: Public Signals (Medium Reliability, Free)

Observable events anyone can detect with the right monitoring.

SignalReliabilityUrgencySource
Hiring signalsHighHighLinkedIn Jobs, Indeed, careers page
Funding announcementsHighMedium-HighCrunchbase, TechCrunch, press releases
Leadership changesMedium-HighMediumLinkedIn, press releases
Product launchesMediumMediumCompany blog, PR, Product Hunt
Tech stack changesMediumMedium-HighBuiltWith, Wappalyzer, job descriptions
Earnings reportsMediumLow-MediumSEC filings, press releases
Awards/recognitionLow-MediumLowIndustry publications
Conference speakingLow-MediumLowEvent websites
Office expansionMediumMediumNews, job listings in new locations
M&A activityHighMediumNews, SEC filings

Advantage: Free and widely available. These should be the backbone of any signal-based outbound strategy.

Category 4: Social Signals (Variable Reliability)

Content the prospect publishes or engages with on social platforms.

SignalReliabilityUrgencySource
Posted about a pain you solveHighHighLinkedIn, Twitter
Shared a competitor's contentMediumMediumLinkedIn, Twitter
Asked for vendor recommendationsVery HighVery HighLinkedIn, communities
Commented on industry trends related to your spaceMediumLow-MediumLinkedIn
Changed their LinkedIn headline (new role)HighHighLinkedIn notifications
Published a thought leadership piece on your topicMediumMediumLinkedIn, company blog

Signal Scoring Model

Not all signals are equal. Score each signal to prioritize outreach:

Signal Strength Matrix

FactorHigh ScoreMedium ScoreLow Score
RecencyLast 7 daysLast 30 days30-90 days
DirectnessExplicit buying action (demo request, vendor search)Implicit buying action (hiring, funding)Tangential (content consumption)
FrequencyMultiple signals in same timeframeSingle signalHistorical signal
SpecificitySpecific to your exact categoryRelated to your general spaceBroadly related
Source reliabilityFirst-party or verified third-partyPublic, verifiableInferred or aggregated

Scoring Formula

Signal Score = (Recency × 3) + (Directness × 3) + (Frequency × 2) + (Specificity × 1) + (Source × 1)

Each factor rated 1-5:

ScorePriorityAction
40-50CriticalContact within 24 hours
30-39HighContact within 3 days
20-29MediumInclude in next campaign batch
10-19LowAdd to monitoring list
Below 10NoiseIgnore

Signal Combinations (Stacking)

Single signals are useful. Signal combinations are powerful. When multiple signals converge, the probability of buying intent increases dramatically:

High-Confidence Combinations

CombinationConfidenceWhy
Funding + Hiring for target roleVery HighMoney + action = active buying cycle
Leadership change + Tech evaluation (G2)Very HighNew leader re-evaluating the stack
Hiring SDRs + Content about scaling outboundHighBuilding the function + researching solutions
Competitor churn + Your website visitVery HighActively looking for alternatives
Conference in your space + LinkedIn post about the topicMedium-HighProblem is top of mind

Signal Stacking Rules

  1. Two signals from different categories = 2x the score. A hiring signal (public) + a G2 research signal (third-party) is much stronger than two hiring signals.
  2. Recency trumps everything. A weak signal from yesterday beats a strong signal from 3 months ago.
  3. Person-level signals > Company-level signals. The VP Sales posting about outbound challenges (person) is stronger than the company posting 3 SDR jobs (company) — because you know exactly WHO is feeling the pain.
  4. Don't stack noise. Three weak signals don't equal one strong signal. "Posted on LinkedIn" + "website has a blog" + "company is in tech" = noise, not intent.

Building a Signal Monitoring System

Manual Monitoring (0 cost, 30 min/day)

ActivityFrequencyTool
Check LinkedIn for job postings at target accountsDailyLinkedIn Jobs search, saved searches
Monitor Crunchbase for funding in your verticalsWeeklyCrunchbase alerts (free tier)
Track LinkedIn posts from target personasDailyLinkedIn feed, saved searches
Check Google Alerts for target companiesDailyGoogle Alerts (free)
Scan industry communities for vendor questionsWeeklyReddit, Slack groups, forums

Automated Monitoring (Paid tools)

Tool CategoryExamplesWhat It Monitors
Intent dataBombora, 6sense, ZoomInfo IntentCategory-level research signals
Job monitoringLinkedIn Recruiter, Otta, PredictLeadsHiring signals
Funding alertsCrunchbase Pro, PitchBookCapital events
Tech detectionBuiltWith, Wappalyzer, HG InsightsStack changes
Social monitoringMention, Brand24, PhantomBusterSocial signals
Website trackingClearbit Reveal, RB2B, LeadfeederWebsite visit signals

Signal Pipeline Architecture

Data Sources (APIs, scraping, alerts)
    ↓
Signal Detection Layer
    → Parse raw data for relevant signals
    → Categorize (hiring, funding, tech, social, first-party)
    ↓
Scoring Engine
    → Apply signal scoring formula
    → Stack multiple signals per account
    → Calculate composite score
    ↓
Prioritization Queue
    → Tier 1 (score 40+): Immediate outreach
    → Tier 2 (score 30-39): Next batch
    → Tier 3 (score 20-29): Add to campaign
    → Below 20: Monitor or discard
    ↓
Outreach Trigger
    → Route to appropriate campaign
    → Match signal to personalization angle
    → Enrich contact data if needed

Signal-to-Message Mapping

Every signal should map to a specific outreach angle:

SignalOpening Line ApproachCampaign Angle
Hiring SDRs"Building the outbound team?"Scaling outbound
Series B funding"Post-Series B is when pipeline becomes a board metric"Growth acceleration
New VP Sales"First 90 days in a new VP Sales role..."New leader priorities
Competitor evaluation"Evaluating {{category}}? Here's what teams miss"Competitive displacement
Tech stack change"Migrating to {{tool}} — most teams also rethink..."Stack optimization
LinkedIn post about pain"Your post about {{topic}} resonated"Thought leadership bridge
Conference attendance"Ahead of {{event}}, thought you'd find this relevant"Event-based relevance

Templates

Signal Tracking Sheet

| Company | Signal Type | Signal Detail | Date Detected | Source | Score | Action | Status |
|---------|------------|--------------|---------------|--------|-------|--------|--------|
| ___ | ___ | ___ | ___ | ___ | ___/50 | ___ | ___ |

Signal-Based Campaign Brief

Campaign: {{campaignName}}
Target Signal: {{primarySignal}}
Supporting Signals: {{secondarySignals}}

Signal Detection:
- Source: {{dataSource}}
- Refresh frequency: {{howOften}}
- Estimated volume: {{leadsPerWeek}}

Personalization Map:
- Opening line template: "___"
- Value prop connection: "___"
- CTA: "___"

Qualification Threshold:
- Minimum signal score: ___
- Required firmographic fit: ___
- Maximum signal age: ___ days

Tips

  • The best time to email someone is within 48 hours of a signal firing. After 2 weeks, the signal is stale and your "I noticed..." line sounds like a lie.
  • Don't chase every signal. Pick 2-3 signal types that correlate with your highest close rates and build systematic monitoring around just those. Depth beats breadth.
  • Hiring signals are the single most reliable free signal for B2B outbound. If a company is hiring for the role your product serves, they are actively investing in that function.
  • Person-level signals always beat company-level signals. "The VP Sales posted about needing better pipeline visibility" is 10x more actionable than "the company raised a round."
  • Create a feedback loop: track which signal types lead to the most meetings. After 3 months, double down on the winners and drop the losers.
  • Signal + fit > fit alone > signal alone. A perfectly matched ICP company with intent signals is your #1 priority. A perfectly matched ICP company with no signals is Tier 2. A non-ICP company with signals is usually noise — don't chase it.

Progressive disclosure: load signal provider integrations and API configurations only when setting up monitoring for a specific campaign.

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.