Xano works best as a supporting tool in your stack, not the main platform. When it plays a supporting role, users pay more and outcomes improve. The speaker recommends it to friends building software packages for exactly this reason.
But the, uh, but the, the way I describe it is I want to be important but not central. And I think that's going to be where you actually wind up, you know, having a greater willingness to pay, and that's where there's better economic benefit. Um, so that's why I talk to people when they're building their software packages, but it's also kind of where I recommend my friends over at Xano. I think that the, the, the best stuff about it is when they're— when they can be that supporting player, you know, getting things out to where they need to go. And where Zano has gone most off the rails is when they are trying to be the central character. And like, I, I call it Zano for X versus X for Zano. Zano for X, fantastic stuff.
