Business Plan and Case Studies
The Statstrade business plan describes The Prediction Network: a social network and supporting platform economy designed to deepen immersion in the places, groups and causes that shape people's identities.
The plan is built around five ideas:
- Communities shape people. People shape communities. Neither exists without the other.
- Connection has expanded in layers. Email connected people. Social media connected communities. The Prediction Network connects communities to futures.
- A future does not just happen. It gathers believers.
- Every meaningful community is trying to create a future that does not yet exist.
- Support is investment, not accountability. The language of surveillance and blame is replaced by collective belonging and shared stake.
Structured prediction is the mechanism that makes belief about a community's future visible, connects belief to reasoning and action, and gives contribution memory over time. The expanded plan also defines Statstrade as the first platform Brand, STATS as its official Token, Playable-governed wallets, tiered plan redemption, prepaid compute, a separate fundraising addon, and the platform authority needed to operate those systems safely.
The PDFs on this page are generated from the LaTeX sources under docs/business-plan whenever the documentation site is built.
Business plan
The Prediction Network
The full business plan covers mutual shaping, immersion, identity, belonging, visible belief, community participation, investment, market position, growth, tiered plans, fundraising, prepaid compute, platform governance, trust, integrity and real-world pilot hotspots.
Community case studies
North Bondi Surf Life Saving Club
A community immersion and readiness example covering patrol participation, training, volunteer referrals, contribution and recognition.
Open the North Bondi SLSC case study
Community Strong Australia
A public-accountability example covering consultation commitments, evidence, participation and published outcomes.
Open the Community Strong Australia case study
City2Surf organisers
An event-network example covering registration, training, fundraising, volunteering and sponsor recognition.
Open the City2Surf organisers case study
Australian Red Cross community readiness
A preparedness example covering local participation, practical Tasks and recognition across community partners.
Open the Australian Red Cross case study
Reckless Ben: Bricks and Minifigs accountability
An accountability example showing how predictions, evidence and public milestones can follow a disputed community outcome.
Open the Reckless Ben case study
Venture plans
Greenways App Platform
This standalone business plan describes a Base44-type AI application builder differentiated around large, long-lived applications. It covers the product experience, customer and beachhead, competitive position, pricing, unit economics, go-to-market, enabling technology, three-year operating model, funding requirement, risks and measurable decision gates.
Open the Greenways App Platform business plan
Technical and commercial papers
The Legible Build
This working paper explains why a database-first application compiler can keep an AI-built, cross-platform system possible to reason about as it grows. It covers legible source and emitted code, immediate database execution, consistency-surface mathematics, comparison with standard architectures, measurement boundaries, and product options including a reasoning workspace, semantic contract registry, verified-build service, and reusable runtime and domain packs.
Source and publication
The main document is generated from docs/business-plan/business-plan.tex. Each case study is generated from its corresponding file under docs/business-plan/case-studies/. Venture plans are generated from docs/business-plan/ventures/. Technical and commercial papers are generated from docs/business-plan/papers/.
Central CI copies the resulting PDFs into docs-gen/static/documents/business-plan/ before Docusaurus builds the production site. Broken or missing PDF links therefore fail the documentation build rather than appearing silently in production.