# Message test — https://www.hockeystack.com/

After reading your page, only 4 of 15 personas could name a reason to pick you over a similar option.

- **Page tested:** https://www.hockeystack.com/
- **Audience tested against:** demand gen marketers in b2b
- **Personas:** 15 simulated
- **Report:** https://grader.wynter.com/r/ai-gtm-b2b-revenue-data-intelligence-platform--J81-GFg

> 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 | 79% | 1 without hesitation, 14 with reservations |
| 2. Relevance | Can they tell what it solves, and who it's for? | 15/15 | 79% | 1 without hesitation, 14 with reservations |
| 3. Value | Do they actually want it? | 10/15 | 59% | all with reservations |
| 4. Differentiation | Is there a reason to pick you over the alternatives? | 4/15 | 39% | 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: Differentiation.** 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

**State what Atlas does that a warehouse plus BI cannot.**

'Atlas is HockeyStack's data foundation that ingests, unifies, and actions your GTM data' reads as the same pipeline story every competitor tells, and 'Reasoning Layer' compounds it. Say the specific thing: which identity matches Atlas resolves that last-touch and CRM-based models drop, and what percentage of anonymous account activity it recovers. A named, checkable capability separates the section; 'data foundation' does not.

*effort medium · impact high · tested against Concrete over abstract*

**Add a switching section for teams leaving an incumbent tool.**

Readers standing next to Bizible or Dreamdata found no reason to move. Add a short block that names the migration case in their terms — historical data backfill, how long parallel running takes, what breaks in existing QBR reporting — and one customer who switched, with what changed in their reports. This answers the objection an evaluator is already holding without asking them to infer it from feature lists.

*effort medium · impact high · tested against Give a reason to choose you*

**Replace 'source of truth' hero with the incrementality claim.**

'Modern Attribution that captures the complete buyer journey' and 'one actionable source of truth' are lines Bizible, Dreamdata and every other attribution vendor could run unchanged. The one idea readers could not find elsewhere — proving causation by comparing exposed and unexposed accounts — is buried as the third feature card. Lead with it: name causal measurement, not attribution coverage, in the H1 and subhead.

*effort low · impact high · tested against Give a reason to choose you*

### Value

**Add lift report specifics beside the incrementality claim.**

'Lift reports compare exposed and unexposed accounts to prove which campaigns actually drive conversions' is the one line readers repeat back — and the one they immediately qualify with 'if proven'. Right now the word 'prove' is doing work nothing on the page supports. Put the mechanics next to the claim: how control (unexposed) accounts are selected, minimum account volume needed for a readable result, and the confidence or significance threshold the report uses. A single named example — 'a…

*effort medium · impact high · tested against Proof next to the claim*

**Add a before/after case study for lift specifically.**

