Young sales professional working at a desk with a computer screen showing data in a modern office

The Sales Team That Was Too Good at the Wrong Thing

Marco Lobo
ยท11 min read
Share
Industry

B2B Coaching & Professional Services

Key result

3x qualified meetings, reply rates doubled, deal cycles compressed 40%

Challenge

Sales team spent 70% of time on manual prospecting instead of closing

What we built

Multi-agent outbound system: research, enrichment, scoring, and personalised sequencing

Tools connected
Claude CodeLinkedIn Sales NavigatorCRMEmail

TL;DR

  • The problem was not sales effort; reps were spending most of their week on signal hunting, enrichment, CRM admin, and first-touch writing instead of conversations.
  • A five-agent Claude Code system took over signal detection, research, qualification, outreach drafting, and CRM operations across the 50-plus-person team.
  • The platform moved from 20-30 qualified leads a month and sub-10% replies to triple the qualified lead flow, roughly double replies, and 40% shorter deal cycles.

How a global coaching platform stopped asking its best people to do work that was never human work to begin with.

Based on a real client engagement. Details changed for confidentiality.


Part One: The Dirty Secret of B2B Sales

Here is something that every VP of Sales knows and almost nobody says at conferences: the majority of time spent in a B2B sales team produces a vanishingly small fraction of its revenue.

Not because the people are bad. Because the work itself is structured wrong.

For decades, the dominant model for enterprise sales has been to hire more prospectors. More researchers. More BDRs. Each one doing the same loop: find a company, check if it fits the profile, find the right contact, write a personalised message, push the result into the CRM, repeat. The logic was always that volume was the answer โ€” that if you hired more people and gave them better lists, the numbers would improve.

They improved. A little. Never enough.

The coaching industry, specifically, had a particular version of this problem. Selling leadership development or talent programs to enterprise HR teams requires a level of contextual precision that generic lead generation simply cannot deliver. A company posting about "employee engagement initiatives" is a different conversation from a company whose CEO just published a LinkedIn essay about the leadership gap they're facing after a round of layoffs. Both are signals. One is warm. The other is urgent. A human who's been in the space for three years can tell the difference instantly.

The problem was that finding those signals โ€” at scale, in real time, across hundreds of companies simultaneously โ€” was not a human-scale task. It never had been. The industry had simply decided to pretend otherwise and hire accordingly.

By the time the platform's revenue leadership looked honestly at their funnel, the numbers told the story plainly. Twenty to thirty qualified leads per month. Reply rates under ten percent. Deal cycles averaging a hundred and twenty days. Conversion rates hovering at fifteen. Not for lack of effort โ€” the team was working hard. But effort applied to the wrong work produces the wrong results, no matter how much of it you apply.


Part Two: The Decision Nobody Was Quite Ready to Make

The brief that landed at AI Heroes was, on the surface, familiar: help us do more prospecting, faster. But as the discovery conversations deepened, what emerged was a different brief entirely. The platform didn't need more prospecting. It needed to stop prospecting in the conventional sense altogether.

The proposal AI Heroes brought back was a bespoke multi-agent AI system built on Claude Code โ€” Anthropic's agentic development engine โ€” that would handle the entire top-of-funnel operation autonomously. Not assist with it. Not speed it up. Replace it.

There was resistance. There is always resistance. The sales leadership's concern was a reasonable one: personalisation was their edge. Every message felt like it came from a person who had actually read the prospect's LinkedIn page. If you automated that, you'd end up with the same generic sequencing the whole industry had already drowned in. Prospects could smell automated outreach. They'd been burned before.

AI Heroes' answer was that the problem with automated outreach wasn't automation. It was the quality of reasoning behind it. Most tools were pattern-matching on keywords. Claude Code could actually understand what a LinkedIn post meant in the context of an enterprise's talent strategy โ€” and respond to that meaning, not the surface signal.

The platform ran a two-week beta with a ten-person sales pod. By the end of the first week, reply rates had moved from eight percent to fourteen. By the end of the second, they were at eighteen.

The rollout decision, after that, was easy.


Part Three: What the Machine Actually Does (In Human Terms)

The system that went live across the platform's fifty-plus person sales team is, underneath the technical architecture, five agents doing five jobs that used to occupy the majority of every sales rep's working day.

The Scout

The first agent doesn't wait for someone to hand it a list. It goes looking. It scans LinkedIn posts, job boards, and public business discussions continuously, trained to recognise the specific signals that indicate an enterprise is in active pain around talent development โ€” companies posting about leadership vacancies at the executive level, HR leaders publicly discussing retention challenges, organisations whose recent job postings suggest a strategic push into learning and development. It filters noise. It surfaces intent. What used to take a rep an hour per company now takes the Scout seconds per hundred.

The Researcher

Once a company surfaces as a signal match, the second agent builds the file. It finds the right contact โ€” not just any contact, but the HR Vice President or L&D Director who will actually care about the conversation โ€” appends company context, recent public activity, firmographic details, and any relevant inflection points the Scout flagged. In under a minute, a blank entry becomes a complete prospect profile.

The Judge

The third agent has one job: say no. It applies the platform's Ideal Customer Profile criteria โ€” company size, industry, the specific pain points that indicate readiness โ€” and scores every enriched lead from zero to a hundred. Anything below the threshold gets rejected before it ever reaches a human. This is the step that most automation tools skip, and it's the reason most automated outreach feels generic: it's written for everyone, which means it resonates with no one.

The Writer

