# Message test — https://www.console.com/ After reading your page, only 0 of 15 personas could name a reason to pick you over a similar option. - **Page tested:** https://www.console.com/ - **Audience tested against:** IT managers and IT operations leaders at mid-market companies - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/console-ai-native-itsm-n7xcgmI > 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? | 2/14 | 29% | all with reservations | | 3. Value | Do they actually want it? | 7/15 | 48% | all with reservations | | 4. Differentiation | Is there a reason to pick you over the alternatives? | 0/15 | 22% | — | **Brand alignment** (a side metric, not one of the four layers) — 0/15, 25% strength. 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. ### Differentiation **Add a line under the H1 naming what this does that ServiceNow and Jira do not.** Automating service requests is a claim every ITSM vendor makes, leaving no reason to pick this one. State the specific edge: deployment time, price model, or the fact that governance and asset data are handled in one agent. *effort medium · impact high · tested against Give a reason to choose you* **Reduce the Palo Alto banner to one instance and state product continuity.** Six repeats of the acquisition banner push the pitch below the fold and read as a product about to be absorbed. Keep one line and say the product continues to ship and support existing customers under its own name. *effort low · impact high · tested against Answer the live objection* **Tie each capability in the subhead to a concrete outcome.** "Continuously enforce access governance" and "effortlessly manage asset and business data" list capabilities without saying what the buyer gets. Attach an outcome to each, such as audit-ready access logs with no quarterly review spreadsheet. *effort medium · impact medium · tested against Tie the feature to the outcome* ### Relevance **Name the buyer and company type in the subhead under the H1.** Nothing on the page says who it is for, so a reader has to guess from the word ITSM. Write a subhead naming the role and company profile, such as IT service leaders at mid-market manufacturers running lean help desks. *effort low · impact high · tested against Name the audience* **Replace "What an ITSM should be" with a headline naming the job buyers do.** The headline names a software category, not a task the buyer would say out loud. Lead with the work instead, such as closing password, access and asset requests without a ticket queue. *effort low · impact high · tested against Lead with the use case* **Add a problem line above the H1 describing today's ticket backlog.** The page opens with the answer and never names the pain the reader arrives with. State the problem first: service desks drowning in repeat access and asset requests that take days to clear. *effort low · impact medium · tested against Problem before solution* ### Value **Add baseline, timeframe and request types beside the "Automate 75%+" claim.** Readers cannot tell what 75% is measured against, over what period, or which request types count, so they discount it. Write the measured comparison, such as 75% of password resets and access requests resolved without a human in the first 90 days. *effort medium · impact high · tested against Specifics beat superlatives* **Place a named customer result directly under the 75% claim.** The claim stands alone with no customer, before-and-after numbers, or source. Put one named account and its ticket volume change immediately beneath it rather than in a separate logo strip. *effort medium · impact high · tested against Proof next to the claim* **Rewrite "context-aware agents" to say what the agents read and do.** The phrase is undefined, so readers cannot tell what the product actually does. Replace it with the plain action, such as agents that read your identity, asset and HR records and action requests automatically. *effort low · impact high · tested against Plain language* ### Clarity **Move "Book a demo" above the fold as the single call to action.** Repeated "Read more" links on the acquisition banner compete with the demo button and appear first. Keep one primary action visible before any other link. *effort low · impact medium · tested against One clear next action* ### Brand alignment (side metric) **Rewrite the subhead using the vocabulary of mid-market IT teams.** "Effortlessly manage asset and business data" could belong to any software company and shows no knowledge of the reader's world. Swap in the systems and requests they actually handle: shop floor devices, store laptops, contractor onboarding. *effort medium · impact high · tested against Concrete over abstract* **Replace the SVG code block under "Deployed company wide at" with readable customer names.** Customer logos render as raw path data, so the social proof section shows nothing. List the company names as text, ideally with sector and employee count. *effort low · impact high · tested against Proof next to the claim* **Add a short section heading above the capability list that reads alone.** After the banners the page jumps straight from one headline to a dense sentence, so a scanner sees no structure. Add headings that carry meaning in their first three words and tell the story without body copy. *effort medium · impact medium · tested against Headings stand alone* --- ## 03 · What the personas said ### Raw SVG code and repeated acquisition banners make the page literally unreadable Seven respondents reported unrendered SVG code appearing in body text, broken layout, and a repeated acquisition banner that blocked the main pitch. One said the page was unreadable junk; another could not read customer logos rendered as SVG paths. > The repeated 'Console joins Palo Alto Networks' banner six times in a row with no context, plus a wall of raw SVG path code dumped into the copy — literally coordinates and fill colors instead of rendered logos. > > — IT Manager, Manufacturing, 501-1000 > the rest of the page was unreadable SVG/code junk, not actual copy, so I'd have closed the tab and asked for a proper page before I'd take it to anyone internally. > > — Senior IT Manager, Retail, 1001-5000 > Literally the raw SVG path code — strings like "fill=\"rgb(27,49,57)\"" and d="M 5.904 7.143..." were sitting right in the body text > > — IT Operations Manager, Information Technology, 201-500 > The rest of the page was just a mess of SVG code and logo markup, no actual customer names or proof points I could read > > — Director of IT Operations, Financial Services, 501-1000 > the page was mostly unreadable junk — logos, SVG code, and "Console joins Palo Alto Networks" repeated six times > > — IT Operations Lead, Healthcare, 1001-5000 > the logos are rendered as raw SVG path data in what I was given, so I can't even see who they mean > > — Senior IT Manager, Information Technology, 1001-5000 > The actual content was buried under literal SVG path code and repeated "Console joins Palo Alto Networks" banners — that's what got in the way, not the ITSM claim itself, which was the one clean sentence on the page. > > — IT Manager, Retail, 501-1000 ### 'Context-aware agents' was read as undefined jargon One respondent flagged the key phrase 'context-aware agents' as undefined and unclear; another said the audience could only be inferred from jargon. > "context-aware agents" is the one phrase that sounds like a feature but it's never defined, so I couldn't tell if that means AI chatbots, automation scripts, or something else entirely. > > — Senior IT Manager, Retail, 1001-5000 ### The audience is never named — buyers had to infer who the page is for Eight respondents said no target audience, company size, sector, or pain point is stated anywhere. Several noted the persona could only be inferred from the tagline, a single statistic, or jargon. > The problem was spelled out fast in that one tagline — automating service requests, access governance, asset/business data — so I got "AI-driven ITSM/helpdesk automation" within seconds. But the intended reader is never stated > > — IT Operations Manager, Information Technology, 201-500 > "who's the reader" is never actually stated — I'm inferring it from the jargon and the "Deployed company wide at" logo wall. No persona, no named use case > > — IT Operations Lead, Healthcare, 1001-5000 > it never names a specific pain point (what's broken today, what it replaces) or names the reader directly > > — Head of IT Operations, Manufacturing, 201-500 > the intended reader is never named outright — I inferred "IT/ITSM buyer at a mid-to-large org" from the tagline and the stat, not from any explicit "this is for you if..." statement > > — Senior IT Manager, Information Technology, 1001-5000 > But it's inferred from a single tagline, not stated plainly like "this is for IT managers at mid-size companies who struggle with X." No named persona, no description of a before/after state > > — Director of IT Operations, Healthcare, 501-1000 > The problem and audience are implied rather than spelled out — I had to infer it from that one line > > — Senior IT Manager, Retail, 1001-5000 ### The 75% automation claim is not believed without mechanism, baseline, or a named customer Nine respondents rejected or suspended judgment on the automation claim because it carries no methodology, baseline, case study, or reference customer. Several said they would need before-and-after metrics from a named account to verify it. > A verified drop in open ticket volume per IT headcount — if they can show a team our size went from X tickets per analyst to 75% fewer with the same staff, that's a headcount argument I can take to my CFO; anything short of that specific number is just marketing copy. > > — IT Manager, Manufacturing, 501-1000 > "automate 75%+ of service requests" and "continuously enforce access governance" are just assertions sitting on a page full of broken SVG junk — no case study, no methodology, no "here's how we measured 75%," > > — Senior IT Manager, Retail, 1001-5000 > If "automate 75%+ of service requests" actually held up, that's real headcount/ticket-queue relief and would be worth a budget line — but it's just a number on a tagline with zero mechanism behind it > > — IT Operations Manager, Information Technology, 201-500 > that's a big "if" with zero evidence behind it: no case study, no named customer, no methodology for how they get to 75% > > — Director of IT Operations, Financial Services, 501-1000 > a number like 75% with zero methodology behind it is a claim I've heard before and been burned by, so I'd take the meeting only to make them show me the measurement > > — IT Operations Lead, Healthcare, 1001-5000 > no case study, no numbers I can sanity-check, and no sense of what it'd take to integrate with our existing systems > > — Head of IT Operations, Manufacturing, 201-500 > no idea how the "context-aware agents" actually work or what proof backs the 75% number > > — Head of IT Operations, Manufacturing, 201-500 > But it's a single unsourced number with nothing behind it, so right now it's a maybe, not a reason to act. I'd take a short meeting only to ask them to show me that 75% figure with a real customer and real before/after numbers — if they can't, I'm out. > > — IT Manager, Retail, 501-1000 > I have zero evidence behind it here: no named customer saying "we went from X to 75% deflection," no methodology > > — Senior IT Manager, Information Technology, 1001-5000 ### The Palo Alto acquisition banner reads as roadmap and survival risk Four respondents interpreted the acquisition messaging as a signal the product may be deprioritized, rebranded into a larger platform, or not survive reorganization, raising integration and roadmap concerns. > that repeated "Console joins Palo Alto Networks" banner suggests an acquisition or rebrand event, which tells me this product may have started life as something else > > — Senior IT Manager, Financial Services, 1001-5000 > it tells me this got acquired, which could mean stability and security-vendor backing, or it could mean the product gets deprioritized and folded into a bigger roadmap I don't control. > > — IT Manager, Manufacturing, 501-1000 > The "Console joins Palo Alto Networks" banner actually makes me pause rather than pick it, since an acquisition raises integration/roadmap risk I'd need answered before shortlisting it seriously > > — IT Operations Manager, Information Technology, 201-500 > a repeated acquisition banner instead of a clear pitch tells me nobody built this page to close me. > > — IT Operations Manager, Healthcare, 201-500 ### No differentiator from ServiceNow or Jira Service Management was identifiable Four respondents said the automation claim is identical to every competitor's and named ServiceNow and Jira Service Management as undifferentiated alternatives. One said competitors with documented, verifiable numbers would win the deal. > "Automate 75%+ of service requests, continuously enforce access governance, and effortlessly manage asset and business data with context-aware agents" — is the same claim every competitor in this space makes, just with their own percentage swapped in > > — Senior IT Manager, Retail, 1001-5000 > there's no comparison point, no architecture detail, no pricing signal, nothing that differentiates it from the other two on my shortlist > > — IT Operations Lead, Healthcare, 1001-5000 > whoever shows a named customer logo with a case study, a demo video, or a methodology note on how that 75% was measured wins my attention > > — Head of IT Operations, Manufacturing, 201-500 > Nothing here gives me a reason to pick it over another option — the only differentiator offered is the 75% automation number, and it's unsourced, so it's not a selling point, it's a question mark. > > — IT Manager, Retail, 501-1000 ### The tone reads as generic ITSM vendor, not written for the reader's sector Four respondents said the messaging targets a generic ITSM persona with no mid-market manufacturing or retail-specific language and no demonstrated sector understanding. > no retail-specific language or named references that would make me feel they understand my sector's problems rather than IT problems in general. > > — Senior IT Manager, Retail, 1001-5000 > As for tone — it's not really written for me, it's written at a generic ITSM buyer persona. > > — IT Manager, Information Technology, 501-1000 --- ## 04 · 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 failed before the messaging was ever tested — half the panel was reading broken output, not a pitch.** *(high)* Seven of 15 reported unrendered SVG code in body text, broken layout, and a repeated acquisition banner covering the main pitch; one called it unreadable junk and another could not identify customer logos. - **The one proof point on the page is the one thing buyers refuse to accept.** *(high)* Nine respondents rejected or suspended judgment on the 75% automation claim for lack of methodology, baseline, or named customer, and several demanded before-and-after metrics from a real account. - **An unsubstantiated number that every competitor also claims actively loses deals rather than merely failing to win them.** *(high)* Four respondents said the automation claim is identical to ServiceNow and Jira Service Management, and one stated competitors with documented, verifiable numbers would take the deal. - **Buyers are doing the page's work for it — qualifying themselves in or out on guesswork.** *(high)* Eight of 15 said no audience, company size, sector, or pain point appears anywhere, leaving persona to be inferred from a tagline, a single statistic, or jargon like 'context-aware agents'. - **The acquisition banner is net-negative: it displaces the pitch physically and undermines it commercially.** *(high)* The repeated banner blocked the main pitch for seven respondents, and four read the acquisition as a signal the product may be deprioritized, rebranded, or not survive reorganization. - **There is no category-level reason to buy — only a claim, and the claim is contested.** *(high)* Four respondents found no differentiator against ServiceNow or Jira, four saw the tone as generic ITSM with no sector-specific language, and nine disbelieved the single automation figure. --- ## 05 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | IT Manager | Manufacturing | 501-1000 | | 2 | Senior IT Manager | Retail | 1001-5000 | | 3 | IT Operations Manager | Information Technology | 201-500 | | 4 | Director of IT Operations | Financial Services | 501-1000 | | 5 | IT Operations Lead | Healthcare | 1001-5000 | | 6 | Head of IT Operations | Manufacturing | 201-500 | | 7 | IT Manager | Retail | 501-1000 | | 8 | Senior IT Manager | Information Technology | 1001-5000 | | 9 | IT Operations Manager | Financial Services | 201-500 | | 10 | Director of IT Operations | Healthcare | 501-1000 | | 11 | IT Operations Lead | Manufacturing | 1001-5000 | | 12 | Head of IT Operations | Retail | 201-500 | | 13 | IT Manager | Information Technology | 501-1000 | | 14 | Senior IT Manager | Financial Services | 1001-5000 | | 15 | IT Operations Manager | Healthcare | 201-500 | --- ## 06 · 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-10-05, then deleted along with the personas and their answers.