Clarity
Do they understand what you do?
15 could name what kind of product this is, unprompted.
https://kylon-main-landing-mockup.lesha27109313.chatgpt.site/15 AI-simulated buyers
Your message needs work: they know what it is, who it's for, and why it's worth their time, but not 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?
12 would take a meeting to learn more.
Is there a reason to pick you over the alternatives?
3 could name a reason to pick you over a similar option.
Your page describes: AI execution platform. They said:
7 couldn't name one; 8 got it right.
Four separate measures, not stages: all 15 personas answered all four questions. Each square is one persona.
Three respondents said the mock-data label and absence of named logos or sourced numbers signal an early-stage startup, which conflicts with an enterprise governance positioning. 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 headline asserts more control without saying what control means in practice. Spell out that Zapier fires an action with no named approver and no record of who authorised it, and that Kylon blocks the send until one exists.
3 of 15 raised this
“"Northline Stays," "RelayWorks," "Fieldcraft" with "12 hrs saved," "38% faster approval," "2.4x more requests closed" are flagged as placeholders, not real logos”
Why: Labelling the before-and-after as illustrative turns the strongest value claim on the page into a hypothetical. Show one real workflow with the firm's size and the measured time before and after.
7 of 15 raised this
“every number on the page is flagged "illustrative" or "mock data," so I have nothing real to anchor on — no named customer, no third-party audit of the approval log”
Why: The heading poses the question a reader most wants answered and leaves it inside a collapsed panel. Make the heading state the answer so a scanner gets it without clicking.
3 of 15 raised this
“the FAQ header 'Is Kylon an AI agent or an agent builder?' is the one phrase that flagged ambiguity, because the page poses that as an open question rather than answering it inline”
These landed. Keep the wording when you edit around it.
The problem and the audience are clear on first read
“the eyebrow line "For operations teams scaling AI" tells you the reader immediately, and the subhead "Your people and AI. Finally on the same team." plus "approve real work before it runs" gives you the problem in the first two lines”
The enforced approval gate is the one thing respondents named as different
“the "1 human review" / enforced approval gate — "sending is blocked until the Guest Ops lead approves" plus "the source, approver, and action are added to the workflow record" is a specific, auditable mechanism”
Why: The enforced approval gate is the one thing that separates Kylon from Slack, Zapier, and autonomy-first tools, but it sits far down under 'Why Kylon'. Put blocking, named approver, and logged decision in the first screen beside the workspace mockup.
3 of 15 raised this
“"Northline Stays," "RelayWorks," "Fieldcraft" with "12 hrs saved," "38% faster approval," "2.4x more requests closed" are flagged as placeholders, not real logos”
Why: Marking the integration row illustrative leaves a buyer unsure whether Kylon connects to their CRM at all. State which systems are live today and which are on the roadmap.
3 of 15 raised this
“"Northline Stays," "RelayWorks," "Fieldcraft" with "12 hrs saved," "38% faster approval," "2.4x more requests closed" are flagged as placeholders, not real logos”
Why: Nothing on the page shows a real company like the reader's using Kylon, so the demo ask rests on assertions alone. One named EU firm of 11-50 people, the workflow it governs, and the result would carry the CTA.
7 of 15 raised this
“every number on the page is flagged "illustrative" or "mock data," so I have nothing real to anchor on — no named customer, no third-party audit of the approval log”
Why: The page tells readers its own numbers are fake, so 12 hrs saved, 38% faster, and 2.4× count for nothing. Either publish real figures with the customer named or cut the block entirely.
7 of 15 raised this
“every number on the page is flagged "illustrative" or "mock data," so I have nothing real to anchor on — no named customer, no third-party audit of the approval log”
Why: The 12-property hotel group is the only scenario shown, and a services firm cannot see its own approval chain in it. Show a client deliverable or invoice going through the same approval gate.
1 of 15 raised this
“the target customer implied by the example (a 12-property hotel group running guest follow-ups) isn't my world. Nothing about compliance frameworks, audit requirements, or the kind of approval chains a professional services firm actually deals with.”
Why: Build-note language tells an enterprise buyer the page is unfinished and the company is pre-launch, which contradicts a governance positioning. Ship only claims that can stand without a caveat.
2 of 15 raised this
“a company with real customers wouldn't ship that to a live page, so this reads like a pre-launch or just-launched site”
Why: A buyer evaluating a governance layer wants to know how long records are retained, who can export them, and whether access is role-restricted. State retention, export format, and who can view the log.
2 of 15 raised this
“a company with real customers wouldn't ship that to a live page, so this reads like a pre-launch or just-launched site”
Why: Invented company names read as placeholder art and undercut claims of enterprise readiness. If no customer will go on record yet, remove the logo row rather than fill it.
2 of 15 raised this
“a company with real customers wouldn't ship that to a live page, so this reads like a pre-launch or just-launched site”
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's only working asset is its clarity, and clarity is not a reason to buy.
Eight respondents understood the problem and audience on first read, yet eight separately said mock-data labels invalidated the metrics, ROI, and logos. Comprehension is high and credibility is zero, so the page converts nothing.
Placeholder proof costs more than it saves: it actively destroys the one differentiator the page earns.
Five respondents named the approval gate as the only differentiator anyone could identify, and three said placeholder customer examples disqualify the proof behind it. The strongest idea on the page is neutralised by its own evidence.
The page disqualifies itself from the enterprise governance category it claims to own.
Three respondents read the mock label and missing named logos as early-stage startup signals conflicting with enterprise positioning. A governance product that cannot show audited, sourced numbers contradicts its own pitch.
Next steps are blocked on a single missing artefact the page could supply today.
Four respondents conditioned any advance on one named customer matching their profile or verified real metrics, with one saying that alone would justify a demo call. Everything else is in place and nothing moves.
The FAQ actively subtracts from the page by posing the differentiation question and refusing to answer it.
Three respondents flagged that the FAQ title asks whether Kylon is an agent builder without answering, and collapsed answers hide the granularity needed to judge differentiation. It plants doubt in the exact area already weakest.
The page rests its entire narrative on one example that breaks for the stated audience.
The hotel scenario did the clarifying work for most readers, but one respondent said it does not map to their firm's approval workflows. A single vertical anecdote carrying the whole problem statement fails the professional-services reader it targets.
Mock placeholders also cancel the differentiation the approval gate earns
3 of 15
“"Northline Stays," "RelayWorks," "Fieldcraft" with "12 hrs saved," "38% faster approval," "2.4x more requests closed" are flagged as placeholders, not real logos”
“the proof points sitting right next to it are flagged "Mock data · replace before launch," so I have zero evidence the 42-min-to-9-min or 14-to-1 numbers are real anywhere”
“the approval-gate mechanic is a genuine differentiator if it's real, but until "mock data" becomes a name I can call, this page gives me no reason to pick Kylon over a rival with actual proof”
The enforced approval gate is the one thing respondents named as different
5 of 15 · what worked
“the "1 human review" / enforced approval gate — "sending is blocked until the Guest Ops lead approves" plus "the source, approver, and action are added to the workflow record" is a specific, auditable mechanism”
“The thing that'd actually tip me toward this one is the "Sending is blocked until the Guest Ops lead approves" mechanic plus the named-approver-and-log detail — that's a concrete enforcement feature, not just a promise of "governance."”
“The approval-gate mechanic — "Sending is blocked until the Guest Ops lead approves" plus the named-owner, logged-decision detail — is the one concrete differentiator that would pull me toward this over a generic "AI agent platform."”
“the approval-gate mechanic is a genuine differentiator if it's real, but until "mock data" becomes a name I can call, this page gives me no reason to pick Kylon over a rival with actual proof”
The mock data label destroys every numeric claim on the page
7 of 15
“every number on the page is flagged "illustrative" or "mock data," so I have nothing real to anchor on — no named customer, no third-party audit of the approval log”
“the "mock data · replace before launch" label under the customer outcomes (12 hrs saved, 38% faster approvals, 2.4x more closed) tells me none of this is proven yet, just illustrative.”
“the "proof" on the page is explicitly mock data — "Mock data · replace before launch" — so right now there's nothing to believe yet”
“the three customer logos (Northline Stays, RelayWorks, Fieldcraft) are flagged the same way - so I have zero actual proof yet, just a well-told hypothetical”
“The "12 hrs saved," "38% faster," "2.4x" stats are flagged as mock data on the page itself, so none of that is real proof yet”
“the 42min-to-9min and "12 hrs saved" numbers are flagged as mock data, so I'd want real ones before I believed the ROI.”
“One verified customer reference—an actual logged example of an approval workflow going from a messy multi-step process to a single human review, with real before/after times, not the mock hotel-group numbers—that's what would get this past a discovery call into an actual pilot.”
Respondents want a named customer like themselves before advancing
4 of 15
“I'd need a named customer in our size band (11-50 employees, EU, professional services) describing the exact bottleneck we have — manager-approval chasing — with a before/after number that isn't labeled illustrative”
“One verified customer reference—an actual logged example of an approval workflow going from a messy multi-step process to a single human review, with real before/after times, not the mock hotel-group numbers—that's what would get this past a discovery call into an actual pilot.”
“That's worth a short demo call, but not worth a real commitment yet — those stats are flagged "mock data, replace before launch," so I'd take the meeting specifically to see our own workflow run through it and get real numbers, not their illustrative ones”
“Early-stage, maybe seed to Series A, B2B startup — the single polished hotel-industry example plus "mock data, replace before launch" sitting right in the copy tells me this is pre-revenue-proof or very early customers”
The FAQ raises a question it never answers and hides detail
3 of 15
“the FAQ header 'Is Kylon an AI agent or an agent builder?' is the one phrase that flagged ambiguity, because the page poses that as an open question rather than answering it inline”
“the FAQ answers are all collapsed with no preview text ("How do permissions and human approval work?+"), so I can't actually see if the approval model is granular (per-action, per-agent, per-integration) or just a single blanket toggle”
“the stacking of category labels - "governed AI execution workspace," "agents," "workflow," "orchestration" all get used almost interchangeably, and none of them is the plain-English sentence I'd use to describe it to my own team”
The problem and the audience are clear on first read
8 of 15 · what worked
“the eyebrow line "For operations teams scaling AI" tells you the reader immediately, and the subhead "Your people and AI. Finally on the same team." plus "approve real work before it runs" gives you the problem in the first two lines”
“The hotel example with the Guest Care agent blocked until "the Guest Ops lead approves" made the problem concrete in about two seconds”
“The eyebrow line "For operations teams scaling AI" plus the subhead "Your people and AI. Finally on the same team." told me the audience before I even hit the fold”
“It's a governed workspace for AI agents that sits on top of tools we already have—letting agents draft work from company data (inbox, CRM, Slack etc.) but blocking any external action until a named human approves it, with a log of who approved what.”
“the eyebrow line "For operations teams scaling AI" plus the H1 "Your people and AI. Finally on the same team." told me the audience, and the subhead spelled the problem”
“The line "For operations teams scaling AI" is right at the top, and "Your people and AI. Finally on the same team" plus the subhead about building a "governed AI execution workspace" where you "approve real work before it runs" told me exactly what pain this hits”
“It's a governed layer sitting on top of AI agents — Kylon connects agents (built or brought-in) to company systems like Slack, Gmail, HubSpot, Salesforce, Notion, Drive, and then forces a human approval gate before any agent action actually executes externally”
“The hook that stuck with me was "14 manual touches to one human review" — that's the pitch I'd repeat to someone else.”
The hotel example does not map to professional services workflows
1 of 15
“the target customer implied by the example (a 12-property hotel group running guest follow-ups) isn't my world. Nothing about compliance frameworks, audit requirements, or the kind of approval chains a professional services firm actually deals with.”
The page reads as pre-launch rather than enterprise-ready
2 of 15
“a company with real customers wouldn't ship that to a live page, so this reads like a pre-launch or just-launched site”
“Early-stage, maybe seed to Series A, B2B startup — the single polished hotel-industry example plus "mock data, replace before launch" sitting right in the copy tells me this is pre-revenue-proof or very early customers”
“The "12 hrs saved," "38% faster," "2.4x" stats are flagged as mock data on the page itself, so none of that is real proof yet”
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.







