Clarity
Do they understand what you do?
15 could name what kind of product this is, unprompted.
https://www.worldpay.com/en-GB15 AI-simulated buyers
Your message needs work: they know what it is and who it's for, but not why it's worth their time or why to pick you.
Do they understand what you do?
15 could name what kind of product this is, unprompted.
Can they tell what it solves, and who it's for?
9 could quickly tell what problem it solves and who it is for.
Do they actually want it?
5 would take a meeting to learn more.
Is there a reason to pick you over the alternatives?
0 could name a reason to pick you over a similar option.
Your page describes: payments. They said:
15 got it right.
Four separate measures, not stages: all 15 personas answered all four questions. Each square is one persona.
Seven respondents said the copy treats a pub group, restaurant, or single-site operator as a generic SMB and never names hospitality-specific problems, solutions, or reference customers. 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 humansThe 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.
Why: Nothing on the page says why to switch from the processor already sitting on the counter. Name the differences a buyer can check: settlement speed, fee structure, contract length, approval rates.
2 of 15 raised this
“Nothing on the page told me what's actually different from what we've got now - lots of buzzwords like "optimise," "embed," "agentic commerce" but no concrete numbers on authorization rates or cost savings.”
Why: "Smarter routing, intelligent retries and higher authorization rates" promises more approvals without a number. State the approval rate lift a comparable business saw and over what period.
9 of 15 raised this
“there's no number on any of it. No "X% uplift in approvals" or "Y% fewer chargebacks" that I could hold them to”
Why: "Boost revenue, innovate at pace and create payment experiences their customers love" names no problem a buyer would recognise. Write the pain instead: declined cards, slow payouts, card fees eating margin.
8 of 15 raised this
“the actual problem being solved is vague - it's all "boost revenue, innovate at pace" type lines, and the five solution tiles (Accept, Protect, Optimise, Embed, Move money) read like a menu of features rather than a problem statement. So the "who" is obvious fast, the "why now" isn't - I'd need a specific pain point or stat tied to my situation, not just "payments at the speed of life."”
These landed. Keep the wording when you edit around it.
The five-card payment stack breakdown explained the offering
Why: Readers cannot tell if this competes with their till system or sits behind it. Say plainly that it processes payments through the POS they already use, and name the ones it works with.
2 of 15 raised this
“Nothing on the page told me what's actually different from what we've got now - lots of buzzwords like "optimise," "embed," "agentic commerce" but no concrete numbers on authorization rates or cost savings.”
Why: Scale numbers from Amazon and Tesco tell a two-site operator nothing about their own outcome. Lead the SMB block with a result from a business their size.
2 of 15 raised this
“Nothing on the page told me what's actually different from what we've got now - lots of buzzwords like "optimise," "embed," "agentic commerce" but no concrete numbers on authorization rates or cost savings.”
Why: The SMB section promises a quote but discloses no transaction fee, monthly cost or how long setup takes. Give a starting rate and a go-live timeframe.
9 of 15 raised this
“there's no number on any of it. No "X% uplift in approvals" or "Y% fewer chargebacks" that I could hold them to”
Why: "Enable streamlined fund management and embedded finance... unlocking new revenue streams" lists capability and leaves the payoff to the reader. Say what each one lets a business do: fewer declines, money in the account same day.
9 of 15 raised this
“there's no number on any of it. No "X% uplift in approvals" or "Y% fewer chargebacks" that I could hold them to”
Why: A pub group or single-site restaurant reads "businesses of all sizes" and cannot tell the page is for them. Name the trade and the setting, including tipping, table service and card machines.
8 of 15 raised this
“the actual problem being solved is vague - it's all "boost revenue, innovate at pace" type lines, and the five solution tiles (Accept, Protect, Optimise, Embed, Move money) read like a menu of features rather than a problem statement. So the "who" is obvious fast, the "why now" isn't - I'd need a specific pain point or stat tied to my situation, not just "payments at the speed of life."”
Why: One-word labels plus "embedded payments" and "routing" force the reader to decode. Spell out in everyday words what each does.
2 of 15 raised this
“words like "embedded payments," "fund management" and "routing" needed unpacking — they're industry shorthand, not plain English”
Why: Every reference customer is an enterprise airline, publisher or software firm, so hospitality readers see no one like themselves. Add a pub group or restaurant chain with its result.
7 of 15 raised this
“The "Small and mid-sized businesses" section with "Apply online" is clearly meant to catch people like me, but the copy there is just as generic as the enterprise pitch - no SME-specific pain point, cost comparison, or reason tailored to a company our size.”
Why: Small operators are told to think big and then handed enterprise scale figures, which reads as an afterthought. Lead with their situation in their words.
7 of 15 raised this
“The "Small and mid-sized businesses" section with "Apply online" is clearly meant to catch people like me, but the copy there is just as generic as the enterprise pitch - no SME-specific pain point, cost comparison, or reason tailored to a company our size.”
Why: Aspirational headings say nothing a competitor could not also say. State the job: take card payments in store and online and get paid faster.
7 of 15 raised this
“The "Small and mid-sized businesses" section with "Apply online" is clearly meant to catch people like me, but the copy there is just as generic as the enterprise pitch - no SME-specific pain point, cost comparison, or reason tailored to a company our size.”
A deliberately adversarial read of the same answers. Each claim was checked back against what the personas said and dropped if nothing supported it.
The page gives a reader nothing to evaluate — no problem, no numbers, no price.
Nine respondents found the problem framing generic and statistic-free, eleven found every value claim unquantified, and others flagged missing cost, setup time and switching detail. Three separate layers of the argument are empty.
Unquantified claims like 'smarter routing' and 'authorisation rates' read as boilerplate any competitor could publish.
Eleven respondents asked for before-and-after authorisation or decline figures from a comparable business, and two could not articulate any advantage over an incumbent POS processor. Without numbers the claims carry no competitive weight.
The page loses the small-business reader it claims to address.
Seven respondents said a pub group, restaurant or single-site operator is treated as a generic SMB with no hospitality problems or reference customers, while four read the positioning as enterprise procurement with SMBs bolted on.
Naming audience segments is being mistaken for speaking to them.
Nine respondents noted the page labels its segments clearly yet never states a concrete business problem, and seven could not find themselves in the copy. The labels are doing the work the content should.
The one section that works is buried under the section that doesn't.
A respondent singled out the five-card payment stack as explaining the offering better than the problem statement above it — the same statement nine respondents called vague. The page leads with its weakest asset.
Feature labels are compressed to the point of meaninglessness.
Respondents said 'Embed' and 'Optimise' are unclear without a sub-line and that terms like embedded payments and routing need unpacking. Compression is compounding the absence of any concrete problem statement.
Respondents could not say how this beats their existing POS processor
2 of 15
“Nothing on the page told me what's actually different from what we've got now - lots of buzzwords like "optimise," "embed," "agentic commerce" but no concrete numbers on authorization rates or cost savings.”
“they just sit underneath checkout and move the money”
Every value claim is unquantified — no metrics, no before-and-after
9 of 15
“there's no number on any of it. No "X% uplift in approvals" or "Y% fewer chargebacks" that I could hold them to”
“"smarter routing, intelligent retries," "advanced fraud screening," "reducing chargebacks" - has no figures attached, so there's nothing to compare against a competitor's shortlist entry”
“A concrete before/after authorization-rate number from a business our size — e.g. "independent hospitality venue went from 91% to 97% approvals" — that's the one outcome that would turn this from a vague label”
“no numbers, no case study with our kind of volume, nothing I could hold them to”
“smarter routing, intelligent retries, higher authorisation rates - that's the bit that matters to me since I'm specifically trying to fix acceptance reliability right now. But the page gives me zero numbers to back that: no "X% uplift in authorisations"”
“A named small hospitality or single-site customer with an actual stat - something like "cut declines by X% for a 20-cover restaurant" - that's the one thing that would make me pick up the phone”
“even those are just "Worldpay helps take flight" style lines with a "Read more" link, not a stat I can hold onto.”
“there's nothing here that tells me by how much, or how it works mechanically - no "reduced false declines by X%" or a named hospitality customer saying "we went from Y to Z".”
“The customer logos - Amazon, Tesco, bet365 - are the one thing that actually registers as a reason to shortlist rather than rule out, because that's real proof of scale rather than a slogan. But there's nothing else to differentiate on: the customer stories for Virgin Atlantic, Springer Nature and Reynolds and Reynolds just say "turns to Worldpay for integrated payments" with no numbers - no uplift %, no processing time, nothing I could compare against a rival's case study.”
“at least that's a real company I could ring up and ask "did this actually cut your decline rate." But even those are just one-line taglines”
“it's travel, not hospitality, and there's no before/after number attached — no "reduced declines by X%" or "cut settlement time from Y to Z days." Against a competitor with even one named hotel or restaurant group and a hard figure, this page loses”
The problem statement is vague marketing language that names no specific pain
8 of 15
“the actual problem being solved is vague - it's all "boost revenue, innovate at pace" type lines, and the five solution tiles (Accept, Protect, Optimise, Embed, Move money) read like a menu of features rather than a problem statement. So the "who" is obvious fast, the "why now" isn't - I'd need a specific pain point or stat tied to my situation, not just "payments at the speed of life."”
“nothing says "hospitality" or "restaurants/hotels" anywhere on this page, so I had to piece together my fit rather than be told it. The problem being solved is generic too — "boost revenue, innovate at pace and create payment experiences" is marketing language, not a stated pain point”
“the actual problem being solved is vague - "boost revenue, innovate at pace and create payment experiences customers love" is just marketing fluff, not a problem statement”
“It's reasonably quick to see who it's for - "Small and mid-sized businesses," "Enterprise," and "Software platforms" sections spell out the audience in plain headers, so I didn't have to hunt for that. The problem being solved is vaguer though”
“nothing in those segments speaks to a one-till restaurant specifically; I can see I'm meant to self-sort into the SMB bucket, but the actual problem being solved for someone like me — day-to-day checkout — isn't spelled out, it's buried under enterprise-scale language like "$2.3 trillion annually."”
“I'd want a small-retail or hospitality example sitting alongside the Enterprise and Software platforms blocks — something like a case study tile titled "Bars & Hospitality" with a one-line result”
Jargon and one-word feature labels block comprehension
2 of 15
“words like "embedded payments," "fund management" and "routing" needed unpacking — they're industry shorthand, not plain English”
“It wasn't the category that was hard, it was the single-word labels — "Embed" and "Optimise" read as jargon on their own, I only got the meaning from the smaller sub-line underneath each one, so it took a second pass.”
Pricing, setup time, and switching details are absent
2 of 15
“there's nothing concrete on cost or fees for someone like me - a small restaurant - so I couldn't tell you how this beats my current basic checkout system in actual pounds saved”
“didn't tell me anything about cost, setup time, or what switching actually involves for a small outfit like mine”
The five-card payment stack breakdown explained the offering
1 of 15 · what worked
Hospitality and small-business readers cannot find themselves on the page
7 of 15
“The "Small and mid-sized businesses" section with "Apply online" is clearly meant to catch people like me, but the copy there is just as generic as the enterprise pitch - no SME-specific pain point, cost comparison, or reason tailored to a company our size.”
“the Amazon and Tesco logos, the "$2.3 trillion annually" figure, and case studies like Virgin Atlantic and Springer Nature all scream "we're built for large corporates" not a one-till restaurant”
“It reads like a company that's used to selling to large, recognisable brands and is trying to stretch down to SMBs almost as an afterthought - "Small and mid-sized businesses... get a quote in minutes" feels bolted onto a page that's really built around enterprise scale”
“There's nothing here saying "here's what a small restaurant saves or gains," just enterprise proof points like "$2.3 trillion annually" and named big brands like Amazon and Tesco — that's not built for me, it's built for someone managing multi-market payment infrastructure.”
“A named small hospitality or single-site customer with an actual stat - something like "cut declines by X% for a 20-cover restaurant" - that's the one thing that would make me pick up the phone”
The page reads as enterprise-first with SMBs bolted on
4 of 15
“It reads like a company that's used to selling to large, recognisable brands and is trying to stretch down to SMBs almost as an afterthought - "Small and mid-sized businesses... get a quote in minutes" feels bolted onto a page that's really built around enterprise scale”
“Who they sell to is clearly split three ways — SMBs, enterprise, and software platforms — so they're trying to be everything to everyone, which is typical of an incumbent defending share rather than a focused challenger with a sharp point of view.”
“the Amazon and Tesco logos, the "$2.3 trillion annually" figure, and case studies like Virgin Atlantic and Springer Nature all scream "we're built for large corporates" not a one-till restaurant”
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.
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.
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:
These answers are AI-simulated and directional. Validate anything you’re betting on with real buyers, your ICPs.
A detailed, section-by-section message test report from verified B2B professionals who are actually in-market for what you sell.







