BP-076Grade C6 supporting cases (6 counted), 1 counter-example
Fund network businesses for the build-out, and judge them by usage and density rather than early revenue
The practice
For businesses whose value depends on a network of users, agents or locations, secure capital matched to the build-out horizon and measure progress by active use and demand per location, not by early revenue or registrations.
Why it works
Network businesses earn little until density makes them useful, so early revenue understates their prospects and registrations overstate them. In the supporting cases a mobile-money service lost money for years before profit, a parcel-locker network earned about €500 a month after two years before becoming its owner's core, and a telecom entrant built usage before raising price. In each, the owners or investors could wait because the evidence they watched was usage and demand for more locations, and the capital they had was patient.
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
- Choose investors whose horizon matches the time to density; agree milestones in usage, not profit, for the build-out.
- Report active users (for example, 90-day active) and demand per location alongside revenue.
- Add locations where customer requests and usage are highest.
- Set a dated test of the usage curve, with a stop rule if it does not bend.
Warning signs
- Growth reported only in registrations.
- Pressure for early profit that would stop expansion of the network.
- Usage per location flat as the network grows.
When it applies
- Mobile money, payments, lockers, marketplaces, telecom and other networked services.
When it does not
- Products without network effects, where early revenue is the right test.
- Markets where the need the network serves is already met (see the counter-evidence in CS-116, where M-Pesa was closed in South Africa).
Evidence grade: Grade C
Anything below B. Plausible, but not yet tested in the KB at the B bar.
Why this grade
Grade C by schema 4.10 route: below the B bar of 14 counted cases across 4 primary regions (6 per 100 cases in the knowledgebase, 235 cases). B needs at least 14 counted supporting cases across at least 4 primary regions; this practice has 6 counted case(s) across 5 region(s). A needs a systematic, peer-reviewed study that tests this practice. None of the research cited in the KB does.
Where it applies
- Transformation type
- Topic (business problem)
- Function
- Starting situation
- Industry
- Region
Supporting and counter cases
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.

