In this interview segment, Xano CEO Prakash Chandran outlines the evolution of Xano's pricing and packaging strategy. He explains the four-tier model—Agency, Enterprise, Free, and a hybrid billing approach that combines seat licenses with usage. The core SKU framework is built around a "build → launch → scale" progression, anchored by a compute sandbox that customers outgrow as their needs increase. Over time, Xano shifted from a generic sandbox pricing to a more use‑case‑driven self‑serve model, tailoring compute allocations for different workloads, including AI and GPU‑intensive applications. The conversation highlights the move toward greater flexibility in deployment and pricing to match diverse customer needs while maintaining both product‑led and sales‑driven growth motions.
Chapters
you have 4 tiers. You've got an agency tier, you've got an enterprise tier, I think you have a free tier. I think you're supporting hybrid billing model where there's some combination of seats and usage. I think what is also evident is that you have a product-led motion and you also have a sales motion. And I'd love it if you could just describe the journey with pricing and packaging.
When we started, um, I think understanding where we were uniquely different from other tools on the market. Scalability was one thing that kept coming up. We decided to go with this whole notion around build, launch, scale as our different SKUs. And then your scaling requirements will rise. And we always thought, look, the lever that we have is like, we give you a compute sandbox. And then when you outgrow that, you're ready to go to the next plan and then the next plan. And so that's really what we've been running with. For quite a long time. On the self-serve side, I think what we've learned is that, um, there's actually more use case-driven ways that I think we can be pricing because a certain amount of compute may, if everyone's building an app and the goal is basically to go from zero to many different users, that might be the right way to price. But as it turns out, like people actually use Zano for different things because we're a horizontal development platform tool. And the more we understand about our users, the more we can communicate value by saying, look, we understand who you are. We understand what you're trying to build. We're going to give you the right amount of compute, even if you're doing an AI application, GPU, things that are more tailored to what you're trying to do, um, versus kind of this holistic just sandbox for you to play in. So I think, um, the evolution that we've gone through right now is like customers want flexibility in the way that they deploy, and they're also much more use case oriented. So it's, that's where we are currently in the journey on our self-serve pricing.