The homepage that invites everyone in, then hands them a form
A quantum software homepage invites every developer in while its product sits behind a form for specialists. Why nobody caused the gap, and one question to run on your own product.
Posted on:
Sep 28, 2026
Team:
André Sequeira
Categories:
Science

A publicly listed quantum software company opens its homepage with an unusually honest admission: only a few hundred people in the world, it says, have the skills to design quantum algorithms. A little further down, it asks: “What if programming a quantum computer was as simple as writing a script?”
It’s a good question. I read it the way it’s phrased, as an aspiration (mainly because I don’t know anything about quantum algorithms), written for the developer who has never touched a qubit.
Then I went looking for the product.
The menu on the website lists some things like measurement-based quantum computation and dynamic memory management. The product is presented as the tool for serious quantum software work. There’s nothing to open. The only way in is a form to register interest, and access goes to selected users based on their use case.
To be fair to them, serving specialists first is very likely the right call. The hardware is early, and experts are the ones who can do something useful with it today. Nothing below argues with that choice.
One page is talking to two people at once
The developer the mission invites can’t get in. The specialist who can get in isn’t the person the mission was written for.
In the framework we use at Mistaek, this is Said and Shipped: the distance between what a company says it is and what it hands a person to use. You usually need two things side by side to see it, a deck and a product, or a site and a dashboard. Here it fits on one page, and anyone can check it in 30 seconds.
What makes it more than a copy problem is where the visitor ends up. Every other surface asks to be believed. The product is where you stop asking. On this page, everything a visitor can open asks to be believed: the mission, the capability list, the partner logos. The one surface that would settle the question sits behind a form.
A developer who took the invitation seriously is left weighing two claims that point in different directions, with nothing to check either of them against.
Nobody decided who the page is for
I don’t think anyone wrote this page badly. My guess is that the mission line and the product copy were written by different people, at different times, for different jobs. A mission is supposed to be ambitious. Product copy is supposed to be accurate for the people who use the product. Each is reasonable on its own. Put them on the same page and the contradiction assembles itself.
That’s Drift, which is what happens in the absence of a decision. Nobody chose to invite developers in and then turn them away. The missing decision is the most basic one a page can make: who it’s for. Without it, each section answers to whoever wrote it, and the person who actually clicked isn’t on anyone’s list.
I can’t tell you what this costs them. I have no data on who fills in the form and who closes the tab. Reasoning from how the page works, I’d expect the developer who arrived on the idea of scripts to read the product menu, recognise very little of it, and conclude it isn’t for them yet. That conclusion might even be correct. The page just never says it.
A good story raises the bar your product has to clear
If an established, listed company ends up here, I’d expect a fifteen-person startup with a raise coming to get there sooner. At that size, I’d expect the deck to change every round, the site to change whenever someone has a free afternoon, and the product to change every sprint, with nobody owning the distance between them.
None of this is an argument against story. The story on that quantum page is good. The missin is clear and worth wanting, and it’s the reason a developer clicked at all. If you distrust copy, I think the instinct is right about one thing: a story with nothing behind it to check. A story makes a promise. The product is where the promise gets kept or broken, and the better the story, the higher the bar the product has to clear.
So the check I’d run is one question about your product:
If I opened your product right now with no context, would I guess it came from the company in your deck?
Answer it privately. Answer it honestly, if you can.
I ran the same check on mistaek
The rest of this site still describes a studio that has since changed, and I’m working on it. Until that’s done, the distance between this article and the pages around it’s mine. I’d rather name it than have you find it.
The check only works if you keep running it, because the answer moves the moment nobody is looking.


