Default Bundle or Preinstallation¶

Distribution policy — instantiates Network Effect Bootstrapping

Places the network inside an existing workflow as the default so participants encounter it with near-zero activation effort.

Default Bundle or Preinstallation rides an existing distribution channel — an operating system, a device image, a suite, a workflow people already use — to place the network in front of participants as the default, so they are enrolled by not opting out rather than by choosing to join. Its defining move is that it manufactures an installed base through placement, not persuasion: the activation effort drops to near zero because the participant never had to seek the network out, decide to sign up, or install anything. It seeds participation by distribution rather than by curation.

Example¶

A hardware vendor launching a companion note-syncing service faces a cold start: the service is only useful once your colleagues also use it, but nobody installs an empty sync tool. Instead of marketing it, the vendor preinstalls it on every device in the enterprise laptop image and sets it as the default target for the built-in "share" action. On day one, an entire organization already has the service present and wired into the workflow they use anyway. Colleagues sharing files find the network already populated with each other — the default placement manufactured the installed base that persuasion could not. The vendor commits, though, that the default is removable and the data portable: the aim is to give the network a running start, not to trap users who would leave if they noticed.

How it works¶

Find a channel the participants already pass through. The mechanism's power is entirely in the placement — an OS, a suite, a device, a mandated workflow — so choosing a channel with real reach is the whole game.
Make the default path the path of least resistance. Enrollment happens by not acting; the network must be the pre-selected option, present before any decision.
Convert presence into use, not just installs. A preinstalled-but-unopened app is a dead installed base; the placement must land inside a workflow that actually invokes it.
Plan the un-defaulting. A default is a starting boost that must eventually justify itself on merit — the design includes making the default removable and the participant free to leave.

Tuning parameters¶

Channel reach vs. relevance — the widest distribution channel versus the one whose users actually need the network. Reach maximizes the installed base; relevance maximizes real use of it.
Default stickiness — how buried the opt-out is. Stickier defaults grow the base faster but slide toward coercion and backlash the harder they are to escape.
Removability — whether and how easily a participant can un-default and export. High removability protects trust and legitimacy at the cost of raw retention.
Bundling breadth — one tightly-integrated default versus a broad bundle. Tighter integration lifts real use; broad bundling risks resentment and antitrust scrutiny.

When it helps, and when it misleads¶

Its strength is that it beats the activation barrier more completely than any incentive can — a participant who is already enrolled has paid no activation cost at all, so a network that was un-seedable by persuasion can acquire an instant installed base.

Its danger is that the same status-quo pull that makes defaults so effective makes them ethically and legally fraught: people stay with a default far past the point of genuine preference simply because it is the default,^[1] so a sticky, hard-to-exit default shades from bootstrap into coercion — and into antitrust exposure when the channel is dominant. The classic misuse is a default that can never be removed, propping up a network that never became worth choosing. The discipline is to treat the default as a temporary boost that the network must earn out of: keep it removable, watch whether real use survives when users notice the default, and plan the graduation from "default-driven" to "chosen."

How it implements the components¶

adoption_friction_reduction — it drives activation effort to near zero by enrolling participants through placement, so joining requires no search, signup, or install.
seed_participation — the placement manufactures an instant installed base, seeding the participant population by distribution rather than curation.
transition_to_self_sustaining_governance — a legitimate default is one the network must earn out of; the mechanism includes the exit — removability and the graduation from default-driven to chosen use.

It does NOT hand-build a curated quality-checked supply layer (initial_utility_floor, participation_side_map — that's Platform Seeding) or pay ongoing per-participant incentives (bootstrap_incentive_budget — that's Cross-Side Subsidy and Early-Adopter Incentive).

Instantiates: Network Effect Bootstrapping — Default Bundle or Preinstallation bootstraps an installed base through distribution rather than persuasion.
Sibling mechanisms: Platform Seeding · Cross-Side Subsidy · Early-Adopter Incentive · Anchor User Recruitment · Standards Adoption Campaign · Compatibility Guarantee · Initial Content Library · Integration or API Tooling · Market-Making for Liquidity · Referral Loop · Staged Cohort Launch

Notes¶

The line between a helpful default and a coercive one is exit cost. A default whose removal is easy and whose real use survives being noticed is bootstrapping; a default that survives only because leaving is hard is not evidence of network value at all — it is the absence of that evidence.

References¶

[1] The default effect (a form of status quo bias): people disproportionately stick with the pre-selected option. It is what makes preinstallation so powerful and, equally, what makes a hard-to-exit default indistinguishable from coercion — the reason removability is the mechanism's ethical hinge. ↩