Clay Signals and Clay Tables: How to Build Live Monitors and Account Scoring

Last updated: 14 October 2026
Clay Signals are Clay's detectors for buying triggers such as job changes, promotions, funding rounds, hiring and tech-stack changes, and they can run as live monitors that keep adding matching companies to your list. A Clay table is Clay's core workspace: a grid where each row is a company or person and each column is an enrichment, lookup or action. Together they give you a self-refreshing list you can score, tier and send to outbound. This guide shows the set-up and a weighted scoring rubric you can copy.
Faraz Ahmed, founder of ThynkGrowth, built and ran a $6.12M quarterly ABM pipeline engine as the sole Clay operator at an enterprise SaaS company, and trained 70 BDRs on AI and Clay. He holds all four Clay certifications, and ThynkGrowth is a Clay Solutions Partner. Signal-led outbound is the core of what we do, so the pattern below is the one we build for clients.
What are Clay Signals?
Clay Signals are automated detectors inside Clay that watch companies and people for buying triggers: job changes, promotions, funding rounds, hiring activity and tech-stack changes. Each detection becomes data in a Clay table that you can filter, score and route to outreach, so your team contacts accounts when something has just changed rather than on an arbitrary schedule.
A signal is a reason to write, not a lead. A static list tells you who could buy; a signal tells you why now. Our guide to what intent data is explains how signals differ from it. Clay is where we run them, and Prospeo is our pick when we want job-change detection and verified contact data in one step, a workflow we cover in how job-change signals book meetings.
What is a Clay table and why does it matter for signals?
A Clay table is Clay's core workspace: a spreadsheet-style grid where each row is a company or person and each column is an enrichment, lookup or action. Columns build on one another, so one row can be found, enriched, scored and prepared for outreach. For signals, the table is where detections land and become decisions.
The row-per-account structure is what makes scoring possible. When funding, hiring and tech-stack data all sit on the same row, you can add them up.
How do you set up a live signal monitor in a Clay table?
Create a Clay table for your ICP, add a signal source such as funding, hiring, job-change or tech-stack detection, set filters that match your ideal customer profile, and switch the source to run as a live monitor. New matching companies then arrive as fresh rows over time, ready for enrichment and scoring without a manual export.
- Define a narrow ICP. Industry, headcount band and region. Loose filters flood the table with rows you will never contact.
- Add one signal source first. Start with funding or hiring, and add more once it is clean.
- Run it as a live monitor so it adds new matching rows over time instead of giving a one-off snapshot.
- Capture the signal date. Without it you cannot apply the recency rule below.
- Enrich the buying contact and verify the email before anything is sent.
- Add score and tier columns. Formulas turn signals into a number and a label.
- Route by tier. Hot accounts go to a sequencer, warm accounts get a lighter touch, watch accounts stay put.
Every new row can spend credits, so tighten filters before switching the monitor on. For the system around the table, see how to build a signal-led GTM system. If you want to learn to build it yourself, ThynkCrew is ThynkGrowth's cohort-based GTM engineering coaching programme: 8 weeks, 12 live sessions and 20 seats, where you build a signal-led outbound system on Clay and are certified on assessment. Crew 01 starts on 14 November 2026.
How do you score accounts from signals?
Give each signal a weight, add the points for every signal an account shows, and map the total to a tier: hot at 70 or above, warm from 40 to 69, watch from 15 to 39. Weights should reflect how closely a signal predicts a buying window, and each signal should lose value as it ages.
| Signal | Rule | Max points |
|---|---|---|
| Recent funding | Round announced in the last 90 days | 25 |
| Executive hire | Relevant leader started 2 weeks to 3 months ago | 25 |
| Hiring for a target role | Open role that matches your offer | 20 |
| Tech-stack match | Uses a tool you integrate with or replace | 15 |
| ICP fit | Headcount, industry and region match | 15 |
| Total | 100 |
Recency rule: full points if the signal is under 90 days old, half points from 91 to 180 days, zero after that.
| Tier | Score |
|---|---|
| Hot | 70 to 100 |
| Warm | 40 to 69 |
| Watch | 15 to 39 |
Sample scored account
This is an illustrative account, not a client. It is a 60-person B2B SaaS company.
| Signal | What we found | Points |
|---|---|---|
| Recent funding | Series A announced 5 weeks ago | 25 |
| Executive hire | None found | 0 |
| Hiring for a target role | Two open SDR roles | 20 |
| Tech-stack match | Runs a CRM we integrate with | 15 |
| ICP fit | In range, outside our core headcount band | 10 |
| Total | 70, Hot |
The account is hot without an executive hire because three signals stacked. Treat these weights as a starting point and recalibrate against your own reply data. Building and calibrating this scoring model is a core exercise in ThynkCrew. One design rule matters: ICP fit alone caps at 15 points, so a static match can never reach hot. Fit is a list; signals are timing.
Which signals convert best?
In our experience, signals tied to a change in who decides or what a company can spend convert best: new executive hires, job changes into relevant roles, and recent funding. Timing matters as much as type. For job changes, the sweet spot is 2 weeks to 3 months after the start date, so weight recency heavily.
The reasoning is simple: new leaders review vendors early, new capital creates budget, an open role shows pain, and tech-stack data shows compatibility but says less about urgency. That is why signal-led outreach consistently out-replies a static list built from the same ICP and the same offer: you reach the account just after something changed, when the need is live. It is also why 70 of the 100 points in the rubric go to time-bound events and only 15 to static fit.
If you would rather not build and maintain this yourself, ThynkGrowth, a Clay Solutions Partner, runs it as a done-for-you signal-led outbound service.
Are Clay Signals the same as intent data?
No. Clay Signals detect specific events such as job changes, funding and hiring. Intent data usually infers interest from browsing or research behaviour, and the two work well together.
How many signals does an account need to be hot?
In this rubric, usually three. No single signal is worth more than 25 points and hot starts at 70, so signals have to stack.
What does it cost to run a live monitor in Clay?
Cost depends on how many rows the monitor adds and which enrichments run on each row. Tight ICP filters keep both down, so narrow the monitor before you switch it on.
Why do signal-led campaigns beat static lists?
Because you reach the account just after something changed, when the need is live, rather than on an arbitrary schedule. Timing and relevance are what lift reply rates, which is why the scoring model weights recent, time-bound events far above static fit.
Related reading
Want this running for your pipeline?
Book a free strategy call. We map your outbound plan whether you work with us or not.
Book a free strategy call