Debug Information

Processing Details

• VTT File: e0db8deb.vtt
• Processing Time: September 11, 2025 at 01:31 PM
• Total Chunks: 1
• Transcript Length: 31,650 characters
• Caption Count: 247 captions

Prompts Used

Prompt 1: Context Setup

You are an expert data extractor tasked with analyzing a podcast transcript. 
I will provide you with part 1 of 1 from a podcast transcript. 
I will then ask you to extract different types of information from this content in subsequent messages. Please confirm you have received and understood the transcript content.

Transcript section:
[00:00:00.400 --> 00:00:04.400] Hey, it's Arvid, and this is the Bootstrap Founder.
[00:00:08.880 --> 00:00:19.200] Today, I'll be talking about a successful marketing project within my own software business that turned out to be so successful that it spawned a business built on top of that business.
[00:00:19.200 --> 00:00:24.320] And when this episode is released, it'll be one day since the platform has been live.
[00:00:24.320 --> 00:00:33.680] So, I'll be sharing the most raw and most timely insight into what happened right now, what the story is, how it happened, and how I went about building this particular project.
[00:00:33.680 --> 00:00:44.720] This episode is sponsored by Paddle.com, my merchant of record payment provider of choice, who's been helping me focus on PodScan and the project that I'll be sharing with you today from day one.
[00:00:44.720 --> 00:00:51.360] They're taking care of all the things related to money so that founders like you and me can focus on the things that only we can build.
[00:00:51.360 --> 00:00:55.200] Paddle handles the rest, sales tax, credit cards failing, all of that.
[00:00:55.200 --> 00:00:56.240] They take care of it.
[00:00:56.240 --> 00:00:57.840] I highly recommend looking into it.
[00:00:57.840 --> 00:01:01.040] So, please check out paddle.com.
[00:01:02.320 --> 00:01:30.160] The thing I built is called the PodScan Ideas newsletter, and on top of that newsletter now sits the PodScan Ideas Vault, which is a platform that tracks, scores, ranks, and analyzes all kinds of business ideas that it pulls from the full transcripts of fresh episodes in real time of around 500 podcasts of all kinds, mainly focused on the entrepreneurial business, finance, philosophy, and science shows out there.
[00:01:30.160 --> 00:01:34.560] Now, I know it's not a novel idea to extract information from other media, right?
[00:01:34.560 --> 00:01:49.200] The whole idea of travel guides or rewatch podcasts for that matter, I watch and listen to quite a few of those, is pretty much an indicator that there is value just from extracting things from existing content created by other people.
[00:01:49.200 --> 00:01:58.800] But PodScan in particular has been extremely well set up to extract information from a whole industry's worth of insights and content in a very, very easy way.
[00:01:58.800 --> 00:02:01.480] And I'm just going to share how all of this came to be.
[00:01:59.840 --> 00:02:08.760] Because I have several customers on PodScan.fm that have lists of podcasts set up with a webhook.
[00:02:08.760 --> 00:02:18.280] Whenever a new episode comes out for any of these shows, it sends the full info about this episode to their servers and they send it through a lot of cleaning up, right?
[00:02:18.280 --> 00:02:27.240] They take the full transcript that I provide with every single show, they analyze it, have an AI summarize it, and do a lot of stuff with it, different things for different people.
[00:02:27.240 --> 00:02:34.760] And then they generate some kind of content from this data and send that out or make it available to their customers.
[00:02:34.760 --> 00:02:40.120] Imagine I have a couple of people just taking podcasts and summarizing them and turning that into a newsletter.
[00:02:40.120 --> 00:02:42.200] It's really as simple as that for some.
[00:02:42.200 --> 00:02:44.440] But there's one really interesting one.
[00:02:44.440 --> 00:02:48.040] I have a particular customer that works in the medical field.
[00:02:48.040 --> 00:02:59.240] He's a doctor who summarizes very specific podcasts in a very specific subfield of his industry, like a subdivision of a particular kind of surgery.
[00:02:59.240 --> 00:03:01.800] It's very, very precise, very specific.
[00:03:01.800 --> 00:03:07.640] And he takes all of the podcasts in that particular industry that are run by experts.
[00:03:07.640 --> 00:03:26.920] He extracts the most relevant information from all these shows and then even translates that into a foreign language so that the people who operate in that field in his particular country are able to get all the information from all these many hundreds of hours of podcasts that come out every week at a glance.
[00:03:26.920 --> 00:03:34.840] He even has the capacity to show only the episodes that are relevant to one particular person and their sub-interest in that sub-field of medicine.
[00:03:34.840 --> 00:03:35.960] It's really, really cool.
[00:03:35.960 --> 00:03:37.720] It's really inspirational.
[00:03:37.720 --> 00:03:40.760] And it's inspired me to do something about it myself.
[00:03:40.760 --> 00:03:44.840] Because I recently thought about what a success story that actually is for the platform, right?
[00:03:44.960 --> 00:03:57.120] From my own marketing perspective, somebody is pulling all this information through my API, through our webhooks that we send out, the real-time webhooks that are activated whenever a new episode comes out and we finish transcribing it.
[00:03:57.120 --> 00:04:02.640] And we sent the full transcript to anybody who has an account on PodScan and is tracking to a particular show.
[00:04:02.640 --> 00:04:04.160] So it's super useful.
[00:04:04.160 --> 00:04:07.520] And I was like, this is a great example of how PodScan can be used.
[00:04:07.520 --> 00:04:11.200] So why don't I tell my audience about this particular use case?
[00:04:11.200 --> 00:04:16.160] There's probably a lot of people out there which could use this, which I then did a couple of weeks later.
[00:04:16.160 --> 00:04:35.840] I started working on sharing not only that this story exists, I shared that on Twitter, which is cool, but also promising that I would build an automation using the existing automation tools out there, things like Zapier or N8N or Make, just to show people how this can be done reliably using that platform and PodScan's API.
[00:04:35.840 --> 00:04:40.640] Because I wanted to show, hey, PodScan can be easily integrated and I wanted to reach more customers, right?
[00:04:40.640 --> 00:04:42.160] That was the motivation behind all of this.
[00:04:42.160 --> 00:04:47.040] So why not do development or coding or integrating as marketing here?
[00:04:47.040 --> 00:04:51.520] There's a phrase called engineering is marketing, and I think this falls under that umbrella.
[00:04:51.520 --> 00:04:58.160] I'm building something, sharing the process of building it, and then the final product so people can see, hmm, I could do this too.
[00:04:58.160 --> 00:05:06.080] So I started building an automation on N8N, which is a very highly flexible but more technical platform to build integrations in.
[00:05:06.080 --> 00:05:11.760] I think Zapier, probably I could have built this too, but N8N is this whole flowchart of all kinds of things.
[00:05:11.760 --> 00:05:13.760] It's quite developer-y, right?
[00:05:13.760 --> 00:05:16.160] If you're the dev, you immediately understand what it is.
[00:05:16.160 --> 00:05:18.880] If you're not technical, it might be more complicated to get into.
[00:05:18.880 --> 00:05:24.880] You'll still figure it out, but it has a couple of components where you need to understand the underlying technology.
[00:05:24.880 --> 00:05:27.120] Other platforms are more plug-and-play.
[00:05:27.120 --> 00:05:34.920] So I took my webhook that came from my podcast list where I just added a couple hundred podcasts from all kinds of interesting industries.
[00:05:35.560 --> 00:05:41.800] And then I took this webhook, pulled it into N8N, and generated a summary for each of these episodes and saved that in a Google Sheet.
[00:05:41.800 --> 00:05:44.520] It's really that simple as a basic functionality.
[00:05:44.520 --> 00:05:47.240] I just used tools that I already had active, right?
[00:05:47.240 --> 00:05:50.600] I didn't have some kind of software service or a back-end or database.
[00:05:50.600 --> 00:05:55.720] I just used Google Sheets, OpenAI's APIs, and everything else that N8N offered.
[00:05:55.720 --> 00:06:00.360] And that was just more logic, like if-then-else and switch and summarize and all of that.
[00:06:00.360 --> 00:06:05.720] I wanted to create a newsletter, just like my customer, out of this data from the podcasts.
[00:06:05.720 --> 00:06:10.440] And I thought, well, my audience isn't medical, my audience is entrepreneurial.
[00:06:10.440 --> 00:06:15.720] Why not take all the good ideas that happen to come from all of these podcasts?
[00:06:15.720 --> 00:06:18.600] Because people talk about, oh, I wish this would exist.
[00:06:18.600 --> 00:06:21.000] Or, hey, this industry has these kind of problems.
[00:06:21.000 --> 00:06:22.360] Somebody really should solve it.
[00:06:22.360 --> 00:06:23.480] And here's an idea I had.
[00:06:23.480 --> 00:06:25.880] I'm not going to build it, but you know, maybe look into it.
[00:06:25.880 --> 00:06:27.400] People talk about this all the time.
[00:06:27.400 --> 00:06:31.480] So, whenever that comes up, an AI can find these things, right?
[00:06:31.560 --> 00:06:36.600] Can find these occurrences and take out the idea, flesh it out a little bit, and present it.
[00:06:36.600 --> 00:06:40.440] So, I could turn it into, well, this could be a solution here.
[00:06:40.440 --> 00:06:51.480] You could build, I don't know, an AI-powered marketplace that sells these things to these people because it knows exactly who they are, or because both are trying to look for sellers and buyers, and it combines them in an interesting way.
[00:06:51.720 --> 00:06:55.960] Things like you could turn this into an info product because people say, I want to read about this.
[00:06:55.960 --> 00:06:59.800] Well, why don't you just build something that facilitates that and gives people that information?
[00:06:59.800 --> 00:07:04.040] There's a lot of good stuff out there that people need and talk about.
[00:07:04.040 --> 00:07:11.320] So, in my workflow on N8N, I took my webhook and I generated this idea-based summary just using OpenAI.
[00:07:11.320 --> 00:07:16.720] I posted the full transcript into an OpenAI prompt, asked it to take the best three ideas out of it.
[00:07:16.720 --> 00:07:20.960] And then I would write those ideas one by one into a Google sheet.
[00:07:20.960 --> 00:07:44.000] And once a week, I thought initially, but it turned out to be once a day, I would take all of the items from my Google sheet, rank them in some way, score them, take the top 10, and turn those top 10 into an email and markdown document that also was generated by an AI and feed that markdown into kit.com, formerly ConvertKit, kind of an email service provider, and just create a new broadcast.
[00:07:44.000 --> 00:07:47.920] That's what they call an email, and send it out to everybody who subscribed to it.
[00:07:47.920 --> 00:07:49.520] That was the idea, right?
[00:07:49.520 --> 00:07:56.480] Get webhook, get summary, save the sheet once a day, pull all the information from the sheet, and put that into one email.
[00:07:56.480 --> 00:07:59.040] Now, Kit has a really wonderful integration.
[00:07:59.040 --> 00:08:07.440] So you can have a landing page where people can easily sign up and you can easily tag them so you know exactly who wants to read this newsletter.
[00:08:07.440 --> 00:08:24.240] I very quickly got something working here that just created a nice list of the top 10 ideas and had additional information for each idea, like how feasible it is, how much money you would need to spend to get there, what the challenges are, the opportunities, and how you can potentially measure the idea if it's implemented right.
[00:08:24.240 --> 00:08:34.720] All of this turned into a newsletter ready to be sent out automatically, scheduled even just from my incoming webhook information that has a transcript for each podcast episode.
[00:08:34.720 --> 00:08:40.400] And a couple hours later, you know, just kind of ironing out the kinks, I had a fully working workflow.
[00:08:40.400 --> 00:08:47.680] I took a screenshot of this, just the N8N workflow page, and I shared that on Twitter and got a lot of positive feedback.
[00:08:47.680 --> 00:08:55.760] People were like, I didn't know that this API could be used in the first place, but I didn't know you could even do this, like pull information, generate a newsletter out of it.
[00:08:55.760 --> 00:09:04.920] And people were signing up for PodScan to begin with to see if they could themselves build something without knowing exactly how to do it because I only shared the workflow, not how I built it.
[00:08:59.760 --> 00:09:06.840] But people were just trying to experiment with that.
[00:09:07.000 --> 00:09:09.480] But that was already a win for me and for PodScan, right?
[00:09:09.480 --> 00:09:16.600] I already had some interest from the community on, hmm, I could see myself using that API for something.
[00:09:16.600 --> 00:09:19.400] People signed up and I got a lot of DMs on Twitter.
[00:09:19.400 --> 00:09:28.920] And that's the interesting part from people that would really like to see me walk them through it so they could set it up themselves, something like that for their own industry.
[00:09:28.920 --> 00:09:30.920] So I decided to make a video out of it.
[00:09:30.920 --> 00:09:35.640] I recorded myself explaining the already set up process in the NHN workflow.
[00:09:35.640 --> 00:09:43.160] Every single thing, I talked about the full configuration, why it's that way, how it happened, and how you can pull it together.
[00:09:43.160 --> 00:09:44.600] Here's where the webhook comes in.
[00:09:44.600 --> 00:09:46.440] Here are the fields you can expect.
[00:09:46.440 --> 00:09:48.040] Here's how you can create a summary.
[00:09:48.040 --> 00:09:50.200] I even shared the prompts for each of these steps.
[00:09:50.200 --> 00:09:54.840] It's in the YouTube videos description, both the summary and the newsletter generation.
[00:09:54.840 --> 00:10:01.800] And I shared which APIs I use, what the kit.com API looks like, how to deal with that, and what Google Sheets can be used like.
[00:10:01.800 --> 00:10:08.920] Obviously, anybody could use whatever they want, but I just shared how I approached it in the video so people could rebuild the exact same thing.
[00:10:08.920 --> 00:10:12.120] And I shared that video on Twitter to great success.
[00:10:12.120 --> 00:10:17.320] A lot of people signed up to PodScan just to see if they could build something like this now that they had this blueprint.
[00:10:17.320 --> 00:10:21.640] But here's the thing: a lot of people were interested in the actual outcome.
[00:10:21.640 --> 00:10:22.760] That newsletter.
[00:10:22.760 --> 00:10:25.480] It wasn't just an experiment to show how PodScan worked.
[00:10:25.480 --> 00:10:28.600] People wanted to actually get the business ideas too.
[00:10:28.600 --> 00:10:29.800] And they told me.
[00:10:29.800 --> 00:10:33.640] So I doubled down and made the newsletter generation tool better and better.
[00:10:33.640 --> 00:10:39.320] I refined the prompts and all of that, just made it more cohesive, but it was still just a newsletter.
[00:10:39.320 --> 00:10:41.160] And people started signing up for it.
[00:10:41.160 --> 00:10:42.360] It's really great.
[00:10:42.360 --> 00:10:50.160] But just a newsletter is wonderful because it's always going to be this way for me to advertise PodScan, being the source of all this information in the newsletter.
[00:10:50.160 --> 00:10:51.920] But there's so much missing, right?
[00:10:51.920 --> 00:10:57.440] In 500 plus podcasts that I currently track for the newsletter, there are a lot of ideas.
[00:10:57.440 --> 00:10:59.360] Most shows have an idea of some sort.
[00:10:59.360 --> 00:11:06.880] I get hundreds of ideas a day, but only a couple of them make it into the email because 10 is a lot to read through in an email.
[00:11:06.880 --> 00:11:08.960] But what do I do with the other ideas?
[00:11:08.960 --> 00:11:17.120] People wouldn't be able to get them because I just take the top 10, but the others might still be interesting and they might be super niche, but somebody might have the perfect idea for them there, right?
[00:11:17.120 --> 00:11:26.080] So I thought, how about I build the platform where I save all of these other ideas and make them available, searchable to anybody who's interested?
[00:11:26.080 --> 00:11:34.960] And obviously, this being an extension of PodScan, because it's sitting on top of PodScan's APIs and PodScan data, I could likely monetize that a little bit as well.
[00:11:34.960 --> 00:11:37.040] The newsletter would always be free.
[00:11:37.040 --> 00:11:43.200] Cool ideas should be out there, but 10 of them for free a day, every single day, that's thousands a year.
[00:11:43.200 --> 00:11:44.160] That's wonderful.
[00:11:44.160 --> 00:11:49.760] How about I make everything free that happens over the last 24 hours, both in the newsletter and on the platform?
[00:11:49.760 --> 00:11:51.520] That was my initial thought.
[00:11:51.520 --> 00:11:56.320] And if it's older than 24 hours, it's pretty much an archived idea.
[00:11:56.320 --> 00:12:04.000] And something that came up last week, and you want to look at it, something like that, I will make it available for a fee through a subscription to the platform.
[00:12:04.000 --> 00:12:04.880] And then some.
[00:12:04.880 --> 00:12:09.440] That's kind of the basic idea for the PodScan ideas vault.
[00:12:09.440 --> 00:12:14.720] And once I started thinking about this, I very quickly came up with this idea of the newsletter vault.
[00:12:14.800 --> 00:12:25.920] Not just a newsletter vault, the idea vault, because a vault would be a place where all the good ideas are stored and stashed, where you can search for them, search for the ones that are related, do deep analysis on one idea.
[00:12:25.920 --> 00:12:33.720] Maybe you could even chat with an idea to see what the potential problems are beyond just a couple of paragraphs that are in the newsletter, like really dive deep.
[00:12:33.800 --> 00:12:41.400] Could do a deep analysis where you have a really smart system, look into the potential pitfalls, all the potential little challenges along the way.
[00:12:41.400 --> 00:12:51.160] You could even have the opportunity to click a button and have the idea be built by tools like Lavable Bolt, V0, any of these tools that allow you to prompt your way into a product.
[00:12:51.160 --> 00:12:54.920] Well, I have the prompt because I have the full idea in great detail.
[00:12:54.920 --> 00:12:57.560] And I have a system that could easily make this available.
[00:12:57.560 --> 00:12:59.960] Well, it's probably not going to be a big surprise.
[00:12:59.960 --> 00:13:09.480] All of this is possible right now because I built this as a software as a service platform on ideas.podscan.fm and it solves exactly this problem.
[00:13:09.480 --> 00:13:11.160] It's the PodScan Ideas Vault.
[00:13:11.160 --> 00:13:17.000] It's a really simple Laravel 12 project that has been completely coded by cloud code.
[00:13:17.000 --> 00:13:25.160] I wrote maybe two lines of code in this manually and everything else was fully automatically prompted into existence.
[00:13:25.160 --> 00:13:30.120] I told it to use Laravel Spark, which is the Paddle integration that I use.
[00:13:30.120 --> 00:13:38.680] And Paddle being my payment provider of choice was the thing that I went for immediately because I thought, yeah, I want to monetize this as quickly as possible.
[00:13:38.680 --> 00:13:40.520] So I'm going to use the thing I know.
[00:13:40.520 --> 00:13:46.440] I used the default tailwind design because it's also very data focused and I don't need to have fancy graphics, anything.
[00:13:46.440 --> 00:13:54.040] The whole platform is very much focused on the data of ideas and the concepts that I'm interested in and that founders might be interested in.
[00:13:54.040 --> 00:14:07.720] And I integrated a couple of webhook endpoints where now that I had this platform running, instead of saving data into Google Sheets, which I ran into like rate limiting issues on occasion, this application would now host all the ideas.
[00:14:07.880 --> 00:14:12.280] I would just save them to my own database, which is it's all hosted on Laravel Cloud.
[00:14:12.280 --> 00:14:16.640] So it's a serverless Postgres database in there, very cheap, very reliable.
[00:14:16.960 --> 00:14:23.280] It's very easy to set up, and Laravel supports this stuff very, very quickly.
[00:14:23.600 --> 00:14:27.280] The database would also host all the past newsletter episodes.
[00:14:27.280 --> 00:14:30.960] It would be an archive of both the ideas and the newsletters that they were in.
[00:14:30.960 --> 00:14:45.680] So my N8N automation could then slowly be either turned into a completely internal process, I'm not there yet, or at least I could use these endpoints of the ideas vault to store and fetch information from and not rely on the Google Sheets anymore, which made it a lot easier.
[00:14:45.680 --> 00:14:49.360] It's much easier to query information than having to sift through a Google Sheet.
[00:14:49.360 --> 00:14:52.160] Even though it's possible, this just made it easier.
[00:14:52.160 --> 00:14:54.000] I built this over two or three days.
[00:14:54.000 --> 00:14:57.840] I created a new account on Paddle, which was verified a couple days after.
[00:14:57.840 --> 00:15:01.440] And then I started integrating all the relevant secrets into the project.
[00:15:01.680 --> 00:15:05.200] You kind of have to test your payment system and then you go for the production system.
[00:15:05.200 --> 00:15:07.440] Very easy to do with Laravel Spark.
[00:15:07.440 --> 00:15:11.200] Just a couple environment details that I had to add and that was it.
[00:15:11.200 --> 00:15:36.640] And now it's a fully functioning software platform that hosts at this point almost 1,500 ideas that were extracted from actual individual podcast episodes with quotes from where that thing was mentioned, with the actual location in the conversation where the idea came from, and what the idea is and what founder it's for, how much it might take you to get to any revenue, how much time it might take, and what the initial investment might be.
[00:15:36.640 --> 00:15:42.720] All of this constantly automatically extracted from podcast episodes as they are being released in hundreds of shows.
[00:15:42.720 --> 00:15:45.520] It's a really cool system, fully automated.
[00:15:45.520 --> 00:15:51.280] And I added a function for people to suggest new podcasts to track that I can then add to the system.
[00:15:51.280 --> 00:15:57.520] I added functions for people to chat with ideas, to even favorite ideas, and have a conversation with those.
[00:15:57.520 --> 00:16:05.480] You can see past newsletter episodes, all of this is pretty much available for free for anything that was added in the last 24 hours or so.
[00:16:05.480 --> 00:16:07.800] Yeah, it's, I think, exactly 24 hours.
[00:16:07.800 --> 00:16:09.480] That stuff stays available.
[00:16:09.480 --> 00:16:17.080] Any idea, any newsletter episode that is 24 hours or younger is completely available to anybody who's interested, both if you're logged in or not logged in.
[00:16:17.080 --> 00:16:24.520] In the moment you want to go to an idea or a newsletter that is older than this, you're asked to purchase a $10 subscription.
[00:16:24.520 --> 00:16:30.280] It's been very simple to build because Claude is highly capable of building these kind of CRUD applications, right?
[00:16:30.280 --> 00:16:35.400] The create, read, update, delete apps that just interact with the database and show things from the database.
[00:16:35.400 --> 00:16:38.520] And then you add comments to it, have a couple of relationships there.
[00:16:38.520 --> 00:16:39.640] Claude is really good at this.
[00:16:39.640 --> 00:16:42.200] So it was really easy to prompt my way into.
[00:16:42.200 --> 00:16:44.280] And this has now been operating for a week.
[00:16:44.280 --> 00:16:47.240] I was just testing the system, see that it is reliable.
[00:16:47.240 --> 00:16:59.160] And yesterday, as of this episode being released, the newsletter itself contains a link to the ideas platform, an actual link to the idea hosted in the ideas world for each idea in the newsletter.
[00:16:59.160 --> 00:17:00.840] I started sharing this on Twitter.
[00:17:00.840 --> 00:17:01.880] I'll see where this is going.
[00:17:01.880 --> 00:17:03.640] Like you're really in the middle of this right now.
[00:17:03.640 --> 00:17:07.000] So I cannot tell you more than I know because I don't know anything about it just yet.
[00:17:07.000 --> 00:17:17.880] But I think this will be an interesting source of revenue for PodScan, which it is because, you know, this is a database that just keeps growing in terms of the value of the content, the ideas.
[00:17:17.880 --> 00:17:25.160] I have vector search happening in there so people can find ideas for keywords that aren't even mentioned in those ideas, but finds it by proximity.
[00:17:25.160 --> 00:17:30.120] I think it's a really interesting project just to source information from what's already out there.
[00:17:30.120 --> 00:17:36.280] But it also has the capacity to show people how easy it is to set up something that sits on top of the PodScan API.
[00:17:36.280 --> 00:17:37.880] So that's the win-win part here, right?
[00:17:37.880 --> 00:17:44.960] All the podcasts, all these episodes, all these transcripts, they have so much valuable data in there, and people get to see this.
[00:17:44.440 --> 00:17:47.840] This is just one way of showing how this can be used.
[00:17:44.600 --> 00:17:49.920] So it's a business on top of a business.
[00:17:50.240 --> 00:17:54.720] I think I'll look into building similar things, other ones just like it over the next couple of weeks.
[00:17:54.720 --> 00:18:08.240] But because this is so heavily automated and it's such a daily injection of fresh ideas into the community, I think it's going to be really a helpful little tool to pull information from podcasts out there and inspire people to do this for their own industries.
[00:18:08.240 --> 00:18:14.560] And in my own numbers, in the prospects on PodScan itself, this has already shown an uptick.
[00:18:14.560 --> 00:18:15.520] People have been signing up.
[00:18:15.520 --> 00:18:24.480] The idea of sharing, the whole concept of taking podcast content and reworking into condensed, extracted information that you then share periodically, that's not just my Dr.
[00:18:24.640 --> 00:18:25.600] Customer's idea.
[00:18:25.600 --> 00:18:28.800] It's not just what the PodScan ideas world is about.
[00:18:28.800 --> 00:18:34.880] That's a generally applicable concept that can be used for podcast data in almost any industry.
[00:18:34.880 --> 00:18:48.800] So if you have experts in the industry that you serve or that you're part of, you can pull all this information that they have, that they share on podcasts out, compress it, and share it with the yet-to-be experts in that industry.
[00:18:48.800 --> 00:18:50.560] Any industry can benefit from this.
[00:18:50.560 --> 00:18:51.680] And that's so wild, right?
[00:18:51.680 --> 00:18:57.600] You could have construction people that do like a certain kind of architecture, or you can have people in biology.
[00:18:57.600 --> 00:19:00.000] You can have nerds like Star Trek fans, all of this.
[00:19:00.000 --> 00:19:07.920] Like there's so much in any industry, podcasts have some kind of info that people are willing to actually pay money for.
[00:19:07.920 --> 00:19:11.440] You could turn this into automated TikToks and monetize through that.
[00:19:11.440 --> 00:19:14.080] You could turn it into newsletters, obviously paid ones too.
[00:19:14.160 --> 00:19:17.600] Could turn it into individual emails that you send out to individual people.
[00:19:17.600 --> 00:19:18.640] It really doesn't matter.
[00:19:18.640 --> 00:19:19.840] The data source is the same.
[00:19:20.000 --> 00:19:22.800] That's the PodScan API with all these podcasts.
[00:19:22.800 --> 00:19:27.600] We even have a Firehost that gives access to all the podcasts as they are being released.
[00:19:27.600 --> 00:19:34.040] So you could technically serve every single industry if you were building the right platform to determine what belongs where.
[00:19:29.920 --> 00:19:35.320] So there's a lot of opportunity here.
[00:19:35.560 --> 00:19:37.800] So that is what I'm trying to do right now.
[00:19:37.800 --> 00:19:41.400] It's engineering as marketing and business building as marketing.
[00:19:41.400 --> 00:19:48.840] And it's both an opportunity to get people to have a subscription on Ideas Vault and to see the power of PodScan and become a subscriber there.
[00:19:48.840 --> 00:19:50.920] So yeah, that's my latest project.
[00:19:50.920 --> 00:19:51.720] I think it's really fun.
[00:19:51.800 --> 00:19:53.240] It's been a lot of fun to build.
[00:19:53.240 --> 00:19:57.320] And please do check it out at ideas.podscan.fm.
[00:19:57.320 --> 00:20:01.480] You'll see all the latest business ideas sourced from these shows there for free.
[00:20:01.480 --> 00:20:04.360] And if you're looking for a business idea, these are really, really cool.
[00:20:04.360 --> 00:20:06.920] And all of them link to the podcast where the idea was discussed.
[00:20:06.920 --> 00:20:08.120] So you can check that out.
[00:20:08.120 --> 00:20:12.440] They're all scored, they're analyzed, might be really interesting to find the thing you want to build.
[00:20:12.440 --> 00:20:14.360] I've seen a couple really, really great ones.
[00:20:14.360 --> 00:20:20.440] And of course, there have been challenges, technical challenges in making this tool work, making it interesting, making the ideas good.
[00:20:20.440 --> 00:20:22.840] I think I'll share more about this over time.
[00:20:22.920 --> 00:20:29.800] Already had to implement quite a lot of things to make ideas pop more, to make them more valuable, which is, I guess, a trade secret at this point.
[00:20:29.800 --> 00:20:36.200] But, you know, I'll share more over the next couple of weeks as I learn more about my customers here and what people want to see.
[00:20:36.200 --> 00:20:37.640] And I just want to see where it goes.
[00:20:37.640 --> 00:20:38.680] So let me know what you think.
[00:20:38.680 --> 00:20:45.560] I'm always excited to hear, particularly in the super early stage, where this could go, where you want to see it go, and all of that.
[00:20:45.560 --> 00:20:52.920] So I'm excited about the PodScan Ideas Vault and the power of PodScan being shown in a real project just sitting on top of the API.
[00:20:52.920 --> 00:20:54.200] And that's it for today.
[00:20:54.200 --> 00:20:56.280] Thank you so much for listening to the Bootstrap Founder.
[00:20:56.280 --> 00:20:59.560] Find me on Twitter at Abitka, A-R-I-D-K-A-H-L.
[00:20:59.560 --> 00:21:10.200] If you want to know what everyone's saying about your brand on 3.8 million podcasts, podscan.fm tracks mentions with a powerful API that turns podcast conversations into actionable data.
[00:21:10.200 --> 00:21:23.680] And if you're hunting for your next business idea, get them delivered fresh from the podcast world at ideas.podscom.fm, where AI extracts the best startup opportunities for hundreds of hours of expert conversations every day.
[00:21:23.680 --> 00:21:27.040] Share this with anyone that needs to stay ahead of the conversation.
[00:21:27.040 --> 00:21:27.840] Thank you so much.
[00:21:27.840 --> 00:21:30.480] Have a wonderful day and bye-bye.

