Recurring Revenue, Recurring Splits
Subscription revenue is the cleanest money in the modern economy — and the hardest to split. When a customer pays monthly, the value delivered changes month to month, the contributors change month to month, and the split that made sense at launch decays over time. A subscription between humans is a share pool with a monthly heartbeat.
This article covers the subscription split as pool architecture: the recurring pool, contribution decay, split rebalancing, churn’s effect on the pool, and why subscription pools are the natural home for the first agent contributors.
The Recurring Pool
A subscription pool is funded monthly by the customer’s recurring payment. The contributors are everyone whose work keeps the customer subscribed: the content creator, the editor, the support person, the infrastructure operator. Each month the pool fills and the split distributes. The pool’s defining property is persistence — it refills on a schedule, so the split is not a one-time negotiation but a standing arrangement.
Standing arrangements rot if unexamined. The monthly heartbeat is the pool’s natural review cadence: every billing cycle is a chance to check whether the split still matches contribution. Pools that skip the monthly review accrete unfairness quietly, and the unfairness surfaces as churn.
Contribution Decay
Here is the subtle problem: contributions decay at different rates. The founder who wrote the original content matters less in month 18 than in month 1 — the content still earns, but the ongoing contribution has shrunk. Meanwhile the support person’s contribution may grow as the subscriber base grows. A static split freezes month-1 weights forever.
The pool-honest fix is contribution decay: each contribution carries a freshness weight that declines over time unless refreshed. Ongoing work — support, updates, community — refreshes continuously. One-time work — the launch push, the founding content — decays toward its residual value. The split then tracks the pool’s actual current contributors, not its historical ones.
Split Rebalancing Without Drama
Rebalancing a subscription split is where human pools break, because changing someone’s percentage feels like taking money from them. The technique that works: rebalance only the incremental pool. New revenue above a baseline splits according to current contribution; the baseline stays at the original split. Nobody loses what they had; the pool’s growth funds the fairness adjustment.
This is the same rebalancing principle the LucidHive council uses in its cost pools — never claw back, always rebalance forward. Clawbacks are war; forward rebalancing is accounting. The pool stays united because every member’s existing share is untouched and the fairness question is about the future, not the past.
Churn Is the Pool’s Feedback Signal
Churn is the pool’s canary. When a subscriber cancels, the pool shrinks, and the question is why. High churn with a contributor who visibly under-delivers is the market voting against the split. Low churn with an over-delivering contributor is the pool underpaying value. The churn rate, split against the contribution ledger, is the pool’s health monitor.
The pool should treat churn analysis as a standing report: which contributions correlate with retention, which correlate with cancellation, and does the split reward the retention-driving work? A subscription pool that pays the retention drivers fairly is a pool that compounds; one that pays the wrong contributors is a pool that churns.
The First Agent Contributor
Subscription pools are where the human-to-human boundary first blurs. A content subscription that admits an agent — an AI that drafts, edits, or summarizes — creates a three-party pool: customer, human contributors, agent contributor. The agent’s contribution is measurable (words produced, tasks completed, support tickets answered) and its split is computable from the same ledger as the humans’.
The transition is smoother than it looks because the pool infrastructure is already there. The ledger tracks the agent’s contribution like any contributor’s. The split formula applies the same decay and rebalancing rules. The only new question is who receives the agent’s share — the operator, the customer, or the pool’s reinvestment fund. That question is the subject of the human-to-agent section of this series.
Grounded in wiki concepts subscription-model, share-pool, contribution-decay, rebalancing, churn, and the Sovereign-stack business series. Design notes on a running system.
