Your pipeline is leaking


Hello Reader

“Sorry we couldn’t find time to chat.”

That sounds like a reasonable email to send a prospect who failed to schedule a meeting.

Except this prospect had never received a meeting link.

The email came from Zapier and landed in the inbox of a qualified enterprise buyer. The company’s automation blamed the buyer for failing to complete an action they’d never been given the chance to take.

Angela Ferrante, who led enterprise marketing at Zapier (and is now head of marketing at Amplitude), recently walked me through how she discovered that email.

It was one example of a much larger problem: qualified buyers were getting trapped inside a broken journey.

Some were sent through live-chat loops. Some received several uncoordinated automated messages. Others received no meaningful follow-up at all.

The company had plenty of demand. Millions in potential pipeline were entering the funnel each month, but too much of it was slipping through the cracks.

Every pipeline leaks, including those built by thoughtful teams with sophisticated systems.

This week I’m going to show you how Angela used a team of agents to find those leaks, fix the buyer experience and recover pipeline that Zapier had already earned.

The Leak Was Bigger Than One Email

At first, Angela thought the issue was a broken automation.

Then her team started looking at other qualified buyers who’d failed to reach a meeting.

They found prospects receiving automated emails with no human follow-up. Others were contacted by several systems in the same week. Some entered the funnel, met the qualification criteria and disappeared without receiving a single message.

It’s a common problem.

A recent Salesforce study on agentic marketing found that 48.6% of inbound leads fail to convert because of inadequate follow-up. Another 31.7% are lost through poor routing or handoffs.

Those numbers make sense when you look at what was happening inside Zapier.

Marketing captured the lead, hubSpot saved the record and then other systems handled the sales activity, content and communications. Each platform recorded its part of the process, but no one could see the complete experience.

The prospect moved between tools and teams while everyone inside the company saw a different piece of the journey.

That’s how a pipeline can leak even when every individual system appears to be working.

So Angela decided to follow the buyers who’d already raised their hands.

Rebuild the Buyer Journey

Finding out what happened to each lead required a lot of manual work.

The most senior person on Angela’s demand gen team was spending approximately 40 minutes investigating every lost lead. He moved between HubSpot, Gong, Contentful and other systems trying to piece the journey together.

Angela described it as “total whack-a-mole.”

One system showed that a form had been submitted, another showed an automated email, a third held the sales activity. None of them gave the team a complete view of what the buyer had actually experienced.

To fix this, Angela established a manual verification loop built around five core questions:

  1. Who is this buyer?
  2. What did they do?
  3. How did we respond?
  4. Who owned the next action?
  5. Did that action happen?

This verification loop gave her team a way to examine the stack through the buyer’s eyes before turning the process over to the automated agents.

The investigation also surfaced problems that a standard pipeline dashboard wouldn’t catch.

Around 30% of the abandoned leads involved an email typo. Someone would enter “gamil.com” instead of “gmail.com,” the automated messages would bounce and the lead would disappear.

The team also found senior buyers at major companies using personal email addresses. Zapier hadn’t been sanctioned inside their companies yet, so they’d signed up with Gmail. A rule that classified personal email addresses as low quality could have removed some of Zapier’s best prospects.

The Agent Investigation

Angela’s agents turned a 40-minute manual investigation into a repeatable workflow with automated verification loops.

Instead of one monolithic agent, Angela designed a specialized 'Agent Team' consisting of three distinct automated tasks, each operating as a Codex scheduled automation.

The first started with a daily HubSpot report of qualified buyers who hadn’t reached a meeting. It pulled activity from across Zapier’s systems and diagnosed where each journey had broken.

The second turned that evidence into a visual timeline showing the buyer’s form submissions, communications, sales activity and missing steps.

Together, the agents gave Angela’s team a complete view of the buyer journey. They sent the diagnosis to Slack and suggested recovery messages for email and LinkedIn, giving sales a clear next step.

The agents weren’t dependable on the first try.

When Angela asked them to process hundreds of leads, the outputs became inconsistent. She added verification steps that compared each result with an approved example and reran any work that failed the check.

That experience gave her three rules for building a dependable agent:

  1. Start with a defined source of truth.
  2. Give the agents a bounded job.
  3. Give it criteria for checking its own work.

As Angela explained, “You have to do it manually first. You teach it how to do it and then you give it good criteria for whether it did the job well.”

Humans and agents working together

Once Angela’s agents made the broken buyer journey visible, it was clear what they needed to do to fix the issue.

Zapier brought everyone together in a cross-functional “No Lead Left Behind” initiative. Sales contacted affected prospects while RevOps repaired the sequences, routing and ownership rules causing the leaks.

According to Angela, weekly pipeline leakage fell from the high six figures to the thousands.

