How Sales Tempo Uses Claude to Build ICPs, Run Competitive Positioning, and Personalize at Scale

Most outbound teams know the drill. Before you send a single email, someone has to figure out who to target, what to say, and why it's different from the last twelve emails that prospect ignored. That work used to eat hours per account. At Sales Tempo, we rebuilt it around Claude, and it changed how fast and how well we can run outbound for clients.

Here's what that workflow actually looks like.

Building the ICP, not guessing at it

Every engagement starts with the same question: who actually fits. We pull firmographic and CRM data through Clay, then use Claude to reason over it, not just filter it. Instead of a static list of "SaaS companies, 50 to 200 employees," we get an actual written rationale: which accounts match on signal, why, and where the edge cases are. That rationale becomes the ICP document a client's sales team can actually read and argue with, not a spreadsheet of firmographic filters nobody remembers the logic behind.

Competitive positioning, built from what prospects are already saying

Some of our best positioning doesn't come from a battlecard. It comes from G2. We built an automation that scrapes recent one and two star reviews on tools like Salesloft, flags the specific complaints, and cross-references the reviewer against our target list. Claude takes that raw complaint text and turns it into a specific value proposition: not "we're better," but "here's the exact integration issue you flagged, and here's how we solve it." That's positioning a prospect already agrees with before you've said a word to them.

Personalization at scale, without the scale part sounding fake

We replaced a $33,000 a year job-change tracking tool with a Clay table that pulls CRM contacts, enriches them with LinkedIn job-change signals, and filters by ICP fit, seniority, and territory. Claude writes the outreach that follows. Because every signal is different (a job change reads differently than a funding round, which reads differently than a G2 complaint), Claude drafts copy that actually matches the trigger instead of forcing every signal into the same template. We built the whole system for a client in under two weeks.

What this actually gets us

Faster ramp on new accounts, positioning that doesn't sound like every other vendor, and outreach that holds up against "did a person actually think about this before hitting send." None of it works without both halves: Clay for the data plumbing, Claude for the judgment calls a spreadsheet can't make.

If you're building or buying outbound infrastructure and want to see how this holds up on your own pipeline, that's a conversation worth having.