How Invoke AI has implemented pricing & packaging

Invoke AI uses an admin panel to manage two account types: enterprise accounts invoiced directly per contract, and self-service accounts that buy seats through Stripe. Add-ons like custom model generation require manual feature toggles, which creates operational overhead.
Chapters
Pricing has a big impact on the customer experience. Pricing is dictated by a lot of systems that you use internally. Can you just talk a little bit about how you've implemented pricing into your application? Like how does it work from a systems perspective between feature flags, entitlements, billing tools, provisioning? Can you paint a picture of how the systems work together?
Yeah. So I think we've had this conversation before too, but every SaaS company that I've ever worked at has that admin panel that you build, right? It's like one of the earliest things that you build. Built gives you some amount of like management access to set things on the account, give them extra credits or whatever, and do all that kind of stuff. So we've built that to manage both our enterprise and our self-service accounts. Our enterprise accounts are effectively like fully manually managed. They're provisioned independently or manually when a customer signs a contract. We're invoicing directly to them and managing the configuration directly. Our self-service accounts integrated via Stripe, people go through and purchase their seats and it's all kind of automated and gets provisioned dynamically as they hit the site. So that's kind of like the two dimensions that we have in the tool that designates like different account types. Our enterprise accounts, that's where we go in and actually manage individual features and entitlements based on the order form and the contract has, has been executed to have, right? So do they have this many seats? Did we give them a couple of free seats, right? Like what, what are the things that we're doing to help them get this started? What features have we turned on? What have we sold as like an add-on? For example, we have a training application and that training application is the first add-on that we've sold where customers get the studio and do all of the generation there. But if they want to like get a nice custom model generation product where you can go in and train a model, that is an add-on, right? And that's how we sell that. That is managed through that admin panel. We go in and say, okay, this is how many seats to that they have. This is the features on. And that's kind of like how we're managing that right now. It's all manually. And it's certainly a significant amount of effort to maintain and change that.
More from Fynn

Schematic at Operators Guild Demo Day 2026: How to bill for AI credits without a surprise bill

Should you move to usage-based pricing because AI is compressing your margins?

Why raising prices every year backfires (a pricing leader on the Mastercard quota model)







