Transcript
A (0:01)
You're going to have a real strong bias to this question because you are a provider of technology solutions. How does a franchisor decide whether today they should buy something or build it themselves?
B (0:20)
Yeah, that's a good question. You know, you have finite resources, both in terms of, you know, money, but also on mind share, right? So anything that you build yourself means you have to spend resources in thinking about what you want to build. And this is true also, like, you know, I use AI all the time, you know, to build applications on my own, to test them out, right? And also internally, like when you like friend Connect is a tech company. Like a lot of the SaaS products, third party products we buy, we could have built it ourselves, you know, tracking what code is built where, like some marketing automation stuff, sending emails and all. You could probably build it yourself. But the problem then becomes like, is it better for me to spend my time and money and resources into building this versus focusing on something that creates a different sheet or something that creates more, where the ROI is going to be higher, right? So it's always a decision. If you have unlimited budget, unlimited time, you know, there's no difference, right? You can build stuff by yourself because it'll be exactly what you want it to be. But the world changes, right? So what happens, like, you know, six months down the road or one year down the road, you want to make some changes to it or you want it to be different. You know, how are you going, you know, how are you, you know, who's going to own it? Like, what are you going to do? And the person who built it, if you build it internally and the person isn't there, you know, what are you going to do about it, right? So there are all of these, these pros and cons. So I'm not saying that, you know, you should never build something or you should always buy something. It's like for most organizations, given finite time, finite resources, it makes sense to buy stuff, some things and it makes sense for you to build certain things. Like that makes you know that that is uniquely yours, right? So if it's uniquely yours, maybe, you know, try to, and you think the ROI is going to be really high from you building it, then you should build it. I'll also give an example, right? With AI, like often people show these examples. You can do this. It's called vibe coding. I just go into replit, enter some text in there and it build me an email sending app, blah, blah, blah, it'll build it for you. It looks pretty cool. You can Say use Google's design and it'll even do that for you. But in the process of building it, there are two things that happen. One of the things is sometimes it'll run into an issue. When you go to the app, it'll say, hey, it doesn't do this thing that I want it to do. The app will then say, oh yeah, I see, I made a mistake, let me go try and fix it. It'll then try to fix it and then introduce another thing. Suddenly you're looking at it like, hey, you didn't fix it. But you also made this mistake over here. Like now it doesn't allow you to like click on this and drill down on it. Like when you're looking at it, it'll say, oh, you're right, this thing doesn't work. Let me go replace, I think I used the wrong module for this thing. Let me go replace it with this other library in Python and it'll explain, really. And I think I'll fix it that way, right? And then at that point you're like, okay. And then it puts this Python library, whatever it does, and it says, hey, now it works great. But then you said, okay, now I also want to do, you know, role based sign in. And then you said, when you try to log in, you say, hey, my login isn't working. Oh, this thing that I've put in here doesn't actually work with this login. I need to update the login. Like it doesn't support X, Y and Z. And you're thinking, as a developer, I've spent like one week on this thing, I'm so close. The only thing left is this little login thing. So then you tell it and you say like, hey, is there a way around it where I don't have to provide this like, you know, role based, like login whatever credentials can you, like, relax it. I can fix it later and the app will say, that's a great idea, why didn't I do it now? And then later on you can fix it. I build the app, I publish it, I tell all my colleagues, hey guys, I built this amazing app that's available that does this thing and people love it. But what they don't realize is that I have put a security thing deliberately in there to just get this thing to work. Because the criteria that I originally put on access control was too hard for this app to implement it, I had to rebuild it all over again. So it's done and it's available. And so there are many examples of where you know, these, like shortcut, like AI allows you to take these shortcuts, you do these shortcuts and it's there and you don't see it until much later. That's why I call this like the last mile problem.