Episode 372: Introducing Ask skucast

We have a confession about skucast: even we couldn't remember which episode held which piece of advice. Nine years of conversations is a lot to carry around in your head, and when the guests are this good, the advice piles up faster than anyone can keep track of it.

So we built something to fix that. Ask skucast is a free tool that lets you put a question to every guest who has ever sat down with Bobby, all at once. Ask about growing your book, hiring, pricing or working with suppliers, and the answer comes from what those guests said on the show, with a citation to the episode so you can hear the full conversation yourself.

This one is a shorter, behind-the-scenes episode. Bobby Lehew demos the tool live, then brings on our own Ritika Chhikara (Ritz), commonsku's Content Marketing Manager and skucast's executive producer, to explain how it got built. Ritz is Toronto-based, has an Ivey MBA, and started her career as a computer engineer, which makes her one of the few people who can argue with both the marketers and the developers and win.

On today's show, we get into why the AI was the easy part, why we made the tool smaller on purpose, and what the first round of anonymous questions says about where distributors are stuck.


AI Bobby, Live on the Air

Bobby opens by asking the tool how distributors are structuring their sales teams, and lets the answer play in full. The voice sounds uncannily like him. The content is pulled from past guests: Caleb Gilbertson of Imprint Engine on delegating your least favourite work first and layering in leadership over a decade, Tom Havens on scaling to eight sales teams with fifteen designers behind them, and the case for team-based management over isolated contributors. Each point traces back to a specific episode.

The Unglamorous Middle

Ask anyone who has built one of these and they will tell you the model is rarely the hard part. Ours was no different. The archive lived in audio, which machines cannot read, so step one was gathering transcripts for more than 350 episodes. Step two was the grind: guest names mangled by the transcription, industry terms garbled beyond recognition, and every file stamped with the same date on ingest, so the tool believed nine years of conversations had all happened last year. Ritz and Bobby spent most of the project adding context, correcting names, and tagging who each guest was and what each episode covered, so the retrieval had something solid to grip.

Making the Problem Smaller

"If you're across a problem that's too big, you make the problem smaller."

— Ritz

The original plan was more ambitious. We wanted the tool to draw on everything: skucast, every issue of The Backpack, every article we have published. It didn't work. With that much unstructured content, a useful answer took 40 to 50 seconds to arrive. Tuning for speed produced answers so generic they weren't worth reading. The fix was to narrow the scope to skucast alone, and the constraint turned into the best feature. Because every answer now lives inside a single show, every answer can link to the exact episode behind it.

What People Are Already Asking

The tool reports topics anonymously (no names unless someone volunteers one), and two buckets dominate early. The first is growth: how to prospect, how to land bigger accounts, how to break through a revenue plateau. The second is teams: how to structure a sales team, how to pay people, how to lead them. A handful of platform support questions have also come through, and for those, this is the wrong door. Ask skucast answers the questions you would bring to a mentor, not to your commonsku account rep. Beyond helping us fix weak spots, the pattern of questions is quietly shaping who we invite onto the show next.

In this episode, we also discuss:

  • The AI tools already running behind every skucast episode, from text-based editing in Descript to transcript cleanup and show notes in Claude
  • What RAG (retrieval-augmented generation) means in plain language, and why the source pool decides the quality of every answer
  • Bad-model days, and Ritz's advice to close the laptop and come back tomorrow
  • Why we sat on the tool for a couple of months before releasing it
  • What might come next, including The Backpack and the AI Promo Brief

Ask skucast

An AI built on 350+ episodes of the show. Ask it anything you'd ask a mentor.

Try Ask skucast →

Curious about the platform behind the podcast? Book a demo with commonsku.

Show Notes: Key Timestamps & Topics

[00:00:06] Nine years, 350 episodes, and the problem Ask skucast was built to solve

[00:01:26] Live demo: how distributors are structuring their teams for selling

[00:03:00] Introducing Ritz, Content Marketing Manager and skucast executive producer

[00:04:05] The AI stack behind the show: Descript and Claude

[00:05:23] Turning nine years of audio into something a machine can read

[00:06:59] "Anyone can build this now": the new ceiling is content and patience

[00:08:48] Why we drew a line at skucast episodes only

[00:10:23] Growth and teams: what people are asking, anonymously

[00:12:37] What's next for Ask skucast


 

