The answers most often asked for in conversations. Missing yours? Write to us via the contact form.
Quantum ecosystems as a service: we design, build and operate complete venture ecosystems consisting of venture builder, incubator, accelerator, hackathon and workforce series, and a strategic fund, plus the enabling foundation underneath (methodology, partner network, space, operations). For two client groups: hardware providers who need traction, and governments who want to build an attractive quantum ecosystem.
Quantum does not fail on physics today; it fails on the distance between hardware, users and capital. Billions in investment flow into the industry while commercial revenue remains a fraction of it, and roughly half of quantum roles go unfilled for lack of trained people. That gap is not closed by a research grant or a generic accelerator. It closes only when startups build on real hardware from day one and everyone involved works in one place.
The first cohort runs within six months of mandate start. Behind that is a three-phase approach: design (8–10 weeks, fixed price), build (around 4 months, fixed price) and ongoing operations (3+ years; for government mandates with a KPI-linked compensation component).
A team with over 15 years of experience building and operating incubators, accelerators and venture funds across three continents, with more than 100 ventures built, incubated and accelerated, including F10 (today Tenity) and QAI Ventures. The operating entity is Konzeptwerkstatt GmbH, based in Switzerland. Details are in the legal notice.
Yes. Each module can be developed on its own, for instance a hackathon series as an entry point or an accelerator for an existing portfolio. The ecosystem reaches its full potential, however, when all modules are in place: the hackathons feed the incubator, the incubator feeds the accelerator, and the fund binds the best teams to the system. Scope and sequence are decided in the design phase.
By your traction: active workloads on your systems, startups architected on your stack, corporate pilots and reference customers, developers with first hours on your hardware, and lighthouse use cases you can point to. Adoption KPIs are defined together in the design sprint and reported quarterly. Fund returns are a by-product, not the goal.
Yes, and this is a growing case: sovereign system sales increasingly bundle ecosystem, application and workforce commitments. We act as the delivery partner that builds the programmes, talent pipeline and application layer around your deployed systems, so the commitments in your contract turn into visible results at the customer.
Three things: compute-time and sandbox quotas with an SLA for programme use, technical mentoring for cohort teams, and input on strategic use-case fields. Everything else (scouting, programmes, corporate channel, events, operations) we deliver.
A direct mandate in three steps: an intro call of 30–60 minutes on roadmap and module selection (under NDA on request), then a fixed-price design sprint of 8–10 weeks delivering the target picture, adoption KPIs, blueprint and budget, followed by build and ongoing operations.
A complete national quantum hub: designed around your strategy, built to operational readiness, operated against a jointly defined KPI framework, and handed over to local ownership at the end. Each phase closes with named, formally accepted deliverables. Details on the governments page.
Design and build phases at a fixed price, with clearly defined deliverables. The operations phase contains a performance-based component linked to the jointly agreed KPI set. Budgets are approved and reviewed by you annually.
Public announcements around quantum hubs consistently promise the same things: research translated into products and growing companies, good jobs, companies attracted to the location, a trained workforce and private capital mobilised. Our KPI framework covers exactly these dimensions: companies attracted and retained, skilled jobs created, practitioners trained, private co-investment alongside public money, plus the programme and ecosystem metrics underneath.
No; the opposite is anchored in the contract: key roles are filled locally in the build phase, your emerging leaders shadow our team from the start, and at the end of the operations phase we hand the hub over to your team. The mandate ends with your independence.
The fund finances the hub's startups, from seed to growth. In the design phase, one of three setups is chosen, from a simple seed vehicle to a full venture fund with a 10-year lifetime, modelled to cover the hub's operating costs over its lifetime and to crowd in private co-investment. Governance, SPV setup and a seat on the investment committee for you are part of it.
Yes, the approach is built for it: defined phases, named deliverables per phase, a transparent cost structure, annual reviews. For market soundings and pre-procurement dialogue we offer a formal briefing with reference material.
Through engineered deal flow: trend reports with strategic focus, AI-assisted screening, university and corporate networks, databases and the hackathon pipeline. From 50–70 qualified applications per cohort, 30 are screened and rated, 15–20 invited to a two-day selection event, and 4–7 teams contracted.
Guaranteed compute time on real hardware, a structured programme with stage gates (venture builder, incubator of 6–9 months or accelerator of 3–6 months), corporates as pilot and first customers, seed financing through the fund and an internationalization path for the best teams.
Corporates are the demand end of the ecosystem: as partners and sponsors they supply real business challenges, run pilot projects with the startups and receive early access to use cases, prototypes and talent in return. Partner models incl. benefits and fees are defined per ecosystem in the design phase.
Through the hackathon and workforce module: hackathons and bootcamps as the entry point, practitioner training aligned with universities and industry demand, and the venture builder as the founding path for researchers. In a market where roughly half of quantum roles go unfilled, the workforce engine is not a side effect of the ecosystem; it is one of its core products.
Your question was not covered?
Ask a question
quantum-ecosystem