02
procore signals
Signal Based Account Prioritization for Procore Sales Reps
Replaced gut feel prioritization with a live signal engine that tells reps who to call first and why, then automates the alert straight to Slack.
clayclaygentfind jobsslackmeta prompting
situation
Reps were prioritizing on instinct. Nothing surfaced which accounts were showing real buying intent versus which were simply next on the list. The goal: help reps prioritize early using real world signals tied to construction activity, so effort goes toward accounts more likely to convert.
the build
- Built a ranking engine that reads live buying signals instead of gut feel. It pulls construction companies across Canada and the US and watches two real-world signs that work is coming: they're hiring project managers, and there's news coverage of new construction they're tied to (read and interpreted by AI, not just keyword-matched).
- Turned those signals into dead-simple priority tiers. Two or more signals means a top-priority "hot" account, one signal is second priority, and everything else waits.
- The moment an account goes hot, the rep gets a Slack message with the reasoning already written — so it lands as a ready-to-act task instead of a row in a report nobody opens.
- One engine, both playbooks. The logic branches for brand-new prospects versus existing CRM accounts, so the same build works whether the rep is hunting or farming.
process map
1Pull construction companies
2Fill in the company details
3Signal: hiring project managers?
4Signal: AI reads the project news
5Rank into priority tiers
6Hot account pings the rep on Slack
7Same engine for new or existing
impact
- An hour of manual research becomes a Slack ping with the reasoning already attached.
- Reps stop guessing which of hundreds of accounts to call first — every day starts with the ones already showing real signs of a coming purchase.
- The exact shift that shortens sales cycles and lifts win rates on the accounts that matter most.
tech stack
currently using
- Clayfiltering, enrichment
- ClaygentAI read news summaries
- Find Jobshiring signal
- Slackrep alerts
- meta promptingtiering logic
phase 2
- ConstructConnect via Salesforce sync for the richer, non delayed signal
- Web scraping to backfill job and project signals where clean API access does not exist
- Salesforce integration for production triggers
- A scoring model with more than two signals for finer tiering
reflections
- The plan matched the build; data access was the catch. The freshest source (ConstructConnect) doesn't connect to Clay, so I substituted hiring and news signals. They work, but they arrive later than a direct feed would.
- The unlock was routing around the missing integration. ConstructConnect does connect to Salesforce, so the right architecture is "ConstructConnect feeds Salesforce, Clay reads Salesforce." Anticipate where a build will break before you start, and find the way around the locked door instead of stalling in front of it.