What drives team upgrades in Retool and what features trigger the process?

The big feature that people upgrade to the Business plan for is granular access control, so they can give somebody view-only access to an app. The Business plan also has audit logs, but those are only really important for larger use cases.

With the Enterprise plan, the big draw was deploying on-prem. If you want to deploy on-prem—before Retool started doing self-serve on-prem—you need to upgrade to the enterprise plan. 

You also need to upgrade if you want to do SSO other than Google—so if you want to integrate with Okta or Active Directory or anything like that—or if you want to integrate Retool with Git and make sure any change to an app is version controlled.

Those were the really big ones. There's some other things in the pricing page they talk about, like custom branding, which is nice—but not that important.

To go back to the self-serve on-prem concept, what that lets you do is deploy Retool on your own servers without talking to a salesperson.

Every piece of open source software on the planet lets you do that, but very, very few  SaaS businesses do the same. Confluence let you do it for a while, but they stopped.

Adding self-serve on-prem was basically about adding another degree of price discrimination—to where there are people who need to deploy on-prem for various reasons, but they're not really relevant for the enterprise plan, so we just decided to separate those two out.