Clarity
Do they understand what you do?
Strong15 of 15
15 could name what kind of product this is, unprompted.
Saved report, kept for 60 days — expires in 60 days. Re-opening it is free.
01
Your verdict
Relevance
Can they tell what it solves, and who it's for?
Strong15 of 1515 could quickly tell what problem it solves and who it is for.
Value
Do they actually want it?
Weak8 of 158 would take a meeting to learn more.
Differentiation
Fix firstIs there a reason to pick you over the alternatives?
Fail3 of 153 could name a reason to pick you over a similar option.
See what they thought you were
Your page describes: Event lead orchestration. They said:
- 3×Event lead capture / CRM sync toolmatches
- 3×Event lead capture and ROI attribution softwarematches
- 2×Event lead capture / lead orchestration softwarematches
- 1×Event lead capture / lead orchestration platformmatches
- 1×Event lead capture and attribution softwarematches
5 couldn't name one; 10 got it right.
Four separate measures, not stages: all 15 personas answered all four questions. Each square is one persona.
Additional signalBrand alignment10 of 15MixedShow finding ▸
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… Not one of the four layers, and it does not affect the scores above or the order to fix them in.
These are 15 simulated buyers. Want 15 real ones?
Test with humans02
Fix these firstFix these first
Three edits, in the order that matters.
The first is on your weakest layer, the second on the next, the third on the layer the most buyers had a problem with. Each says what to change on the page and why, with one simulated answer behind it.
Add a comparison line stating per-event pricing versus per-seat badge scanners
Why: 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.
5 of 15 raised this
“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 employeessimulated Moves DifferentiationGive a reason to choose youReplace the demo dashboard's ROI figures with one named customer's event result
Why: 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.
8 of 15 raised this
“the ROI numbers on the page (3.9x, 14.2x) are demo placeholders, not our numbers”
Field Marketing Director, SaaS · 1001-5000 employeessimulated Moves ValueProof next to the claimReplace the eyebrow "Event Lead Orchestration" with plain words for what the app does
Why: "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.
5 of 15 raised this
“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 employeessimulated Moves ClarityPlain language
Keep these · 2
These landed. Keep the wording when you edit around it.
- Keep · Relevance
The problem statement and audience land immediately, without requiring 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…” Show full quote
“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 employeessimulated - Keep · Differentiation
The per-event attribution loop is the differentiator respondents could name
“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…” Show full quote
“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 employeessimulated
03
All recommendations
Differentiation
Fail3 of 15Moves DifferentiationAnswer the live objection
List supported CRMs and enrichment sources by name in the How It Works section
Why: "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.
5 of 15 raised this
“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”
Moves DifferentiationLead with the use case
Rewrite the H1 "Own Your Event Ecosystem" to name per-event revenue attribution
Why: 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.
5 of 15 raised this
“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”
Value
Weak8 of 15Moves ValueAnswer the live objection
Add a line under the ROI panel explaining how a closed deal is traced to an event
Why: 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.
8 of 15 raised this
“the ROI numbers on the page (3.9x, 14.2x) are demo placeholders, not our numbers”
Moves ValueSpecifics beat superlatives
Replace the zeroed placeholder metrics under "Events to date" with real filled-in numbers
Why: "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.
8 of 15 raised this
“the ROI numbers on the page (3.9x, 14.2x) are demo placeholders, not our numbers”
Clarity
Strong15 of 15Relevance
Strong15 of 15No specific edits needed here — this layer held up.
Brand alignment
Mixed10 of 15Moves Brand alignmentAnswer the live objection
Add a security and access line near the CRM sync step covering SSO and data handling
Why: 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.
6 of 15 raised this
“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.”
Moves Brand alignmentOne clear next action
Replace "Join the waitlist" with one live next action and drop the competing demo links
Why: 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.
6 of 15 raised this
“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.”
04
Buyer evidence
Biggest risks
A deliberately adversarial read of the same answers. Each claim was checked back against what the personas said and dropped if nothing supported it.
- high
The page's central proof point actively destroys trust instead of building it
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.
- high
Relevance is wasted because the page converts recognition into rejection
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.
- high
The integration list functions as a disqualification notice, not a capability list
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…
- high
The page disqualifies itself from enterprise deals before a conversation starts
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…
- high
The one differentiator respondents can articulate is the same claim they refuse to believe
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…
- medium
Differentiation reaches a minority while objections reach a majority
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.
Differentiation
The HubSpot/Apollo/iOS-only stack disqualifies the product outright
5 of 15
“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 employeessimulated See all 4 comments
“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 employeessimulated “"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…” Show full quote
“"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 employeessimulated “"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 employeessimulated The per-event attribution loop is the differentiator respondents could name
3 of 15 · what worked
“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…” Show full quote
“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 employeessimulated See all 4 comments
“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…” Show full quote
“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 employeessimulated “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 employeessimulated “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 →…” Show full quote
“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 employeessimulated
Value
Every ROI number is read as a demo mockup, not a customer result
8 of 15
“the ROI numbers on the page (3.9x, 14.2x) are demo placeholders, not our numbers”
Field Marketing Director, SaaS · 1001-5000 employeessimulated See all 7 comments
“no named customers, no proof behind "14.2x ROI."”
Chief Marketing Officer, B2B Services · 1001-5000 employeessimulated “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 employeessimulated “"$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…” Show full quote
“"$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 employeessimulated “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 employeessimulated “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…” Show full quote
“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 employeessimulated “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 employeessimulated The value claim rests on attribution accuracy that the page does not evidence
1 of 15
“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…” Show full quote
“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 employeessimulated
Clarity
The workflow mechanism is understandable, even where the marketing headers get in the way
5 of 15
“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 employeessimulated See all 5 comments
“Event lead capture app that syncs to your CRM and claims ROI tracking per event.”
Chief Marketing Officer, B2B Services · 1001-5000 employeessimulated “The mechanism walkthrough (scan → enrich → outreach → CRM sync → opportunity → attributed revenue) was concrete enough that I could picture the workflow, which is more…” Show full quote
“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 employeessimulated “"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…” Show full quote
“"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 employeessimulated “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…” Show full quote
“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 employeessimulated
Relevance
The problem statement and audience land immediately, without requiring inference
6 of 15 · what worked
“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…” Show full quote
“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 employeessimulated See all 5 comments
“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…” Show full quote
“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 employeessimulated “"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 employeessimulated “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…” Show full quote
“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 employeessimulated “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…” Show full quote
“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 employeessimulated
Brand alignment
Early-stage positioning reads as not enterprise-ready
6 of 15
“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 employeessimulated See all 5 comments
“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 employeessimulated “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…” Show full quote
“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 employeessimulated “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…” Show full quote
“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 employeessimulated “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 employeessimulated
05
How this works
Who we simulated (15 personas)
15 AI-simulated personas matched to your target market. Each answered independently, without seeing your goal, the scoring criteria, or each other’s answers. Attribution is role, industry and company size only.
Field Marketing DirectorSaaS · 1001-5000 employeesUS
Business Development ManagerSoftware · 201-500 employeesEU
Business Development DirectorTechnology Services · 501-1000 employeesUS
Chief Marketing OfficerB2B Services · 1001-5000 employeesEU
Senior CMOSaaS · 201-500 employeesUS
Director of MarketingSoftware · 501-1000 employeesEU
Senior Director of MarketingTechnology Services · 1001-5000 employeesUS
Field Marketing ManagerB2B Services · 201-500 employeesEU
Field Marketing DirectorSaaS · 501-1000 employeesUS
Business Development ManagerSoftware · 1001-5000 employeesEU
Business Development DirectorTechnology Services · 201-500 employeesUS
Chief Marketing OfficerB2B Services · 501-1000 employeesEU
Senior CMOSaaS · 1001-5000 employeesUS
Director of MarketingSoftware · 201-500 employeesEU
Senior Director of MarketingTechnology Services · 501-1000 employeesUS
Methodology
Every answer on this page was written by an AI model role-playing a buyer profile, scored on Wynter’s B2B Message Layers framework. The personas were sampled in code across role, industry, company size and behavioral traits; the model wrote only the answers. Scores arrive through fixed verdict categories and the counts are computed in our own code, so no number here was written by a model.
Score details: the count and the strength
The count is how many personas cleared the bar on each question. A yes can be unhesitating or come with reservations; the scorecard counts both as a yes, and this is the only place the difference is shown. Per layer:
- Clarity: 15 of 15, 6 without hesitation, 9 with reservations
- Relevance: 15 of 15, 11 without hesitation, 4 with reservations
- Value: 8 of 15, all with reservations
- Differentiation: 3 of 15, all with reservations
These answers are AI-simulated and directional. Validate anything you’re betting on with real buyers, your ICPs.
Your next 3 moves
- 1.Add a comparison line stating per-event pricing versus per-seat badge scanners
- 2.Replace the demo dashboard's ROI figures with one named customer's event result
- 3.Replace the eyebrow "Event Lead Orchestration" with plain words for what the app does
See what real buyers say.
A detailed, section-by-section message test report from verified B2B professionals who are actually in-market for what you sell.
Trusted by
RetentionThis report is kept for 60 days, until 10 Nov 2026, then deleted along with the personas, their answers and everything derived from them. The link stays live for that whole period so it can be shared or revisited, and stops working afterwards.
The email address it was requested from is kept beyond that, because it subscribes you to the newsletter — that was the price of the report. You can unsubscribe in one click from any issue, which stops the email without affecting a report still inside its 60 days. The public report page never shows the requester’s address.
The email address it was requested from is kept beyond that, because it subscribes you to the newsletter — that was the price of the report. You can unsubscribe in one click from any issue, which stops the email without affecting a report still inside its 60 days. The public report page never shows the requester’s address.