# Message test — https://www.cplaneai.com/ After reading your page, only 7 of 15 personas could name a reason to pick you over a similar option. - **Page tested:** https://www.cplaneai.com/ - **Audience tested against:** Control Engineers and plant managers at Oil and Gas companies of > 10,000 employees who need to upgrade their control systems to make them more cyber secure and to break free from vendor lock-in. These customers have a preferred control system vendor but they are frustrated that they are at the whims of these vendors for innovation and products. The other frustration is that they cannot swap out a piece of hardware if it's no longer supported. - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/open-automation-delivered-cplane-r4lrRjQ > 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 | 78% | all with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 15/15 | 97% | 13 without hesitation, 2 with reservations | | 3. Value | Do they actually want it? | 14/15 | 74% | all with reservations | | 4. Differentiation | Is there a reason to pick you over the alternatives? | 7/15 | 48% | all with reservations | **Brand alignment** (a side metric, not one of the four layers) — 15/15, 78% 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 **Attach deployment detail to the ExxonMobil and Petrobras logos.** 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. *effort medium · impact high · tested against Proof next to the claim* **Give EvalKit a named section with what it includes.** 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. *effort medium · impact high · tested against Answer the live objection* **Promote IEC 61131-3 and OPC UA into a top-level heading.** 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. *effort low · impact high · tested against Give a reason to choose you* ### Value **Source the 50% cost claim once, with a before/after breakdown.** "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… *effort medium · impact high · tested against Proof next to the claim* **Define "production-proven deployments" with a refinery reference.** "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. *effort medium · impact high · tested against Specifics beat superlatives* ### Clarity **State where COPA 500 sits in the control stack.** 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. *effort low · impact high · tested against Show the product early* --- ## 03 · What is working ### The vendor-neutral open control category itself lands, pending refinery proof Two respondents restated the positioning cleanly as an open platform replacing proprietary DCS with built-in security, and judged the category real. One conditioned acceptance on evidence of actual refinery deployments. > 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 > > — Plant Operations Manager, Oil and Gas, 5000+ > 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. > > — Control Engineer, Refining, 5000+ ### Role-based segmentation lets readers place themselves within seconds Nine respondents named the role-segmented navigation and hero message as the reason they could immediately tell who the page was for. Several noted the problem was stated outright rather than left to inference. > 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 > > — Plant Operations Manager, Oil and Gas, 5000+ > 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 > > — Control Engineer, Refining, 5000+ > 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. > > — Senior Control Engineer, Process Manufacturing, 5000+ > 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 > > — Lead Control Engineer, Oil and Gas, 5000+ > 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. > > — Operations Manager, Process Manufacturing, 5000+ > 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." > > — Plant Operations Manager, Oil and Gas, 5000+ ### IEC 61131-3 and OPC UA compatibility is the one differentiator respondents could name Four respondents cited standards compatibility as a concrete technical differentiator against proprietary DCS languages. One of them noted the compatibility claim itself is undercut by absent deployment proof. > 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 > > — Operations Manager, Process Manufacturing, 5000+ > 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 > > — Control Engineer, Refining, 5000+ > 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. > > — Senior Control Engineer, Process Manufacturing, 5000+ > 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 > > — Lead Control Engineer, Oil and Gas, 5000+ ### EvalKit reads as a real de-risking mechanism competitors do not offer Two respondents singled out the EvalKit structured evaluation offer as lowering the risk of committing to the platform. One added that the surrounding claims repeated around it lack specificity. > 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 > > — Plant Operations Manager, Oil and Gas, 5000+ > 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. > > — Senior Control Engineer, Process Manufacturing, 5000+ --- ## 04 · What the personas said ### What the product actually is in the stack has to be inferred Four respondents could not determine CPLANE.ai's layer in the hardware/software stack or whether COPA 500 replaces or supplements existing controllers, saying product mechanics had to be pieced together from scattered technical terms. > 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. > > — Lead Control Engineer, Oil and Gas, 5000+ > what I couldn't tell from a quick read is exactly what hardware or software they're asking me to rip out and replace > > — Plant Manager, Refining, 5000+ > 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 > > — Plant Operations Manager, Oil and Gas, 5000+ ### The 50% cost-reduction claim is not believed because no named reference site backs it Nine respondents rejected or suspended judgment on the TCO and cost claims, demanding named oil-and-gas references, before/after numbers, or a methodology. One noted the cost claim is repeated four times without a single cited source. > 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. > > — Operations Manager, Process Manufacturing, 5000+ > 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 > > — Plant Operations Manager, Oil and Gas, 5000+ > 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. > > — Control Engineer, Refining, 5000+ > 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. > > — Senior Control Engineer, Process Manufacturing, 5000+ > 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 > > — Lead Control Engineer, Oil and Gas, 5000+ > 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 > > — Plant Manager, Refining, 5000+ ### A discovery call is conditional on sourcing the numbers, not on more messaging One respondent said they would take a discovery call if the cost reduction and redundancy claims were sourced and explained. Others framed named reference sites and a TCO breakdown as the specific gate to moving forward. > 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. > > — Control Engineer, Refining, 5000+ > I'd take the "Strategy Call" to get the sourcing behind the 50% number, see what "software-based redundancy" actually means mechanically > > — Plant Manager, Refining, 5000+ ### Customer logos raise credibility but read as borrowed without deployment detail Respondents said ExxonMobil and Petrobras logos make the vendor more credible than proof-free competitors, while three read them as a mid-size vendor borrowing scale it lacks, since no deployment scale or reference detail accompanies the names. > 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%," > > — Operations Manager, Process Manufacturing, 5000+ > 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. > > — Senior Control Engineer, Process Manufacturing, 5000+ > 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. > > — Operations Manager, Process Manufacturing, 5000+ > 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. > > — Operations Manager, Process Manufacturing, 5000+ --- ## 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 central economic claim is dead on arrival, so everything built on it collapses.** *(high)* 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.** *(high)* 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.** *(high)* 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.** *(high)* 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.** *(high)* 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.** *(medium)* 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. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | Operations Manager | Process Manufacturing | 5000+ | | 2 | Plant Operations Manager | Oil and Gas | 5000+ | | 3 | Control Engineer | Refining | 5000+ | | 4 | Senior Control Engineer | Process Manufacturing | 5000+ | | 5 | Lead Control Engineer | Oil and Gas | 5000+ | | 6 | Plant Manager | Refining | 5000+ | | 7 | Operations Manager | Process Manufacturing | 5000+ | | 8 | Plant Operations Manager | Oil and Gas | 5000+ | | 9 | Control Engineer | Refining | 5000+ | | 10 | Senior Control Engineer | Process Manufacturing | 5000+ | | 11 | Lead Control Engineer | Oil and Gas | 5000+ | | 12 | Plant Manager | Refining | 5000+ | | 13 | Operations Manager | Process Manufacturing | 5000+ | | 14 | Plant Operations Manager | Oil and Gas | 5000+ | | 15 | Control Engineer | Refining | 5000+ | --- ## 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-08-26, then deleted along with the personas and their answers.