Sign up to save your podcasts
Or
Share How AI Is Making Software Risky (Thanks, Vibe Coding)
Share to email
Share to Facebook
Share to X
Share to email
Share to Facebook
Share to X
Or
How AI Is Making Software Risky (Thanks, Vibe Coding)
New apps are popping up in the photo booth space faster than I can keep up with.
And the pitch is almost always the same: I couldn't find a solution that worked for me, so I built one. And now you can have it too.
Sometimes that's exactly what it is. A founder who solved their own problem and wants to share it. That part is genuinely cool, and I'm not here to knock it. But there's a whole other side to this that nobody in our industry is actually talking about. The side that could put your business and your clients at risk before you ever see it coming.
This episode isn't about how to use AI in your business. That's a different conversation for a different day. This one is about the software AI is helping people build, the stuff landing in your inbox and getting passed around in the groups, and the questions you need to be asking before you hand over your data.
Because here's the thing. The moment you start loading client information into a tool, names, emails, phone numbers, photos, videos, you've taken on a level of responsibility that most people never stop to think about. And if the app running your business has no privacy policy, no terms and conditions, and no real infrastructure underneath it? That responsibility lands on you when something goes wrong.
And something always goes wrong eventually. That's just software.
What you'll learn in this episode:
What "vibe coding" actually is and why it's showing up everywhere in our space right now
What a full stack app means in plain English and what's usually missing from the tools being sold to us
The four things real software has that vibe-coded apps almost never do: error reporting, security, data backups, and staged updates
What "spaghetti code" is and why it matters when something breaks on a Saturday night
The exact questions to ask any software vendor before you hand over your client list
What a good answer sounds like versus a bad one, and how to tell the difference without being a tech person
Why the software you choose becomes a sales decision, not just an operational one, when you're going after corporate clients
The difference between building tools for yourself and selling them to others, and why that line changes everything
Why your photo booth business insurance does not cover you the moment you start selling an app you built
Which companies in our space are building it the right way and what actually makes them different
Resources Mentioned:
Your Next Steps:
View all episodes
By Catalina BlochNew apps are popping up in the photo booth space faster than I can keep up with.
And the pitch is almost always the same: I couldn't find a solution that worked for me, so I built one. And now you can have it too.
Sometimes that's exactly what it is. A founder who solved their own problem and wants to share it. That part is genuinely cool, and I'm not here to knock it. But there's a whole other side to this that nobody in our industry is actually talking about. The side that could put your business and your clients at risk before you ever see it coming.
This episode isn't about how to use AI in your business. That's a different conversation for a different day. This one is about the software AI is helping people build, the stuff landing in your inbox and getting passed around in the groups, and the questions you need to be asking before you hand over your data.
Because here's the thing. The moment you start loading client information into a tool, names, emails, phone numbers, photos, videos, you've taken on a level of responsibility that most people never stop to think about. And if the app running your business has no privacy policy, no terms and conditions, and no real infrastructure underneath it? That responsibility lands on you when something goes wrong.
And something always goes wrong eventually. That's just software.
What you'll learn in this episode:
What "vibe coding" actually is and why it's showing up everywhere in our space right now
What a full stack app means in plain English and what's usually missing from the tools being sold to us
The four things real software has that vibe-coded apps almost never do: error reporting, security, data backups, and staged updates
What "spaghetti code" is and why it matters when something breaks on a Saturday night
The exact questions to ask any software vendor before you hand over your client list
What a good answer sounds like versus a bad one, and how to tell the difference without being a tech person
Why the software you choose becomes a sales decision, not just an operational one, when you're going after corporate clients
The difference between building tools for yourself and selling them to others, and why that line changes everything
Why your photo booth business insurance does not cover you the moment you start selling an app you built
Which companies in our space are building it the right way and what actually makes them different
Resources Mentioned:
Your Next Steps: