A proposed three-month Insight pilot pairs each deliverable with a review gate. Longer-term expansion follows evidence rather than a fixed launch calendar.
Proposed pilot sequence · not completed milestones
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.
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.
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.
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.
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.
Test a source-linked EX Insight briefing against a defined user task before expanding product scope.
Evaluate additional coverage and integrations only when recurring use and delivery costs support them.
Assess API services, market operations and ecosystem utility as separate readiness decisions, without a fixed launch year.
Timing and scope can change as product evidence, data availability, partnerships and jurisdictional requirements evolve.
Evaluate calibration, error and usefulness in real product workflows.
Look for repeat use, retention and clear customer value.
Confirm data availability, permitted use and partner readiness.
Review security, reliability, legal and compliance dependencies.
Targets are directional and may change based on validation, partnerships, operational readiness and applicable requirements.
“Each phase builds the operating capability required for the next—product before expansion, network before scale.”
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.
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.
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.