Clarity
Fix firstDo they understand what you do?
Fail3 of 15
3 could name what kind of product this is, unprompted.
Saved report, kept for 60 days — expires in 47 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?
Strong14 of 1514 would take a meeting to learn more.
Differentiation
Is there a reason to pick you over the alternatives?
Mixed9 of 159 could name a reason to pick you over a similar option.
See what they thought you were
Your page describes: B2B prospecting intelligence. They said:
- 1×Sales intent / signal-based lead generation toolwrong
- 1×Sales intent data / outbound automation toolwrong
- 1×Sales intent signal / prospecting toolwrong
- 1×Sales intent-signal / outbound prospecting toolwrong
- 1×Sales intent/signal-based prospecting toolwrong
10 couldn't name one; 5 named the wrong one.
Four separate measures, not stages: all 15 personas answered all four questions. Each square is one persona.
Additional signalBrand alignment15 of 15StrongShow finding ▸
Two respondents said the visual proof worked against the page: incomplete screenshots undercut the authenticity the founder tone had built, and the logo wall carried no named case studies or customer quotes to back the claims. 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.
Define how the fit score is calculated, beside the score.
Why: The page shows precise numbers — 94, 88, 86 — under a column called "Fit" and a card labelled "Fit score / 100", but never says what goes into them. Readers said they could not act on the recommendations without seeing the scoring logic, which is doubly awkward because the page also promises "Not a score, not a percentage." Add one line under the queue table naming the inputs, e.g. "Fit = signal recency + role seniority + your ICP filters (company size, stage, title). No black-box intent…
3 of 15 raised this
“the only soft spot is "fit score" being thrown around before you know how it's calculated”
Head of Sales Development, SaaS · 11-50 employeessimulated Moves ClarityProof next to the claimPut MCP access through Claude and Cursor above the fold.
Why: The clearest thing on this page that rivals cannot claim — querying the queue from Claude or Cursor over MCP — never appears in the copy tested here, and where it does surface it reads as a placeholder rather than something working today. Give it a named section with a real example of what a rep types and what comes back, and say whether it ships today or is in beta. That is the reason to choose this over any other signal tool.
Moves DifferentiationGive a reason to choose youAttach the reply-rate numbers to the accounts that produced them.
Why: The headline metrics were discounted because the proof rests on two accounts over 90 days and the caveat sits away from the claim. Move the sourcing next to each number: who, what volume, what period, what baseline they replaced. "90% reached the same day" and "9,090 in queue right now" mean little without knowing whose pipeline they came from. Named results from Payoneer or Sommo beside the figure would carry more than the unnamed logo wall does.
6 of 15 raised this
“which is a sample size I wouldn't hang a purchase decision on, and I'd want to see it across more accounts and a longer window”
Sales Development Representative, SaaS · 51-200 employeessimulated Moves ValueProof next to the claim
Keep these · 3
These landed. Keep the wording when you edit around it.
- Keep · Clarity
The problem and audience land within the first two lines
“the headline "Twenty people worth writing to. Every morning." plus the "paste a LinkedIn URL, we show you everyone who engaged" bit tells you in ten seconds this…” Show full quote
“the headline "Twenty people worth writing to. Every morning." plus the "paste a LinkedIn URL, we show you everyone who engaged" bit tells you in ten seconds this is for outbound sales/SDR types”
Sales Manager, Technology · 1-10 employeessimulated - Keep · Differentiation
Respondents named MCP integration through Claude and Cursor as the differentiator
“"Your signals live inside Claude and Cursor through MCP... Nobody else in this category has this" — is the one thing that would actually tip a shortlist decision”
Sales Development Representative, SaaS · 51-200 employeessimulated - Keep · Value
The claimed lift is large enough to justify a workflow change if it survives validation
“If the numbers hold — 55% acceptance vs 24% cold, 30% LinkedIn reply vs 6%, 8% email reply vs 2% — that's a real jump over what I'm…” Show full quote
“If the numbers hold — 55% acceptance vs 24% cold, 30% LinkedIn reply vs 6%, 8% email reply vs 2% — that's a real jump over what I'm doing manually right now”
Business Development Representative, B2B Services · 1-10 employeessimulated
03
All recommendations
Clarity
Fail3 of 15Moves ClarityPlain language
Stop contradicting yourself on scores versus plain-words signals.
Why: "Signal, in plain words — 'Hiring a Head of Growth, posted this morning.' Not a score, not a percentage" sits directly above tables whose most prominent column is a numeric Fit score. Readers flagged the terminology as muddled. Rewrite that block to say the signal is always quotable plain text and the score only orders the queue, e.g. "The signal is a sentence you can quote. The score only decides what you read first."
3 of 15 raised this
“the only soft spot is "fit score" being thrown around before you know how it's calculated”
Moves ClarityConclusion first
Rank the eleven signals instead of listing them flat.
Why: "Eleven signals. Every one you can quote." then a flat eleven-row table buries the point that a handful drive the results. The line "The three at the top produce most of the replies" is contradicted by the table, which is sorted by detection speed and where "Company followers" is separately called "The highest-converting source we have." Split the table into "The three that produce most replies" and "Also watched", and make clear one engine reads all of them.
3 of 15 raised this
“the only soft spot is "fit score" being thrown around before you know how it's calculated”
Differentiation
Mixed9 of 15Moves DifferentiationGive a reason to choose you
Turn the quotable-signal test into a head-to-head comparison.
Why: "The only test we apply" and the "WE DON'T CHASE" list are the sharpest differentiating idea on the page, but they are framed as internal policy rather than a contrast a buyer can use. Rewrite as a two-column comparison — what intent-data vendors send you (page views, topic scores, unnamed accounts) versus what arrives in your queue (a named person, a dated public action, a quotable first line) — so the choice is visible without body copy.
Value
Strong14 of 15Moves ValueAnswer the live objection
Answer the "will it work on my data" objection with a pilot offer.
Why: Readers said they would only believe the lift after seeing it on their own volume, and the page leaves that unresolved — the free scan of a single LinkedIn post URL is not the same thing. Add a short block answering it directly: what a pilot on their own ICP looks like, how many days before the first queue arrives, and what a success threshold would be. Keep "Scan it free" as the entry point but say where it leads.
6 of 15 raised this
“which is a sample size I wouldn't hang a purchase decision on, and I'd want to see it across more accounts and a longer window”
Relevance
Strong15 of 15Moves RelevanceName the audience
Name the role and team size the queue is built for.
Why: Readers worked out who this was for from workflow mechanics — the fifteen-minute queue, the j/k/a/e keys — rather than from any line they could point at. Add a named-audience line under the headline, e.g. "For founders and two-to-ten-person outbound teams doing their own prospecting" and state whether it suits an SDR pod or a solo seller. It costs one line and stops the reader inferring.
4 of 15 raised this
“I'd want a line naming the role directly — "built for BDRs and SDRs running outbound" — plus a mention of team size or quota context, so I'm…” Show full quote
“I'd want a line naming the role directly — "built for BDRs and SDRs running outbound" — plus a mention of team size or quota context, so I'm not inferring it from workflow details”
Brand alignment
Strong15 of 15Moves Brand alignmentProof next to the claim
Replace the bare logo wall with one named customer result.
Why: "Teams already running on B2B Signals" followed by Payoneer, Sommo, ERA and the rest carries no name, number or quote, and the incomplete product screenshots read as unfinished next to the plain-spoken founder voice everywhere else. Swap one logo for a two-line attributed result — person, role, company, what changed — and finish the screenshots so what is shown matches what the copy promises.
2 of 15 raised this
“the parts that don't are the ones still marked "capture pending," which undercuts the otherwise credible, practitioner voice”
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 core numbers are its largest liability, and the honesty of the caveat does not rescue them.
Six of 15 respondents — the largest theme on the page — discounted or dismissed the headline reply-rate and acceptance metrics because the proof rests on two accounts over 90 days, and several demanded a live pilot on their own data before believing anything. One explicitly said the sample-size caveat undercut the metrics even while reading as honest, so the disclosure buys goodwill and costs belief at the same time.
- high
Every positive result on the page is conditional on proof the page does not supply, so nothing here can be banked.
The value upside is explicitly conditional — the two respondents who said the lift would justify a workflow change tied it to results holding beyond the pilot. The differentiator is qualified the same way, with one of three respondents calling MCP integration an unverified placeholder rather than something demonstrated. Meanwhile six respondents rejected the proof outright. The page's wins are promissory notes drawn on an account six people said is empty.
- high
Quantified claims are actively counterproductive because the page publishes numbers it will not explain.
Three respondents said the fit score is quoted as a precise number with no definition, and stated they could not accept the recommendations without transparent scoring logic. Precision without derivation reads as a claim to be checked rather than a benefit to be enjoyed, and the same suspicion falls on the reply-rate figures six respondents already discounted.
- high
The visual proof cancels out the founder tone the page works to establish.
Two respondents said incomplete screenshots undercut the authenticity the founder voice had built, and that the logo wall carries no named case studies or customer quotes. Combined with the two-account sample flagged by six respondents, the page shows logos it cannot substantiate and screenshots it cannot complete — the assets meant to prove the claims are the ones inviting doubt.
- medium
The page never names its reader, forcing every prospect to self-qualify from mechanics.
Four respondents reverse-engineered the target reader from workflow detail rather than any explicit statement, and one asked directly for role naming and team size. Clarity of problem does not substitute for clarity of audience: readers should not have to audit the workflow to learn whether the product is for them.
- medium
Renaming established categories hides the product's actual architecture from buyers.
Two respondents said the copy conflates signal, queue and fit score with proprietary feature names, and that listing signal types without ranking obscures the fact that a single engine drives all of them. Paired with the three respondents who could not get a definition of the fit score, the vocabulary problem is not stylistic — it is concealing how the product works.
Clarity
The fit score is quoted as a precise number but never defined
3 of 15
“the only soft spot is "fit score" being thrown around before you know how it's calculated”
Head of Sales Development, SaaS · 11-50 employeessimulated See all 3 comments
“That's worth a meeting, but only a technical one where I can ask exactly how "fit" is scored, what happens when the scraped signal is stale or wrong,…” Show full quote
“That's worth a meeting, but only a technical one where I can ask exactly how "fit" is scored, what happens when the scraped signal is stale or wrong, and whether their "2 accounts, first 90 days" sample means anything at our volume”
Founder, B2B Services · 11-50 employeessimulated “the only fuzzy word is "fit score" (94, 88, 91 etc.) — it's presented as precise but never defined, so I can't tell if it's a real model…” Show full quote
“the only fuzzy word is "fit score" (94, 88, 91 etc.) — it's presented as precise but never defined, so I can't tell if it's a real model output or a made-up number dressed up to look rigorous”
Business Development Representative, B2B Services · 51-200 employeessimulated Terminology is muddled by renaming established terms and listing signals without ranking
2 of 15
“the mix of signal types (hiring, competitor, influencer, G2, RSVPs) listed all at once without ranking makes you do a bit of work to see it's one engine,…” Show full quote
“the mix of signal types (hiring, competitor, influencer, G2, RSVPs) listed all at once without ranking makes you do a bit of work to see it's one engine, not five bolted-on features”
Head of Sales Development, SaaS · 11-50 employeessimulated See all 2 comments
“"signal," "queue," "opener," "fit score," "ICP qualified" all get thrown around like established category terms when really they're just their names for scraping + templated first lines”
Sales Manager, Technology · 1-10 employeessimulated The problem and audience land within the first two lines
5 of 15 · what worked
“the headline "Twenty people worth writing to. Every morning." plus the "paste a LinkedIn URL, we show you everyone who engaged" bit tells you in ten seconds this…” Show full quote
“the headline "Twenty people worth writing to. Every morning." plus the "paste a LinkedIn URL, we show you everyone who engaged" bit tells you in ten seconds this is for outbound sales/SDR types”
Sales Manager, Technology · 1-10 employeessimulated See all 4 comments
“It was clear within the first two lines — "Twenty people worth writing to. Every morning" plus "We watch hiring posts, competitor engagement and job changes across your…” Show full quote
“It was clear within the first two lines — "Twenty people worth writing to. Every morning" plus "We watch hiring posts, competitor engagement and job changes across your market" told me exactly what this does before I hit the fold.”
Founder, B2B Services · 201-500 employeessimulated “the "first line you can quote back to them" test is the one bit of specificity that made me stop and actually read rather than skim past as…” Show full quote
“the "first line you can quote back to them" test is the one bit of specificity that made me stop and actually read rather than skim past as fluff”
Founder, B2B Services · 11-50 employeessimulated “It's obvious within the first line: "Twenty people worth writing to. Every morning" plus the subhead about hiring posts, competitor engagement and job changes tells me exactly what…” Show full quote
“It's obvious within the first line: "Twenty people worth writing to. Every morning" plus the subhead about hiring posts, competitor engagement and job changes tells me exactly what problem this solves”
Business Development Representative, B2B Services · 51-200 employeessimulated
Differentiation
Respondents named MCP integration through Claude and Cursor as the differentiator
3 of 15 · what worked
“"Your signals live inside Claude and Cursor through MCP... Nobody else in this category has this" — is the one thing that would actually tip a shortlist decision”
Sales Development Representative, SaaS · 51-200 employeessimulated See all 3 comments
“The MCP integration — "Your signals live inside Claude and Cursor through MCP... Nobody else in this category has this" — is the one concrete differentiator I'd actually…” Show full quote
“The MCP integration — "Your signals live inside Claude and Cursor through MCP... Nobody else in this category has this" — is the one concrete differentiator I'd actually weigh against alternatives”
Business Development Representative, B2B Services · 1-10 employeessimulated “The MCP integration line — "Nobody else in this category has this" letting you query signals from inside Claude or Cursor — is the one thing that would…” Show full quote
“The MCP integration line — "Nobody else in this category has this" letting you query signals from inside Claude or Cursor — is the one thing that would actually differentiate it on a shortlist, if it's real and not "capture pending" vapourware; right now it's an unverified screenshot placeholder”
Senior Sales Development Representative, Technology · 201-500 employeessimulated
Value
The two-account, 90-day sample is treated as the page's central credibility problem
6 of 15
“which is a sample size I wouldn't hang a purchase decision on, and I'd want to see it across more accounts and a longer window”
Sales Development Representative, SaaS · 51-200 employeessimulated See all 7 comments
“But it's "2 accounts, first 90 days" — that's a pilot, not proof, and I'd want to see it against my own list before I believe it transfers.”
Business Development Representative, B2B Services · 1-10 employeessimulated “the only proof offered is "two accounts, first 90 days" against platform averages, which is thin for a claim that big”
Senior Sales Development Representative, Technology · 201-500 employeessimulated “That's worth a meeting, but only a technical one where I can ask exactly how "fit" is scored, what happens when the scraped signal is stale or wrong,…” Show full quote
“That's worth a meeting, but only a technical one where I can ask exactly how "fit" is scored, what happens when the scraped signal is stale or wrong, and whether their "2 accounts, first 90 days" sample means anything at our volume”
Founder, B2B Services · 11-50 employeessimulated “"2 accounts, first 90 days" — that's a sample size a rounding error could produce, and until I see it across more accounts or at our own volume…” Show full quote
“"2 accounts, first 90 days" — that's a sample size a rounding error could produce, and until I see it across more accounts or at our own volume it's not proof, it's a promising anecdote dressed as a metric”
Founder, B2B Services · 11-50 employeessimulated “I'd want to see it live on our own market before I'd trust the "2 accounts, first 90 days" numbers as anything more than a best-case anecdote”
Sales Manager, Technology · 51-200 employeessimulated “2 accounts, first 90 days”
Senior Sales Development Representative, Technology · 11-50 employeessimulated The claimed lift is large enough to justify a workflow change if it survives validation
2 of 15 · what worked
“If the numbers hold — 55% acceptance vs 24% cold, 30% LinkedIn reply vs 6%, 8% email reply vs 2% — that's a real jump over what I'm…” Show full quote
“If the numbers hold — 55% acceptance vs 24% cold, 30% LinkedIn reply vs 6%, 8% email reply vs 2% — that's a real jump over what I'm doing manually right now”
Business Development Representative, B2B Services · 1-10 employeessimulated See all 2 comments
“the acceptance/reply table (55% vs 24% acceptance, 30% vs 6% reply) is the kind of number that, if it held up outside a two-account sample, would actually move…” Show full quote
“the acceptance/reply table (55% vs 24% acceptance, 30% vs 6% reply) is the kind of number that, if it held up outside a two-account sample, would actually move our pipeline math”
Head of Sales Development, SaaS · 11-50 employeessimulated
Relevance
The target reader is inferred from workflow mechanics, never stated
4 of 15
“I'd want a line naming the role directly — "built for BDRs and SDRs running outbound" — plus a mention of team size or quota context, so I'm…” Show full quote
“I'd want a line naming the role directly — "built for BDRs and SDRs running outbound" — plus a mention of team size or quota context, so I'm not inferring it from workflow details”
Business Development Representative, B2B Services · 51-200 employeessimulated See all 2 comments
“The reader is inferred rather than stated outright — it's someone running or managing outbound (SDR, founder, sales lead) at a B2B company”
Founder, B2B Services · 11-50 employeessimulated
Brand alignment
Incomplete screenshots and an unnamed logo wall undercut the founder credibility
2 of 15
“the parts that don't are the ones still marked "capture pending," which undercuts the otherwise credible, practitioner voice”
Sales Development Representative, SaaS · 51-200 employeessimulated See all 2 comments
“the logo wall (Payoneer, Somm, ERA, Clarity Global...) with zero named case studies or quotes behind it — I'd want to hear from one of them directly, e.g.…” Show full quote
“the logo wall (Payoneer, Somm, ERA, Clarity Global...) with zero named case studies or quotes behind it — I'd want to hear from one of them directly, e.g. "Payoneer's SDR team saw X"”
Senior Sales Development Representative, Technology · 201-500 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.
FounderB2B Services · 11-50 employeesEU
Sales Development RepresentativeSaaS · 51-200 employeesUS
Senior Sales Development RepresentativeTechnology · 201-500 employeesEU
Business Development RepresentativeB2B Services · 1-10 employeesUS
Head of Sales DevelopmentSaaS · 11-50 employeesEU
Sales ManagerTechnology · 51-200 employeesUS
FounderB2B Services · 201-500 employeesEU
Sales Development RepresentativeSaaS · 1-10 employeesUS
Senior Sales Development RepresentativeTechnology · 11-50 employeesEU
Business Development RepresentativeB2B Services · 51-200 employeesUS
Head of Sales DevelopmentSaaS · 201-500 employeesEU
Sales ManagerTechnology · 1-10 employeesUS
FounderB2B Services · 11-50 employeesEU
Sales Development RepresentativeSaaS · 51-200 employeesUS
Senior Sales Development RepresentativeTechnology · 201-500 employeesEU
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: 3 of 15, 7 without hesitation, 8 with reservations
- Relevance: 15 of 15, 4 without hesitation, 11 with reservations
- Value: 14 of 15, all with reservations
- Differentiation: 9 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.Define how the fit score is calculated, beside the score.
- 2.Put MCP access through Claude and Cursor above the fold.
- 3.Attach the reply-rate numbers to the accounts that produced them.
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 24 Oct 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.