Clarity
Do they understand what you do?
15 could name what kind of product this is, unprompted.
https://www.cplaneai.com/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?
14 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: Open Automation Control Systems. They said:
14 couldn't name one; 1 got it right.
Four separate measures, not stages: all 15 personas answered all four questions. Each square is one persona.
15 of 15 recognized the kind of company behind the page, in a tone written for them. 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: The logo strip under "Trusted by leading operators and partners" reads as borrowed scale because nothing says what was deployed. Add site, scope and duration — how many control loops, which unit, since when — beside the names.
4 of 15 raised this
“are the one thing that would pull me toward a call over a competitor with no logos, because that's a harder claim to fake than "documented cost reductions of over 50%,"”
Why: "Up to 50% lower cost of ownership" is repeated across three role sections with no methodology or named site, so readers suspend judgment rather than book a call. Replace one repetition with a line-item comparison of hardware, software and maintenance at a…
8 of 15 raised this
“A named reference plant running this in production for 2+ years that I can actually call and ask about downtime and real cost numbers - not a case study PDF, an actual phone call with their engineer.”
Why: Readers cannot tell whether the product replaces existing controllers or runs alongside them; the stack position is pieced together from scattered terms. Add a line naming the hardware it runs on and what it displaces.
3 of 15 raised this
“Phrases like "production-proven deployments, not pilots" and "Advanced control through analytics and AI" are the kind of lines that sound like product description but are really just reassurance copy - they don't tell me what runs on the controller, what the failover mechanism actually is, or how the O-PAS conformance was tested, so I had to infer the architecture from scattered nouns (IEC 61131-3, OPC UA, COPA 500) rather than from any single clear statement of what the thing is.”
These landed. Keep the wording when you edit around it.
Role-based segmentation lets readers place themselves within seconds
“they literally segment readers with tabs: "For Control Engineers / For Automation Leaders / For Plant Managers / For System Integrators." I didn't have to hunt — I clicked into Plant Managers and it opened with "You own the risk" which is exactly my seat”
IEC 61131-3 and OPC UA compatibility is the one differentiator respondents could name
“The IEC 61131-3 and OPC UA / Ignition compatibility line is the one concrete technical detail that would keep it on the shortlist - that's a real standard, not marketing fluff”
The vendor-neutral open control category itself lands, pending refinery proof
“They sell an open, software-defined automation/control system meant to replace proprietary DCS setups in plants — basically a vendor-neutral control platform (IEC 61131-3, OPC UA, integrates with Ignition) with built-in cybersecurity”
Why: EvalKit is the de-risking mechanism competitors do not offer, but it appears nowhere in the visible copy above the fold or in the role sections. Name it, state what arrives, what it costs, and how long an evaluation takes.
4 of 15 raised this
“are the one thing that would pull me toward a call over a competitor with no logos, because that's a harder claim to fake than "documented cost reductions of over 50%,"”
Why: Standards compatibility is the one thing readers can name as concretely different from proprietary DCS, yet it sits buried as the second bullet under For Control Engineers. Say it near the hero: existing 61131-3 logic and OPC UA HMIs run unchanged.
4 of 15 raised this
“are the one thing that would pull me toward a call over a competitor with no logos, because that's a harder claim to fake than "documented cost reductions of over 50%,"”
Why: "Production-proven deployments at major global operators, not pilots, not proofs of concept" asserts exactly the thing readers doubt. Name one refinery or process plant, the year it went live, and what it controls.
8 of 15 raised this
“A named reference plant running this in production for 2+ years that I can actually call and ask about downtime and real cost numbers - not a case study PDF, an actual phone call with their engineer.”
No specific edits needed here — this layer held up.
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 central economic claim is dead on arrival, so everything built on it collapses.
Nine of 15 rejected or suspended judgment on the 50% cost-reduction and TCO claims, with one noting it is repeated four times without a single source. Repetition without a methodology reads as padding, not evidence.
Marquee logos are actively damaging credibility, not building it.
Three respondents read ExxonMobil and Petrobras as a mid-size vendor borrowing scale it lacks because no deployment detail accompanies them. Naming customers while withholding deployment facts invites the suspicion that there is nothing to show.
Strong targeting is being wasted: readers arrive oriented and then hit a proof vacuum.
Nine cited role-based segmentation as letting them place themselves instantly, yet nine rejected the cost claims and four could not locate the product in the stack. The page wins attention and then has nothing verifiable to spend it on.
No amount of additional copy will move this page forward — the gate is sourcing, not messaging.
Respondents framed named reference sites and a TCO breakdown as the specific condition for a discovery call. Rewriting claims will not clear a gate defined entirely by missing external evidence.
The page never states what it replaces, leaving buyers unable to scope a purchase.
Four respondents could not determine CPLANE.ai's layer in the stack or whether COPA 500 replaces or supplements existing controllers, piecing mechanics together from scattered technical terms. Buyers cannot budget or plan a migration they cannot define.
The single named differentiator is standards compliance, which is table stakes, not advantage.
Four respondents could name only IEC 61131-3 and OPC UA compatibility as concrete differentiation, and one noted even that is undercut by absent deployment proof. A protocol list any vendor can claim is not a moat.
IEC 61131-3 and OPC UA compatibility is the one differentiator respondents could name
4 of 15 · what worked
“The IEC 61131-3 and OPC UA / Ignition compatibility line is the one concrete technical detail that would keep it on the shortlist - that's a real standard, not marketing fluff”
“every big number is unsourced and repeated rather than proven: ">50% lower cost of ownership" and "production-proven deployments at major global operators" appear four times across the personas with no named refinery, no O-PAS conformance certificate, no case study link”
“They sell an open, software-defined automation/control platform meant to replace or sit alongside proprietary DCS systems — think open process control (O-PAS style architecture, they mention COPA 500 and O-PAS High Availability) with IEC 61131-3 programming and OPC UA/Ignition integration, so control engineers aren't locked into one vendor's hardware and software stack.”
“The one thing that would actually pull me toward this versus a generic "open automation" pitch is the specificity of "Develop control applications using familiar IEC 61131-3 programming languages" plus "Integrated with... any OPC UA-compliant platform of your choice" - that's a real interoperability claim my engineers can go test, not marketing fluff”
Customer logos raise credibility but read as borrowed without deployment detail
4 of 15
“are the one thing that would pull me toward a call over a competitor with no logos, because that's a harder claim to fake than "documented cost reductions of over 50%,"”
“the name-dropping of ExxonMobil, Petrobras, and the U.S. Air Force as "trusted by" logos, plus a real product name like COPA 500, suggests they've landed a handful of serious pilots with big operators but are still small enough to need those logos to borrow credibility.”
“if they were Honeywell-sized they wouldn't need to lean so hard on "production-proven, not pilots, not proofs of concept," that's a defensive line you write when people assume you're small.”
“there's no detail on scale or what those deployments actually looked like, so I'd want a real reference call before I believed the "production-proven" line.”
EvalKit reads as a real de-risking mechanism competitors do not offer
2 of 15 · what worked
“The "EvalKit" mention under Step 4 — "we run a structured evaluation... so your engineering team can validate the platform in your environment, against your requirements" — is the one thing that would actually tip me toward picking this over a competitor”
“The thing that would actually move a shortlist decision is the "EvalKit" mentioned in Step 4 — "we run a structured evaluation... so your engineering team can validate the platform in your environment, against your requirements." That's a concrete, low-risk mechanism to de-risk the decision, and a competitor that only offers a sales demo loses to that.”
The 50% cost-reduction claim is not believed because no named reference site backs it
8 of 15
“A named reference plant running this in production for 2+ years that I can actually call and ask about downtime and real cost numbers - not a case study PDF, an actual phone call with their engineer.”
“I'd want named reference plants in oil and gas specifically, not just Petrobras/ExxonMobil as logos, and a real TCO breakdown before I take this further than a first meeting”
“I wouldn't move past that first conversation without named reference sites and a real TCO breakdown, not just the claim repeated across four different personas on the page.”
“One named operator — ideally a refinery or process plant our scale — with a documented before/after: actual hardware/software/maintenance spend, downtime during migration, and time-to-payback. Give me that one reference case with real numbers instead of 'major global operators' and I'll take the strategy call seriously; without it, it's just a claim I can't take to a capital review.”
“the page gives me logos (ExxonMobil, Petrobras) and phrases like "production-proven deployments, not pilots" without a named reference site, a case study with numbers, or an architecture diagram showing how the redundancy actually fails over”
“the "50% lower cost of ownership" and "documented cost reductions of over 50%" numbers appear four separate times on this page and never once cite a source, a plant, or a methodology”
A discovery call is conditional on sourcing the numbers, not on more messaging
2 of 15
“I wouldn't move past that first conversation without named reference sites and a real TCO breakdown, not just the claim repeated across four different personas on the page.”
“I'd take the "Strategy Call" to get the sourcing behind the 50% number, see what "software-based redundancy" actually means mechanically”
What the product actually is in the stack has to be inferred
3 of 15
“Phrases like "production-proven deployments, not pilots" and "Advanced control through analytics and AI" are the kind of lines that sound like product description but are really just reassurance copy - they don't tell me what runs on the controller, what the failover mechanism actually is, or how the O-PAS conformance was tested, so I had to infer the architecture from scattered nouns (IEC 61131-3, OPC UA, COPA 500) rather than from any single clear statement of what the thing is.”
“what I couldn't tell from a quick read is exactly what hardware or software they're asking me to rip out and replace”
“is CPLANE a controller replacing my DCS controller, a middleware layer sitting on top, or an orchestration tool? The page keeps saying what it does for my business (lower TCO, no lock-in) but never says what it is in a hardware/software stack sense”
The vendor-neutral open control category itself lands, pending refinery proof
2 of 15 · what worked
“They sell an open, software-defined automation/control system meant to replace proprietary DCS setups in plants — basically a vendor-neutral control platform (IEC 61131-3, OPC UA, integrates with Ignition) with built-in cybersecurity”
“The category is real to me, but I'd still want to see the O-PAS conformance details and who's actually running COPA 500 in a refinery before I'd call it proven rather than promising.”
Role-based segmentation lets readers place themselves within seconds
8 of 15 · what worked
“they literally segment readers with tabs: "For Control Engineers / For Automation Leaders / For Plant Managers / For System Integrators." I didn't have to hunt — I clicked into Plant Managers and it opened with "You own the risk" which is exactly my seat”
“the "Who We Help" section literally splits into "For Control Engineers / For Automation Leaders / For Plant Managers / For System Integrators," so the intended reader is spelled out, not inferred”
“the hero line "Freedom from vendor lock-in. Security by design. Up to 50% lower cost of ownership" told me the problem in one screen, and the "Who We Help" section with explicit tabs for Control Engineers, Automation Leaders, Plant Managers, and System Integrators told me exactly who they're targeting without me having to infer anything.”
“the intended reader isn't left to guesswork: they literally split the page into "For Control Engineers / For Automation Leaders / For Plant Managers / For System Integrators," so I could jump straight to my own role and see the pitch tailored to me”
“the "Industrial Automation is at a Crossroads" section spells out the problem (proprietary lock-in, vendor dependency, cybersecurity bolted on) and then the "Who We Help" tabs literally name the readers: Control Engineers, Automation Leaders, Plant Managers, System Integrators.”
“The audience is spelled out explicitly too, not inferred - there are literal tabs "For Control Engineers / For Automation Leaders / Plant Managers / System Integrators" and I fall right into the Plant Manager bucket, which opens with "You own the risk. When something goes wrong, it lands on you."”
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.