Prompt 2: Key Takeaways

Now please extract the key takeaways from the transcript content I provided.

Extract the most important key takeaways from this part of the conversation. Use a single sentence statement (the key takeaway) rather than milquetoast descriptions like "the hosts discuss...". 

Limit the key takeaways to a maximum of 3. The key takeaways should be insightful and knowledge-additive. 

IMPORTANT: Return ONLY valid JSON, no explanations or markdown. Ensure:
- All strings are properly quoted and escaped
- No trailing commas
- All braces and brackets are balanced
Format: {"key_takeaways": ["takeaway 1", "takeaway 2"]}

Prompt 3: Segments

Now identify 2-4 distinct topical segments from this part of the conversation.

For each segment, identify:
- Descriptive title (3-6 words)  
- START timestamp when this topic begins (HH:MM:SS format)
- Double check that the timestamp is accurate - a timestamp will NEVER be greater than the total length of the audio
- Most important Key takeaway from that segment. Key takeaway must be specific and knowledge-additive.
- Brief summary of the discussion

IMPORTANT: The timestamp should mark when the topic/segment STARTS, not a range. Look for topic transitions and conversation shifts.

Return ONLY valid JSON. Ensure all strings are properly quoted, no trailing commas:
{
  "segments": [
    {
      "segment_title": "Topic Discussion", 
      "timestamp": "01:15:30",
      "key_takeaway": "main point from this segment",
      "segment_summary": "brief description of what was discussed"
    }
  ]
}