The fourth agent is where the earlier scepticism was really tested. It writes the outreach. Not templates with variables swapped in. Actual messages, grounded in the specific signal that surfaced the company and the specific context of the person receiving them. A message that references a CMO's recent post about hybrid team performance. A follow-up that acknowledges a company's announced expansion into new markets and connects it to what leadership capacity gaps typically emerge during that kind of growth. It runs A/B variations. It iterates based on what gets replies. It learns.

The Administrator

The fifth agent does what no sales rep has ever genuinely enjoyed doing: the CRM work. Every qualified lead pushed into HubSpot. Every engagement logged. Every sequence triggered without manual input. Deal stages updated. Reps notified via Slack when a prospect engages. The pipeline stays clean because nothing depends on a rep remembering to update it.


Part Four: The Numbers That Surprised Everyone โ€” Including the People Who Built It

The metric everyone expected to move was lead volume. And it did โ€” qualified leads went from roughly twenty-five per month to seventy-five. That was the plan.

The metric nobody expected to move was reply rate.

Reply rates in B2B outreach are stubborn. The industry average sits in the single digits. The platform's team, doing personalised outreach manually, had been at eight percent โ€” already above average, because the team was genuinely good at this. When the AI system pushed replies to twenty percent, the sales leadership ran the numbers twice. Twenty percent, at scale, to cold enterprise prospects. That was not what the team had been told to expect from automation.

What it meant was that the personalisation concern โ€” the fear that machines would flatten the human quality of the outreach โ€” had been wrong. Or at least, wrong in the specific way it was framed. The machine wasn't worse at personalisation than the best human on the team. For the mid-tier volume of outreach that nobody had time to do well manually, it was considerably better.

MetricBeforeAfter
Qualified leads per month2575
Outreach reply rate8%20%
Meetings bookedBaseline3x
Prospecting time per repBaseline-50%
Average deal cycle120+ days72 days
Pipeline value growthโ€”+35%

The deal cycle compression โ€” from a hundred and twenty days to seventy-two โ€” was the result nobody had modelled for. When prospects receive outreach timed to the moment they are actively in pain, rather than whenever a rep gets around to them, the conversations start warmer. The first call skips the needs-assessment phase that usually eats the first two meetings. Things move faster because the entry point is better.


Part Five: What This Is Really About

The temptation, when you look at results like these, is to write a story about artificial intelligence. About what Claude Code can do. About multi-agent architectures and agentic reasoning engines and the future of GTM automation.

But that would miss the actual story.

What the platform discovered is something much older and more uncomfortable than any technology: that for years, they had been asking their most valuable people to spend most of their time doing work that those people were wildly overqualified for, and that the work was suffering because of it. Not despite human involvement. Because of it โ€” because humans at scale and under time pressure are inconsistent in ways that a well-designed system is not.

The best instincts, applied to the right twenty conversations, are irreplaceable. Those same instincts, applied to two hundred and thirty LinkedIn tabs before 9am, are diluted to the point of being indistinguishable from a template.

The AI system didn't replace the team. It gave them back the thing they were actually hired to do.


It is 8:34am on a Wednesday. The first rep arrives at her desk. She has a Slack notification: seventeen new qualified leads, already enriched, already scored, three flagged as high-priority based on signals that came in overnight. There are two replies in her inbox from prospects who responded to outreach sent at 6am, before she was out of bed. One wants to book a call for Thursday. One has questions about the executive coaching programme.

She opens her calendar. She reads the replies. She thinks about what she wants to say.

She does not open LinkedIn.

The agent built for this

Frequently Asked Questions

Marco Lobo

Founder, AI Heroes

I build AI companies and the systems inside them. At AI Heroes, we give businesses the functional capacity to grow without the headcount growth normally demands โ€” sales that follows up, marketing that runs, content that ships, ops that handles itself. We audit where you're leaving growth on the table, build the team that captures it, and hand it over completely.

I've built at scale before. Leading product and GTM at SlideSpeak AI (1M+ monthly users, profitable, bootstrapped). CPO at Disperse โ€” the AI construction platform that went from 3 to 200+ people on $35M raised. I also co-founded LOBOMAR, a luxury fashion label featured in Elle, Cosmopolitan, and the LA Times, with shows at the London Design Museum, Wereldmuseum, and Amsterdam Fashion Week.

Related Articles

Woman in glasses reviewing stacks of legal documents at a desk with a typewriter and folders labelled Manchester Conveyancing
AI SolutionsLegalConveyancing

The Stack of Leases That Never Got Smaller

A Manchester conveyancing firm spent years turning away portfolio deals. Then they changed one thing about how their fee earners spent their Tuesdays.

Marco Lobo
Marco Loboยท6 Mar 2026ยท12 min read
Editorial pen-and-watercolour scene of an AI-native engineering pipeline: a fast stream of AI-generated pull requests flowing from a Claude-assisted source into a single human review-and-security checkpoint that has become the bottleneck, with small Claude and GitHub wordmarks used editorially
AI EngineeringAI-Native EngineeringEngineering Leadership

How to Run an AI-Native Engineering Org in 2026

Agentic coding doesn't remove the engineering bottleneck โ€” it moves it from writing code to verifying it. Here's the 2026 operating model for an AI-native engineering org: the processes to rewrite, how code review changes, and the metrics that prove it's working.

Marco Lobo
Marco Loboยท3 Jun 2026ยท11 min read
AI Heroes illustration of Claude Code dynamic workflows coordinating planner, worker and evaluator agents around a shared evidence store.
AI AgentsClaude CodeDynamic Workflows

Claude Code Dynamic Workflows: What Is Actually New in 2026?

Claude Code dynamic workflows are not just parallel agents. They turn a prompt into an executable orchestration script that can split work, store intermediate results, cross-check findings and return one synthesised answer.

Marco Lobo
Marco Loboยท29 May 2026ยท11 min read