Clarity
Do they understand what you do?
7 could name what kind of product this is, unprompted.
https://ux.snu.ac.kr/15 AI-simulated buyers
Your message needs work: they could not tell what it is, who it's for, why it's worth their time, or why to pick you.
Do they understand what you do?
7 could name what kind of product this is, unprompted.
Can they tell what it solves, and who it's for?
0 could quickly tell what problem it solves and who it is for.
Do they actually want it?
1 would take a meeting to learn more.
Is there a reason to pick you over the alternatives?
0 could name a reason to pick you over a similar option.
Your page describes: HCI research laboratory. They said:
3 couldn't name one; 8 named the wrong one; 4 got it right.
Four separate measures, not stages: all 15 personas answered all four questions. Each square is one persona.
Five respondents said the intern blog and Lab Stories content is internal culture and recruiting material aimed at prospective students. The mix of dense academic summaries with casual intern diary posts was called misaligned with professional buyers. 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 page jumps straight to project summaries without naming the problem a buyer already feels. State it plainly, such as teams shipping AI assistants with no reliable way to test whether the conversation actually works.
6 of 15 raised this
“I'd need a line near the top like 'we help product teams validate conversational AI UX before launch' plus a visible way to engage — a contact form, a rate card, or 'commission a study' button”
Why: Named clients give trust but nothing behind them, so a buyer has to take the roster on faith. Build out one project with the question asked, the method used, and what the client did with it.
4 of 15 raised this
“The only semi-concrete signal is the client roster — LG전자 고객품질연구소 and 삼성전자 — which at least tells me this lab has done work with large Korean corporates”
Why: The page opens with a name and a project list, so a reader cannot tell whether this is a research archive or a service they can hire. Write a line saying the lab evaluates and validates conversational AI user experience for companies.
6 of 15 raised this
“This isn't a product at all — it's a university research lab page. SNU UX LAB (Seoul National University) is an academic HCI/UX research group”
These landed. Keep the wording when you edit around it.
Named client work for LG and Samsung is the one concrete asset respondents believed
“The one thing that would actually pull me toward shortlisting them is the named client list with specific project titles — "LG전자 고객품질연구소" on the ThinQ On voice agent work and "삼성전자 경험기획그룹" on the Clothing Care pilot.”
Why: Nowhere does the page say who it is for, so a product or quality lead has to guess whether it applies to them. Name the roles and teams, such as conversational AI product and quality teams launching voice or chat assistants.
6 of 15 raised this
“I'd need a line near the top like 'we help product teams validate conversational AI UX before launch' plus a visible way to engage — a contact form, a rate card, or 'commission a study' button”
Why: There is no visible way to start a conversation, so an interested reader has nowhere to go. Add one inquiry link with a clear label about commissioning a project.
6 of 15 raised this
“I'd need a line near the top like 'we help product teams validate conversational AI UX before launch' plus a visible way to engage — a contact form, a rate card, or 'commission a study' button”
Why: Nothing on the page says why this lab rather than an agency or an in-house team. Name the specific edge, such as validated evaluation criteria for voice and chat agents built from repeated enterprise studies.
4 of 15 raised this
“The only semi-concrete signal is the client roster — LG전자 고객품질연구소 and 삼성전자 — which at least tells me this lab has done work with large Korean corporates”
Why: The enterprise client names are buried inside project metadata where a scanning reader misses them. Pull the names up so the track record is visible before any body copy.
4 of 15 raised this
“The only semi-concrete signal is the client roster — LG전자 고객품질연구소 and 삼성전자 — which at least tells me this lab has done work with large Korean corporates”
Why: The LG and Samsung entries describe background context but never say what was delivered or what changed. Add one line per project naming the deliverable, such as an evaluation framework, test protocol, or benchmark scores.
6 of 15 raised this
“there's no pricing, engagement model, timeline, or methodology detail on the page, so I can't tell what it would cost my team in time or budget, or how an engagement would actually run.”
Why: A buyer cannot tell what working with the lab involves, what methods are used, or how long it takes. Describe the steps of a typical evaluation and a typical timeframe.
6 of 15 raised this
“there's no pricing, engagement model, timeline, or methodology detail on the page, so I can't tell what it would cost my team in time or budget, or how an engagement would actually run.”
Why: Each summary opens with industry context about LG's AI initiative before reaching anything the lab did. Put the result or method first and the background after.
6 of 15 raised this
“there's no pricing, engagement model, timeline, or methodology detail on the page, so I can't tell what it would cost my team in time or budget, or how an engagement would actually run.”
Why: Every project is stamped closed, making the work read as finished case files rather than capabilities available now. Show the delivery year and what the client got instead of a closed marker.
6 of 15 raised this
“This isn't a product at all — it's a university research lab page. SNU UX LAB (Seoul National University) is an academic HCI/UX research group”
Why: 'Recent Project' tells a scanner nothing about what kind of work the lab does. Change it to name the work, such as voice and chat UX evaluation projects for enterprise clients.
6 of 15 raised this
“This isn't a product at all — it's a university research lab page. SNU UX LAB (Seoul National University) is an academic HCI/UX research group”
Why: Intern diary posts about dinner and bookshelves sit directly under enterprise project work, making the site read as recruiting material. Keep the homepage on client work and link to the stories from a recruiting page.
5 of 15 raised this
“half the page is intern blog diary entries about packing for a conference or chopping clams, which is charming for students browsing the lab but tells me nothing about engagement model, cost, or methodology.”
Why: The heading gives no clue that what follows is internal culture writing, so a corporate reader reads it as the lab's professional voice. Label it clearly as life in the lab for prospective students.
5 of 15 raised this
“half the page is intern blog diary entries about packing for a conference or chopping clams, which is charming for students browsing the lab but tells me nothing about engagement model, cost, or methodology.”
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 does not read as a commercial offering at all, so no amount of message tuning will help until it is reframed as a service.
Six respondents read the site as an academic archive or project portfolio rather than a product or vendor offering, with project titles functioning as internal research reports carrying no value proposition.
Buyers are being asked to do the selling work themselves, and most will simply leave instead.
Six respondents had to reverse-engineer audience, buyer problem, and use case from context, and one found no contact form or commissioning path to act on even after inferring purpose.
The page cannot survive a procurement conversation because every input a buyer needs is absent.
Six respondents cited missing methodology, outcome metrics, pricing, timelines, and capability statements; a further respondent found no feature list, demo, or comparison cues for vendor evaluation.
The one asset that works is being wasted.
Four respondents named the LG ThinQ and Samsung work as the only concrete differentiator, yet four also said it sits without case studies, project detail, or measurable outcomes and would need independent verification.
The page serves two audiences and converts neither.
Five respondents read the intern blog and Lab Stories as recruiting content for prospective students, and called the mix of dense academic summaries with casual intern diaries misaligned with professional buyers.
The site signals the lab is not currently taking work.
Respondents flagged that '[종료]' closed tags frame all research as finished case files with no stated deliverables, compounding the absence of any visible engagement or commissioning path.
Audience and problem statement must be reverse-engineered
6 of 15
“I'd need a line near the top like 'we help product teams validate conversational AI UX before launch' plus a visible way to engage — a contact form, a rate card, or 'commission a study' button”
“There's no problem statement or target-reader line anywhere on this page because it's not selling anything”
“Honestly, there's no "problem solved" or "who it's for" stated anywhere because this isn't selling anything — it's a lab homepage listing research projects”
“It wasn't spelled out as a "problem/solution" at all — this reads as a lab homepage, not a pitch, so there's no stated pain point to solve.”
“this is just a university lab's project portfolio, not a tool solving a problem for a defined buyer”
“there's no stated problem or audience, just a list of project titles and client names like "LG전자 고객품질연구소" or "삼성전자 경험기획그룹" with a sentence or two of context each”
“the 'who it's for' (students wanting to intern, or companies wanting to commission UX studies) is never stated outright — I pieced it together from context”
No product feature list, demo, or comparison signals exist for vendor evaluation
1 of 15
“It's not a vendor page with a product, pricing, or deployment claim; it's SNU's lab page listing project case studies like "LG전자 고객품질연구소" and "삼성전자 경험기획그룹"”
Named client work for LG and Samsung is the one concrete asset respondents believed
4 of 15 · what worked
“The one thing that would actually pull me toward shortlisting them is the named client list with specific project titles — "LG전자 고객품질연구소" on the ThinQ On voice agent work and "삼성전자 경험기획그룹" on the Clothing Care pilot.”
“they've done paid work for LG전자 and 삼성전자 on exactly my domain (voice/chat agent UX evaluation for ThinQ On and ChatThinQ)”
“The one thing that'd tip me toward shortlisting them over a generic UX consultancy is the client roster embedded in the project titles—LG전자 (twice, for ThinQ On voice agent and ChatThinQ), 삼성전자, 콘텐츠진흥원”
“The one concrete thing that would pull me toward actually contacting them is the named client work — "LG전자 고객품질연구소" on the ThinQ On voice-agent UX evaluation”
The client roster is credibility without evidence behind it
4 of 15
“The only semi-concrete signal is the client roster — LG전자 고객품질연구소 and 삼성전자 — which at least tells me this lab has done work with large Korean corporates”
“The one thing that would actually tip me toward this lab over a competitor is the specific client roster tied to specific named products — "LG전자 고객품질연구소" on the 'LG 씽큐 온' voice agent project”
“seeing "LG전자 고객품질연구소" and "삼성전자 경험기획그룹" actually commissioned repeat work (two separate LG projects, in 2024 and 2025) tells me real companies trust them enough to pay twice”
“the "Lab Stories" intern blog posts actually undercut confidence by showing this is largely a training ground for students, not a seasoned consultancy bench.”
No methodology, metrics, pricing, or engagement model is given
6 of 15
“there's no pricing, engagement model, timeline, or methodology detail on the page, so I can't tell what it would cost my team in time or budget, or how an engagement would actually run.”
“There's no stated methodology, no comparison to how I'd evaluate conversational-AI UX today, no metric like "reduces eval cycle time"”
“there's no methodology writeup, no published findings, no sense of turnaround time or cost, just client names and a sentence of project description”
“there's nothing on this page telling me what that methodology actually is, what the evaluation criteria were, or any outcome data from the LG or Samsung engagements”
“it's not a tool or service with a value prop, it's a lab's project archive and student blog”
The page reads as a university lab portfolio, not a commercial offering
6 of 15
“This isn't a product at all — it's a university research lab page. SNU UX LAB (Seoul National University) is an academic HCI/UX research group”
“The project titles themselves are the blocker — things like '음성 중심 대화 경험의 UX 평가 요소와 검증 방법 연구' read as dense academic-paper language, not a pitch”
“This is a university research lab, not a product at all — it's Seoul National University's UX Lab, doing applied research projects with corporate partners like LG and Samsung”
“This isn't a product at all — it's a university research lab's site.”
“things like '[종료] Voice 중심 대화 경험의 UX 평가 요소와 검증 방법 연구' read as internal research-report headlines, not pitch copy, so there's no verb like 'we help' or 'we offer' anywhere”
“University UX research lab doing client projects for LG, Samsung etc. Not a product at all.”
“This isn't a product at all — it's a university research lab's site, specifically Seoul National University's UX LAB.”
Closed-project tagging and missing deliverables make the work feel archived and…
2 of 15
“The project blurbs literally cut off mid-sentence—'기능적 성능과 사용 효능감(UX)을...'—so I never get the actual claim or outcome”
The tone targets students and recruits, not corporate buyers
5 of 15
“half the page is intern blog diary entries about packing for a conference or chopping clams, which is charming for students browsing the lab but tells me nothing about engagement model, cost, or methodology.”
“The tone definitely isn't written for someone like me — it swings between dry academic project summaries ("Voice 중심 대화 경험의 UX 평가 요소와 검증 방법 연구") and chatty, diary-style intern stories about book shelves and plastic bags”
“writes for grad students/interns, not buyers like me”
“half the page is intern diary posts about book shelves and plastic bags over someone's face during a study, which reads like it's written for prospective students or the lab's own community, not for a company deciding on a research partnership”
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.







