This is a great article. It is a very good reminder about what to charge for things and I do need to remind myself of these things. Some additional thoughts:
If you count opensource software as a type of V4V a lot can be learned from the successes and failures of opensource business models. Would it be possible to take these lessons and apply it to any other V4V 'product'?
Here is a simple example that relates to your UI framework example. Opensource is 'friction-less'. That means, any developer can try it, and when they do, if it is a good piece of software this will end up being used in many different companies. This friction-less software will win out over any paid software because there is no purchase order required to get started and developers are free to get started with no overhead. Later if the software becomes a necessary part of the business (which it usually does) it is best to have positioned yourself to be able to 'sell' support, or 'sell' training, or 'sell' any number of things. The product is not the software, it is you.
AND
The same goes for every developer that has used your software while being paid by their company to do so, they contribute, they find and fix bugs, they become experts, and they provide value back to the project in return for the value that they also take and THEY also become the product.
This cycle can expand and expand, and I think this might be the true key to V4V is this snowball effect that is created from a friction-less experience both for the developer and the users of the software. The Microsoft loosing to Linux+Apache moment.
If this momentum could be created in any V4V, then it is very possible that it could succeed. I would need to brainstorm more how it might apply to a podcast, or other types of products V4V scenarios, but these are not my specialty. Someone could very well become the Linus Torvalds of podcasting if they figure out how to unlock this opensource effect.
I will conclude by saying, the road to opensource was also not easy at all and there were many failures and even to this day people are unsure if opensource is a good model, but I firmly believe in it and always have, always will.
cloud fodder
npub10n…ztl5h
2023-07-23 06:52:33
in reply to naddr1qq…9t38
Author Public Key
npub10npj3gydmv40m70ehemmal6vsdyfl7tewgvz043g54p0x23y0s8qzztl5hPublished at
2023-07-23 06:52:33Event JSON
{
"id": "30930d88fd5d3e46ce678f3e0678dbe1ca24d7c4442551e0746678526ba1f509",
"pubkey": "7cc328a08ddb2afdf9f9be77beff4c83489ff979721827d628a542f32a247c0e",
"created_at": 1690095153,
"kind": 1,
"tags": [
[
"a",
"30023:1bc70a0148b3f316da33fe3c89f23e3e71ac4ff998027ec712b905cd24f6a411:1689936610900",
"",
"root"
]
],
"content": "This is a great article. It is a very good reminder about what to charge for things and I do need to remind myself of these things. Some additional thoughts:\n\nIf you count opensource software as a type of V4V a lot can be learned from the successes and failures of opensource business models. Would it be possible to take these lessons and apply it to any other V4V 'product'?\n\nHere is a simple example that relates to your UI framework example. Opensource is 'friction-less'. That means, any developer can try it, and when they do, if it is a good piece of software this will end up being used in many different companies. This friction-less software will win out over any paid software because there is no purchase order required to get started and developers are free to get started with no overhead. Later if the software becomes a necessary part of the business (which it usually does) it is best to have positioned yourself to be able to 'sell' support, or 'sell' training, or 'sell' any number of things. The product is not the software, it is you.\n\nAND\n\nThe same goes for every developer that has used your software while being paid by their company to do so, they contribute, they find and fix bugs, they become experts, and they provide value back to the project in return for the value that they also take and THEY also become the product.\n\nThis cycle can expand and expand, and I think this might be the true key to V4V is this snowball effect that is created from a friction-less experience both for the developer and the users of the software. The Microsoft loosing to Linux+Apache moment. \n\nIf this momentum could be created in any V4V, then it is very possible that it could succeed. I would need to brainstorm more how it might apply to a podcast, or other types of products V4V scenarios, but these are not my specialty. Someone could very well become the Linus Torvalds of podcasting if they figure out how to unlock this opensource effect.\n\nI will conclude by saying, the road to opensource was also not easy at all and there were many failures and even to this day people are unsure if opensource is a good model, but I firmly believe in it and always have, always will.",
"sig": "033332ecba131a3afc4422d452b34b29c7f0ca764ef3d1ccca1126ef9a23988a4c8c7f59a883f61246561cffe86e41b23dfe83a0e74163e6a7d1c2a0884bd5c5"
}