<?xml version="1.0" encoding="UTF-8"?><rss xmlns:dc="http://purl.org/dc/elements/1.1/" xmlns:content="http://purl.org/rss/1.0/modules/content/" xmlns:atom="http://www.w3.org/2005/Atom" version="2.0" xmlns:cc="http://cyber.law.harvard.edu/rss/creativeCommonsRssModule.html">
    <channel>
        <title><![CDATA[Stories by EigenOrbit on Medium]]></title>
        <description><![CDATA[Stories by EigenOrbit on Medium]]></description>
        <link>https://medium.com/@eigenorbit?source=rss-aa34937b3439------2</link>
        <image>
            <url>https://cdn-images-1.medium.com/fit/c/150/150/1*V9j4dmCBXJW1j8KbZSLvxg.png</url>
            <title>Stories by EigenOrbit on Medium</title>
            <link>https://medium.com/@eigenorbit?source=rss-aa34937b3439------2</link>
        </image>
        <generator>Medium</generator>
        <lastBuildDate>Fri, 13 Nov 2026 21:45:17 GMT</lastBuildDate>
        <atom:link href="https://medium.com/@eigenorbit/feed" rel="self" type="application/rss+xml"/>
        <webMaster><![CDATA[yourfriends@medium.com]]></webMaster>
        <atom:link href="http://medium.superfeedr.com" rel="hub"/>
        <item>
            <title><![CDATA[One API key for several quantum computers: how to switch hardware without rewriting code]]></title>
            <link>https://medium.com/@eigenorbit/one-api-key-for-several-quantum-computers-how-to-switch-hardware-without-rewriting-code-d630cd033dcf?source=rss-aa34937b3439------2</link>
            <guid isPermaLink="false">https://medium.com/p/d630cd033dcf</guid>
            <category><![CDATA[aws]]></category>
            <category><![CDATA[python]]></category>
            <category><![CDATA[cloud-computing]]></category>
            <category><![CDATA[quantum-computing]]></category>
            <category><![CDATA[api]]></category>
            <dc:creator><![CDATA[EigenOrbit]]></dc:creator>
            <pubDate>Fri, 13 Nov 2026 14:32:06 GMT</pubDate>
            <atom:updated>2026-11-13T14:32:06.779Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Comparing quantum computers should take a changed line of code, not a week of new accounts and SDKs.</em></p><p><strong>Key points</strong></p><ul><li>Running the same circuit on two quantum vendors usually means two accounts, two SDKs, two billing systems and two ways of counting cost.</li><li>EigenOrbit Router is a multi-vendor quantum API. It puts devices on Amazon Braket and IBM Quantum behind one API key and one prepaid balance, and shows the price of every job before it runs.</li><li>With eigenkit, moving a circuit from a simulator to a real QPU means changing the device string.</li></ul><p>Most quantum algorithms are developed on one vendor’s stack. The team learns its SDK, sets up its billing and gets used to its queue. When someone later asks how the same circuit would do on a different machine, the honest answer is often “we’d need a week to find out”.</p><p>That week has little to do with physics. It goes into a new account, a new SDK, another set of credentials, a different pricing unit and a fresh round of reading documentation. For a team that wants to compare hardware regularly, that overhead adds up fast.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*ega1QeVZjO2xuaaa3-umpg.jpeg" /></figure><h3>Why is it hard to run the same quantum circuit on different hardware?</h3><p>Every vendor packages access differently. The main differences are:</p><ul><li><strong>Accounts and credentials.</strong> Each provider has its own sign-up, keys and permissions, and many companies need a procurement step for each one.</li><li><strong>SDKs and formats.</strong> Circuits written for one stack often need rewriting, and results can come back in different shapes or bit orders.</li><li><strong>Pricing.</strong> Some vendors charge per shot, some per task, some per second or minute of processor time. Comparing the cost of the same experiment across machines takes a spreadsheet.</li><li><strong>Spend control.</strong> A loop that submits more jobs than intended can run up a bill before anyone notices, and each vendor has its own way of setting limits.</li></ul><p>None of these problems is hard on its own. Together, they make teams stay with the hardware they started on, even when another machine might suit the problem better.</p><h3>What is a quantum router?</h3><p>A quantum router sits between your code and the vendors. You send jobs to one endpoint with one key, and the router passes them on to the device you name.</p><p><a href="https://router.eigenorbit.com/">EigenOrbit Router</a> is a multi-vendor quantum API: a single access point to quantum computers and simulators from different providers. It sends jobs to devices on Amazon Braket and IBM Quantum, with one API key and one prepaid balance. The full list of devices is in the <a href="https://router.eigenorbit.com/docs/devices">documentation</a>.</p><h3>How does pricing work?</h3><p>Each job’s price is shown and reserved before it is sent. You can ask for an estimate at no cost, and when you submit, the estimated amount is held on your balance. After the job finishes, the actual cost is charged.</p><p>Every price is in one unit, US dollars, whichever vendor runs the job, so the cost of the same experiment on two machines can be compared directly. On a QPU, the final charge is never more than the amount held. The details are in the <a href="https://router.eigenorbit.com/docs/billing">Router documentation</a>.</p><p>If a job is rejected, fails, or is cancelled before it reaches the vendor, the hold is released in full. A job that fails inside the router after the vendor ran it is not charged.</p><p>Each key can also have its own spending limit. A student project, a CI pipeline and a research team can each get a key with a cap, and once a key reaches its cap, the router stops accepting new jobs from it.</p><h3>How do you switch quantum hardware in one line?</h3><p>Router is built into <a href="https://github.com/eigenorbit/eigenkit">eigenkit</a>, EigenOrbit’s open-source library for writing a quantum algorithm once and running it on many backends. Installation and setup take two lines:</p><pre>pip install &quot;eigenkit[router]&quot;<br>export EIGENORBIT_ROUTER_API_KEY=eo_live_...</pre><p>A circuit is built once and given a provider, which names the device:</p><pre>provider = RouterConfig(device=&quot;braket/sv1&quot;, shots=1000)<br>circuit = Circuit(spec, all_z(2), provider=provider)<br>values = circuit(weights, inputs)  # one router job</pre><p>To move from the Braket simulator to IQM’s 20-qubit Garnet processor, only the device changes:</p><pre>provider = RouterConfig(device=&quot;braket/iqm_garnet&quot;, shots=1000)</pre><p>The rest of the code stays the same. According to the documentation, eigenkit returns results in the same shape, data type and bit order as the same code run with your own vendor credentials. On real hardware the numbers will of course differ from run to run, as shot-based results always do.</p><p>Teams that do not use eigenkit can call the HTTP API directly: submit a job, check its status and fetch the result.</p><h3>Where Router fits</h3><p>Router is one part of a larger idea at EigenOrbit: comparing quantum hardware should be routine, not a project. <a href="https://benchmarks.eigenorbit.com/">Benchmarks</a> helps choose which machine might suit a workload. Router then makes it practical to run the same code on that machine and on the one you used before, and to see what each run cost.</p><h3>About EigenOrbit</h3><p><a href="https://eigenorbit.com/">EigenOrbit</a> builds quantum labs for companies. Each lab is set up around the client’s own problems: it tests every quantum idea against the client’s classical solver and runs what wins on the right machine. Router, Benchmarks and the open-source eigenkit library are part of every lab, and some of them can also be used on their own.</p><h3>Sources</h3><ul><li><a href="https://router.eigenorbit.com/">EigenOrbit Router</a></li><li><a href="https://router.eigenorbit.com/docs/quickstart">Router documentation: quickstart</a></li><li><a href="https://router.eigenorbit.com/docs/billing">Router documentation: billing</a></li><li><a href="https://github.com/eigenorbit/eigenkit">eigenkit on GitHub</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=d630cd033dcf" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[Quantum pilot, in-house team or a lab: what each costs and what you keep]]></title>
            <link>https://medium.com/@eigenorbit/quantum-pilot-in-house-team-or-a-lab-what-each-costs-and-what-you-keep-3b71119455ed?source=rss-aa34937b3439------2</link>
            <guid isPermaLink="false">https://medium.com/p/3b71119455ed</guid>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[hiring]]></category>
            <category><![CDATA[quantum-computing]]></category>
            <category><![CDATA[technology-strategy]]></category>
            <category><![CDATA[innovation]]></category>
            <dc:creator><![CDATA[EigenOrbit]]></dc:creator>
            <pubDate>Fri, 13 Nov 2026 13:39:22 GMT</pubDate>
            <atom:updated>2026-11-13T13:39:22.803Z</atom:updated>
            <content:encoded><![CDATA[<p><em>Most companies reach the same fork after their first quantum briefing. A comparison of the three usual routes, with the numbers we could find.</em></p><p><strong>Key points</strong></p><ul><li>A small in-house quantum team in Western Europe costs roughly €250K to €440K a year in salaries alone, before hiring time and employer costs.</li><li>A one-off pilot is cheaper to start but answers one question, and the next question means a new contract.</li><li>A licensed lab sits in between: an outside team works on your problems over a year, and the methods and code stay with you.</li><li>The right choice depends mostly on how many quantum questions you expect to ask in the next two or three years.</li></ul><p>The first quantum briefing usually goes well. A vendor or an adviser shows where the technology might matter for the business, someone senior asks to look into it, and a budget line appears.</p><p>A few weeks later, someone has to decide who will actually do the work. Most companies end up choosing between hiring their own people, buying a pilot from a vendor or consultancy, and licensing a lab that an outside team runs on their problems.</p><p>These options are rarely compared side by side, partly because each one leaves the company with something different at the end of the year. Below we put them next to each other, using public salary data, the estimates providers publish for pilots, and the published terms of one lab model.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*QGhdpg4A4TWJ7HQ4c7XaYA.jpeg" /></figure><h3>How much does an in-house quantum team cost?</h3><p>In Western Europe, a three-person quantum team costs roughly €250K to €440K a year in salaries, and hiring it usually takes months.</p><p>Three people is about the minimum for taking a business problem all the way to a quantum or classical verdict. One designs the algorithms. Another follows the research closely enough to tell a real result from a hopeful one. The third makes the code run on actual hardware.</p><p>In Germany, Switzerland, the Netherlands and France, recruiter <a href="https://www.deeprec.ai/global-quantum-computing-salary-guide">DeepRec.ai</a> puts mid-level salaries at €90K to €120K for a quantum algorithm engineer, €85K to €110K for a research scientist and €75K to €100K for a quantum software engineer. Senior people in the same roles earn €90K to €160K. A three-person team therefore costs about €250K to €330K a year at mid level and up to €440K at senior level. That is salary only. Employer contributions, equipment, cloud and hardware access come on top.</p><p>Finding these people takes time. In a 2026 survey by QuEra, reported by <a href="https://www.intelligentcio.com/north-america/2026/05/06/quera-computing-report-shows-quantum-market-shifting-from-hype-to-proof-driven-investment/">IntelligentCIO</a>, 37% of organizations named the workforce shortage as a challenge to adoption. A company hiring here competes with quantum start-ups and hardware makers for the same small group of people.</p><p>In return, the company gets a team that learns its business and can switch between problems as priorities change. For a company planning to work with quantum for years, that continuity is hard to buy any other way.</p><p>The weak spot is that with two or three specialists, much of the know-how sits in a few heads. If one of them leaves, a large part of the capability can go too, unless methods and code are documented and shared from the first month.</p><h3>How much does a quantum computing pilot cost?</h3><p>Providers’ own estimates put a three- to four-month quantum proof of concept at around $100K, and a full pilot at up to $150K–400K, often with hardware time billed on top.</p><p>A pilot is the most common first step. A hardware vendor, a consultancy or a specialist firm takes one use case, for example a scheduling problem or a portfolio model, and works on it for a few months. At the end there is a report and, often, a presentation to management.</p><p>Pilot prices are rarely published, and the figures that exist come from providers themselves. Yuval Boger, CMO of quantum software company Classiq, has said a three- to four-month proof of concept can often be done for about $100,000 (<a href="https://www.classiq.io/insights/quantum-computing-proof-of-concept">Classiq</a>). Development firm <a href="https://www.gilzor.com/insights/quantum-app-development-cost">Gilzor</a> gives broader planning ranges: $15K to $40K for a feasibility study, $40K to $150K for a hybrid proof of concept and $150K to $400K for a full pilot. Both are estimates rather than market data, but they give a sense of scale.</p><p>Hardware time is often billed separately. IBM lists pay-as-you-go access at $96 per minute of quantum processor time, and Quantinuum’s machines on Azure start at $125,000 a month, according to the price tracker <a href="https://quantumcomputingcost.com/quantum-computer-price-list/">quantumcomputingcost.com</a>. A pilot that runs many experiments on real hardware can see this line grow quickly.</p><p>For a company that is still unsure, a pilot is the easiest way in. Nobody has to be hired, and the commitment ends with the project.</p><p>Its limits tend to appear afterwards. A pilot answers the question it was scoped for, and the next question is a new project with a new contract. When the pilot is run by a hardware vendor, the comparison is often between their machine and nothing, rather than between their machine and the best classical method the company already uses. And the code and tuned models frequently stay with the provider.</p><p>Pilots also seem to move budgets less than one might expect. In the same QuEra survey, only 9% of organizations said successful pilot results were the main reason their quantum spending went up.</p><h3>What is a quantum lab, and how much does it cost?</h3><p>A quantum lab is an outside team of scientists, with its own software, that works on one company’s problems for a longer period, usually a year. Prices vary by provider; ours is €150K a year.</p><p>Unlike a pilot, a lab is not tied to one question. It can take a routing problem in spring and a materials simulation in autumn, and it is expected to compare every quantum idea with a strong classical baseline. Whatever it builds along the way belongs to the client.</p><p>To give a concrete reference point, our own <a href="https://eigenorbit.com/">EigenOrbit Lab</a> is priced at €150K a year, takes up to 12 weeks to set up and leaves the client with the methods, code, tuned classical baselines and a record of every run. Other providers will structure this differently, and the figure is here to make the comparison tangible, not as a market average.</p><p>The people in a lab are not your employees, so the company still needs someone inside who owns the topic and turns results into decisions. A lab also depends on the client bringing real problems and data. Without them, there is little for it to test.</p><h3>How to choose</h3><p>The most useful question is how many quantum questions the company expects to ask over the next two or three years.</p><p>If the answer is one, a well-scoped pilot may be enough. It is worth insisting that the pilot compares the quantum approach with the best classical method you already use, and that the code is handed over at the end.</p><p>If quantum is likely to become a permanent part of R&amp;D, with several business units involved, an in-house team starts to make sense. It is the most expensive option and the slowest to start, but it builds capability that belongs to the company.</p><p>A lab fits the space in between: companies that expect a steady flow of questions but are not yet sure quantum deserves a permanent team. It can also serve as a bridge, building methods and baselines that a future in-house team inherits.</p><p>Whichever route a company picks, two things carry over from one option to the next. Every quantum result should be measured against a strong classical baseline, and whatever is learned should stay with the company.</p><h3>About EigenOrbit</h3><p><a href="https://eigenorbit.com/">EigenOrbit</a> builds quantum labs for companies. Each lab is set up around the client’s own problems: it tests every quantum idea against the client’s classical solver and runs what wins on the right machine. If classical methods win, the lab recommends classical.</p><p>Sources</p><ul><li><a href="https://www.deeprec.ai/global-quantum-computing-salary-guide">DeepRec.ai: Global Salary Guide, Quantum Computing</a></li><li><a href="https://www.intelligentcio.com/north-america/2026/05/06/quera-computing-report-shows-quantum-market-shifting-from-hype-to-proof-driven-investment/">IntelligentCIO: QuEra report shows quantum market shifting from hype to proof-driven investment</a></li><li><a href="https://www.classiq.io/insights/quantum-computing-proof-of-concept">Classiq: How to execute a quantum computing proof-of-concept project</a></li><li><a href="https://www.gilzor.com/insights/quantum-app-development-cost">Gilzor: Quantum app development cost 2026</a></li><li><a href="https://quantumcomputingcost.com/quantum-computer-price-list/">quantumcomputingcost.com: Quantum computer price list 2026</a></li><li><a href="https://quantumcomputingreport.com/a-four-step-process-for-end-users-to-leverage-quantum-technology/">Quantum Computing Report: A four-step process for end users to leverage quantum technology</a></li><li><a href="https://eigenorbit.com/">EigenOrbit</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=3b71119455ed" width="1" height="1" alt="">]]></content:encoded>
        </item>
        <item>
            <title><![CDATA[AI Is Reshaping Consulting. Is Quantum Computing Next?]]></title>
            <link>https://medium.com/@eigenorbit/ai-is-reshaping-consulting-is-quantum-computing-next-f8f513ebc934?source=rss-aa34937b3439------2</link>
            <guid isPermaLink="false">https://medium.com/p/f8f513ebc934</guid>
            <category><![CDATA[consulting]]></category>
            <category><![CDATA[business-strategy]]></category>
            <category><![CDATA[future-of-work]]></category>
            <category><![CDATA[quantum-computing]]></category>
            <category><![CDATA[artificial-intelligence]]></category>
            <dc:creator><![CDATA[EigenOrbit]]></dc:creator>
            <pubDate>Fri, 13 Nov 2026 12:15:15 GMT</pubDate>
            <atom:updated>2026-11-13T12:15:15.296Z</atom:updated>
            <content:encoded><![CDATA[<p><em>AI is taking over the analyst work consulting was built on. Meanwhile, clients are putting real money into quantum, often without independent advice.</em></p><p><strong>Key points</strong></p><ul><li>Junior research and analysis is the part of consulting AI absorbs first, and entry-level hiring at top firms has fallen since 2023.</li><li>One in three large companies spent over $10 million on quantum in 2025 (McKinsey).</li><li>Classical methods still win on many business problems today. Where they don’t should be settled by benchmarks.</li><li>Advisory work is likely to become more automated and easier to check.</li></ul><p>Ask a consulting team to cut a retailer’s delivery costs, and the proposal will usually name its tools: a routing heuristic, a commercial solver, perhaps a demand forecast on top. What it rarely says is whether anyone checked if part of the routing problem could run better on a quantum computer.</p><p>For most problems today, that check would come back in favour of classical methods. The result still has value. The client gets a measured baseline instead of an assumption, and a reason to look again in a year or two.</p><p>The missing line in the proposal is a small detail, but it points to a larger shift. Consulting is automating its own work faster than it is changing how that work is sold, and quantum has not yet made it onto the standard list of methods.</p><figure><img alt="" src="https://cdn-images-1.medium.com/max/1024/1*luOpNj73LvUfaFT1Y9YVzQ.jpeg" /></figure><h3>How AI is changing the consulting business model</h3><p>Consulting firms have long been built like a pyramid. Partners win the work, managers run the projects, and a wide layer of analysts reads reports, builds models and writes first drafts. Most billable hours come from that bottom layer.</p><p>It is also the layer AI tools reach first. McKinsey says its internal assistant, Lilli, cuts search and synthesis time by up to 30 percent, according to <a href="https://www.theregister.com/2025/12/16/mckinsey_may_cut_staff/">The Register</a>. The same article, citing Bloomberg, reported that the firm was discussing a few thousand job cuts over 18 to 24 months, mostly in support functions.</p><p>Hiring numbers point the same way. <a href="https://www.reveliolabs.com/news/business/the-industry-that-advised-disruption-is-being-disrupted">Revelio Labs</a> found that demand for consultant roles at top firms is about 40% below its 2023 peak. Senior roles grew 55% since 2020 while entry-level hiring fell. By 2025 these firms had more people in AI roles than entry-level consultants, against almost four juniors per AI hire in 2015.</p><p>Pricing is where this gets awkward. Hourly billing made sense when analysis took people weeks. Once software does much of it, clients have more reason to ask for fixed outcomes, or for models they keep and rerun themselves after the project ends.</p><h3>Why quantum computing belongs in strategic advice</h3><p>Large companies are already spending on quantum, whether or not their advisers bring it up.</p><p>McKinsey’s <a href="https://www.mckinsey.com/capabilities/mckinsey-technology/our-insights/mckinsey-quantum-technology-monitor-2026-a-commercial-tipping-point">Quantum Technology Monitor 2026</a> counts more than 300 organizations working with quantum companies, Airbus, E.ON and JPMorgan Chase among them. A third of large companies put more than $10 million into quantum in 2025. Start-ups in the field raised $12.6 billion that year, over six times the 2024 figure.</p><p>Without an independent view, most of what a company learns about quantum comes from vendors. Each vendor is building a different machine and has good reason to show it at its best. Comparing their claims across a dozen platforms takes specialist time that few companies have in-house.</p><p>On many business problems, well-tuned classical methods still come out ahead. Hardware is improving fast, though, and research on where quantum can help keeps producing new results, especially in optimization and in simulating molecules and materials. Companies already hire consultants for exactly these kinds of problems.</p><p>So the useful question is less whether quantum works and more where it beats what the client already runs, and from when. Answering it takes a measurement. The same problem runs on the client’s classical solver and on quantum hardware available today, and the results are compared on time, cost and quality. Often classical wins for now, and the client keeps a benchmark to rerun next year. Sometimes one part of the problem does better on quantum, which is worth knowing early.</p><h3>What the future of consulting could look like</h3><p>Advisory work later this decade may look less like a team on site for three months and more like a set of automated tools run by a few senior people.</p><p>The tools would take over the repeatable part. A business problem gets turned into a mathematical model, run on suitable classical and quantum hardware, and reported in the same format every time, so a result from 2026 can be compared with one from 2028.</p><p>In quantum, this only works if the code is not tied to one vendor, because nobody yet knows which architectures will suit which problems. The tests also have to be easy to rerun. A benchmark ages as fast as the hardware it was measured on.</p><p>People would spend their time on what tools handle badly. Picking the problem worth solving is one example, and it is often not the problem in the original brief. Deciding what a better result means for a particular business is another. Then there is the slow work of getting an operations team to trust a plan it did not build.</p><h3>Questions worth asking</h3><p>AI and quantum have one thing in common here. Both make advice easier to check. If the analysis is automated and the benchmark can be rerun, a client can test a recommendation instead of taking it on trust. A decision to stay classical can be revisited when new data arrives, and so can a forecast that quantum will pay off by 2028.</p><p>For consulting firms and in-house strategy teams, a few questions follow. Does quantum appear in the standard evaluation of optimization and simulation problems, even when the likely answer is to wait? Can the measurements behind a technology recommendation be repeated by someone else? Does the client keep anything reusable once the project ends?</p><p>Each company will answer differently. The questions themselves are likely to come up more often over the next few years.</p><h3>About EigenOrbit</h3><p><a href="https://eigenorbit.com/">EigenOrbit</a> builds quantum labs for companies. Each lab is set up around the client’s own problems: it tests every quantum idea against the client’s classical solver and runs what wins on the right machine. If classical methods win, the lab recommends classical. Methods, code and tuned classical baselines stay with the client.</p><p>The lab combines EigenOrbit’s scientists with its own tools, including <a href="https://eigenorbit.com/quasar/">QUASAR</a>, an AI research agent that tests quantum ideas against the strongest classical methods, and the open-source library <a href="https://github.com/eigenorbit/eigenkit">eigenkit</a>, which runs the same code on 12 simulators and quantum computers. The team of nine is headquartered in Luxembourg.</p><h3>Sources</h3><ul><li><a href="https://www.reveliolabs.com/news/business/the-industry-that-advised-disruption-is-being-disrupted">Revelio Labs: The industry that advised disruption is being disrupted</a></li><li><a href="https://www.theregister.com/2025/12/16/mckinsey_may_cut_staff/">The Register: Hot for its bot, McKinsey may cut thousands of jobs</a></li><li><a href="https://www.mckinsey.com/capabilities/mckinsey-technology/our-insights/mckinsey-quantum-technology-monitor-2026-a-commercial-tipping-point">McKinsey Quantum Technology Monitor 2026</a></li></ul><img src="https://medium.com/_/stat?event=post.clientViewed&referrerSource=full_rss&postId=f8f513ebc934" width="1" height="1" alt="">]]></content:encoded>
        </item>
    </channel>
</rss>