# Message test — https://survicate.com/pricing/ After reading your page, only 8 of 14 personas could quickly tell what problem it solves and who it is for. - **Page tested:** https://survicate.com/pricing/ - **Audience tested against:** Mid-market B2C Digital product companies, that have outgrown from google forms, typeform or are to small for qualtrics. - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/pricing-survicate-JG0TflA > 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 | 99% | 14 without hesitation, 1 with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 8/14 | 54% | all with reservations | | 3. Value | Do they actually want it? | 14/15 | 74% | all with reservations | | 4. Differentiation | Is there a reason to pick you over the alternatives? | 10/15 | 61% | all with reservations | **Brand alignment** (a side metric, not one of the four layers) — 11/15, 63% strength (all with reservations). Does the page read like the company you actually are? **Fix first: Relevance.** 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. ### Relevance **Move the value proposition above the three plan cards.** What the product does surfaces only in the testimonials and the feature table, below the pricing. Put one sentence naming multichannel surveys plus AI theme clustering before the first price. *effort medium · impact high · tested against Front-load the meaning* **Add a problem-first line above the pricing tables.** The page opens with 'Pricing loved for value, trusted for scale' — a claim about pricing, not the reader's problem. State the job first: collecting feedback across web, email and in-app, and turning open-text answers into themes. *effort low · impact high · tested against Problem before solution* **Name the audience in the headline, not the logo wall.** Readers had to infer who this is for from badges and testimonials. Move 'CX, Product, Research and Marketing teams' into the top headline so a research lead can point at it. *effort low · impact high · tested against Name the audience* ### Differentiation **Replace 'Custom' response and data point cells with ranges.** Pro and Enterprise show 'Custom yearly pool of responses' and 'Custom data points limit' in every cell, so no one can budget. Give starting volumes and the overage rate per response. *effort medium · impact high · tested against Specifics beat superlatives* **State the reason to choose Survicate above the plans.** Nothing on the page separates this from a cheaper form builder with an analysis layer. Lead with the AI clustering of open-text responses — the capability readers named as the reason to switch. *effort medium · impact high · tested against Give a reason to choose you* **Define 'data points' where the number first appears.** '1,000 data points /mo' is a billing metric no first-time reader can price. Add a parenthetical saying what consumes one. *effort low · impact high · tested against Plain language* ### Value **Attach a number to the time-savings claims outside testimonials.** 'Give Survicate a test drive' and the feature bullets promise savings the testimonials alone substantiate. Put the clustering result — 2,000+ responses sorted into themes in a day and a half — next to the claim it proves. *effort low · impact medium · tested against Proof next to the claim* ### Clarity **Explain MCP in the banner instead of abbreviating it.** 'Introducing Survicate MCP: customer feedback, everywhere you work' asks readers to decode an abbreviation in the first line on the page. Say what it connects to in plain words. *effort low · impact medium · tested against Plain language* ### Brand alignment (side metric) **Surface the enterprise trust features out of the bullet lists.** 'SAML SSO, access logs', 'Custom ToS, DPA, and NDA' and 'On-demand security Q&A' sit buried at the bottom of identical bullet stacks, so the page reads as self-serve SMB. Give security and legal terms their own labelled row. *effort medium · impact medium · tested against Answer the live objection* --- ## 03 · What is working ### AI clustering of open-text responses is the capability respondents named as… Five points identify AI clustering of messy text into themes, alongside multichannel consolidation and CRM targeting, as solving real operational constraints of basic forms. Two framed it as the reason to save manual analysis time. > real multichannel distribution (in-app, mobile SDK, pop-ups) plus CRM-attribute targeting and the AI categorization actually cutting the manual tagging work my team does now. That's a real operational gain, not a nice-to-have. > > — Customer Experience Director, Fintech, 201-500 > Cutting the time from "collect 2,000 open-text responses" to "have a themed, actionable summary" from days down to under an hour, reliably — if the Research Hub can do that on my own messy data, not just Wellhub's, that's the whole pitch justified. > > — Product Manager, SaaS, 51-200 > we'd consolidate survey collection across email, in-app, mobile and web into one system with the Research Hub doing the clustering/analysis we currently do manually after exporting Typeform data — that's real time saved for my team > > — Senior Product Manager, E-commerce, 201-500 > Watching the AI actually cluster a batch of our own messy NPS/CSAT free-text responses into sensible themes with no manual cleanup - if that works on our data, not just their demo data, it's worth the switch. > > — Customer Experience Manager, Fintech, 51-200 ### The Wellhub quote naming the clustering mechanism and response volume is the strongest… Three points single out the Wellhub testimonial for showing a concrete before/after on AI categorization, and one calls the Trustpilot 4.2-to-4.8 jump credible because it is specific. Two noted customer quotes conveyed the use case better than the header copy. > the page gives me three named customers (Intergiro, Wellhub, Kard) with decent specifics like the Trustpilot jump from 4.2 to 4.8, which is the kind of proof that makes me pay attention rather than skim past. > > — Research Lead, Digital Products, 501-1000 > The customer quotes actually did more work than the header copy - Bruna Maia's line about clustering 2,000 responses into themes and the Trustpilot rating jump from 4.2 to 4.8 told me more about the use case than the "Introducing Survicate MCP" banner did. > > — Customer Experience Manager, Fintech, 51-200 > The Wellhub quote about clustering 2,000+ responses into clear themes is the closest thing to a concrete before/after on the page. > > — Director of Product, Media & Publishing, 501-1000 ### The feature spec table gives buyers something concrete to compare One point credits the feature spec table with enabling comparison against competitors on capabilities; another characterised the product plainly as a beefed-up Google Forms with multichannel distribution and an analysis layer. > things like "Advanced Display Logic," "AI Follow-up Questions," "Answer Piping," and the integration count (25+ vs 44+) are specific enough that I could check them against a competitor's spec sheet. > > — Customer Experience Director, Fintech, 201-500 > It's a customer feedback / survey platform — basically a beefed-up Google Forms with multichannel distribution (email, web pop-ups, in-app, mobile SDK) plus some analysis layer on top > > — Director of Product, Media & Publishing, 501-1000 --- ## 04 · What the personas said ### Core product terms — 'Research Hub', 'Research Assistant', 'data points', 'MCP' — go… Six points flag jargon used before it is explained, including the banner copy's unexplained MCP abbreviation and a headline called vague. Respondents wanted plain-English definitions, especially for the pricing unit. > Mostly it's the jargon soup at the top — "Research Hub," "Research Assistant," "data points" — none of which are defined before you hit them, so you're guessing at what's a feature vs. a pricing unit vs. a module name. > > — Product Manager, SaaS, 51-200 > The opening banner "Introducing Survicate MCP: customer feedback, everywhere you work" is jargon-first with no explanation of what MCP even is > > — Customer Experience Manager, Fintech, 51-200 > terms like "Research Hub," "data points," and "Research Assistant" are unexplained jargon I had to guess the meaning of rather than being told plainly what they do. > > — Senior Product Manager, Media & Publishing, 201-500 > "data points" vs "survey responses" as two separate pricing units is never actually defined anywhere I read. Those two units sitting side by side on the pricing cards without a plain-English distinction is what actually slowed me down. > > — Customer Experience Director, SaaS, 201-500 ### The problem the product solves is never stated — it has to be inferred Ten points report the problem statement is implied, scattered, or absent, and that the target audience is inferred only from the logo wall, badges, and testimonials rather than stated. Two noted the value proposition sits below the pricing tables. > There's no single sentence stating the problem - it's split across the hero line, feature bullets, and plan tables, so I had to stitch together "multichannel surveys" plus "Data In/Out" plus "Research Hub" myself rather than being told it directly. > > — Research Lead, Digital Products, 501-1000 > The "customer feedback, everywhere you work" line and "4,000+ CX, Product, Research and Marketing teams trust us" told me who this is for pretty fast - it's the same functional buyers as us. But the actual problem being solved is inferred from the feature list > > — Research Lead, Digital Products, 501-1000 > the tagline "Customer Feedback Platform. Survey and listen to your customers across every channel" at the bottom tells you what it is, but that's buried after all the pricing and comparison tables, not up top. > > — Product Manager, SaaS, 51-200 > the closest thing to "who's it for" is the logo line "4,000+ CX, Product, Research and Marketing teams trust us" > > — Product Manager, E-commerce, 51-200 > the intended reader is never actually named — I had to infer "CX, Product, Research and Marketing teams" from a small trust-badge line buried near the top logos, not from any headline or subhead that says "built for X." > > — Customer Experience Director, SaaS, 201-500 > The "who's it for" part is inferred, not stated — the testimonials from a "Product Lead," "UX Research Lead," and "CRM Manager" tell me it's aimed at CX/Product/Research/Marketing people > > — Product Manager, Media & Publishing, 51-200 > Problem's implied, not stated — I had to infer it from the feature list and testimonials rather than any single line telling me "here's the problem we solve." > > — Director of Product, Media & Publishing, 501-1000 ### 'Custom' pricing cells and undefined usage units make the pricing page unusable for… Eight points cite endless Custom cells on Pro and Enterprise, no per-unit overage or response ceiling, undefined 'data points' as a billing metric, and integrations gated behind tiers without numbers. Several called this budgeting risk and opacity versus… > the pricing tiers are a mess of "Custom" and "starts at" with no real number for Pro or Enterprise, and I can't tell from the comparison table what actually happens to my existing Typeform workflows during migration - there's no mention of import/migration support anywhere on the page > > — Research Lead, Digital Products, 501-1000 > if a competitor prices in plain "responses" and this one makes me guess what I'm actually buying, that opacity alone could knock it off the shortlist. > > — Product Manager, SaaS, 51-200 > the comparison table listing "44+ All" integrations for Pro versus "25+" for Growth with no explanation of which specific ones move (e.g. Salesforce, Amplitude are locked behind Pro) would make me pause and check pricing carefully before shortlisting it seriously, since Typeform doesn't gate integrations that opaquely > > — Senior Product Manager, E-commerce, 201-500 > the pricing tiers gate half those integrations behind Pro/Enterprise with "Custom" pricing and no numbers — if Salesforce and Amplitude are Pro-only and Pro is "book a call" pricing, I can't compare it against a competitor's sheet > > — Director of Product, Media & Publishing, 501-1000 > the fine print in the comparison table - things like "1 dashboard" on Growth or "3 chats" for the AI Research Assistant feel stingy and vague on what a "chat" or a "data point" actually buys you, and the FAQ literally lists "How do you count datapoints?" as an open question > > — Customer Experience Manager, Fintech, 51-200 > Growth caps at 1,500 responses/mo before overage, and anything past that is "custom" behind a "Book a Call" wall — that's a red flag for predictable budgeting, and I've been burned by "custom" pricing turning into a negotiation tax before. > > — Customer Experience Director, Digital Products, 201-500 ### The page reads as self-serve SMB SaaS, not enterprise-ready Two points place the brand as mid-market SaaS still scaling up-market, lacking enterprise sales confidence signals. > The tone is written more for a mid-market ops/product manager than for someone at my level - lots of feature-listing and self-serve trial framing ("no card required," "10-day trial") which reads more startup-PLG than enterprise-sales. For a director signing off on integration risk, I'd want less "start free trial" and more "here's your dedicated CSM and here's who else at your scale uses this" > > — Research Lead, E-commerce, 501-1000 ### Benefit claims outside the testimonials carry no quantified proof Points note no case studies or numbers behind claims like time savings, and testimonials lacking sourcing or methodology. Three said the AI clustering claim only holds if proven on real messy data before they would trust a migration. > the page gives me zero proof points, no case study with numbers on time saved or response-rate lift, just testimonials like "twice as fast" with no baseline. > > — Customer Experience Director, Fintech, 201-500 > if a competitor's page has a named case study with a verifiable before/after number, that wins over this one by default, because right now Survicate is asking me to trust a quote with no company link or methodology behind it. > > — Customer Experience Director, Fintech, 201-500 > I'd want to see how the AI categorization actually performs on messy open-text data before I trust it > > — Senior Product Manager, E-commerce, 201-500 > If it worked exactly as promised, I'd get multichannel collection plus the AI clustering (the Wellhub quote about 2,000 responses sorted into themes in a day and a half) instead of manually tagging Google Forms exports myself — that's real time saved, if true. > > — Customer Experience Director, Digital Products, 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. - **Testimonials are doing the page's explanatory job, which means the copy the company wrote fails and the copy customers wrote succeeds.** *(high)* Six respondents say the audience is inferred from logos, badges and testimonials, and two state customer quotes conveyed the use case better than the header copy; the Wellhub quote is named the strongest asset by four. - **Pricing actively blocks the purchase decision rather than supporting it.** *(high)* Eight respondents cite endless Custom cells, no overage or ceiling numbers, and integrations gated without figures, calling it budgeting risk; two also note the value proposition sits below the pricing tables. - **The billing metric is undefined twice over — respondents can neither price it nor understand it.** *(high)* 'Data points' appears as unexplained jargon respondents wanted defined in plain English and simultaneously as an undefined billing metric behind Custom cells, compounding opacity into a single unpriceable unit. - **The one capability respondents value is the one they refuse to believe.** *(high)* Four name AI clustering of messy text as the differentiating capability, yet three say that same claim only holds if proven on real messy data before they would migrate, and benefit claims outside testimonials carry no numbers. - **A reader must reverse-engineer the product from evidence artefacts before any message lands.** *(high)* Six report the problem statement is implied, scattered or absent, and four flag core terms — Research Hub, Research Assistant, MCP — used before explanation, with the headline called vague. - **The page positions itself against Google Forms, not against enterprise buyers' alternatives.** *(medium)* The clearest plain description offered was 'a beefed-up Google Forms', and two respondents read the brand as self-serve SMB SaaS lacking enterprise sales confidence signals — consistent with pricing that hides every enterprise number. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | Customer Experience Director | Fintech | 201-500 | | 2 | Research Lead | Digital Products | 501-1000 | | 3 | Product Manager | SaaS | 51-200 | | 4 | Senior Product Manager | E-commerce | 201-500 | | 5 | Director of Product | Media & Publishing | 501-1000 | | 6 | Customer Experience Manager | Fintech | 51-200 | | 7 | Customer Experience Director | Digital Products | 201-500 | | 8 | Research Lead | SaaS | 501-1000 | | 9 | Product Manager | E-commerce | 51-200 | | 10 | Senior Product Manager | Media & Publishing | 201-500 | | 11 | Director of Product | Fintech | 501-1000 | | 12 | Customer Experience Manager | Digital Products | 51-200 | | 13 | Customer Experience Director | SaaS | 201-500 | | 14 | Research Lead | E-commerce | 501-1000 | | 15 | Product Manager | Media & Publishing | 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-02, then deleted along with the personas and their answers.