Clarity
Do they understand what you do?
15 could name what kind of product this is, unprompted.
https://mybrains.ai/15 AI-simulated buyers
Your message needs work: they know what it is and who it's for, but not why it's worth their time or 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?
7 would take a meeting to learn more.
Is there a reason to pick you over the alternatives?
6 could name a reason to pick you over a similar option.
Your page describes: AI knowledge base. They said:
15 got it right.
Four separate measures, not stages: all 15 personas answered all four questions. Each square is one persona.
Five respondents read a young venture-backed startup selling to mid-market and enterprise ops or IT buyers, citing deployment options and breezy tone. One said the saving is small for a 1-10 person team. 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 supplier-says-Friday, board-says-Thursday catch is what buyers remembered, but it only appears inside a demo. Name it as a capability: Brains spots when your tools disagree and tells you before you act on the wrong one.
Why: Buyers could not see that any real company uses this, or one their size. Put a named customer, their headcount and one concrete result next to the 'Is the Northstar launch plan ready' demo.
4 of 15 raised this
“I'd take a meeting only if they'll walk me through the mechanism and show a reference customer of my size; the free 30-day POV on one workflow is a reasonable low-risk way to test it”
Why: Readers had to guess the audience from the app list. State who it is for, such as ops leads at small teams running work across Slack, Gmail and a CRM.
2 of 15 raised this
“But the intended reader is never stated outright. There's no 'for COO/ops leaders' line, only a team-picker (Leadership, Customer success, Sales...) and a headline, '10x your team', that tells me nothing”
These landed. Keep the wording when you edit around it.
The problem statement and Thursday-launch demo land
“the 'Is Thursday's launch still on?' example, where the supplier email and the customer promise get reconciled, is the sort of thing I'd value at my size”
Approval gates and conflict flagging are the differentiators that stick
“The one thing that would keep it on my shortlist is the comparison table row 'Flags conflicting information: Surfaces it for you to decide', plus the 'A person approves' line”
Why: Buyers saw no difference from the AI already inside Gmail or Teams. Say that Brains reads across Slack, Gmail, HubSpot and Monday together, not one vendor's apps.
Why: Approval gates kept buyers interested, but the toggle is shown without saying what it does. Write that Brains drafts emails and actions but sends nothing until you approve.
Why: 'Fewer forgotten follow-ups' gives no sense of how much time or how many misses this saves. State hours saved per week or follow-ups caught, with where the number comes from.
4 of 15 raised this
“I'd take a meeting only if they'll walk me through the mechanism and show a reference customer of my size; the free 30-day POV on one workflow is a reasonable low-risk way to test it”
Why: Buyers could not judge whether the trial leads to something they can afford. Say what it costs after the trial, per user or per team.
4 of 15 raised this
“I'd take a meeting only if they'll walk me through the mechanism and show a reference customer of my size; the free 30-day POV on one workflow is a reasonable low-risk way to test it”
No specific edits needed here — this layer held up.
Why: '10× your team' tells a buyer nothing about what they get. Lead with the concrete job, such as asking one question and getting an answer from your email, Slack and CRM.
4 of 15 raised this
“I picture a young, venture-backed software startup, probably a few years old and fewer than a hundred people, selling to mid-market and enterprise teams.”
Why: This line reads as a pitch-deck slogan. Say plainly that Brains turns your company's emails, chats and CRM into one place your AI can search.
4 of 15 raised this
“I picture a young, venture-backed software startup, probably a few years old and fewer than a hundred people, selling to mid-market and enterprise teams.”
Why: 'POV' is enterprise procurement language that tells small teams this is not for them. Use plain wording like a free 30-day trial.
4 of 15 raised this
“I picture a young, venture-backed software startup, probably a few years old and fewer than a hundred people, selling to mid-market and enterprise teams.”
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 earns attention with the problem and then loses the buyer at the proof stage.
4 of 15 found the Thursday-launch problem concrete. 4 of 15 then found no hours-saved, accuracy figures, named customers or pricing, so the interest the page builds has nothing to convert into.
Readers can repeat what the product connects, but they cannot say why to buy it instead of the AI they already pay for.
3 of 15 repeated the Gmail/Slack/CRM integration list almost word for word. 3 of 15 still saw no difference from Copilot or Gemini, which means the integration list is being read as a commodity.
The headline wastes the page's most valuable space because it names neither a reader nor an outcome.
3 of 15 called '10× your team' uninformative slogan-speak. 2 of 15 had to infer the audience from the team picker, so the headline fails to tell readers both who it is for and what it does.
Smaller buyers screen themselves out before they reach the value argument.
4 of 15 read the page as built for mid-market and enterprise ops or IT, and one said the saving is too small for a 1-10 person team. With no stated audience, nothing corrects that impression.
The only differentiators that hold sit inside the asset readers trust least.
3 of 15 kept the product on their shortlist because of approval gates and conflict flagging from the comparison table. Readers in the proof theme called that same self-authored table unsupported.
The vague metaphors cost the page the moment where it had readers' agreement.
3 of 15 called 'living knowledge base' and 'connects the dots' vague. Those phrases appear right where the concrete demo had landed with 4 of 15, which turns clear understanding back into abstraction.
Approval gates and conflict flagging are the differentiators that stick
3 of 15 · what worked
“The one thing that would keep it on my shortlist is the comparison table row 'Flags conflicting information: Surfaces it for you to decide', plus the 'A person approves' line”
“'A person approves. Brains drafts. Nothing is sent, posted or changed until someone on your team says yes,' plus 'If someone can't open a file today, they can't see it through Brains either.'”
“'Do anything / + Require approval' paired with 'Brains drafts. Nothing is sent, posted or changed until someone on your team says yes.'”
“'Flags conflicting information: surfaces it for you to decide' and 'Every answer linked to its source, down to the thread or record,'”
Claims lack numbers, named customers and method
4 of 15
“I'd take a meeting only if they'll walk me through the mechanism and show a reference customer of my size; the free 30-day POV on one workflow is a reasonable low-risk way to test it”
“To pick this one I'd need a named reference customer of roughly my size, a measured figure for how often it correctly detects and surfaces a conflict, and a plain definition of how it indexes my sources.”
“The 'Thursday launch' demo made the problem concrete, but I saw no numbers on hours saved or accuracy, and '10× your team' is empty”
“That's real, but it's convenience for me, not a line on the P&L, and the page gives me no hours saved, no error rates, nothing to size it against.”
“a table the vendor wrote about itself is an unsupported claim, and what would rule it out is that nothing shows how it detects a conflict or any accuracy figure”
“I'd take a meeting only if they show numbers from a comparable 50-200 person company and can tell me who controls what the AI is allowed to see and send”
“What would rule it out is the comparison table: it's all ticks and crosses on the vendor's own terms, with no numbers, no customer names and nothing from a 50-200 person company”
“I saw no named customers and no price, so for a 1-10 person shop on Teams I'd want proof”
“Proof that it catches something like the Thursday-launch miss before it costs me a customer, in a shop my size, with a number attached, like hours a week I and my managers stop spending chasing status.”
How the product works and what category it is in stays unclear
3 of 15
“I'd call it a company-memory or context layer for AI, but the page never defines 'brain' or says how the connecting and indexing actually works”
“honestly it sounds like what Copilot or Gemini already promise.”
“The phrases doing the damage were 'living knowledge base' and 'connects the dots for you'.”
Respondents can repeat back what the product connects
3 of 15
“it's an AI layer that plugs into Gmail, Slack, the CRM and project boards, builds one company knowledge base”
“it's a layer that plugs into Gmail, Slack, the CRM and the rest, builds one company knowledge base”
“Looks like an AI layer that plugs into Slack, Gmail, the CRM and so on, builds a company-wide knowledge base, and then answers questions and drafts follow-ups using that context.”
The intended reader is never stated
2 of 15
“But the intended reader is never stated outright. There's no 'for COO/ops leaders' line, only a team-picker (Leadership, Customer success, Sales...) and a headline, '10x your team', that tells me nothing”
“The intended reader is never actually stated though. No 'for CFOs' or 'for ops teams' anywhere.”
The problem statement and Thursday-launch demo land
4 of 15 · what worked
“the 'Is Thursday's launch still on?' example, where the supplier email and the customer promise get reconciled, is the sort of thing I'd value at my size”
“The problem was fairly quick to find: 'Every day, you explain your company to AI. From scratch.' and the Slack/Gmail/Monday 'Not connected to your AI' demo made it concrete within a scroll or two.”
“The problem was clear fast: 'Every day, you explain your company to AI. From scratch' and the Thursday-launch demo”
“'Every day, you explain your company to AI. From scratch.' and the Thursday-launch story right under it say that AI forgets”
“If it truly worked, I'd stop being the human copy-paste between Slack, Gmail and the CRM, which is a real annoyance.”
The page reads as built for larger companies, not small buyers
4 of 15
“I picture a young, venture-backed software startup, probably a few years old and fewer than a hundred people, selling to mid-market and enterprise teams.”
“The tone is polished and a bit breezy, more product-launch energy than finance-buyer energy, and '10× your team' is hype I tune out.”
“The 'Pick a team' tabs, the on-prem and 'separate tenant' deployment options, and the 'your IT team can sign off' security section all say they expect a buying committee, not one person with a card.”
“at 1-10 people I carry most of that context in my head, so the saving is small, and nothing on the page says it works with Teams, which is what I run on.”
“The tone is polished and a bit breathless ('10× your team', 'Every organization has a brain')”
“The deployment options (separate tenant, on-prem, your own AWS/GCP/Azure) and the 'IT team can sign off' section tell me that.”
'10× your team' and similar slogans read as empty
3 of 15
“The tone is part-way for me: the Thursday-launch example reads like my week, but '10x your team' and 'Every organization has a brain' are slogan-speak”
“The '10× your team' headline is empty, and I'd still want numbers proving it beats what Copilot or Gemini already do.”
“the '10× your team' headline is empty noise that tells me nothing”
“'Every organization has a brain' and '10× your team' read like pitch-deck language, and there's not a single customer name or number to show they've sold to a 25-person shop like mine.”
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.