Timestamp format: HH:MM:SS (e.g., 00:05:30, 01:22:45) marking the START of each segment.

Prompt 4: Media Mentions

Now scan the transcript content I provided for ACTUAL mentions of specific media titles:

Find explicit mentions of:
- Books (with specific titles)
- Movies (with specific titles)  
- TV Shows (with specific titles)
- Music/Songs (with specific titles)

DO NOT include:
- Websites, URLs, or web services
- Other podcasts or podcast names

IMPORTANT: 
- Only include items explicitly mentioned by name. Do not invent titles.
- Valid categories are: "Book", "Movie", "TV Show", "Music"
- Include the exact phrase where each item was mentioned
- Find the nearest proximate timestamp where it appears in the conversation
- THE TIMESTAMP OF THE MEDIA MENTION IS IMPORTANT - DO NOT INVENT TIMESTAMPS AND DO NOT MISATTRIBUTE TIMESTAMPS
- Double check that the timestamp is accurate - a timestamp will NEVER be greater than the total length of the audio
- Timestamps are given as ranges, e.g. 01:13:42.520 --> 01:13:46.720. Use the EARLIER of the 2 timestamps in the range.

Return ONLY valid JSON. Ensure all strings are properly quoted and escaped, no trailing commas:
{
  "media_mentions": [
    {
      "title": "Exact Title as Mentioned",
      "category": "Book",
      "author_artist": "N/A",
      "context": "Brief context of why it was mentioned",
      "context_phrase": "The exact sentence or phrase where it was mentioned",
      "timestamp": "estimated time like 01:15:30"
    }
  ]
}

