Editors and research teams
People who repeatedly check fixture context, player availability and changing reports before producing a briefing. Their frequency of use and willingness to pay still need validation.
EX Group starts with EX Insight: a proposed research workflow for sports editors and analysts, turning scattered pre-match updates into a source-linked briefing. Market infrastructure remains the longer-term direction, built on product evidence.
A match is more than the final score. Lineups, injuries, recent form and the timing of each update can change how an event is understood. When these inputs sit in separate feeds, the same question can produce several incompatible answers.
The first proposed task is a pre-match brief: fix the event and information cut-off, preserve sources and distinguish confirmed facts from unresolved claims. The pilot would compare this process with the editor’s current workflow, not assume that a polished summary proves better research.
The proposed sequence starts with EX Insight and one recurring research task. Distribution and APIs follow only if the workflow is useful and repeatable. EX Sport and EXT remain separate expansion decisions, not three simultaneous launches.
Shared data definitions make these layers easier to connect, while separate access rules and operating boundaries keep each product understandable on its own. An intelligence user does not automatically become a market participant or need to hold a token.
Test a recurring research task with an Insight pre-match brief.
Explore partnerships and APIs after repeatable, viable delivery.
Assess demand and operating requirements separately for Sport and EXT.
Built as independent products. Designed to become more valuable together.
First priority: a source-linked pre-match brief for editors and researchers. Test source accuracy, review effort and repeat use before expanding into advanced model comparisons or enterprise delivery.
Explore InsightA later market-infrastructure concept covering outcome rules, order-book visibility and resolution records. Any live service would depend on independently assessed demand, operating readiness and applicable requirements.
Explore EX SportA utility-led ecosystem layer for access, incentives and participation across EX products—introduced only as products and controls become ready.
Explore EXTA probability is the beginning of a question, not the end of an analysis. EX Insight is designed to place the estimate beside its source context and a comparable market view, so a difference can be investigated instead of simply acted on.
In this fictional example, 52% and 47% differ by five percentage points. A useful review asks whether the outcome definition, timestamp and information set match—and whether new information would change either view.
See the intelligence platformIllustrative interface only. Not live data, a recommendation or an indication of future results.
The proposed pilot focuses on sports editors and researchers preparing pre-match coverage. The task is to reconcile scattered updates into a source-linked briefing—not to provide a betting recommendation. The first competition and data sources would be agreed before a pilot.
People who repeatedly check fixture context, player availability and changing reports before producing a briefing. Their frequency of use and willingness to pay still need validation.
Fix the event and cut-off time, preserve the source for each claim, flag conflicting reports and separate confirmed facts from interpretation.
A concise summary, source list, unresolved questions and revision notes. The pilot would test whether this reduces checking effort without sacrificing accuracy.
This is a proposed pilot scope. The current website shows illustrative interfaces, not a connected research service or verified customer results.
The reference architecture separates data ingestion, model evaluation, market services and product access. This lets each layer be examined against its own responsibilities, rather than treating intelligence, execution and security as one opaque system.
Reliable operation begins with practical questions: where did an input come from, which version produced an output, who may use it, and what should happen if a dependency fails? These questions guide the design; they are not a claim of certification or a published service guarantee.
Explore our technology
More signals are useful only when they improve an observable outcome. The proposed feedback loop connects event records, model estimates and market context, then evaluates where the information is timely, consistent and helpful to a real workflow.
Model updates should be tested before they are adopted. Product signals should be used only within appropriate permissions and privacy boundaries. Network effects are therefore a development hypothesis to validate, not an automatic consequence of collecting more data.
Explore the data networkStart with one recurring task for sports editors and researchers, rather than every audience at once.
Test source accuracy, review time and missed information; an interface example is not product evidence.
Assess repeat use, willingness to pay and the cost to deliver the product together.
Use evidence to decide on APIs, market services and ecosystem mechanisms—not simultaneous launch assumptions.
Agree the pilot task, data rights, sample input and manual-workflow baseline.
Build and assess a source-linked research prototype with revision records.
Review use, willingness to pay and delivery cost; continue, refine or pause.
These proposed windows start from an agreed pilot kick-off, not today. They depend on data rights, staffing and scope. The 3–6 month follow-on is conditional on useful results; no completed milestones or release dates are claimed.