The integration that ships as a default is the one that wins

Software competitions are usually decided by distribution rather than features, and the sharpest form of distribution is being the default in something people already use.

The mechanic

A capability that requires a user to go and enable it reaches the fraction of users who go and enable things. That fraction is small and does not grow much with marketing.

The same capability shipped on by default reaches everyone. The quality bar for on-by-default is much higher, which is the real cost.

Why incumbents keep winning

Not because their version is better. Because their version is present. A competitor’s product can be clearly superior and still lose to something that is adequate and already there when the user opens the tab.

This is why platform partnerships get negotiated harder than they look from the outside — the placement, not the revenue share, is the asset.

The exception worth noting

Defaults lose when the workflow they interrupt is one the user cares about enough to notice. A bad default in an area people are attentive to generates active removal and lasting resentment, and that is difficult to recover from.

What it means if you are building

The distribution question is not a go-to-market afterthought. If there is no plausible path to being switched on for someone by default, the product needs to be enormously better rather than modestly better, and “modestly better” is where most of them land.

Reported at The Verge and WIRED; analysis ours.