WEBVTT 00:00:00.000 --> 00:00:03.779 Imagine paying $250 a month just for the privilege 00:00:03.779 --> 00:00:06.919 of knowing exactly when, like, 5 ,000 people 00:00:06.919 --> 00:00:08.320 have heard your voice. Which is wild, right? 00:00:08.400 --> 00:00:10.080 Because anywhere else on the internet, that is 00:00:10.080 --> 00:00:13.019 just basic data. Exactly. I mean, you post a 00:00:13.019 --> 00:00:16.079 video on YouTube, you watch the view count hit 00:00:16.079 --> 00:00:18.719 5 ,000, and you just move on. It's completely 00:00:18.719 --> 00:00:21.539 free. Yeah. But in the podcasting world, that 00:00:21.539 --> 00:00:24.679 exact hard cap number is a total luxury. It's 00:00:24.679 --> 00:00:26.660 something only the enterprise class seems to 00:00:26.660 --> 00:00:30.149 get. It really is. And welcome to the deep dive, 00:00:30.269 --> 00:00:31.809 by the way. If you're listening to this, you 00:00:31.809 --> 00:00:34.390 are probably standing at the edge of this massive, 00:00:34.670 --> 00:00:37.350 incredibly murky landscape, just trying to figure 00:00:37.350 --> 00:00:39.990 out where your audio actually belongs. And we 00:00:39.990 --> 00:00:42.009 have brought together a huge stack of research 00:00:42.009 --> 00:00:43.869 to help you figure that out. We really have. 00:00:43.950 --> 00:00:46.170 We've got platform feature guides, in -depth 00:00:46.170 --> 00:00:48.890 pricing comparisons from places like Alitu and 00:00:48.890 --> 00:00:53.670 Boomcaster, verified G2 user reviews, and... 00:00:53.770 --> 00:00:57.130 This one highly specific, kind of painfully revealing 00:00:57.130 --> 00:00:59.689 Reddit thread from the pro podcasting community. 00:01:00.189 --> 00:01:02.210 That Reddit thread is fascinating, honestly. 00:01:02.570 --> 00:01:05.569 It just exposes this massive disconnect between, 00:01:05.569 --> 00:01:08.530 you know, with the marketing page's promise and 00:01:08.530 --> 00:01:10.709 what independent creators actually end up dealing 00:01:10.709 --> 00:01:12.969 with. Right, because the market has just fragmented 00:01:12.969 --> 00:01:15.769 in ways nobody saw coming a decade ago. Totally. 00:01:16.269 --> 00:01:21.049 So our mission today is laser focused. For you, 00:01:21.109 --> 00:01:24.109 the listener, the goal is to choose a hosting 00:01:24.109 --> 00:01:26.650 platform that is tailored specifically to your 00:01:26.650 --> 00:01:29.370 budget and your technical experience level. We're 00:01:29.370 --> 00:01:31.469 cutting straight through the marketing jargon 00:01:31.469 --> 00:01:33.890 today. Oh, 100%. We're going to compare the features 00:01:33.890 --> 00:01:36.829 you actually care about. So ease of use, dynamic 00:01:36.829 --> 00:01:39.829 ad insertion, advanced analytics, AI transcription, 00:01:40.209 --> 00:01:43.109 and even custom website builders. Because right 00:01:43.109 --> 00:01:46.310 now, choosing a host feels a lot like trying 00:01:46.310 --> 00:01:48.989 to buy a house in a completely unregulated market. 00:01:49.170 --> 00:01:53.000 Yes. That's the perfect analogy. Do you want 00:01:53.000 --> 00:01:56.140 a move -in -ready condo where everything is managed 00:01:56.140 --> 00:01:57.500 for you, but you're not allowed to paint the 00:01:57.500 --> 00:01:59.599 walls? Right. Or do you want that raw plot of 00:01:59.599 --> 00:02:01.540 land where you have to run all the plumbing yourself, 00:02:01.819 --> 00:02:05.060 but you own every single bleed of grass? Exactly. 00:02:05.579 --> 00:02:08.259 And more importantly, what are you actually paying 00:02:08.259 --> 00:02:11.800 for when some platforms charge literally nothing 00:02:11.800 --> 00:02:14.219 and others want hundreds of dollars a month? 00:02:14.419 --> 00:02:17.120 To understand that crazy price gap, we really 00:02:17.120 --> 00:02:19.810 have to break down what a podcast host actually 00:02:19.810 --> 00:02:22.210 does at a mechanical level. Right. Because I 00:02:22.210 --> 00:02:24.530 think a lot of people just assume it's like uploading 00:02:24.530 --> 00:02:27.409 a video to YouTube. And it's fundamentally not. 00:02:27.590 --> 00:02:30.250 No, it's not. So let's start right there. Because 00:02:30.250 --> 00:02:31.990 if you're just starting out, your budget might 00:02:31.990 --> 00:02:34.530 be zero. And your technical experience might 00:02:34.530 --> 00:02:36.509 also be zero. You just want to get your voice 00:02:36.509 --> 00:02:39.139 out there. Exactly. And the first name that inevitably 00:02:39.139 --> 00:02:42.699 pops up is Spotify for creators. Formally anchor 00:02:42.699 --> 00:02:44.960 for those who remember the old branding. Right. 00:02:45.080 --> 00:02:47.840 They rebranded it and their big neon flashing 00:02:47.840 --> 00:02:51.340 selling point is that it is completely 100 percent 00:02:51.340 --> 00:02:54.340 free. Not just a trial either. No. Unlimited 00:02:54.340 --> 00:02:57.479 audio and video hosting forever. Which is, I 00:02:57.479 --> 00:03:00.060 mean, in a space where server storage and bandwidth 00:03:00.060 --> 00:03:02.840 are physical things that cost actual money. How 00:03:02.840 --> 00:03:04.659 on earth are they doing that? Well, it all comes 00:03:04.659 --> 00:03:07.020 down to the underlying philosophy of the open 00:03:06.960 --> 00:03:09.379 web versus the walled garden. OK, break that 00:03:09.379 --> 00:03:13.219 down for me. So historically, a podcast host 00:03:13.219 --> 00:03:16.580 really only had one job. It was there to generate 00:03:16.580 --> 00:03:20.099 and host an RSS feed. An RSS feed. Right. And 00:03:20.099 --> 00:03:23.039 an RSS feed is essentially just a simple text 00:03:23.039 --> 00:03:25.719 document. It's a list of instructions. OK. When 00:03:25.719 --> 00:03:28.340 you publish an episode, you're putting an MP3 00:03:28.340 --> 00:03:31.560 file on a server. And the host updates that text 00:03:31.560 --> 00:03:34.289 document to basically say, hey, Episode 1 is 00:03:34.289 --> 00:03:37.550 located at this exact web address. So apps like 00:03:37.550 --> 00:03:40.030 Apple Podcasts or Overcast, they don't actually 00:03:40.030 --> 00:03:42.409 hold your audio file. Exactly. They don't host 00:03:42.409 --> 00:03:44.389 anything. They just read that text document and 00:03:44.389 --> 00:03:46.610 pull the file from your host server whenever 00:03:46.610 --> 00:03:48.889 someone hits play. OK, so it's like a digital 00:03:48.889 --> 00:03:51.430 phone book. Apple Podcasts just looks up the 00:03:51.430 --> 00:03:53.669 number and dials it. That is a perfect way to 00:03:53.669 --> 00:03:55.949 think about it. Now, generating that text document 00:03:55.949 --> 00:03:58.550 and hosting those heavy MP3 files, that costs 00:03:58.550 --> 00:04:00.909 money. Right. Server space isn't free. So when 00:04:00.909 --> 00:04:03.159 Spotify for creators offers to do all of this 00:04:03.159 --> 00:04:05.979 for free with unlimited storage, they're actively 00:04:05.979 --> 00:04:08.599 absorbing that massive server cost. But why? 00:04:08.840 --> 00:04:10.599 What's in it for them? Because they're playing 00:04:10.599 --> 00:04:12.699 a much larger game. They want to own the entire 00:04:12.699 --> 00:04:15.560 ecosystem. Ah, I see. They give you monetization 00:04:15.560 --> 00:04:18.060 tools like subscriptions and access to their 00:04:18.060 --> 00:04:20.720 Spotify audience network for programmatic ads, 00:04:21.660 --> 00:04:22.980 assuming you meet their thresholds, of course. 00:04:23.120 --> 00:04:25.420 Right, assuming you're big enough. But what's 00:04:25.420 --> 00:04:29.079 the trade -off there? The trade -off is control 00:04:29.079 --> 00:04:32.060 and support. Yeah, I was looking at some of the 00:04:32.060 --> 00:04:34.720 chatter online, the G2 reviews, and people were 00:04:34.720 --> 00:04:37.040 mentioning that recent updates actually stripped 00:04:37.040 --> 00:04:40.540 away some really beloved tools. Like what? Like 00:04:40.540 --> 00:04:42.540 they used to have these built -in transition 00:04:42.540 --> 00:04:44.319 tunes and background music that people loved, 00:04:44.500 --> 00:04:47.139 gone. Oh, wow. And worse, if something breaks, 00:04:47.459 --> 00:04:49.920 like say your RSS feed suddenly stops communicating 00:04:49.920 --> 00:04:52.519 with Apple, you are not getting a human being 00:04:52.519 --> 00:04:54.819 on the phone to help you. No, you're relying 00:04:54.819 --> 00:04:58.050 entirely on automated support. which can be a 00:04:58.050 --> 00:05:00.649 nightmare. Right. So when you use a totally free 00:05:00.649 --> 00:05:03.810 platform, you're making a deliberate trade. You're 00:05:03.810 --> 00:05:06.509 trading advanced white glove customer support 00:05:06.509 --> 00:05:09.949 and granular control for a highly frictionless 00:05:09.949 --> 00:05:13.089 free experience. Which, to be fair, is fantastic 00:05:13.089 --> 00:05:15.649 for testing the waters. It removes all the financial 00:05:15.649 --> 00:05:18.790 barriers to entry. It does. But if you're trying 00:05:18.790 --> 00:05:21.829 to build a serious business, that lack of human 00:05:21.829 --> 00:05:25.420 support becomes a massive liability. Okay, so 00:05:25.420 --> 00:05:27.060 let me push back on the alternatives, then. Go 00:05:27.060 --> 00:05:29.660 for it. Let's look at Buzzsprout. Our sources 00:05:29.660 --> 00:05:33.339 constantly cite them as a huge favorite for hobbyists, 00:05:33.839 --> 00:05:36.740 and they also offer a quote -unquote free tier. 00:05:36.819 --> 00:05:39.879 Right, they do. But it's a 90 -day trial, they 00:05:39.879 --> 00:05:42.220 limit you to just two hours of audio a month, 00:05:42.920 --> 00:05:45.699 and the kicker. After 90 days, they literally 00:05:45.699 --> 00:05:47.920 delete your episodes. They wipe them from the 00:05:47.920 --> 00:05:50.970 server. It just feels so cunative. If Spotify 00:05:50.970 --> 00:05:54.009 is free forever with unlimited storage, why would 00:05:54.009 --> 00:05:56.009 anyone subject themselves to a platform that 00:05:56.009 --> 00:05:57.709 actively deletes their hard work after three 00:05:57.709 --> 00:05:59.970 months? I know, it sounds totally counterintuitive 00:05:59.970 --> 00:06:02.250 at first glance. It really does. But it really 00:06:02.250 --> 00:06:04.889 comes down to what you value more. Do you want 00:06:04.889 --> 00:06:09.149 raw, permanent storage? Or do you want an optimized 00:06:09.149 --> 00:06:11.490 workflow and education? Education, what do you 00:06:11.490 --> 00:06:13.930 mean by that? Buzzsprout isn't trying to be a 00:06:13.930 --> 00:06:17.259 permanent free locker. They are heavily invested 00:06:17.259 --> 00:06:19.899 in making the process of podcasting as simple 00:06:19.899 --> 00:06:22.759 as possible. They want to give you a taste of 00:06:22.759 --> 00:06:25.819 a premium workflow. Even on their lower tiers, 00:06:26.160 --> 00:06:29.300 they offer IAB certified analytics, which is 00:06:29.300 --> 00:06:32.660 huge for tracking real human downloads. Right. 00:06:32.680 --> 00:06:34.879 We'll definitely get into the IAB stuff later 00:06:34.879 --> 00:06:36.860 because it's super important. And they have these 00:06:36.860 --> 00:06:40.199 incredibly clean intuitive dashboards. So when 00:06:40.199 --> 00:06:42.889 you choose Buzzsprout, You're basically paying, 00:06:43.209 --> 00:06:45.629 eventually, when you upgrade to their $12 plan, 00:06:46.110 --> 00:06:48.670 for an ecosystem that actively teaches you how 00:06:48.670 --> 00:06:51.610 to be better at podcasting. Oh, I see. Many creators 00:06:51.610 --> 00:06:54.269 find that user experience so vastly superior 00:06:54.269 --> 00:06:57.509 to Spotify's that they will accept the 90 -day 00:06:57.509 --> 00:07:00.250 deletion rule. They use it to test the waters, 00:07:00.790 --> 00:07:03.079 knowing they plan to upgrade anyway. Okay, that 00:07:03.079 --> 00:07:04.660 makes sense. It's like a high -end gym giving 00:07:04.660 --> 00:07:06.800 you a free week pass, but you're only allowed 00:07:06.800 --> 00:07:08.779 to use the treadmills for 20 minutes at a time. 00:07:08.959 --> 00:07:10.920 Exactly. They want you to experience the nice 00:07:10.920 --> 00:07:13.560 locker rooms and the vibe, so you eventually 00:07:13.560 --> 00:07:15.639 buy the real membership. Right. But what if you 00:07:15.639 --> 00:07:18.660 just need raw permanent storage on a budget? 00:07:18.920 --> 00:07:21.360 Like, you don't want to be locked into Spotify's 00:07:21.360 --> 00:07:23.339 corporate ecosystem, but you also don't want 00:07:23.339 --> 00:07:25.839 your files deleted. That is where a platform 00:07:25.839 --> 00:07:28.600 like Podbean enters the conversation. They strike 00:07:28.600 --> 00:07:31.120 a really nice middle ground. What's their pricing 00:07:31.120 --> 00:07:33.779 look like? They have a free tier, but it's capped 00:07:33.779 --> 00:07:37.019 at five hours of total storage and 100 gigabytes 00:07:37.019 --> 00:07:39.740 of bandwidth per month. So no video, I assume? 00:07:39.860 --> 00:07:42.879 No video and no advanced monetization on the 00:07:42.879 --> 00:07:45.860 free tier. But their paid tier starts at just 00:07:45.860 --> 00:07:48.860 nine dollars a month, and that immediately unlocks 00:07:48.860 --> 00:07:51.680 unlimited audio. Nine dollars for unlimited audio 00:07:51.680 --> 00:07:54.519 is incredibly competitive. It really is. It's 00:07:54.519 --> 00:07:56.339 probably the best bang for your buck if sheer 00:07:56.339 --> 00:07:59.779 volume is your main concern. I also noticed RSS 00:07:59.779 --> 00:08:03.019 .com in our research stack. They start around 00:08:03.019 --> 00:08:05.139 five bucks a month, which is super cheap. Yeah. 00:08:05.180 --> 00:08:06.759 And they have a really interesting angle too. 00:08:06.879 --> 00:08:09.839 Right. They offer a completely free local and 00:08:09.839 --> 00:08:13.339 niche plan specifically for community focused 00:08:13.339 --> 00:08:16.660 or nonprofit style shows. Which I love. And it 00:08:16.660 --> 00:08:18.560 highlights a really important realization for 00:08:18.560 --> 00:08:21.759 creators. Which is? Paying for a host, even if 00:08:21.759 --> 00:08:24.300 it's just five or nine dollars a month, fundamentally 00:08:24.300 --> 00:08:26.300 changes your relationship with the platform. 00:08:26.410 --> 00:08:28.689 You transition from being the product to being 00:08:28.689 --> 00:08:31.329 the customer. Exactly. You gain leverage. You 00:08:31.329 --> 00:08:33.929 get a smoother workflow. You retain total control 00:08:33.929 --> 00:08:36.889 over your RSS feed. And you get access to way 00:08:36.889 --> 00:08:39.029 better analytics. OK, but let's pivot for a second. 00:08:39.269 --> 00:08:41.610 Let's say paying $9 isn't the issue. What if 00:08:41.610 --> 00:08:43.950 your biggest bottleneck isn't money, but time? 00:08:44.169 --> 00:08:47.110 Your time is the ultimate bottleneck. It really 00:08:47.110 --> 00:08:49.529 is. I know so many people who want to start a 00:08:49.529 --> 00:08:51.909 show, but the thought of learning how to use 00:08:51.909 --> 00:08:54.190 separate recording software and then taking that 00:08:54.190 --> 00:08:56.730 file into Audacity or GarageBand. And learning 00:08:56.730 --> 00:08:59.629 how to edit. Yes. And then exporting the MP3 00:08:59.629 --> 00:09:02.210 and then uploading it to a host. I mean, it's 00:09:02.210 --> 00:09:04.669 exhausting just saying it out loud. That manual 00:09:04.669 --> 00:09:07.750 friction is exactly what kills most new podcasts 00:09:07.750 --> 00:09:11.450 by, like, episode seven. Podfate is real. It 00:09:11.450 --> 00:09:14.769 is. But historically, a host was just a digital 00:09:14.769 --> 00:09:17.309 filing cabinet. Now we're seeing this massive 00:09:17.309 --> 00:09:21.129 paradigm shift toward what we can call the streamliners. 00:09:21.210 --> 00:09:22.970 The streamliners. I like that. So what are they 00:09:22.970 --> 00:09:24.870 doing differently? They're transforming from 00:09:24.870 --> 00:09:27.750 mere storage lockers into full -fledged all -in 00:09:27.750 --> 00:09:29.870 -one production studios right into your browser 00:09:29.870 --> 00:09:32.059 window. It reminds me of the difference between 00:09:32.059 --> 00:09:34.980 buying raw ingredients at the grocery store versus 00:09:34.980 --> 00:09:37.440 getting one of those meal kits delivered to your 00:09:37.440 --> 00:09:39.279 door. That's exactly what it is. Like the meal 00:09:39.279 --> 00:09:41.320 kit definitely costs a premium, but you save 00:09:41.320 --> 00:09:43.460 hours of prep time. You don't have to measure 00:09:43.460 --> 00:09:46.480 out the spices. And the recipe is basically foolproof. 00:09:46.759 --> 00:09:49.019 Riverside is a phenomenal example of this. Right. 00:09:49.259 --> 00:09:52.460 Their pro plan is $24 a month. So what is that 00:09:52.460 --> 00:09:54.840 24 bucks actually doing under the hood? Well, 00:09:54.980 --> 00:09:57.580 Riverside initially built its whole reputation 00:09:57.580 --> 00:10:00.929 on remote recording. Okay. If you and I are recording 00:10:00.929 --> 00:10:04.289 over a standard web tool, like Zoom, the audio 00:10:04.289 --> 00:10:06.370 is being compressed and sent over the internet 00:10:06.370 --> 00:10:09.669 in real time. Which means if your internet dips, 00:10:10.169 --> 00:10:13.009 the audio glitches. Right. And that glitch is 00:10:13.009 --> 00:10:15.669 permanently recorded into the file. Riverside 00:10:15.669 --> 00:10:18.710 bypasses that entirely. Wait, how? Do they not 00:10:18.710 --> 00:10:20.950 use the internet to record? They use the internet 00:10:20.950 --> 00:10:23.970 to let us see and hear each other live. But the 00:10:23.970 --> 00:10:27.009 actual high -resolution recording up to 4K video 00:10:27.009 --> 00:10:29.990 and pristine audio happens locally. Locally, 00:10:29.990 --> 00:10:33.049 like on my actual hard drive? Directly onto your 00:10:33.049 --> 00:10:35.210 computer's hard drive and my computer's hard 00:10:35.210 --> 00:10:37.830 drive. Ah! So it's like we both have physical 00:10:37.830 --> 00:10:40.470 tape decks sitting on our desks, recording our 00:10:40.470 --> 00:10:42.970 own voices perfectly, regardless of what the 00:10:42.970 --> 00:10:45.269 Wi -Fi is doing between us. Exactly. And while 00:10:45.269 --> 00:10:47.850 we're talking, it's quietly uploading those pristine 00:10:47.850 --> 00:10:50.649 local files to their servers in the background. 00:10:50.769 --> 00:10:53.870 That is so smart. But where Riverside has really 00:10:53.870 --> 00:10:56.549 evolved recently is that they've now become the 00:10:56.549 --> 00:10:59.909 host as well. They've integrated this AI co -creator. 00:11:00.129 --> 00:11:02.110 I saw that in the feature guide. What does the 00:11:02.110 --> 00:11:05.450 AI co -creator actually do? So you finish recording, 00:11:05.509 --> 00:11:08.330 and instead of downloading the files to edit 00:11:08.330 --> 00:11:12.309 yourself in Premiere or Audacity, their AI acts 00:11:12.309 --> 00:11:14.549 as your editing agent. It edits for you. Yes. 00:11:14.850 --> 00:11:17.529 It can assemble the episode. clean up the audio, 00:11:17.850 --> 00:11:20.029 generate your show notes, create a full transcript, 00:11:20.610 --> 00:11:22.889 and even pull out vertical promotional clips 00:11:22.889 --> 00:11:25.509 for social media. Oh, wow. And then from that 00:11:25.509 --> 00:11:28.110 exact same browser window, you literally hit 00:11:28.110 --> 00:11:30.710 a button and it publishes directly to your Spotify 00:11:30.710 --> 00:11:33.490 and Apple Podcasts feeds. That is wild. You never 00:11:33.490 --> 00:11:35.870 even leave the browser tab. But then we have 00:11:35.870 --> 00:11:39.129 Alitu. Our sources mention Alitu is billed specifically 00:11:39.129 --> 00:11:42.690 as a quote unquote podcast maker. Yes. But it's 00:11:42.690 --> 00:11:45.629 significantly more expensive. It's $38 a month. 00:11:46.570 --> 00:11:49.090 If Riverside is already doing all that AI magic 00:11:49.090 --> 00:11:53.549 for 24, what is Alitu's value proposition to 00:11:53.549 --> 00:11:57.110 justify an extra 14 bucks? Alitu is hyper -focused 00:11:57.110 --> 00:12:00.490 on podcasters who want absolutely zero technical 00:12:00.490 --> 00:12:03.070 friction and who are primarily audio -driven. 00:12:03.370 --> 00:12:05.529 OK, so no video. Right. It's mostly for audio. 00:12:05.669 --> 00:12:07.309 It's described almost like having a personal 00:12:07.309 --> 00:12:09.600 audio engineer who never sleeps. I could use 00:12:09.600 --> 00:12:12.080 one of those. While Riverside leads heavily into 00:12:12.080 --> 00:12:15.299 high -end remote video, Alitu focuses on automating 00:12:15.299 --> 00:12:18.120 the really tedious parts of audio editing. Its 00:12:18.120 --> 00:12:20.460 standout feature is the automatic audio cleanup. 00:12:20.759 --> 00:12:22.919 What does that entail? It automatically levels 00:12:22.919 --> 00:12:24.820 the volume, so you and your guests sound equally 00:12:24.820 --> 00:12:28.539 loud. It reduces background noise. And most importantly, 00:12:28.700 --> 00:12:31.740 it uses AI to automatically detect and remove 00:12:31.740 --> 00:12:34.779 filler words. Wait, like the ums and ahs? Exactly. 00:12:34.899 --> 00:12:37.360 The ums, the ahs, the awkward long pauses. It 00:12:37.360 --> 00:12:39.500 just sniffs them out cleanly. Wait, I was thinking 00:12:39.500 --> 00:12:41.899 about this when I saw that $38 price tag. At 00:12:41.899 --> 00:12:44.139 first, you get sticker shock. Sure. $38 is a 00:12:44.139 --> 00:12:46.679 lot for just hosting. But if I'm paying a freelance 00:12:46.679 --> 00:12:52.120 audio editor $50 or $100 an episode just to painstakingly 00:12:52.120 --> 00:12:56.080 cut out every time I say, um, Alitu's AI is actually 00:12:56.080 --> 00:12:59.779 replacing a human contractor. That is the exact 00:12:59.779 --> 00:13:02.179 mental calculation they want you to make. It's 00:13:02.179 --> 00:13:04.679 not just a storage locker. It's an employee. 00:13:04.899 --> 00:13:08.039 Exactly. It's designed for creators Maybe journalists 00:13:08.039 --> 00:13:10.500 or consultants or life coaches who need a really 00:13:10.500 --> 00:13:13.879 fast turnaround have zero audio engineering experience 00:13:13.879 --> 00:13:16.059 and just want to add theme music right in the 00:13:16.059 --> 00:13:18.500 browser and hit publish. The focus on the AI 00:13:18.500 --> 00:13:21.700 aspect for a second, specifically AI transcription. 00:13:22.000 --> 00:13:24.220 Oh, transcription is huge right now. It really 00:13:24.220 --> 00:13:26.519 is. Having a written transcript of your audio 00:13:26.519 --> 00:13:29.179 has become incredibly important, both for accessibility 00:13:29.179 --> 00:13:32.679 and for SEO. So how do these streamliners compare 00:13:32.679 --> 00:13:35.220 to the traditional hosts when it comes to getting 00:13:35.220 --> 00:13:38.460 a transcript? Riverside and Alitu have these 00:13:38.460 --> 00:13:41.179 transcription tools baked directly into their 00:13:41.179 --> 00:13:43.539 platform infrastructure. It's just part of that 00:13:43.539 --> 00:13:45.759 monthly fee you're already paying. OK, so it's 00:13:45.759 --> 00:13:48.299 all inclusive. Right. But the traditional older 00:13:48.299 --> 00:13:51.950 hosts, they are scrambling to catch up. by offering 00:13:51.950 --> 00:13:55.090 AI as an add -on service. Ah, I see. Yeah, I 00:13:55.090 --> 00:13:57.129 saw in the Boomcaster guide that Buzzsprout has 00:13:57.129 --> 00:13:59.990 something called Co -host AI. Yes. Co -host AI? 00:14:00.149 --> 00:14:03.309 It crafts show notes, chapter markers, and they 00:14:03.309 --> 00:14:07.049 have this magic mastering thing for audio enhancement. 00:14:07.230 --> 00:14:09.950 But it's an extra fee. A significant one, too. 00:14:10.149 --> 00:14:12.429 The guide mentioned it could add an extra $30 00:14:12.429 --> 00:14:15.409 a month to your bill. And that's why the cost 00:14:15.409 --> 00:14:17.850 architecture is so vital to monitor here. You 00:14:17.850 --> 00:14:19.889 have to look at the total package. Definitely. 00:14:20.460 --> 00:14:22.519 Transistor took a completely different approach. 00:14:23.019 --> 00:14:26.740 They built in -house AI transcription as an incredibly 00:14:26.740 --> 00:14:29.240 cheap add -on. How cheap are we talking? Just 00:14:29.240 --> 00:14:32.019 one dollar per hour of audio. Or they do a five 00:14:32.019 --> 00:14:34.100 -hour bundle for five dollars a month. Wow, that 00:14:34.100 --> 00:14:37.620 is dirt cheap compared to 30 bucks. It is. Podbean 00:14:37.620 --> 00:14:40.799 also offers its own Podbean AI for noise reduction 00:14:40.799 --> 00:14:42.840 and transcripts as an add -on. Which really means 00:14:42.840 --> 00:14:44.879 you have to map out your entire workflow before 00:14:44.879 --> 00:14:46.899 you buy anything. You absolutely do. Because 00:14:46.899 --> 00:14:49.100 think about it, if you're paying 12 bucks a month, 00:14:49.340 --> 00:14:52.620 for basic hosting on Buzzsprout. Right. But then 00:14:52.620 --> 00:14:54.840 you're paying an extra 30 for their AI tools 00:14:54.840 --> 00:14:57.240 to do your show notes and transcripts, you're 00:14:57.240 --> 00:15:01.080 suddenly at $42 a month. Exactly. At that point, 00:15:01.279 --> 00:15:05.039 the $38 for Alitu's all -in -one meal kit actually 00:15:05.039 --> 00:15:07.299 makes more financial sense and it sinks you time. 00:15:07.539 --> 00:15:10.799 It requires a really rigorous audit of your time 00:15:10.799 --> 00:15:13.879 versus your money. Consolidating your transcription, 00:15:14.460 --> 00:15:16.740 your audio leveling, and your hosting into one 00:15:16.740 --> 00:15:19.440 platform might actually reduce your overhead 00:15:19.440 --> 00:15:21.860 even if the sticker price seems high at first. 00:15:22.399 --> 00:15:24.759 I completely see the appeal. If your experience 00:15:24.759 --> 00:15:27.340 level is low and your desire to edit is zero, 00:15:27.620 --> 00:15:30.100 these all -in -one streamliners are just a godsend. 00:15:30.240 --> 00:15:32.279 They're perfect for that specific demographic. 00:15:32.919 --> 00:15:36.340 I see a massive financial wall approaching. Oh, 00:15:36.340 --> 00:15:38.639 the multi -show wall. Yes. Let's say you use 00:15:38.639 --> 00:15:41.639 Alitu. You're happily paying your $38 a month. 00:15:41.820 --> 00:15:44.200 You catch the podcasting bug. Happens all the 00:15:44.200 --> 00:15:46.580 time. You decide, hey, I want to launch a second 00:15:46.580 --> 00:15:49.200 show, maybe a five minute daily news briefing. 00:15:49.759 --> 00:15:52.539 What happens then? Do you have to pay another 00:15:52.539 --> 00:15:55.200 $38 every single month for that second show? 00:15:55.500 --> 00:15:57.960 In almost all cases with these per show pricing 00:15:57.960 --> 00:16:02.159 models. Yes. Yes. Your costs multiply directly 00:16:02.159 --> 00:16:04.879 in tandem with your creative output. That is 00:16:04.879 --> 00:16:07.559 brutal. It is. And that's exactly where I think 00:16:07.559 --> 00:16:10.500 creators get frustrated and start looking to 00:16:10.500 --> 00:16:13.019 completely rethink their architecture. Those 00:16:13.019 --> 00:16:15.980 per show fees act as a penalty for experimentation. 00:16:16.139 --> 00:16:18.059 They really do discourage you from trying new 00:16:18.059 --> 00:16:20.120 things. Right. If you want to build a network 00:16:20.120 --> 00:16:22.039 of three or four shows, you need a totally different 00:16:22.039 --> 00:16:24.559 solution. So let's look at platforms built for 00:16:24.559 --> 00:16:27.799 scaling up. When you reach this stage, you are 00:16:27.799 --> 00:16:29.700 no longer just thinking about a single audio 00:16:29.700 --> 00:16:32.399 file. You are thinking about brand architecture, 00:16:32.860 --> 00:16:35.899 scale, and cross promotion. Transistor is a name 00:16:35.899 --> 00:16:38.559 that comes up constantly in this tier. They dominate 00:16:38.559 --> 00:16:41.000 this specific conversation. Their starter plan 00:16:41.000 --> 00:16:44.490 is $19 a month. And the absolute standout feature 00:16:44.490 --> 00:16:47.070 that our sources hammer home over and over again 00:16:47.070 --> 00:16:49.830 is that Transistor gives you unlimited podcasts 00:16:49.830 --> 00:16:52.870 under one single account. Which is huge. You 00:16:52.870 --> 00:16:56.029 get 20 ,000 monthly downloads across all your 00:16:56.029 --> 00:16:59.370 shows combined without paying a dime extra. From 00:16:59.370 --> 00:17:02.190 an economic standpoint, this is a massive differentiator. 00:17:02.269 --> 00:17:04.670 I can imagine. If you look at the G2 user reviews 00:17:04.670 --> 00:17:07.549 and the migration patterns, this unlimited shows 00:17:07.549 --> 00:17:11.190 feature is explicitly cited as the primary reason 00:17:11.190 --> 00:17:14.190 users leave platforms like Buzzsprout or Libsyn. 00:17:14.359 --> 00:17:17.259 That makes total sense. Think about a marketing 00:17:17.259 --> 00:17:20.019 agency producing podcasts for three different 00:17:20.019 --> 00:17:22.900 corporate clients. Managing three separate billing 00:17:22.900 --> 00:17:26.700 accounts at $20 each is $60 a month. Transistor 00:17:26.700 --> 00:17:29.500 consolidates that to $19. That's a no -brainer 00:17:29.500 --> 00:17:31.839 for agencies. But wait, how do they afford that? 00:17:31.940 --> 00:17:34.799 If server space costs money, how can Transistor 00:17:34.799 --> 00:17:37.480 host five of my podcasts for the same price that 00:17:37.480 --> 00:17:40.059 Buzzsprat charges to host one? It's an actuarial 00:17:40.059 --> 00:17:42.670 calculation. It's very similar to how a buffet 00:17:42.670 --> 00:17:44.970 restaurant operates. Okay, I love a buffet analogy. 00:17:45.230 --> 00:17:47.390 Go on. Transistor knows that the vast majority 00:17:47.390 --> 00:17:50.710 of podcasts fade out or they maintain very small 00:17:50.710 --> 00:17:53.369 audiences. Sadly true. So they cap your total 00:17:53.369 --> 00:17:56.680 monthly downloads at 20 ,000. It doesn't matter 00:17:56.680 --> 00:17:58.960 if you have one show getting 20 ,000 downloads 00:17:58.960 --> 00:18:02.900 or 10 shows getting 2 ,000 downloads each. The 00:18:02.900 --> 00:18:05.420 bandwidth cost to Transistor is exactly the same 00:18:05.420 --> 00:18:07.619 either way. They are selling you an allowance 00:18:07.619 --> 00:18:09.980 of bandwidth and letting you slice it up across 00:18:09.980 --> 00:18:13.160 as many RSS feeds as you want. That is brilliant. 00:18:13.440 --> 00:18:16.269 And so freeing for the creator. It really encourages 00:18:16.269 --> 00:18:18.349 you to play around. You could start a highly 00:18:18.349 --> 00:18:22.450 niche, weird fiction podcast just for fun. And 00:18:22.450 --> 00:18:24.509 it costs you absolutely nothing extra to host 00:18:24.509 --> 00:18:26.410 it right alongside your professional business 00:18:26.410 --> 00:18:29.710 show. Exactly. Now, Captivate is another platform 00:18:29.710 --> 00:18:31.950 playing heavily in this multi -show space. Right. 00:18:31.970 --> 00:18:34.349 I saw them. They charge $17 a month, which is 00:18:34.349 --> 00:18:36.390 slightly cheaper. And they also offer unlimited 00:18:36.390 --> 00:18:39.789 shows. But they seem to focus heavily on growth 00:18:39.789 --> 00:18:42.349 and marketing tools. Captivate positions itself 00:18:42.349 --> 00:18:44.970 very strongly for professional podcasts. who 00:18:44.970 --> 00:18:48.109 view their content as a business ecosystem. What 00:18:48.109 --> 00:18:50.589 kind of tools do they offer? They include things 00:18:50.589 --> 00:18:52.789 designed specifically to help you pitch yourself. 00:18:53.230 --> 00:18:56.029 For instance, they have trackable links for sponsorships. 00:18:56.109 --> 00:18:58.349 Oh, that's handy. They have a one -click media 00:18:58.349 --> 00:19:00.930 kit generation tool that automatically pulls 00:19:00.930 --> 00:19:03.470 your latest listener demographics into a nice 00:19:03.470 --> 00:19:06.470 PDF. And they have a dynamic show notes builder. 00:19:06.970 --> 00:19:09.049 Let's talk about building that business ecosystem, 00:19:09.089 --> 00:19:12.279 actually. Because an audio feed floating in the 00:19:12.279 --> 00:19:15.339 void of Apple podcasts is only one part of the 00:19:15.339 --> 00:19:17.400 puzzle. It really is. If you're building a brand, 00:19:17.619 --> 00:19:20.619 you need a website. And not just a single landing 00:19:20.619 --> 00:19:23.539 page with a play button, but a real searchable 00:19:23.539 --> 00:19:27.220 website for SEO, for capturing email newsletters, 00:19:27.519 --> 00:19:30.019 for selling merch. So how do these platforms 00:19:30.019 --> 00:19:33.619 handle the website building aspect? They handle 00:19:33.619 --> 00:19:36.480 it with varying degrees of complexity, catering 00:19:36.480 --> 00:19:38.720 to different technical comfort levels. Walk me 00:19:38.720 --> 00:19:40.740 through it. Transistor takes a very automated 00:19:40.740 --> 00:19:43.460 approach. They generate a built -in website for 00:19:43.460 --> 00:19:46.059 your show based on a few design themes. OK, pre 00:19:46.059 --> 00:19:48.390 -standard. But. What's particularly unique is 00:19:48.390 --> 00:19:50.269 that if you use their unlimited show feature, 00:19:50.690 --> 00:19:53.170 they will also auto -generate a network website. 00:19:53.250 --> 00:19:55.990 Oh, really? Yeah, it aggregates all of your different 00:19:55.990 --> 00:19:59.009 podcasts into one central hub automatically. 00:19:59.289 --> 00:20:01.890 That's super cool. Podbean and Buzzsprout offer 00:20:01.890 --> 00:20:04.609 basic customizable sites too, right? They do, 00:20:04.650 --> 00:20:06.890 yeah. But what if you're a total control freak? 00:20:07.049 --> 00:20:09.089 What if you want ultimate control over your branding 00:20:09.089 --> 00:20:12.190 and you already run a heavy -duty WordPress site? 00:20:12.349 --> 00:20:14.569 Then you look toward platforms that integrate 00:20:14.569 --> 00:20:17.170 deeply with existing content management systems. 00:20:17.869 --> 00:20:20.470 Our sources highlight Castos and Blueberry for 00:20:20.470 --> 00:20:22.849 this exact use case. Right, I've heard of them. 00:20:23.049 --> 00:20:25.650 Castos utilizes a plugin called Seriously Symbol 00:20:25.650 --> 00:20:29.150 Podcasting, while Blueberry uses one called PowerPress. 00:20:29.849 --> 00:20:31.950 I've heard of these plugins, but I'm a bit hazy 00:20:31.950 --> 00:20:34.589 on the mechanics. How does a WordPress plugin 00:20:34.589 --> 00:20:37.809 actually interface with a podcast host? It's 00:20:37.809 --> 00:20:39.950 incredibly powerful because it centralizes your 00:20:39.950 --> 00:20:42.579 entire workflow. Okay. Normally, you'd log into 00:20:42.579 --> 00:20:45.220 your podcast host's dashboard. You'd upload your 00:20:45.220 --> 00:20:48.059 audio, write your show notes, and publish. Right, 00:20:48.200 --> 00:20:50.680 step one. Then step two, you'd separate log into 00:20:50.680 --> 00:20:53.759 your website, create a new blog post, copy the 00:20:53.759 --> 00:20:56.319 embed code from your host, paste it into the 00:20:56.319 --> 00:20:58.940 blog, and hit publish again. Which is just redundant 00:20:58.940 --> 00:21:02.339 work. Exactly, it's annoying. These plugins eliminate 00:21:02.339 --> 00:21:05.000 the podcast host's dashboard entirely. Wait, 00:21:05.019 --> 00:21:07.859 really? You never log in to Castos? You log directly 00:21:07.859 --> 00:21:10.700 into your own WordPress website. You create a 00:21:10.700 --> 00:21:13.359 new blog post. The plugin adds a little module 00:21:13.359 --> 00:21:15.440 at the bottom of the post where you attach your 00:21:15.440 --> 00:21:18.200 mp3 file. Oh, that's seamless. When you hit publish 00:21:18.200 --> 00:21:21.099 on the blog post, the plugin secretly sends the 00:21:21.099 --> 00:21:23.799 audio file to Castos or Blueberry's servers for 00:21:23.799 --> 00:21:28.200 storage, updates your global RSS feed, and automatically 00:21:28.200 --> 00:21:31.380 displays a sleek media player right there on 00:21:31.380 --> 00:21:33.720 your blog post. So you're publishing your podcast 00:21:33.720 --> 00:21:35.819 from the exact same interface where you publish 00:21:35.819 --> 00:21:38.480 your written articles. Yes. You own the domain, 00:21:38.819 --> 00:21:41.519 you capture the SEO value directly, and you own 00:21:41.519 --> 00:21:43.839 all the traffic. I also saw a platform mentioned 00:21:43.839 --> 00:21:46.240 called Podcastics. Oh yeah. They offer a white 00:21:46.240 --> 00:21:48.599 label site that includes reviews, ratings, polls, 00:21:48.740 --> 00:21:50.980 and heat maps. Heat maps are incredible. Heat 00:21:50.980 --> 00:21:53.420 maps, meaning you can see exactly where people's 00:21:53.420 --> 00:21:55.579 cursors are hovering and clicking on your podcast 00:21:55.579 --> 00:21:58.829 webpage. That level of behavioral data highlights 00:21:58.829 --> 00:22:02.390 a critical realization for creators scaling up. 00:22:02.809 --> 00:22:05.390 Owning your platform via a dedicated website 00:22:05.390 --> 00:22:09.069 is crucial for long -term brand building. You 00:22:09.069 --> 00:22:12.029 really cannot rely solely on the interface of 00:22:12.029 --> 00:22:14.750 Spotify or Apple to convey your brand identity 00:22:14.750 --> 00:22:17.210 or capture your audience. You just can't. They 00:22:17.210 --> 00:22:19.500 control the ecosystem there, not you. I love 00:22:19.500 --> 00:22:21.319 this because we're talking about building your 00:22:21.319 --> 00:22:24.059 own media empire complete with multiple shows, 00:22:24.400 --> 00:22:27.539 network websites, and custom analytics for roughly 00:22:27.539 --> 00:22:30.400 20 bucks a month. It's an insane amount of leverage 00:22:30.400 --> 00:22:32.220 compared to what it would cost to start a radio 00:22:32.220 --> 00:22:35.039 station 20 years ago. Oh, totally. But to truly 00:22:35.039 --> 00:22:37.460 be a media empire, you actually have to make 00:22:37.460 --> 00:22:39.759 money. You can't just pay 20 bucks a month out 00:22:39.759 --> 00:22:42.380 of pocket forever. And that transition from a 00:22:42.380 --> 00:22:44.859 passionate hobbyist to a revenue generating entity 00:22:44.859 --> 00:22:47.539 is exactly where the technical requirements of 00:22:47.539 --> 00:22:50.059 your hosting platform become incredibly demanding. 00:22:50.339 --> 00:22:52.960 Which means we need to master advertising. Yes. 00:22:53.599 --> 00:22:55.579 This is where things get really complicated. 00:22:55.740 --> 00:22:58.099 Let's dive into the monetization maze. We really 00:22:58.099 --> 00:23:01.000 need to focus specifically on dynamic ad insertion, 00:23:01.160 --> 00:23:05.579 or DAI. DAI is the buzzword of the decade. It 00:23:05.579 --> 00:23:07.660 really is. We also need to address what we're 00:23:07.660 --> 00:23:09.400 calling the impression dilemma, which came up 00:23:09.400 --> 00:23:11.900 in that fascinating Reddit thread. Right. First, 00:23:12.099 --> 00:23:14.900 though, for anyone who isn't a seasoned audio 00:23:14.900 --> 00:23:19.200 engineer, What actually is dynamic ad insertion 00:23:19.200 --> 00:23:22.279 mechanically? It is arguably the most significant 00:23:22.279 --> 00:23:25.119 technological advancement in podcast monetization 00:23:25.119 --> 00:23:28.500 in the last 10 years. To understand it, you have 00:23:28.500 --> 00:23:32.420 to look at how ads used to be done. The baked 00:23:32.420 --> 00:23:34.960 in ad. Right. Back in the day, you recorded yourself 00:23:34.960 --> 00:23:37.880 reading a promo for like A mattress company. 00:23:38.160 --> 00:23:40.359 A classic podcast sponsor. Exactly. You took 00:23:40.359 --> 00:23:42.599 that audio clip, you permanently mixed it into 00:23:42.599 --> 00:23:45.700 the middle of episode 12, exported the MP3, and 00:23:45.700 --> 00:23:48.440 it lived there forever. Forever. Five years later, 00:23:48.519 --> 00:23:50.400 someone discovers your show, they binge listen 00:23:50.400 --> 00:23:52.980 to episode 12, and they hear a promo code for 00:23:52.980 --> 00:23:55.059 a mattress discount that literally expired in 00:23:55.059 --> 00:23:57.539 2021. Which is a huge problem. Baked -in ads 00:23:57.539 --> 00:23:59.799 are permanent and inflexible. You are leaving 00:23:59.799 --> 00:24:01.480 money on the table because your back catalog 00:24:01.480 --> 00:24:04.220 is essentially dead inventory. Right. Dynamic 00:24:04.220 --> 00:24:06.839 ad insertion changes this entirely. I like to 00:24:06.839 --> 00:24:08.819 think of it like a digital printing press. Okay, 00:24:08.859 --> 00:24:11.859 walk me through the printing press analogy. Imagine 00:24:11.859 --> 00:24:16.019 a newspaper publisher. With a baked -in ad, the 00:24:16.019 --> 00:24:18.119 publisher prints 10 ,000 copies of the paper 00:24:18.119 --> 00:24:21.500 on Monday with a car ad on page 2 and puts them 00:24:21.500 --> 00:24:24.279 in a warehouse. Anyone who picks up that paper, 00:24:24.359 --> 00:24:26.380 whether it's Monday or three years from now, 00:24:26.579 --> 00:24:29.539 sees that exact same car ad. Makes perfect sense. 00:24:29.819 --> 00:24:32.170 Dynamic ad insertion is a printing press. that 00:24:32.170 --> 00:24:35.289 only prints the newspaper the exact microsecond. 00:24:35.730 --> 00:24:38.250 A reader picks it up off their driveway. With 00:24:38.250 --> 00:24:41.390 DAI, your main episode audio and your ad audio 00:24:41.390 --> 00:24:43.630 are stored as completely separate files on the 00:24:43.630 --> 00:24:45.869 host's server. Okay, so they aren't mixed together 00:24:45.869 --> 00:24:49.349 yet. No. You have episode 12 and you have a 30 00:24:49.349 --> 00:24:52.329 -second audio clip for a new sponsor. When a 00:24:52.329 --> 00:24:54.710 listener on their phone taps download on episode 00:24:54.710 --> 00:24:57.690 12, the server acts as the printing press. Right 00:24:57.690 --> 00:24:59.910 then and there. Right then. In a fraction of 00:24:59.910 --> 00:25:02.410 a second, it stitches the 30 -second ad audio 00:25:02.410 --> 00:25:05.089 into the main episode file, maybe as a pre -roll 00:25:05.089 --> 00:25:07.890 before the show starts, or a mid -roll in a designated 00:25:07.890 --> 00:25:10.349 empty slot. And then it delivers that newly assembled 00:25:10.349 --> 00:25:12.769 file. Exactly. It delivers that newly assembled, 00:25:12.769 --> 00:25:15.930 customized MP3 to the listener's phone. That 00:25:15.930 --> 00:25:18.349 is incredible. So the file is literally being 00:25:18.349 --> 00:25:22.029 assembled in real time, on demand, every single 00:25:22.029 --> 00:25:24.650 time someone hits play. Yes. And this allows 00:25:24.650 --> 00:25:27.210 you to run a two -week ad campaign for a sponsor 00:25:27.210 --> 00:25:30.430 and insert that ad into your entire back catalog 00:25:30.430 --> 00:25:32.690 of hundreds of episodes simultaneously. Which 00:25:32.690 --> 00:25:35.309 means someone listening to episode one from five 00:25:35.309 --> 00:25:37.869 years ago gets today's mattress ad. Precisely. 00:25:38.109 --> 00:25:40.069 And when the two weeks are up, you simply turn 00:25:40.069 --> 00:25:42.569 the campaign off in your dashboard. The server 00:25:42.569 --> 00:25:45.170 stops stitching that specific ad into the downloads. 00:25:45.390 --> 00:25:47.750 So your archives revert back to being ad -free? 00:25:47.930 --> 00:25:50.750 Ad -free. Or you just swap in a brand new sponsor. 00:25:50.890 --> 00:25:53.470 Your archives become this timeless, constantly 00:25:53.470 --> 00:25:56.430 monetizable asset. It turns a dusty library into 00:25:56.430 --> 00:25:58.950 a constant revenue generator. It's brilliant. 00:25:59.289 --> 00:26:01.589 But as brilliant as that sounds, our research 00:26:01.589 --> 00:26:04.730 shows that the reality of executing this is incredibly 00:26:04.730 --> 00:26:06.910 messy. Oh, it's a nightmare for independent creators. 00:26:07.130 --> 00:26:08.950 Let's look at this Reddit thread from the Fur 00:26:08.950 --> 00:26:12.410 podcasting community. We have a user named Graham 00:26:12.410 --> 00:26:15.329 Cooley. He posted looking for a very specific 00:26:15.329 --> 00:26:18.809 type of DAI capability. His request is a perfect 00:26:18.809 --> 00:26:22.109 case study. It exposes a massive fault line in 00:26:22.109 --> 00:26:24.809 the hosting market between what advertisers want 00:26:24.809 --> 00:26:27.349 and what prosumer platforms can actually deliver. 00:26:27.950 --> 00:26:30.170 What was he trying to do? He had sponsors who 00:26:30.170 --> 00:26:31.990 wanted to buy a specific number of impressions. 00:26:32.710 --> 00:26:34.670 Let's say they only wanted to pay for exactly 00:26:34.670 --> 00:26:37.589 5 ,000 listens. Okay, pretty standard digital 00:26:37.589 --> 00:26:40.069 ad buy. Right. So he wanted to upload an ad, 00:26:40.390 --> 00:26:42.569 have it run dynamically across his back catalog, 00:26:43.089 --> 00:26:46.309 and automatically stop stitching the ad the precise 00:26:46.309 --> 00:26:49.230 moment it hit 5 ,000 downloads. Which sounds 00:26:49.230 --> 00:26:51.809 perfectly reasonable. That is how digital advertising 00:26:51.809 --> 00:26:54.069 works everywhere else on the internet. Everywhere 00:26:54.069 --> 00:26:56.509 else, yeah. You buy 5 ,000 impressions on a website, 00:26:56.930 --> 00:26:59.630 the banner ad loads 5 ,000 times, and then it 00:26:59.630 --> 00:27:02.450 automatically turns off. But in the podcasting 00:27:02.450 --> 00:27:05.069 world, Graham found out this is a massive headache. 00:27:05.450 --> 00:27:07.750 It reveals the critical difference between date 00:27:07.750 --> 00:27:10.269 -based scheduling and impression -based scheduling. 00:27:10.769 --> 00:27:14.019 Let's break that down. A user named Jordan Pods, 00:27:14.140 --> 00:27:16.339 who disclosed they actually work as a podcast 00:27:16.339 --> 00:27:18.799 producer at Buzzsprout, replied to Graham. What 00:27:18.799 --> 00:27:21.240 did they suggest? They suggested platforms like 00:27:21.240 --> 00:27:24.359 Buzzsprout, Transistor, and Captivate. But Graham 00:27:24.359 --> 00:27:27.200 replied saying he had actually called Buzzsprout 00:27:27.200 --> 00:27:29.819 tech support. Oh boy. And Buzzsprout told him 00:27:29.819 --> 00:27:32.740 outright, there is not a way to have the content 00:27:32.740 --> 00:27:35.099 automatically removed once the downloads meet 00:27:35.099 --> 00:27:37.910 a certain number. That is brutal. He would have 00:27:37.910 --> 00:27:41.309 to manually monitor his own stats, log into the 00:27:41.309 --> 00:27:44.069 dashboard, and manually turn the ad off when 00:27:44.069 --> 00:27:46.369 it hit the 5 ,000 mark. Which is practically 00:27:46.369 --> 00:27:49.049 impossible to manage effectively. Yeah. Especially 00:27:49.049 --> 00:27:51.630 if you have multiple campaigns running simultaneously 00:27:51.630 --> 00:27:54.009 across different time zones. You'd have to, like, 00:27:54.150 --> 00:27:56.170 wake up at 3 a .m. to turn an ad off so you don't 00:27:56.170 --> 00:27:58.769 over -deliver. Exactly. This is the reality of 00:27:58.769 --> 00:28:01.329 date -based DAI, which is the industry standard 00:28:01.329 --> 00:28:04.680 for almost all prosumer hosts right now. So, 00:28:04.880 --> 00:28:06.960 on Transistor's professional plan, which costs 00:28:06.960 --> 00:28:10.599 $49 a month, or on Captivate, you schedule campaigns 00:28:10.599 --> 00:28:13.839 by the calendar. Yes. You say, run this ad from 00:28:13.839 --> 00:28:17.299 March 1st to March 15th. You cannot set a hard 00:28:17.299 --> 00:28:19.720 impression cap. I just don't understand why. 00:28:19.859 --> 00:28:22.539 Why can I set an exact impression cap on a tiny, 00:28:22.920 --> 00:28:26.200 custom -built blog, but not on a dedicated podcast 00:28:26.200 --> 00:28:28.480 hosting platform? It comes back to the fundamental 00:28:28.480 --> 00:28:30.839 architecture of the RSS feed that we discussed 00:28:30.839 --> 00:28:33.839 earlier. Okay, remind me. Remember. Podcasting 00:28:33.839 --> 00:28:37.099 is not a closed centralized ecosystem like YouTube 00:28:37.099 --> 00:28:40.230 or Instagram. When you publish an episode, you 00:28:40.230 --> 00:28:42.670 are just pushing a text file out into the wild. 00:28:43.390 --> 00:28:45.309 Right. Listeners are pulling your audio through 00:28:45.309 --> 00:28:48.069 dozens of fragmented, totally independent apps. 00:28:48.450 --> 00:28:51.930 Apple Podcasts, Spotify, Overcast, Pocket Casts, 00:28:52.029 --> 00:28:54.069 Castbox. Right, the host doesn't control the 00:28:54.069 --> 00:28:56.650 app the listener is using. Exactly. To count 00:28:56.650 --> 00:28:59.529 real -time impressions across all those disparate 00:28:59.529 --> 00:29:02.910 apps, consolidate that data instantly, and tell 00:29:02.910 --> 00:29:05.609 the server to stop stitching the audio the microsecond 00:29:05.609 --> 00:29:09.309 it hits exactly 5 ,000 downloads. requires immense 00:29:09.309 --> 00:29:12.589 enterprise -grade server power. It's a huge coordination 00:29:12.589 --> 00:29:14.950 problem. Yes, it requires highly specialized 00:29:14.950 --> 00:29:17.670 ad tech infrastructure. A blog can count impressions 00:29:17.670 --> 00:29:20.109 easily because the blog server controls the entire 00:29:20.109 --> 00:29:21.950 web page. Right, it sees everything happening 00:29:21.950 --> 00:29:25.750 on the page. But a podcast host only sees a ping 00:29:25.750 --> 00:29:29.369 from Apple servers or a ping from a random Android 00:29:29.369 --> 00:29:32.589 phone in Germany at totally unpredictable intervals. 00:29:33.099 --> 00:29:36.619 Tracking that with perfectly synchronized real 00:29:36.619 --> 00:29:40.480 -time precision is computationally very expensive. 00:29:41.140 --> 00:29:43.859 OK, so who actually has that computational power? 00:29:44.099 --> 00:29:47.180 Good question. Another Reddit user, Jake Berger, 00:29:47.680 --> 00:29:50.200 chimed into the thread and pointed Gram toward 00:29:50.200 --> 00:29:53.220 a platform called Spreaker. Ah, Spreaker. Spreaker 00:29:53.220 --> 00:29:55.980 uses technology powered by Triton Digital's audio 00:29:55.980 --> 00:29:59.240 ad server. And they actually can do hard -capped, 00:29:59.640 --> 00:30:01.980 impression -based campaigns. They can. They possess 00:30:01.980 --> 00:30:04.380 that enterprise -level architecture. But there 00:30:04.380 --> 00:30:06.660 is a massive financial barrier to entry. Oh, 00:30:06.859 --> 00:30:09.240 yeah. To access that specific campaign tool on 00:30:09.240 --> 00:30:11.299 Spreaker, you have to be on their publisher plan. 00:30:11.460 --> 00:30:13.720 And here is the punchline, folks. Right. What 00:30:13.720 --> 00:30:17.049 does that publisher plan cost? $250 a month. 00:30:17.210 --> 00:30:19.410 It's staggering. Graham literally replied to 00:30:19.410 --> 00:30:22.230 the thread saying that paying $250 a month just 00:30:22.230 --> 00:30:24.549 to gain access to a tool to limit his ads is 00:30:24.549 --> 00:30:26.549 hard to justify. I don't blame him. The other 00:30:26.549 --> 00:30:28.549 option our sources mentioned for this is Megaphone, 00:30:28.670 --> 00:30:31.089 which is owned by Spotify. Right, Megaphone is 00:30:31.089 --> 00:30:34.029 the big player here. Megaphone definitely does 00:30:34.029 --> 00:30:37.960 impression -based DAI. And incredibly advanced 00:30:37.960 --> 00:30:40.259 targeting. Like you can target listeners based 00:30:40.259 --> 00:30:42.880 on Nielsen demographic data. Which is incredible 00:30:42.880 --> 00:30:45.700 for advertisers. But they are strictly an enterprise 00:30:45.700 --> 00:30:47.799 platform. They require you to prove you have 00:30:47.799 --> 00:30:50.480 at least 20 ,000 downloads per episode just to 00:30:50.480 --> 00:30:52.980 get in the door. This raises an important question 00:30:52.980 --> 00:30:55.119 about the current state of the industry. What's 00:30:55.119 --> 00:30:58.359 that? The most sophisticated automated monetization 00:30:58.359 --> 00:31:01.940 tools are heavily gate kept. You either pay exorbitant 00:31:01.940 --> 00:31:06.369 monthly fees or you need a massive top 1 % audience 00:31:06.369 --> 00:31:08.789 size. Let me stop you there, because I'm putting 00:31:08.789 --> 00:31:10.970 myself in the shoes of the independent creator 00:31:10.970 --> 00:31:13.730 listening to this right now. OK. Does this mean 00:31:13.730 --> 00:31:16.390 they are just completely locked out of professional 00:31:16.390 --> 00:31:20.009 advertising unless they have $250 a month to 00:31:20.009 --> 00:31:23.029 burn or 20 ,000 downloads an episode? It feels 00:31:23.029 --> 00:31:24.970 that way, doesn't it? Are independent creators 00:31:24.970 --> 00:31:27.670 just stuck manually refreshing their Buzzsprout 00:31:27.670 --> 00:31:30.720 dashboards every three hours? I refuse to believe 00:31:30.720 --> 00:31:33.019 that's the only way to do business. It's not. 00:31:33.220 --> 00:31:35.779 It just forces a slight pivot in how you negotiate 00:31:35.779 --> 00:31:37.920 with sponsors. Okay, tell me how to pivot. For 00:31:37.920 --> 00:31:40.640 the vast majority of independent creators, date 00:31:40.640 --> 00:31:43.900 -based DAI, the kind offered by Transistor for 00:31:43.900 --> 00:31:47.900 $49 or Captivate for roughly $20, is more than 00:31:47.900 --> 00:31:50.940 sufficient. But how do I handle the sponsor wanting 00:31:50.940 --> 00:31:54.019 5 ,000 impressions? You simply have to educate 00:31:54.019 --> 00:31:56.980 your sponsor. Instead of selling an exact impression 00:31:56.980 --> 00:31:59.680 count, you negotiate based on your average monthly 00:31:59.680 --> 00:32:02.240 downloads. Oh, I see. You approach the sponsor 00:32:02.240 --> 00:32:05.940 and say, my back catalog reliably gets 10 ,000 00:32:05.940 --> 00:32:08.519 downloads a month. I will sell you a two -week 00:32:08.519 --> 00:32:11.480 calendar slot, which should hit roughly 5 ,000 00:32:11.480 --> 00:32:14.220 impressions. So you sell the time slot, not the 00:32:14.220 --> 00:32:17.339 exact listener count. Precisely. You sell the 00:32:17.339 --> 00:32:20.000 calendar real estate. It's an estimation. but 00:32:20.000 --> 00:32:23.140 is a widely accepted standard practice for independent 00:32:23.140 --> 00:32:25.480 and mid level shows. So the sponsor understands 00:32:25.480 --> 00:32:28.279 there's a margin of error. Exactly. However, 00:32:28.579 --> 00:32:30.619 if you truly have corporate sponsors demanding 00:32:30.619 --> 00:32:33.559 exact third party audited impression caps to 00:32:33.559 --> 00:32:36.359 the single digit and they are paying you a premium 00:32:36.359 --> 00:32:40.289 CPM rate to justify it, then suddenly. That $250 00:32:40.289 --> 00:32:43.029 a month for Spreaker isn't a burden. Exactly. 00:32:43.369 --> 00:32:46.789 It becomes a necessary and justifiable cost of 00:32:46.789 --> 00:32:49.049 doing high level advertising business. That makes 00:32:49.049 --> 00:32:51.970 total sense. You have to match your platform's 00:32:51.970 --> 00:32:54.630 capability to your sponsor's specific demands. 00:32:54.849 --> 00:32:56.890 You don't need a semi truck to deliver a pizza. 00:32:57.170 --> 00:32:59.690 Right. And you don't need Spreaker to run an 00:32:59.690 --> 00:33:02.950 ad for a local coffee shop. But if you are chasing 00:33:02.950 --> 00:33:05.509 those big corporate sponsors, you can't just 00:33:05.509 --> 00:33:07.730 hand them a screenshot of your Apple Podcasts 00:33:07.730 --> 00:33:09.769 analytics page. No, they will laugh you out of 00:33:09.769 --> 00:33:11.789 the room. You're going to need enterprise -level 00:33:11.789 --> 00:33:14.430 data to prove your numbers are real. Which leads 00:33:14.430 --> 00:33:16.849 us to the final frontier of choosing a host. 00:33:17.789 --> 00:33:20.150 Proving your worth through advanced analytics 00:33:20.150 --> 00:33:23.069 and agency tools. Because at the end of the day, 00:33:23.609 --> 00:33:26.460 the data is what you are actually selling. We 00:33:26.460 --> 00:33:29.079 hear this acronym thrown around constantly in 00:33:29.079 --> 00:33:31.799 podcasting almost like a badge of honor, IAB 00:33:31.799 --> 00:33:34.839 certification. It's everywhere. Buzzsprout proudly 00:33:34.839 --> 00:33:37.480 says they have it. Captivate has it. Libsyn has 00:33:37.480 --> 00:33:40.740 it. Acast has it. What is the Interactive Advertising 00:33:40.740 --> 00:33:43.599 Bureau and why does their specific certification 00:33:43.599 --> 00:33:47.079 matter so much to advertisers? The IAB sets the 00:33:47.079 --> 00:33:49.140 technical and ethical standards for the digital 00:33:49.140 --> 00:33:52.140 advertising industry globally. In podcasting, 00:33:52.500 --> 00:33:55.000 it is notoriously difficult to determine what 00:33:55.000 --> 00:33:58.140 actually constitutes a listen. Why is it difficult? 00:33:58.279 --> 00:33:59.960 Doesn't the server just count how many times 00:33:59.960 --> 00:34:02.779 the file was downloaded? It does, but a download 00:34:02.779 --> 00:34:05.599 does not necessarily equal a human ear. What 00:34:05.599 --> 00:34:08.380 do you mean? Well, what if a podcast app on someone's 00:34:08.380 --> 00:34:10.440 phone is set to automatically download every 00:34:10.440 --> 00:34:13.420 new episode over Wi -Fi, but the user hasn't 00:34:13.420 --> 00:34:15.599 actually opened the app in three months? Oh, 00:34:15.880 --> 00:34:17.719 the file was downloaded, but nobody heard the 00:34:17.719 --> 00:34:21.139 ad. Exactly. Or, what if a search engine bot 00:34:21.139 --> 00:34:24.469 scrapes the RSS feed to index it. The server 00:34:24.469 --> 00:34:27.530 registers a request for the audio file. Advertisers 00:34:27.530 --> 00:34:30.030 absolutely refuse to pay money for a bot downloading 00:34:30.030 --> 00:34:32.150 an MP3. Right. That's just throwing money into 00:34:32.150 --> 00:34:35.369 a furnace. So how does the IAB fix this? IAB 00:34:35.369 --> 00:34:38.250 certification means the hosting platform's proprietary 00:34:38.250 --> 00:34:40.949 analytics algorithm has been rigorously audited 00:34:40.949 --> 00:34:43.670 by an independent third party. OK. They verify 00:34:43.670 --> 00:34:45.929 that the host is actively filtering out known 00:34:45.929 --> 00:34:48.510 bot traffic, ignoring server requests from data 00:34:48.510 --> 00:34:50.989 centers, and filtering out duplicate downloads. 00:34:51.539 --> 00:34:53.719 Duplicate downloads, like if I listen twice. 00:34:53.900 --> 00:34:55.760 Or if you download the first half of an episode 00:34:55.760 --> 00:34:58.300 on Wi -Fi, pause it, and then stream the second 00:34:58.300 --> 00:35:00.960 half over cellular data an hour later. Oh, that 00:35:00.960 --> 00:35:03.500 makes sense. The IAB standard ensures that only 00:35:03.500 --> 00:35:06.440 counts as one single download, not two. It's 00:35:06.440 --> 00:35:09.139 the industry's gold standard for truth. When 00:35:09.139 --> 00:35:12.019 you hand an advertiser an IAB certified report, 00:35:12.440 --> 00:35:14.960 they trust that those numbers represent actual 00:35:14.960 --> 00:35:18.630 living human beings. OK, so. IAB certification 00:35:18.630 --> 00:35:21.650 is the absolute baseline for establishing trust. 00:35:21.730 --> 00:35:24.349 Air minimum. But what if you need to go much 00:35:24.349 --> 00:35:27.349 deeper than just how many humans listened? Deep 00:35:27.349 --> 00:35:29.150 analytics. Right. What if you were producing 00:35:29.150 --> 00:35:32.929 a podcast not to sell mattresses, but as a B2B 00:35:33.239 --> 00:35:35.400 business to business marketing tool for your 00:35:35.400 --> 00:35:37.280 software company. That's a whole different ballgame. 00:35:37.579 --> 00:35:40.019 Our sources highlight a platform called Cohost, 00:35:40.440 --> 00:35:43.199 which was created by the podcast agency Quill. 00:35:43.199 --> 00:35:46.280 It starts at thirty one dollars a month. What 00:35:46.280 --> 00:35:48.780 makes them so special for corporate shows? Cohost 00:35:48.780 --> 00:35:51.480 is explicitly built for brands and agencies who 00:35:51.480 --> 00:35:54.280 use podcasting as a lead generation tool. They 00:35:54.280 --> 00:35:56.599 offer a feature they call B2B analytics. How 00:35:56.599 --> 00:35:58.719 does that differ from standard analytics? Well, 00:35:58.920 --> 00:36:01.519 a standard IAB certified host might tell you 00:36:01.519 --> 00:36:03.960 that 500 people in Chicago listen to your show 00:36:03.960 --> 00:36:06.800 on an iPhone. Right. Co -host claims to be able 00:36:06.800 --> 00:36:08.760 to show you exactly which companies your listeners 00:36:08.760 --> 00:36:11.539 work at, their general job roles, their industry, 00:36:11.940 --> 00:36:14.099 and the average revenue of those companies. Hold 00:36:14.099 --> 00:36:16.659 on. How is that technically possible? How does 00:36:16.659 --> 00:36:19.260 an audio file know where I work? It's essentially 00:36:19.260 --> 00:36:22.239 an advanced form of IP mapping. IP mapping? Yeah. 00:36:22.360 --> 00:36:25.079 When a device downloads an episode, it leaves 00:36:25.079 --> 00:36:27.500 an Ikey address, like a digital footprint on 00:36:27.500 --> 00:36:30.360 the server. Co -host takes those IP addresses 00:36:30.360 --> 00:36:33.659 and cross -references them against massive third 00:36:33.659 --> 00:36:36.519 -party corporate databases. Oh, wow. So if someone 00:36:36.519 --> 00:36:38.639 is listening on their company's Wi -Fi network 00:36:38.639 --> 00:36:42.440 or through a corporate VPN, Co -host's system 00:36:42.440 --> 00:36:46.340 recognizes that IP block belongs to, say, a midsize 00:36:46.340 --> 00:36:48.989 logistics firm in Chicago. rather than just a 00:36:48.989 --> 00:36:51.130 residential internet provider. Whoa. So instead 00:36:51.130 --> 00:36:53.010 of pitching an advertiser by saying, my average 00:36:53.010 --> 00:36:55.250 listener is a 35 -year -old male. Right. Which 00:36:55.250 --> 00:36:57.590 is vague. You can go to your boss and say, last 00:36:57.590 --> 00:36:59.949 week, our episode was downloaded by a marketing 00:36:59.949 --> 00:37:02.710 director at a logistics firm that makes $50 million 00:37:02.710 --> 00:37:06.630 a year. Yes. For a B2B podcast where a single 00:37:06.630 --> 00:37:09.050 listener could eventually represent a $50 ,000 00:37:09.050 --> 00:37:12.289 enterprise software contract, that granular, 00:37:12.710 --> 00:37:15.510 company -level data is infinitely more valuable 00:37:15.510 --> 00:37:18.369 than raw download volume. You are measuring the 00:37:18.369 --> 00:37:20.670 financial quality of the audience, not just the 00:37:20.670 --> 00:37:24.199 quantity. Exactly. complete opposite end of the 00:37:24.199 --> 00:37:26.960 monetization spectrum. You have platforms like 00:37:26.960 --> 00:37:29.619 Acast and Red Circle. How are they different? 00:37:29.900 --> 00:37:32.719 They aren't about hyper -niche B2B targeting. 00:37:33.199 --> 00:37:35.579 They're built for massive distribution and plugging 00:37:35.579 --> 00:37:38.320 directly into programmatic advertising marketplaces. 00:37:38.519 --> 00:37:41.239 I hear programmatic a lot, but what does a programmatic 00:37:41.239 --> 00:37:43.699 ad transaction actually look like in practice? 00:37:44.039 --> 00:37:46.780 Programmatic advertising is where unsold ad inventory 00:37:46.780 --> 00:37:49.059 is automatically filled by an algorithmic ad 00:37:49.059 --> 00:37:51.690 network. It's very similar to how banner ads 00:37:51.690 --> 00:37:54.469 load on a news website. OK. It happens in milliseconds. 00:37:55.030 --> 00:37:57.349 Let's run a simulation. I'm ready. You host your 00:37:57.349 --> 00:37:59.590 show on Red Circle. You have a mid -roll ad slot 00:37:59.590 --> 00:38:02.690 empty in episode 50. A listener hits play. In 00:38:02.690 --> 00:38:04.650 the fraction of a second before the audio starts, 00:38:05.010 --> 00:38:07.329 Red Circle's server sends a signal to an automated 00:38:07.329 --> 00:38:10.510 ad exchange. It says, I have a listener in New 00:38:10.510 --> 00:38:13.030 York using an iPhone listening to a true crime 00:38:13.030 --> 00:38:16.500 podcast. Who wants to buy this ad slot? So it's 00:38:16.500 --> 00:38:19.400 an instantaneous auction? Exactly. Computers 00:38:19.400 --> 00:38:21.940 representing various advertisers place bids. 00:38:22.320 --> 00:38:24.340 A national insurance company's algorithm bids 00:38:24.340 --> 00:38:27.159 two cents. A local New York concert promoter 00:38:27.159 --> 00:38:29.860 bids four cents. And the promoter wins? The promoter 00:38:29.860 --> 00:38:32.960 wins the auction. Their pre -recorded 30 -second 00:38:32.960 --> 00:38:35.699 audio ad is instantly routed to Red Circle, stitched 00:38:35.699 --> 00:38:38.059 into the episode dynamically, and the listener 00:38:38.059 --> 00:38:40.429 hears the concert ad. All of this happens in 00:38:40.429 --> 00:38:42.269 the time it takes the listener's thumb to lift 00:38:42.269 --> 00:38:44.929 off the play button. Exactly. That is staggering 00:38:44.929 --> 00:38:47.449 technology. It really is. Red Circle has an ad 00:38:47.449 --> 00:38:49.710 platform that connects podcasters and advertisers 00:38:49.710 --> 00:38:52.789 directly to facilitate this. Acast has one of 00:38:52.789 --> 00:38:55.289 the largest podcast ad marketplaces globally. 00:38:55.449 --> 00:38:57.710 So if your goal is to generate revenue purely 00:38:57.710 --> 00:39:00.309 through raw audience scale, without manually 00:39:00.309 --> 00:39:02.690 calling up sponsors and negotiating deals yourself, 00:39:03.170 --> 00:39:05.349 these platforms provide the exact infrastructure 00:39:05.349 --> 00:39:08.079 to do that. Precisely. And we shouldn't forget 00:39:08.079 --> 00:39:10.340 Transistor in this analytics conversation, either. 00:39:10.719 --> 00:39:12.840 We talked about them for their unlimited multi 00:39:12.840 --> 00:39:15.679 -show hosting, but our sources constantly praise 00:39:15.679 --> 00:39:18.239 their analytics dashboards, too. They do. They 00:39:18.239 --> 00:39:21.039 have these episode burn -down charts that compare 00:39:21.039 --> 00:39:23.500 your latest episode's performance against historical 00:39:23.500 --> 00:39:26.079 data, and they integrate seamlessly with third 00:39:26.079 --> 00:39:28.519 -party tracking tools like Chartable. Plus, and 00:39:28.519 --> 00:39:31.159 this is a huge selling point in the G2 reviews, 00:39:31.639 --> 00:39:36.760 they have rock -solid 247 human customer support 00:39:36.760 --> 00:39:39.300 via live chat. Which brings us full circle to 00:39:39.300 --> 00:39:41.719 our very first point about the hidden cost of 00:39:41.719 --> 00:39:44.380 free platforms. Exactly. If a technical glitch 00:39:44.380 --> 00:39:47.619 is preventing your highly monetized revenue generating 00:39:47.619 --> 00:39:49.599 episode from publishing on a Tuesday morning, 00:39:49.900 --> 00:39:52.260 having a real human being available on live chat 00:39:52.260 --> 00:39:54.719 to fix it immediately is an invaluable feature. 00:39:54.840 --> 00:39:56.659 It's an insurance policy on your revenue stream. 00:39:56.820 --> 00:40:00.260 It really is. Okay. We have covered an incredible 00:40:00.260 --> 00:40:02.460 amount of ground today. Let's synthesize all 00:40:02.460 --> 00:40:04.800 this advice and give you, the listener, a final 00:40:04.800 --> 00:40:07.039 cheat sheet. Sounds good. You really have to 00:40:07.039 --> 00:40:10.570 match the tool to the job. If your podcast is 00:40:10.570 --> 00:40:13.010 a B2B marketing tool designed to generate high 00:40:13.010 --> 00:40:15.889 ticket leads, paying $31 a month for co -hosts 00:40:15.889 --> 00:40:18.590 to see exactly what companies are listening is 00:40:18.590 --> 00:40:21.349 vastly more valuable than using a free platform. 00:40:28.650 --> 00:40:31.329 But if you are monetizing your show via Patreon 00:40:31.329 --> 00:40:34.389 or direct listener support and you honestly don't 00:40:34.389 --> 00:40:36.650 care about corporate sponsors or programmatic 00:40:36.650 --> 00:40:39.469 auctions, then Transistor's private podcast feeds 00:40:39.469 --> 00:40:42.150 might be the perfect play. Right, which are included 00:40:42.150 --> 00:40:46.630 in their base $19 plan. You can generate an exclusive, 00:40:46.969 --> 00:40:49.889 password -protected, ad -free feed for your loyal 00:40:49.889 --> 00:40:52.929 fans effortlessly. It's entirely about identifying 00:40:52.929 --> 00:40:55.570 your primary revenue stream and choosing the 00:40:55.570 --> 00:40:57.630 platform architecture that seamlessly supports 00:40:57.630 --> 00:41:00.300 it. Let's round up this deep dive. If you are 00:41:00.300 --> 00:41:02.519 standing at the starting line and budget is your 00:41:02.519 --> 00:41:05.460 absolute only concern, Spotify for creators or 00:41:05.460 --> 00:41:08.320 a pod beans free tier are your best bets to get 00:41:08.320 --> 00:41:10.719 your voice out there. If you have absolutely 00:41:10.719 --> 00:41:13.139 no technical experience, you don't want to learn 00:41:13.139 --> 00:41:15.719 how to use audio editing software and you want 00:41:15.719 --> 00:41:18.760 a streamlined automated workflow. Look at Riverside 00:41:18.760 --> 00:41:22.079 for high end remote video or Alitu for an automated 00:41:22.079 --> 00:41:24.239 audio meal kit. And as your experience grows, 00:41:24.780 --> 00:41:26.960 if you want unlimited shows, network websites 00:41:26.960 --> 00:41:29.800 and solid date based din... an anacad insertion 00:41:29.800 --> 00:41:32.460 without breaking the bank, Transistor and Captivate 00:41:32.460 --> 00:41:34.920 are incredibly strong contenders that won't penalize 00:41:34.920 --> 00:41:37.179 you for experimenting. But if you are playing 00:41:37.179 --> 00:41:39.800 in the big leagues and you absolutely must have 00:41:39.800 --> 00:41:42.260 impression based dynamic ads to satisfy corporate 00:41:42.260 --> 00:41:45.039 sponsors who want exact listener counts, you 00:41:45.039 --> 00:41:47.380 have to be ready to pay enterprise prices. You 00:41:47.380 --> 00:41:49.659 really do. You're looking at Spreaker's $250 00:41:49.659 --> 00:41:52.940 a month plan or Megaphone if you have the massive 00:41:52.940 --> 00:41:55.880 download numbers to qualify. You truly get what 00:41:55.880 --> 00:41:58.480 you pay for in this digital real estate market. 00:41:58.760 --> 00:42:01.730 Which brings us to a lingering. Somewhat philosophical 00:42:01.730 --> 00:42:03.829 question that emerges from studying all these 00:42:03.829 --> 00:42:06.449 sources. Let's hear it. We are witnessing a profound 00:42:06.449 --> 00:42:09.289 evolution in this space. Podcast hosts are no 00:42:09.289 --> 00:42:12.110 longer just simple RSS feed generators. No, they're 00:42:12.110 --> 00:42:15.309 not. They are rapidly transforming into massive 00:42:15.309 --> 00:42:18.289 all -in -one ecosystems. They're offering AI 00:42:18.289 --> 00:42:21.250 editing, built -in website builders, proprietary 00:42:21.250 --> 00:42:24.289 ad networks, and exclusive monetization tools 00:42:24.289 --> 00:42:26.809 all under one roof. Like we said earlier, they're 00:42:26.809 --> 00:42:28.849 building the whole neighborhood, not just selling 00:42:28.849 --> 00:42:32.440 you the house. Precisely. And this raises a provocative 00:42:32.440 --> 00:42:34.880 thought for you to ponder as you make your final 00:42:34.880 --> 00:42:38.639 choice. The fundamental architecture of podcasting 00:42:38.639 --> 00:42:42.019 has historically been decentralized and fiercely 00:42:42.019 --> 00:42:45.579 open. Anyone could create an RSS feed and distribute 00:42:45.579 --> 00:42:48.699 it to any app anywhere in the world. But as these 00:42:48.699 --> 00:42:51.099 hosting platforms bundle more and more proprietary 00:42:51.099 --> 00:42:54.260 tools into their closed ecosystems, are we moving 00:42:54.260 --> 00:42:56.739 away from that open nature? That's a scary thought. 00:42:56.940 --> 00:42:59.300 Will the future of podcasting require you to 00:42:59.300 --> 00:43:02.039 choose not just a host, but a walled media garden? 00:43:02.519 --> 00:43:04.960 Because when you're editing workflow, your website, 00:43:05.260 --> 00:43:07.280 your granular analytics, and your advertising 00:43:07.280 --> 00:43:10.440 are all locked into a single provider's proprietary 00:43:10.440 --> 00:43:13.159 format. The technical cost of migrating away 00:43:13.159 --> 00:43:16.300 becomes exceptionally high. Exactly. You might 00:43:16.300 --> 00:43:18.920 find that the convenient, move -in -ready condo 00:43:18.920 --> 00:43:21.539 you bought is actually a gated community that 00:43:21.539 --> 00:43:24.760 you can never realistically leave. Wow. It's 00:43:24.760 --> 00:43:26.380 something to think carefully about as you sign 00:43:26.380 --> 00:43:27.199 that digital lease.