Mutualism
Mutualism is the arrangement where two entities combine efforts to produce value. The user brings real-time energy, attention, and intent toward something they're trying to accomplish; the team brings work designed and built in advance, absorbing complexity the user would otherwise handle themselves. Both contributions are necessary, and the team's prepared work is what makes the user's live energy go further than it otherwise would.
Definition
Mutualism is the configuration in which user value and business value is produced jointly by the user's real-time activity and the provider's pre-recorded work, with neither contribution sufficient on its own.
The two contributions
The user contributes energy, attention, and intent in real time. They arrive pursuing some sought state — already in motion, under their own steam, for reasons predating the offering — and bring metabolic and motivational resources to the traversal. The provider contributes pre-recorded work: design, engineering, and content built in advance, absorbing complexity the user would otherwise pay for in real-time effort. The provider's structural advantages (full attention to the design problem, full context across users, time to absorb complexity) get spent up front so the user's in-the-moment energy goes further than it would unaided. Both contributions are necessary, and neither produces the result alone.
Energy flows one way
The offering doesn't generate user energy; it interacts with energy the user already has and makes that energy more efficient toward the state being pursued. The flow is unidirectional — user → through the offering → toward the sought state. This rules out a class of design moves that try to substitute provider energy for user energy: motivational copy meant to make uninterested users care, gamification meant to manufacture engagement on top of an absent pursuit. Those produce thin engagement that fades the moment the prop is removed, because there's no underlying pursuit they're efficiency-improving.
Margin-on-efficacy fits the configuration
The provider captures margin on the improvement in the user's route efficacy — the delta between what the user could achieve without the offering and what they achieve when integrating its affordances into their pursuit. Capture attaches to the delta, not to the affordances themselves. The user keeps the value of the pursuit (the pursuit is theirs, in service of their sought state); the provider's capture is honest because it's priced against an improvement the user wouldn't have gotten otherwise. Margin-on-efficacy is the form of value capture that fits mutualism — and subscription, the canonical activation-era capture form, requires ongoing efficacy delivery against ongoing payment.
Parasitism as the alternative
Parasitism is the configuration where the user's pursuit gets redirected into engagement that doesn't deliver the state they came for — variable-reward loops, novelty-seeking, attention capture substituted for the sought state. Parasitism misdirects the energy flow rather than reversing it: the user keeps spending energy on the offering, but the energy isn't producing the value they came to produce. The framework's apparatus is built to optimize the mutualistic engine; applied to a parasitic offering, it optimizes the wrong engine — metrics read as if value is being produced while the user's energy is being captured rather than served. Mutualism is the only configuration that runs sustainably in self-serve SaaS at scale, because the user has to stay motivated to produce both their own value and the commercial capture the business depends on.
Example
A SaaS analytics tool at the signup cohort level. The provider has built the app — pre-recorded engineering, design, content. A user signs up because they want to understand their conversion funnel; they bring intent, time, and attention to setting up dashboards. Value gets produced when the user actually understands their funnel, and that production requires both sides: the user's traversal (writing queries, reading charts, drawing conclusions) and the provider's affordances (the data pipeline, the chart library, the templates). Subscription captures margin against the delta between what the user could do in a spreadsheet and what they get with the app. Neither side alone produces the value: the app sitting idle produces nothing; the user without the app produces a worse version of the same understanding, more slowly.