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?
Strong14 of 1514 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?
Mixed10 of 1510 could name a reason to pick you over a similar option.
See what they thought you were
Your page describes: AI automation. They said:
- 3×AI agent / workflow automationmatches
- 3×AI agent / workplace automation assistantmatches
- 2×AI agent / AI teammate for business operationsmatches
- 1×AI agent / cross-tool workflow automationmatches
- 1×AI workflow automation / agent assistantmatches
- 1×AI workflow automation / AI agent assistantmatches
- 1×AI workflow/ops agentmatches
- 1×AI workflow/ops automation agentmatches
2 couldn't name one; 13 got it right.
Four separate measures, not stages: all 15 personas answered all four questions. Each square is one persona.
Additional signalBrand alignment11 of 15MixedShow finding ▸
Replace "People use Lindy at some pretty cool places" with a named customer outcome. 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 section after the Stripe reconciliation example covering audit log, rollback and permissions.
Why: A finance lead reading the Stripe close example has no way to know whether actions are logged, reversible, or scoped by role. Add a short block naming the audit trail, undo path, and who can grant tool access.
3 of 15 raised this
“there's nothing on the page about rollback, audit trail, or who eats the cost of a bad auto-action, which after getting burned once is exactly what I'd dig…” Show full quote
“there's nothing on the page about rollback, audit trail, or who eats the cost of a bad auto-action, which after getting burned once is exactly what I'd dig into before a competitor”
Co-Founder, Software · 1-10 employeessimulated Moves DifferentiationAnswer the live objectionAdd time or cost saved per week beside each Slack scenario.
Why: The scenarios show speed in seconds but not what that is worth. Attach the recurring saving, such as hours of incident triage or close time removed per month, to each example.
5 of 15 raised this
“Before I take a meeting I'd want to know how it handles messy, non-standard ledgers and who's liable when it mis-reconciles something in a real audit, not a…” Show full quote
“Before I take a meeting I'd want to know how it handles messy, non-standard ledgers and who's liable when it mis-reconciles something in a real audit, not a demo.”
Senior Operations Manager, Startups · 51-200 employeessimulated Moves ValueTie the feature to the outcomeAdd a line under the subhead naming the roles and company size Lindy is built for.
Why: Nothing on the page says who should buy, so readers reconstruct it from logos and Slack handles. Name the teams, growth, support, engineering, finance, and the company stage you serve.
4 of 15 raised this
“I didn't have to hunt for it, but the "who exactly" (my size company? my industry?) is pieced together from the example cast and the logo wall (Shopify,…” Show full quote
“I didn't have to hunt for it, but the "who exactly" (my size company? my industry?) is pieced together from the example cast and the logo wall (Shopify, Apple, Airbnb) rather than stated as "built for 200-person SaaS companies" or similar.”
Founder, Technology · 201-500 employeessimulated Moves RelevanceName the audience
Keep these · 3
These landed. Keep the wording when you edit around it.
- Keep · Clarity
The core category — an agent that executes multi-step work across tools, not a chatbot…
“It's an AI agent that plugs into your existing tools—Slack, Gmail, Zendesk, HubSpot, PostHog, GitHub—and actually does multi-step work: pulling data, diffing code, drafting replies, filing tickets, reconciling…” Show full quote
“It's an AI agent that plugs into your existing tools—Slack, Gmail, Zendesk, HubSpot, PostHog, GitHub—and actually does multi-step work: pulling data, diffing code, drafting replies, filing tickets, reconciling spreadsheets, then reporting back in thread.”
Operations Manager, SaaS · 11-50 employeessimulated - Keep · Relevance
The Slack scenario mockups communicate the use case better than the headline does
“the Slack-thread mockups right up top do the work. "ad spend doubled," "support inbox is blowing up," "signups are throwing 500s," "reconcile Stripe vs. the gsheet ledger" —…” Show full quote
“the Slack-thread mockups right up top do the work. "ad spend doubled," "support inbox is blowing up," "signups are throwing 500s," "reconcile Stripe vs. the gsheet ledger" — those are concrete ops/eng/finance pain points, and I didn't have to dig for them”
Senior Operations Manager, Startups · 51-200 employeessimulated - Keep · Value
Specific named scenarios map onto problems respondents have right now
“it directly touches the ad spend monitoring problem I already have with Google Ads. That's worth a meeting.”
Founder, Technology · 201-500 employeessimulated
03
All recommendations
Differentiation
Mixed10 of 15- Shown aboveAdd a section after the Stripe reconciliation example covering audit log, rollback and permissions.
Moves DifferentiationAnswer the live objection
Add an approval line under each Slack scenario stating that write actions wait for your click.
Why: Buyers can't tell whether 'Pause the campaign' or 'Merge the revert' executes on its own or waits for a human. State that every write action requires explicit approval, and say what happens if nobody clicks.
3 of 15 raised this
“there's nothing on the page about rollback, audit trail, or who eats the cost of a bad auto-action, which after getting burned once is exactly what I'd dig…” Show full quote
“there's nothing on the page about rollback, audit trail, or who eats the cost of a bad auto-action, which after getting burned once is exactly what I'd dig into before a competitor”
Moves DifferentiationGive a reason to choose you
Replace "Connected to everything" with a line naming depth of a specific integration.
Why: "Gmail, Slack, Notion, HubSpot, and 1,000+ more" reads like a thin API wrapper any competitor could claim. Name what Lindy can actually read and write in one or two named tools instead of counting logos.
3 of 15 raised this
“there's nothing on the page about rollback, audit trail, or who eats the cost of a bad auto-action, which after getting burned once is exactly what I'd dig…” Show full quote
“there's nothing on the page about rollback, audit trail, or who eats the cost of a bad auto-action, which after getting burned once is exactly what I'd dig into before a competitor”
Value
Strong13 of 15Relevance
Strong14 of 15Clarity
Strong15 of 15Moves ClarityLead with the use case
Add a plain category sentence under the H1 saying what Lindy is.
Why: "Not an AI tool. A coworker" makes readers infer the category from screenshots. Say in words that Lindy is an AI agent that executes multi-step work across your connected tools, not a chatbot.
2 of 15 raised this
“Words like "done in 21s" and "−64% blended CAC if paused" are precise-looking but have no source attached”
Brand alignment
Mixed11 of 15Moves Brand alignmentProof next to the claim
Replace "People use Lindy at some pretty cool places" with a named customer outcome.
Why: A wall of Shopify, Apple and NVIDIA logos with a jokey caption proves nothing about results. Put one named customer, the job Lindy runs for them, and a number beside the logos.
Moves Brand alignmentProof next to the claim
Label the Slack scenarios as product examples and link to a live demo on real data.
Why: The chat screenshots read as staged mockups, so the 21-second and 1,340-ticket figures get discounted. Mark them as examples and offer a recorded or live run against a real account.
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 copy is dead weight; the screenshots are doing the entire job of positioning.
Five respondents said the Slack scenario mockups and logos conveyed relevance faster than the explicit copy, six reconstructed the buyer from screenshots rather than stated positioning, and one had to infer the category from examples. Delete the images and…
- high
The page's only persuasive asset is also its least credible one, so comprehension and belief cancel out.
Five respondents discounted the same demos as mockups with no real data, while five others relied on those scenarios to understand relevance and four tied them to live problems. The asset carrying the message is the asset being dismissed.
- high
Nothing on the page survives a procurement review.
Three respondents flagged missing rollback, audit trail, and liability framing as contract risk and could not tell whether write actions require approval, and two said reliability claims lack sourced data. An agent with production write access and no stated…
- high
Clear comprehension of the category is being mistaken for a working message — respondents understood the product and still would not believe it.
Six respondents read back the agent category accurately, the page's strongest result, yet five discounted the evidence as staged and said competitors with real case studies would win. Understanding without belief loses the deal.
- high
The single asked-for proof — performance on the buyer's own messy data — is exactly what the page refuses to show.
Five respondents wanted a live demo on their own data or live-account CAC evidence, and two said reliability claims lack sourced real-world data. The page answers a demand for real data with staged data.
- medium
Every named integration is a liability rather than a proof point because depth is never substantiated.
Two respondents said PostHog integration could be a thin API wrapper, and three called out Stripe reconciliation audit liability specifically. Logos invite scrutiny the page cannot withstand.
Differentiation
Missing rollback, approval, and audit framing reads as unacceptable risk
3 of 15
“there's nothing on the page about rollback, audit trail, or who eats the cost of a bad auto-action, which after getting burned once is exactly what I'd dig…” Show full quote
“there's nothing on the page about rollback, audit trail, or who eats the cost of a bad auto-action, which after getting burned once is exactly what I'd dig into before a competitor”
Co-Founder, Software · 1-10 employeessimulated See all 3 comments
“It's the action verbs with no mechanism attached — "pause the campaign," "merge the threads," "refund it" are all presented as one-click buttons, but nothing says whether those…” Show full quote
“It's the action verbs with no mechanism attached — "pause the campaign," "merge the threads," "refund it" are all presented as one-click buttons, but nothing says whether those write actions go through an approval step, a sandbox, or straight to production.”
Director of Operations, SaaS · 11-50 employeessimulated “Before I take a meeting I'd want to know how it handles messy, non-standard ledgers and who's liable when it mis-reconciles something in a real audit, not a…” Show full quote
“Before I take a meeting I'd want to know how it handles messy, non-standard ledgers and who's liable when it mis-reconciles something in a real audit, not a demo.”
Senior Operations Manager, Startups · 51-200 employeessimulated
Value
Staged screenshots are the single biggest barrier to believing the value
5 of 15
“Before I take a meeting I'd want to know how it handles messy, non-standard ledgers and who's liable when it mis-reconciles something in a real audit, not a…” Show full quote
“Before I take a meeting I'd want to know how it handles messy, non-standard ledgers and who's liable when it mis-reconciles something in a real audit, not a demo.”
Senior Operations Manager, Startups · 51-200 employeessimulated See all 6 comments
“every example is a staged screenshot with suspiciously clean round numbers and no named customer attached to the finance use case specifically — the testimonials at the bottom…” Show full quote
“every example is a staged screenshot with suspiciously clean round numbers and no named customer attached to the finance use case specifically — the testimonials at the bottom are about meetings, email, and general "second brain" stuff”
Senior Operations Manager, Startups · 51-200 employeessimulated “I'd want to know how it handles our actual PostHog schema and our messier, less-clean data, not a demo environment”
Director of Operations, Technology · 201-500 employeessimulated “every example is their mockup data — Meta, Google, PostHog all look clean and pre-wired, and I have no idea what setup/integration pain looks like with our messier…” Show full quote
“every example is their mockup data — Meta, Google, PostHog all look clean and pre-wired, and I have no idea what setup/integration pain looks like with our messier accounts”
VP of Operations, Software · 1-10 employeessimulated “I'd want them to run it live against our own Zendesk/Intercom data during the meeting, not a canned screenshot, and I'd want to know what happens when the…” Show full quote
“I'd want them to run it live against our own Zendesk/Intercom data during the meeting, not a canned screenshot, and I'd want to know what happens when the clustering is wrong”
Founder, SaaS · 11-50 employeessimulated “the incident-response examples (the PR #4821 revert, the CSV export timeout) are all clean, single-cause scenarios with a one-line fix — nothing here shows it handling a messy…” Show full quote
“the incident-response examples (the PR #4821 revert, the CSV export timeout) are all clean, single-cause scenarios with a one-line fix — nothing here shows it handling a messy multi-factor incident”
Operations Manager, SaaS · 11-50 employeessimulated Specific named scenarios map onto problems respondents have right now
4 of 15 · what worked
“it directly touches the ad spend monitoring problem I already have with Google Ads. That's worth a meeting.”
Founder, Technology · 201-500 employeessimulated See all 3 comments
“"23 of 31 escalations are the same CSV export timeout" is exactly the kind of answer I want instead of a pile of individually-read tickets. That's worth a…” Show full quote
“"23 of 31 escalations are the same CSV export timeout" is exactly the kind of answer I want instead of a pile of individually-read tickets. That's worth a demo”
Co-Founder, Software · 1-10 employeessimulated “If it actually did what that OAuth incident thread shows — diff the PRs, match the trace, draft the revert and incident note in 12 seconds — that's…” Show full quote
“If it actually did what that OAuth incident thread shows — diff the PRs, match the trace, draft the revert and incident note in 12 seconds — that's real: it would cut the first 20-30 minutes of a production incident”
Operations Manager, SaaS · 11-50 employeessimulated
Relevance
The page never says who it is for
4 of 15
“I didn't have to hunt for it, but the "who exactly" (my size company? my industry?) is pieced together from the example cast and the logo wall (Shopify,…” Show full quote
“I didn't have to hunt for it, but the "who exactly" (my size company? my industry?) is pieced together from the example cast and the logo wall (Shopify, Apple, Airbnb) rather than stated as "built for 200-person SaaS companies" or similar.”
Founder, Technology · 201-500 employeessimulated See all 4 comments
“"for a 5-person team doing the job of 20" or "for the founder who's also the ops department" — instead of making me infer it from Slack screenshots”
Co-Founder, Software · 1-10 employeessimulated “The headline "Not an AI tool. A coworker" and "Lindy is your AI teammate that plugs into your tools, learns how you work, and takes real work off…” Show full quote
“The headline "Not an AI tool. A coworker" and "Lindy is your AI teammate that plugs into your tools, learns how you work, and takes real work off your plate" is a positioning tagline, not a problem statement — it doesn't name who it's for.”
Founder, SaaS · 11-50 employeessimulated “The "who" is never spelled out in a sentence like "built for ops teams" — I inferred it from the channel names (#growth, #support, #eng, #finance, #sales) and…” Show full quote
“The "who" is never spelled out in a sentence like "built for ops teams" — I inferred it from the channel names (#growth, #support, #eng, #finance, #sales) and the people pinging it (Ryan, Haneen, Batoor)”
Co-Founder, Startups · 51-200 employeessimulated The Slack scenario mockups communicate the use case better than the headline does
4 of 15 · what worked
“the Slack-thread mockups right up top do the work. "ad spend doubled," "support inbox is blowing up," "signups are throwing 500s," "reconcile Stripe vs. the gsheet ledger" —…” Show full quote
“the Slack-thread mockups right up top do the work. "ad spend doubled," "support inbox is blowing up," "signups are throwing 500s," "reconcile Stripe vs. the gsheet ledger" — those are concrete ops/eng/finance pain points, and I didn't have to dig for them”
Senior Operations Manager, Startups · 51-200 employeessimulated
Clarity
Reliability and integration depth are asserted without evidence
2 of 15
“Words like "done in 21s" and "−64% blended CAC if paused" are precise-looking but have no source attached”
Founder, Technology · 201-500 employeessimulated See all 2 comments
“never say whether that's a native PostHog connector or just API calls wrapped in a slick UI”
Director of Operations, Technology · 201-500 employeessimulated The category still has to be inferred from examples rather than stated
1 of 15
“the page just telling me straight. If they'd led with "multi-step workflow agent across your SaaS tools" instead of the coworker metaphor, I wouldn't have had to do…” Show full quote
“the page just telling me straight. If they'd led with "multi-step workflow agent across your SaaS tools" instead of the coworker metaphor, I wouldn't have had to do that translation work.”
Co-Founder, Software · 1-10 employeessimulated The core category — an agent that executes multi-step work across tools, not a chatbot…
5 of 15 · what worked
“It's an AI agent that plugs into your existing tools—Slack, Gmail, Zendesk, HubSpot, PostHog, GitHub—and actually does multi-step work: pulling data, diffing code, drafting replies, filing tickets, reconciling…” Show full quote
“It's an AI agent that plugs into your existing tools—Slack, Gmail, Zendesk, HubSpot, PostHog, GitHub—and actually does multi-step work: pulling data, diffing code, drafting replies, filing tickets, reconciling spreadsheets, then reporting back in thread.”
Operations Manager, SaaS · 11-50 employeessimulated See all 5 comments
“It's an AI agent that plugs into your work tools — Slack, Gmail, Zendesk, Stripe, PostHog, HubSpot, etc. — and actually does tasks”
Senior Operations Manager, Startups · 51-200 employeessimulated “It's an AI agent that plugs into your existing stack—Slack, Gmail, PostHog, Zendesk, HubSpot, Stripe, GitHub, Notion—and actually executes multi-step tasks: pulling data, joining it across tools, drafting…” Show full quote
“It's an AI agent that plugs into your existing stack—Slack, Gmail, PostHog, Zendesk, HubSpot, Stripe, GitHub, Notion—and actually executes multi-step tasks: pulling data, joining it across tools, drafting fixes, filing tickets, reconciling ledgers.”
Founder, SaaS · 11-50 employeessimulated “It's an AI agent that plugs into your work tools (Slack, Gmail, Zendesk, HubSpot, PostHog, Stripe etc.) and actually does tasks for you - debugging ad spend, clustering…” Show full quote
“It's an AI agent that plugs into your work tools (Slack, Gmail, Zendesk, HubSpot, PostHog, Stripe etc.) and actually does tasks for you - debugging ad spend, clustering support tickets, reconciling a Stripe ledger, building a deck - not just answering questions.”
Operations Manager, Technology · 201-500 employeessimulated “I'd call it an AI ops assistant or agentic automation tool, not a chatbot.”
VP of Operations, Startups · 51-200 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.
FounderTechnology · 201-500 employeesEU
Co-FounderSoftware · 1-10 employeesUS
Operations ManagerSaaS · 11-50 employeesEU
Senior Operations ManagerStartups · 51-200 employeesUS
Director of OperationsTechnology · 201-500 employeesEU
VP of OperationsSoftware · 1-10 employeesUS
FounderSaaS · 11-50 employeesEU
Co-FounderStartups · 51-200 employeesUS
Operations ManagerTechnology · 201-500 employeesEU
Senior Operations ManagerSoftware · 1-10 employeesUS
Director of OperationsSaaS · 11-50 employeesEU
VP of OperationsStartups · 51-200 employeesUS
FounderTechnology · 201-500 employeesEU
Co-FounderSoftware · 1-10 employeesUS
Operations ManagerSaaS · 11-50 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: 15 of 15, 1 without hesitation, 14 with reservations
- Relevance: 14 of 15, 2 without hesitation, 12 with reservations
- Value: 13 of 15, all with reservations
- Differentiation: 10 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 section after the Stripe reconciliation example covering audit log, rollback and permissions.
- 2.Add time or cost saved per week beside each Slack scenario.
- 3.Add a line under the subhead naming the roles and company size Lindy is built for.
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.