Just like the last proposal, I have no problem with what you've come up with.
But the lack of an .exe exporter means it's a no for me.
It also means it's not worth me taking up the early-adopter option, because without the guarantee of an .exe exporter, I'd be wasting my time.
I'm also not a fan of commercial non-official plugins/exporters.
Money's not a problem, in any amount, I just think that (a) you need to keep your revenue streams future-proof, and (b) people need to get value for money from their official purchase.
None of my questions were answered in the last thread, but here goes anyway:
How come you haven't come up with license upgrade prices?
It doesn't have to be complicated.
Just allow people to pay the difference.
We're not talking physical goods here, so there's no depreciation value to be factored in.
The "ALSO-" section could look like it only applies to the Pro license the way you've posted it (I assume it applies to all licenses), so you may want to point that out a bit more clearly.
Again, it's all pretty irrelevant to me while there's no .exe export.
The projects that I'm working on involve Unity, Construct 0.x, and Java, so maybe when I'm done with those, Construct 2 will be worth looking at (for the reason I've stated several times already).
The problem is, I may well be more than happy with the toolset that I've used to make those, and may not choose to add another.
I fear you may push away other Construct users without the inclusion of an .exe exporter early on too.
Just my opinion.