The case studies on the page ('cutting ad spend in half', '8x8's Marketing Team Drives Business Growth') sit far from the Lift & Incrementality block and don't say what the lift report showed. Readers wanting to act on incrementality asked for a before/after against their own numbers. Publish one case with the prior attribution read, the lift-report read, and the budget decision that followed — dollars moved, program killed or scaled — placed directly under the Lift & Incrementality copy…

*effort medium · impact high · tested against Proof next to the claim*

**Offer a validation pilot against recent closed-won deals.**

The only CTAs are 'Get a Demo' and 'Live Preview', neither of which answers the question buyers actually hold: does this match my CRM? Add a named, bounded next step under the Lift section — for example a benchmark run against the last two quarters of closed-won opportunities, with a stated turnaround — so the evaluator has a way to test the claim rather than accept it.

*effort medium · impact high · tested against Answer the live objection*

### Clarity

**Define 'Atlas' and 'Agents' where each term first appears.**

'HockeyStack Agents: Forecast Challenger' and the ATLAS section both use branded names before the reader knows what they are, and 'Reasoning Layer' compounds it with an undefined internal term. Add a plain gloss at first mention — Atlas as the ingestion and identity-resolution layer, Agents as the automated recommendation feature — so readers stop reverse-engineering the data flow to work out what the product does.

*effort low · impact medium · tested against Plain language*

### Brand alignment (side metric)

**Answer the obvious measurement objections in the FAQ.**

The confident case-study headlines ('hit their monthly revenue targets after cutting ad spend in half') sitting beside a page that never addresses accuracy, minimum data volume, or CRM reconciliation reads as evasion rather than confidence. Name the hard questions in plain terms — what happens when account volume is too low for a lift read, how the numbers reconcile when they disagree with Salesforce — and answer them. Stating a limit raises trust in the claims that remain.

*effort medium · impact medium · tested against Answer the live objection*

---

## 03 · What is working

### The hero line and audience callout are the one part respondents read cleanly

Six respondents named the hero line and the explicit audience/role section as clearly stating the problem, the solution, and who the product is for. Two of these pointed to role tabs and case study logos as doing the persona work without a stated persona line. This was the most consistently praised element on the page.

> the hero line "Modern Attribution that captures the complete buyer journey. From first touch to closed-won" tells you the problem (fragmented marketing/sales data, no clear pipeline attribution) and the fix in one breath. The "Empower Every Revenue Team" section spells out the audience directly: Marketing Leaders, GTM Operations, Sales Leaders
> 
> — Demand Generation Manager, Enterprise Software, 5000+

> the hero line "Modern Attribution that captures the complete buyer journey... unify your marketing and sales data into one actionable source of truth" tells you the problem (fragmented, last-touch-biased marketing/sales data) in the first two lines. The audience is spelled out too, not inferred: "Empower Every Revenue Team — Marketing Leaders, GTM Operations, Sales Leaders"
> 
> — Director of Demand Generation, B2B SaaS, 201-500

> the hero line "Modern Attribution that captures the complete buyer journey... Unify your marketing and sales data into one actionable source of truth" tells you the problem (fragmented, last-touch data) and the fix.
> 
> — Head of Demand Generation, Enterprise Software, 501-1000

> the "Empower Every Revenue Team" section naming Marketing Leaders, GTM Operations, and Sales Leaders makes it easy to place yourself
> 
> — Senior Demand Generation Manager, B2B SaaS, 5000+

> the hero line "Modern Attribution that captures the complete buyer journey. From first touch to closed-won" tells you the problem (disconnected marketing/sales data, no clean pipeline attribution) in one breath, and the "Empower Every Revenue Team — Marketing Leaders, GTM Operations, Sales Leaders" section spells out exactly who it's for
> 
> — Demand Generation Manager, B2B SaaS, 501-1000

### Lift and incrementality is the claim respondents could repeat back and wanted to be true

Six respondents singled out lift and incrementality as the substantive idea on the page, describing it as solving QBR causality disputes, covering a gap for events and low-volume programs, and proving causation rather than correlation. Several specifically named the exposed-vs-unexposed account comparison as the mechanism that made it credible as a concept. This is the only claim respondents treated as more than…

> The Lift & Incrementality piece — "compare exposed and unexposed accounts to prove which campaigns actually drive conversions... ideal for low-volume, high-impact programs like events and content" — is the one thing here that could actually differentiate this from a Bizible or Dreamdata
> 
> — Head of Demand Generation, B2B SaaS, 1001-5000

> The "Lift & Incrementality" section is the one thing that could differentiate it — comparing exposed vs. unexposed accounts to prove campaigns actually drive conversions is a real, specific claim, not just "unify your data" fluff
> 
> — Senior Demand Generation Manager, Technology Services, 51-200

> the "Lift & Incrementality" bit for proving campaigns like events actually converted is genuinely useful if it holds up, since that's hard to prove with what I have now.
> 
> — Demand Generation Manager, Enterprise Software, 5000+

> If it actually worked, I'd stop arguing in QBRs about whether that dark-funnel content program or that events spend actually moved pipeline — the "Lift & Incrementality" piece comparing exposed vs. unexposed accounts is the one feature that would genuinely change my day-to-day
> 
> — Director of Demand Generation, B2B SaaS, 201-500

> The "lift and incrementality" piece is the part that would actually matter to me — proving events and content drive conversions rather than just correlate with them
> 
> — Director of Demand Generation, Technology Services, 501-1000

> if this genuinely does exposed-vs-unexposed testing that's a real methodological difference, not a marketing line
> 
> — Director of Demand Generation, Technology Services, 501-1000

### The tone lands with marketing leaders under budget pressure

Three respondents said the voice correctly targets tired marketing leaders reconciling conflicting reports and defending spend in budget reviews, and understands that buyer's pain. One added that the page appropriately assumes attribution literacy rather than over-explaining basics.

> it skips the 101 explainer and goes straight into "attribution model," "dark funnel," "lift and incrementality," which assumes I already know why last-touch CRM data is garbage. That's a plus
> 
> — Demand Generation Manager, Technology Services, 1001-5000

> The tone does feel aimed at someone like me specifically — phrases like "prove what's working, fix what's not" and the explicit "Marketing Leaders / GTM Operations / Sales Leaders" tabs are written by someone who's sat in my budget review and knows the exact fight I'm having
> 
> — Head of Demand Generation, Technology Services, 201-500

> they know their buyer is a marketing leader tired of reconciling five reports
> 
> — Director of Demand Generation, Technology Services, 501-1000

---

## 04 · What the personas said

### Branded and buzzword terms are used without any mechanism behind them

Six respondents said key terms — 'Atlas', 'Agents', 'cookieless tracking', 'dark funnel', 'industry-best scoring' — appear without definition or explanation of how they work. Two said they had to reverse-engineer the data flows themselves to understand what the product actually does. The vendor vocabulary actively hid the mechanics rather than compressing them.

> phrases like "actionable source of truth" and "reasoning layer" are the kind of vendor filler that don't tell you anything mechanical, so I had to infer that Atlas is just ETL plus identity resolution
> 
> — Head of Demand Generation, B2B SaaS, 1001-5000

> "Cookieless tracking" and "dark funnel" are the culprits — both get used as if they're self-evidently understood mechanisms, but neither is defined: does cookieless mean IP-based firmographic matching, first-party pixel, email hash matching?
> 
> — Director of Demand Generation, B2B SaaS, 201-500

> the friction is words like "Atlas," "Agents," and "one actionable source of truth," which are branded/vague enough that I have to translate them back into normal terms
> 
> — Demand Generation Manager, B2B SaaS, 501-1000

> Two phrases did it: "cookieless tracking" and "dark funnel" — both get used as if the mechanism is self-evident, but neither is defined anywhere on the page.
> 
> — Senior Demand Generation Manager, Enterprise Software, 1001-5000

### Company size and segment fit cannot be determined from the page

Two respondents said they could not tell whether the platform is built for mid-market or enterprise, and inferred fit only from customer logos rather than from anything stated. One other respondent read the logos as accurately signalling mid-market B2B SaaS, meaning the logos are carrying segment positioning the copy does not state.

> What's less obvious is company size/segment fit — the case studies (8x8, ActiveCampaign, n8n) suggest mid-market to enterprise B2B SaaS, but that's inferred from logos, not stated outright.
> 
> — Head of Demand Generation, B2B SaaS, 1001-5000

> What's still fuzzy is company size/stack fit — nothing tells me if this is built for a 51-200 person shop like mine or only makes sense at enterprise scale with messy multi-source data.
> 
> — Senior Demand Generation Manager, Technology Services, 51-200

### Every respondent who liked the incrementality claim conditioned it on proof that is not…

Seven respondents attached an explicit 'if proven' to the lift and incrementality claim, asking for control group definitions, sample sizes, accuracy benchmarks against their own CRM, and a case study with before/after numbers. Three said they would need a pilot against recent closed-won deals or a technical review of a real lift report before taking a next meeting. The differentiating claim and the missing proof…

> no sample dashboard, no methodology for the lift reports (what's the control group, how do they define "unexposed"?)
> 
> — Head of Demand Generation, B2B SaaS, 1001-5000

> It's basically a Bizible/Dreamdata-type competitor - not something new to me, and given I already run something adjacent, I'd need to see specifics on data accuracy and integration coverage before I'd say this beats what I have.
> 
> — Demand Generation Manager, Enterprise Software, 5000+

> I'd want them to show me the 8x8 or ActiveCampaign case study specifics (what stack size, what it replaced, how long setup took) before I'd give it more than 30 minutes
> 
> — Senior Demand Generation Manager, Technology Services, 51-200

> I'd need to see accuracy benchmarks against my own CRM reporting before I believe the "defend it in the boardroom" line.
> 
> — Director of Demand Generation, Technology Services, 501-1000

> But as written it's just a feature description with no proof: no sample size, no definition of what counts as "exposed," no case study number tied specifically to a lift result
> 
> — Director of Demand Generation, B2B SaaS, 201-500

> I'd want them to run a pilot against our own last 2-3 closed-won deals and show me their attribution matches or beats what we already know happened
> 
> — Director of Demand Generation, Technology Services, 501-1000

> A real case study with before/after attribution numbers that survived a boardroom challenge — if I could take one customer's data and reconcile it against what our CRM currently shows, that's the only thing that would justify pulling budget for this.
> 
> — Head of Demand Generation, Enterprise Software, 501-1000

### Outside of incrementality, the page reads as the same category language every competitor…

Four respondents placed the product in the standard B2B attribution/GTM analytics category alongside Bizible and Dreamdata and could not find separation from them. Two named 'Atlas' and 'source of truth' as generic language used by all competitors, and two asked for a direct competitor comparison to justify switching. One said the positioning was generic-competent but not sharp enough to support beating incumbents.

> to pick this one I'd need a side-by-side or at least a named customer saying why they left one of those for HockeyStack, not just a case study headline
> 
> — Senior Demand Generation Manager, Technology Services, 51-200

> Basically a B2B attribution/GTM analytics tool, same category as Dreamdata or Bizible, not something new.
> 
> — Director of Demand Generation, Technology Services, 501-1000

> the language ("Modern Attribution," "Atlas," "forward-looking insights") is the same vocabulary every vendor in this space uses, so it reads like a company that understands its market segment well but hasn't earned the right to talk to me like they've beaten the incumbents yet
> 
> — Director of Demand Generation, Technology Services, 501-1000

### Confident claims sitting next to unanswered objections read as evasive

Two respondents flagged a credibility gap: the case studies are stated confidently while the FAQ stays silent on the obvious questions, and the jargon-heavy messaging offers nothing to a budget decision-maker. The mismatch between assertion and proof was read as a tone problem, not just a content gap.

> that gap between the swagger of the case study headlines and the silence on methodology is what makes we wonder if the substance matches the tone.
> 
> — Demand Generation Manager, Enterprise Software, 201-500

> Tone's aimed at marketing ops people, not budget owners like me — heavy on jargon, light on proof.
> 
> — Director of Demand Generation, Enterprise Software, 51-200

---

## 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 one differentiating claim cannot survive contact with a buying committee, because nobody can act on it without proof the page never supplies.** *(high)*
  Six respondents named lift and incrementality as the only substantive idea, and seven attached an explicit 'if proven' condition to it, demanding control group definitions, sample sizes, CRM accuracy benchmarks and before/after case numbers. Three would only advance to a pilot or technical review of a real lift report. The single asset that carries the page is also the single asset that stalls the next meeting.
- **Strip out incrementality and there is no reason to switch vendors left on the page.** *(high)*
  Four respondents filed the product into the standard attribution/GTM analytics category next to Bizible and Dreamdata with no separation, two flagged 'Atlas' and 'source of truth' as language every competitor uses, and two asked for a direct competitor comparison. Since the only claim treated as more than table stakes is the unproven one (theme 6), the page offers incumbents no threat.
- **Branded vocabulary is doing the work that mechanism explanation should do, and it is costing comprehension.** *(high)*
  Six respondents said 'Atlas', 'Agents', 'cookieless tracking', 'dark funnel' and 'industry-best scoring' appear with no definition of how they work, and two had to reverse-engineer the data flows themselves. Two separately named 'Atlas' and 'source of truth' as generic competitor language. The naming buys no differentiation and destroys clarity at the same time.
- **Customer logos are carrying the segment positioning the copy refuses to state, which means qualification depends on whether a reader recognises the brands.** *(medium)*
  Two respondents could not tell whether the platform is built for mid-market or enterprise and inferred fit only from logos; one read the logos as signalling mid-market B2B SaaS. Two respondents also credited case study logos and role tabs with doing persona work in the absence of a stated persona line. Positioning that only works for readers who already know the customer base is not positioning.
- **The page is written for someone who already believes attribution matters and locks out the person who signs the cheque.** *(medium)*
  Three respondents praised the voice for assuming attribution literacy and targeting marketing leaders defending spend, but two said the jargon-heavy messaging offers nothing to a budget decision-maker and that the FAQ stays silent on obvious questions. The literacy assumption that earns credibility with the champion is the same thing that leaves them without material to sell internally.
- **Confidence without evidence is reading as evasion, not authority.** *(medium)*
  Two respondents flagged confidently stated case studies against an FAQ silent on the obvious questions and called it a credibility gap, a tone problem rather than a content gap. Combined with the seven respondents who conditioned the headline claim on proof and the six who found branded terms undefined, the assertive voice reads as concealment.

---

## 06 · Who answered

| # | Role | Industry | Company size |
| --- | --- | --- | --- |
| 1 | Director of Demand Generation | Technology Services | 501-1000 |
| 2 | Head of Demand Generation | B2B SaaS | 1001-5000 |
| 3 | Demand Generation Manager | Enterprise Software | 5000+ |
| 4 | Senior Demand Generation Manager | Technology Services | 51-200 |
| 5 | Director of Demand Generation | B2B SaaS | 201-500 |
| 6 | Head of Demand Generation | Enterprise Software | 501-1000 |
| 7 | Demand Generation Manager | Technology Services | 1001-5000 |
| 8 | Senior Demand Generation Manager | B2B SaaS | 5000+ |
| 9 | Director of Demand Generation | Enterprise Software | 51-200 |
| 10 | Head of Demand Generation | Technology Services | 201-500 |
| 11 | Demand Generation Manager | B2B SaaS | 501-1000 |
| 12 | Senior Demand Generation Manager | Enterprise Software | 1001-5000 |
| 13 | Director of Demand Generation | Technology Services | 5000+ |
| 14 | Head of Demand Generation | B2B SaaS | 51-200 |
| 15 | Demand Generation Manager | Enterprise Software | 201-500 |

---

## 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. <https://wynter.com>

This report is kept for 60 days from 2026-08-22, then deleted along with the personas and their answers.