🎙️ Read Full Episode Transcript +

[00:00:06] Bobby: Well, it's been nine years of the skucast, 350 episodes, and somewhere in that archive, one of our guests has already answered a question about business you're asking right now. The trouble has always been finding it. On today's brief show, we're going to share a little bit more about an AI tool we built to fix that.

[00:00:23] It's called Ask skucast. It's live now at commonsku.com/ask-skucast. And welcome to skucast, the podcast for innovators and maverick thinkers in the promotional product space. My name is Bobby Lehew. I'm the Chief AI Officer at commonsku, and I'm glad you're here. Ask skucast is a free tool that allows you to ask a question to the entirety of our guests at once, all of our skucast guests at once, whether it's growing your business, supplier relationships, hiring, building a team, AI.

[00:00:51] Answers come from what our guests said, and it cites the episode so you can go hear the whole conversation. You know how some folks love a behind-the-scenes or how we built it? Well, we're gonna do that today, demo for you how it works, and tell you why and how we built it. But first, a huge thank you to all our guests for sharing their wisdom.

[00:01:09] This kind of experience is only possible because each and every one of you have been generous with your time and your advice. So this is not only a great resource, but it's a testament to their generosity and to your generosity. For today's episode, I'll play a few examples, or one primary example, of how Ask skucast works.

[00:01:26] I'll ask it a question and let you hear how I, or rather how AI Bobby, responds. It's about to get real meta. Here's one example. I ask Ask skucast, "How are distributors structuring their teams for selling?" Here's the reply.

[00:01:41] AI Bobby: It really depends on the size and sophistication of the distributor. I've talked to distributors everywhere from five people to 500, and there's no single playbook. What I've seen work is this: the distributors who are scaling intentionally build out layers of leadership first. Caleb Gilbertson at Imprint Engine talks about the Delegate and Elevate framework.

[00:02:01] You look at what you're doing today that you don't like doing, and that's the first thing you delegate. Over time, you build an executive team. He went from doing everything himself to having a full C-suite, and that happened over a decade of deliberate moves. On the sales side specifically, Tom Havens described scaling to eight sales teams with 15 designers backing them up.

[00:02:22] That's a structure where you've got specialized roles, salespeople in the field, design support behind them, and the infrastructure to make both effective. The other thing that matters is how you connect your team to your systems. Team-based management, where people work in collaborative units rather than as isolated contributors, seems to make a huge difference as you grow.

[00:02:42] When you've got visibility across what the whole team is doing, you can scale faster and catch problems earlier. But honestly, the structure that works depends on who you're selling to, how you're selling, and what your margin structure looks like. A distributor selling to local businesses needs a different team than one chasing national accounts.

[00:02:59] Bobby: Now that's just one example, but I thought I'd invite Ritz, who's the executive producer of the skucast, on for a brief minute to talk about the how.

[00:03:06] Ritika Chhikara is our Content Marketing Manager at commonsku and the executive producer of this show, which means she's the reason these episodes exist at all, and she's the architect behind Ask skucast. Along with Joel on our team, who edits every one of our episodes, they all make me sound a lot smarter than I am.

[00:03:23] Ritz is Toronto-based, an Ivey MBA, and before any of the content work, she trained as a computer engineer — from circuits to storytelling, as she puts it — which turns out to be exactly the right background for a project like this one. Here's my chat with Ritz.

[00:03:36] Bobby: Well, Ritz, welcome to skucast, which is a really funny thing to say to the person who produces it, but welcome.

Ritz: Great to be here, Bobby. Yeah, it is a little weird being on this side of the mic.

Bobby: For listeners who only ever hear the finished episode, what they don't know is you and I obsess about AI, all things AI, and we've been working as colleagues really closely regarding AI for a while.

[00:03:58] Before we get into Ask skucast, can you talk about what other AI tools we've used for producing the show?

[00:04:05] Ritz: Yeah, absolutely. I'd say the big one is really Descript, and for those who don't know what that is, it's a video editor which has these amazing AI features baked into it. And the one that we live in is text-based editing, where you can essentially cross out a line from the transcript and it's just gone from the audio.

