EX Insight
Research example available
Read the sampleReview a fictional brief and its source records.
ROADMAP
/ 10
Define. Test. Decide what comes next.
A proposed three-month Insight pilot pairs each deliverable with a review gate. Longer-term expansion follows evidence rather than a fixed launch calendar.
01SCOPEBaseline
02TESTPrototype
03REVIEWDecision
Proposed pilot sequence · not completed milestones
AVAILABLE TO REVIEW
Project progress and public deliverables
Review what is available today, then explore the next phase.
Last reviewed:EX Sport
Simulation available
View the demoExplore the simulated market experience.
EXT
Icons and official resources available
Official resourcesCheck the published scope and utility status.
Website and public resource updates
Official resources in one place
Logo downloads, the project contact and published information are grouped on the EXT page.
EXT icons published
The original 32 × 32 SVG and 64 × 64 PNG are available through direct public links.
Research example available
A fictional pre-match brief demonstrates source records, unresolved questions and revision history.
These records cover public resources and demonstrations. Pilot results, revenue and team experience will be disclosed separately when verified.
01Scope and baseline
02Prototype and evaluation
03Pilot review and decision
A deliverable and a decision at every step.
Indicative windows below start from an agreed pilot kick-off, not from this website’s publication date. Timing depends on data access, people and scope; these are targets, not completed work or release commitments.
Agree the task and baseline
Proposed deliverables: participant needs, one agreed competition, a rights checklist, sample input and a manual-workflow baseline. Gate: usable data permission and agreed review criteria; unresolved rights stop the data-dependent work.
Build a narrow research prototype
Proposed deliverables: source-linked briefing, uncertainty handling and revision records. Gate: replayable examples assessed for source accuracy, missed information and time to review against the agreed baseline.
Review use and willingness to pay
Proposed deliverables: permissioned pilot feedback, usage findings, delivery-cost estimate and a pricing discussion. Gate: decide whether to refine, continue or pause using criteria set at kick-off—not a preselected success story.
Months 3–6 are a conditional follow-on: only a useful, repeatable workflow would justify additional coverage or an API pilot. EX Sport and EXT keep separate readiness gates.
Explore longer-term direction and supporting detail
MILESTONES, GATES AND DEPENDENCIES
Progress depends on evidence of readiness—not calendar dates alone.
The roadmap moves from product validation to distribution and then infrastructure scale. Data quality, model performance, security, partnerships and applicable requirements form stage gates between phases.
01
Research validation
Test a source-linked EX Insight briefing against a defined user task before expanding product scope.
- Task and baseline
- Briefing prototype
- Pilot evaluation
02
Repeatable distribution
Evaluate additional coverage and integrations only when recurring use and delivery costs support them.
- Coverage decisions
- Partner pilots
- Delivery economics
03
Infrastructure options
Assess API services, market operations and ecosystem utility as separate readiness decisions, without a fixed launch year.
- API readiness
- Market requirements
- Utility assessment
HOW IT WORKS
The gates between phases
Timing and scope can change as product evidence, data availability, partnerships and jurisdictional requirements evolve.
01
MODEL
Intelligence quality
Evaluate calibration, error and usefulness in real product workflows.
02
PRODUCT
Engagement evidence
Look for repeat use, retention and clear customer value.
03
DATA
Rights and coverage
Confirm data availability, permitted use and partner readiness.
04
CONTROL
Operational readiness
Review security, reliability, legal and compliance dependencies.
EX PRINCIPLE / MILESTONES, GATES AND DEPENDENCIES
A forward-looking product roadmap.
Targets are directional and may change based on validation, partnerships, operational readiness and applicable requirements.
WHY IT MATTERS
“Each phase builds the operating capability required for the next—product before expansion, network before scale.”
CORE CAPABILITIES
What each stage is intended to unlock.
01
First · Research validation
Validate a narrow EX Insight research workflow before broader product work.
The foundation phase should validate a coherent research experience and a clearly explained market demo. Useful evidence includes user feedback, data-quality checks and the ability to trace an example from input to output; these are intended milestones, not completed achievements.
- Task definition
- Source-linked prototype
- Pilot evaluation
02
Then · Repeatable distribution
Explore additional coverage and partners only after useful results and sustainable delivery.
Expansion should follow a repeatable product, not precede it. New coverage requires suitable data rights, local context, partner responsibilities and an operating model that can support the additional complexity.
- Coverage decisions
- Partner pilots
- Cost to serve
03
Later · Infrastructure options
Assess enterprise APIs, market services and ecosystem mechanisms against separate readiness conditions.
Institutional readiness involves more than adding an endpoint. It requires versioned interfaces, documented permissions, integration testing and support arrangements. Timing remains dependent on the readiness of those underlying capabilities.
- API integration
- Market readiness
- Utility assessment