# Message test — https://fusionauth.io/ After reading your page, 12 of 15 personas would take a meeting to learn more. - **Page tested:** https://fusionauth.io/ - **Audience tested against:** Mid-market CTOs and VPs of Engineering building customer facing applications - B2C, B2B2C - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/authentication-user-management-software-fusion-IenWsWY > 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 | 97% | 13 without hesitation, 2 with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 13/15 | 75% | 3 without hesitation, 10 with reservations | | 3. Value | Do they actually want it? | 12/15 | 67% | all with reservations | | 4. Differentiation | Is there a reason to pick you over the alternatives? | 12/15 | 67% | all with reservations | **Brand alignment** (a side metric, not one of the four layers) — 15/15, 78% 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. ### Value **Add a pricing section with tiers and a starting number.** "Predictable Pricing — scale users, regions, and workloads with no surprises" is the page's core argument, and nothing on the page shows a price, tier, or unit of billing. Show the model and a starting figure, or link straight to it. *effort medium · impact high · tested against Specifics beat superlatives* **Quantify the cost claim with before/after numbers.** "No unpredictable pricing" and "Increase revenue" carry no figures. Replace one with a named customer's before/after: prior IdP bill, FusionAuth bill, engineering hours saved. *effort medium · impact high · tested against Proof next to the claim* **Place a proof point beside each of the four outcome claims.** "Ship faster", "Scale confidently", "Increase revenue", "Reduce risk" sit alone with a subordinate clause each. Attach a customer name, a number, or a timeframe to at least two so the outcomes stop reading as aspiration. *effort medium · impact medium · tested against Tie the feature to the outcome* ### Differentiation **Promote 'no forced upgrades' and unlimited IdPs into the hero area.** The two claims readers repeat back sit far down the page in a bullet list and a testimonial. Move "No forced SaaS upgrades" and "add as many Identity Providers as you want at no extra cost" up next to the value props. *effort low · impact high · tested against Give a reason to choose you* **Lead 'Deploy Anywhere' with self-hosted, not the abstract label.** Self-hosted, on-prem and air-gapped deployment is the concrete separator from Auth0, but the heading buries it behind a generic phrase. Rewrite the heading around running identity on your own infrastructure. *effort low · impact medium · tested against Front-load the meaning* ### Relevance **Name the buyer and their current stack near the top.** "Built for Teams Running Critical Systems" is too vague to point at; the Auth0/Okta-at-scale buyer only surfaces in testimonials at the bottom. Say who this is for — engineering teams outgrowing their current identity provider's pricing. *effort low · impact high · tested against Name the audience* **Address migration effort from an incumbent provider.** The page pitches replacing an existing identity provider but never says what the switch costs in engineering time or how user data moves across. Add a migration line with a concrete timeframe or tooling reference. *effort medium · impact medium · tested against Answer the live objection* ### Clarity **State what FusionAuth is in the H1, and define CIAM.** "Identity, Your Way" is a slogan; readers scroll past mission copy and undefined "CIAM" before learning the product is customer authentication software you can self-host. Put the category and the plain-English definition in the first two lines. *effort low · impact high · tested against Lead with the use case* --- ## 03 · What is working ### 'No forced upgrades' and no-extra-cost-per-IdP pricing are repeated back as memorable Five respondents cited these two specific claims unprompted as concrete differentiators against Auth0 and Cognito, including the Com Laude proof point. > The line "no forced SaaS upgrades, no shared infrastructure blast radius, no unpredictable pricing" is the thing that would actually move it up my shortlist — it's specific enough to be a real differentiator against Auth0-style vendors > > — Chief Technology Officer, Software as a Service, 201-500 > The line that would actually move me toward this one is the no-extra-cost-per-IdP claim in the Com Laude quote — "you can keep adding as many Identity Providers as you want at no extra cost" — because that's a concrete, checkable pricing mechanic, not fluff > > — VP of Engineering, Consumer Technology, 1001-5000 > "No forced SaaS upgrades, no shared infrastructure blast radius" — that's the line that'd pull me in vs Cognito > > — Vice President of Engineering, Digital Services, 5000+ > that's a concrete, checkable pricing behaviour, not just "predictable pricing" marketing fluff, and per-IdP fees are exactly where Auth0/Okta bleed you at our scale. > > — Head of Engineering, Mobile Applications, 501-1000 ### Self-hosting and deployment options are read as the real differentiator Several respondents named self-hosted deployment and the 'Deploy Anywhere' framing as the concrete thing that separates this from Auth0, and connected it to vendor lock-in and AWS cost pressure. > Avoid Cognito lock-in, self-host if AWS costs bite > > — Vice President of Engineering, Digital Services, 5000+ > the hero line "Identity, Your Way" plus the subhead about securing "humans, services, and AI across any environment" gave me the category and angle within a few seconds, and "Deploy Anywhere... self-hosted, dedicated, on-prem, hybrid, or air-gapped" told me the problem is vendor lock-in / control over deployment, which is exactly my own pain point. > > — CTO, Digital Services, 5000+ ### The Auth0-alternative positioning lands clearly Six respondents identified the brand as an alternative for Auth0/Okta customers hitting pricing walls at scale, and read the hero and value props as aimed at engineering and compliance-conscious buyers within seconds. > selling to engineering teams at enterprises replacing Auth0/Okta > > — Vice President of Engineering, Mobile Applications, 501-1000 > the hero line "Identity, Your Way" plus "secures access for humans, services, and AI across any environment" told me it's identity/auth infrastructure within a couple seconds, and "API-Driven by Design... built to integrate into your product" made clear it's for engineering teams > > — Senior VP of Engineering, Software as a Service, 201-500 > It's a customer identity and access management (CIAM) platform — basically login, authentication, and authorization infrastructure (SSO, MFA, user management) that you build into your own product via API > > — Senior VP of Engineering, Software as a Service, 201-500 > it's clearly devs/CTOs migrating off something like Auth0, given the pricing complaints in the testimonials ("Auth0's pricing was outrageous") > > — Chief Technology Officer, Consumer Technology, 1001-5000 > The tell for me was the customer quotes comparing it directly to Auth0 on pricing and IdP fees — that's the category, full stop. > > — Senior VP of Engineering, Consumer Technology, 1001-5000 --- ## 04 · What the personas said ### The product category is buried behind marketing slogans Five respondents had to scroll past mission-statement headers and vague AI positioning before finding a concrete description of what the product is; the CIAM acronym is never defined. > the sub-headers like "Identity, Your Way" and "API-Driven by Design" are the vague part, they're mission-statement filler that could apply to any dev tool > > — Chief Technology Officer, Software as a Service, 201-500 > It's phrases like "Identity, Your Way" and "API-Driven by Design" — they're marketing shorthand, not descriptions of what the product does, so I had to skip past them to the denser sentence about "humans, services, and AI across any environment" to actually get the category. > > — VP of Engineering, Consumer Technology, 1001-5000 > the term 'CIAM' itself is never spelled out on the page, and 'API-Driven by Design' plus 'fine-grained authorization' are the kind of generic phrases that could describe half a dozen dev-tools categories until you hit the 'Deploy Anywhere' section and it clicks. > > — CTO, Digital Services, 5000+ > the actual problem — vendor lock-in and pricing pain — only becomes clear once you hit "Don't Let Identity Become the Bottleneck" and the "No forced SaaS upgrades / No unpredictable pricing" bullets further down. > > — Head of Engineering, Digital Services, 5000+ ### Buyers infer the target audience from vocabulary instead of being told Three respondents said the intended buyer and their current stack are scattered across sections or implied by word choice rather than stated near the top. > The intended reader is never named outright as "VP of Engineering" or "if you use Okta" — I inferred that from cues like "Every identity capability is available via API and built to integrate into your product, pipelines, and workflows" > > — VP of Engineering, Consumer Technology, 1001-5000 > I'd want a line near the top that names my actual job and my actual pain in one breath — something like 'For engineering leaders replacing homegrown auth or escaping Auth0 pricing at scale' > > — Senior VP of Engineering, Consumer Technology, 1001-5000 ### Migration cost and switching effort are unaddressed for a page selling a rip-and-replace Two respondents noted the page pitches replacing an incumbent identity provider without addressing what migration actually costs in effort or money. > I picture a mid-size, developer-tools-focused vendor — not a scrappy two-year-old startup, but not Okta-scale either > > — Senior VP of Engineering, Software as a Service, 201-500 ### The page never shows pricing, the one thing its whole argument rests on Ten respondents flagged that predictable-pricing and cost-savings claims arrive with no pricing model, tiers, or benchmark numbers, leaving the central value proposition unverifiable and the differentiation claim uncredible. > FusionAuth wins that comparison the moment they show a migration case study with real hours/timeline for a company our size, since right now Clerk feels more concretely "shown" for devs and Auth0 has the incumbent trust > > — Chief Technology Officer, Software as a Service, 201-500 > But none of that is quantified on the page — no pricing tiers, no benchmark of "typical savings vs Auth0/Okta," no migration effort estimate — so it's a "maybe worth a scoping call" not a "worth a meeting with numbers in hand." > > — VP of Engineering, Consumer Technology, 1001-5000 > "predictable pricing" is unproven; need actual numbers vs Auth0/Cognito tiers before it beats staying put > > — Vice President of Engineering, Digital Services, 5000+ > no benchmark on migration effort, no concrete pricing tiers, no compliance certifications named (ISO 27001? SOC 2? GDPR data residency specifics?) > > — Head of Engineering, Mobile Applications, 501-1000 > I'd need one migration case study with real before/after cost and engineering-hours numbers to move this from "interesting" to "shortlist leader." > > — Senior VP of Engineering, Software as a Service, 201-500 > the page doesn't show me the pricing model or migration mechanics, so it's worth a call to get numbers and a reference customer who actually migrated off Auth0 at our scale > > — Chief Technology Officer, Consumer Technology, 1001-5000 ### Cost claims need before/after numbers and a named migration case study to be believed Respondents asked for concrete evidence: engineering hours saved, migration cost, before/after figures. Existing testimonials came from smaller companies and did not prove the case at respondents' scale or compliance requirements. > The one outcome that matters is a real number: X engineer-weeks to migrate a comparable company off homegrown auth, with zero surprise costs at renewal — if they can show me that combination of low migration cost and stable pricing over 2-3 years, that's the meeting-closer > > — Chief Technology Officer, Software as a Service, 201-500 > the testimonials are from WeRoad, Com Laude, Wonder Giant, DoubleGDP, which aren't companies at my scale or in my sector > > — Senior VP of Engineering, Software as a Service, 201-500 --- ## 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's core promise—better pricing—is the one claim it refuses to substantiate, so the whole argument collapses on inspection.** *(high)* Seven of 15 flagged predictable-pricing and cost-savings claims arriving with no model, tiers, or benchmarks; two more asked for before/after engineering hours and migration figures. The differentiation claim is left uncredible. - **Positioning against Auth0 works only until a buyer asks what switching costs, and then the page goes silent.** *(high)* Five respondents read the Auth0-alternative framing instantly, but two noted the page pitches replacing an incumbent IdP without addressing migration effort or money, and two more wanted a named migration case study. - **The page makes readers work to learn what it sells, spending its best attention window on slogans.** *(high)* Five respondents scrolled past mission-statement headers and vague AI positioning to find a concrete product description, and CIAM is never defined. Three more had to infer the intended buyer from vocabulary rather than being told. - **Every claim that lands is a specific mechanic, and every claim that fails is an abstraction — the page is weighted the wrong way.** *(medium)* Recall clusters on concrete items: no forced upgrades, no extra cost per IdP, self-hosting, Deploy Anywhere (5 and 3 respondents). The failures are all vague AI positioning, undefined CIAM, and unquantified cost claims. - **Self-hosting is doing the differentiation work the pricing message claims credit for.** *(medium)* Three respondents named self-hosted deployment as the concrete separator from Auth0, tying it to lock-in and AWS cost pressure, while seven found the pricing argument unverifiable. The page leads with the weaker asset. - **Existing social proof actively undermines the pitch at enterprise scale.** *(medium)* Two respondents said testimonials came from smaller companies and did not prove the case at their scale or compliance requirements — a problem for a page that six respondents read as aimed at compliance-conscious buyers hitting pricing walls at scale. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | Chief Technology Officer | Software as a Service | 201-500 | | 2 | CTO | Mobile Applications | 501-1000 | | 3 | VP of Engineering | Consumer Technology | 1001-5000 | | 4 | Vice President of Engineering | Digital Services | 5000+ | | 5 | Senior VP of Engineering | Software as a Service | 201-500 | | 6 | Head of Engineering | Mobile Applications | 501-1000 | | 7 | Chief Technology Officer | Consumer Technology | 1001-5000 | | 8 | CTO | Digital Services | 5000+ | | 9 | VP of Engineering | Software as a Service | 201-500 | | 10 | Vice President of Engineering | Mobile Applications | 501-1000 | | 11 | Senior VP of Engineering | Consumer Technology | 1001-5000 | | 12 | Head of Engineering | Digital Services | 5000+ | | 13 | Chief Technology Officer | Software as a Service | 201-500 | | 14 | CTO | Mobile Applications | 501-1000 | | 15 | VP of Engineering | Consumer Technology | 1001-5000 | --- ## 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-08-25, then deleted along with the personas and their answers.