[00:04:27] It's just so easy. Anyone can use it. You don't have to be a video editor to really produce anything at all. Although we have a great video producer. That's Joel, and she ends up taking the first pass on all of our episodes. And once that is locked in Descript, that's when Claude comes in. So we've set up these skills and projects in Claude that end up cleaning up the transcripts, setting up the show notes for us, also getting some of those customer quotes ready for socials.

[00:04:58] Bobby: Having wrangled podcasts in the past, you and I know just how complicated some of the audio engineering can be.

[00:05:04] There's just so many details and nuance that now are a click of a button. And so that's part of the reason why we got really excited with AI early on, because we saw it working in audio. But anyways, let's get into how Ask skucast got made. Now, we had nine years of conversation basically sitting in a library of audio files.

[00:05:23] So what happened to those files before any of it could answer a question?

[00:05:26] Ritz: Yeah, that's a great question, Bobby. You know, people assume AI is gonna be the hard bit. The hard bit is really the data cleanup. It's, like you mentioned, nine years, more than 350 episodes that we've produced, and all of them sitting in audio, something that the machines cannot read.

[00:05:45] So I guess the first part is gonna be the transcripts, getting our hands on all of those transcripts, which was a bit tedious, but it's also... It wasn't the hardest bit. The cleaning up of the transcripts — as you can imagine, the transcripts had all of our guests' names that were wrong, the industry terms, they were all babbled.

[00:06:03] And once we were able to ingest it to our tool, they all got stamped the same date. So as far as the tool goes, all of these conversations happened in the last year. So really, the big part was a lot of cleanup, a lot of adding more context to all of our transcripts — who the guest is, what that episode is about — so that the retrieval could grab onto something.

[00:06:26] And yeah, the unglamorous truth is that data work was most of what the project was about.

[00:06:32] Bobby: Yeah, it's kind of wild to think, because now transcriptions are much cleaner than they used to be. We're talking nine years ago, which is just eons ago in terms of AI, you know? So for anyone listening who's sitting on a pile of their own content and sort of wondering whether they could do something like this.

[00:06:46] Now, this could be something internally. They may be sitting on piles of content internally or externally. Maybe they've got blog posts, things like that. What did this show you, this whole process of going through it? What did it show you in terms of what's possible with AI?

[00:06:59] Ritz: Anyone can build this now, and genuinely anyone.

[00:07:03] There are no excuses left. As you know, I am an engineer, but I also want to say that that was almost a lifetime ago, and I did not need any of that knowledge to work on this particular project. The tools are really off the shelf, and it sounds a little cliché when I say that the ceiling that used to be the technology and skill set is no longer there, but it's also so true.

[00:07:30] The new ceiling is gonna be your content and your patience. So if you are sitting on years of episodes or articles or webinars, you've already done the hard bit. Building the tool is really gonna be the easier side of it. One caveat, though. The difference between just building a fun experimental tool versus a tool that people are gonna come back to is gonna be the boring stuff.

[00:07:53] Like I mentioned, the cleanup, tightening up that scope, testing it out with questions until they stop being embarrassing. You know, we've been through that. And some of the days, the model just acts up and goes haywire. It's gonna come back with all sorts of nonsense for no reason whatsoever. We all have those days. It's gonna happen. Go for a walk, take the day off, come back to it the next day, and it's gonna be fine.

[00:08:20] Bobby: Yeah. I think one of the fun things that you and I explored through this, 'cause we were testing it with lots of questions, is how well, in the end, the AI was answering the questions.

[00:08:32] That was really cool. It's interesting: training a tool to draw down on the right conversations is probably one of the hardest parts. Our original concept was going to draw on all our content, but we sort of drew a line in the sand that it would only answer questions from the skucast episodes.

[00:08:48] Why did that line in the sand matter?

[00:08:51] Ritz: Yeah. So this is where I'm gonna geek out a little bit about the tools. So these tools, all of them work the same way underneath. You ask them a question, and it goes and fetches the most relevant chunk of content. This is what is essentially called a RAG.

[00:09:05] That's retrieval-augmented generation. And all of this fetching and all of the responses, how good or how bad they are, they all come down to what it's fetching from. Like I said, in our case, it was huge, and it was mixed. We were looking at all of our skucast episodes. We were looking at our newsletters, The Backpack, all of the issues we've done, all of the articles that we have produced.

