Lots of calls, little learning
Discovery, sales and client calls every week — but what made the calls that closed work wasn’t captured anywhere.
WonderkidSocial creates YouTube content for its clients. The team runs a lot of calls — discovery calls, sales calls and client calls — and every new client starts with a 1.5–2 hour workshop to build their YouTube content and a long-term content plan. We built two agents: one that learns from the sales calls that closed, and one that builds each new content plan on what has worked before.

“We have a lot of calls — sales calls, discovery calls, client workshops. Now one agent tells us which questions to ask based on the calls that actually closed, and the other builds content plans from what has already worked for similar clients. Our plans start from real data instead of a blank page.”
Discovery, sales and client calls every week — but what made the calls that closed work wasn’t captured anywhere.
Each new client meant a 1.5–2 hour workshop to plan their YouTube content for a long time ahead.
What had performed for similar clients before wasn’t pulled into the next plan.
The first agent analyses every sales call — which questions were asked and which should have been — trained on the calls that previously turned into clients.
The second agent knows to look for similar past clients, analyses their content plans and the videos that were made, and generates a stronger plan from what has worked before.
Each new content plan starts with the knowledge of every plan and video before it — not a blank page.
One operating system where clients onboard and follow their reporting — with agents alongside it that learn from every event, from what performed to the copy that sold.
A rebuilt sales process, run by agents: new leads found and contacted with personalised cold email, every CRM lead enriched and qualified, audits pre-qualified.
HubSpot enriched and scored, lookalikes from three years of deals, leads pulled from competitors’ LinkedIn.
A 30-minute call. No slides — just your workflows, and what we’d build first.