# Message test — https://dev.web.querdenkerengineering.de/de After reading your page, only 8 of 15 personas could name a reason to pick you over a similar option. - **Page tested:** https://dev.web.querdenkerengineering.de/de - **Audience tested against:** German-speaking Heads of R&D, CTOs and senior product managers at mid-sized device manufacturers in the DACH region (50-2000 employees) in medical technology, industrial automation / drive technology / energy, and measurement and lab equipment. They build connected products with embedded electronics, firmware and an IoT cloud, have a small or overloaded in-house development team, and currently work with freelancers, engineering service providers or an EMS partner's design department. They are under pressure from the EU Cyber Resilience Act, functional safety (IEC 61508, ISO 13849) and medical standards (IEC 60601, MDR), and fear vendor lock-in and missed series-production dates. NOT for: pure software/SaaS companies, consumer gadget startups without budget, or corporations with large in-house electronics departments. They read the page in German. - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/querdenker-engineering-elektronik-und-software-glZnFFs > 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? | 13/15 | 81% | 2 without hesitation, 13 with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 15/15 | 78% | all 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? | 8/15 | 52% | 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 **Add escrow agent, trigger events and access terms under the Unabhängigkeit section** "Für unsere Eigenprodukte liegen Unterlagen und Fertigungsdaten bei einer unabhängigen Stelle" never says who holds the deposit, what triggers release, or what the buyer receives. Name the escrow agent, the trigger events and the contract clause that governs… *effort medium · impact high · tested against Proof next to the claim* **Add a CRA project example with the actual documentation artifacts produced** The CRA section claims "Wir liefern, was der Cyber Resilience Act verlangt" but every case study cites SIL 3, PL e or MDR instead. Add one example naming the CRA deliverables: SBOM, vulnerability handling process, update chain evidence. *effort medium · impact high · tested against Proof next to the claim* **Replace the Eisenhower and Valéry quote with team size and current capacity** The literary aside after the phase list gives a buyer nothing to compare against other engineering firms. State how many engineers are in the Offenburg core team and when a project can start. *effort low · impact medium · tested against Give a reason to choose you* ### Clarity **Add a line under the H1 naming the buyer role and company type** Who this is for can only be guessed from the case studies. Write who you work with, for example hardware manufacturers in drive technology, energy and medical devices who must ship connected products under CRA. *effort low · impact medium · tested against Name the audience* ### Value **Replace one anonymous Auftraggeber label with a named client and a result** Every project reads "Hersteller von Antriebs- und Automatisierungstechnik" with no company, no timeline and no outcome. Name one client, the development duration and what shipped, or offer a reference call. *effort medium · impact high · tested against Specifics beat superlatives* --- ## 03 · What is working ### The offering registers in seconds as embedded product engineering with CRA compliance Ten respondents read the headline and bullets and restated the offering accurately — contract embedded engineering for regulated hardware, from architecture through field updates. Several said scope was clear in about five seconds. > a development partner/contract engineering house for regulated hardware+firmware products, not a software tool or platform I'd buy off a shelf > > — Director of Product Development, Drive Technology, 1001-5000 > an embedded systems development partner with a reusable hardware/software platform bolted on, not a standalone product I'd buy off a shelf > > — Head of R&D, Energy, 51-200 > this reads as a contract development house that takes a product from architecture through certification and into production > > — Chief Technology Officer, Measurement and Laboratory Equipment, 201-500 > outsourced R&D partner covering hardware, software, and compliance work (CRA, IEC 61508, IEC 60601) from concept through production and field support > > — Senior Product Manager, Medical Technology, 501-1000 > The headline "Systempartner für sichere vernetzte Produkte" plus the bullets - Elektronik, Firmware, Applikation, IoT-Cloud, "Von der Idee bis zum Update im Feld" - told me in five seconds this is an outsourced dev shop for connected devices > > — Senior Product Manager, Medical Technology, 501-1000 > a SIL 3 safety subsystem for a drives manufacturer, a Li-Ion battery for a medical device company - that's the kind of proof that makes me believe they can actually deliver > > — Director of Product Development, Industrial Automation, 1001-5000 > The headline "Systempartner für sichere vernetzte Produkte" plus the bullet list - Elektronik, Firmware, Applikation, IoT-Cloud, "Von der Idee bis zum Update im Feld" - told me straight away this is a full-stack embedded dev shop > > — Senior Product Manager, Measurement and Laboratory Equipment, 501-1000 > They're an engineering services firm in Offenburg doing embedded electronics, firmware and IoT-cloud development for connected devices - hardware design, embedded software, safety functions (SIL/PL), and CRA compliance work (updates, vulnerability handling, evidence). > > — Chief Technology Officer, Energy, 201-500 ### CRA compliance is the line that lands Five respondents singled out the explicit naming of the CRA obligation as a concrete pain point stated early rather than vague innovation language, and one valued compliance built in from architecture rather than bolted on. > The CRA angle is spelled out explicitly too: "Wir liefern, was der Cyber Resilience Act verlangt" with updates, vulnerability handling, and evidence/documentation named directly - that's exactly my current problem > > — Head of R&D, Energy, 51-200 > The problem gets sharpened further down under the Cyber Resilience Act section — "Updates über Jahre liefern, Schwachstellen melden und schließen, alles nachweisen" — which names a very concrete pain (CRA compliance) rather than vague "innovation" talk. > > — Chief Technology Officer, Measurement and Laboratory Equipment, 201-500 > the real change is CRA compliance getting baked in from architecture onward instead of bolted on late — "Wir planen es ab der Architektur ein und begleiten es bis in den Betrieb" > > — Head of R&D, Drive Technology, 51-200 > Updates über Jahre liefern, Schwachstellen melden und schließen, alles nachweisen: Der Cyber Resilience Act macht das für vernetzte Geräte zur Pflicht > > — Head of R&D, Industrial Automation, 51-200 ### Case studies in drive safety and medical devices map to the reader's regulated-hardware… Three respondents said the named project examples demonstrated capability across safety certifications and device types and connected directly to their own regulated-hardware context. > The reader isn't named outright as "Head of Product Development at a drive manufacturer" but I could infer it from the project examples - drive safety subsystems, medical device battery packs - which map closely to my own world > > — Director of Product Development, Drive Technology, 1001-5000 > a SIL 3 safety subsystem for a drives manufacturer, a Li-Ion battery for a medical device company - that's the kind of proof that makes me believe they can actually deliver > > — Director of Product Development, Industrial Automation, 1001-5000 --- ## 04 · What the personas said ### Who the page is for, and who is behind it, is never stated outright Three respondents said the target reader is only inferable from case studies, company identity is scattered across sections rather than stated upfront, and an internal phase-list reads like documentation rather than customer-facing copy. > Who it's for is never stated explicitly as a persona ("for R&D heads at drive/automation companies") — I had to infer that from the project examples > > — Head of R&D, Drive Technology, 51-200 > the phase-list in the middle (Anfrage, Planung, Entwicklung, Verifikation, Serie...) which reads more like an internal process map than customer-facing copy > > — Director of Product Development, Industrial Automation, 1001-5000 > the friction was that identity is scattered across sections (platform blocks like qdCloud/qdCoreX, the CRA paragraph, the project case studies) rather than stated in one line up front > > — Head of R&D, Drive Technology, 51-200 ### Every claim is unquantified and every case study is anonymous Seven respondents found no metrics on compliance cost or timeline, no named client companies, no outcomes, and no audit or certification sign-off. Several said they would require reference calls to production customers before committing. > I'd want to know who at a comparable drive manufacturer is actually running production with them, not just a case-study writeup > > — Director of Product Development, Drive Technology, 1001-5000 > the page gives me no numbers - no typical timeline reduction, no cost comparison to doing it with my current suppliers, no case study showing a CRA audit actually passed using their qdCloud/qdCoreX stack > > — Head of R&D, Energy, 51-200 > nothing here is quantified: no timeline, no cost comparison to what freelancers cost us, no named medtech client I can call > > — Senior Product Manager, Medical Technology, 501-1000 > That's a named application area with the right standards attached, which is more than most competitors put on a landing page. What would rule them out, or at least stall me, is that it's a single project summary with no client name, no outcome metric > > — Senior Product Manager, Medical Technology, 501-1000 > the page asserts "Wir liefern, was der Cyber Resilience Act verlangt" without showing me an audit, a certification body sign-off, or even one client reference specifically for CRA evidence packages > > — Chief Technology Officer, Energy, 201-500 > A reference customer our size who'll actually talk to me about a CRA-relevant product they've maintained for years - real update cadence, a disclosed vulnerability handled end-to-end, and who ate the cost when something slipped > > — Senior Product Manager, Measurement and Laboratory Equipment, 501-1000 > the page only gives me one relevant named reference, the Li-Ion battery project under IEC 60601-1/62133-2/MDR, and no client name, no outcome numbers, no timeline or cost comparison > > — Director of Product Development, Medical Technology, 1001-5000 ### The CRA evidence does not match the CRA claim Two respondents noted the case studies cite SIL/PL and MDR rather than CRA, and asked for actual CRA documentation artifacts before treating compliance as a differentiator. > the CRA claims are still just assertions on the page ("Wir liefern, was der Cyber Resilience Act verlangt") with no artifact shown — no sample traceability matrix, no vulnerability-handling SLA, nothing I can compare against a competitor's documentation package > > — Head of R&D, Drive Technology, 51-200 > it would rule them out, or at least drop them behind a competitor, that none of the three case studies actually show a CRA evidence trail - they're SIL/PL and MDR > > — Chief Technology Officer, Energy, 201-500 ### The page is written for engineers and leaves budget approvers out Two respondents found the acronym density hard for non-technical approvers, and one noted no team size or capacity signals to judge partnership fit. > it's dense with acronyms (FSoE, SIL 3, PL e, semf, StateSmith) and reads like a case-study log rather than polished sales copy. That's actually fine by me since I can parse it, but there's no plain-language framing for whoever above me signs the budget > > — Senior Product Manager, Medical Technology, 501-1000 > there's no team size, capacity, or pricing signal that would let me size them up as a partner for our scale > > — Director of Product Development, Measurement and Laboratory Equipment, 1001-5000 ### The escrow and IP-ownership pitch is named as the differentiator but has no mechanism… Three respondents named anti-lock-in escrow as what sets the firm apart from typical services shops. Five others said the same claim is unusable without a named escrow agent, triggers, or contract terms. > the "Unabhängigkeit" / escrow point ("liegen Unterlagen und Fertigungsdaten bei einer unabhängigen Stelle") is stated as a policy line with no named escrow agent or contract mechanism > > — Director of Product Development, Drive Technology, 1001-5000 > "Was wir für Sie entwickeln, geht an Sie über: Schaltplan, Layout, Quellcode, Fertigungsunterlagen" and the escrow-style backup for their own platform if they can't deliver - that's a concrete differentiator against a typical services shop, because vendor lock-in and IP ownership are real risks I've been burned by before > > — Head of R&D, Energy, 51-200 > the "unabhängige Stelle" escrow line for source/Fertigungsunterlagen — it's a good instinct but it's one vague sentence with no named escrow agent, trigger conditions, or contract mechanism > > — Chief Technology Officer, Measurement and Laboratory Equipment, 201-500 > the "Unabhängigkeit" pitch about IP escrow if they "können nicht mehr liefern" is a nice risk-mitigation line but it's undefined - who's the independent Stelle, what triggers release, is that in the contract or just marketing > > — Senior Product Manager, Medical Technology, 501-1000 > Für unsere Eigenprodukte liegen Unterlagen und Fertigungsdaten bei einer unabhängigen Stelle. Können wir nicht mehr liefern, bekommen Sie Zugriff darauf. > > — Director of Product Development, Industrial Automation, 1001-5000 > A reference customer our size who'll actually talk to me about a CRA-relevant product they've maintained for years - real update cadence, a disclosed vulnerability handled end-to-end, and who ate the cost when something slipped > > — Senior Product Manager, Measurement and Laboratory Equipment, 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 single strongest hook — CRA compliance — is unsupported by its own evidence, which turns the lead claim into a liability.** *(high)* Five respondents singled out CRA as the line that lands, but two found the case studies cite SIL/PL and MDR rather than CRA and asked for actual CRA artifacts. The proof contradicts the promise. - **Clarity is being mistaken for persuasion: readers understand the offer instantly and still have nothing to act on.** *(high)* Ten respondents restated the offering accurately in about five seconds, yet seven found no metrics, no named clients, no outcomes, and no certification sign-off. Fast comprehension of an unevidenced claim just accelerates the exit. - **The stated differentiator is unusable as written and cannot survive a competitive comparison.** *(high)* Three respondents named escrow and IP ownership as what sets the firm apart, but five said the claim is unusable without a named escrow agent, triggers, or contract terms. A differentiator nobody can verify is a slogan. - **The page cannot clear a buying committee because it never addresses the person who signs.** *(high)* Two respondents found acronym density hard for non-technical approvers, one noted no team size or capacity signals, and seven demanded cost and timeline metrics before committing. Nothing here converts engineer interest into budget. - **Anonymity undercuts the one section doing relevance work.** *(medium)* Three respondents said the drive-safety and medical-device examples connected to their own regulated-hardware context, but seven noted the case studies name no clients and report no outcomes. Relatable scenarios without attribution read as hypotheticals. - **Basic identity gaps make the firm look smaller and less credible than the work described.** *(medium)* Two respondents said the target reader is only inferable from case studies, company identity is scattered rather than stated upfront, and an internal phase-list reads like documentation. Two more found no capacity signals to judge partnership fit. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | Director of Product Development | Drive Technology | 1001-5000 | | 2 | Head of R&D | Energy | 51-200 | | 3 | Chief Technology Officer | Measurement and Laboratory Equipment | 201-500 | | 4 | Senior Product Manager | Medical Technology | 501-1000 | | 5 | Director of Product Development | Industrial Automation | 1001-5000 | | 6 | Head of R&D | Drive Technology | 51-200 | | 7 | Chief Technology Officer | Energy | 201-500 | | 8 | Senior Product Manager | Measurement and Laboratory Equipment | 501-1000 | | 9 | Director of Product Development | Medical Technology | 1001-5000 | | 10 | Head of R&D | Industrial Automation | 51-200 | | 11 | Chief Technology Officer | Drive Technology | 201-500 | | 12 | Senior Product Manager | Energy | 501-1000 | | 13 | Director of Product Development | Measurement and Laboratory Equipment | 1001-5000 | | 14 | Head of R&D | Medical Technology | 51-200 | | 15 | Chief Technology Officer | Industrial Automation | 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-19, then deleted along with the personas and their answers.