386: One Year of Podscan: Reflecting on Tech & Business Decisions

Hey. It's Arvid, and this is the Bootstrap founder. Today, I wanna reflect on something that is both foundational to the business and quite personal to me. It's been pretty much a year since I started PodScan, and I think it's time to look at the choices I made back then in terms of technology and dependencies and services and everything around the business and see how they're holding up today. This episode is sponsored by paddle.com, the merchant of record that has been responsible for allowing me to reach profitability just this month. Paddle is truly more. That's m o r, merchant of record, because their product has allowed me to focus on building my own product that people actually want to pay money for. And that's why Paddle does more for you. They deal with taxes and they reach out to customers when they have failed payments. They charge in people's local currency. Do all these things that I don't need to focus on so I can really be present for my customers and their needs. It's amazing. Go check out paddle.com to learn more. So PodScan itself is doing pretty well. It has grown from this experiment that it was a year ago into something quite substantial. It's profitable now and has customers of all kinds that I didn't even expect to serve in the beginning. With every week, I think I shift closer to the perfect messaging and I reach more of the right people at the right time. What I want to share with you today though is me walking through the tech stack and the business stack of the PodScan business and the product. I'll talk about what expectations I had back then in the beginning and if they've been fulfilled, if they've been exceeded or if I had too big or too small expectations. Essentially, what worked out and what is still lacking. I'll start with the tech side of things and then go more into the business side. The services that I use to make PodScan run. Let's start with the tech stack. There are a couple of major choices you always have to make in a software business when you start. What's the general infrastructure that you built your product on? What's the development pipeline and what are the components that you integrate your system with from the beginning? For me, the general architecture was quite simple. I wanted to build a single central application server that pretty much does everything. I didn't want to overcomplicate it. If I need any external stuff, I just gonna set up servers that are gonna be their own deployment somewhere else, any external services or back on processes that happen on another server. I figured that out. But from the beginning, I wanted to build one central kind of monolith application. And for that, I needed to make a tech choice. The biggest choice that I made at the beginning of PodScan was to …