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 lands: they know what it is, who it's for, why it's worth their time, and 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?
15 would take a meeting to learn more.
Is there a reason to pick you over the alternatives?
11 could name a reason to pick you over a similar option.
Your page describes: quantum-safe encryption. They said:
11 couldn't name one; 4 got it right.
Four separate measures, not stages: all 15 personas answered all four questions. Each square is one persona.
Two respondents wanted company history and size to assess stability, and one read the logo row as partner badges rather than customer references. 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: A reader cannot tell whether the box needs a call-home to license or recover after a power cut. State that licensing works offline and the gateway restarts unattended.
1 of 15 raised this
“not some new category, just VPN concentrators with a different cipher suite and a crypto-agility subscription model”
Why: "An active subscription updates the software" leaves buyers unsure whether encryption stops when the subscription ends. State that the gateway keeps encrypting and only algorithm updates pause.
2 of 15 raised this
“they never say what happens to the encrypted link if that subscription lapses, and if a competitor states plainly that gateways fail open, fail closed, or keep running on last-known-good algorithms, that answer wins the deal”
Why: Nothing on the page says whether the gateway will slow a SCADA link. Publish throughput and added latency numbers next to the hardware description.
5 of 15 raised this
“zero proof it survives a real plant environment, just diagrams and NIST algorithm names”
These landed. Keep the wording when you edit around it.
The 'no telemetry, no cloud dependency' line is the differentiator respondents can…
“The specific thing that would push me toward this one over a competitor is "no telemetry is sent to the manufacturer, and there is no dependency on third-party cloud services" combined with "no activation is required: the licence is included, pre-installed and bound to the serial number."”
The drop-in, nothing-gets-replaced deployment story lands as the clearest and most…
“The "nothing on your sites is replaced" line is the one that would stick with me because it answers my first worry, which is workload on my team.”
Respondents understood the product as quantum-safe encryption for OT operators
“They make a hardware box called a "Quantum Gateway" that you drop into your existing network, one on each end of a connection, to encrypt traffic between sites, remote workers, or cloud environments so it can't be cracked once quantum computers arrive.”
Why: The one thing that separates this gateway from cloud-managed VPN appliances sits buried below the diagrams. Put a line in the hero saying the gateway runs with no telemetry and no cloud dependency.
1 of 15 raised this
“not some new category, just VPN concentrators with a different cipher suite and a crypto-agility subscription model”
Why: The heading reads as a category slogan any security vendor could use, so buyers file the product as a generic VPN appliance. Say plainly it is a post-quantum VPN gateway for OT sites.
1 of 15 raised this
“not some new category, just VPN concentrators with a different cipher suite and a crypto-agility subscription model”
Why: Buyers work out that this is for OT and critical infrastructure from icons and diagrams rather than words. Name water, energy, ports and airports and the OT or ICS security owner in the subhead.
3 of 15 raised this
“I inferred the reader from the diagrams and industry logos rather than a direct sentence naming the buyer”
Why: The unlabeled logo row reads as customer references and then disappoints. Add a caption naming what the row is, and place any customer names separately.
2 of 15 raised this
“there's no company history, no size, no named industry vertical beyond generic "critical infrastructure," so I can't tell if this is a two-year-old startup or an established OT security player”
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 asks for a security purchase decision while withholding every number a buyer needs to make it.
Five respondents flagged missing latency, throughput, failure-rate, independent validation and per-site pricing; two more could not determine subscription lapse terms or cost. Comprehension is high, but nothing on the page can be evaluated.
Comprehension is being mistaken for persuasion — the page explains itself well and proves nothing.
Nine respondents across two themes restated the proposition and deployment story accurately, yet five demanded a named production reference and two could not verify the vendor exists at scale. Understanding the claim is not believing it.
The logo row actively damages credibility by reading as partners where customers were expected.
One respondent read the row as partner badges rather than customer references, while five separately said the value case only closes with a named reference — one specifying a utility six months in production. The page's only social proof answers the wrong…
The single differentiator is a negation, and negations are trivially copied by any competitor willing to ship an on-prem build.
Six respondents named 'no telemetry, no cloud dependency' as the concrete differentiator, and one categorized the product as a VPN appliance with post-quantum crypto rather than anything novel. Absence of cloud is a configuration, not a moat.
Making buyers decode their own relevance from icons costs the page every reader who does not bother.
Four respondents inferred the buyer and use case from OT icons and diagrams instead of explicit sector naming. The ones who worked it out were tested and paid attention; a live visitor is not.
The strongest asset on the page — drop-in deployment — is asserted operationally and never quantified.
Five respondents tied the nothing-gets-replaced story to reduced retraining, re-certification and routing workload, yet five others said the value case needs latency, throughput and failure-rate data. The claim most likely to close the deal is the one with…
The 'no telemetry, no cloud dependency' line is the differentiator respondents can…
6 of 15 · what worked
“The specific thing that would push me toward this one over a competitor is "no telemetry is sent to the manufacturer, and there is no dependency on third-party cloud services" combined with "no activation is required: the licence is included, pre-installed and bound to the serial number."”
“"no telemetry sent to the manufacturer, and no dependency on third-party cloud services" line plus "after a power failure, the gateway restarts by itself and continues operating" — that's the kind of detail that matters for OT”
“for OT and critical infrastructure links, air-gapped/offline-capable security tooling with no phone-home is a real differentiator, not fluff.”
“"no telemetry is sent to the manufacturer, and there is no dependency on third-party cloud services" line plus "the licence is included, pre-installed and bound to the serial number" — that's a specific, checkable design choice, not marketing fluff, and for a gov OT shop it's a real differentiator against competitors who route through vendor cloud dashboards”
The product is placed as a VPN appliance, not a new category
1 of 15
“not some new category, just VPN concentrators with a different cipher suite and a crypto-agility subscription model”
Commercial and technical terms are left undefined
2 of 15
“they never say what happens to the encrypted link if that subscription lapses, and if a competitor states plainly that gateways fail open, fail closed, or keep running on last-known-good algorithms, that answer wins the deal”
“The crypto-agility line is the culprit: "when the algorithms change, an active subscription updates the software" never says which algorithm families are supported beyond ML-KEM/FIPS-203, so "crypto-agile" is a label without a definition”
The drop-in, nothing-gets-replaced deployment story lands as the clearest and most…
5 of 15 · what worked
“The "nothing on your sites is replaced" line is the one that would stick with me because it answers my first worry, which is workload on my team.”
“my team gets quantum-safe encryption on the links between our sites, control rooms and remote users without touching SCADA, PLCs or ripping out anything — "nothing on your sites is replaced" is the line that matters to me because it means no retraining, no re-certifying control systems”
“"your IT team only needs to add or adjust a few routes," tells me the workload hit is a rack-mount and a routing change, not a migration project. It's worth a 30-minute call on that basis alone, especially since they offer it with no contact details required”
“They sell hardware gateways that bolt quantum-resistant encryption onto existing SCADA/OT links without ripping out your firewall or PLCs — basically a drop-in VPN-style box pair”
“What made it click was the concrete diagram of gateway-at-each-end plus the "nothing removed, just add a route" framing — that's a real deployment story, not just buzzwords.”
“"SCADA, PLCs, sensors and cameras keep working as they do today" and the logos (Advantech, OnLogic, NIST) I inferred OT/critical-infrastructure IT leadership without much effort”
Respondents understood the product as quantum-safe encryption for OT operators
4 of 15 · what worked
“They make a hardware box called a "Quantum Gateway" that you drop into your existing network, one on each end of a connection, to encrypt traffic between sites, remote workers, or cloud environments so it can't be cracked once quantum computers arrive.”
“the diagram callouts — SCADA, PLCs, sensors, control rooms, "critical OT environments" — make it obvious pretty fast that this is aimed at industrial/utility-type operators like me”
“the H1 "Quantum-safe encryption for multi-site networks" and the subhead "Deploy quantum-safe encryption across existing connections without redesigning your network" told me the problem (harden site-to-site/OT/remote-access traffic against future quantum decryption without ripping out infrastructure) in the first two lines.”
The target sector is inferred from diagrams and icons rather than named
3 of 15
“I inferred the reader from the diagrams and industry logos rather than a direct sentence naming the buyer”
“I inferred the specific persona from the icons and examples rather than a direct sentence naming me”
“I'd want my own sector named explicitly — energy, grid, utility — not just "OT" and generic examples like solar parks and water treatment”
No performance data or named production customer backs the claims
5 of 15
“zero proof it survives a real plant environment, just diagrams and NIST algorithm names”
“the page gives me no numbers: no latency overhead, no failure rate, no independent validation beyond citing FIPS-203”
“I'd need a reference customer in a similar OT environment, the actual routing/firewall placement diagram for our topology, and clarity on what happens to traffic if the subscription lapses”
“One verifiable reference: a similarly-sized utility or critical-infrastructure operator with this gateway live on a real SCADA link for at least six months, and someone I can actually call”
“But "worth a meeting" hinges on numbers I didn't see: latency/throughput overhead of the gateway, actual failover behaviour beyond "restarts after power failure," and price per site.”
Vendor stability is unverifiable and the logo row does not read as customer proof
2 of 15
“there's no company history, no size, no named industry vertical beyond generic "critical infrastructure," so I can't tell if this is a two-year-old startup or an established OT security player”
“The logo row (Red Hat, Advantech, OnLogic, NIST) reads like partner/hardware-supplier badges, not customer logos, which tells me they're still building credibility rather than showcasing a client base.”
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.







