TL;DR: Part 1 covered the architecture - HubSpot, Clay ABM, 92 sequences, routing logic, reporting. Part 2 covers what runs on top of it. How signals translate to outreach angles. How High Priority accounts get worked. How events stopped being a one-email activity and became a structured conversion system. And what the Signal-To-Motion™ framework looks like in practice.
The Strategy Problem Volume Outbound Can't Solve
Most outbound strategy defaults to one decision: who to reach and what to say.
For a firm with a finite enterprise market - roughly 200 accounts in one region, 5,800 globally in the product arm, this framing is wrong. When the market is small, every uncontextualized message damages future access. The question isn't who to reach. It's when.
Signal-led outbound answers the when. An account that just hired a new HR leader, announced a system migration, or posted a role requiring HRIS transformation experience is not the same account it was three months ago. The business problem just became live.
Outreach during that window is relevant. Outside it, it's noise.
The entire outbound strategy was built on one principle: only reach out when something happening inside the account makes the outreach genuinely worth receiving.
How Signals Translate to Message Angles
A signal tells you the timing. It doesn't tell you what to say.
The mistake most teams make: they mention the signal. "Saw you just hired a Head of HR - wanted to reach out." The prospect knows you scraped a job board.
The right approach: use the language inside the signal, not the signal itself.
A job posting for a Senior HRIS Implementation Manager that mentions "multi-country payroll coordination" and "legacy system migration" is telling you exactly what the business is dealing with. Your first line mirrors that language.
Not because you reference the post, but because that's the vocabulary of their current problem.
This applied across both business units:
Consulting arm - 13 service-line routing paths
Each account's platform situation (currently on SF, evaluating Workday, running legacy) combined with their signal score determined which of 13 sequences they entered.
An account hiring for SF expertise got a different angle than one actively migrating off a legacy system, even if both scored above the Prospect threshold.
Product arm - 11 product routing paths
Signal scores across 6 categories (HR leadership change, platform situation, headcount growth, compliance pressure, HRIS hiring, and transformation announcements) determined which product sequence was most relevant.
An account showing payroll-related hiring signals got the Reimburse+Renefits track. An account with high document management signal got ePFile.
Routing happened automatically. The Claygent read the signal pattern and assigned the sequence. No manual sequencing decisions.
The 3 Cold Outbound Angles for High Priority Accounts
For accounts that scored into the High Priority tier - the ones with concentrated, recent, multi-signal evidence, cold outbound ran in parallel with inbound sequences.
Three angle variants. Each addresses the same problem from a different direction.
Angle 1: The cost of scale
What it addresses: manual HR processes that work at 200 employees, break at 500. The prospect doesn't think of this as a problem until scale makes the cost visible.
Angle 2: The gap the platform created
What it addresses: SAP SuccessFactors is a strong core HCM. It doesn't solve everything adjacent to it - expense management, document handling, benefits administration.
Angle 3: The coordination problem
What it addresses: HR, payroll, and IT owning overlapping pieces of the same process. No single owner. Repeated manual reconciliation. This angle names the coordination friction directly, which is the day-to-day reality most HR ops teams live in.
The angle selection wasn't manual.
The routing Claygent assigned the most signal-appropriate variant based on which signals drove the High Priority score.
Post-Event Follow-Up as a Pipeline System
Events were the firm's warmest asset and their worst-converting one.
15-20 senior enterprise attendees per event. One email blast to all of them. Then nothing.
The problem wasn't the event. It was the absence of anything systematic after it.
Segmentation before follow-up
Attendees weren't treated as a homogeneous group. Each was scored against the signal framework before any outreach. An attendee with a recent leadership change and active HRIS hiring on their company scored differently than one with no active signals. Sequence assignment reflected the score.
Timing logic
First follow-up within 24 hours of the event. Personalized to the conversation - referencing specific content from the session, not a generic "great to meet you." Subsequent touches at Day 3, Day 7, and Day 14 depending on response.
Handoff criteria
A positive reply or meeting request triggered an immediate handoff alert to the correct business unit owner via Google Chat. No reply sat in a queue.
The result: every event produced a structured 14-day pipeline motion instead of a single email that went unanswered.
What the Signal-To-Motion™ System Looks Like Running
The full loop, from signal to conversation:
- Clay detects a buying signal → leadership change, HRIS hiring, transformation announcement, EOL pressure
- Scoring Claygent updates the account score
- Account crosses threshold → classified as Prospect or High Priority
- Routing Claygent reads signal pattern → assigns the right sequence and angle variant
- HubSpot enrolls the contact → sequence triggers with Day 1 email within the first hour
- Reply arrives → Reply Claygent classifies sentiment → alert fires to correct owner
- Dashboard captures the full chain - signal detected to reply received, with no manual entry
The sales team sees accounts, sequences, signal explanations, and reply classifications inside HubSpot. No context switching between tools. No manual research before outreach.
The Claygent that explains scoring outputs a plain English summary in the contact record: why this account scored as High Priority, which signals drove it, and what the recommended entry angle is. The rep reads one paragraph and knows exactly where to start.
What This Means in Practice
The firm went from no outbound infrastructure to a fully automated, signal-routed, dual-BU pipeline system in 6 weeks.
The post-event system alone converted a consistent source of warm relationships that had produced zero pipeline for years.
That's not a messaging improvement. That's infrastructure.