Agents Need Clarity

Angela’s agent worked because its job was specific and its requirements were clear.

This same principle applies when you’re using Claude to analyze marketing and pipeline data. If you give it an open-ended instruction such as “analyze my pipeline,” it’ll decide what to examine each time and your answer will always vary.

One week it might focus on conversion rates, the next it will be prioritizing deal size, lead source or stage velocity. This makes it incredibly difficult to track your progress.

Your instructions need to make the analytical (and repair) process repeatable.

Your Pipeline Agent Instruction Framework

To move from unpredictable results to a dependable system, you need a standardized blueprint for your automation.

The following Pipeline Agent Instruction Framework provides a repeatable structure for defining how your agents should think, investigate, and repair pipeline issues.

1. Give it one objective

Tell Claude exactly what it’s investigating.

For example: “Identify qualified inbound leads that failed to reach a sales meeting.”

2. Name the source of truth

Specify the report, date range, fields and systems the agents can use.

Use frozen daily or weekly snapshots for historical comparisons. CRM records change constantly, so a live report can produce a different version of the past every time the agents runs.

3. Define your terms

Explain what your company means by a qualified lead, successful follow-up, conversion, owner and recoverable pipeline.

Claude shouldn’t have to infer those definitions from inconsistent CRM records.

4. Supply the statistical baseline

Give the agents calculations it can use to recognize an exception:

  • The conversion rate by stage and cohort
  • The median time leads spend in each stage
  • The normal response-time range
  • The historical conversion rate by source
  • The percentage of leads with missing data
  • The expected conversion probability by segment

Use your CRM, SQL or Python for calculations that need to run the same way every time. Claude can interpret the results, investigate exceptions and explain what should happen next.

5. Write explicit decision rules

Your rules might include:

  • Flag qualified leads with no human response after four business hours.
  • Flag leads that receive more than three automated messages without a reply.
  • Flag opportunities sitting in a stage longer than the historical 75th percentile.
  • Flag records whose assigned owner conflicts with territory rules.
  • Review personal email addresses against company and role data before suppression.

6. Require evidence

Ask Claude to show the records, messages and events supporting every diagnosis.

It should label missing information, explain its confidence and identify any assumptions it made.

7. Define the approval points

Tell the agents which actions it can complete, which require human approval and which situations need to be escalated.

8. Add a verification step

Give the agents a checklist for reviewing its work before it publishes a report, changes a record or contacts a buyer.

You don’t need to start with a fully autonomous GTM system.

Start with ten lost leads and one question: What happened?

Once your agent can answer that question consistently, you can teach it how to help.

Where is your pipeline leaking? Hit reply and tell me what you find.

Driver Labs is a community for marketing leaders, agency owners and solopreneurs who want to build AI systems that work.

We show you exactly what’s working inside real agencies and teams, step by step with nothing left out, alongside peers tackling the same priorities, pressures and standards.

Join the Driver Labs community here.

Free session — Sept 3, 3pm PT We'll show you how to build an AI agent that runs a full campaign from competitive research to campaign brief.

Free to attend.

Save your seat

Did some one forward you this email? You can subscribe here.

2120 Contra Costa Blvd #1059 , Pleasant Hill, CA 94523
Unsubscribe · Preferences

AI at Work

AI at Work is a weekly newsletter on how marketing teams redesign workflows, roles, and systems with AI. Real examples, practical frameworks, and repeatable processes operators can use immediately. Join thousands of successful marketing leaders by subscribing below!

Read more from AI at Work
AI Agents

Hello Reader You’ve been meaning to set up AI correctly. Then a campaign needs approving, a client asks for changes and three meetings appear on your calendar. The setup gets pushed to next week while you continue dragging work through the same collection of chats, files and tools. You may already have several useful pieces. A Project containing your brand documents or a prompt that produces a decent brief. Maybe you even have an agent with a name and job title. But every task still begins...

AI Creative Campaigns

Hello Reader, A recent post in r/marketing collected dozens of AI-generated posters from different companies. Same blocky type, painted illustrations and crowded layout, even when the companies had nothing in common. At the start of this week the post had 932 upvotes and 250 comments. People had opinions. Some defended the posters as an effective way for small organizations to make something presentable. Others said they’d started scrolling past the style because every poster looked the same....

Client acquisition

Hello Reader I'm busy. You're busy. And every agency owner and fractional CMO I know is running the same two tracks right now. Track one is "deliver more with less, with AI, faster." Track two is "keep growing pipeline so track one keeps running." Track one wins my calendar most days. I don't think much about track two until the pipeline dries up and then I panic and go looking for a quick fix. I know I shouldn't, but I get sucked into the LinkedIn and YouTube hype. Someone posts about the...