Clarity
Do they understand what you do?
15 could name what kind of product this is, unprompted.
https://demandos.com/15 AI-simulated buyers
Your message lands: they know what it is, who it's for, why it's worth their time, and 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?
15 could quickly tell what problem it solves and who it is for.
Do they actually want it?
12 would take a meeting to learn more.
Is there a reason to pick you over the alternatives?
11 could name a reason to pick you over a similar option.
Your page describes: Contact data. They said:
14 couldn't name one; 1 got it right.
Four separate measures, not stages: all 15 personas answered all four questions. Each square is one persona.
Rewrite "Thing we're hearing" as a real heading. 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: The strongest proof — named reps with live dial, connect and booked counts — is only implied by "Assign rep" and "Our reps can work your list." Show the actual roster table with the accountability it implies.
Why: The page never compares its price to running an in-house SDR, so buyers cannot judge the offer. State a cost per booked meeting or per verified mobile beside "See rate card."
4 of 15 raised this
“every stat on the page — 96% mobile coverage, 94% owner verified — is drawn from their own curated sample of 217 records, not my vertical”
These landed. Keep the wording when you edit around it.
The headline names the buyer and the problem without requiring inference
“For Vertical Software Companies / Find hard-to-identify owner mobile numbers" and "You sell to people who don't live on LinkedIn" tells me exactly who this is for”
The rep-level pod dashboard is the differentiator respondents named
“that's a number I can hold them to in a contract ("show me 15%+ connect-to-booked on my own list or we walk"), not just a marketing claim”
The offer would solve SDR time waste and reach hard-to-get owner numbers
“my reps would stop wasting half their week calling front desks and chasing dead LinkedIn profiles, and I'd get owner-level mobiles that actually connect”
Why: "Manufacturing owner" and "CEO, Legal software" saying "Clearly, this is working" prove nothing. Name the company, the vertical and the meetings booked per month.
Why: "Don't like cold calling? Our reps can work your list" leaves buyers unsure whether the list can be bought alone or whether calling is bundled into the price. Say which parts are separate.
Why: "Mobile coverage 96%" and "Owner verified 94%" float beside the table with no sample size, date or method. Add a one-line footnote naming the sample and how verification is performed.
4 of 15 raised this
“every stat on the page — 96% mobile coverage, 94% owner verified — is drawn from their own curated sample of 217 records, not my vertical”
Why: Nobody commits to a contact list sight unseen. Replace the vague "Continue →" with a named test — a sample of verified owner mobiles in the buyer's vertical and market before signing.
4 of 15 raised this
“every stat on the page — 96% mobile coverage, 94% owner verified — is drawn from their own curated sample of 217 records, not my vertical”
No specific edits needed here — this layer held up.
No specific edits needed here — this layer held up.
Why: The section label reads as a typo and carries no meaning to a scanning reader. Say what the recordings show — owners answering, meetings booked.
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's core numbers are treated as marketing, not evidence.
Five respondents said verification methodology, error rates and sourcing go unexplained, and one noted stats come from the vendor's curated sample; two more asked for competitive and cost-per-meeting benchmarks. Headline metrics carry no weight without…
The one asset respondents praised is also the one they suspect is fabricated.
Five named the rep-level pod dashboard the strongest differentiator, but two conditioned that entirely on the table being real rather than a mockup. A differentiator that needs verification before it lands is not yet doing its job.
The page never says what is actually being sold or what it costs.
Two respondents could not tell whether the list can be bought without rep dialing or whether the calling pod is priced in, and two more found no cost or competitive benchmark. Packaging and price are both absent.
The page cannot close; every path ends in an off-page proof request.
Respondents demanded a live pilot on their own accounts, named references in their vertical, GDPR answers, and cost-per-meeting proof against internal SDR economics. None of that exists on the page.
Naming the buyer is the page's only unambiguous win, and it happens before any of the hard questions.
Eight respondents said the header immediately identified vertical software companies and their pain, but every downstream theme — sourcing, price, packaging, compliance — is unresolved. Strong opening comprehension collapses into unanswered evaluation…
Respondents rewrote the category for the page because the page did not claim one.
Seven described the offer as two combined services — sourcing plus outsourced cold calling — and explicitly said it is not a list vendor or platform. The page forces buyers to construct its own positioning.
The rep-level pod dashboard is the differentiator respondents named
6 of 15 · what worked
“that's a number I can hold them to in a contract ("show me 15%+ connect-to-booked on my own list or we walk"), not just a marketing claim”
“seeing S. Kim at 1,412 dials, 226 connects, 16.0% booked rate, side by side with seven other named reps, is a level of operational transparency I haven't seen from a data vendor before”
“The thing that would actually tilt me toward this one over a competitor is the pod roster table with rep-level stats — S. Kim, 1,412 dials, 226 connects, 16.0% rate — that's a specific, checkable claim, not a vague "we book meetings" line.”
“The 16% connect-to-booked rates and the pod roster with named reps and live dial counts make it feel operational rather than theoretical”
“the one thing that would tip a decision either way is the pod roster stats — "1,412 Dials / 226 Booked / 16.0%" per rep — because that's an actual conversion number I could hold against my current SDR cost per meeting”
The coverage and verification percentages are unsourced and undocumented
4 of 15
“every stat on the page — 96% mobile coverage, 94% owner verified — is drawn from their own curated sample of 217 records, not my vertical”
“"verified" and "validating" are just status labels on a screen — I don't know their verification method, source, or error rate”
“I still wanted proof behind numbers like "96% mobile coverage" and "94% owner verified" — no methodology given, so I'd treat those as marketing until shown how "verified" is defined.”
The page gives no cost or competitive benchmark to evaluate against
2 of 15
“I'd want two or three logo-named references in my exact space before I even take the call, otherwise it's just a data vendor with a call center bolted on and I already have something adjacent that mostly covers this.”
“it's still not enough to rule anyone in or out, because there's no named account behind those numbers and no comparison to what coverage looks like for competitors.”
“A hard number: cost per booked meeting versus what I pay my own SDRs today, shown against a comparable vertical — if that math beats my current cost by a real margin, that's the only thing that gets me past "not my problem" into a conversation.”
Buying requires a live pilot and EU compliance answers the page does not give
2 of 15
“I'd want them to run 100-200 of my actual target accounts live before I'd believe it holds outside their demo data”
“I'd need to know data sourcing/compliance (GDPR matters a lot here since we're EU-based and they're clearly built for a US market with US area codes)”
The offer would solve SDR time waste and reach hard-to-get owner numbers
1 of 15 · what worked
“my reps would stop wasting half their week calling front desks and chasing dead LinkedIn profiles, and I'd get owner-level mobiles that actually connect”
Whether the calling pod is optional or bundled into pricing is unclear
2 of 15
“the page never actually says whether I can buy the list without the reps, and that ambiguity is what I'd want cleared up on the call”
“the copy never says plainly whether I can buy just 'Find + Validate' without the cold-calling pod, so I had to infer the packaging rather than being told it”
The offer reads as a bundled find-verify-dial service rather than a data platform
6 of 15
“it's really a data-sourcing service bolted onto an outsourced SDR/calling function — not a sales engagement platform at all.”
“contact data sourcing + verification + outsourced SDR dialing" as one bundled service, not just a list vendor”
“it's really two things bolted together: a contact data/enrichment service specifically for hard-to-reach SMB owners, plus an outsourced SDR calling service layered on top”
“They find, verify, and dial owner-level mobile numbers for hard-to-reach local business owners, then run cold-calling reps to book meetings on your calendar/CRM — basically a data-sourcing plus outsourced SDR-dialing service bundled together, not a straight sales engagement platform.”
“They find and verify owner mobile numbers for hard-to-reach small business owners, then have their own reps cold call that list to book meetings on your calendar.”
“They find owner mobile numbers for hard-to-reach local business owners (plumbers, roofers, marina owners, etc.), verify those numbers, and then have their own reps cold-call the list to book meetings that sync to your CRM. So it's really a three-part service: lead sourcing/enrichment (find owner contacts), data verification, and outsourced SDR/cold-calling”
The headline names the buyer and the problem without requiring inference
7 of 15 · what worked
“For Vertical Software Companies / Find hard-to-identify owner mobile numbers" and "You sell to people who don't live on LinkedIn" tells me exactly who this is for”
“the header "For Vertical Software Companies" and the subhead "You sell to people who don't live on LinkedIn" told me who this is for and the problem in one breath”
“the header "For Vertical Software Companies" plus the subhead "Find hard-to-identify owner mobile numbers... You sell to people who don't live on LinkedIn" told me both the problem and the reader in one line.”
“The problem is spelled out again in the "Are you paying the data quality tax?" checklist ("Reps call front desks because owner mobile numbers are missing," "reps spend more time researching contacts than dialing") which nails the actual operational pain”
“For Vertical Software Companies" as the header, then "Find hard-to-identify owner mobile numbers" and "You sell to people who don't live on LinkedIn" tells me exactly who this is for (B2B software selling into fragmented, offline verticals like plumbing, dental, marinas, auto repair)”
“the header "For Vertical Software Companies" plus "You sell to people who don't live on LinkedIn" told me in one line who this is for and what problem it solves”
“the header "For Vertical Software Companies / Find hard-to-identify owner mobile numbers" tells you the reader (vertical SaaS/software sellers) and the problem (can't find owner mobile numbers because "you sell to people who don't live on LinkedIn") in the first two lines. No hunting needed, no inference required.”
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.







