Using network effects (not patents) to build defensible software
builtbykrit.com
builtbykrit.com
Which is why I now need an account to play games or work with photoshop, why we have "smart" light-switches that need to talk to their platform to turn on the light half a meter away and why there are half a dozen isolated messenger services instead of a single federated protocol (not even starting with "smart home" systems).
However the article is a good summary of all the reasons that will cause companies to pursue network effects and the signs you can watch out for to spot them.
And I think a lot of people look at network effects right now primarily as a growth lever, but wouldn't think to use them (when they're working) as an argument with investors that their product is defensible.
Of course an opponent with stronger budget and marketing doing the same thing reaaonably well will extinguish or coopt you network. Or buy you off (which might be the desired game plan).
Users then end up paying for suddenly disappearing or closed of network.
I'm also not entirely sure how it connects to "defensible" software. The ability to set a standard so that you're able to build that audience that you need for a network effect to kick in is difficult, and is typically rare. It might serve well in a small niche market, but you'll be unlikely to expand past that market with out getting scooped by one of the bigger competitors.
I'm curious to learn how it's supposed to offer protection in the current environment.