# Message test — https://quantumnetwork.ch/ After reading your page, only 6 of 15 personas could name a reason to pick you over a similar option. - **Page tested:** https://quantumnetwork.ch/ - **Audience tested against:** Mid-market SaaS CMOs at 200–1000 person companies who own demand gen and report to the CEO. - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/quantum-network-eYCaaY0 > These answers are generated by AI, scored on Wynter's B2B Message > Layers framework using behaviorally-diverse simulated personas. The > methodology is real and the critique is directional. What a simulated > persona cannot have is a live budget, a renewal coming up, or a boss > asking about this quarter. --- ## 01 · The scores Every persona answered all four questions. These are four independent proportions of the same panel, not stages of a funnel. | Layer | Question | Cleared the bar | Strength | Of those who passed | | --- | --- | --- | --- | --- | | 1. Clarity | Do they understand what you do? | 15/15 | 84% | 4 without hesitation, 11 with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 15/15 | 100% | all without hesitation | | 3. Value | Do they actually want it? | 12/15 | 67% | all with reservations | | 4. Differentiation | Is there a reason to pick you over the alternatives? | 6/15 | 44% | all with reservations | **Brand alignment** (a side metric, not one of the four layers) — 9/15, 56% strength (all with reservations). Does the page read like the company you actually are? **Fix first: Differentiation.** Earliest failing layer, walking the sequence in order — not simply the lowest score. --- ## 02 · What to change, layer by layer Ordered worst-first. Specific edits, not a restatement of the score. ### Differentiation **Add a comparison line under the 1 Gbit/s paragraph contrasting the gateway with IPsec or WireGuard tunnels.** 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. *effort medium · impact high · tested against Give a reason to choose you* **Add a line under the four feature tiles naming who else offers this and why choose you.** 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. *effort low · impact high · tested against Give a reason to choose you* **Replace the bare 1 Gbit/s and 10 Gbit/s figures with tested conditions and packet sizes.** 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. *effort medium · impact medium · tested against Proof next to the claim* ### Value **Add a customer result line near "Get my proposal" with sector, site count and outcome.** No named reference appears anywhere, so interest stops short of budget. One production deployment with a measurable result closes the gap. *effort medium · impact high · tested against Proof next to the claim* **Merge "Get my proposal" and "Talk to an expert" into one primary action.** 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. *effort low · impact medium · tested against One clear next action* ### Clarity **State the recommended firewall placement in the install paragraph instead of "in front of or behind".** Offering both positions without a default leaves the network engineer to design the topology themselves. Name the recommended placement and when the alternative applies. *effort low · impact medium · tested against Answer the live objection* ### Brand alignment (side metric) **Replace or supplement the Red Hat, Advantech, OnLogic and NIST logo row with a named deployment.** 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. *effort medium · impact high · tested against Proof next to the claim* **Add a short business-outcome paragraph after the subheading, aimed at the budget holder.** 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. *effort medium · impact medium · tested against Name the audience* **Add a line under the install paragraph stating typical install time and downtime.** 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. *effort low · impact medium · tested against Answer the live objection* --- ## 03 · What is working ### Respondents can repeat the core offer back: quantum-safe encryption for OT without… Seven respondents restated the product accurately as a gateway appliance that wraps site-to-site OT traffic in post-quantum encryption while leaving existing hardware in place. The 'no hardware replacement' phrase was reproduced almost verbatim. > 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. > > — CMO, Enterprise Software, 501-1000 > OT links quantum-safe without ripping out hardware—real if true. Worth a 30-min call, not a purchase yet. > > — CMO, Enterprise Software, 201-500 > 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 > > — Senior CMO, Software as a Service (SaaS), 201-500 > 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. > > — Chief Marketing Officer, Technology, 501-1000 > A gateway goes in at each end of the connection... Nothing on your sites is replaced > > — Chief Marketing Officer, Technology, 201-500 > 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 > > — CMO, Enterprise Software, 501-1000 > 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. > > — Chief Marketing Officer, Technology, 501-1000 ### The opening lines name the problem and the audience without making anyone hunt Nine respondents said the problem and target audience are stated explicitly in the subheading and first two lines rather than buried in feature lists. Several noted they did not have to infer who the page was for. > 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. > > — CMO, Enterprise Software, 501-1000 > 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. > > — Senior CMO, Software as a Service (SaaS), 201-500 > 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. > > — Chief Marketing Officer, Technology, 501-1000 > Protect your critical OT traffic with quantum-safe encryption without replacing your existing hardware > > — CMO, Enterprise Software, 201-500 > 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." > > — Chief Marketing Officer, Technology, 201-500 > 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." > > — Senior CMO, Software as a Service (SaaS), 201-500 --- ## 04 · What the personas said ### Deployment specifics go unanswered: firewall placement and install disruption Two respondents could not determine the recommended firewall topology placement from the page, and one said the non-disruptive install claim needs verification from an existing utility or industrial customer. > 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. > > — Senior CMO, Software as a Service (SaaS), 201-500 ### The industrial-only proof makes relevance outside OT unclear One respondent said non-industrial customer logos are needed before the page reads as relevant to a SaaS context. > 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 > > — Senior CMO, Software as a Service (SaaS), 201-500 ### No named customer exists anywhere on the page, and it stalls the decision Eight respondents flagged the absence of a named utility or operator reference. They said one production reference would convert interest to budget, and that its absence would lose the deal to a competitor showing an operator logo. > 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. > > — CMO, Enterprise Software, 501-1000 > 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. > > — CMO, Enterprise Software, 501-1000 > 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. > > — CMO, Enterprise Software, 501-1000 > No customer names, no numbers on price or actual deployments, so it's a maybe not a pick. > > — CMO, Enterprise Software, 201-500 > 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 > > — CMO, Enterprise Software, 501-1000 > "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. > > — Chief Marketing Officer, Technology, 201-500 ### The performance specs are unbenchmarked against the VPNs buyers already run Three respondents said the throughput and latency numbers sit in isolation with no head-to-head comparison to IPsec or WireGuard, no load testing evidence, and no long-term cost detail. > 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 > > — Chief Marketing Officer, Technology, 201-500 > "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 > > — Chief Marketing Officer, Technology, 201-500 > 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 > > — CMO, Enterprise Software, 501-1000 ### Partner and standards logos read as borrowed credibility from an early-stage company 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. > 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. > > — Chief Marketing Officer, Technology, 201-500 > 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. > > — Senior CMO, Software as a Service (SaaS), 501-1000 > 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 > > — CMO, Enterprise Software, 501-1000 > 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. > > — Senior CMO, Software as a Service (SaaS), 201-500 > 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. > > — CMO, Enterprise Software, 501-1000 ### The page is pitched at network engineers and gives a C-suite buyer nothing Three respondents described the tone as a technical vendor pitch for OT engineers, missing the business-level or commercial framing a decision-maker would need. > 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. > > — Senior CMO, Software as a Service (SaaS), 201-500 > 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 > > — CMO, Enterprise Software, 501-1000 --- ## 05 · The hardest read An adversarial pass over the findings. Every claim below was checked against the panel's own answers; unsupported ones were dropped. - **The page's clarity win is cosmetic: people understand the offer and still cannot act on it.** *(high)* 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.** *(high)* 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.** *(high)* 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.** *(high)* 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.** *(high)* 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.** *(medium)* 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. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | Chief Marketing Officer | Technology | 201-500 | | 2 | CMO | Enterprise Software | 501-1000 | | 3 | Senior CMO | Software as a Service (SaaS) | 201-500 | | 4 | Chief Marketing Officer | Technology | 501-1000 | | 5 | CMO | Enterprise Software | 201-500 | | 6 | Senior CMO | Software as a Service (SaaS) | 501-1000 | | 7 | Chief Marketing Officer | Technology | 201-500 | | 8 | CMO | Enterprise Software | 501-1000 | | 9 | Senior CMO | Software as a Service (SaaS) | 201-500 | | 10 | Chief Marketing Officer | Technology | 501-1000 | | 11 | CMO | Enterprise Software | 201-500 | | 12 | Senior CMO | Software as a Service (SaaS) | 501-1000 | | 13 | Chief Marketing Officer | Technology | 201-500 | | 14 | CMO | Enterprise Software | 501-1000 | | 15 | Senior CMO | Software as a Service (SaaS) | 201-500 | --- ## 07 · Before you act on this The methodology is real, and the critique is directional. What a simulated persona cannot have is a live budget, a renewal coming up, or a boss asking about this quarter. **Validate anything you're betting on with real ICPs who are actually in-market.** Being wrong is more expensive than you think. Finding out is cheaper than you'd guess. Wynter runs message testing with verified B2B professionals — trusted by HubSpot, RingCentral, Shopify, Cognism, Paddle, Veeam, Rippling and Miro. This report is kept for 60 days from 2026-09-26, then deleted along with the personas and their answers.