# Message test — https://supplier.io/ After reading your page, only 10 of 15 personas could name a reason to pick you over a similar option. - **Page tested:** https://supplier.io/ - **Audience tested against:** Procurement leaders at enterprises - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/supplier-io-supplier-data-diversity-intelligen-ky-JPnA > 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 | 81% | 2 without hesitation, 13 with reservations | | 3. Value | Do they actually want it? | 15/15 | 78% | all with reservations | | 4. Differentiation | Is there a reason to pick you over the alternatives? | 10/15 | 59% | all with reservations | **Brand alignment** (a side metric, not one of the four layers) — 14/15, 74% 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 **Define "verified" and "resolved" in a line under the Atlas paragraph.** Atlas claims to resolve records to "one verified record per supplier" but never says how a match is made or what verification confirms. Add a sentence naming the matching method and the sources checked, so the claim is testable rather than asserted. *effort medium · impact high · tested against Plain language* **Add a line under the stat band showing the Kraft Heinz before and after numbers.** The $1M savings figure is the only hard outcome and arrives with no baseline, so a buyer cannot judge it. Give duplicate count before, verified records after, match rate and the timeframe. *effort medium · impact high · tested against Proof next to the claim* **Replace "The leader in supplier data and intelligence" with a named, checkable reason to pick Supplier.io.** "The leader in supplier data and intelligence" is a claim every vendor in the category makes. Swap it for something only you can say, such as resolving vendor masters against 239M legal entities in 145 countries with continuous re-verification. *effort low · impact high · tested against Give a reason to choose you* **Add an EU customer proof point with data-residency and GDPR handling next to the coverage claim.** The page claims 145 countries but every proof point reads US, with US federal compliance language and no European reference. Name a European customer and state where data is processed, so the global claim has evidence beside it. *effort medium · impact medium · tested against Proof next to the claim* ### Clarity **Add a one-line map of Atlas, Supplier Intelligence and SupplierOne under "Clean data that stays clean".** Readers cannot tell how the three branded product lines stack or which one they would buy first. State in plain words that Atlas fixes the vendor master, the Intelligence products run on top of it, and SupplierOne is the supplier-facing side. *effort low · impact medium · tested against Plain language* ### Relevance **Name the buyer role in the hero subhead under "Build Every Supplier Decision on Data You Can Verify".** The page speaks to procurement buyers and to suppliers at once, so readers have to infer which one they are. Say explicitly that this page is for enterprise procurement and supplier data owners, and point suppliers elsewhere. *effort low · impact medium · tested against Name the audience* ### Value **Add a proof-of-concept offer beside "Get a free assessment" stating what it runs on.** Buyers will not commit without seeing match rates against their own vendor master, and "free assessment" does not say whether their data is used. Spell out that you run the assessment on their ERP extract and return duplicate and match rates. *effort medium · impact high · tested against Answer the live objection* ### Brand alignment (side metric) **Replace US-centric compliance wording with coverage language that matches the 145-country claim.** The page claims global reach while the compliance and logo proof read US-only. Align the examples with the markets you say you cover. *effort low · impact medium · tested against Proof next to the claim* --- ## 03 · What is working ### The headline and problem statement land fast Respondents said the opening screen names the pain quickly and communicates the core value proposition in the headlines. Several identified the target as large-enterprise procurement leadership from the hero line alone. > It was obvious fast — the subhead says it straight out: "You've spent millions on S2P platforms, analytics, risk tools, and AI. None of it works when the supplier data underneath is fragmented, duplicated, and out of date." > > — Chief Procurement Officer, Retail, 5000+ > the hero line "None of it works when the supplier data underneath is fragmented, duplicated, and out of date" tells me the problem in one sentence > > — Head of Sourcing, Healthcare, 5000+ > the subhead "Build Every Supplier Decision on Data You Can Verify" plus the line "You've spent millions on S2P platforms, analytics, risk tools, and AI. None of it works when the supplier data underneath is fragmented, duplicated, and out of date" told me the problem > > — VP of Procurement, Manufacturing, 1001-5000 ### The duplicate-resolution outcome is understood and believed Respondents could restate the payoff in their own words: duplicate vendor records resolved into verified entities across ERPs, including the post-merger case. > They clean up and verify your supplier/vendor master data — resolving duplicate vendor records to one verified entity, enriching them with certifications and spend history > > — Chief Procurement Officer, Retail, 5000+ > one verified record per supplier instead of six conflicting ones across ERPs, which is a real problem for us given our M&A history > > — Procurement Director, Financial Services, 1001-5000 --- ## 04 · What the personas said ### Product architecture and module naming are not explained Respondents had to re-read to map branded module names to functions, and said the stacking of products is unexplained without a diagram. Terms like 'verified' and 'resolved' are used without defining the matching methodology behind them. > terms like "Supplier Intelligence products," "Atlas," and "SupplierOne" are used almost interchangeably with generic phrases like "data foundation" and "sourcing," so I had to re-read a couple of sections to figure out which brand name mapped to which function > > — Procurement Director, Financial Services, 5000+ > the product naming is what slows you down: "Atlas," "Supplier Intelligence," "SupplierOne" are introduced without a clean diagram showing how they stack > > — Senior Procurement Manager, Technology, 1001-5000 > verified against what standard, resolved using what match logic (exact tax ID, fuzzy name-match, human review)? > > — Head of Sourcing, Healthcare, 5000+ ### Buyer and supplier audiences are addressed without being distinguished One respondent said the page speaks to multiple personas at once without separating them, and another noted the intended reader is inferred rather than named. > the persona split between buyer-side features and the "Are you a supplier? Get found" section bolted at the bottom — that's a second audience that isn't flagged until you're well into the page > > — Head of Sourcing, Healthcare, 5000+ ### The page reads as US-first despite claiming global coverage Respondents flagged US-heavy customer logos, US federal compliance language, and the absence of any EU or healthcare reference. Several said an EU customer proof point with GDPR handling specifics is missing. > "239M+ legal entities across 145 countries" sounds like coverage, but nothing here tells me it's actually verified well for European entities, and none of the named logos (Kraft Heinz, Aramark, United, JetBlue, Logitech) are EU or healthcare > > — Head of Sourcing, Healthcare, 1001-5000 > it leans quite heavily into US-specific supplier diversity and FAR compliance language (the contracting officer quote, "diverse suppliers"), which makes me wonder how much of this is genuinely built for an EU buyer like me versus a US-first product with Europe bolted on > > — Senior Procurement Manager, Technology, 1001-5000 > I'd want an EU-based or EU-operating named customer with a spend and vendor-count footprint close to ours, plus a line acknowledging GDPR/EU entity-data handling specifically - right now every proof point is a US corporate > > — Senior Procurement Manager, Technology, 1001-5000 > it's written with a US enterprise supplier-diversity compliance lens (FAR clauses, Tier 2 reporting, economic impact storytelling) that reads slightly off-target for an EU retail CPO > > — Chief Procurement Officer, Retail, 1001-5000 ### The core function reads as supplier data cleanup, not a sourcing platform Several respondents independently restated the product as vendor master deduplication and enrichment, with sourcing and reporting treated as layered extras. They arrived at this reading without the page stating it, which they treated as a correction rather… > supplier data quality and enrichment platform ("Atlas" is the core engine) with sourcing and reporting bolted on. I'd call it supplier master data management / supplier data enrichment, not a sourcing tool per se > > — Head of Sourcing, Healthcare, 1001-5000 > So it's supplier data management / master data cleansing with a sourcing and reporting module bolted on, not a sourcing platform itself. > > — VP of Procurement, Manufacturing, 1001-5000 > it's a supplier master data management / data enrichment platform, with a sourcing directory and diversity-spend reporting bolted on > > — Head of Sourcing, Healthcare, 5000+ ### The Kraft Heinz $1M savings claim is the only concrete proof and respondents want its… The savings figure drove interest and read as more credible than generic competitor messaging, but respondents noted it is the page's sole ROI evidence and lacks baseline or before/after metrics to validate it. > the Kraft Heinz quote about saving $1M in maintenance is the only concrete bit that'd make me believe the ROI > > — Head of Sourcing, Healthcare, 1001-5000 > the Kraft Heinz quote about saving "almost $1 million worth of maintenance a year" is the kind of line that would get me to take a call, provided they can show me the before/after on a vendor master close to our size and complexity > > — Senior Procurement Manager, Technology, 1001-5000 > Kraft Heinz quote about saving "$1 million worth of maintenance a year," which is a nice anecdote but not a methodology > > — Head of Sourcing, Healthcare, 5000+ > Kraft Heinz's Stefanie Fink giving a hard number — "almost $1 million worth of maintenance a year" saved on just the proof-of-concept records. That's the kind of quantified, attributable claim a competitor's generic "trusted by leading enterprises" copy usually doesn't have > > — Procurement Director, Financial Services, 1001-5000 > That Kraft Heinz quote about saving "almost $1 million worth of maintenance a year" from a proof-of-concept is the kind of concrete number that makes me want a demo rather than a brochure > > — VP of Procurement, Manufacturing, 5000+ ### No one would move forward without a proof-of-concept on their own data Respondents said vendor-supplied demo data and a single case study are insufficient, and named the specific test they would require: match rates and duplicate detection run against their own vendor master or post-merger ERP records. > A verified match-rate number on data like ours — e.g. "on a comparable financial services ERP with X million vendor records, we resolved Y% to unique legal entities" — that's the single proof point that would turn this from a maybe into a pilot conversation > > — Procurement Director, Financial Services, 5000+ > A live demo where Atlas runs against our actual vendor master and surfaces duplicate/fragmented records our current MDM tool has already missed — if it catches real errors we know exist, that's the proof; a generic match-rate stat isn't. > > — VP of Procurement, Manufacturing, 1001-5000 > But that's one customer's result, not mine — I'd want them to run the same proof-of-concept against our vendor master before I'd put real time on the calendar, not just take the pitch. > > — Chief Procurement Officer, Retail, 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 sells a sourcing platform and buyers read it as data cleanup — the positioning is being rewritten by the reader.** *(high)* 3 of 15 independently restated the product as vendor master deduplication and enrichment, treating sourcing and reporting as layered extras, and the 2 who believed the payoff described it as duplicate resolution. The understood value is the narrowest one. - **A fast headline buys attention the rest of the page cannot convert.** *(high)* 5 of 15 said the opening names the pain quickly, but 4 of 15 would not move forward without a proof-of-concept on their own data and 5 of 15 called the single savings figure unvalidated. Early comprehension collapses at the evidence layer. - **One customer number is the entire business case, and it is unverifiable as written.** *(high)* The Kraft Heinz $1M figure is the page's sole ROI evidence for 5 of 15 respondents, with no baseline or before/after metrics. A single undocumented number is easier for a competitor to beat than to defend. - **The global coverage claim is contradicted by the page's own proof, which costs credibility beyond geography.** *(high)* 3 of 15 flagged US-heavy logos and US federal compliance language with no EU or healthcare reference, and asked for an EU proof point with GDPR specifics. A claim the page visibly fails to support makes its other claims suspect. - **Branded module names force work onto the reader and bury the methodology that would make the product credible.** *(medium)* 3 of 15 had to re-read to map module names to functions and said stacking is unexplained without a diagram, with 'verified' and 'resolved' used without defining the matching methodology. That same undefined methodology is what 4 of 15 demand be proven on… - **Naming no reader means every reader self-selects, and they are selecting the cleanup story.** *(medium)* The page addresses buyer and supplier audiences without separating them and the intended reader is inferred rather than named; 3 of 15 then defaulted to reading the product as vendor master deduplication. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | Head of Sourcing | Healthcare | 1001-5000 | | 2 | Procurement Director | Financial Services | 5000+ | | 3 | VP of Procurement | Manufacturing | 1001-5000 | | 4 | Chief Procurement Officer | Retail | 5000+ | | 5 | Senior Procurement Manager | Technology | 1001-5000 | | 6 | Head of Sourcing | Healthcare | 5000+ | | 7 | Procurement Director | Financial Services | 1001-5000 | | 8 | VP of Procurement | Manufacturing | 5000+ | | 9 | Chief Procurement Officer | Retail | 1001-5000 | | 10 | Senior Procurement Manager | Technology | 5000+ | | 11 | Head of Sourcing | Healthcare | 1001-5000 | | 12 | Procurement Director | Financial Services | 5000+ | | 13 | VP of Procurement | Manufacturing | 1001-5000 | | 14 | Chief Procurement Officer | Retail | 5000+ | | 15 | Senior Procurement Manager | Technology | 1001-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-10-05, then deleted along with the personas and their answers.