The two options aren't "the original owner releases a new layer on top of his service" and "no such layer can exist". That's the whole point of white-labeling, and I doubt cperciva would mind people releasing layers that use his service as a backend, in the same way he releases a layer that adds value to Amazon's storage.
He wouldn't be giving away any value, somebody else would be starting a company that happened to pay him for service.
He wouldn't be giving away any value, somebody else would be starting a company that happened to pay him for service.
If he wouldn't be giving away value, then how could there be enough margin for said company to survive? The point of white-labeling is to let other people build solutions outside of your core competency, using your system effectively as a commodity.
For someone like cperciva, that would be giving away an awful lot of value to people whose sole contribution would be marketing and extremely high-level software development.
He should hire to fill this gap, not give away his margins to marketing suits.
Comments
The two options aren't "the original owner releases a new layer on top of his service" and "no such layer can exist". That's the whole point of white-labeling, and I doubt cperciva would mind people releasing layers that use his service as a backend, in the same way he releases a layer that adds value to Amazon's storage.
He wouldn't be giving away any value, somebody else would be starting a company that happened to pay him for service.
If he wouldn't be giving away value, then how could there be enough margin for said company to survive? The point of white-labeling is to let other people build solutions outside of your core competency, using your system effectively as a commodity.
For someone like cperciva, that would be giving away an awful lot of value to people whose sole contribution would be marketing and extremely high-level software development.
He should hire to fill this gap, not give away his margins to marketing suits.