Message test · Meetsol

Only 1 of 15 buyers could say why they would pick Meetsol over an alternative.

https://www.meetsol.com/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.

Simulated responsesNo humans answered these questions. Every quote below was written by an AI model role-playing a buyer profile.
Share score cardDownload as markdown
Saved report, kept for 60 days — expires in 60 days. Re-opening it is free.
01

Your verdict

  • Clarity

    Do they understand what you do?

    Strong15 of 15

    15 could name what kind of product this is, unprompted.

  • Relevance

    Can they tell what it solves, and who it's for?

    Strong12 of 15

    12 could quickly tell what problem it solves and who it is for.

  • Value

    Do they actually want it?

    Weak7 of 15

    7 would take a meeting to learn more.

  • Differentiation

    Fix first

    Is there a reason to pick you over the alternatives?

    Fail1 of 15

    1 could name a reason to pick you over a similar option.

See what they thought you were

Your page describes: agentic HR system. They said:

  • 4×Agentic HR platform / next-gen HRISmatches
  • 3×Agentic HRIS / HR system of recordmatches
  • 2×Agentic HR system / HRIS replacementmatches
  • 1×Agentic HR system / AI-native HRISmatches
  • 1×Agentic HRIS / core HR systemmatches
  • 1×Agentic HRIS / HR platformmatches
  • 1×AI-native HR system / HRIS replacementmatches
  • 1×AI-native HRIS / agentic HR platformmatches
  • 1×AI-native HRIS / HR system of recordmatches

15 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 ▸

Two respondents said the positioning signals a pre-launch startup courting investors, recruits, or design partners rather than addressing a ready buyer. 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 humans
02

Fix these first

Fix 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.

  1. Extend the Builders paragraph with what the founders decided to build differently.

    Why: Workday pedigree is the only concrete claim, and it reads as credentials rather than a product argument. Say what they learned at Workday that shapes Sol's architecture, and what they refused to repeat.

    Moves Differentiation
    Give a reason to choose you

  2. Add a section under Our Product showing product screens or a short workflow walkthrough.

    Why: A reader gets four claim blocks and never sees the product. Show two or three screens of the agent doing a task so buyers can judge it.

    7 of 15 raised this

    “without telling me what actually gets automated or what breaks today that this fixes”
    Senior HR Manager, SaaS · 501-1000 employeessimulated
    Moves Value
    Show the product early

  3. Replace "Run at the pace of human ambition" headline with what Sol does.

    Why: The opening line reads as a slogan and delays the product for a full scroll. Lead with the job Sol performs for an HR team.

    9 of 15 raised this

    “nowhere does it say what the agent actually executes (approves a PTO request? updates comp data? resolves a policy question?)”
    Director of Human Resources, SaaS · 501-1000 employeessimulated
    Moves Clarity
    Lead with the use case

Keep these · 2