If no media is mentioned, return: {"media_mentions": []}

Full Transcript

[00:00:00.400 --> 00:00:04.400] Hey, it's Arvid, and this is the Bootstrap Founder.
[00:00:08.880 --> 00:00:19.200] Today, I'll be talking about a successful marketing project within my own software business that turned out to be so successful that it spawned a business built on top of that business.
[00:00:19.200 --> 00:00:24.320] And when this episode is released, it'll be one day since the platform has been live.
[00:00:24.320 --> 00:00:33.680] So, I'll be sharing the most raw and most timely insight into what happened right now, what the story is, how it happened, and how I went about building this particular project.
[00:00:33.680 --> 00:00:44.720] This episode is sponsored by Paddle.com, my merchant of record payment provider of choice, who's been helping me focus on PodScan and the project that I'll be sharing with you today from day one.
[00:00:44.720 --> 00:00:51.360] They're taking care of all the things related to money so that founders like you and me can focus on the things that only we can build.
[00:00:51.360 --> 00:00:55.200] Paddle handles the rest, sales tax, credit cards failing, all of that.
[00:00:55.200 --> 00:00:56.240] They take care of it.
[00:00:56.240 --> 00:00:57.840] I highly recommend looking into it.
[00:00:57.840 --> 00:01:01.040] So, please check out paddle.com.
[00:01:02.320 --> 00:01:30.160] The thing I built is called the PodScan Ideas newsletter, and on top of that newsletter now sits the PodScan Ideas Vault, which is a platform that tracks, scores, ranks, and analyzes all kinds of business ideas that it pulls from the full transcripts of fresh episodes in real time of around 500 podcasts of all kinds, mainly focused on the entrepreneurial business, finance, philosophy, and science shows out there.
[00:01:30.160 --> 00:01:34.560] Now, I know it's not a novel idea to extract information from other media, right?
[00:01:34.560 --> 00:01:49.200] The whole idea of travel guides or rewatch podcasts for that matter, I watch and listen to quite a few of those, is pretty much an indicator that there is value just from extracting things from existing content created by other people.
[00:01:49.200 --> 00:01:58.800] But PodScan in particular has been extremely well set up to extract information from a whole industry's worth of insights and content in a very, very easy way.
[00:01:58.800 --> 00:02:01.480] And I'm just going to share how all of this came to be.
[00:01:59.840 --> 00:02:08.760] Because I have several customers on PodScan.fm that have lists of podcasts set up with a webhook.
[00:02:08.760 --> 00:02:18.280] Whenever a new episode comes out for any of these shows, it sends the full info about this episode to their servers and they send it through a lot of cleaning up, right?
[00:02:18.280 --> 00:02:27.240] They take the full transcript that I provide with every single show, they analyze it, have an AI summarize it, and do a lot of stuff with it, different things for different people.
[00:02:27.240 --> 00:02:34.760] And then they generate some kind of content from this data and send that out or make it available to their customers.
[00:02:34.760 --> 00:02:40.120] Imagine I have a couple of people just taking podcasts and summarizing them and turning that into a newsletter.
[00:02:40.120 --> 00:02:42.200] It's really as simple as that for some.
[00:02:42.200 --> 00:02:44.440] But there's one really interesting one.
[00:02:44.440 --> 00:02:48.040] I have a particular customer that works in the medical field.
[00:02:48.040 --> 00:02:59.240] He's a doctor who summarizes very specific podcasts in a very specific subfield of his industry, like a subdivision of a particular kind of surgery.
[00:02:59.240 --> 00:03:01.800] It's very, very precise, very specific.
[00:03:01.800 --> 00:03:07.640] And he takes all of the podcasts in that particular industry that are run by experts.
[00:03:07.640 --> 00:03:26.920] He extracts the most relevant information from all these shows and then even translates that into a foreign language so that the people who operate in that field in his particular country are able to get all the information from all these many hundreds of hours of podcasts that come out every week at a glance.
[00:03:26.920 --> 00:03:34.840] He even has the capacity to show only the episodes that are relevant to one particular person and their sub-interest in that sub-field of medicine.
[00:03:34.840 --> 00:03:35.960] It's really, really cool.
[00:03:35.960 --> 00:03:37.720] It's really inspirational.
[00:03:37.720 --> 00:03:40.760] And it's inspired me to do something about it myself.
[00:03:40.760 --> 00:03:44.840] Because I recently thought about what a success story that actually is for the platform, right?
[00:03:44.960 --> 00:03:57.120] From my own marketing perspective, somebody is pulling all this information through my API, through our webhooks that we send out, the real-time webhooks that are activated whenever a new episode comes out and we finish transcribing it.
[00:03:57.120 --> 00:04:02.640] And we sent the full transcript to anybody who has an account on PodScan and is tracking to a particular show.
[00:04:02.640 --> 00:04:04.160] So it's super useful.
[00:04:04.160 --> 00:04:07.520] And I was like, this is a great example of how PodScan can be used.
[00:04:07.520 --> 00:04:11.200] So why don't I tell my audience about this particular use case?
[00:04:11.200 --> 00:04:16.160] There's probably a lot of people out there which could use this, which I then did a couple of weeks later.
[00:04:16.160 --> 00:04:35.840] I started working on sharing not only that this story exists, I shared that on Twitter, which is cool, but also promising that I would build an automation using the existing automation tools out there, things like Zapier or N8N or Make, just to show people how this can be done reliably using that platform and PodScan's API.
[00:04:35.840 --> 00:04:40.640] Because I wanted to show, hey, PodScan can be easily integrated and I wanted to reach more customers, right?
[00:04:40.640 --> 00:04:42.160] That was the motivation behind all of this.
[00:04:42.160 --> 00:04:47.040] So why not do development or coding or integrating as marketing here?
[00:04:47.040 --> 00:04:51.520] There's a phrase called engineering is marketing, and I think this falls under that umbrella.
[00:04:51.520 --> 00:04:58.160] I'm building something, sharing the process of building it, and then the final product so people can see, hmm, I could do this too.
[00:04:58.160 --> 00:05:06.080] So I started building an automation on N8N, which is a very highly flexible but more technical platform to build integrations in.
[00:05:06.080 --> 00:05:11.760] I think Zapier, probably I could have built this too, but N8N is this whole flowchart of all kinds of things.
[00:05:11.760 --> 00:05:13.760] It's quite developer-y, right?
[00:05:13.760 --> 00:05:16.160] If you're the dev, you immediately understand what it is.
[00:05:16.160 --> 00:05:18.880] If you're not technical, it might be more complicated to get into.
[00:05:18.880 --> 00:05:24.880] You'll still figure it out, but it has a couple of components where you need to understand the underlying technology.
[00:05:24.880 --> 00:05:27.120] Other platforms are more plug-and-play.
[00:05:27.120 --> 00:05:34.920] So I took my webhook that came from my podcast list where I just added a couple hundred podcasts from all kinds of interesting industries.
[00:05:35.560 --> 00:05:41.800] And then I took this webhook, pulled it into N8N, and generated a summary for each of these episodes and saved that in a Google Sheet.
[00:05:41.800 --> 00:05:44.520] It's really that simple as a basic functionality.
[00:05:44.520 --> 00:05:47.240] I just used tools that I already had active, right?
[00:05:47.240 --> 00:05:50.600] I didn't have some kind of software service or a back-end or database.
[00:05:50.600 --> 00:05:55.720] I just used Google Sheets, OpenAI's APIs, and everything else that N8N offered.
[00:05:55.720 --> 00:06:00.360] And that was just more logic, like if-then-else and switch and summarize and all of that.
[00:06:00.360 --> 00:06:05.720] I wanted to create a newsletter, just like my customer, out of this data from the podcasts.
[00:06:05.720 --> 00:06:10.440] And I thought, well, my audience isn't medical, my audience is entrepreneurial.
[00:06:10.440 --> 00:06:15.720] Why not take all the good ideas that happen to come from all of these podcasts?
[00:06:15.720 --> 00:06:18.600] Because people talk about, oh, I wish this would exist.
[00:06:18.600 --> 00:06:21.000] Or, hey, this industry has these kind of problems.
[00:06:21.000 --> 00:06:22.360] Somebody really should solve it.
[00:06:22.360 --> 00:06:23.480] And here's an idea I had.
[00:06:23.480 --> 00:06:25.880] I'm not going to build it, but you know, maybe look into it.
[00:06:25.880 --> 00:06:27.400] People talk about this all the time.
[00:06:27.400 --> 00:06:31.480] So, whenever that comes up, an AI can find these things, right?
[00:06:31.560 --> 00:06:36.600] Can find these occurrences and take out the idea, flesh it out a little bit, and present it.
[00:06:36.600 --> 00:06:40.440] So, I could turn it into, well, this could be a solution here.
[00:06:40.440 --> 00:06:51.480] You could build, I don't know, an AI-powered marketplace that sells these things to these people because it knows exactly who they are, or because both are trying to look for sellers and buyers, and it combines them in an interesting way.
[00:06:51.720 --> 00:06:55.960] Things like you could turn this into an info product because people say, I want to read about this.
[00:06:55.960 --> 00:06:59.800] Well, why don't you just build something that facilitates that and gives people that information?
[00:06:59.800 --> 00:07:04.040] There's a lot of good stuff out there that people need and talk about.
[00:07:04.040 --> 00:07:11.320] So, in my workflow on N8N, I took my webhook and I generated this idea-based summary just using OpenAI.
[00:07:11.320 --> 00:07:16.720] I posted the full transcript into an OpenAI prompt, asked it to take the best three ideas out of it.
[00:07:16.720 --> 00:07:20.960] And then I would write those ideas one by one into a Google sheet.
[00:07:20.960 --> 00:07:44.000] And once a week, I thought initially, but it turned out to be once a day, I would take all of the items from my Google sheet, rank them in some way, score them, take the top 10, and turn those top 10 into an email and markdown document that also was generated by an AI and feed that markdown into kit.com, formerly ConvertKit, kind of an email service provider, and just create a new broadcast.
[00:07:44.000 --> 00:07:47.920] That's what they call an email, and send it out to everybody who subscribed to it.
[00:07:47.920 --> 00:07:49.520] That was the idea, right?
[00:07:49.520 --> 00:07:56.480] Get webhook, get summary, save the sheet once a day, pull all the information from the sheet, and put that into one email.
[00:07:56.480 --> 00:07:59.040] Now, Kit has a really wonderful integration.
[00:07:59.040 --> 00:08:07.440] So you can have a landing page where people can easily sign up and you can easily tag them so you know exactly who wants to read this newsletter.
[00:08:07.440 --> 00:08:24.240] I very quickly got something working here that just created a nice list of the top 10 ideas and had additional information for each idea, like how feasible it is, how much money you would need to spend to get there, what the challenges are, the opportunities, and how you can potentially measure the idea if it's implemented right.
[00:08:24.240 --> 00:08:34.720] All of this turned into a newsletter ready to be sent out automatically, scheduled even just from my incoming webhook information that has a transcript for each podcast episode.
[00:08:34.720 --> 00:08:40.400] And a couple hours later, you know, just kind of ironing out the kinks, I had a fully working workflow.
[00:08:40.400 --> 00:08:47.680] I took a screenshot of this, just the N8N workflow page, and I shared that on Twitter and got a lot of positive feedback.
[00:08:47.680 --> 00:08:55.760] People were like, I didn't know that this API could be used in the first place, but I didn't know you could even do this, like pull information, generate a newsletter out of it.
[00:08:55.760 --> 00:09:04.920] And people were signing up for PodScan to begin with to see if they could themselves build something without knowing exactly how to do it because I only shared the workflow, not how I built it.
[00:08:59.760 --> 00:09:06.840] But people were just trying to experiment with that.
[00:09:07.000 --> 00:09:09.480] But that was already a win for me and for PodScan, right?
[00:09:09.480 --> 00:09:16.600] I already had some interest from the community on, hmm, I could see myself using that API for something.
[00:09:16.600 --> 00:09:19.400] People signed up and I got a lot of DMs on Twitter.
[00:09:19.400 --> 00:09:28.920] And that's the interesting part from people that would really like to see me walk them through it so they could set it up themselves, something like that for their own industry.
[00:09:28.920 --> 00:09:30.920] So I decided to make a video out of it.
[00:09:30.920 --> 00:09:35.640] I recorded myself explaining the already set up process in the NHN workflow.
[00:09:35.640 --> 00:09:43.160] Every single thing, I talked about the full configuration, why it's that way, how it happened, and how you can pull it together.
[00:09:43.160 --> 00:09:44.600] Here's where the webhook comes in.
[00:09:44.600 --> 00:09:46.440] Here are the fields you can expect.
[00:09:46.440 --> 00:09:48.040] Here's how you can create a summary.
[00:09:48.040 --> 00:09:50.200] I even shared the prompts for each of these steps.
[00:09:50.200 --> 00:09:54.840] It's in the YouTube videos description, both the summary and the newsletter generation.
[00:09:54.840 --> 00:10:01.800] And I shared which APIs I use, what the kit.com API looks like, how to deal with that, and what Google Sheets can be used like.
[00:10:01.800 --> 00:10:08.920] Obviously, anybody could use whatever they want, but I just shared how I approached it in the video so people could rebuild the exact same thing.
[00:10:08.920 --> 00:10:12.120] And I shared that video on Twitter to great success.
[00:10:12.120 --> 00:10:17.320] A lot of people signed up to PodScan just to see if they could build something like this now that they had this blueprint.
[00:10:17.320 --> 00:10:21.640] But here's the thing: a lot of people were interested in the actual outcome.
[00:10:21.640 --> 00:10:22.760] That newsletter.
[00:10:22.760 --> 00:10:25.480] It wasn't just an experiment to show how PodScan worked.
[00:10:25.480 --> 00:10:28.600] People wanted to actually get the business ideas too.
[00:10:28.600 --> 00:10:29.800] And they told me.
[00:10:29.800 --> 00:10:33.640] So I doubled down and made the newsletter generation tool better and better.
[00:10:33.640 --> 00:10:39.320] I refined the prompts and all of that, just made it more cohesive, but it was still just a newsletter.
[00:10:39.320 --> 00:10:41.160] And people started signing up for it.
[00:10:41.160 --> 00:10:42.360] It's really great.
[00:10:42.360 --> 00:10:50.160] But just a newsletter is wonderful because it's always going to be this way for me to advertise PodScan, being the source of all this information in the newsletter.
[00:10:50.160 --> 00:10:51.920] But there's so much missing, right?
[00:10:51.920 --> 00:10:57.440] In 500 plus podcasts that I currently track for the newsletter, there are a lot of ideas.
[00:10:57.440 --> 00:10:59.360] Most shows have an idea of some sort.
[00:10:59.360 --> 00:11:06.880] I get hundreds of ideas a day, but only a couple of them make it into the email because 10 is a lot to read through in an email.
[00:11:06.880 --> 00:11:08.960] But what do I do with the other ideas?
[00:11:08.960 --> 00:11:17.120] People wouldn't be able to get them because I just take the top 10, but the others might still be interesting and they might be super niche, but somebody might have the perfect idea for them there, right?
[00:11:17.120 --> 00:11:26.080] So I thought, how about I build the platform where I save all of these other ideas and make them available, searchable to anybody who's interested?
[00:11:26.080 --> 00:11:34.960] And obviously, this being an extension of PodScan, because it's sitting on top of PodScan's APIs and PodScan data, I could likely monetize that a little bit as well.
[00:11:34.960 --> 00:11:37.040] The newsletter would always be free.
[00:11:37.040 --> 00:11:43.200] Cool ideas should be out there, but 10 of them for free a day, every single day, that's thousands a year.
[00:11:43.200 --> 00:11:44.160] That's wonderful.
[00:11:44.160 --> 00:11:49.760] How about I make everything free that happens over the last 24 hours, both in the newsletter and on the platform?
[00:11:49.760 --> 00:11:51.520] That was my initial thought.
[00:11:51.520 --> 00:11:56.320] And if it's older than 24 hours, it's pretty much an archived idea.
[00:11:56.320 --> 00:12:04.000] And something that came up last week, and you want to look at it, something like that, I will make it available for a fee through a subscription to the platform.
[00:12:04.000 --> 00:12:04.880] And then some.
[00:12:04.880 --> 00:12:09.440] That's kind of the basic idea for the PodScan ideas vault.
[00:12:09.440 --> 00:12:14.720] And once I started thinking about this, I very quickly came up with this idea of the newsletter vault.
[00:12:14.800 --> 00:12:25.920] Not just a newsletter vault, the idea vault, because a vault would be a place where all the good ideas are stored and stashed, where you can search for them, search for the ones that are related, do deep analysis on one idea.
[00:12:25.920 --> 00:12:33.720] Maybe you could even chat with an idea to see what the potential problems are beyond just a couple of paragraphs that are in the newsletter, like really dive deep.
[00:12:33.800 --> 00:12:41.400] Could do a deep analysis where you have a really smart system, look into the potential pitfalls, all the potential little challenges along the way.
[00:12:41.400 --> 00:12:51.160] You could even have the opportunity to click a button and have the idea be built by tools like Lavable Bolt, V0, any of these tools that allow you to prompt your way into a product.
[00:12:51.160 --> 00:12:54.920] Well, I have the prompt because I have the full idea in great detail.
[00:12:54.920 --> 00:12:57.560] And I have a system that could easily make this available.
[00:12:57.560 --> 00:12:59.960] Well, it's probably not going to be a big surprise.
[00:12:59.960 --> 00:13:09.480] All of this is possible right now because I built this as a software as a service platform on ideas.podscan.fm and it solves exactly this problem.
[00:13:09.480 --> 00:13:11.160] It's the PodScan Ideas Vault.
[00:13:11.160 --> 00:13:17.000] It's a really simple Laravel 12 project that has been completely coded by cloud code.
[00:13:17.000 --> 00:13:25.160] I wrote maybe two lines of code in this manually and everything else was fully automatically prompted into existence.
[00:13:25.160 --> 00:13:30.120] I told it to use Laravel Spark, which is the Paddle integration that I use.
[00:13:30.120 --> 00:13:38.680] And Paddle being my payment provider of choice was the thing that I went for immediately because I thought, yeah, I want to monetize this as quickly as possible.
[00:13:38.680 --> 00:13:40.520] So I'm going to use the thing I know.
[00:13:40.520 --> 00:13:46.440] I used the default tailwind design because it's also very data focused and I don't need to have fancy graphics, anything.
[00:13:46.440 --> 00:13:54.040] The whole platform is very much focused on the data of ideas and the concepts that I'm interested in and that founders might be interested in.
[00:13:54.040 --> 00:14:07.720] And I integrated a couple of webhook endpoints where now that I had this platform running, instead of saving data into Google Sheets, which I ran into like rate limiting issues on occasion, this application would now host all the ideas.
[00:14:07.880 --> 00:14:12.280] I would just save them to my own database, which is it's all hosted on Laravel Cloud.
[00:14:12.280 --> 00:14:16.640] So it's a serverless Postgres database in there, very cheap, very reliable.
[00:14:16.960 --> 00:14:23.280] It's very easy to set up, and Laravel supports this stuff very, very quickly.
[00:14:23.600 --> 00:14:27.280] The database would also host all the past newsletter episodes.
[00:14:27.280 --> 00:14:30.960] It would be an archive of both the ideas and the newsletters that they were in.
[00:14:30.960 --> 00:14:45.680] So my N8N automation could then slowly be either turned into a completely internal process, I'm not there yet, or at least I could use these endpoints of the ideas vault to store and fetch information from and not rely on the Google Sheets anymore, which made it a lot easier.
[00:14:45.680 --> 00:14:49.360] It's much easier to query information than having to sift through a Google Sheet.
[00:14:49.360 --> 00:14:52.160] Even though it's possible, this just made it easier.
[00:14:52.160 --> 00:14:54.000] I built this over two or three days.
[00:14:54.000 --> 00:14:57.840] I created a new account on Paddle, which was verified a couple days after.
[00:14:57.840 --> 00:15:01.440] And then I started integrating all the relevant secrets into the project.
[00:15:01.680 --> 00:15:05.200] You kind of have to test your payment system and then you go for the production system.
[00:15:05.200 --> 00:15:07.440] Very easy to do with Laravel Spark.
[00:15:07.440 --> 00:15:11.200] Just a couple environment details that I had to add and that was it.
[00:15:11.200 --> 00:15:36.640] And now it's a fully functioning software platform that hosts at this point almost 1,500 ideas that were extracted from actual individual podcast episodes with quotes from where that thing was mentioned, with the actual location in the conversation where the idea came from, and what the idea is and what founder it's for, how much it might take you to get to any revenue, how much time it might take, and what the initial investment might be.
[00:15:36.640 --> 00:15:42.720] All of this constantly automatically extracted from podcast episodes as they are being released in hundreds of shows.
[00:15:42.720 --> 00:15:45.520] It's a really cool system, fully automated.
[00:15:45.520 --> 00:15:51.280] And I added a function for people to suggest new podcasts to track that I can then add to the system.
[00:15:51.280 --> 00:15:57.520] I added functions for people to chat with ideas, to even favorite ideas, and have a conversation with those.
[00:15:57.520 --> 00:16:05.480] You can see past newsletter episodes, all of this is pretty much available for free for anything that was added in the last 24 hours or so.
[00:16:05.480 --> 00:16:07.800] Yeah, it's, I think, exactly 24 hours.
[00:16:07.800 --> 00:16:09.480] That stuff stays available.
[00:16:09.480 --> 00:16:17.080] Any idea, any newsletter episode that is 24 hours or younger is completely available to anybody who's interested, both if you're logged in or not logged in.
[00:16:17.080 --> 00:16:24.520] In the moment you want to go to an idea or a newsletter that is older than this, you're asked to purchase a $10 subscription.
[00:16:24.520 --> 00:16:30.280] It's been very simple to build because Claude is highly capable of building these kind of CRUD applications, right?
[00:16:30.280 --> 00:16:35.400] The create, read, update, delete apps that just interact with the database and show things from the database.
[00:16:35.400 --> 00:16:38.520] And then you add comments to it, have a couple of relationships there.
[00:16:38.520 --> 00:16:39.640] Claude is really good at this.
[00:16:39.640 --> 00:16:42.200] So it was really easy to prompt my way into.
[00:16:42.200 --> 00:16:44.280] And this has now been operating for a week.
[00:16:44.280 --> 00:16:47.240] I was just testing the system, see that it is reliable.
[00:16:47.240 --> 00:16:59.160] And yesterday, as of this episode being released, the newsletter itself contains a link to the ideas platform, an actual link to the idea hosted in the ideas world for each idea in the newsletter.
[00:16:59.160 --> 00:17:00.840] I started sharing this on Twitter.
[00:17:00.840 --> 00:17:01.880] I'll see where this is going.
[00:17:01.880 --> 00:17:03.640] Like you're really in the middle of this right now.
[00:17:03.640 --> 00:17:07.000] So I cannot tell you more than I know because I don't know anything about it just yet.
[00:17:07.000 --> 00:17:17.880] But I think this will be an interesting source of revenue for PodScan, which it is because, you know, this is a database that just keeps growing in terms of the value of the content, the ideas.
[00:17:17.880 --> 00:17:25.160] I have vector search happening in there so people can find ideas for keywords that aren't even mentioned in those ideas, but finds it by proximity.
[00:17:25.160 --> 00:17:30.120] I think it's a really interesting project just to source information from what's already out there.
[00:17:30.120 --> 00:17:36.280] But it also has the capacity to show people how easy it is to set up something that sits on top of the PodScan API.
[00:17:36.280 --> 00:17:37.880] So that's the win-win part here, right?
[00:17:37.880 --> 00:17:44.960] All the podcasts, all these episodes, all these transcripts, they have so much valuable data in there, and people get to see this.
[00:17:44.440 --> 00:17:47.840] This is just one way of showing how this can be used.
[00:17:44.600 --> 00:17:49.920] So it's a business on top of a business.
[00:17:50.240 --> 00:17:54.720] I think I'll look into building similar things, other ones just like it over the next couple of weeks.
[00:17:54.720 --> 00:18:08.240] But because this is so heavily automated and it's such a daily injection of fresh ideas into the community, I think it's going to be really a helpful little tool to pull information from podcasts out there and inspire people to do this for their own industries.
[00:18:08.240 --> 00:18:14.560] And in my own numbers, in the prospects on PodScan itself, this has already shown an uptick.
[00:18:14.560 --> 00:18:15.520] People have been signing up.
[00:18:15.520 --> 00:18:24.480] The idea of sharing, the whole concept of taking podcast content and reworking into condensed, extracted information that you then share periodically, that's not just my Dr.
[00:18:24.640 --> 00:18:25.600] Customer's idea.
[00:18:25.600 --> 00:18:28.800] It's not just what the PodScan ideas world is about.
[00:18:28.800 --> 00:18:34.880] That's a generally applicable concept that can be used for podcast data in almost any industry.
[00:18:34.880 --> 00:18:48.800] So if you have experts in the industry that you serve or that you're part of, you can pull all this information that they have, that they share on podcasts out, compress it, and share it with the yet-to-be experts in that industry.
[00:18:48.800 --> 00:18:50.560] Any industry can benefit from this.
[00:18:50.560 --> 00:18:51.680] And that's so wild, right?
[00:18:51.680 --> 00:18:57.600] You could have construction people that do like a certain kind of architecture, or you can have people in biology.
[00:18:57.600 --> 00:19:00.000] You can have nerds like Star Trek fans, all of this.
[00:19:00.000 --> 00:19:07.920] Like there's so much in any industry, podcasts have some kind of info that people are willing to actually pay money for.
[00:19:07.920 --> 00:19:11.440] You could turn this into automated TikToks and monetize through that.
[00:19:11.440 --> 00:19:14.080] You could turn it into newsletters, obviously paid ones too.
[00:19:14.160 --> 00:19:17.600] Could turn it into individual emails that you send out to individual people.
[00:19:17.600 --> 00:19:18.640] It really doesn't matter.
[00:19:18.640 --> 00:19:19.840] The data source is the same.
[00:19:20.000 --> 00:19:22.800] That's the PodScan API with all these podcasts.
[00:19:22.800 --> 00:19:27.600] We even have a Firehost that gives access to all the podcasts as they are being released.
[00:19:27.600 --> 00:19:34.040] So you could technically serve every single industry if you were building the right platform to determine what belongs where.
[00:19:29.920 --> 00:19:35.320] So there's a lot of opportunity here.
[00:19:35.560 --> 00:19:37.800] So that is what I'm trying to do right now.
[00:19:37.800 --> 00:19:41.400] It's engineering as marketing and business building as marketing.
[00:19:41.400 --> 00:19:48.840] And it's both an opportunity to get people to have a subscription on Ideas Vault and to see the power of PodScan and become a subscriber there.
[00:19:48.840 --> 00:19:50.920] So yeah, that's my latest project.
[00:19:50.920 --> 00:19:51.720] I think it's really fun.
[00:19:51.800 --> 00:19:53.240] It's been a lot of fun to build.
[00:19:53.240 --> 00:19:57.320] And please do check it out at ideas.podscan.fm.
[00:19:57.320 --> 00:20:01.480] You'll see all the latest business ideas sourced from these shows there for free.
[00:20:01.480 --> 00:20:04.360] And if you're looking for a business idea, these are really, really cool.
[00:20:04.360 --> 00:20:06.920] And all of them link to the podcast where the idea was discussed.
[00:20:06.920 --> 00:20:08.120] So you can check that out.
[00:20:08.120 --> 00:20:12.440] They're all scored, they're analyzed, might be really interesting to find the thing you want to build.
[00:20:12.440 --> 00:20:14.360] I've seen a couple really, really great ones.
[00:20:14.360 --> 00:20:20.440] And of course, there have been challenges, technical challenges in making this tool work, making it interesting, making the ideas good.
[00:20:20.440 --> 00:20:22.840] I think I'll share more about this over time.
[00:20:22.920 --> 00:20:29.800] Already had to implement quite a lot of things to make ideas pop more, to make them more valuable, which is, I guess, a trade secret at this point.
[00:20:29.800 --> 00:20:36.200] But, you know, I'll share more over the next couple of weeks as I learn more about my customers here and what people want to see.
[00:20:36.200 --> 00:20:37.640] And I just want to see where it goes.
[00:20:37.640 --> 00:20:38.680] So let me know what you think.
[00:20:38.680 --> 00:20:45.560] I'm always excited to hear, particularly in the super early stage, where this could go, where you want to see it go, and all of that.
[00:20:45.560 --> 00:20:52.920] So I'm excited about the PodScan Ideas Vault and the power of PodScan being shown in a real project just sitting on top of the API.
[00:20:52.920 --> 00:20:54.200] And that's it for today.
[00:20:54.200 --> 00:20:56.280] Thank you so much for listening to the Bootstrap Founder.
[00:20:56.280 --> 00:20:59.560] Find me on Twitter at Abitka, A-R-I-D-K-A-H-L.
[00:20:59.560 --> 00:21:10.200] If you want to know what everyone's saying about your brand on 3.8 million podcasts, podscan.fm tracks mentions with a powerful API that turns podcast conversations into actionable data.
[00:21:10.200 --> 00:21:23.680] And if you're hunting for your next business idea, get them delivered fresh from the podcast world at ideas.podscom.fm, where AI extracts the best startup opportunities for hundreds of hours of expert conversations every day.
[00:21:23.680 --> 00:21:27.040] Share this with anyone that needs to stay ahead of the conversation.
[00:21:27.040 --> 00:21:27.840] Thank you so much.
[00:21:27.840 --> 00:21:30.480] Have a wonderful day and bye-bye.