Expo offers both usage-based and annual pricing because different customers need different things. Some want flexibility and pay month-to-month; others need predictable budgets and pay upfront. For Workflows, they let customers start flexible, figure out how much they use, then switch to annual pricing once they know their patterns.
Chapters
It kind of gets back to what the customer needs. And we've had a lot of conversations with organizations who really value flexibility and they want usage-based pricing. They want to pay for what they use month to month. And then we have organizations that do an annual budgeting process and they can't go back to that budget mid-year and say, I need more because we didn't plan our adoption correctly. We actually used way more. They also don't want to. Under, uh, purchase and not use what they're actually purchasing upfront. So there's a predictability versus flexibility trade-off that we're also trying to help the enterprise customers. It's super easy to just say, put your credit card down, pay for what you use. We're balancing some of this out by doing both too. And it kind of depends on the product. So we have a product called Workflows. Workflows are effectively charged by minutes. Minutes, and we have some organizations that want to pay upfront for those minutes and we'll do a credit drawdown model. But some companies aren't entirely sure how many minutes they're going to consume, especially with new apps. So what we're doing with them is we'll put them on an enterprise contract. We'll put all our products annualized upfront, and then we'll actually have workflows be usage-based. So this allows us to establish a baseline for that product. The customer starts to get the flexibility initially, which they value, but then as they understand the usage patterns in the app. Then we can set something more predictable or annual-based. That's very, very consistent and easier to understand when you're planning something with finance.
