Program Roadmap
Apr 2026
Launch Week
Program announced. All posts live. Partner comms sent. Challenge portal open.
Launch - 15 Sep 2026
Phase I - Ideation
Concept proposals accepted from global research community. Phase I closes 15 September 2026.
16 Sep - 14 Nov 2026
Phase I Review
Proposals reviewed by enterprise sponsors and independent assessors. Finalists selected.
17 Nov 2026 - 28 Feb 2027
Phase II - PoC
Selected teams build PoC. AWS compute credits, Classiq tooling, and expert office hours provided.
1 Mar - 30 Apr 2027
Review + Close
PoC results benchmarked.
Winners announced 30
April 2027.
Initiative Scope & Format
Unlock unprecedented opportunities in quantum computing innovation
Global Call
Open to all teams, remote-first execution
In Person Event
End of year event in South Carolina
Partnership
In collaboration with organizations across academia, start-ups, and enterprises
Local Streams
Regional initiatives aligned with global phases, locally funded to deploy real-world solutions.
Infrastructure
Teams provided with tools, data, and backends to build prototypes.
Goal:
Create viable, reproducible solutions within the global initiative.
Evaluation criteria
We target transformative applications in quantum technologies.
KPI / quantum advantage
Evidence/validity of approach
Clarity/Quality of explanation
Potential for scalability for industrial relevance
Business value
Who can join?
Individuals aged 18+, companies, and academic teams not under sanctions or export restrictions.
Can teams include multiple institutions?
Yes. Cross-institutional teams are welcome — one lead entity must be designated.
Is there a team size limit?
No fixed limit. Typical teams include 2–8 members.
What level of expertise is required?
Graduate-level knowledge or equivalent hands-on experience is expected.
Do I need hardware access?
No. Simulators are sufficient; hardware runs are scheduled as capacity allows.
Which platforms are supported?
Multiple backends per cohort; configurations are disclosed for fair comparison.
Is Classiq required?
No, it’s optional but recommended for design and orchestration.
Can I use other SDKs?
Yes — Qiskit, Cirq, PennyLane, CUDA-Q, or any reproducible and license-compliant stack.
How will projects be evaluated?
By a pre-registered rubric: correctness, impact, efficiency, portability, reproducibility, and security.
Will code be published?
Not by default — only method summaries and selected snippets may appear publicly.
How are ties resolved?
Through secondary metrics and documented reviewer discussions.
Who owns the IP?
Individuals aged 18+, companies, and academic teams not under sanctions or export restrictions.
Can I submit multiple entries?
Yes, if they’re materially distinct and well-documented.
Can I use previously published work?
Yes, provided it includes meaningful improvements and proper licensing.
What artifacts are required?
Container image, environment file, deterministic seeds, structured logs, and README with run commands.
Will mentorship be available?
Yes — through office hours and group clinics (no guaranteed 1:1).
Are cloud resources provided?
Teams can use their own or available partner credits; details posted per cohort.
Can enterprises submit problem statements?
Yes, if they’re generalizable and publishable at the metric level.
What’s the timeline?
Full program milestones are published on the cohort page.
Can parts of my report be redacted?
Yes, with justification — balancing transparency and trade-secret protection.
How are conflicts of interest managed?
Declared in advance; reviewers recused when needed. Sponsors have no influence over results.
