# Message test — https://www.meetsol.com/ After reading your page, only 1 of 15 personas could name a reason to pick you over a similar option. - **Page tested:** https://www.meetsol.com/ - **Audience tested against:** SMB, tech, US based, growing - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/sol-GHR1q6w > These answers are generated by AI, scored on Wynter's B2B Message > Layers framework using behaviorally-diverse simulated personas. The > methodology is real and the critique is directional. What a simulated > persona cannot have is a live budget, a renewal coming up, or a boss > asking about this quarter. --- ## 01 · The scores Every persona answered all four questions. These are four independent proportions of the same panel, not stages of a funnel. | Layer | Question | Cleared the bar | Strength | Of those who passed | | --- | --- | --- | --- | --- | | 1. Clarity | Do they understand what you do? | 15/15 | 52% | all with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 12/15 | 67% | all with reservations | | 3. Value | Do they actually want it? | 7/15 | 47% | all with reservations | | 4. Differentiation | Is there a reason to pick you over the alternatives? | 1/15 | 27% | with reservations | **Brand alignment** (a side metric, not one of the four layers) — 8/15, 52% strength (all with reservations). Does the page read like the company you actually are? **Fix first: Value.** Earliest failing layer, walking the sequence in order — not simply the lowest score. --- ## 02 · What to change, layer by layer Ordered worst-first. Specific edits, not a restatement of the score. ### Differentiation **Extend the Builders paragraph with what the founders decided to build differently.** 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. *effort medium · impact high · tested against Give a reason to choose you* **Rewrite "Agentic by design" to state what Sol does that a bolted-on HRIS assistant cannot.** "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. *effort medium · impact high · tested against Specifics beat superlatives* **Add a line under the hero naming the migration path off an existing HRIS.** "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. *effort medium · impact high · tested against Answer the live objection* ### Value **Add a section under Our Product showing product screens or a short workflow walkthrough.** 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. *effort high · impact high · tested against Show the product early* **Replace "A self-maintaining platform" body copy with a named task Sol completes end to end.** "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. *effort medium · impact high · tested against Tie the feature to the outcome* **Add availability and design-partner terms beside the "Sign up for early access" button.** 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. *effort low · impact high · tested against Answer the live objection* ### Relevance **Add a line under the hero naming the buyer role and company size Sol fits.** 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. *effort low · impact high · tested against Name the audience* ### Clarity **Replace "Run at the pace of human ambition" headline with what Sol does.** 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. *effort low · impact medium · tested against Lead with the use case* ### Brand alignment (side metric) **Move investor and advisor logos below the fold, out of the primary Team section.** 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. *effort low · impact medium* **Add a data handling and security line under the product section.** 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. *effort low · impact medium · tested against Answer the live objection* --- ## 03 · What is working ### The problem statement lands fast and matches a real pain Three respondents said the problem is clearly identified in the first seconds and recognized it as their own frustration with current HRIS systems. This was the page's most consistent success. > The problem statement is right up top and easy to spot — "Work changed. Your HR system didn't." > > — Senior HR Manager, SaaS, 501-1000 > 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 ### Workday founder pedigree is the one differentiator respondents could name — and the only… Eight respondents identified the founders' Workday leadership as concrete, checkable differentiation. All eight also said it is insufficient on its own against incumbents with live products and reference customers. > 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 > 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 > 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 > 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 > 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 > 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 --- ## 04 · What the personas said ### Nobody can say what the agent actually does day-to-day Ten respondents said the agentic and self-maintaining claims are asserted but never operationalized — no workflow examples, screenshots, or task-level outcomes. Several called the language buzzwords and slogans, and two could not tell how data is handled. > 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 > 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 > 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 > without telling me what actually gets automated or what breaks today that this fixes > > — Senior HR Manager, SaaS, 501-1000 > 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 > 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 > 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 > 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 > 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 ### The buyer has to be inferred from the contact section and founder bios Six respondents said the target audience is never stated upfront and had to be reconstructed from bios, contact details, or scattered signals. One respondent also judged the described pain point as aimed at far larger enterprises than their own. > 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 > 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 > 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 > 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 > "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 > 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 ### Every outcome claim is unproven — no customers, demo, or numbers Nine respondents flagged the absence of reference customers, working demo, case studies, or quantified before-and-after metrics. One noted a system-of-record swap needs finance and IT sign-off, which the page gives them nothing to bring. > without telling me what actually gets automated or what breaks today that this fixes > > — Senior HR Manager, SaaS, 501-1000 > 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 > 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 > 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 > 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 > 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 > 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 > 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 ### The 2027 go-live puts the product outside any current buying decision Four respondents read the timeline and early-stage status as execution risk that blocks immediate purchase, with one saying it eliminates fit for smaller companies. Two framed the page as a pre-launch design-partner ask rather than a purchase. > 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 > "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 ### The page reads as an investor or recruiting pitch, not a buyer page Two respondents said the positioning signals a pre-launch startup courting investors, recruits, or design partners rather than addressing a ready buyer. > 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 > "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 --- ## 05 · The hardest read An adversarial pass over the findings. Every claim below was checked against the panel's own answers; unsupported ones were dropped. - **The page sells a category, not a product — the core claim collapses the moment anyone asks what the software does.** *(high)* 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. - **The only recognized strength is a founder credential, which means the page is selling people rather than software.** *(high)* 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. - **There is nothing a champion can carry into an internal approval, so even convinced readers stall.** *(high)* 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. - **The page disqualifies itself from the current buying cycle and never says who should keep reading.** *(high)* 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. - **The single moment that works — the problem statement — is squandered because nothing after it pays off.** *(medium)* 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. - **The page is written for the wrong audience entirely and will be read as fundraising collateral.** *(medium)* 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. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | Director of Human Resources | SaaS | 501-1000 | | 2 | VP of People Ops | Software Development | 11-50 | | 3 | Chief People Officer | Professional Services | 51-200 | | 4 | HR Manager | Technology | 201-500 | | 5 | Senior HR Manager | SaaS | 501-1000 | | 6 | Director of Human Resources | Software Development | 11-50 | | 7 | VP of People Ops | Professional Services | 51-200 | | 8 | Chief People Officer | Technology | 201-500 | | 9 | HR Manager | SaaS | 501-1000 | | 10 | Senior HR Manager | Software Development | 11-50 | | 11 | Director of Human Resources | Professional Services | 51-200 | | 12 | VP of People Ops | Technology | 201-500 | | 13 | Chief People Officer | SaaS | 501-1000 | | 14 | HR Manager | Software Development | 11-50 | | 15 | Senior HR Manager | Professional Services | 51-200 | --- ## 07 · Before you act on this The methodology is real, and the critique is directional. What a simulated persona cannot have is a live budget, a renewal coming up, or a boss asking about this quarter. **Validate anything you're betting on with real ICPs who are actually in-market.** Being wrong is more expensive than you think. Finding out is cheaper than you'd guess. Wynter runs message testing with verified B2B professionals — trusted by HubSpot, RingCentral, Shopify, Cognism, Paddle, Veeam, Rippling and Miro. This report is kept for 60 days from 2026-09-09, then deleted along with the personas and their answers.