Clarity
Do they understand what you do?
15 could name what kind of product this is, unprompted.
https://www.zealid.com/trust-circle15 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?
10 would take a meeting to learn more.
Is there a reason to pick you over the alternatives?
10 could name a reason to pick you over a similar option.
Four separate measures, not stages: all 15 personas answered all four questions. Each square is one persona.
Six respondents said the page positions as EU-native without acknowledging US applicability, making the compliance argument irrelevant to US advisory and small firms and leaving jurisdiction unconfirmed. 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 cost of disconnected workflows" names friction and risk but never quantifies either. State admin hours saved per matter and price against SharePoint plus a separate e-signing tool.
3 of 15 raised this
“I'd want a line naming firm size or team structure — something like "built for 10-50 person advisory teams" — plus a concrete migration path from SharePoint”
Why: The current testimonials read as placeholder copy and carry no proof. Name mid-size law and accounting practices, with headcount and what they replaced.
2 of 15 raised this
“the AMLR deadline mention ("takes effect July 10, 2027") without any specifics on how their "ongoing, automated verifications" actually work compared to a rival's would rule them out if a competitor spelled out the mechanics”
Why: "Trust Circle is a regulated EU identity layer with a client portal..." reads as vendor, feature and workspace at once. Open the sentence with the plain noun — a client workspace that combines identity verification, document sharing and qualified e-signing.
3 of 15 raised this
“the only friction was the CMS junk like "Insert custom BG here" sitting mid-copy, which made me do a double-take”
These landed. Keep the wording when you edit around it.
The bundle — identity verification, document sharing, qualified e-signatures in one…
“we'd drop the ID-photo-by-email chasing and consolidate our SharePoint-plus-signing-tool setup into one auditable place”
The AMLR deadline and eIDAS specifics made the page concrete
“The AMLR deadline (July 2027) and the eIDAS/QES angle are the actual hooks that made me pay attention”
Why: Readers weighing a switch from a setup that already works get no answer on what migration costs them. Add a line on setup time, data import and what stays in SharePoint.
3 of 15 raised this
“I'd want a line naming firm size or team structure — something like "built for 10-50 person advisory teams" — plus a concrete migration path from SharePoint”
Why: A mandatory client app install reads as friction added to onboarding, which undercuts the drop-off argument in "Integrated Identity and Signing". Say what the client actually installs, why, and how long it takes.
3 of 15 raised this
“I'd want a line naming firm size or team structure — something like "built for 10-50 person advisory teams" — plus a concrete migration path from SharePoint”
Why: "Two-minute biometric verification" and "Instantly verify" assert an outcome with no mechanism. Describe the NFC passport read, the liveness check and what ZealiD checks against, so the claim is inspectable.
2 of 15 raised this
“the AMLR deadline mention ("takes effect July 10, 2027") without any specifics on how their "ongoing, automated verifications" actually work compared to a rival's would rule them out if a competitor spelled out the mechanics”
Why: The nine-member cap raises an immediate fit question for larger deal teams and no line on the page answers it. Say which firm sizes the workspace serves and how seats scale.
2 of 15 raised this
“the AMLR deadline mention ("takes effect July 10, 2027") without any specifics on how their "ongoing, automated verifications" actually work compared to a rival's would rule them out if a competitor spelled out the mechanics”
No specific edits needed here — this layer held up.
Why: "regulated EU identity layer" tells US and non-EU firms the pitch is not for them. Say plainly which jurisdictions the service covers and whether firms outside the EU can use it.
5 of 15 raised this
“this is EU-built (Sweden data hosting, eIDAS QES, EU AMLR deadlines) and I'm a US financial advisory firm — none of that regulatory scaffolding applies to me”
Why: "Insert custom BG here - this text will only appear on page editor" is shipped on the live page and signals an unfinished, small operation. Remove it and audit for other artifacts.
5 of 15 raised this
“this is EU-built (Sweden data hosting, eIDAS QES, EU AMLR deadlines) and I'm a US financial advisory firm — none of that regulatory scaffolding applies to me”
Why: Stacked acronyms force a first-time reader to decode before they can judge fit. Add a half-sentence gloss beside each, tied to the obligation it creates for the firm.
5 of 15 raised this
“this is EU-built (Sweden data hosting, eIDAS QES, EU AMLR deadlines) and I'm a US financial advisory firm — none of that regulatory scaffolding applies to me”
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 sells a category, not this product — comprehension is the only thing working.
Nine respondents restated the bundle correctly (theme 6), yet two said the mechanism behind the automated verifications is never explained (theme 3) and the product name itself was unresolvable for others (theme 0). Understood but interchangeable.
The strongest concrete hook on the page is also the one that disqualifies a third of the audience.
The AMLR deadline and eIDAS detail are cited as what made the page concrete, but six respondents read the same EU-only framing as evidence the pitch excludes US firms and left jurisdiction unconfirmed.
Nothing on the page survives a procurement conversation.
Three respondents found no cost, time-savings, migration-cost or firm-size numbers against the incumbent SharePoint setup, and three more demanded named mid-size and US references before crediting any claim. Both the business case and the proof are absent.
Production defects are doing brand damage, not just slowing reading.
Three respondents read a leftover CMS artifact as a signal of a smaller, less polished operation and called the testimonials template copy — the page is actively arguing the vendor is not credible.
The page asks buyers to absorb cost and friction it never justifies.
A mandatory client app install was read as friction against a setup that already works, and the nine-member cap was questioned as too small for large deal teams — constraints stated without compensating value.
Comprehension of the bundle is being mistaken for belief in it.
The one positive on differentiation is absent: every differentiation theme is negative, covering unexplained mechanism and missing named customers, while the positives are confined to restating what the product is.
No numbers on cost, time saved, or migration effort against the current SharePoint and…
3 of 15
“I'd want a line naming firm size or team structure — something like "built for 10-50 person advisory teams" — plus a concrete migration path from SharePoint”
“"worth a meeting" depends on numbers they didn't give me — how much time/cost this actually saves versus our current SharePoint+DocuSign setup, and what migrating client data and re-training clients on yet another app (they need the ZealiD app too) really costs us”
“this wants every client to download the ZealiD app and biometrically verify before they can even open a document - that's friction I'd be pushing onto clients”
The page never explains how the automated verifications work
2 of 15
“the AMLR deadline mention ("takes effect July 10, 2027") without any specifics on how their "ongoing, automated verifications" actually work compared to a rival's would rule them out if a competitor spelled out the mechanics”
“"Up to 9 members per Trust Circle" sounds arbitrary and possibly too small for an M&A deal team”
Named customers are the missing proof, specifically US and mid-size firm references
2 of 15
“There's also zero named customers, just two anonymous quotes about SHA chasing and QES friction, no logos, no "used by X law firms in the US"”
“A named mid-size US or EU law firm — ideally litigation or corporate, my size, 50-200 lawyers — saying they moved off SharePoint-plus-DocuSign and cut their document-chasing time, with a person's name and title attached”
'Trust Circle' is read as ambiguous — vendor, feature, or workspace unit
2 of 15
“the name itself, "Trust Circle," which sounds like it could be a vendor, a feature, or the whole product, and the page uses it as all three”
“"Trust Circle" is used both as the whole product name and as the per-client workspace unit, so I initially couldn't tell if I was buying one system or provisioning many discrete "Circles."”
Stacked compliance jargon and a leftover CMS artifact read as an unfinished page
3 of 15
“the only friction was the CMS junk like "Insert custom BG here" sitting mid-copy, which made me do a double-take”
“leftover CMS notes like "Insert custom BG here" still in the copy — which makes me wonder if this is a smaller, less polished operation”
“jargon-stacking — QES, AMLR, eIDAS, CDD, KYC all dropped without a beat — meant I had to slow down and mentally sort what's a feature versus what's a compliance term”
The bundle — identity verification, document sharing, qualified e-signatures in one…
5 of 15 · what worked
“we'd drop the ID-photo-by-email chasing and consolidate our SharePoint-plus-signing-tool setup into one auditable place”
“If it actually did what it says, I'd stop being the person chasing "where's the latest SHA" and stop emailing clients asking them to photograph passports — that's a real, specific pain”
“It's a secure client workspace for law firms and accountants that bundles identity verification, document sharing, and qualified electronic signatures into one place”
“a secure client workspace that combines identity verification, document sharing, and legally-binding e-signatures for professional services firms”
“It's a client workspace that bundles identity verification, document sharing, and qualified e-signatures for regulated professional services firms”
The AMLR deadline and eIDAS specifics made the page concrete
1 of 15 · what worked
“The AMLR deadline (July 2027) and the eIDAS/QES angle are the actual hooks that made me pay attention”
“The AMLR July 2027 deadline is the one line that makes this "now" rather than "someday," so yes, book the demo, but I'm going in skeptical”
The EU-only compliance framing puts US firms outside the pitch
5 of 15
“this is EU-built (Sweden data hosting, eIDAS QES, EU AMLR deadlines) and I'm a US financial advisory firm — none of that regulatory scaffolding applies to me”
“The tone is competent and specific in places ("Article 25(2) of eIDAS," "audited annually") which tells me they know their home market cold, but there's zero acknowledgment that a US firm might be reading this - no ESIGN/UETA mention, no US case studies, nothing.”
“they're selling to EU firms and just repackaged the same pitch for a US audience without adjusting the compliance story”
“I'd need to see my jurisdiction and our actual matter types named — US-based legal services, litigation or transactional work, not just EU AMLR and eIDAS references — plus a line confirming QES holds up for a US firm dealing with EU counterparties”
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.







