Exploring Metrics for Tracking SME Growth with Clay Support

Youcef S. · 2025-12-15T15:51:29.915Z

Hello Clay Support, I’m trying to set up a signal to detect growth in SMEs, and I wanted to check what is technically feasible on your side. The idea is to approximate business growth using a combination of proxies, such as: • Headcount variance over time (headcount at date X, then rechecked at a later date) • Number of active job postings • Ratio of live job postings to total headcount • Fundraising events • Revenue growth or variation, when available My question is whether Clay allows: • Tracking and comparing these metrics at two different points in time (especially headcount) • Combining multiple signals into a single growth indicator or trigger • Accessing or integrating reliable data sources for fundraising and revenue changes If some of these signals are not directly available, I’d also be interested in knowing what workarounds or integrations you would recommend.

Exploring Metrics for Tracking SME Growth with Clay Support | Clay

Clay Support
APP
·
·
Yes, Clay can track and compare headcount variance over time using built-in enrichments and formulas—just add headcount enrichments for different dates and use formulas to calculate growth percentages between them [1], [2], [3]. You can also combine multiple signals (like headcount, job postings, fundraising, and revenue) into a single growth indicator by building a custom scoring model, assigning weights to each factor, and letting Clay auto-calculate composite scores .
For fundraising and revenue, Clay integrates with Crunchbase and Autobound, providing access to funding rounds, revenue estimates, and growth trajectory data [6], [7], [8]. These sources are reliable and updated automatically, so you can use them to detect SME growth signals effectively .
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you need any further help setting up your growth detection signals or have more questions about combining metrics, I’m here to assist. Would you like to provide more details about what you’re trying to achieve or any specific challenges you’re facing?
Youcef S.
·
·
Hello, Thanks for the clarification on tracking headcount and building composite growth signals. I’d like to go one step further and understand the practical implementation of the fundraising and revenue signals you mentioned. Specifically:
How can fundraising events be implemented in Clay using Crunchbase (or other sources)?
Which enrichments or fields should be used to track funding rounds over time?
Is it possible to trigger or score companies based on recent fundraising activity?
How is revenue data handled in practice?
Are revenue figures and revenue growth directly available as enrichments, or only estimates?
Can revenue changes over time be compared similarly to headcount variance?
Additionally, could you confirm:
Whether Crunchbase and revenue-related enrichments are fully available on the Starter plan
Any limitations (credits, historical depth, refresh frequency) that apply to these data sources on that plan
If you have documentation, examples, or best practices for setting this up, that would be helpful.
Clay Support
APP
·
·
You can implement fundraising signals in Clay by adding the Crunchbase enrichment to your table—just search for "Crunchbase" and select actions like "Enrich a company's latest funding round" to get details on recent funding, including date, type, and amount. For revenue, use the "Enrich a company's financials" action to access Crunchbase’s revenue range estimates. These enrichments let you track and compare fundraising and revenue data over time, and you can build custom signals to score or trigger actions based on recent activity (e.g., funding within the last 6 months) [1] [2] [3] .
On the Starter plan:
Crunchbase and revenue enrichments are available, but you’ll need to use Clay’s managed account (not your own API key) unless you upgrade to a plan that supports custom API keys [5] [6].
Credits are required for each enrichment—costs are listed next to each source when you set up a signal [7] [8] [9].
Historical depth and refresh frequency depend on Crunchbase’s data, not Clay’s limits. You can’t use your own API key for Crunchbase on the Starter plan, so you’re limited to Clay’s managed account .
Revenue figures are estimates, not exact numbers, and you can compare changes over time using formulas or custom signals .
Best practices:
Use custom signals to combine fundraising and revenue data into a single growth score.
Set up monitoring frequency for your signals to track changes over time.
If you want to use your own API key for Crunchbase, you’ll need to upgrade to a plan that supports it [10] [11].
Clay Support
APP
·
·
Is that what you were looking for?
Clay Support
APP
·
·
If you still need additional help with implementing fundraising and revenue signals or have more questions, I’m here to assist. Would you like to share more details about what you’re trying to resolve or understand further?
Ketan K.
·
·
Youcef S. you can check out https://recepto.ai as well - it has hundreds of these “plays” that you can configure on your ICP. We are in process of connecting with Clay as well
Clay Support
APP
·
To track fundraising in Clay using Crunchbase:
Add the Crunchbase enrichment to your table and use actions like Enrich a company's latest funding round to get the most recent funding date, type, and amount. You can also use Enrich a company's financials for revenue range and total funding. These enrichments let you compare funding and revenue over time by adding multiple enrichments at different points and using formulas to calculate changes [1] [2] [3] .
For scoring, create a custom signal to flag companies with recent funding (e.g., within the last 6 months) and combine this with other metrics into a growth score [6].
On the Starter plan, Crunchbase and revenue enrichments are available, but you’ll use Clay’s managed account (not your own API key). Credits are required for each enrichment, and historical depth/refresh frequency depend on Crunchbase’s data. You can’t use your own API key for Crunchbase on the Starter plan .
Revenue figures are estimates, not exact numbers, and you can compare changes over time using formulas or custom signals .
Clay Support
APP
·
·
Did that answer your question?
Clay Support
APP
·
·
To implement fundraising and revenue signals in Clay using Crunchbase:
Add the Crunchbase enrichment to your table and use actions like Enrich a company's latest funding round (for date, type, amount) and Enrich a company's financials (for revenue range, total funding) [1] [2] [3] .
Track funding rounds over time by running these enrichments at different points and comparing the results in formulas or custom signals .
Score companies based on recent fundraising by creating a custom signal that flags companies with funding within a set period (e.g., last 6 months) and combining this with other metrics into a growth score [6] [7] [8].
Revenue data is provided as estimates (range, not exact figures), and you can compare changes over time using formulas or custom signals [5].
On the Starter plan:
Crunchbase and revenue enrichments are available, but you’ll use Clay’s managed account (not your own API key) .
Credits are required for each enrichment—costs are shown when you set up a signal [4].
Historical depth and refresh frequency depend on Crunchbase’s data, not Clay’s limits .
You can’t use your own API key for Crunchbase on the Starter plan .
Best practices: Use custom signals to combine fundraising and revenue data into a single growth score, and set up monitoring frequency to track changes over time .
Clay Support
APP
·
·
Did that answer your question?
Clay Support
APP
·
·
If you still need additional help with implementing fundraising and revenue signals or have more questions, I’m here to assist. Would you like to share more details about what you’re trying to resolve or understand further?
Youcef S.
·
·
Hello Clay Support, I’d like to align on a more focused setup for detecting short-term (weekly / bi-weekly) growth signals in Clay. At this stage, I want to concentrate specifically on the following signals: 1. Headcount variance (employee count at date X, then re-checked at date Y) 2. Number of live job openings 3. Ratio of live job openings to total headcount 4. Recent fundraising events (used as a contextual flag) 5. Estimated revenue variation (low-weight, supplementary signal) My main questions are:
Which of these signals are realistically possible to implement and monitor over time in Clay?
For each signal, how frequently is the underlying data typically updated (e.g. LinkedIn-based headcount, job postings, Crunchbase funding, revenue estimates)?
Which of these signals can reasonably be compared at a weekly or bi-weekly cadence, and which ones are better treated as event-based or slow-moving?
Are there any known limitations in Clay (refresh frequency, historical depth, data lag) that would materially affect monitoring these signals at short intervals?
The goal is to understand what is technically reliable and operationally realistic, rather than theoretical availability.
Clay Support
APP
·
·
All five signals are technically possible in Clay, but with different refresh realities:
Headcount variance: Fully supported with scheduled enrichments. Company and people data refreshes every 2-3 weeks on a rolling basis, so weekly/bi-weekly monitoring works but expect some lag .
Job openings & ratios: Available through job posting enrichments. These update more frequently than headcount data and work well for weekly monitoring [1].
Fundraising events: Supported via Crunchbase integration. Updates depend on Crunchbase's refresh cycle, making this better as an event-based signal rather than weekly monitoring .
Revenue variation: Available as estimates through Crunchbase financials. Data refreshes vary but generally slower - treat as supplementary/monthly signal .
Key limitations for short-term monitoring:
Company data has slowest refresh at 3 months, fastest daily
Each scheduled run consumes credits regardless of new results
Weekly runs work well for trend monitoring but daily is better for time-sensitive signals [2]
For reliable weekly/bi-weekly monitoring, focus on job postings and use headcount/fundraising as supporting context rather than primary triggers.

21 comments