EX Insight
Review a fictional brief and its source records.
EX Group starts with EX Insight: a proposed pre-match research tool for sports editors and analysts. Explore a sample brief with sources, open questions and revision notes.
Review what is available today, then explore the next phase.
Last reviewed:Review a fictional brief and its source records.
Explore the simulated market experience.
Check the published scope and utility status.
Lineups, injuries and changing reports can tell different stories about the same match. A useful brief keeps each claim tied to its source and update time.
The proposed pilot brings these updates into one reviewable brief, then compares the checking effort and accuracy with the editor’s current workflow.
Start with one useful research task in EX Insight. Evaluate distribution and APIs after repeat use; EX Sport and EXT remain separate, conditional next steps.
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.
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.
Built as independent products. Designed to become more valuable together.
Swipe to explore the three product directions
3 source records · 1 open question · 2 revisions
The first product focus: a pre-match brief that keeps sources, unresolved claims and revisions together for editorial review.
Explore InsightA later market-infrastructure concept for outcome rules, order books and resolution records, subject to demand and operating readiness.
Explore EX SportA utility-led ecosystem layer for access, incentives and participation across EX products—introduced only as products and controls become ready.
Explore EXTProbability comparison is a later research direction. Compare estimates only when they use the same event, outcome definition and information cutoff.
Here, 52% and 47% differ by five percentage points. The gap prompts a review of assumptions and sources; it does not establish a return or an advantage.
About EX InsightIllustrative interface only. Not live data, a recommendation or an indication of future results.
The reference architecture separates data ingestion, model evaluation and product access, so inputs, outputs and responsibilities can be reviewed independently.
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.

Feedback can highlight missed updates, unclear sources and repeated work. Use these findings to test whether the next version improves the research task.
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.
Start 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.
Swipe to explore the proposed stages
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.