# Message test — https://www.nazdaq-it.com/ After reading your page, only 2 of 15 personas could name a reason to pick you over a similar option. - **Page tested:** https://www.nazdaq-it.com/ - **Audience tested against:** Small/mid size manufacturer enterprises.. admins and cios. - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/nazdaq-your-erp-innovation-partner--QND0X4 > 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 | 79% | 1 without hesitation, 14 with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 15/15 | 90% | 8 without hesitation, 7 with reservations | | 3. Value | Do they actually want it? | 11/15 | 60% | all with reservations | | 4. Differentiation | Is there a reason to pick you over the alternatives? | 2/15 | 31% | all with reservations | **Brand alignment** (a side metric, not one of the four layers) — 13/15, 70% 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 'Real problems, proven solutions' with a stated-position claim.** 'Real problems, proven solutions' and 'One Platform. A Million Use Cases' are the two lines carrying the differentiation argument, and both are claims a competitor could copy verbatim. Respondents landed on architecture and LN-specific depth as the separator; state it in the heading instead — e.g. how many years of Infor LN/Baan work, the number of LN print event types supported, or that output is driven from LN print events rather than exported and reprocessed downstream. 'A Million Use… *effort medium · impact high · tested against Specifics beat superlatives* **Move native ION and Infor OS integration into the hero subhead.** The only thing on this page that respondents could name as a reason to choose this vendor — native Infor OS/ION integration and LN-level expertise — is buried as a single bullet ('Native Infor OS & ION') inside the LN Data Integration card, six modules down. The hero currently says 'Pre-built solutions for Infor LN, M3, and Infor CloudSuite ... all in one unified software suite', which any Infor-adjacent vendor or generic ETL tool could write. Rewrite the subhead so it leads with what is… *effort low · impact high · tested against Give a reason to choose you* **Add a comparison line contrasting this with generic ETL and custom development.** The 'How we solve it' text already gestures at the alternative — 'complex configurations or custom development' — but only in passing, deep in one tab. Respondents reached for ETL tools as the mental comparison and had to construct the contrast themselves. Put a short, explicit comparison near the top: what an LN shop otherwise does (custom ABAP-style development, Boomi/generic ETL, manual re-export to Excel) and what changes when output is handled inside the Infor stack. Keep it factual, no… *effort medium · impact medium · tested against Give a reason to choose you* ### Value **Put a quantified outcome beside each module's benefit line.** Every module description states a capability with no magnitude: 'Automate document processing and delivery directly from Infor LN print events', 'Replicate CloudSuite data ... in near real-time'. Respondents accepted the manual-reformatting problem as real but could not size it, so they could not build an internal case. Attach one number per module — hours per month of report reformatting removed, replication latency in seconds, number of documents processed per run, typical implementation… *effort medium · impact high · tested against Specifics beat superlatives* **Rewrite the ETI testimonial to include a measurable before and after.** 'We simply do not know how to work without it' plus 'streamlined and optimized our business document management and reporting — securing better results with maximum control' reads as sentiment, not evidence — respondents called it vague and said the logo wall does not substitute for proof. Ask ETI for a figure to sit inside the quote or as a stat line directly beneath it: documents automated per month, days of manual reporting eliminated, go-live timeline. Keep the number adjacent to the quote… *effort medium · impact high · tested against Proof next to the claim* **Add a screenshot of actual LN print output beside the output module.** The LN Document Output Management block lists 'Branded PDF & Excel output' and 'Zero-touch processing on print' with nothing to look at; readers wanted to see real LN print output before believing the claim. Show a before/after pair — the raw LN print versus the branded PDF and structured Excel it becomes — captioned with the one click or print event that produced it. This makes the value visible without asking the reader to trust an adjective. *effort medium · impact medium · tested against Show the product early* ### Clarity **Group the six LN modules under two or three labelled outcomes.** 'LN Document Output Management', 'LN Reporting', 'LN Report-to-Excel', 'LN CloudSuite Data Sync' and 'LN Data Integration' repeat capabilities across cards — 'Multi-channel delivery' appears under two, Excel output under three — so module boundaries blur. Add short group headers such as document output and delivery, reporting and Excel, and data movement, and add one line to each card naming what it does that its neighbour does not (for example, Report-to-Excel is one-click ad hoc conversion… *effort medium · impact medium · tested against Headings stand alone* ### Brand alignment (side metric) **Cut 'One Platform. A Million Use Cases' from the tab strip.** The technical, non-aspirational tone is what makes this vendor read as an established Infor specialist rather than a startup. 'One Platform. A Million Use Cases' breaks that register and sits awkwardly at the end of a list of precise product tabs. Replace it with something in the same voice as the rest of the page, such as a plain line naming how many Infor LN and M3 deployments the suite runs in. *effort low · impact low · tested against Plain language* --- ## 03 · What is working ### The page tells Infor ERP admins in the first screen that this is for them Respondents said the headline, hero and tab structure name the audience — Infor LN/M3/CloudSuite shops and their admins/IT teams — with no ambiguity, and several credited product naming and insider terminology for doing that work. Nine points describe immediate audience recognition, and one adds that the Challenges & Solutions section clarifies the product using specific verbs. The flip side, named by two… > the header says it straight: "Enhance Your Infor CloudSuite Data and Document Processes" and lists "Infor LN, M3, and Infor CloudSuite" right up top, so I knew in five seconds who this is for > > — IT Administrator, Discrete Manufacturing, 201-500 > It would need our actual ERP or adjacent systems named — something like NetSuite, SAP, or whatever data/document pain points map to our stack — plus a concrete before/after metric tied to a role like mine, not just an Infor-specific admin persona. > > — Senior Systems Administrator, Process Manufacturing, 501-1000 > the headline "Enhance Your Infor CloudSuite Data and Document Processes" plus the subhead naming "Infor LN, M3, and Infor CloudSuite" tells you exactly who this is for right away > > — IT Administrator, Manufacturing, 1001-5000 > the header "Enhance Your Infor CloudSuite Data and Document Processes" plus the subhead naming "Infor LN, M3, and Infor CloudSuite" tells you exactly who this is for > > — IT Administrator, Process Manufacturing, 501-1000 > the "Challenges & Solutions" section spelled it out in plain terms (print-to-Excel, dynamic recipient routing, near-real-time replication) rather than leaving it as vague platform-speak. > > — Chief Information Officer, Discrete Manufacturing, 201-500 > Two lines in, I know this is for shops running Infor LN/M3/CloudSuite who are wrestling with report output, document distribution, and data sync — that's a narrow, well-defined audience, not vague B2B mush. > > — Systems Administrator, Manufacturing, 1001-5000 ### The manual report-reformatting problem is believed to be real and worth evaluating Two respondents accepted the core value premise — reducing manual labour on report reformatting — as credible enough to justify an evaluation, though both attached a condition ('if real', 'needs metrics'). Belief in the problem is present; belief in the magnitude is not. > Cutting the hours my team spends manually reformatting LN canned reports into usable Excel every week - if that genuinely drops to one click with zero rework, that alone justifies the eval, everything else is a bonus > > — Senior Systems Administrator, Manufacturing, 1001-5000 ### The vendor reads as an established Infor specialist, not a startup or a generalist Five points describe the vendor as a mature, niche Infor-focused ISV, credited to the logo wall, product maturity and insider terminology. Two respondents specifically praised the technical, non-aspirational tone as correct for an IT audience. > The product name "B2Win Suite" and version number ("B2Win Suite 7.0") suggest something that's been around a while and iterated, and the customer list (ULMA Construction, Curtiss-Wright, Mettler Toledo, Kongsberg) points to a company that's spent years selling specifically into manufacturing/industrial Infor shops > > — Systems Administrator, Discrete Manufacturing, 201-500 > the breadth of the logo wall (ULMA Construction, Mettler Toledo, Curtiss-Wright, Staples, Kongsberg) and a product now at "B2Win Suite 7.0" tells me this has years of iteration behind it > > — IT Administrator, Process Manufacturing, 501-1000 > the language is functional and technical (ETL, ION, low-code workflow) rather than aspirational buzzword soup, which is the one thing that keeps me reading instead of closing the tab > > — VP of IT, Process Manufacturing, 501-1000 > The tone is written for someone like me in the sense that it skips explaining what Infor LN is and goes straight into "canned reports," "print events," "ION" — that's insider shorthand aimed at an IT/systems buyer who already lives in this ERP > > — Systems Administrator, Process Manufacturing, 501-1000 --- ## 04 · What the personas said ### Four overlapping product names blur where one module ends and the next begins Three respondents said the brand stacks multiple features under one umbrella without organizing them, and that four product names with overlapping capabilities make module boundaries unclear. This was the only clarity complaint raised. > the brand tries to cover five things at once — reporting, replication, document output, ETL — all under one 'B2Win Suite' umbrella, so I had to mentally sort the feature bullets into buckets myself rather than the page doing it for me. > > — Senior Systems Administrator, Process Manufacturing, 501-1000 > Four product names (Output Management, Report-to-Excel, Data Sync, Data Integration) all under "B2Win Suite" with overlapping feature lists like "multi-channel delivery" appearing in two different tiles meant I had to reread to work out if these are separate modules I'd buy separately or one thing with different views on it > > — Chief Information Officer, Process Manufacturing, 501-1000 ### No respondent found a quantified proof point anywhere on the page Eight points say the same thing: no time savings, cost reduction, implementation timeline, latency figure or before/after metric is given. Several noted the customer list and testimonial are not substitutes — one said the customer list lacks the proof needed to justify an internal purchase, another called the testimonial vague. One respondent said they would need a live demo of actual LN print output before… > the page gives me zero numbers - no "X hours saved" or "Y% fewer manual touches" - just before/after bullet pairs > > — IT Administrator, Discrete Manufacturing, 201-500 > What's missing is proof it actually saves hours - the logos (ULMA, Curtiss-Wright, etc.) are there but no numbers on time or headcount saved, which is what I'd need before taking this further. > > — Systems Administrator, Discrete Manufacturing, 201-500 > the page gives me zero hard numbers — no "X hours saved" or "Y% reduction in manual handling" — just a customer quote saying "we simply do not know how to work without it," which is nice color but not proof. > > — VP of IT, Manufacturing, 1001-5000 > there's zero quantification anywhere on the page — no "X hours saved per week" or customer-reported percentage, just a single testimonial that "we simply do not know how to work without it," which tells me nothing I can take to a budget meeting. > > — Senior Systems Administrator, Process Manufacturing, 501-1000 > the page gives me mechanism in prose ("routing LN output through a low-code/no-code workflow platform... documents can be automatically generated, enhanced, split, and enriched") but no numbers: no time-to-implement, no % reduction in manual rework, no sizing of what "near real-time" replication actually means in latency. > > — Chief Information Officer, Process Manufacturing, 501-1000 > I'd walk in wanting a live demo against our actual LN print output, not a slide deck, and a straight answer on implementation timeline > > — Chief Information Officer, Discrete Manufacturing, 201-500 ### What the product does is understood as middleware that automates document output and… Respondents restated the core function consistently: an Infor LN/M3 add-on or automation layer for document output, reporting and distribution. Four points paraphrase it in near-identical terms, indicating the basic category lands. > they take clunky ERP print output and turn it into automated, multi-channel document delivery plus structured Excel/reporting, and sync CloudSuite data to your own databases faster > > — IT Administrator, Discrete Manufacturing, 201-500 > It's some kind of add-on layer for Infor LN/M3/CloudSuite that automates spitting out reports and documents - turning ERP print jobs into proper Excel files and routing PDFs to the right people automatically. > > — Systems Administrator, Discrete Manufacturing, 201-500 > They automate document output and data reporting/integration for Infor ERP systems (LN, M3, CloudSuite) — basically taking ERP print jobs and reports and turning them into routed, multi-channel documents or clean Excel/data feeds instead of manual rework. > > — VP of IT, Manufacturing, 1001-5000 > It's a data/document automation layer sitting on top of Infor LN, M3 and CloudSuite ERPs — basically it handles report generation, replicating ERP data out to other databases, and automating how documents (invoices, etc.) get formatted, split, and distributed to different recipients/channels. > > — IT Administrator, Manufacturing, 1001-5000 ### Native ION and Infor OS integration is the one differentiator respondents can name Five points identify native ION / Infor OS integration and LN-specific expertise as what separates this from generic ETL tools, with two respondents adding that the architectural specificity reduces perceived implementation risk. Three of those points frame it as the only concrete differentiator on the page, and one said the native integration claim itself needs verification. > The one thing that'd tip it toward this vendor over a generic competitor is the specificity to LN - "Infor LN 'canned reports'" and "B2Win Suite integration" tell me they actually know this ERP's quirks > > — IT Administrator, Discrete Manufacturing, 201-500 > The "B2Win Suite integration" and "Native Infor OS & ION" bullets are the one thing that would actually matter to me in a shortlist comparison — deep, native ION/Infor OS hooks are a real differentiator versus a generic ETL tool bolted on top > > — VP of IT, Manufacturing, 1001-5000 > the specificity of "B2Win Suite integration" and "Native Infor OS & ION" under LN Data Integration - that tells me they've built for Infor's actual architecture, not a generic connector wrapped in Infor branding, which matters when I'm judging implementation risk against our LN setup > > — Senior Systems Administrator, Manufacturing, 1001-5000 > Everything else — "near real-time replication," "zero-touch processing," "full traceability" — is a feature label with no number attached (no replication lag in seconds/minutes, no doc-processing volume, no error rate), so none of it would differentiate this from a rival with the same bullet points > > — Senior Systems Administrator, Process Manufacturing, 501-1000 > it would rule itself in or out on the "Infor OS & ION" native integration line under LN Data Integration — that's the one concrete technical detail that distinguishes "built for this stack" from "generic ETL slapped on top." > > — IT Administrator, Manufacturing, 1001-5000 ### The named ETI customer quote is the strongest evidence on the page but respondents… One respondent called the ETI quote about dependency on the product the single strongest differentiation point, and another said the named quote is verifiable but insufficient on its own without detailed case study evidence. A third noted feature claims around it carry no specific numbers. > The one line that would actually pull me toward this over a rival is the ETI quote - "We simply do not know how to work without it" - because that's a real customer voicing dependency, not marketing adjectives. > > — Systems Administrator, Discrete Manufacturing, 201-500 > Everything else — "near real-time replication," "zero-touch processing," "full traceability" — is a feature label with no number attached (no replication lag in seconds/minutes, no doc-processing volume, no error rate), so none of it would differentiate this from a rival with the same bullet points > > — Senior Systems Administrator, Process Manufacturing, 501-1000 > The one thing that would tilt me toward this vendor over a generic competitor is the ETI quote — "We simply do not know how to work without it" — attributed to a named IT Director at a named company, because it's at least a real person I could theoretically go verify > > — Chief Information Officer, Process Manufacturing, 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 cannot survive an internal business case because it hands buyers nothing to put in one.** *(high)* Eight of 15 respondents found zero quantified proof anywhere — no time savings, cost reduction, implementation timeline, latency or before/after metric. One said explicitly the customer list lacks the proof needed to justify an internal purchase, another called the testimonial vague, and a third demanded a live demo of actual LN print output first. The two respondents who accepted the manual-reformatting premise both conditioned it on 'if real' and 'needs metrics'. Belief in the problem… - **Every strength on the page is a recognition strength, and recognition is the cheapest thing to earn in a niche category.** *(high)* The positives are audience identification (8 of 15), category comprehension (4 of 15) and vendor credibility as an established Infor ISV (4 of 15) — all of which are delivered by product naming, insider terminology and a logo wall. Not one positive theme concerns value or proof. The page wins the first screen and loses everything after it, since 8 of 15 found no quantified proof and only 5 of 15 could name any differentiator. - **The page rests its entire competitive case on one unverified integration claim.** *(high)* Native ION / Infor OS integration is the only concrete differentiator respondents could name (5 of 15), three of those points said it was the only one on the page, and one said the claim itself needs verification. Remove it and the page has no answer to generic ETL tools. - **The strongest evidence asset on the page was judged insufficient by the same respondents who praised it.** *(high)* Of the 3 respondents on the ETI quote, one called it the single strongest differentiation point, another said the named quote is verifiable but insufficient without detailed case study evidence, and a third noted the surrounding feature claims carry no numbers. The page's best proof point is simultaneously its ceiling. - **The product architecture is unsellable as presented: buyers who understand the category still cannot tell what they are buying.** *(medium)* Comprehension of the category lands with 4 of 15 respondents, but 2 of 15 said four overlapping product names blur where one module ends and the next begins and that features are stacked under one umbrella without organization. Understanding the function does not tell a buyer which module to scope, price or license. - **The technical, non-aspirational tone praised by respondents is the same tone that starves the page of business justification.** *(medium)* Two respondents praised the technical, non-aspirational register as correct for an IT audience (part of the 4 of 15 on vendor credibility), yet 8 of 15 found no implementation timeline, cost reduction or time-savings figure — the exact material an IT buyer needs to escalate internally. The tone earns trust from the reader and gives them nothing to forward. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | Senior Systems Administrator | Manufacturing | 1001-5000 | | 2 | IT Administrator | Discrete Manufacturing | 201-500 | | 3 | Chief Information Officer | Process Manufacturing | 501-1000 | | 4 | VP of IT | Manufacturing | 1001-5000 | | 5 | Systems Administrator | Discrete Manufacturing | 201-500 | | 6 | Senior Systems Administrator | Process Manufacturing | 501-1000 | | 7 | IT Administrator | Manufacturing | 1001-5000 | | 8 | Chief Information Officer | Discrete Manufacturing | 201-500 | | 9 | VP of IT | Process Manufacturing | 501-1000 | | 10 | Systems Administrator | Manufacturing | 1001-5000 | | 11 | Senior Systems Administrator | Discrete Manufacturing | 201-500 | | 12 | IT Administrator | Process Manufacturing | 501-1000 | | 13 | Chief Information Officer | Manufacturing | 1001-5000 | | 14 | VP of IT | Discrete Manufacturing | 201-500 | | 15 | Systems Administrator | Process Manufacturing | 501-1000 | --- ## 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-25, then deleted along with the personas and their answers.