Agreed on all points. There are already plenty of per-seat licensing models that explicitly acknowledge bots - e.g. Perforce's "service users" (used for e.g. t

Agreed on all points. There are already plenty of per-seat licensing models that explicitly acknowledge bots - e.g. Perforce's "service users" (used for e.g. the heavy hitting CI build accounts that have more activity than dozens of engineers combined) which don't even count against seat limits. Per seat is just a way to charge roughly by organization size, which has some semi-linear correlation to SaaS usage, even if automation / "AI" adds a potentially large productivity or load multiplier. Even if "AI" somehow breaks that assumption at some point, where one engineer can reasonably use 'infinite' resources, it's pretty easy to couch usage based pricing in the veneer of seat based pricing. Just apply rate limits per user - say, high enough to handle your 95th percentile customers - and offer "virtual seats" for the power users who want to increase their API rates, or require a higher tier "enterprise" accounts - just as existing SaaSes already do, complete with public documentation of some of their API limits right on the pricing page no less.