I should have been more clear that I meant a linkage with revenue, which does not necessarily need to be a percentage. This helps at the high end and low end. Just quickly noodling this, I might define buckets based on revenue:
- free until revenue hits $X/mo (versus # of customers, this better tracks ability to pay)
- buckets defined as revenue of $X-$Y pays $Z
- max revenue tier is $X/mo, BUT
- pricing can go higher with more value-added services. Really common examples: SSO, Salesforce integration, QuickBooks integration, we'll call customers to find out why they churned, we'll proactively handle renewals of your customers who pay by PO (this is a PITA), and other things your $$$$$ customers will ask for.
Also: no pricing model will work for every one of your potential customers. And it's easier to lower prices than raise them.