[7klBo4t8]

Patrick - Thank you I hadn't heard of price discrimination before. So I can internalize this by giving only one price point I'm forcing those in the market with other peoples money (above my price point) into the lowest tier plan or to take their business where a plan matches their intended use more? And those below my price point to just go elsewhere. My goal / thought was to reduce complexity at the purchase point so in the example of appointment reminder everyone signs up at the personal level and then at the next screen before payment are offered addons like "Record Custom Reminders" and more "Appointments per month" but I can see how I would be introducing more complexity then I'd be removing.

[patio11]

Your way of doing it almost certainly decreases conversion rates, but feel free to test.

The idea is that, for every transaction ever, someone has an amount of money they'll go up to for that purchase. If it costs more than that, no sale. If it costs less than that, they capture what is called a "consumer surplus." (This is micro-econ 101.) It happens to be the case that a lot of software is sold to businesses which have ways of calculating value against which all common startup software price points are negligible. Accordingly, attempting to capture some of the consumer surpluses from businesses does not leave them meaningfully worse off.

Can I give you a concrete example of how this works for Appointment Reminder? I have a particular customer whose appointments are worth in excess of $2,000 each. His actual usage of the software puts him in the $29 / month plan, but the software demonstrably makes him in excess of $10k each month. He pays $199 a month for the software, and told me that if I charged him $2k a month he'd pay it without a second thought.

It is strongly not in my interest to tell him "OK, start on the $9 plan and you can upgrade to the $29 plan when your usage goes over the limit.", because he'd never reach the higher plans. The difference in $29 and $199 is not meaningful to his business but, aggregated over similarly situated customers, it is very meaningful to mine.

[damoncali]

The problem you're having is that you're equating usage/features with value. They're not the same, or even correlated as much as you'd think. Precisely the same software can be an order of magnitude (or several!) more valuable to one customer than it is to another. You can't always use features and usage as a means by which to price discriminate, because sometimes there is literally no difference to go off of.

I run a bug tracker with one plan- $20/month. I have customers who are stretching to pay the $20 a month, and others who would easily have paid $200. Yet there is no way to tell one from another by looking at how they use the product. It's kind of frustrating. I am giving up 9 customer's worth of value because I can't figure out how to charge one of them more than $20 per month. (Actually, I can, but my billing code isn't finished yet).