Not to mention in companies that just acquire other companies, the parent company has a lot of revenue, but the sub-companies can be chronically cash-strapped.

Not to mention in companies that just acquire other companies, the parent company has a lot of revenue, but the sub-companies can be chronically cash-strapped. In big companies (and conglomerates) any given product does not draw from the total financial resources of the entire organization and its various revenue streams. A single megacorp product can have a 250K budget and generate 500K revenue, but they're not gonna get any more money for their product development just because the megacorp makes more money outside that product. And that revenue is probably just gonna get stolen by the megacorp to use somewhere else, the money doesn't go back into improving the first product. And what's the purpose of this license? Is it to generate revenue for the developer? If so, you want your terms to invite more liberal use by larger companies, as they may start using your project in more and more of their products which will net you more and more revenue. If it's too expensive for one of their products, it's too expensive for all of them. The best way to get a large company "hooked" on your project is to provide an initial term of free use, like 6 or 16 months, and to track use remotely via metrics gathering ("checking for upgradeable versions on start-up"). Once they've used it for free long enough, you go and ask (politely) for your money. If you price right, it'll be cheaper for them to pay you than to remove your project.