# Message test — https://www.shrinkmystack.com/ After reading your page, only 3 of 15 personas could name a reason to pick you over a similar option. - **Page tested:** https://www.shrinkmystack.com/ - **Audience tested against:** Mid market CFOs and Finance leads - **Personas:** 15 simulated - **Report:** https://grader.wynter.com/r/shrinkmystack-the-system-of-record-and-agent-f-OULmBZQ > 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 | 78% | all with reservations | | 2. Relevance | Can they tell what it solves, and who it's for? | 15/15 | 88% | 7 without hesitation, 8 with reservations | | 3. Value | Do they actually want it? | 8/15 | 52% | all with reservations | | 4. Differentiation | Is there a reason to pick you over the alternatives? | 3/15 | 33% | all with reservations | **Brand alignment** (a side metric, not one of the four layers) — 11/15, 64% 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 **Add a section contrasting the record with tools finance already owns.** ServiceNow is mentioned once and never positioned, and readers whose contract and renewal data already sits in procurement suites have to guess at the overlap. Add a short section stating what this does that a procurement or ITSM record does not: reads the real terms out of the contract document, sizes capability-level overlap between tools, and labels every figure by evidence rather than accepting declared numbers. State the boundary in terms of what it adds, not what competitors lack. *effort medium · impact high · tested against Give a reason to choose you* **Promote 'verified vs. declared' into the hero headline.** The verified-versus-declared labelling is the one thing readers repeat back as the reason to pick this over dashboards, consultant decks and spreadsheets — yet it is buried mid-paragraph as 'Every figure is labeled by how well we can prove it.' Replace or extend the H1 'The system of record and agent for your SaaS stack' so verified-versus-declared is in the first few words, and make it a named, repeatable label rather than a sentence a scanning reader will skim past. *effort low · impact high · tested against Front-load the meaning* **Rewrite 'Record plus agent' nav labels to say what they do.** The section labels — 'Record plus agent', 'Start with the number', 'Where this goes' — read as internal shorthand and give a scanning reader no reason to prefer this page to any other SaaS management page. Rewrite each so the heading alone carries the distinguishing idea: contracts read and labelled by evidence, overlap sized in dollars, renewals dated from first upload. Headings are where differentiation is either made or lost. *effort low · impact medium · tested against Headings stand alone* ### Value **Add one named customer result beside the overlap claim.** Nothing on the page carries a customer name, reference or before/after figure, so 'tool overlap sized in dollars' and 'unused seats and dead tools surface on their own' rest entirely on assertion. Put a single specific proof point directly next to the overlap claim in 'Where do we overlap?' — a named company or, failing that, an anonymised but concrete result with sector, stack size and dollars of overlap found. Proof placed at the claim does more than a logo strip further down. *effort high · impact high · tested against Proof next to the claim* **Move roadmap caveats into one dated availability line.** The page repeats in-development flags inline — 'Claude is the first connector and is not switched on in production yet', 'names what it still needs' — so the reader assembles a picture of half a product from scattered admissions. Consolidate this into a single short 'What is live today' line under the product section: contracts, terms, renewal dates, overlap sizing and spend are live on first upload; usage connectors and identity data arrive on a stated date. Naming what works today, in one… *effort medium · impact high · tested against Answer the live objection* **Replace savings claims with an audit output the reader can check.** Because so much is flagged as forthcoming, any number on the page reads as projection. Instead of asserting savings, state exactly what the free audit returns from what already works: number of tools found, dollars of overlap sized, contracts read, renewals in the next 90 days. 'Start the free audit' should be followed by a line naming the deliverable and the timeframe already claimed elsewhere — about ten minutes from a contract set and a finance sheet — so value is verifiable rather than… *effort medium · impact high · tested against Specifics beat superlatives* ### Brand alignment (side metric) **Define 'agent' where it first appears.** 'The system of record and agent for your SaaS stack' asks the reader to carry an undefined term through the whole page, and it is unclear whether they are buying one system or three bundled components. Add a clause at first use saying plainly what the agent does — answers questions about your stack on demand from the record — and make the product section state that the record and the agent are one product, not modules. *effort low · impact medium · tested against Plain language* --- ## 03 · What is working ### The problem and audience land within the first screen Seven respondents said the page states the problem and who it is for immediately, with no inference required, several citing the hero line and CTAs as signalling a finance/ops rather than IT audience. This was the most consistent positive reaction and it happened fast — within about ten seconds of reading. > the hero line "One living record of every tool you pay for" plus "Upload your contracts and a finance sheet... you have a living record of every tool you pay for — what you own, what you pay, who owns it, and when it renews" tells me exactly what it does and it's aimed squarely at finance/procurement/IT teams managing SaaS spend, which is me. I didn't have to hunt > > — Finance Manager, Financial Services, 1001-5000 > the subhead "The system of record and agent for your SaaS stack" plus "One living record of every tool you pay for" told me the problem (sprawl, unowned renewals, unmonitored AI spend) within the first screen > > — Finance Lead, Professional Services, 201-500 > It was obvious within the first screen — "the system of record and agent for your SaaS stack" plus "One living record of every tool you pay for" tells you exactly what it does before you even scroll. > > — Finance Manager, Financial Services, 201-500 ### 'Verified vs. declared' is the one line respondents could repeat back as a differentiator Six respondents independently named the verified-versus-declared labelling on usage numbers as the thing that sets the product apart, contrasting it with dashboards, consultant decks, spreadsheets and competitors showing unvalidated savings. One tied it directly to replacing outdated spreadsheets in renewal negotiations. This is the only differentiation claim that landed. > The one thing that would actually pull me toward this one is the "verified vs declared" labeling on every number - "we never show you a wrong one" is a real point of difference from a generic spend dashboard > > — Director of Finance, Technology, 501-1000 > the "labeled by how well we can prove it" framing — verified vs. declared, and the line "when we can't back a number, we say so — we never show you a wrong one." That's a concrete, checkable claim about data integrity that a spend dashboard or a generic consultant deck doesn't usually make > > — Finance Manager, Financial Services, 1001-5000 > The thing that would actually pull me toward this one is the "verified vs. declared" labelling and the explicit line "we never show you a wrong one" — most competitors just show a blended savings number > > — Finance Lead, Professional Services, 201-500 > The thing that would make me pick it is the "verified vs. declared" labeling on every dollar figure — "we never show you a wrong number" plus the caveat that missing contracts stay blank instead of guessed > > — Chief Financial Officer, Healthcare, 501-1000 > Every figure is labeled by how well we can prove it. When we can't back a number, we say so — we never show you a wrong one. > > — VP of Finance, Manufacturing, 1001-5000 > the real change is Okta plus the AI usage connectors turning "declared" seat counts into actual observed usage — that's the number I'd take to a renewal conversation, not a spreadsheet someone half-updated eight months ago > > — Finance Lead, Professional Services, 201-500 --- ## 04 · What the personas said ### Load-bearing terms and the product's shape are left undefined Four respondents could not tell whether this is one system or three bundled components, and said 'agent' and 'verified' carry weight without being defined. One reduced the offering to a SaaS audit dashboard with chat and noted there is no proof of the headcount replacement being implied. > the tabs listing 'System of record / AI usage / Contracts & renewals' side by side as if they're three separate things, which made me pause to work out whether this is one product or three bundled together > > — VP of Finance, Manufacturing, 1001-5000 > Same with "verified" — verified against what exactly, a contract PDF a human still has to read, or an API check? Those two words are load-bearing and neither is defined precisely enough for me to know what I'm buying. > > — Chief Financial Officer, Healthcare, 201-500 > Basically a glorified SaaS audit dashboard with some agentic chat bolted on, built around dollar figures it labels "verified" versus "declared." > > — Chief Financial Officer, Healthcare, 201-500 > Whether it actually delivers depends on whether Okta and the AI usage connectors (currently only Claude, and not "switched on in production" per their own admission) actually work as promised > > — Finance Lead, Professional Services, 201-500 ### ERP-centric and manufacturing buyers do not see themselves addressed Three respondents said the page needs to reference ERP integration explicitly and that the tone, while careful, is not aimed at ERP-centric environments. One noted company size and sector are left unspecified even though the audience is otherwise clear. > A line naming SAP or an ERP-adjacent workflow explicitly — something like 'sits alongside SAP Ariba/vendor master' — plus one manufacturing or industrial reference logo would do it > > — VP of Finance, Manufacturing, 1001-5000 > What's less clear is company size or industry fit; there's no "built for mid-market healthcare" or similar, so I'm assuming general applicability rather than being told it. > > — Chief Financial Officer, Healthcare, 201-500 ### Roadmap disclosure reads as half the product not existing yet, and it blocks consideration Eight respondents said a large share of the promised functionality — live usage connectors, Okta identity data, the AI/Claude piece — is flagged as in development rather than in production, and they treated the savings numbers as unverifiable as a result. Several said this directly blocks deal consideration or real validation today. > half the value — Okta connector, AI usage connections, renewal alerts — is labeled "built and waiting" or "coming next," not shipped. > > — VP of Finance, Manufacturing, 201-500 > The "in development," "coming next," "not switched on in production yet" language all over the connectors section is the tell; a mature vendor wouldn't ship a page that honest about gaps. > > — Director of Finance, Technology, 201-500 > it's explicitly an "illustrative sample," Okta and directory integration (the thing that turns seat counts into real unused-seat dollars) is "next," not live, and Claude is "not switched on in production yet" — so today it's mostly a nicer read of data I already have in ServiceNow plus finance exports > > — Finance Manager, Financial Services, 1001-5000 > the mechanics that would actually produce those numbers for me — Okta identity connection, Entra, Workspace, ChatGPT/Gemini connectors — are flagged "in development" or "coming next." So no, I wouldn't take a meeting yet > > — Director of Finance, Technology, 201-500 > Whether it actually delivers depends on whether Okta and the AI usage connectors (currently only Claude, and not "switched on in production" per their own admission) actually work as promised > > — Finance Lead, Professional Services, 201-500 ### No named customers or case studies, so credibility rests on assertion Four respondents pointed out there are no customer names, references or case studies anywhere on the page, and said this undermines the credibility of the claims. One specifically wanted a manufacturing reference customer running real contract data before assigning value. > Small, early-stage vendor — feels like a seed or Series A startup, maybe a dozen people, still building half the connectors they're selling. > > — Chief Financial Officer, Healthcare, 201-500 ### Adjacent incumbents are never named, so overlap has to be guessed Respondents flagged that the page does not address overlap with tools they already own — ServiceNow is named once, and one respondent said the contract and renewal data is already tracked in their existing Coupa contract. Differentiation against these has to be inferred. > the page never names what ServiceNow's contract/renewal module can't do, so I had to infer the differentiation from scattered lines like 'agent,' 'living record,' and 'overlap sized in dollars' rather than being told it directly > > — Finance Manager, Financial Services, 1001-5000 ### Respondents want an audit on their own data before spending time One respondent said a real contract audit against their own company data would be required before investing further time. This sets the bar for what the page currently cannot supply on its own. --- ## 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 clarity win is cosmetic: respondents understand the pitch fast and then stall on whether the product exists.** *(high)* Seven respondents got problem and audience inside ten seconds (theme 5), but eight said the connectors, Okta identity data and the AI piece are flagged as in development and treated the savings numbers as unverifiable, several saying this blocks deal consideration outright (theme 2). Fast comprehension is being spent on a product respondents conclude is half-built. Three more could not tell whether it is one system or three bundled components (theme 0). - **The only differentiator that lands is undermined by the same page that makes it.** *(high)* Six respondents could repeat 'verified vs. declared' back as the thing that sets the product apart (theme 7). But eight flagged that the live usage connectors and identity data that would produce verification are not in production (theme 2), and four found no customer names, references or case studies anywhere on the page (theme 3). The differentiator is a claim about proof with no proof behind it. - **Credibility rests entirely on assertion, and the page offers no substitute path to it.** *(high)* Four respondents found no customer names, references or case studies anywhere (theme 3), one specifically wanting a manufacturing reference running real contract data before assigning value. Another said a real audit against their own company data would be required before investing further time (theme 6). Both routes to belief — someone else's evidence or their own — are closed off by the page. - **The roadmap disclosure is the single largest drag on the page and outweighs every positive reaction combined.** *(high)* Eight respondents raised the in-development functionality and unverifiable savings, several stating it blocks deal consideration or real validation today (theme 2). That is more respondents than named the clarity win (seven, theme 5) or the one working differentiator (six, theme 7). The strongest signal on the page is a reason not to buy yet. - **Buyers are left to do the competitive analysis themselves, and they conclude they already own this.** *(medium)* ServiceNow is named once and overlap with tools respondents already run is never addressed, so differentiation has to be inferred (theme 4). One respondent said the contract and renewal data is already tracked in their existing Coupa contract. When the page's own differentiator depends on verification that is not yet shipping (theme 2), 'we already have this' is the default conclusion. - **Undefined load-bearing language makes the headcount and savings implications unsupportable.** *(medium)* Three respondents said 'agent' and 'verified' carry weight without definition, one reducing the offering to a SaaS audit dashboard with chat and noting there is no proof of the headcount replacement being implied (theme 0). The savings numbers were separately treated as unverifiable because of the roadmap disclosure (theme 2). Two independent routes lead to the same place: the quantified claims cannot be checked. --- ## 06 · Who answered | # | Role | Industry | Company size | | --- | --- | --- | --- | | 1 | VP of Finance | Manufacturing | 201-500 | | 2 | Director of Finance | Technology | 501-1000 | | 3 | Finance Manager | Financial Services | 1001-5000 | | 4 | Finance Lead | Professional Services | 201-500 | | 5 | Chief Financial Officer | Healthcare | 501-1000 | | 6 | VP of Finance | Manufacturing | 1001-5000 | | 7 | Director of Finance | Technology | 201-500 | | 8 | Finance Manager | Financial Services | 501-1000 | | 9 | Finance Lead | Professional Services | 1001-5000 | | 10 | Chief Financial Officer | Healthcare | 201-500 | | 11 | VP of Finance | Manufacturing | 501-1000 | | 12 | Director of Finance | Technology | 1001-5000 | | 13 | Finance Manager | Financial Services | 201-500 | | 14 | Finance Lead | Professional Services | 501-1000 | | 15 | Chief Financial Officer | Healthcare | 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.