Clarity
Do they understand what you do?
Strong15 of 15
15 could name what kind of product this is, unprompted.
Saved report, kept for 60 days — expires in 60 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?
Strong13 of 1513 would take a meeting to learn more.
Differentiation
Fix firstIs there a reason to pick you over the alternatives?
Weak8 of 158 could name a reason to pick you over a similar option.
See what they thought you were
Your page describes: agentic meeting platform. They said:
- 3×Agentic meeting assistantmatches
- 3×AI meeting assistant / agentic meeting platformmatches
- 1×Agentic meeting assistant / AI meeting platformmatches
8 couldn't name one; 7 got it right.
Four separate measures, not stages: all 15 personas answered all four questions. Each square is one persona.
Additional signalBrand alignment8 of 15WeakShow finding ▸
Seven respondents said the tone and personas target AI-native startup builders, developers and individual contributors, leaving ops managers, compliance-focused orgs and cross-functional leaders outside the frame. 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.
Add a named customer with a before/after number beneath the "Done before you hang up" section.
Why: Nothing on the page says who already runs Tana on real calls or what changed for them. Name one company, its team size, and a concrete result like hours saved or issues filed per week.
5 of 15 raised this
“What would rule it out, or at least stall it, is that every proof point is generic: no named customer logos, no "Acme Corp cut X hours of…” Show full quote
“What would rule it out, or at least stall it, is that every proof point is generic: no named customer logos, no "Acme Corp cut X hours of admin," just a fictional-sounding "Acme" in the demo screenshots”
Operations Manager, Technology Services · 1001-5000 employeessimulated Moves DifferentiationProof next to the claimAdd a pilot offer line next to the primary download button.
Why: The timeline comparison is illustrative, and buyers want to see Tana run on their own messy calls before believing it. Offer a trial on live calls with a stated setup time.
5 of 15 raised this
“if it can only do clean retrieval on curated examples, it's not worth more than a trial, not a full rollout decision.”
Senior Operations Manager, Engineering · 51-200 employeessimulated Moves ValueAnswer the live objection
Keep these · 3
These landed. Keep the wording when you edit around it.
- Keep · Clarity
The mechanism is understood and repeatable — an agent that acts, not a notetaker
“files the Linear bug, drafts the follow-up email, updates HubSpot, logs decisions with owners, all before the call ends”
Team Lead, Software Development · 51-200 employeessimulated - Keep · Relevance
The hero line and role-segmented blocks land in the first scroll
“For product/sales teams; role list spelled it out.”
Team Lead, Product Management · 11-50 employeessimulated - Keep · Value
Propose-then-accept defuses the unsupervised-agent objection
03
All recommendations
Differentiation
Weak8 of 15- Shown aboveAdd a named customer with a before/after number beneath the "Done before you hang up" section.
Moves DifferentiationGive a reason to choose you
Replace "Tana doesn't take notes" with a line naming what it writes into Linear, Jira and HubSpot.
Why: A buyer comparing Tana to Granola or Fireflies cannot tell from the hero what is different beyond a negation. Say the agent files the issue in Linear and updates the HubSpot deal during the call, not after.
5 of 15 raised this
“What would rule it out, or at least stall it, is that every proof point is generic: no named customer logos, no "Acme Corp cut X hours of…” Show full quote
“What would rule it out, or at least stall it, is that every proof point is generic: no named customer logos, no "Acme Corp cut X hours of admin," just a fictional-sounding "Acme" in the demo screenshots”
Moves DifferentiationProof next to the claim
Add a short proof line under the integrations logo row showing one filed-issue example from a real customer.
Why: The logo wall shows what Tana connects to, not that anyone relies on it. Attach one named team's live workflow to the row so the integrations read as proof rather than ambition.
5 of 15 raised this
“What would rule it out, or at least stall it, is that every proof point is generic: no named customer logos, no "Acme Corp cut X hours of…” Show full quote
“What would rule it out, or at least stall it, is that every proof point is generic: no named customer logos, no "Acme Corp cut X hours of admin," just a fictional-sounding "Acme" in the demo screenshots”
Value
Strong13 of 15Moves ValueProof next to the claim
Source the 30,000 hours stat inline, or cut it.
Why: The number appears with no basis, so readers discount it along with the surrounding claims. Attribute it to customer call data over a stated period, or drop it.
5 of 15 raised this
“if it can only do clean retrieval on curated examples, it's not worth more than a trial, not a full rollout decision.”
Clarity
Strong15 of 15No specific edits needed here — this layer held up.
Relevance
Strong15 of 15No specific edits needed here — this layer held up.
Brand alignment
Weak8 of 15Moves Brand alignmentAnswer the live objection
Add a line under "Aligned without another meeting" on where call data is stored and who can see it.
Why: An agent with write access to Linear and HubSpot raises an immediate security question for anyone in a regulated or larger org. State that capture runs locally, name the retention and access controls, and say an approval step precedes every write.
6 of 15 raised this
“The tone is confident and a bit cheeky ("Meetings that ship," "your IT department won't freak out") which is fun copy, but it's clearly tuned for a scrappier…” Show full quote
“The tone is confident and a bit cheeky ("Meetings that ship," "your IT department won't freak out") which is fun copy, but it's clearly tuned for a scrappier buyer persona than mine”
Moves Brand alignmentName the audience
Rewrite "For AI-native teams that build products, not PowerPoints" to name ops and cross-functional leads.
Why: That line reads as a founder-to-founder joke and shuts out ops managers, program leads and compliance-minded buyers who do the follow-up work. Name the roles who own decisions and owners after a meeting, not just builders.
6 of 15 raised this
“The tone is confident and a bit cheeky ("Meetings that ship," "your IT department won't freak out") which is fun copy, but it's clearly tuned for a scrappier…” Show full quote
“The tone is confident and a bit cheeky ("Meetings that ship," "your IT department won't freak out") which is fun copy, but it's clearly tuned for a scrappier buyer persona than mine”
Moves Brand alignmentConcrete over abstract
Replace the generic role pitch blocks with one concrete meeting outcome per role.
Why: The role sections read as filler next to the detailed Linear bug example. Give each role a specific artifact Tana produces, such as the CRM field an account manager stops updating by hand.
6 of 15 raised this
“The tone is confident and a bit cheeky ("Meetings that ship," "your IT department won't freak out") which is fun copy, but it's clearly tuned for a scrappier…” Show full quote
“The tone is confident and a bit cheeky ("Meetings that ship," "your IT department won't freak out") which is fun copy, but it's clearly tuned for a scrappier buyer persona than mine”
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
Clarity is the page's only real win, and it buys nothing — people understand the product and still refuse to move.
Seven restated the mechanism correctly and five found the hero legible, yet six cited missing logos and retention data as an advancement blocker and five withheld belief pending a pilot. Comprehension is not the bottleneck; proof is.
- high
The page asks for belief it never earns: every quantitative claim on it is unsourced.
Five respondents dismissed the mocked timeline and called out the 30,000 hours stat as unsourced, and six demanded before/after numbers, named customers and retention figures. Nothing on the page survives a request for evidence.
- high
Audience targeting is self-defeating: the page names roles it then writes past.
Five said the role-segmented blocks landed immediately, but seven said the tone speaks founder-to-founder and excludes ops, compliance and cross-functional leaders — and one called the role pitches filler against the technical copy.
- high
Buyers told you exactly what would unblock them and the page supplies none of it.
Respondents specified a named Jira customer, a 200+ person company past month three, and a live pilot on unscripted calls. Six and five respondents respectively named these gaps — the highest-cited themes on the page.
- medium
The strongest objection-handling moment on the page is invisible to almost everyone.
Only one respondent surfaced propose-then-accept as answering the fear of an agent with write access, despite seven correctly describing a product that files into Linear, Jira and HubSpot. The safeguard is buried under the capability.
- low
Undefined jargon undercuts the page's one working asset.
The act-vs-transcribe distinction and named integrations carried comprehension for seven respondents, but 'knowledge graph' was flagged as undefined and structurally unexplained — friction introduced where the page was otherwise clear.
Differentiation
No named customers, logos or retention data — the most-cited blocker
5 of 15
“What would rule it out, or at least stall it, is that every proof point is generic: no named customer logos, no "Acme Corp cut X hours of…” Show full quote
“What would rule it out, or at least stall it, is that every proof point is generic: no named customer logos, no "Acme Corp cut X hours of admin," just a fictional-sounding "Acme" in the demo screenshots”
Operations Manager, Technology Services · 1001-5000 employeessimulated See all 6 comments
“I'd need to see it hold up on a messy 90-minute cross-team call with crosstalk and jargon, and I'd want a named reference customer our size using it…” Show full quote
“I'd need to see it hold up on a messy 90-minute cross-team call with crosstalk and jargon, and I'd want a named reference customer our size using it with Jira specifically — the page lists Linear/Jira/GitHub integrations but every example screenshot is Linear, which makes me wonder how solid the Jira path actually is.”
Director of Operations, Technology Services · 501-1000 employeessimulated “A named 200+ person company on record saying they still use it after three months and that decisions logged in the graph actually got pulled up and acted…” Show full quote
“A named 200+ person company on record saying they still use it after three months and that decisions logged in the graph actually got pulled up and acted on in a later meeting”
Senior Operations Manager, Technology Services · 201-500 employeessimulated “there's no named customer anywhere on this page, no logo, no "Company X runs this across 400 engineers on Jira" — every proof point is a generic mocked-up…” Show full quote
“there's no named customer anywhere on this page, no logo, no "Company X runs this across 400 engineers on Jira" — every proof point is a generic mocked-up screenshot (and it's always Linear, never Jira, in the examples), so on the thing that matters most to me — who else like me already trusts this — the page gives me nothing, and that absence is the single biggest reason I'd hesitate to pick it over a competitor”
Director of Operations, Technology Services · 501-1000 employeessimulated “A named reference customer with a quote about hours saved or decisions not re-litigated — something I can call and verify”
Operations Manager, Engineering · 11-50 employeessimulated “the page gives me zero actual figures, just the mocked timeline graphic — before I take a meeting I'd want one customer reference with hard before/after metrics”
Head of Operations, Product Management · 501-1000 employeessimulated
Value
The claims are only believable after a demo on messy, unscripted calls
5 of 15
“if it can only do clean retrieval on curated examples, it's not worth more than a trial, not a full rollout decision.”
Senior Operations Manager, Engineering · 51-200 employeessimulated See all 5 comments
“Watch it sit through one of our actual messy, interrupt-heavy engineering calls and file a Linear issue I'd hand to a dev with zero edits — if it…” Show full quote
“Watch it sit through one of our actual messy, interrupt-heavy engineering calls and file a Linear issue I'd hand to a dev with zero edits — if it does that without me cleaning it up, I'm sold”
Head of Operations, Software Development · 201-500 employeessimulated “"done before you hang up" needs a live demo proof, not copy.”
Team Lead, Product Management · 11-50 employeessimulated “"30,000 hours in meetings" is a throwaway stat with no source, and "done before you hang up" is a demo claim until I see it on a messy…” Show full quote
“"30,000 hours in meetings" is a throwaway stat with no source, and "done before you hang up" is a demo claim until I see it on a messy 45-minute call with crosstalk and three different trackers in play.”
Operations Lead, Product Management · 1001-5000 employeessimulated “One real, verifiable case where a HubSpot deal field updates correctly straight off a call transcript, with no manual cleanup after — that single mechanism working as claimed…” Show full quote
“One real, verifiable case where a HubSpot deal field updates correctly straight off a call transcript, with no manual cleanup after — that single mechanism working as claimed is what turns this from marketing copy into something I'd actually pilot”
Team Lead, Software Development · 51-200 employeessimulated Propose-then-accept defuses the unsupervised-agent objection
1 of 15 · what worked
Clarity
"Knowledge graph" is used without definition and creates friction
1 of 15
“'knowledge graph' itself is the term that makes me pause, since it's used as if it's self-evidently a thing (nodes, entities, provenance?) without ever being defined structurally.”
Senior Operations Manager, Engineering · 51-200 employeessimulated The mechanism is understood and repeatable — an agent that acts, not a notetaker
6 of 15 · what worked
“files the Linear bug, drafts the follow-up email, updates HubSpot, logs decisions with owners, all before the call ends”
Team Lead, Software Development · 51-200 employeessimulated See all 6 comments
“every call feeds one shared "knowledge graph," so you can later ask "what did we decide about SSO" and get an answer with provenance”
Senior Operations Manager, Engineering · 51-200 employeessimulated “It's an AI meeting assistant that sits in your video calls, listens, and then actually executes tasks off the back of them — files bugs into Linear, drafts…” Show full quote
“It's an AI meeting assistant that sits in your video calls, listens, and then actually executes tasks off the back of them — files bugs into Linear, drafts follow-up emails, updates the CRM, logs decisions with owners — instead of just spitting out a summary afterward like a notetaker would.”
Head of Operations, Software Development · 201-500 employeessimulated “It's an AI meeting assistant that sits in on your Zoom/Teams/Meet calls, captures what's said, and actually does the follow-up work in real time — filing a Linear…” Show full quote
“It's an AI meeting assistant that sits in on your Zoom/Teams/Meet calls, captures what's said, and actually does the follow-up work in real time — filing a Linear ticket, drafting the recap email, updating HubSpot, logging who owns what — instead of just handing you a transcript afterward.”
Director of Operations, Technology Services · 501-1000 employeessimulated “It's an AI meeting assistant that sits in on Zoom/Teams/Meet calls, captures what's said, and then auto-files the resulting work into tools we already use — opens a…” Show full quote
“It's an AI meeting assistant that sits in on Zoom/Teams/Meet calls, captures what's said, and then auto-files the resulting work into tools we already use — opens a Linear/Jira ticket, updates HubSpot, drafts the follow-up email, logs decisions with owners.”
Operations Lead, Product Management · 1001-5000 employeessimulated “the page was unusually concrete about mechanism (Linear, Gmail, HubSpot named directly)”
Operations Manager, Engineering · 11-50 employeessimulated
Relevance
The hero line and role-segmented blocks land in the first scroll
5 of 15 · what worked
“For product/sales teams; role list spelled it out.”
Team Lead, Product Management · 11-50 employeessimulated See all 3 comments
“the hero line "Tana doesn't take notes. It captures your calls, files the issue, drafts the email and updates the CRM before you hang up, and remembers what…” Show full quote
“the hero line "Tana doesn't take notes. It captures your calls, files the issue, drafts the email and updates the CRM before you hang up, and remembers what everyone promised" tells you the problem (meetings produce work and context that gets lost/retyped) in the first few seconds.”
Senior Operations Manager, Engineering · 51-200 employeessimulated “there's a literal row of segments (Product and tech, Consultants, VCs, Founders, Customer success, Sales) each with its own pitch, so I didn't have to hunt”
Head of Operations, Software Development · 201-500 employeessimulated
Brand alignment
The page reads as founder-to-founder and excludes ops and manager roles
6 of 15
“The tone is confident and a bit cheeky ("Meetings that ship," "your IT department won't freak out") which is fun copy, but it's clearly tuned for a scrappier…” Show full quote
“The tone is confident and a bit cheeky ("Meetings that ship," "your IT department won't freak out") which is fun copy, but it's clearly tuned for a scrappier buyer persona than mine”
Operations Manager, Technology Services · 1001-5000 employeessimulated See all 7 comments
“there's no "ops," "internal comms," or "cross-functional" persona bucket, so I'd read this as a tool built by a dev-tool-adjacent team for similar teams”
Senior Operations Manager, Engineering · 51-200 employeessimulated “my role (ops manager tracking institutional memory across meetings) isn't one of the named buckets”
Senior Operations Manager, Engineering · 51-200 employeessimulated “"For AI-native teams that build products, not PowerPoints" is a jab at traditional corporates, which tells me they're chasing startups and scale-ups, not a 501-1000 person ops org…” Show full quote
“"For AI-native teams that build products, not PowerPoints" is a jab at traditional corporates, which tells me they're chasing startups and scale-ups, not a 501-1000 person ops org like mine”
Head of Operations, Product Management · 501-1000 employeessimulated “The tone is sharp and confident — "Tana doesn't take notes" as an opener is a good hook — but it's written for someone building product or closing…” Show full quote
“The tone is sharp and confident — "Tana doesn't take notes" as an opener is a good hook — but it's written for someone building product or closing deals, not running ops; there's no "Director of Ops" or cross-functional admin persona card, so I'm reading it as an adjacent buyer rather than the intended one”
Director of Operations, Engineering · 1001-5000 employeessimulated “Tone's for builders, not directors like me.”
Team Lead, Product Management · 11-50 employeessimulated “the tone leans more "founder pitching founders" than "vendor pitching an ops manager," it's confident and a bit breathless”
Operations Manager, Technology Services · 51-200 employeessimulated The role-based pitch sections read as filler against the technical copy
1 of 15
“the role-based mini-pitches ("Run more deals without losing the thread") feel more like generic SaaS marketing copy than something aimed at a skeptical ops manager”
Operations Manager, Engineering · 11-50 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.
Operations ManagerTechnology Services · 1001-5000 employeesUS
Team LeadProduct Management · 11-50 employeesEU
Senior Operations ManagerEngineering · 51-200 employeesUS
Head of OperationsSoftware Development · 201-500 employeesEU
Director of OperationsTechnology Services · 501-1000 employeesUS
Operations LeadProduct Management · 1001-5000 employeesEU
Operations ManagerEngineering · 11-50 employeesUS
Team LeadSoftware Development · 51-200 employeesEU
Senior Operations ManagerTechnology Services · 201-500 employeesUS
Head of OperationsProduct Management · 501-1000 employeesEU
Director of OperationsEngineering · 1001-5000 employeesUS
Operations LeadSoftware Development · 11-50 employeesEU
Operations ManagerTechnology Services · 51-200 employeesUS
Team LeadProduct Management · 201-500 employeesEU
Senior Operations ManagerEngineering · 501-1000 employeesUS
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: 15 of 15, 5 without hesitation, 10 with reservations
- Relevance: 15 of 15, 11 without hesitation, 4 with reservations
- Value: 13 of 15, all with reservations
- Differentiation: 8 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.Add a named customer with a before/after number beneath the "Done before you hang up" section.
- 2.Add a pilot offer line next to the primary download button.
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 4 Dec 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.