A quick story from a recent client project

Hey there, Matteo here from Kinetyca.

I wanted to share an interesting outbound problem we ran into recently, since the fix ended up being pretty counterintuitive.

A client came to us already sending millions of emails a month. Normally that much volume means a dialled-in outbound motion. Here, it meant the opposite. Reply rates had flatlined, cost per lead kept climbing every month, and the assumption internally had been that more volume would eventually fix it. So they sent more. Nothing moved.

They came to us wanting the actual system rebuilt, not another vendor running more of the same campaigns on top of it.

Here's what we found once we opened it up.

01What was their problem?

The client sells into school districts, US and UK both. On paper that reads like one market. It isn't.

Funding structures differ by region. Buying authority changes with district size, sometimes it's an individual educator, sometimes it's a district administrator. Job titles vary by state. Regulatory context shifts by geography. One outbound system was messaging all of it the same way, and that mismatch was the real problem, not the volume.

Underneath that sat a second issue. Years of CRM growth had left records outdated and inconsistent, and the team was mid-migration from NetSuite to HubSpot at the same time. Any fix had to work through a live data migration, not around it.

02How did we rebuild?

Here's the sequence:

• Data cleanup first. Every record got normalised in Clay before a single email went back out, since bad inputs make personalisation impossible no matter how good the message is.
• Segmentation that matched reality. Separate targeting logic for US districts and UK schools, using geography, job title, and funding structure as real inputs instead of a generic list.
• AI personalisation with actual context. Clay's AI fields pulled school-specific detail into each message, geography and role, not a first-name merge tag, with prompts iterated daily against live reply signals.
• A controlled pilot before scaling. 20,000 emails a month across a 10,000-lead US test, sent through Smartlead, expanding past 100,000 a month only once the signal held up. Deliverability stayed clean throughout.
• CRM alignment in parallel. The NetSuite-to-HubSpot migration ran alongside the build, so data flow and pipeline tracking stayed intact and warm leads never drifted out of sync with what outbound was producing.

03The Results

Here's where it landed:

• ✅ 30 positive replies in the first 10 days
• ✅ A 3 percent reply rate and 70 additional leads after expanding into the UK
• ✅ 165 warm leads within 30 days of scaling
• ✅ 14 deals closed

None of that came from sending more. It came from fixing what the system was actually saying to people, then deciding how hard to push it. Volume is a multiplier. If the signal underneath it is broken, more volume just makes the problem more expensive to run.

If your outbound needs the same kind of system rebuild, not just more volume, let's talk.