Clarity
Do they understand what you do?
15 could name what kind of product this is, unprompted.
https://rlr-passenger.vercel.app/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?
14 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: automation governance. 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.
Two respondents read the page as a small, early-stage vendor good at positioning but technically unproven, with a public sector orientation rather than manufacturing expertise. 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 buyer cannot tell whether checking each system "without asking that system's vendor" needs vendor cooperation, new hardware, or ripping out existing kit. Say how data arrives, which vendor types are already connected, and how long connecting one takes.
Why: The cost claim for governing sensors early has no number behind it, so it reads as assertion. Give one operator's before and after on audit hours, retrofit cost, or vendors onboarded.
4 of 15 raised this
“One real customer reference showing a before/after number — audit hours cut, or an actual liability dispute resolved because the log existed — that's the only thing that turns this from a nice pitch into a business case I can take to my board.”
Why: The table is the thing that makes Passenger concrete, but it sits after several screens of claims. Put it directly under the hero so a reader sees the record before reading arguments about it.
4 of 15 raised this
“phrases like "covers all seven parts of the Automation Governance Framework" — that framework is never defined on the page, so I'm taking on faith that it's a real standard and not something the vendor invented and named themselves.”
These landed. Keep the wording when you edit around it.
The Rule/Observed/Verdict table is what makes the product legible
“the mock table with "Rule / Observed / Verdict" was the clearest bit of proof of mechanism, everything else was more about the problem than the product”
The multi-vendor scaling problem and its audience land within seconds
“The headline problem is spelled out early — "Automation governance starts at robot one. Most operators find out at robot two" — and it's reinforced by the list of specific pains (robot four costing more to integrate, insurers asking who held control)”
Respondents can state the product back as a vendor-agnostic governance and audit layer
“It's a governance layer that sits on top of your automation and IoT fleet — sensors, meters, AMRs, drones, robots — and checks every vendor's system against a single rulebook you own, logging breaches and compliance without depending on the vendor's own reporting.”
Why: "No vendor operates in our facility unless they integrate with Passenger" proves enthusiasm, not result. Add what changed for the Zoo: number of vendors governed, audit time before and after, or a permit or insurance decision the log settled.
Why: "All seven parts of the Automation Governance Framework" and the codes AG-4 and AG-6 look like names Passenger made up, so the standard carries no weight. State who wrote it, who maintains it, and name the seven parts or link them.
Why: The page never says who buys this or at what scale, so an operations director cannot confirm the page is for them. Name the role and the trigger, such as running two or more robot vendors across multiple sites.
4 of 15 raised this
“One real customer reference showing a before/after number — audit hours cut, or an actual liability dispute resolved because the log existed — that's the only thing that turns this from a nice pitch into a business case I can take to my board.”
Why: Two hero buttons split attention and neither says what happens next. Keep the walkthrough and state its length and who runs it.
2 of 15 raised this
“I'd need a line naming the P&L or risk owner directly — something like "built for the COO or ops director who signs the insurance renewal," plus a number: estate size, insurer, or dollar figure tied to a real customer, not just a logo bar.”
Why: Toronto Zoo, Kitchener and Markham read as public sector only, so an industrial operator doubts the fleet experience. Name an industrial site, robot count, or years running mixed fleets alongside those logos.
2 of 15 raised this
“The reference customers - Toronto Zoo, City of Kitchener, City of Markham, Walmart, Compass Group - suggest they've sold mostly into municipal/public sector and a couple of larger logos, which reads like early-stage traction rather than deep enterprise penetration; nothing there screams manufacturing.”
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 sells a proof artifact it never proves anyone accepted.
Six respondents leaned on the Rule/Observed/Verdict record as the differentiator, yet four asked for evidence the log was actually used in an insurance or council decision. The strongest asset on the page is an unvalidated mock-up.
The compliance claim collapses because the page never shows how data leaves independent vendors.
Four respondents named integration mechanism as the decision blocker and demanded a live multi-vendor demo before believing the claim, while five described the product as a cross-vendor audit layer. The core promise rests on the one unexplained step.
The named framework actively costs credibility rather than lending it.
Four respondents saw AG-4 and AG-6 codes with no definition of the seven parts and assumed the vendor invented the framework. Undefined jargon converted an intended authority signal into evidence of self-certification.
Nothing on the page counters the read that this is an early-stage vendor outside manufacturing.
Two respondents read the brand as young, positioning-strong and technically unproven with a public sector tilt, and four found no quantified customer outcome anywhere. Absent proof, the positioning polish itself reads as the tell.
No one can route this page to a budget holder.
Three respondents had to infer the buyer because no title, company scale or P&L owner appears, and four found no quantified before/after on audit time or liability. Clear pain with no named owner and no sizing does not open a deal.
Clarity is masking the evaluation gap, so the page will pass reviews and lose deals.
Five respondents grasped the audience instantly and five restated the product accurately, while four blocked on integration, four on missing numbers and four on the undefined framework. Every objection sits after comprehension, at the point of purchase.
No numbers or customer before/after exist to size the value
4 of 15
“One real customer reference showing a before/after number — audit hours cut, or an actual liability dispute resolved because the log existed — that's the only thing that turns this from a nice pitch into a business case I can take to my board.”
“A real before/after number — something like a documented drop in audit-prep hours or a faster vendor-four onboarding time from an existing customer — not the mocked-up table.”
“A confirmed case where the log Passenger produced was actually handed to an insurer or council and accepted as the answer to "who was in control" — not a demo table, an event that really happened”
“What would rule it out is that everything past that table is still a promise — there's no case study showing two live competing vendor systems actually being ingested and cross-checked, no numbers on how much faster robot four gets deployed, so if a competitor showed me an actual multi-vendor demo or a customer citing a specific insurance or audit outcome, I'd drop this one fast.”
How data gets out of independent vendors is the blocking unanswered question
4 of 15
“the page doesn't say how it connects to what we already run, so I'd want that answered first before booking time”
“how does Passenger actually ingest and verify signals from vendor systems it doesn't control (is it reading vendor APIs, sensor feeds, something else), what happens when a vendor won't integrate”
“Yes, it's worth a meeting — but only to watch it actually ingest two competing vendor systems live and produce that Rule/Observed/Verdict table on the spot; if that demo is real, this becomes a easy story to sell internally as "we govern the fleet once instead of relitigating it every time we buy a new machine."”
“One record, one login, that lets me answer an insurer or auditor's question in minutes instead of chasing three vendor portals - if that's real and it actually ingests our existing access control logs without a rip-and-replace, that alone justifies the call.”
The named framework is undefined and reads as vendor-invented
4 of 15
“phrases like "covers all seven parts of the Automation Governance Framework" — that framework is never defined on the page, so I'm taking on faith that it's a real standard and not something the vendor invented and named themselves.”
“Naming an actual framework standard without ever spelling out what the seven parts are is the kind of thing that makes me squint - either define it or don't wave it at me.”
“if a competitor shows up with a named standard I can verify against a third party (ISO, NIST, an insurer's own checklist) instead of a framework this same vendor invented, that competitor wins the credibility argument”
“The one thing that would pull me toward it is the sample table — "BUBS-04 Vendor A / Stay off the north path 07:00–09:00 / North path, 08:12 / Breach" — that's a concrete, vendor-agnostic artifact I could actually put in front of an insurer, and it's more specific than anything my current portals spit out. What rules it out as-is is the Toronto Zoo quote sitting alone with no case detail and the "AG-4/AG-6 Automation Governance Framework" being their own invented taxonomy with nothing independent behind it”
The Rule/Observed/Verdict table is what makes the product legible
5 of 15 · what worked
“the mock table with "Rule / Observed / Verdict" was the clearest bit of proof of mechanism, everything else was more about the problem than the product”
“The Rule/Observed/Verdict table with the Toronto Zoo quote pinned next to it would tip me toward this one over a competitor — that's a concrete artefact plus a named reference customer, which is more than most vendors give you at this stage”
“That table with rules/observed/verdict rows is the actual product, in effect: a compliance and audit record for mixed autonomous fleets.”
“The one thing that would pull me toward it is the sample table — "BUBS-04 Vendor A / Stay off the north path 07:00–09:00 / North path, 08:12 / Breach" — that's a concrete, vendor-agnostic artifact I could actually put in front of an insurer, and it's more specific than anything my current portals spit out. What rules it out as-is is the Toronto Zoo quote sitting alone with no case detail and the "AG-4/AG-6 Automation Governance Framework" being their own invented taxonomy with nothing independent behind it”
“The thing that would actually pull it onto my shortlist is the record example itself — the table with "BUBS-04 Vendor A / Stay off north path 07:00–09:00 / North path, 08:12 / Breach" is concrete in a way most vendor pages aren't; it shows me the actual artifact I'd hand to an insurer or council, not just a promise of one.”
“The thing that would actually pick this one over a competitor is the Rule/Observed/Verdict table with real-looking rows like "BUBS-04 Vendor A — Stay off the north path 07:00–09:00 — North path, 08:12 — Breach." That's concrete enough to picture in a renewal meeting”
Respondents can state the product back as a vendor-agnostic governance and audit layer
4 of 15 · what worked
“It's a governance layer that sits on top of your automation and IoT fleet — sensors, meters, AMRs, drones, robots — and checks every vendor's system against a single rulebook you own, logging breaches and compliance without depending on the vendor's own reporting.”
“It's a governance layer that sits over a mixed fleet of robots and IoT devices, checking each system's behavior against rules you define and keeping an independent, dated audit log you control rather than the vendor.”
“It's a cross-vendor rules and audit layer for mixed robot/IoT fleets — basically a compliance engine that checks each robot or sensor against a rulebook you write once, and keeps the log yourself instead of relying on the vendor's portal.”
“It's a governance layer that sits on top of whatever robots and IoT devices we already run - checks each machine's behaviour against rules we set, logs it, and keeps that record independent of the vendors.”
The buyer is never named by title, scale, or P&L ownership
2 of 15
“I'd need a line naming the P&L or risk owner directly — something like "built for the COO or ops director who signs the insurance renewal," plus a number: estate size, insurer, or dollar figure tied to a real customer, not just a logo bar.”
“I'd want a line naming the actual buyer title — 'built for VPs of Operations managing mixed robot fleets across sites' — rather than making me infer it from the vertical bullets, plus a concrete headcount or site-count example so I can see if the scale matches mine.”
The multi-vendor scaling problem and its audience land within seconds
5 of 15 · what worked
“The headline problem is spelled out early — "Automation governance starts at robot one. Most operators find out at robot two" — and it's reinforced by the list of specific pains (robot four costing more to integrate, insurers asking who held control)”
“The problem is stated fast, right in the subhead: "Automation governance starts at robot one. Most operators find out at robot two."”
“the section headers do the diagnostic work for you: "Nobody can say what the first robot returned," "Robot four costs more to add than robot one," "When two systems conflict, the question lands on you."”
“The problem was clear fast: "Every vendor sold you a robot. Nobody sold you the rules" — that section header, plus the follow-on bullets about robot four costing more to add and insurers asking who held control, laid out the pain in about ten seconds of reading.”
The brand reads as young and unproven, with no manufacturing credibility
2 of 15
“The reference customers - Toronto Zoo, City of Kitchener, City of Markham, Walmart, Compass Group - suggest they've sold mostly into municipal/public sector and a couple of larger logos, which reads like early-stage traction rather than deep enterprise penetration; nothing there screams manufacturing.”
“it reads like a framework they invented and are trying to make sound standard.”
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.







