Dale Carnegie runs business training and professional development. Between February and July 2026 I rebuilt how their HubSpot drives sales: a call priority queue, plus three AI agents working inside the same instance. Meetings booked went from 5 a month to 91, with no added headcount. This is how it came together.
The starting point
7,000 contacts sat in HubSpot with plenty of volume and no working priority system. Reps were guessing who to call next, and the database wasn't earning its keep. The baseline, measured before anything changed:
- 1,703 contacts under active management.
- 1,292 contacts in active sequences.
- 633 calls made a month.
- 5 meetings booked a month.
Why wasn't the first build an AI agent?
Because the leak wasn't a missing agent. It was plenty of contacts and no order to work them in, so the first build was a call priority queue that ranks the database and tells reps who to call next. Every engagement starts with a diagnosis of where revenue is actually leaking, and here the leak was obvious once it was measured.
Which AI agents run in Dale Carnegie's HubSpot?
Three, each taking one repetitive job off the team. With the queue in place, I added a full AI-agentic revenue operations layer on top of it:
- The enrichment agent preps every contact before the call.
- The coaching agent reviews calls and reports back to the team.
- The re-engagement agent automatically follows up with anyone who doesn't book.
What results did the agents deliver?
Meetings booked went from 5 to 91 a month. Between February and July 2026, inside the same HubSpot instance and with the same headcount:
- Contacts under active management: 1,703 to 11,413 (6.7×).
- Contacts in active sequences: 1,292 to 2,375 (1.8×).
- Calls made a month: 633 to 1,247 (2.0×).
- Meetings booked a month: 5 to 91 (18.2×).
Calls roughly doubled, but meetings grew eighteen-fold: meetings per 100 calls went from under 1 to more than 7. That's the compounding effect of the priority queue and all three agents working together in the background.
At any given time, 2,375 of the 11,413 contacts, about 21% of the database, are inside an active AI-managed sequence. The rest sit ranked and ready in the priority queue, waiting their turn instead of getting lost.
“The sales engine works. They never thought HubSpot could work together with AI agents this way. HubSpot's own features are maximized, and it's still assisted by AI that acts like 24/7 employees, consistently monitoring, building, coaching and reporting.”
What came next
Dale Carnegie has since signed a new contract for the marketing side of the business. An agent builds tailor-fit email templates and its own banner creative per audience segment, writes copy per segment instead of one-size-fits-all blasts, and reports on opens, clicks and engagement as part of the standing workflow.
What to take from it
- Fix the order of work before adding agents. The priority queue came first.
- Agents compound when they share one system: prep, call review and follow-up all feed the same HubSpot.
- Measure from day one. Every number above has a baseline from before the build.
The case studies page has the charts behind these numbers. To see what a build like this includes, read about HubSpot services, or start with a short call.
Quick answers from this post.
Did Dale Carnegie hire more reps to get these results?
No. Calls made nearly doubled and meetings booked went from 5 to 91 a month in the same HubSpot instance, with no added headcount.
What does each of the three agents do?
There's an enrichment agent that preps every contact before the call, a coaching agent that reviews calls and reports back to the team, and a re-engagement agent that follows up with anyone who doesn't book.
What was built before the agents?
A call priority queue that ranks the database and tells reps who to call next. The three agents were added on top of it.