Clarity
Do they understand what you do?
15 could name what kind of product this is, unprompted.
https://quantumnetwork.ch/15 AI-simulated buyers
Your message needs work: they know what it is, who it's for, and why it's worth their time, but not why to pick you.
Do they understand what you do?
15 could name what kind of product this is, unprompted.
Can they tell what it solves, and who it's for?
15 could quickly tell what problem it solves and who it is for.
Do they actually want it?
13 would take a meeting to learn more.
Is there a reason to pick you over the alternatives?
7 could name a reason to pick you over a similar option.
Your page describes: quantum-safe network security. They said:
9 couldn't name one; 6 got it right.
Four separate measures, not stages: all 15 personas answered all four questions. Each square is one persona.
Three points said the logo strip signals an early-stage vendor leaning on others' names rather than an established one, compounded by the missing case study. Two others read the page as a lean specialist software vendor without judging it. Not one of the four layers, and it does not affect the scores above or the order to fix them in.
These are 15 simulated buyers. Want 15 real ones?
Test with humansThe first is on your weakest layer, the second on the next, the third on the layer the most buyers had a problem with. Each says what to change on the page and why, with one simulated answer behind it.
Why: Mixing physical, virtual and client gateways in one network is the strongest claim on the page, but nothing says competitors cannot do it. Write that single-topology and cloud-managed VPNs force endpoint or firewall changes, while QPN needs only route edits.
Why: OT and utility operators are only inferred from the SCADA diagrams further down. Say in the opening lines that this is for teams protecting SCADA and control traffic across sites over the public internet.
6 of 15 raised this
“What would rule this vendor out, or at least drop them a slot, is the total absence of independent certification or a named reference deployment”
These landed. Keep the wording when you edit around it.
The page names its audience in seconds through SCADA imagery and OT use cases
“The problem is spelled out too: "Traffic can be read, changed or stored" over public internet, which is precisely the SCADA-over-internet exposure I deal with.”
Deployment flexibility, no endpoint touches and offline operation separate the product…
“The "combinable deployment modes" line — site-to-site, edge-to-cloud, and remote client gateways all sitting in the same QPN — is the one concrete differentiator here, because most competitors force you into one topology”
The core product description lands: a post-quantum encryption gateway for SCADA that…
“They sell a hardware gateway box you drop into your existing network stack, in front of or behind your firewall, that encrypts traffic between two sites so anyone intercepting it on the public internet just gets ciphertext — basically a quantum-resistant VPN/encryption appliance for SCADA and OT links.”
Why: The page claims "a typical latency of one millisecond on the protected line" with no test setup behind it, so readers treat it as marketing. State the link type, packet size, throughput and gateway model measured.
Why: "Our gateways are crypto-agile: when the standards move, the software moves" does not say what actually changes or how. Name the algorithm swap as a signed software update, with no hardware or endpoint changes.
Why: "Get my proposal" and "Talk to an expert" compete before the reader knows what the gateway is. Keep the proposal button primary and demote the other to a text link.
6 of 15 raised this
“What would rule this vendor out, or at least drop them a slot, is the total absence of independent certification or a named reference deployment”
No specific edits needed here — this layer held up.
No specific edits needed here — this layer held up.
Why: Nothing on the page shows the gateway running in a real utility or OT network, so it reads as untested. Add an anonymised reference such as sector, number of protected sites and months in production.
3 of 15 raised this
“The naming of partners like Advantech, OnLogic and Red Hat/Ubuntu/SuSE/Debian as "industry-standard" hardware/OS support feels like a young company trying to borrow credibility by association rather than a Cisco or Thales who'd just say "runs on your existing infrastructure"”
Why: Buyers in critical infrastructure need to know who has audited the box, and the page leaves it blank. Say what independent pen-test or certification work exists, or is in progress with a date.
3 of 15 raised this
“The naming of partners like Advantech, OnLogic and Red Hat/Ubuntu/SuSE/Debian as "industry-standard" hardware/OS support feels like a young company trying to borrow credibility by association rather than a Cisco or Thales who'd just say "runs on your existing infrastructure"”
Why: A bare row of Red Hat, Advantech, OnLogic and NIST logos reads as a young vendor borrowing other names. Label them as certified hardware platforms, supported Linux distributions and the standards body behind ML-KEM.
3 of 15 raised this
“The naming of partners like Advantech, OnLogic and Red Hat/Ubuntu/SuSE/Debian as "industry-standard" hardware/OS support feels like a young company trying to borrow credibility by association rather than a Cisco or Thales who'd just say "runs on your existing infrastructure"”
A deliberately adversarial read of the same answers. Each claim was checked back against what the personas said and dropped if nothing supported it.
The page is comprehensible but unbuyable — clarity wins do not convert into a purchase decision
Six respondents said missing named OT references, certification and pen-test evidence halt progression past pilot and budget approval, while the positive themes cover only comprehension of the offer and audience fit.
Every quantified proof point on the page is treated as unverified vendor assertion
Four respondents rejected the 1ms latency figure for lacking methodology or test conditions, and two said 'crypto-agile' has no engineering definition. The page's specifics read as marketing, not evidence.
The differentiation story collapses because its two pillars are the same claims respondents refuse to accept
Crypto-agility is named a differentiator by three respondents yet dismissed as undefined by two, and one explicitly said unproven latency undercuts the deployment-flexibility position. The strongest claims are the least substantiated.
The page actively signals immaturity, which compounds every other evidence gap
Three respondents read the partner logo strip as an early-stage vendor borrowing others' names, explicitly compounded by the missing case study that six others flagged as deal-blocking.
Audience targeting works by accident rather than by statement, leaving the fit unowned
Six respondents identified OT and critical-infrastructure operators, but two noted this is inferred from SCADA visuals rather than stated outright — the page never claims the audience it wins.
Only the NIST standard survives scrutiny, so the page's credibility rests entirely on a third party's name
Three respondents cited FIPS-203/ML-KEM as the verifiable, concrete claim, while latency, crypto-agility, partner logos and customer proof were all challenged. Nothing proprietary stands up.
Deployment flexibility, no endpoint touches and offline operation separate the product…
4 of 15 · what worked
“The "combinable deployment modes" line — site-to-site, edge-to-cloud, and remote client gateways all sitting in the same QPN — is the one concrete differentiator here, because most competitors force you into one topology”
“The "drop it in front of or behind your existing firewall, adjusting a few network routes, without touching servers, clients or applications" line is the thing that would actually pull me toward this one over a rival — that's a concrete deployment claim, not just a slogan, and it maps to a real procurement fear (rip-and-replace risk)”
“The thing that would tip it toward a shortlist call rather than a tab-close is the "physical gateways, virtual gateways and software clients can be combined within the same QPN" line plus the three named deployment modes — site-to-site, edge-to-cloud, remote access. That's concrete enough to mean we could pilot on one port/SCADA link without committing our whole topology to it”
“The "no telemetry, no cloud dependency" line and the claim it can run on private networks and offline OT environments is what would push it up my shortlist over a cloud-managed competitor”
NIST FIPS-203/ML-KEM standardization and crypto-agility are the differentiators…
3 of 15 · what worked
“I'd need the NIST FIPS-203 compliance and a reference deployment in a comparable water/OT environment before this goes anywhere near budget”
“The one concrete thing that would keep them on the shortlist is the NIST FIPS-203/ML-KEM standardization line — that's a real, checkable technical detail, not marketing fluff”
“the "crypto-agile" pitch means I'm not re-architecting again in five years when NIST rotates ML-KEM. That's worth a technical call”
No named customer blocks the deal, not just credibility
6 of 15
“What would rule this vendor out, or at least drop them a slot, is the total absence of independent certification or a named reference deployment”
“it's the actual proof (latency numbers, deployment cost, who's already running it at OT scale) that's missing”
“I'd want them to map our actual stack and show me one existing OT customer reference before I'd let this near a live control network”
“the heavy reliance on logos (Red Hat, Advantech, OnLogic, NIST) instead of named customer case studies suggests they're still building credibility and don't yet have big reference logos of their own to show”
“No named utility customers, so not worth a meeting yet.”
“A named reference customer running this on a port, airport or utility network, with a sourced number for latency and throughput under real OT traffic, plus a plain answer to how a crypto update is pushed and verified for audit — that would make it feel built for me rather than aimed at me.”
“no third-party pen test, no named customer, no latency benchmark methodology behind that "one millisecond" number”
The 1ms latency claim is disbelieved because no test conditions, methodology or…
4 of 15
“I need a reference deployment at OT scale, real latency test data under load, and a price point before I take this past a first call.”
“what's not proven is the "crypto-agile" claim and the 1ms latency figure — I'd want a reference deployment in a similar water/OT environment before I'd believe it holds under load”
“"1ms latency" claim is specific enough to matter, but no named utility deploying it - that rules it out for now.”
“But "typical latency of one millisecond" has no test conditions attached, and I still have no named customer or case study, so right now it's worth one technical call to get those specifics, not a purchase commitment.”
“A named critical-infrastructure or government deployment with a third-party validated latency/throughput benchmark under real traffic conditions — that's the single proof point that turns this from a sales page into something I'd put in front of my team for a pilot.”
"Crypto-agile" reads as marketing shorthand without an engineering definition
2 of 15
“don't tell me what a firmware update actually requires: downtime, a truck roll, remote push? That vagueness is what stops me from calling it a settled category name”
“"crypto-agile" which sounds great but is never defined — agile how, does it need a firmware push, a config change, or a hardware swap when the standard changes?”
The core product description lands: a post-quantum encryption gateway for SCADA that…
3 of 15 · what worked
“They sell a hardware gateway box you drop into your existing network stack, in front of or behind your firewall, that encrypts traffic between two sites so anyone intercepting it on the public internet just gets ciphertext — basically a quantum-resistant VPN/encryption appliance for SCADA and OT links.”
“I get quantum-resistant encryption on my inter-site and remote-access links without touching SCADA, PLCs or firewalls — that's a real gap closed, since "harvest now, decrypt later" against a water utility is a genuine board-level risk”
“quantum-safe encryption for existing networks, no hardware swap. Reader's inferred - OT/SCADA operators, from "SCADA and dispatch" diagram.”
The page names its audience in seconds through SCADA imagery and OT use cases
6 of 15 · what worked
“The problem is spelled out too: "Traffic can be read, changed or stored" over public internet, which is precisely the SCADA-over-internet exposure I deal with.”
“the diagram right after with the control room, SCADA, PLCs, sensors, cameras spelled out who this is for even before they said it explicitly”
“The named use cases — solar parks, container ports, airport control towers, water treatment plants, SCADA/OT environments — make it obvious this is aimed at critical infrastructure and industrial network operators, not a generic enterprise IT buyer”
“It was obvious fast — the hero line "Protect your network with quantum-safe encryption, without replacing your existing hardware" plus the diagram with control room, PLCs, SCADA and "Your machines... all unchanged" told me within seconds this is for OT/critical-infrastructure operators”
“the header line "Protect your network with quantum-safe encryption, without replacing your existing hardware" tells you the problem (quantum-era encryption risk on existing infra) and the fix in one sentence, and the SCADA/control-room diagram with "Solar park, Container port, Airport control tower, Water treatment plant" makes it obvious this is aimed at critical infrastructure / OT operators”
“The intended reader isn't spelled out in a sentence like "for CISOs at utilities" — I inferred it from the imagery: solar parks, container ports, airport control towers, water treatment plants, SCADA.”
The partner logo wall reads as borrowed credibility from a small startup
3 of 15
“The naming of partners like Advantech, OnLogic and Red Hat/Ubuntu/SuSE/Debian as "industry-standard" hardware/OS support feels like a young company trying to borrow credibility by association rather than a Cisco or Thales who'd just say "runs on your existing infrastructure"”
“The Advantech/OnLogic/Red Hat/NIST logo strip is them borrowing credibility rather than having their own track record”
“smallish, engineering-heavy vendor — probably under a few hundred people, maybe 5-10 years old, spun out of a crypto or networking R&D background rather than a big incumbent”
15 AI-simulated personas matched to your target market. Each answered independently, without seeing your goal, the scoring criteria, or each other’s answers. Attribution is role, industry and company size only.
Every answer on this page was written by an AI model role-playing a buyer profile, scored on Wynter’s B2B Message Layers framework. The personas were sampled in code across role, industry, company size and behavioral traits; the model wrote only the answers. Scores arrive through fixed verdict categories and the counts are computed in our own code, so no number here was written by a model.
The count is how many personas cleared the bar on each question. A yes can be unhesitating or come with reservations; the scorecard counts both as a yes, and this is the only place the difference is shown. Per layer:
These answers are AI-simulated and directional. Validate anything you’re betting on with real buyers, your ICPs.
A detailed, section-by-section message test report from verified B2B professionals who are actually in-market for what you sell.







