Legalese sucks hard (and layman-readable licenses are hard to write), but ambiguity is even worse.
Our business is to create good looking products that speed-up the development for web developers and not to go after people who use our products without a license. Probably there are 1000 people every day who just "View Source" of the page and get the product. We cannot and don't want to focus on those people :D
Licenses aren't just "ugh, we do software but we have to put up some stuff about licensing." Licenses are essential to any form of commercial software. If I base my front end on your bundle, which I paid for, I'm basing my business on your bundle. If I don't know what I've bought and what I can and can't do with your bundle, I don't know what I can do with my business. That's an absolute deal breaker. There's a reason why licenses look the way they do. This kind of stuff is incredibly hard to specify and the evaluation criteria isn't "I'm a programmer and I think I know what it means" it's "I'm a court of law reviewing how licenses have been interpreted historically for the past thousand years."
Did you pay a lawyer who specializes in software licenses to write that license? If you did, find a different lawyer. If you didn't, take down the license and your offer to let people use software you don't know how to license until you have found an actual lawyer and had them draft an actual license that is as professional as your product.
If you want a plain-vanilla license out of their law firm's files, expect it to cost a few thousand dollars to have your license prepared (mostly for the time it takes them to understand what you want). If you want an unusual or highly customized license, expect it to cost more like five to ten thousand dollars to have it prepared (because they will need to bill you for time spent writing that custom document). Licenses are hard. They are literally the contract between your business and your customers' businesses. They matter.
If you had a real license, I would have bought a pro license this morning. You don't, so all I can do is complain about it on hacker news and hope in some future life I find your site again and find a decent license on it.
How about just offering it for sale on envato under their licensing. Yes, you give up a bit of revenue because they take a cut but you don't have to pay a lawyer to draft a license for you, and you can still offer it on your own page under your own non-professionally-drafted license at the same time if you really want to do that too.
On another note, I personally see a license as one of many signs of product maturity. If there is a well established license in place, then that tells me the product is likely pretty stable and this along with other factors helps me determine if I should make the time investment to try and use that product. I think the issue here isn't whether your current users are having any problems with your license, but rather there are likely potential users who haven't even touched it because of the license. Having an explicit license is very helpful in the long run.
but honestly, tiering by license sucks. an alternative would be to make the core free open source software and, say, widget enterprise only.
That's pretty much what copyright does. However, copyright laws vary among countries. Also, like copyright a license is only as meaningful to the extent someone is willing to lawyer up and enforce it.
If I use it for a client, I've passed the client a risk because the license is non-standard. One reason for selecting a standard license is to just avoid the distraction of creating a non-standard one.
Good luck.