This is the part that I pointed out generally doesn't work. I mean, tough love time: everyone wants to be paid to work on their own open source project. No one wants to pay you to do that. No one. At best, people may want your project (as part of their product, for example) and be willing to pay you (perhaps indirectly) just to know that it's maintained. This is how Linus et. al. make a living. And that's very rare -- you have to have a project that is (1) already there and valuable and (2) meets some need of a party with deep pockets willing to pay for it.
The model in your head, where you get to have total control over your project and a paycheck from it is a utopia that doesn't exist, sorry. I don't begrudge you for wanting it, I want it too. I just don't see a path to get there.
Basically, you need to choose your license carefully in order to make sure it reflects what you want to happen with your code. There is a lot of flexibility https://www.gnu.org/licenses/license-list.html#GPLCompatible...
It's thin gruel if you're operating on the "build a product, sell it to people" model. But you're not talking about building a business on this, are you? So sooner or later, you're going to wake up to the fact that nobody's going to pay you to share your toys, any more than a kid on the playground is going to get any love for wanting to play ball but also get paid rent for the glove he's providing.
But you both make a very valid point for making it open source as soon as possible. And it seems as if you have a good overview of the ways to monetize open source. Do you know how companies any of those Open Source companies ensure that none of their competitors just downloads all the source code and sells their exact same product?