# Message test — https://get-iris.com/ After reading your page, only 3 of 15 personas could name a reason to pick you over a similar option. - **Page tested:** https://get-iris.com/ - **Audience tested against:** Mid-Market SaaS CMOs, Director of Marketing, Field Marketing, Business Development, Event Management - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/iris-event-lead-orchestration-wOlEIm8 > 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 | 87% | 6 without hesitation, 9 with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 15/15 | 94% | 11 without hesitation, 4 with reservations | | 3. Value | Do they actually want it? | 8/15 | 52% | all with reservations | | 4. Differentiation | Is there a reason to pick you over the alternatives? | 3/15 | 33% | all with reservations | **Brand alignment** (a side metric, not one of the four layers) — 10/15, 59% strength (all with reservations). Does the page read like the company you actually are? **Fix first: Value.** 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 a comparison line stating per-event pricing versus per-seat badge scanners** Nothing on the page says why Iris beats the scanner the organizer rents you. Say you charge per event, keep lead data across events instead of resetting, and attribute dollars per event. *effort medium · impact high · tested against Give a reason to choose you* **List supported CRMs and enrichment sources by name in the How It Works section** "CRM Synced" never says which CRMs, so buyers assume HubSpot-only and disqualify it. Name the integrations you support today and what is on the roadmap with dates. *effort low · impact high · tested against Answer the live objection* **Rewrite the H1 "Own Your Event Ecosystem" to name per-event revenue attribution** The headline is a category slogan any event vendor could run. Lead with the job buyers say out loud: know which events returned pipeline, per event. *effort low · impact medium · tested against Lead with the use case* ### Value **Replace the demo dashboard's ROI figures with one named customer's event result** The 3.9x blended ROI and $1.1M pipeline sit inside a phone mockup, so buyers read every number as invented demo data. Swap in one real event with a named company, spend and closed-won amount. *effort medium · impact high · tested against Proof next to the claim* **Add a line under the ROI panel explaining how a closed deal is traced to an event** Buyers cannot tell whether attribution survives to deal close or just tags the scan. State what Iris matches on, badge scan to CRM opportunity, and how long the attribution window runs. *effort low · impact high · tested against Answer the live objection* **Replace the zeroed placeholder metrics under "Events to date" with real filled-in numbers** "0 Scanned", "$0k Pipeline" and "Return on spend 0.0x" make the product look like it has no results. Show a populated example program with dollar figures and event count. *effort low · impact medium · tested against Specifics beat superlatives* ### Clarity **Replace the eyebrow "Event Lead Orchestration" with plain words for what the app does** "Orchestration" forces readers to reverse-engineer the function from the screenshots below. Say it captures booth leads, syncs them to your CRM, and reports revenue per event. *effort low · impact medium · tested against Plain language* ### Brand alignment (side metric) **Add a security and access line near the CRM sync step covering SSO and data handling** Nothing on the page tells a buyer with a security review who holds the lead data or whether SSO and role permissions exist. State where data is stored, who can access it, and what authentication you support. *effort medium · impact high · tested against Answer the live objection* **Replace "Join the waitlist" with one live next action and drop the competing demo links** A waitlist plus "See how it works", "Try the demo" and six "Learn more" links reads pre-launch and splits attention. Pick one action and repeat it. *effort low · impact medium · tested against One clear next action* --- ## 03 · What is working ### The problem statement and audience land immediately, without requiring inference Eight respondents said the problem section surfaces real pain fast and names who the product is for on the first screens, with the audience restated in the FAQ. Several noted it required no inference. > The "Problem" section spells it out in plain language — "Big spend. Little control." and lines like "You're spending thousands on the booth, the travel, the team, then handing the most important part to a tool you barely chose" and "By the time the data's clean, the moment's gone." That's a real, specific pain > > — Business Development Director, Technology Services, 501-1000 > the hero line "Big spend. Little control." plus "Lead capture is borrowed, messy, and days too late" told me the problem in the first few seconds, and the FAQ spells out "Who is it for?" explicitly > > — Director of Marketing, Software, 501-1000 > "Big spend. Little control." and the trio of problem cards (borrowed scanner, follow-up days too late, scattered data across scanner/phone/notebook) name the pain in about five seconds > > — Field Marketing Director, SaaS, 501-1000 > It was clear fast, not buried — the "Problem" section spells out "Big spend. Little control." and "Lead capture is borrowed, messy, and days too late," so I had the pain point within seconds of scrolling. The FAQ makes the audience explicit too: "field marketing, sales, and RevOps teams, or a founder working the booth" > > — Business Development Manager, Software, 1001-5000 > the hero line "Big spend. Little control." plus the subhead about sponsoring events and lead capture being "borrowed, messy, and days too late" told me the problem in five seconds, and the FAQ nails the audience explicitly: "Any GTM operator who captures leads at events... field marketing, sales, and RevOps teams, or a founder working the booth." I didn't have to infer anything > > — Business Development Director, Technology Services, 201-500 ### The per-event attribution loop is the differentiator respondents could name Four respondents pointed to specific differentiators: dollar figures attributed per event versus generic scanners, data persisting across events instead of resetting, per-event pricing instead of competitor per-seat fees, and same-day follow-up versus… > I'd get owned lead data and same-day follow-up instead of waiting on the event organizer's scanner file for a week — that's real, since the badge-scanner dependency is our actual pain today. > > — Field Marketing Director, SaaS, 1001-5000 > The "own your data, no per-event scanner rental" line and the fact it's priced per-event not per-seat would tip me toward it over a competitor that locks you into per-user fees > > — Field Marketing Director, SaaS, 1001-5000 > the framing of owning your data across events rather than it resetting each time is a genuinely good differentiator against the badge-scanner-as-a-service model > > — Business Development Manager, Software, 201-500 > The thing that would actually move me toward this one over a generic lead-scanner app is the attribution loop shown step by step — Scan → Enrich → Outreach → CRM Synced → Opportunity → "Revenue Attributed" with the concrete "$40,000 attributed to SaaStr, 14.2x ROI on this event." > > — Senior CMO, SaaS, 201-500 --- ## 04 · What the personas said ### Every ROI number is read as a demo mockup, not a customer result Eight respondents flagged the ROI figures, including the 14.2x claim, as placeholders from cherry-picked demo data with no named customers or case study. This was the single most repeated objection. > the ROI numbers on the page (3.9x, 14.2x) are demo placeholders, not our numbers > > — Field Marketing Director, SaaS, 1001-5000 > no named customers, no proof behind "14.2x ROI." > > — Chief Marketing Officer, B2B Services, 1001-5000 > the ROI language stacked with mockup numbers like "14.2x ROI" and "$40,000 attributed" without saying whether that's a real customer or an illustrative demo screen > > — Director of Marketing, Software, 501-1000 > "$40,000 attributed to SaaStr, 14.2x ROI on this event" is the number I actually need to defend event budgets to my CFO, since right now I can't cleanly tie booth spend to closed revenue at all. That's worth a meeting — but only a first one, and I'd walk in wanting to see the Apollo enrichment and HubSpot sync live on a messy real badge, not the demo's clean Sarah Chen/Meridian Corp flow > > — Senior Director of Marketing, Technology Services, 1001-5000 > there's no named customer, no case study, nothing showing this at scale in a company like mine, only mocked-up screens > > — Field Marketing Manager, B2B Services, 201-500 > just a mocked-up demo with fictional names like Sarah Chen and made-up ROI numbers like "14.2x ROI," so while I get what it does fast, I have zero proof anyone like me has actually used it and it worked > > — Chief Marketing Officer, B2B Services, 501-1000 > I'd want a case study with a named company, real spend-to-close numbers, and confirmation Salesforce/ZoomInfo are actually shipping before I put this in front of budget > > — Field Marketing Director, SaaS, 501-1000 ### The HubSpot/Apollo/iOS-only stack disqualifies the product outright Five respondents said the narrow integration surface blocks adoption. Missing Salesforce support specifically disqualifies it against Salesforce-native competitors, and Apollo/HubSpot-only reads as vendor lock-in in mixed-stack environments. > the narrow stack: HubSpot only, Apollo only, iOS only, "Salesforce planned next" — if a competitor already covers Salesforce or Android, that's an easy tiebreaker away from Iris > > — Field Marketing Director, SaaS, 1001-5000 > I'd need to see it acknowledge a multi-region, multi-brand enterprise setup — something like Salesforce support live (not "planned next"), SSO/security compliance mentioned > > — Director of Marketing, Software, 501-1000 > "Iris is focused on HubSpot today... Salesforce planned next" and "Iris supports Apollo today... ZoomInfo and Clay planned." We're a Salesforce shop, so that single sentence knocks it out of the running against any competitor that already supports our stack > > — Business Development Director, Technology Services, 501-1000 > "Iris supports Apollo today... HubSpot today" — narrow stack lock-in rules it out if we're not on those. > > — Chief Marketing Officer, B2B Services, 1001-5000 ### Early-stage positioning reads as not enterprise-ready Seven respondents said the early-stage framing and demo-heavy tone signal an early-adopter pitch aimed at smaller, faster-moving companies. They cited absent enterprise security, governance, SSO, multi-region messaging and no enterprise customer base, with… > the single-integration limits (iOS only, HubSpot only, Apollo only, "planned" for everything else) scream v1 product, not a mature vendor with a real install base. > > — Business Development Manager, Software, 201-500 > Small early-stage startup, US-flavoured, selling to mid-market SaaS sales/marketing teams. Not written for a EU services CMO. > > — Chief Marketing Officer, B2B Services, 1001-5000 > I picture a small, early-stage startup, maybe seed to Series A, not an established enterprise vendor — the "join the waitlist," "in early access, so join the waitlist for access and pricing," and the honest "Iris is focused on HubSpot today... Salesforce planned next" language all read as a young team > > — Director of Marketing, Software, 501-1000 > the tone is also very demo-forward and screenshot-heavy, which reads a bit more like a pitch to an early adopter or design partner than a fully de-risked enterprise sale — fine for a first conversation, but I'd want a real customer reference, not just Sarah Chen from Meridian Corp > > — Senior Director of Marketing, Technology Services, 1001-5000 > it feels aimed at someone smaller and faster-moving than me, even if the workflow itself is one I understand. > > — Director of Marketing, Software, 501-1000 ### The workflow mechanism is understandable, even where the marketing headers get in the way Four respondents could restate how the product works — concrete steps, syncing event leads to CRM with per-event ROI tracking. Two of those said marketing headers and the product name obscure the function and force reverse-engineering. > I'd call it event lead orchestration, which is literally what they call it — reasonably clear category, though "orchestration" is doing some inflating for what's really capture-plus-sync-plus-attribution. > > — Business Development Director, Technology Services, 501-1000 > Event lead capture app that syncs to your CRM and claims ROI tracking per event. > > — Chief Marketing Officer, B2B Services, 1001-5000 > The mechanism walkthrough (scan → enrich → outreach → CRM sync → opportunity → attributed revenue) was concrete enough that I could picture the workflow, which is more than most of these pages manage. > > — Director of Marketing, Software, 501-1000 > "Event Lead Orchestration" — nobody outside this vendor calls it that, so I had to reverse-engineer the actual function from the screenshots and FAQ rather than the marketing name > > — Field Marketing Director, SaaS, 501-1000 > the only friction was the repeated marketing headers ('Own Your Event Ecosystem,' 'One app. Your leads from day one.') sitting on top of the actual flow, so I had to skip past the slogans to get to the six-step scan/enrich/sync/attribute sequence > > — Business Development Director, Technology Services, 201-500 ### The value claim rests on attribution accuracy that the page does not evidence One respondent said the value depends on whether attribution holds through deal close, not on the ROI framing itself — the page asserts the loop without showing it survives real pipeline data. > I'd need them to walk through how attribution actually gets tied to a closed deal (multi-touch, first-touch, how they handle a lead that goes cold for four months and reopens), because "revenue traced back to the event" is the whole value prop and it's also the easiest thing to hand-wave. > > — Senior CMO, SaaS, 201-500 --- ## 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 proof point actively destroys trust instead of building it** *(high)* Eight of 15 respondents read every ROI figure, including 14.2x, as demo mockups with no named customer or case study — the most repeated objection on the page. A quantified claim that reads as fabricated is worse than no claim. - **Relevance is wasted because the page converts recognition into rejection** *(high)* Eight respondents said the problem and audience land with no inference required, yet eight dismissed the ROI proof and five said the integration stack disqualifies the product outright. The page earns attention and then loses the deal. - **The integration list functions as a disqualification notice, not a capability list** *(high)* Five respondents said the HubSpot/Apollo/iOS-only surface blocks adoption, with missing Salesforce support cited as disqualifying against Salesforce-native competitors and the stack reading as vendor lock-in. No messaging fix recovers a buyer who has already… - **The page disqualifies itself from enterprise deals before a conversation starts** *(high)* Six respondents read the early-stage, demo-heavy tone as an early-adopter pitch for smaller companies, citing absent security, governance, SSO and multi-region messaging and no enterprise customer base. Combined with the narrow stack, the addressable… - **The one differentiator respondents can articulate is the same claim they refuse to believe** *(high)* Three respondents named per-event dollar attribution as the differentiator, while eight dismissed the ROI numbers as cherry-picked and one noted attribution is never shown surviving to deal close. The differentiator and the credibility gap are the same… - **Differentiation reaches a minority while objections reach a majority** *(medium)* Only three of 15 respondents could name a differentiator, against eight who rejected the ROI evidence, six who read it as not enterprise-ready, and five blocked by integrations. Objection volume outweighs the positive signal roughly three to one. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | Field Marketing Director | SaaS | 1001-5000 | | 2 | Business Development Manager | Software | 201-500 | | 3 | Business Development Director | Technology Services | 501-1000 | | 4 | Chief Marketing Officer | B2B Services | 1001-5000 | | 5 | Senior CMO | SaaS | 201-500 | | 6 | Director of Marketing | Software | 501-1000 | | 7 | Senior Director of Marketing | Technology Services | 1001-5000 | | 8 | Field Marketing Manager | B2B Services | 201-500 | | 9 | Field Marketing Director | SaaS | 501-1000 | | 10 | Business Development Manager | Software | 1001-5000 | | 11 | Business Development Director | Technology Services | 201-500 | | 12 | Chief Marketing Officer | B2B Services | 501-1000 | | 13 | Senior CMO | SaaS | 1001-5000 | | 14 | Director of Marketing | Software | 201-500 | | 15 | Senior Director of Marketing | Technology Services | 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-09-11, then deleted along with the personas and their answers.