[00:09:29] And that's where we hit the wall. To get a genuinely useful response — because the data was so much, and it was unstructured data — I remember initially it took us 40, 50 seconds to get a useful response, and no one has that amount of time in today's era. And when we tuned it up for more speed, we remember getting really generic, useless responses, and that's also when we were like, "This is not working at all."

[00:09:56] I guess that's when we pivoted. That's where we did what a reasonable person should do if you're across a problem that's too big: you make the problem smaller. So we pivoted to skucast only. And the fun bit is that the constraint ended up becoming a feature, where, you know, now every answer is linking back to a specific episode where you can go back.

[00:10:17] You can listen to them. It's grounded in that reality.

[00:10:23] Bobby: Ask skucast gives us anonymous reports of topics people are asking. So we only know names if people submit names, which you don't have to. It's anonymous. But what kinds of topics are we seeing surface to the top right now? And I actually wanna interject this thought.

[00:10:35] Ask skucast is the tool we dropped, and it's just the beginning, because we're learning what our distributor customers and the market is struggling with, whether it's building a team or driving sales and growth. But what kinds of topics are you seeing surface right now, and why is that important?

[00:10:51] Ritz: Yeah. But first, to reiterate, it is all anonymized, so we do not know who these conversations are being held with. That is a very important distinction to make here. But getting into topics, I think the two big buckets that we're getting: one is all about growth. So some of the questions will be, how do I prospect?

[00:11:11] How do I land bigger accounts? And how do I get past this revenue ceiling that I've been stuck at?

[00:11:16] Bobby: Yeah.

[00:11:17] Ritz: And the other big one is all about teams. Mostly about how do I structure a sales team? How do I pay people? How do I lead them? Those kinds of things. So these are the two big buckets. We are getting a few platform-specific questions that are more for the support side, which we, you know, we understand why that could happen.

[00:11:35] But just to let everyone know, this is the wrong tool for that. It's been trained on skucast conversations, and that's all the value it's bringing — the stuff that you would ask from a mentor.

[00:11:47] Bobby: Yeah.

[00:11:48] Ritz: Yeah. And I think the second bit of the question was why this really matters.

[00:11:53] Bobby: Yeah.

[00:11:53] Ritz: It's really a live read of where the industry is at. So it's doing two things for us in the moment. It is showing us where the tool is weak so that we know what to fix and make it more useful for our users. And the second one is just showing us some of the topics that they are asking again and again.

[00:12:14] So if there's a topic that we haven't covered, it ends up getting us our guest drafts ready for the upcoming episodes.

[00:12:21] Bobby: We will keep shaping this tool as we go along. Ritz, thank you for all the work that you've done on this. It's been phenomenal. And it's funny, you and I have been sitting on this for actually a couple months.

[00:12:30] We could have released this a while back. We held on. It was good because we were able to make some final tweaks and improvements, but what's next on your list to improve?

[00:12:37] Ritz: Yeah, I mean, Ask skucast is definitely one. It's not one and done. We have to keep iterating on it, keep training on it. And second is building more of it.

[00:12:46] I know we've discussed, if people find this useful, then bringing this to other aspects, like maybe getting The Backpack. Backpack would be a really good choice, getting all of those trends in, and maybe AI Promo Brief after that. So again, there's a lot that we can build out here.

[00:13:04] It just boils down to the usefulness. Like, what are people really gonna be using it for?

[00:13:10] Bobby: Great. Ritz, thanks again for being on your own show. That was cool. Congrats to you for this tool, and we are excited to roll it out.

[00:13:20] Ritz: Oh, thanks a lot, Bobby.

Frequently Asked Questions

What is Ask skucast?+

A free AI tool from commonsku that answers business questions using only what guests have said across 350+ episodes of skucast. Every answer cites the episode it came from.

Is Ask skucast free?+

Yes. It lives at commonsku.com/ask-skucast, needs no signup, and there is no limit on questions.

What should promotional products distributors ask it?+

Anything you would bring to a mentor: prospecting, landing larger accounts, breaking through a revenue ceiling, structuring and paying a sales team, supplier relationships, and using AI in your business.

Does Ask skucast answer commonsku support questions?+

No. It is trained on skucast conversations, not the platform. For account help, use commonsku's regular support channels.

Is the voice really Bobby Lehew?+

No. It is an AI built on the show with Bobby's involvement and review. The guests supplied the advice; the tool makes nine years of it searchable.

Previous Post