# Message test — https://proekspert.com/ After reading your page, only 6 of 15 personas could name a reason to pick you over a similar option. - **Page tested:** https://proekspert.com/ - **Audience tested against:** Roles: VP/Head of R&D, Head of Engineering, Head of Product Development, CTO, Director of Connected/Digital Products, senior technical PM, embedded software lead, product security owner. Company types: hardware OEMs and machine builders — HVAC, drives, industrial automation, energy and lab equipment, industrial vehicles — EU-market-facing, Nordics/Baltics/DACH. Size: ~200–5,000 employees, €50M–€1B. Or one business unit inside a larger group. Looking for: embedded and cloud engineering capacity without hiring, CRA/IEC 62443 compliance before deadlines, a route from standalone device to connected product with a data layer that pays for itself, and someone willing to take over legacy firmware. - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/software-design-and-data-services-proekspert-qdY77wQ > 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 | 81% | 2 without hesitation, 13 with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 10/15 | 61% | 1 without hesitation, 9 with reservations | | 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 | 47% | 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 **Replace "AI-ready" with the data path it describes.** "engineered AI-ready, governed by design" asserts a state nobody can verify. State the move it makes: siloed device data pulled into one governed layer, with a before/after on what the plant could then query. *effort medium · impact high · tested against Specifics beat superlatives* **Surface the CRA compliance case study on the homepage.** The CRA/IEC 62443 work only exists as an unlabelled case-study link and footer nav. Give it a headline block naming the deadline, the audit outcome and how long remediation took, so compliance buyers see the one thing rivals lead with. *effort medium · impact high · tested against Give a reason to choose you* **Add problem and outcome to each client example.** Logos and "Digital leaders we've guided" carry no detail on what was fixed. Under each named client, give one line of problem plus one measured result, so the reader can tell this firm apart from any other engineering vendor. *effort medium · impact medium · tested against Proof next to the claim* ### Relevance **Curate case study tiles by scenario, not by client.** The three featured links — Power BI migration, CRA compliance, roof measurement — read as a random sample. Label them by the job: legacy firmware modernization, embedded-to-cloud, device data platform, so buyers find their own situation. *effort medium · impact high · tested against Lead with the use case* **Rewrite competency tile headings as problems, not categories.** "Embedded software and systems" and "Custom software development" are category labels that overlap and leave service boundaries unclear. Lead each with the job — getting a device to talk to the cloud, meeting a security audit — then list the capability. *effort medium · impact high · tested against Lead with the use case* **Name mid-size manufacturers alongside "established global enterprises".** "established global enterprises" and the 300+ customer scale signal that smaller manufacturers are not the fit. Add a line naming the size of team or product line the engagements typically serve. *effort low · impact medium · tested against Name the audience* ### Value **Attach timelines and outcomes to the featured case studies.** The value section offers 30+ years, 150+ experts and 79 NPS — company facts, not customer results. Give each case tile a figure: weeks to audit-ready, months to first cloud deployment, defect or downtime change. *effort medium · impact high · tested against Specifics beat superlatives* **Add a measured result to the Danfoss quotes.** "A high professional level" and "react very swiftly" are praise with nothing behind them. Pair each Danfoss reference with what shipped and what improved, or cut them for testimonials that carry numbers. *effort low · impact medium · tested against Proof next to the claim* ### Brand alignment (side metric) **Move awards and recruitment badges off the buyer path.** Employer branding competes with the mission-critical positioning the hero sets up. Keep the homepage on client outcomes and relocate awards to the careers or about page. *effort low · impact low* --- ## 03 · What is working ### The headline and competency grid make the audience obvious within seconds Six respondents said the hero line, subhead and client logos immediately identify the page as serving hardware and connected-device makers. They could name the audience without scrolling. > They're a software engineering house that builds embedded/IoT systems and cloud data layers for hardware manufacturers—essentially an outsourced R&D partner for connected devices. > > — Chief Technology Officer, Laboratory Equipment, 501-1000 > the reader is implied to be someone like me — an R&D or engineering lead at a manufacturer — but it's never explicitly stated as "for R&D heads at manufacturers"; I inferred that from the client logos (Danfoss, Ericsson, GPV) and the competency list, not from a direct sentence naming the buyer > > — Head of R&D, HVAC Manufacturing, 501-1000 --- ## 04 · What the personas said ### Competency tiles name categories instead of stating the problem being solved Five respondents said the six-plus competency tiles read as a generic capability list with no problem statement, leaving service boundaries unclear. Several had to infer the business model from case studies rather than read it stated. > the page never uses the words "consultancy," "services," or "partner engagement," it just lists competencies like a product menu > > — Head of R&D, Energy Equipment, 501-1000 > The "problem," though, I had to infer rather than have stated plainly - it's a scattershot of six-plus competencies (embedded, cloud, data platforms, CX design) rather than one named pain point > > — Head of Engineering, Laboratory Equipment, 1001-5000 > The six-plus competency labels themselves - "AI-ready data platforms," "customer experience design," "user-centric digital services" - are generic consultancy phrases that could sit on almost any dev shop's site > > — Head of Engineering, Laboratory Equipment, 1001-5000 ### Compliance and CRA work is buried below the homepage hierarchy Two respondents found compliance services only in footer navigation, and the CRA/IEC 62443 deadline only surfaced inside case study links rather than on the page itself. > There's no sentence that says "if your firmware can't meet CRA by 2027, here's what we do about it" until you dig into the case study links. > > — Director of Digital Products, HVAC Manufacturing, 51-200 > so I had to go down to the footer nav ("EU CRA compliance service," "IEC 62443 compliance analysis service") to actually confirm they do the thing I need > > — Head of Product Development, HVAC Manufacturing, 201-500 ### The case studies shown do not match the scenarios respondents came with Four respondents said existing case studies address the wrong problems, wanting a scoped embedded-to-cloud example, legacy firmware modernization data, or data-platform proof equivalent to Solarstones. > The case study quotes (roof-measurement turn rate to "60-99%", "engagement increased 100%") are for completely different problems - sales tools, shop-floor UX - not legacy firmware modernization, so they don't actually give me a before/after I can map onto my problem. > > — Chief Technology Officer, Industrial Vehicles, 501-1000 > "AI-ready data platforms... governed by design" is a claim, not proof — I'd need a case study with numbers like the Solarstones one (60-99% turn rate) for a data-platform project specifically, not just embedded/IoT wins, before I'd believe it applies to us. > > — Director of Digital Products, Laboratory Equipment, 51-200 > there's no case study on the page walking through a legacy firmware modernization end-to-end with timelines, team size, or cost, so I don't actually know what "worked" looks like in practice for someone in my position. > > — VP of R&D, Industrial Automation, 201-500 ### No numbers anywhere: no timelines, costs, team sizes or outcome metrics Seven respondents said the value proposition carries no concrete figures — CRA remediation timeline or cost, delivery timelines, quality metrics, baseline methodology behind the Danfoss references, or vertical-specific outcomes. > the page gives me a Danfoss quote about "swift reaction to critical situations" and a Solarstones case with a "60-99% turn rate" that has no baseline or methodology attached > > — Head of Engineering, Laboratory Equipment, 1001-5000 > the page gives me zero numbers on delivery timelines, cost vs. an in-house hire, or defect/quality rates, just a "79 NPS" with no methodology and testimonials with no metrics attached > > — Director of Engineering, Industrial Automation, 51-200 > The one outcome that matters is a signed-off, audit-ready compliance package for a specific product line delivered inside our deadline window — not a gap analysis or a slide deck > > — Head of Product Development, HVAC Manufacturing, 201-500 > A named energy-equipment or utility client — not Danfoss by proxy, but someone in my exact vertical dealing with grid or HVAC hardware going connected — plus a one-line case outcome like 'cut connected-product time-to-market from 18 months to 6,' would make me feel they'd built this page for me instead of for generic 'smart device manufacturers.' > > — Director of Connected Products, Energy Equipment, 1001-5000 > no case study shows firmware maintenance burden solved with numbers > > — VP of R&D, Industrial Vehicles, 201-500 > there's no case study on the page walking through a legacy firmware modernization end-to-end with timelines, team size, or cost, so I don't actually know what "worked" looks like in practice for someone in my position. > > — VP of R&D, Industrial Automation, 201-500 ### Nothing on the page separates the firm from compliance-focused competitors Two respondents said client examples lack detail on problems solved or outcomes, and a named CRA case study with timeline and cost is missing versus competitors positioned on compliance. > no case study shows firmware maintenance burden solved with numbers > > — VP of R&D, Industrial Vehicles, 201-500 ### "AI-ready" and the data layer story are asserted without definition or migration path Three respondents said "AI-ready" is never defined with metrics or before/after data, and the path from siloed device data to a data layer is never explicitly stated. > What would rule them out, or at least knock them down the shortlist, is that "AI-ready" is never defined anywhere on the page—no metric, no before/after data volume or latency number, nothing like "reduced integration time by X%" > > — Chief Technology Officer, Laboratory Equipment, 501-1000 > "AI-ready data platforms... governed by design" is a claim, not proof — I'd need a case study with numbers like the Solarstones one (60-99% turn rate) for a data-platform project specifically, not just embedded/IoT wins, before I'd believe it applies to us. > > — Director of Digital Products, Laboratory Equipment, 51-200 ### Awards and recruitment badges pull the page away from the buyer audience Three respondents said employer branding and awards messaging dilutes mission-critical positioning for compliance buyers, and one added the enterprise-scale framing offers no proof of fit for mid-size manufacturers. > Where it stops feeling written for me is the pile of employer-branding badges (Family-friendly employer, Work-Happy People, Dream Employer finalist) — that's HR trying to recruit engineers, not a VP trying to de-risk a connected-product build, and it dilutes the "mission-critical" framing they lead with. > > — Director of Connected Products, Energy Equipment, 1001-5000 > right now it reads as "built for Danfoss-scale engagements," and I'd want proof they can right-size for us. > > — Director of Digital Products, Laboratory Equipment, 51-200 --- ## 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 tells visitors who it is for and then fails to tell them anything else.** *(high)* Six respondents named the audience within seconds from the hero and logos, but seven found no timelines, costs, team sizes or outcome metrics, and five read the competency tiles as a category list with no problem statement. - **Buyers are being forced to do the firm's positioning work themselves.** *(high)* Several respondents had to infer the business model from case studies, two found compliance services only in footer navigation, and three said the migration path from siloed device data to a data layer is never stated. - **The proof assets actively work against the page rather than supporting it.** *(high)* Four respondents said the case studies address the wrong problems, and two said client examples lack detail on problems solved or outcomes — so the one place the model can be inferred is also the weakest asset. - **The CRA opportunity is being handed to competitors.** *(high)* The CRA/IEC 62443 deadline surfaces only inside case study links, compliance sits in footer navigation, and two respondents specifically wanted a named CRA case study with timeline and cost against competitors positioned on compliance. - **Every differentiation claim on the page is an assertion a competitor could copy verbatim.** *(high)* "AI-ready" is never defined with metrics or before/after data, the Danfoss references carry no baseline methodology, and nothing separates the firm from compliance-focused competitors. - **The page is optimised for a recruiting and prestige audience at the buyer's expense.** *(medium)* Three respondents said employer branding and awards dilute mission-critical positioning for compliance buyers, and enterprise-scale framing offered no proof of fit for mid-size manufacturers — page real estate spent on badges instead of the missing numbers. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | Chief Technology Officer | Laboratory Equipment | 501-1000 | | 2 | Director of Connected Products | Industrial Automation | 1001-5000 | | 3 | Director of Digital Products | HVAC Manufacturing | 51-200 | | 4 | VP of R&D | Industrial Vehicles | 201-500 | | 5 | Head of R&D | Energy Equipment | 501-1000 | | 6 | Head of Engineering | Laboratory Equipment | 1001-5000 | | 7 | Director of Engineering | Industrial Automation | 51-200 | | 8 | Head of Product Development | HVAC Manufacturing | 201-500 | | 9 | Chief Technology Officer | Industrial Vehicles | 501-1000 | | 10 | Director of Connected Products | Energy Equipment | 1001-5000 | | 11 | Director of Digital Products | Laboratory Equipment | 51-200 | | 12 | VP of R&D | Industrial Automation | 201-500 | | 13 | Head of R&D | HVAC Manufacturing | 501-1000 | | 14 | Head of Engineering | Industrial Vehicles | 1001-5000 | | 15 | Director of Engineering | Energy Equipment | 51-200 | --- ## 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.