Pokemon Pricing - let me know how you do it?

Okay, so the Pokemon catchphrase 'Gotta catch 'em all' sums up this problem:

Some pricing models inhibit the natural expansion volume of the customers - e.g.:

We sell factory locations, but customers start with 1 factory and grow slowly from there.
We sell 10 users... but every customer have 100+ potential users.
We price per patient... but only get to handle patients of type A, not types B and C.

The simple example-fix is to price per number of employees (a volume outside the control of the customer) instead of per user (a volume controlled and reduced by the customer)... but what other ways have you guys used to solve the share-of-wallet problem?

Asking for a friend 😉

5 comments