Usage-Based Pricing for Internal Tools

Diving deeper into

Abhishek Nayak, CEO of Appsmith, on building an open source internal tool builder

Interview
The idea behind the usage-based model is that it's a shared risk model.
Analyzed 4 sources

This pricing model turns Appsmith from a software vendor into an adoption partner. The company gets paid mainly when support agents, ops staff, or other business users actually spend time in apps built on the platform, not when engineers merely install it. That directly addresses the biggest pain point in internal tools, which is that many seats get bought in advance but only a fraction of employees ever use the software enough to justify the spend.

  • Appsmith prices usage at $0.40 per user hour, capped at $20 per user per month, and says most revenue comes from business users of finished apps rather than the engineers building them. That makes expansion depend on real workflow adoption inside teams like support and customer operations.
  • This is a direct contrast with seat based internal tool vendors. Retool’s per seat model helped it scale to $82M ARR in 2022, but it also created friction around sharing because viewers and creators were charged similarly, which limited product led expansion across large orgs.
  • The comparison with Airplane shows why this matters. Airplane also acknowledged pushback on uniform seat pricing and expected to add usage based elements over time, especially for scheduled jobs and uneven product use. That suggests Appsmith identified a real structural weakness in seat pricing for internal tools.

The category is moving toward pricing that matches actual work done inside internal apps. As more deployments spread across large companies with thousands of occasional users, the winners are likely to be platforms that monetize active workflows, not just provisioned accounts, because that keeps procurement easy at the start and expansion strong once usage becomes habitual.