BP-060Grade B20 supporting cases (19 counted), 0 counter-examples
Make the economics work for every node of the ecosystem, and re-price shared contracts before you outgrow them
The practice
Treat agents, partners, developers and revenue-share vendors as part of the product: monitor their economics and reliability, and re-price contracts before the business outgrows them.
Why it works
Platform and network businesses depend on parties they do not employ: cash agents, third-party developers, outsourced vendors on revenue share. If those parties cannot earn a living, they leave or cut quality, and the network weakens. Watching their economics, and not only the company's own, protects the network. Revenue-share contracts that made sense at small scale can become very expensive as the business grows; re-pricing them before then is easier than after.
KB synthesis: the mechanism is the knowledgebase's own reasoning, drawn from the member lessons. Factual support is the case claims under evidence.cases and the research under evidence.research (R-refs).
How to apply it
- Track agent and partner earnings, liquidity and reliability as core KPIs.
- Design commissions so every node earns enough to stay.
- Review revenue-share contracts against growth scenarios and re-price before thresholds are crossed.
- Watch third-party developers' and partners' economics, not only platform revenue.
Warning signs
- Agent churn or cash shortages rise.
- Partner quality complaints increase.
- Revenue-share payments grow faster than revenue.
When it applies
- Mobile money, agent banking, platforms, consoles and outsourced network operations.
When it does not
- Vertically integrated businesses with no material ecosystem.
Evidence grade: Grade B
At least 6 counted supporting cases for every 100 cases in the knowledgebase (6 × cases ÷ 100, rounded to the nearest whole number), whose primary regions span at least 4 regions.
Why this grade
Grade B by schema 4.10 route: >=14 counted cases across >=4 primary regions (the case bar is 6 per 100 cases in the knowledgebase, 235 cases). A needs a systematic, peer-reviewed study that tests this practice. None of the research cited in the KB does. 1 supporting case(s) rest only on company-reported claims and are not counted toward the grade.
Where it applies
- Transformation type
- Topic (business problem)
- Function
- Starting situation
- Industry
- Region
Supporting and counter cases
Safaricom (with Vodafone) CS-014
Nintendo Co., Ltd. CS-097
Bharti Airtel Limited (formerly Bharti Tele-Ventures) CS-057
CD PROJEKT S.A. CS-121
TOTVS S.A. CS-127
Researched and fact-checked knowledgebase · Knowledgebase built 5 November 2026
Practices, their evidence grades and case summaries are public. Full case studies are available in AXIOM to subscribers and AXIOM Discover participants.

