Pay for a recurring task
Explore team or individual plans only if reviewable briefings save meaningful effort or improve output quality. Compare willingness to pay with the participant’s current tools and budget.
Prioritise the EX Insight subscription hypothesis: identify the buyer, test recurring value and measure delivery costs before pursuing additional revenue paths.
The initial commercial hypothesis is an EX Insight research subscription for editors and small research teams. Price, packaging and demand are to be tested; this is not an announced paid service.
Explore team or individual plans only if reviewable briefings save meaningful effort or improve output quality. Compare willingness to pay with the participant’s current tools and budget.
Proposed acquisition: direct conversations with editors and research teams, a scoped briefing demonstration, then an opt-in pilot. Measure continued use before considering broader media distribution.
Model subscription income as paying accounts × realised price. Account for data licensing, inference, hosting, review and support costs before estimating contribution margin. No financial forecast is presented as achieved.
A bottom-up market estimate should use the reachable target segment and evidenced annual spending, with dated sources and explicit assumptions—not total global sports audiences.
The longer-term model keeps several options open without assuming they will mature together. Each option has a separate customer, cost structure and readiness decision.
Proceed when multiple use cases require the same fields and delivery contract. Validate licensing, workload, support and acceptance criteria before quoting access or integration fees.
Any transaction-fee hypothesis depends on eligible activity, sustainable liquidity and operating costs. A website demo does not establish a live venue or fee income.
The first subscription hypothesis stands independently of EXT. Evaluate membership, points and tokens against a concrete product need; do not treat token demand as evidence of software demand.
EX Group’s planned model connects individual software access, partner distribution, enterprise infrastructure and market services. Each revenue stream answers a different customer need while drawing on common data, model and operational capabilities.
EX Insight can provide recurring access to advanced intelligence, briefings, alerts and professional analytical workflows.
Partners and professional teams can access structured data, model outputs and integration support through usage-based services.
Where available, transaction and ecosystem services can connect revenue to participation and market infrastructure use.
The sequence begins with intelligence use cases before broader infrastructure is introduced.
Test whether users return for better context and decision support.
Embed intelligence in existing products and professional workflows.
Release market services where product and compliance readiness permit.
Reuse data, models and controls across new customer channels.
The long-term model depends on common services reducing duplication as interfaces, customers and distribution channels expand.
“The model scales from individual intelligence subscriptions to enterprise infrastructure relationships.”
Recurring access to advanced intelligence tools creates a durable software layer.
A subscription proposition must connect price to a useful recurring task, such as research depth, update needs or team workflows. Product packaging, retention and cost to serve would need validation before recurring revenue can be treated as established.
Exchange activity supports transaction-based economics aligned with platform participation.
Transaction economics depend on eligible activity, actual liquidity and the costs of running the service. Fee schedules and partner arrangements would need to be published or agreed separately; this page does not announce trading volumes or fee revenue.
APIs and ecosystem capabilities extend the platform into partner products and institutional workflows.
Enterprise value may come from usable data, integration support and dependable delivery. A commercial discussion should define licensed uses, expected workload, support responsibilities and acceptance criteria before agreeing scope or pricing.