SMYS 3 | From Clay Tables to Intent HQ: Building the BDR Action Layer

Key Takeaways

• BDRs spend two hours daily juggling CRM, LinkedIn, Apollo.
• Clay scores tens of thousands of accounts using firmographic and technographic data.
• Composite scores above 40% trigger signal monitoring, filtering low-fit accounts.
• Custom Intent HQ app consolidates data into a single actionable view.
• Unify’s outbound program generated $15M pipeline in 12 months.

Pulse Analysis

The biggest productivity drain for business‑development reps isn’t a lack of data—it’s the manual stitching of that data across disparate tools. Most BDRs start their day toggling between a CRM for ownership, LinkedIn Sales Navigator for contacts, and Apollo for intent signals, spending up to two hours just to answer three basic questions: which accounts are assigned, who to call, and why now. This “action layer gap” forces reps to become ad‑hoc integrators, diluting their highest‑leverage activities and inflating operational costs.

Garrett Wolfe’s solution begins with a rigorous scoring engine in Clay that ingests tens of thousands of companies and normalizes firmographic and technographic attributes into a zero‑to‑one metric. By employing a waterfall enrichment strategy—Lead Magic, revenue databases, LinkedIn, and employee counts—the model ensures coverage even when a single vendor fails. Only accounts surpassing a 40 percent composite threshold advance to signal monitoring, dramatically reducing noise and focusing BDR effort on high‑fit prospects. This disciplined filtering replaces gut‑driven list building with data‑driven prioritization.

The final piece is the Intent HQ web app, built with Claude Code, which presents the enriched, scored accounts and real‑time intent signals on a single dashboard. Reps no longer need to switch contexts; they receive a clear, actionable view that tells them which accounts to own, which contacts to engage, and the timely reason for outreach. The result—a $15 million pipeline in twelve months for Unify—demonstrates how a well‑architected GTM stack can turn raw data into revenue. As more high‑growth firms adopt similar action layers, the role of GTM engineering will shift from optional tooling to a core competitive advantage.