# Message test — https://www.zealid.com/trust-circle After reading your page, only 10 of 15 personas would take a meeting to learn more. - **Page tested:** https://www.zealid.com/trust-circle - **Audience tested against:** SME with 2-100 people law firms dealing with ongoing reguliations to store data - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/identity-first-client-workspace-secure-documen-3eTH1vo > These answers are generated by AI, scored on Wynter's B2B Message > Layers framework using behaviorally-diverse simulated personas. The > methodology is real and the critique is directional. What a simulated > persona cannot have is a live budget, a renewal coming up, or a boss > asking about this quarter. --- ## 01 · The scores Every persona answered all four questions. These are four independent proportions of the same panel, not stages of a funnel. | Layer | Question | Cleared the bar | Strength | Of those who passed | | --- | --- | --- | --- | --- | | 1. Clarity | Do they understand what you do? | 15/15 | 90% | 8 without hesitation, 7 with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 15/15 | 99% | 14 without hesitation, 1 with reservations | | 3. Value | Do they actually want it? | 10/15 | 58% | all with reservations | | 4. Differentiation | Is there a reason to pick you over the alternatives? | 10/15 | 58% | all with reservations | **Brand alignment** (a side metric, not one of the four layers) — 9/15, 56% strength (all with reservations). Does the page read like the company you actually are? **Fix first: Value.** Earliest failing layer, walking the sequence in order — not simply the lowest score. --- ## 02 · What to change, layer by layer Ordered worst-first. Specific edits, not a restatement of the score. ### Value **Add cost and time figures next to the SharePoint comparison.** "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. *effort medium · impact high · tested against Specifics beat superlatives* **State migration effort and timeline for firms leaving SharePoint.** 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. *effort medium · impact high · tested against Answer the live objection* **Address the client-side app install objection where signing is described.** 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. *effort low · impact medium · tested against Answer the live objection* ### Differentiation **Replace template testimonials with named firms and firm size.** The current testimonials read as placeholder copy and carry no proof. Name mid-size law and accounting practices, with headcount and what they replaced. *effort high · impact high · tested against Proof next to the claim* **Explain how automated identity verification actually works.** "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. *effort medium · impact high · tested against Proof next to the claim* **State firm size range, including how deal teams above nine work.** 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. *effort low · impact medium · tested against Answer the live objection* ### Clarity **Define what Trust Circle is in the first four words.** "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. *effort low · impact medium · tested against Plain language* ### Brand alignment (side metric) **State jurisdiction coverage in the hero, not just EU.** "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. *effort low · impact high · tested against Name the audience* **Delete the CMS placeholder line about custom background.** "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. *effort low · impact high* **Define AMLR, eIDAS and QES on first use.** 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. *effort low · impact medium · tested against Plain language* --- ## 03 · What is working ### The bundle — identity verification, document sharing, qualified e-signatures in one… Nine respondents restated the product as a single compliant workspace combining identity verification, document sharing and QES, and several named that consolidation of SharePoint plus separate e-signing as the value. > we'd drop the ID-photo-by-email chasing and consolidate our SharePoint-plus-signing-tool setup into one auditable place > > — Senior Partner, Accounting, 1-10 > 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 > > — Practice Manager, Legal Services, 51-200 > It's a secure client workspace for law firms and accountants that bundles identity verification, document sharing, and qualified electronic signatures into one place > > — Office Manager, Legal Services, 51-200 > a secure client workspace that combines identity verification, document sharing, and legally-binding e-signatures for professional services firms > > — Managing Partner, Accounting, 1-10 > It's a client workspace that bundles identity verification, document sharing, and qualified e-signatures for regulated professional services firms > > — Practice Manager, Accounting, 1-10 ### The AMLR deadline and eIDAS specifics made the page concrete Respondents pointed to the explicit regulatory deadline and technical specification as what created clarity and urgency. One noted the deadline justifies urgency even while migration effort still needs validation. > The AMLR deadline (July 2027) and the eIDAS/QES angle are the actual hooks that made me pay attention > > — Managing Partner, Financial Advisory, 11-50 > 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 > > — Managing Partner, Financial Advisory, 11-50 --- ## 04 · What the personas said ### 'Trust Circle' is read as ambiguous — vendor, feature, or workspace unit Three respondents said the product name conflates the system with the workspace unit and could not tell what it refers to, requiring clarification before reading further. > 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 > > — Senior Partner, Legal Services, 51-200 > "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." > > — Managing Partner, Legal Services, 51-200 ### Stacked compliance jargon and a leftover CMS artifact read as an unfinished page Respondents flagged CMS artifacts in the copy as a sign of incomplete production and a smaller, less polished operation, and said unexplained compliance terminology slowed comprehension. Testimonials were called generic template copy. > the only friction was the CMS junk like "Insert custom BG here" sitting mid-copy, which made me do a double-take > > — Managing Partner, Financial Advisory, 11-50 > leftover CMS notes like "Insert custom BG here" still in the copy — which makes me wonder if this is a smaller, less polished operation > > — Managing Partner, Financial Advisory, 11-50 > 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 > > — Managing Partner, Legal Services, 51-200 ### No numbers on cost, time saved, or migration effort against the current SharePoint and… Respondents said the page omits cost and time-savings comparisons, SharePoint migration cost, and firm size guidance. A mandatory client app install was read as friction against a setup that already works. > 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 > > — Managing Partner, Financial Advisory, 11-50 > "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 > > — Practice Manager, Legal Services, 51-200 > 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 > > — Office Manager, Accounting, 1-10 ### The page never explains how the automated verifications work The AMLR deadline is invoked without mechanism detail, and one respondent questioned whether the nine-member cap fits large deal teams. > 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 > > — Practice Manager, Legal Services, 51-200 > "Up to 9 members per Trust Circle" sounds arbitrary and possibly too small for an M&A deal team > > — Managing Partner, Financial Advisory, 11-50 ### Named customers are the missing proof, specifically US and mid-size firm references Three respondents said they need named customer logos or case studies — mid-size law firms, US domestic references — before treating the claims as credible. > 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" > > — Compliance Officer, Financial Advisory, 11-50 > 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 > > — Senior Partner, Legal Services, 51-200 ### The EU-only compliance framing puts US firms outside the pitch 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. > 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 > > — Compliance Officer, Financial Advisory, 11-50 > 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. > > — Practice Manager, Financial Advisory, 11-50 > they're selling to EU firms and just repackaged the same pitch for a US audience without adjusting the compliance story > > — Office Manager, Financial Advisory, 11-50 > 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 > > — Compliance Officer, Legal Services, 51-200 --- ## 05 · The hardest read An adversarial pass over the findings. Every claim below was checked against the panel's own answers; unsupported ones were dropped. - **The page sells a category, not this product — comprehension is the only thing working.** *(high)* 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.** *(high)* 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.** *(high)* 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.** *(high)* 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.** *(medium)* 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.** *(medium)* 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. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | Senior Partner | Accounting | 1-10 | | 2 | Compliance Officer | Financial Advisory | 11-50 | | 3 | Practice Manager | Legal Services | 51-200 | | 4 | Office Manager | Accounting | 1-10 | | 5 | Managing Partner | Financial Advisory | 11-50 | | 6 | Senior Partner | Legal Services | 51-200 | | 7 | Compliance Officer | Accounting | 1-10 | | 8 | Practice Manager | Financial Advisory | 11-50 | | 9 | Office Manager | Legal Services | 51-200 | | 10 | Managing Partner | Accounting | 1-10 | | 11 | Senior Partner | Financial Advisory | 11-50 | | 12 | Compliance Officer | Legal Services | 51-200 | | 13 | Practice Manager | Accounting | 1-10 | | 14 | Office Manager | Financial Advisory | 11-50 | | 15 | Managing Partner | Legal Services | 51-200 | --- ## 07 · Before you act on this The methodology is real, and the critique is directional. What a simulated persona cannot have is a live budget, a renewal coming up, or a boss asking about this quarter. **Validate anything you're betting on with real ICPs who are actually in-market.** Being wrong is more expensive than you think. Finding out is cheaper than you'd guess. Wynter runs message testing with verified B2B professionals — trusted by HubSpot, RingCentral, Shopify, Cognism, Paddle, Veeam, Rippling and Miro. This report is kept for 60 days from 2026-08-26, then deleted along with the personas and their answers.