+1 on this comment. I think it gets to the core of corporate software policies. At my 'day job' its extremely difficult to get approval for using licensed software ... *if it is based on cpu/servers/uses*. Even if it were "free" getting the legal and administration by-in of taking on the responsibility to track, manage, account for and remit licensing information is almost impossible. It has to be sold up to the Director level as a "must have" with incredible amounts of red tape. On the other hand, I find it fairly easy to get the sign-off/approval for "developer" licensed software. Even for fairly expensive software. I can usually get approval for $500 or $1000 per-dev-seat licenses for a handful of developers with only direct management approval. This is because the accounting is simple. Even if they require "maintance" the accounting is what matters. We can "count the developers" who use something and then Mgt can put this on their buget and it slides in easily. But if I ask for a "server license" for something that has to be calculated based on # of systems its installed on, or god-forbid the # of "cores" or "processors" ... thats almost impossible. Who knows what system's the QA team is going to install this on ... and if its CPU-locked then we have to involve IT to license the computer-of-the-day. then what does "cores" or "processors" mean on VMWare systems (I hate them but IT insists on them). Its just hell and in practice almost impossible to get licensed software on these systems. So in conclusion, I think you'd be much more successful in your new licensing/product scheme if you can have the "Professional" version something that is easy to account for at a person level, not a distribution level. Make it a 'per developer' or "per site" license, maybe even based on the size of the corp if needed, but make it easy to account for. If a company has to figure out how many processors something is going to run on "in production" or figure out ways of re-using licenses for QA/DEV or for failover machines its extremely hard to justify and get through. Make it a fix fee per developer or organization and I think you'll find a lot more revenue.