These landed. Keep the wording when you edit around it.

  1. Keep · Differentiation

    Workday founder pedigree is the one differentiator respondents could name — and the only…

    “Pete Schlampp (former Workday EVP Products/Chief Strategy Officer), Jim Stratton (former Workday CTO), Jon Ruggiero (15 years as Workday's Chief Technology Architect) — that's not "we admire Workday,"…” Show full quote
    “Pete Schlampp (former Workday EVP Products/Chief Strategy Officer), Jim Stratton (former Workday CTO), Jon Ruggiero (15 years as Workday's Chief Technology Architect) — that's not "we admire Workday," that's the people who built Workday's platform starting over”
    Director of Human Resources, SaaS · 501-1000 employeessimulated
  2. Keep · Relevance

    The problem statement lands fast and matches a real pain

    “The problem statement is right up top and easy to spot — "Work changed. Your HR system didn't."”
    Senior HR Manager, SaaS · 501-1000 employeessimulated
03

All recommendations

Differentiation

Fail1 of 15
Moves DifferentiationSpecifics beat superlatives

Rewrite "Agentic by design" to state what Sol does that a bolted-on HRIS assistant cannot.

Why: "Built for change, designed to scale, and reimagined with AI from the ground up" could sit on any HR vendor's page. Contrast one specific thing Sol does because it was built this way against what incumbents cannot do.

Moves DifferentiationAnswer the live objection

Add a line under the hero naming the migration path off an existing HRIS.

Why: "Replace your HRIS" asks for the biggest swap in HR and says nothing about how. Name the migration approach, timeline, and what runs in parallel so finance and IT have something to evaluate.

Value

Weak7 of 15
Moves ValueTie the feature to the outcome

Replace "A self-maintaining platform" body copy with a named task Sol completes end to end.

Why: "Sol handles the operational load" never says which work disappears. Name one job, like closing a job requisition or updating a manager's org chart after a reorg, and what it takes today.

7 of 15 raised this

“without telling me what actually gets automated or what breaks today that this fixes”
Senior HR Manager, SaaS · 501-1000 employeessimulated
Moves ValueAnswer the live objection

Add availability and design-partner terms beside the "Sign up for early access" button.

Why: Buyers cannot tell whether they can buy this now or are joining a waitlist for a future release. State when it goes live, what design partners get, and what is expected of them.

7 of 15 raised this

“without telling me what actually gets automated or what breaks today that this fixes”
Senior HR Manager, SaaS · 501-1000 employeessimulated

Relevance

Strong12 of 15
Moves RelevanceName the audience

Add a line under the hero naming the buyer role and company size Sol fits.

Why: Buyers reconstruct the audience from founder bios and the contact form. Say who this is for, such as heads of HR operations at companies of a given headcount, in the hero.

7 of 15 raised this

“I had to infer from context clues like "leaders," "HR can spend less time managing systems," and the "For prospective customers" line about "if you lead people at…” Show full quote
“I had to infer from context clues like "leaders," "HR can spend less time managing systems," and the "For prospective customers" line about "if you lead people at a growing enterprise"”
Director of Human Resources, SaaS · 501-1000 employeessimulated
Additional signal

Brand alignment

Weak8 of 15
Moves Brand alignment

Move investor and advisor logos below the fold, out of the primary Team section.

Why: Sutter Hill and NEA logos sitting next to founder bios make the page read as a fundraising deck. Lead the section with customer-facing credibility and keep investors as a footnote.

2 of 15 raised this

“They're clearly targeting enterprise-ish People leaders eventually, but right now they're really selling to two audiences: prospective enterprise customers who'll wait years for something real, and engineers/investors who…” Show full quote
“They're clearly targeting enterprise-ish People leaders eventually, but right now they're really selling to two audiences: prospective enterprise customers who'll wait years for something real, and engineers/investors who want to join or fund the story. The tone is polished, confident, and design-forward (the repeated stylized headlines, the founder bios with LinkedIn links) which tells me this was written to impress a boardroom or a recruiting candidate as much as an HR buyer”
Director of Human Resources, Professional Services · 51-200 employeessimulated
Moves Brand alignmentAnswer the live objection

Add a data handling and security line under the product section.

Why: The page claims an agent needs the full picture of how work gets done but never says where that data lives or who sees it. State the hosting model, certifications in progress, and what the agent can access.

2 of 15 raised this

“They're clearly targeting enterprise-ish People leaders eventually, but right now they're really selling to two audiences: prospective enterprise customers who'll wait years for something real, and engineers/investors who…” Show full quote
“They're clearly targeting enterprise-ish People leaders eventually, but right now they're really selling to two audiences: prospective enterprise customers who'll wait years for something real, and engineers/investors who want to join or fund the story. The tone is polished, confident, and design-forward (the repeated stylized headlines, the founder bios with LinkedIn links) which tells me this was written to impress a boardroom or a recruiting candidate as much as an HR buyer”
Director of Human Resources, Professional Services · 51-200 employeessimulated
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 page sells a category, not a product — the core claim collapses the moment anyone asks what the software does.

    Ten respondents said the agentic and self-maintaining claims are never operationalized, with no workflow examples, screenshots, or task-level outcomes, and several called the language buzzwords. Two could not even tell how data is handled.

  • high

    The only recognized strength is a founder credential, which means the page is selling people rather than software.

    Eight respondents named Workday pedigree as the sole checkable differentiator, and all eight said it is insufficient against incumbents with live products. With ten unable to describe the product, biography is doing all the work.

  • high

    There is nothing a champion can carry into an internal approval, so even convinced readers stall.

    Nine respondents flagged missing reference customers, demo, case studies, and quantified metrics; one noted a system-of-record swap requires finance and IT sign-off the page equips them for nothing.

  • high

    The page disqualifies itself from the current buying cycle and never says who should keep reading.

    Four respondents read the 2027 go-live as execution risk blocking purchase, one saying it eliminates fit for smaller companies, while six had to reconstruct the target buyer from bios and contact details.

  • medium

    The single moment that works — the problem statement — is squandered because nothing after it pays off.

    Only three respondents cited the fast-landing problem statement as a success, against nine who found the solution unexplained and nine who found outcome claims unproven. Recognition of pain converts to nothing.

  • medium

    The page is written for the wrong audience entirely and will be read as fundraising collateral.

    Two respondents said the positioning courts investors, recruits, or design partners rather than buyers, and two others framed the timeline as a pre-launch design-partner ask. Founder bios substitute for buyer targeting.

Differentiation

  • Workday founder pedigree is the one differentiator respondents could name — and the only…

    8 of 15 · what worked

    “Pete Schlampp (former Workday EVP Products/Chief Strategy Officer), Jim Stratton (former Workday CTO), Jon Ruggiero (15 years as Workday's Chief Technology Architect) — that's not "we admire Workday,"…” Show full quote
    “Pete Schlampp (former Workday EVP Products/Chief Strategy Officer), Jim Stratton (former Workday CTO), Jon Ruggiero (15 years as Workday's Chief Technology Architect) — that's not "we admire Workday," that's the people who built Workday's platform starting over”
    Director of Human Resources, SaaS · 501-1000 employeessimulated
    See all 6 comments
    “The founder pedigree is the only concrete thing that would move me toward it — Pete Schlampp as former Workday EVP Products, Jim Stratton as former Workday CTO”
    VP of People Ops, Software Development · 11-50 employeessimulated
    “it's also the only concrete thing on the page — there's no feature, no demo, no case study, so if a competitor showed me even one screenshot of…” Show full quote
    “it's also the only concrete thing on the page — there's no feature, no demo, no case study, so if a competitor showed me even one screenshot of "answers, not tickets" actually working, that competitor wins outright”
    Chief People Officer, Professional Services · 51-200 employeessimulated
    “Pete Schlampp as former Workday EVP Products, Jim Stratton as former Workday CTO, Jon Ruggiero 15 years as Workday's Chief Technology Architect. That's a specific, checkable reason to…” Show full quote
    “Pete Schlampp as former Workday EVP Products, Jim Stratton as former Workday CTO, Jon Ruggiero 15 years as Workday's Chief Technology Architect. That's a specific, checkable reason to believe they understand the guts of an HR system of record”
    HR Manager, Technology · 201-500 employeessimulated
    “The founder pedigree is the one concrete thing that would keep it on the shortlist — four ex-Workday leaders plus Sutter Hill and NEA backing gives me some…” Show full quote
    “The founder pedigree is the one concrete thing that would keep it on the shortlist — four ex-Workday leaders plus Sutter Hill and NEA backing gives me some reason to believe they understand the category, more than a random AI-HR startup would. But that's a reason to watch it, not pick it”
    VP of People Ops, Professional Services · 51-200 employeessimulated
    “there's no number here — no "cuts time-to-answer by X%" or "reduces HRIS admin hours by Y" — just founder pedigree and vibes from two CPO quotes”
    HR Manager, SaaS · 501-1000 employeessimulated

Value

  • Every outcome claim is unproven — no customers, demo, or numbers

    7 of 15

    “without telling me what actually gets automated or what breaks today that this fixes”
    Senior HR Manager, SaaS · 501-1000 employeessimulated
    See all 8 comments
    “there's no customer name I recognize actually live on it (first customers go live 2027), no case study, no number I can check”
    Chief People Officer, Technology · 201-500 employeessimulated
    “there's no number here — no "cuts time-to-answer by X%" or "reduces HRIS admin hours by Y" — just founder pedigree and vibes from two CPO quotes”
    HR Manager, SaaS · 501-1000 employeessimulated
    “there's no number anywhere (no % reduction in tickets, no time-to-resolution stat, no cost-of-maintenance comparison to Workday/ADP), and go-live isn't until "early 2027," so this is a bet…” Show full quote
    “there's no number anywhere (no % reduction in tickets, no time-to-resolution stat, no cost-of-maintenance comparison to Workday/ADP), and go-live isn't until "early 2027," so this is a bet on a roadmap, not a product”
    Director of Human Resources, SaaS · 501-1000 employeessimulated
    “there's zero mechanism here — no demo, no workflow example, no data on what "self-maintaining" means in practice.”
    VP of People Ops, Software Development · 11-50 employeessimulated
    “I'd need a named customer my size and industry describing a before/after — actual hours saved, tickets reduced, or a specific workflow that changed — not just a…” Show full quote
    “I'd need a named customer my size and industry describing a before/after — actual hours saved, tickets reduced, or a specific workflow that changed — not just a founder pedigree and two quotes from an advisor and a CPO at a much smaller company.”
    HR Manager, Technology · 201-500 employeessimulated
    “they don't tell me the ticket volume drops by X%, or headcount on system admin goes from 6 FTEs to 2, or time-to-answer goes from days to minutes”
    Senior HR Manager, SaaS · 501-1000 employeessimulated
    “But their own first customers "go live in early 2027," so there's nothing to actually test now, and swapping the core HR system of record is about as…” Show full quote
    “But their own first customers "go live in early 2027," so there's nothing to actually test now, and swapping the core HR system of record is about as high-disruption a change as exists — payroll, benefits, comp all sit on top of it, and I'd need finance and IT sign-off, not just me.”
    VP of People Ops, Professional Services · 51-200 employeessimulated

  • The 2027 go-live puts the product outside any current buying decision

    4 of 15

    “their own timeline says first customers go live in early 2027, there are no named enterprise customers yet, just two quotes from an advisor and a CPO at…” Show full quote
    “their own timeline says first customers go live in early 2027, there are no named enterprise customers yet, just two quotes from an advisor and a CPO at LaunchDarkly”
    HR Manager, Technology · 201-500 employeessimulated
    See all 2 comments
    “"Our first customers go live in early 2027" — that's a real, checkable fact, not marketing fluff, and it tells me this isn't shipping yet”
    Senior HR Manager, SaaS · 501-1000 employeessimulated

Relevance

  • The buyer has to be inferred from the contact section and founder bios

    7 of 15

    “I had to infer from context clues like "leaders," "HR can spend less time managing systems," and the "For prospective customers" line about "if you lead people at…” Show full quote
    “I had to infer from context clues like "leaders," "HR can spend less time managing systems," and the "For prospective customers" line about "if you lead people at a growing enterprise"”
    Director of Human Resources, SaaS · 501-1000 employeessimulated
    See all 6 comments
    “it's clearly aimed at HR/People leaders at bigger companies given "growing enterprise" in the contact section and the Workday pedigree of the founders, but nowhere does it say…” Show full quote
    “it's clearly aimed at HR/People leaders at bigger companies given "growing enterprise" in the contact section and the Workday pedigree of the founders, but nowhere does it say "this is for CPOs at 500+ person companies" or similar. I had to piece that together from the founders' bios”
    Chief People Officer, Professional Services · 51-200 employeessimulated
    “Who it's for is less explicit - there's no "this is for HR leaders at 500-5000 person companies" line - I had to infer it from "growing enterprise"…” Show full quote
    “Who it's for is less explicit - there's no "this is for HR leaders at 500-5000 person companies" line - I had to infer it from "growing enterprise" in the contact section”
    Director of Human Resources, Software Development · 11-50 employeessimulated
    “That's clear enough in a five-second scan. Who it's for is less explicit — no "for VPs of People" label anywhere, but the "for prospective customers... if you…” Show full quote
    “That's clear enough in a five-second scan. Who it's for is less explicit — no "for VPs of People" label anywhere, but the "for prospective customers... if you lead people at a growing enterprise" line in the contact section confirms it's aimed at HR leaders at bigger companies”
    VP of People Ops, Professional Services · 51-200 employeessimulated
    “"For prospective customers... if you lead people at a growing enterprise" only shows up way down in the Contact section. Everything before that is written in the abstract,…” Show full quote
    “"For prospective customers... if you lead people at a growing enterprise" only shows up way down in the Contact section. Everything before that is written in the abstract, at "leaders" and "HR" and "managers" generically”
    Chief People Officer, Technology · 201-500 employeessimulated
    “audience, mostly inferred from the contact section rather than declared upfront, which is a minor knock — I'd want a line near the top like "built for CHROs…” Show full quote
    “audience, mostly inferred from the contact section rather than declared upfront, which is a minor knock — I'd want a line near the top like "built for CHROs at 500-5,000 employee companies"”
    Director of Human Resources, Professional Services · 51-200 employeessimulated

  • The problem statement lands fast and matches a real pain

    3 of 15 · what worked

    “The problem statement is right up top and easy to spot — "Work changed. Your HR system didn't."”
    Senior HR Manager, SaaS · 501-1000 employeessimulated
    See all 2 comments
    “That's clear enough in a five-second scan. Who it's for is less explicit — no "for VPs of People" label anywhere, but the "for prospective customers... if you…” Show full quote
    “That's clear enough in a five-second scan. Who it's for is less explicit — no "for VPs of People" label anywhere, but the "for prospective customers... if you lead people at a growing enterprise" line in the contact section confirms it's aimed at HR leaders at bigger companies”
    VP of People Ops, Professional Services · 51-200 employeessimulated

Clarity

  • Nobody can say what the agent actually does day-to-day

    9 of 15

    “nowhere does it say what the agent actually executes (approves a PTO request? updates comp data? resolves a policy question?)”
    Director of Human Resources, SaaS · 501-1000 employeessimulated
    See all 9 comments
    “I still don't know what it actually does day to day, what data it ingests, or how "self-maintaining" and "answers, not tickets" translate into an actual workflow.”
    VP of People Ops, Software Development · 11-50 employeessimulated
    “Those phrases sound like features but they're really just restated promises; none of them tell me what actually changes on a Tuesday when a manager needs a comp…” Show full quote
    “Those phrases sound like features but they're really just restated promises; none of them tell me what actually changes on a Tuesday when a manager needs a comp change approved or a policy question answered.”
    HR Manager, Technology · 201-500 employeessimulated
    “without telling me what actually gets automated or what breaks today that this fixes”
    Senior HR Manager, SaaS · 501-1000 employeessimulated
    “Beyond that buzzword, though, they never actually show me a workflow - "answers, not tickets" and "self-maintaining platform" sound nice but I couldn't tell you mechanically what it…” Show full quote
    “Beyond that buzzword, though, they never actually show me a workflow - "answers, not tickets" and "self-maintaining platform" sound nice but I couldn't tell you mechanically what it does day one for a manager approving a comp change or an employee looking up PTO policy.”
    Director of Human Resources, Software Development · 11-50 employeessimulated
    “Still light on what "agentic" actually does day-to-day though — no product screenshot or workflow example, so I'm going on positioning, not proof.”
    VP of People Ops, Professional Services · 51-200 employeessimulated
    “Beyond that buzzword I couldn't pin down what it actually does day-to-day; no product screenshot, no workflow example, just "answers, not tickets" and "self-maintaining platform," which tells me…” Show full quote
    “Beyond that buzzword I couldn't pin down what it actually does day-to-day; no product screenshot, no workflow example, just "answers, not tickets" and "self-maintaining platform," which tells me nothing concrete about the underlying mechanics.”
    Chief People Officer, Technology · 201-500 employeessimulated
    “they never tell me what the agent actually does day-to-day—automate open enrollment, draft policy answers, flag attrition risk?—so I couldn't describe a concrete workflow”
    HR Manager, SaaS · 501-1000 employeessimulated
    “I couldn't tell you the actual mechanism, what data it touches, or how it integrates with payroll/benefits/comp”
    Senior HR Manager, Software Development · 11-50 employeessimulated

Brand alignment

  • The page reads as an investor or recruiting pitch, not a buyer page

    2 of 15

    “They're clearly targeting enterprise-ish People leaders eventually, but right now they're really selling to two audiences: prospective enterprise customers who'll wait years for something real, and engineers/investors who…” Show full quote
    “They're clearly targeting enterprise-ish People leaders eventually, but right now they're really selling to two audiences: prospective enterprise customers who'll wait years for something real, and engineers/investors who want to join or fund the story. The tone is polished, confident, and design-forward (the repeated stylized headlines, the founder bios with LinkedIn links) which tells me this was written to impress a boardroom or a recruiting candidate as much as an HR buyer”
    Director of Human Resources, Professional Services · 51-200 employeessimulated
    See all 2 comments
    “"Our first customers go live in early 2027" — that's a real, checkable fact, not marketing fluff, and it tells me this isn't shipping yet”
    Senior HR Manager, SaaS · 501-1000 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.

Director of Human ResourcesSaaS · 501-1000 employeesUS
VP of People OpsSoftware Development · 11-50 employeesUS
Chief People OfficerProfessional Services · 51-200 employeesUS
HR ManagerTechnology · 201-500 employeesUS
Senior HR ManagerSaaS · 501-1000 employeesUS
Director of Human ResourcesSoftware Development · 11-50 employeesUS
VP of People OpsProfessional Services · 51-200 employeesUS
Chief People OfficerTechnology · 201-500 employeesUS
HR ManagerSaaS · 501-1000 employeesUS
Senior HR ManagerSoftware Development · 11-50 employeesUS
Director of Human ResourcesProfessional Services · 51-200 employeesUS
VP of People OpsTechnology · 201-500 employeesUS
Chief People OfficerSaaS · 501-1000 employeesUS
HR ManagerSoftware Development · 11-50 employeesUS
Senior HR ManagerProfessional Services · 51-200 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, all with reservations
  • Relevance: 12 of 15, all with reservations
  • Value: 7 of 15, all with reservations
  • Differentiation: 1 of 15, 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. 1.Extend the Builders paragraph with what the founders decided to build differently.
  2. 2.Add a section under Our Product showing product screens or a short workflow walkthrough.
  3. 3.Replace "Run at the pace of human ambition" headline with what Sol does.

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.

Test with humans
Trusted by
HubSpotRingCentralShopifyCognismPaddleVeeamRipplingMiro
RetentionThis report is kept for 60 days, until 8 Nov 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.