Clarity
Do they understand what you do?
15 could name what kind of product this is, unprompted.
https://www.resemble.ai/products/detect15 AI-simulated buyers
Your message needs work: they know what it is, who it's for, and why it's worth their time, but not 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?
14 could quickly tell what problem it solves and who it is for.
Do they actually want it?
14 would take a meeting to learn more.
Is there a reason to pick you over the alternatives?
6 could name a reason to pick you over a similar option.
Your page describes: deepfake detection. They said:
15 got it right.
Four separate measures, not stages: all 15 personas answered all four questions. Each square is one persona.
Five respondents described the voice as confident and feature-forward rather than analytical, missing board-level risk framing, telecom-specific credibility, and case studies. One noted it casts a wide net instead of owning one lane. 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 per-model coverage list of named generators with accuracy per model is the only claim buyers said they could test, and it sits below general benchmark copy. Put it high on the page so the specific evidence lands before the broad claims.
Why: Buyers had to infer the audience from compliance wording rather than read it. State it outright, for example fraud and security teams at banks and contact centers screening inbound voice calls.
7 of 15 raised this
“Who it's for is less explicit — it's not stated as "built for CISOs" or "for government," but the mentions of "compliance teams, legal review, and trust & safety workflows" and later "Built for regulated industries" let me infer the buyer without much digging.”
These landed. Keep the wording when you edit around it.
Explainability and exportable audit trails are the value respondents actually want
“the explainability angle — audit trails, artifact-level reasoning, "why it was flagged not just that it was" — would matter for our compliance and trust & safety workflows, since our current tools mostly just give a score with no rationale to hand to legal or regulators”
The named per-model coverage table is the most credible differentiator on the page
“The "250+ generative AI models tested against in real time" with named coverage — ElevenLabs, Midjourney, Kling, Sora, etc. — with specific per-model accuracy numbers (99% Flux, 98% Midjourney, 94% Stable Diffusion) is the one thing that could tip a shortlist decision, because most competitors just say "detects deepfakes" without naming what they actually beat”
The multimodal detection promise comes through clearly
“takes in audio, video, or images and returns a verdict plus an explanation of why something's flagged as AI-generated or manipulated, rather than just a bare score”
Why: Accuracy percentages appear with no named dataset, test date, or false-positive rate, so buyers discount them and assume a vendor-run test. State what corpus was used, when, and the false-positive rate next to each number.
Why: Nothing on the page says what this does that a competing detection vendor does not. Write one line naming the specific difference, verdict with explanation and exportable audit trail, plus on-prem deployment.
No specific edits needed here — this layer held up.
No specific edits needed here — this layer held up.
Why: The voice reads as product marketing rather than security, so security and fraud leaders discount it before reaching the evidence. Lead with the loss being prevented and the regulatory exposure, not the capability list.
4 of 15 raised this
“it's confident and feature-forward ("Up to 99.5% accuracy," "Zero day coverage") but skips the thing I'd actually want first — a named financial-services logo or a board-level risk framing”
Why: Security buyers are already asking where audio is processed and stored, and the page leaves it to them. Answer it plainly beside the on-prem line: what stays on their infrastructure and what the audit trail exports.
4 of 15 raised this
“it's confident and feature-forward ("Up to 99.5% accuracy," "Zero day coverage") but skips the thing I'd actually want first — a named financial-services logo or a board-level risk framing”
Why: The page switches between verdict and score and varies the product name, which blurs the exact distinction it is selling on. Pick one label for the output, define it once, and use it everywhere.
4 of 15 raised this
“it's confident and feature-forward ("Up to 99.5% accuracy," "Zero day coverage") but skips the thing I'd actually want first — a named financial-services logo or a board-level risk framing”
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 own numbers are its weakest asset, and the differentiator only survives where the numbers are specific enough to be checked.
Five respondents discounted accuracy and model-count claims as unsourced, two ranking the page behind Pindrop and Actimize; the per-model table earned credit from four precisely because it can be tested, and one still wants independent verification.
The core differentiator is undermined by the page's own copy before a buyer can evaluate it.
Two respondents said verdict and score are used interchangeably and the product name varies across the page, while five others cite verdict-plus-explanation as the value that closes their compliance gap. The page blurs the exact distinction it is selling.
Buyers have to assemble the audience themselves, which turns qualification into guesswork.
Six respondents inferred the target persona from compliance language and scattered context clues rather than reading it stated; only one found problem and audience clear in the first two lines.
The voice disqualifies the page from the enterprise security deals its own strongest proof points are built for.
Five respondents read the tone as startup product marketing missing board-level risk framing, telecom credibility and case studies, while on-prem deployment and exportable audit trails are procurement- and compliance-grade assets being sold in the wrong…
Clarity about what the product does is not translating into belief that it works.
Only three respondents restated the multimodal verdict promise, while five discounted the accuracy claims as unvalidated and five found the voice feature-forward rather than analytical. Comprehension is shallower than the doubt.
Spreading across every use case costs the page the one lane where it is most credible.
One respondent said the page casts a wide net instead of owning a lane, and the assets that land — on-prem procurement fit and audit-trail compliance — are narrow, specific claims cited by three and five respondents respectively.
The named per-model coverage table is the most credible differentiator on the page
4 of 15 · what worked
“The "250+ generative AI models tested against in real time" with named coverage — ElevenLabs, Midjourney, Kling, Sora, etc. — with specific per-model accuracy numbers (99% Flux, 98% Midjourney, 94% Stable Diffusion) is the one thing that could tip a shortlist decision, because most competitors just say "detects deepfakes" without naming what they actually beat”
“the "attack coverage" list — voice clone, replay attack, face swap, partial edit, synthetic image, live call interception, video conferencing, reverse image search all marked "DETECTED" — because that's specific enough to test against”
“The "250+ generative AI models tested against in real time" table with specific accuracy numbers per model — DALL-E 3 at 98%, Flux at 99%, Veo at 99% — is more concrete than most vendors give me, and would make me pick this over a competitor that just claims "industry-leading accuracy" with no breakdown.”
“The 250+ model coverage table with named generators — ElevenLabs, Sora, Kling, Veo, Suno, StyleGAN — broken out by modality is the one thing that would put this ahead of a vaguer competitor, because it's checkable”
The intended buyer is never named on the page
7 of 15
“Who it's for is less explicit — it's not stated as "built for CISOs" or "for government," but the mentions of "compliance teams, legal review, and trust & safety workflows" and later "Built for regulated industries" let me infer the buyer without much digging.”
“The who is inferred, not spelled out: it's built for "compliance teams, legal review, and trust & safety workflows that need evidence, not just a score," plus the industry callout and the Zoom/Teams/Meet/Webex angle points at contact-center and fraud/security roles like mine. So problem: clear and fast. Intended reader: I had to piece it together”
“A line naming my industry and my exact pain point directly — something like "built for insurance and financial-services fraud teams fighting synthetic voice claims and impersonation in claims calls" — rather than making me infer it from a generic Zoom/Teams/compliance list”
“the intended reader is never stated outright — there's no "for security teams at banks" or "for contact center fraud analysts" line anywhere”
“Pretty much instant — the hero line "Know what's real with multimodal deepfake detection" plus "Most tools return a score. Resemble Detect returns a verdict and an explanation" told me the problem (score-only tools aren't enough, you need evidence) within the first two lines.”
“the intended reader is never explicitly named upfront — I had to infer it from scattered mentions”
“the intended reader is never explicitly named; I had to infer it from scattered mentions”
On-prem deployment reads as a concrete procurement advantage
3 of 15 · what worked
“real-time voice clone and live-call-interception detection inside our existing contact center stack means fewer successful vishing/social-engineering fraud losses I have to explain after the fact”
“the on-prem/data residency mention buried in the header ("Available on-prem or in the cloud via API") matters a lot given my procurement constraints”
Explainability and exportable audit trails are the value respondents actually want
4 of 15 · what worked
“the explainability angle — audit trails, artifact-level reasoning, "why it was flagged not just that it was" — would matter for our compliance and trust & safety workflows, since our current tools mostly just give a score with no rationale to hand to legal or regulators”
“a real-time flag with an audit trail ("exportable for legal, compliance, and regulatory review") could close a gap our current monitoring doesn't touch”
“The "audit trail: exportable for legal, compliance, and regulatory review" line is the part that actually matters to me, not the accuracy percentages.”
Accuracy and model-count claims are unsourced, so respondents discount them
4 of 15
“the 99.5% accuracy and "250+ models" figures need a named source or independent benchmark before I'd put any weight on them”
“An independent third-party test showing the on-prem build hits comparable accuracy against attack types we actually see — voice clone and replay attacks on live telco call traffic — not just their own benchmark page; without that, it doesn't get past the first meeting”
“I'd want their false-positive rate on our actual call volume and a couple of reference customers in insurance or BFSI before I take this past a first call — those benchmark numbers mean nothing until I see them against my traffic, not theirs”
“If a competitor on my shortlist shows me a false-positive rate and one client in financial services, they win the meeting over this page as written”
“I'd need the accuracy numbers sourced against a named benchmark before I trust the 99.5% figure”
Inconsistent naming muddies the verdict-versus-score distinction
2 of 15
“"verdict" and "score" get used almost interchangeably later in the page (accuracy percentages everywhere) even though the whole pitch is verdict-not-score, so the copy slightly undercuts its own distinction”
“it's called "deepfake detection" in the hero, then "authenticity scoring," "explainable detection," and "Resemble Intelligence" as if those are separate things, so I'm left doing the work of collapsing four marketing names into one product in my head.”
The multimodal detection promise comes through clearly
3 of 15 · what worked
“takes in audio, video, or images and returns a verdict plus an explanation of why something's flagged as AI-generated or manipulated, rather than just a bare score”
The tone reads startup product-marketing, not enterprise security
4 of 15
“it's confident and feature-forward ("Up to 99.5% accuracy," "Zero day coverage") but skips the thing I'd actually want first — a named financial-services logo or a board-level risk framing”
“the total absence of company facts — no "founded in," no customer logos I recognize, no team size — so I'm inferring their maturity from confidence and polish, not evidence, and that's a gap a page this specific about accuracy percentages should have closed”
“there's no telecom-specific case study, no logo I recognize from telco fraud, and the "trusted partners" section is just a placeholder line with no names shown to me”
“the tone is still more product-marketing than analyst-brief: punchy claims, demo videos, benchmark tables with no methodology”
“the copy has that slightly breathless "we test 250+ models" startup energy rather than the buttoned-up tone of an established enterprise security player”
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.







