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?
12 would take a meeting to learn more.
Is there a reason to pick you over the alternatives?
6 could name a reason to pick you over a similar option.
Your page describes: quantum-safe network security. They said:
12 couldn't name one; 3 got it right.
Four separate measures, not stages: all 15 personas answered all four questions. Each square is one persona.
Five respondents interpreted partner and standards logos in place of customer logos as a signal of a young spin-out without an enterprise sales motion or real commercial traction. 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: Buyers already run VPN tunnels and cannot tell what this replaces or beats. State the throughput, latency and key-exchange difference against the tunnel they run today.
2 of 15 raised this
“what does ML-KEM/FIPS-203 actually protect me against today versus a standard IPsec/WireGuard tunnel I already run, what's the real throughput/latency hit above 1 Gbit/s, and what does the crypto-agility subscription cost long-term”
Why: No named reference appears anywhere, so interest stops short of budget. One production deployment with a measurable result closes the gap.
5 of 15 raised this
“One named utility or industrial operator saying they've run this in production for at least a year with zero SCADA disruption — that single proof point turns it from an interesting call into something I'd actually push through procurement.”
Why: Offering both positions without a default leaves the network engineer to design the topology themselves. Name the recommended placement and when the alternative applies.
2 of 15 raised this
“the fuzzy part was "in front of or behind your existing firewall," which reads like they're hedging on the actual topology instead of just telling me the recommended placement for our setup.”
These landed. Keep the wording when you edit around it.
The opening lines name the problem and the audience without making anyone hunt
“the subhead "Protect your critical OT traffic with quantum-safe encryption without replacing your existing hardware" and the next line "Built for OT teams and utility operators who need to securely connect SCADA and control systems across sites" basically hands you the problem and the audience in the first two sentences.”
Respondents can repeat the core offer back: quantum-safe encryption for OT without…
“They sell a hardware gateway box you drop in front of and behind your existing OT connections to make the link between sites quantum-safe encrypted, without touching the SCADA/PLC gear itself — basically a "quantum-safe VPN appliance" for critical infrastructure.”
Why: Hardware, Cryptography, Crypto-agile and Clients are all claims a rival post-quantum vendor could copy. Name the one thing only this gateway does, such as keeping existing firewalls and routing untouched.
2 of 15 raised this
“what does ML-KEM/FIPS-203 actually protect me against today versus a standard IPsec/WireGuard tunnel I already run, what's the real throughput/latency hit above 1 Gbit/s, and what does the crypto-agility subscription cost long-term”
Why: The numbers sit alone with no test setup, so a network engineer reads them as marketing. Say what hardware, traffic profile and duration produced them.
2 of 15 raised this
“what does ML-KEM/FIPS-203 actually protect me against today versus a standard IPsec/WireGuard tunnel I already run, what's the real throughput/latency hit above 1 Gbit/s, and what does the crypto-agility subscription cost long-term”
Why: Two buttons side by side split the reader between a quote and a conversation with no guidance on which comes first. Lead with one and demote the other to a text link.
5 of 15 raised this
“One named utility or industrial operator saying they've run this in production for at least a year with zero SCADA disruption — that single proof point turns it from an interesting call into something I'd actually push through procurement.”
No specific edits needed here — this layer held up.
Why: A row of partner and standards logos where customer logos usually sit reads as a young spin-out with no live installs. Name one utility or operator site, or describe an anonymised deployment with sector, site count and go-live date.
5 of 15 raised this
“The logos (Red Hat, Advantech, OnLogic, NIST) read like hardware/OS partners, not customers, which itself tells me they're early-stage and leaning on partner credibility because they don't have named client wins yet.”
Why: Everything below the headline speaks to the engineer routing packets, leaving the person signing off with no reason to care. State the compliance deadline, risk or cost avoided in one sentence.
5 of 15 raised this
“The logos (Red Hat, Advantech, OnLogic, NIST) read like hardware/OS partners, not customers, which itself tells me they're early-stage and leaning on partner credibility because they don't have named client wins yet.”
Why: The claim that machines keep working is asserted with nothing behind it. Give the hours required, whether a maintenance window is needed, and what happens if the gateway fails.
5 of 15 raised this
“The logos (Red Hat, Advantech, OnLogic, NIST) read like hardware/OS partners, not customers, which itself tells me they're early-stage and leaning on partner credibility because they don't have named client wins yet.”
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's clarity win is cosmetic: people understand the offer and still cannot act on it.
Seven respondents restated the product accurately and nine found the problem and audience explicit, yet eight flagged the absence of any named customer as the thing stalling the decision. Comprehension is not the bottleneck; proof is.
Partner and standards logos are actively damaging the brand, not neutral filler.
Five respondents read partner and standards badges standing in for customer logos as evidence of an early-stage spin-out with no commercial traction, while eight separately demanded a named reference. The substitution invites the worst inference.
The page hands the deal to any competitor with a single operator logo.
Eight respondents said one production reference would convert interest to budget and its absence would lose the deal outright. Nothing else on the page compensates for that.
Every claim on the page is self-referential, so nothing can be verified before a buying decision.
Three respondents found throughput and latency numbers with no head-to-head against IPsec or WireGuard and no load testing, and one said the non-disruptive install claim needs confirmation from an existing customer. The performance story and the deployment…
The page cannot survive contact with the person who signs, because it only speaks to the person who installs.
Three respondents read the tone as a technical pitch for OT engineers with no business or commercial framing, while three others wanted cost detail alongside the specs. The economic buyer is given nothing to take forward.
The narrow industrial proof sets a ceiling on the addressable audience the page can serve.
One respondent said non-industrial logos are needed before the page reads as relevant to SaaS, and the explicit audience naming that nine respondents praised works as exclusion outside OT. Precision on who it's for is doubling as a statement of who it isn't.
The performance specs are unbenchmarked against the VPNs buyers already run
2 of 15
“what does ML-KEM/FIPS-203 actually protect me against today versus a standard IPsec/WireGuard tunnel I already run, what's the real throughput/latency hit above 1 Gbit/s, and what does the crypto-agility subscription cost long-term”
“"up to 1 Gbit/s per physical gateway... the same software stack reaches 10 Gbit/s" virtually. That's concrete enough to compare against a competitor's spec sheet, and most quantum-safe pitches I've seen stay abstract about performance”
“An independent conformance/pen-test report showing the ML-KEM implementation actually holds up under real attack simulation, paired with a reference site running it live on multi-site OT traffic — without that it's just a claim on a webpage”
No named customer exists anywhere on the page, and it stalls the decision
5 of 15
“One named utility or industrial operator saying they've run this in production for at least a year with zero SCADA disruption — that single proof point turns it from an interesting call into something I'd actually push through procurement.”
“What I couldn't tell you is who's actually running this in production — no named utility or operator logged, just logos (Red Hat, Advantech, NIST) that read more like partners/standards than customers.”
“What would rule it out, or at least stall it, is the total absence of a named utility or industrial reference — Red Hat, Advantech, NIST are partners and standards bodies, not "site X has been running this since 2024." Against a competitor with even one named operator logo, I'd lean that way regardless of how clean this diagram is.”
“No customer names, no numbers on price or actual deployments, so it's a maybe not a pick.”
“An independent conformance/pen-test report showing the ML-KEM implementation actually holds up under real attack simulation, paired with a reference site running it live on multi-site OT traffic — without that it's just a claim on a webpage”
“"the same software stack reaches 10 Gbit/s" and the crypto-agile bit — "when the algorithms change, an active subscription updates the software, the hardware stays." That's a concrete technical differentiator versus a competitor who might lock you into fixed hardware for algorithm updates. But it's still just a claim on a page — I'd need a named reference customer running SCADA over this at that throughput before it beats an incumbent.”
Deployment specifics go unanswered: firewall placement and install disruption
2 of 15
“the fuzzy part was "in front of or behind your existing firewall," which reads like they're hedging on the actual topology instead of just telling me the recommended placement for our setup.”
Respondents can repeat the core offer back: quantum-safe encryption for OT without…
6 of 15 · what worked
“They sell a hardware gateway box you drop in front of and behind your existing OT connections to make the link between sites quantum-safe encrypted, without touching the SCADA/PLC gear itself — basically a "quantum-safe VPN appliance" for critical infrastructure.”
“OT links quantum-safe without ripping out hardware—real if true. Worth a 30-min call, not a purchase yet.”
“you drop in at each end of a network link to encrypt traffic between sites (control rooms to SCADA/OT equipment, offices, cloud) using post-quantum algorithms like ML-KEM, so it's future-proofed against quantum decryption”
“They sell a hardware/software gateway appliance that sits at each end of an existing network link and wraps the traffic in post-quantum encryption (they cite ML-KEM/FIPS-203) without touching the SCADA, PLCs or firewall behind it.”
“A gateway goes in at each end of the connection... Nothing on your sites is replaced”
“our multi-site OT links stop being a soft spot on the perimeter map — we'd close the "public internet between sites" gap they call out without ripping out SCADA gear or firewalls”
“our OT/site-to-site links stop being a "harvest now, decrypt later" liability without a forklift upgrade — "without replacing your existing hardware" and up to 1 Gbit/s per gateway, 10 Gbit/s virtual, is the specific claim I'd want to test.”
The industrial-only proof makes relevance outside OT unclear
1 of 15
“I'd need a line naming SaaS or corporate site-to-site VPN traffic explicitly, not just SCADA/OT — something like "also secures inter-office or cloud-to-cloud links" — plus a customer logo or case study that isn't industrial”
The opening lines name the problem and the audience without making anyone hunt
7 of 15 · what worked
“the subhead "Protect your critical OT traffic with quantum-safe encryption without replacing your existing hardware" and the next line "Built for OT teams and utility operators who need to securely connect SCADA and control systems across sites" basically hands you the problem and the audience in the first two sentences.”
“the subhead spells it out immediately: "Protect your critical OT traffic with quantum-safe encryption without replacing your existing hardware," followed right away by "Built for OT teams and utility operators who need to securely connect SCADA and control systems across sites, over any public network." That's problem and audience in the first two lines, no digging required.”
“The subhead does the work in one line: "Protect your critical OT traffic with quantum-safe encryption without replacing your existing hardware," followed immediately by "Built for OT teams and utility operators who need to securely connect SCADA and control systems across sites, over any public network." That's problem plus audience in two sentences, right at the top, no hunting required.”
“Protect your critical OT traffic with quantum-safe encryption without replacing your existing hardware”
“the subhead spells it out immediately: "Protect your critical OT traffic with quantum-safe encryption without replacing your existing hardware. Built for OT teams and utility operators who need to securely connect SCADA and control systems across sites."”
“the subhead literally spells it out: "Protect your critical OT traffic with quantum-safe encryption without replacing your existing hardware," followed immediately by "Built for OT teams and utility operators who need to securely connect SCADA and control systems across sites."”
Partner and standards logos read as borrowed credibility from an early-stage company
5 of 15
“The logos (Red Hat, Advantech, OnLogic, NIST) read like hardware/OS partners, not customers, which itself tells me they're early-stage and leaning on partner credibility because they don't have named client wins yet.”
“The partner logos (Red Hat, Advantech, OnLogic, NIST) read like they're piggybacking on other people's credibility because they don't have their own customer names to show.”
“there's no pricing, no case study, no named customer, no team page, which is what I'd expect from a young technical team that hasn't yet built the commercial layer around a genuinely good engineering pitch”
“Small, specialized vendor — feels like a 20-50 person security startup that spun out of either a crypto research group or a defense/industrial contractor, not a big enterprise player. The logo row (Red Hat, Advantech, OnLogic, NIST) is doing a lot of the credibility work for them — those look like hardware/OEM partners and a standards body, not customer logos, which tells me they're young enough that they can't show real customer names yet.”
“I picture a small, technical spin-out — maybe 20-50 people, a few years old, probably born out of a crypto or NIST-standards research background rather than a classic security vendor.”
The page is pitched at network engineers and gives a C-suite buyer nothing
3 of 15
“The tone is written for a network engineer or OT operations lead, not for me: it's all "your IT team connects it by adding or adapting a few routes," DIN rails, PLCs, firewalls staying in place — very hands-on, reassuring-to-a-technician language, not a growth or risk pitch aimed at a C-suite budget holder.”
“there's no pricing, no case study, no named customer, no team page, which is what I'd expect from a young technical team that hasn't yet built the commercial layer around a genuinely good engineering pitch”
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.







