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

After reading your page, 13 of 15 personas would take a meeting to learn more — and value was the weakest of the four.

- **Page tested:** https://www.measuredsem.com/
- **Audience tested against:** Mid-market SaaS CMOs at 200–1000 person companies who own demand gen and report to the CEO.
- **Personas:** 15 simulated
- **Report:** https://grader.wynter.com/r/measured-sem-search-marketing-that-compounds-s-1mteOEY

> 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? | 15/15 | 88% | 7 without hesitation, 8 with reservations |
| 3. Value | Do they actually want it? | 13/15 | 70% | all with reservations |
| 4. Differentiation | Is there a reason to pick you over the alternatives? | 13/15 | 70% | all with reservations |

**Brand alignment** (a side metric, not one of the four layers) — 14/15, 74% 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

**Attach verifiable evidence beside each case study metric.**

The line "Anonymized snapshots from real client engagements" is where the value claim breaks down — readers accept the 10x, 1,300% and 20x figures as memorable but say they cannot take them to a committee. Add, under each case card, the starting baseline period and the measurement source, e.g. "Baseline Jan 2022; measured in GA4 + Search Console, organic sessions only." Where a client will allow it, name them or at least state size and shape: "Series B cybersecurity vendor, ~120 employees."…

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

**Date each case study and add a recent engagement.**

CASE 002's "12-year engagement" and "Y1 Y6 Y12" timeline reads as history rather than present-day capability, and it also implies a buyer must wait years for results. Label each case with the engagement window (e.g. "2023–2025") and lead the set with the most recent one. For the long engagement, pull out an early milestone — what moved in the first two quarters — so the page answers the reader wondering how soon anything happens.

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

**Cite the Google signal terms or label them plainly.**

Terms like contentEffort, siteFocusScore, NavBoost and chromeInTotal split readers: some read practitioner expertise, others cannot tell whether these are real Google ranking factors or your own invented labels, and the page offers nothing to check. Add one line at the top of the Methodology section stating where the terms come from (e.g. "Signal names as they appear in the 2024 Google Search leak and DOJ trial exhibits") and link a source. That converts the same copy from unsourced jargon…

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

### Differentiation

**Show the methodology with a work sample or artifact.**

"Our work is structured to score on every one of them simultaneously. That's the modern playbook" asserts a method without ever showing it. Replace or follow the five pillars with one concrete artifact readers can look at — a redacted topical authority map, a sample content brief, or a before/after of one page — captioned with what changed and what happened. Method described is taste; method shown is differentiation.

*effort high · impact high · tested against Tie the feature to the outcome*

**Make founder involvement a specific, testable commitment.**

"Run by two partners. No junior reps." is the one claim readers repeat back, but it currently reads as a promise with nothing behind it. Pull it higher and make it checkable: state which partner runs your account, what they do weekly, and how many accounts each carries — e.g. "Each partner runs no more than five accounts. Both are on every strategy call. No account managers, ever." Numbers make it verifiable rather than reassuring.

*effort low · impact high · tested against Specifics beat superlatives*

**State the vertical fit before the case metrics.**

The industrial B2B case worked as differentiation because of the vertical, not the multiple. Rewrite the case headers so the situation leads rather than the label — "Multi-product industrial manufacturer, long sales cycle, dealer network" — and add one line naming the specific problem each engagement started from. That is the reason to choose you over a generalist agency that could also claim 10x.

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

### Brand alignment (side metric)

**Say plainly that this is an agency, not software.**

The signals-framework language — pillars, signal names, "SVC / 01" — reads like product copy, leaving some readers working out whether they are buying a tool or a team. Add a short line near the top, above Receipts, of the form "A two-partner SEO, content and PPC agency for B2B tech. The partners do the work." One sentence removes the ambiguity without softening the expert tone.

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

---

## 03 · What is working

### The case study headline metrics are the single most memorable thing on the page

Ten respondents pointed to the concrete numbers — 20x, 10x, 1,300% growth, session counts, YoY growth — as what made the offer legible and stuck with them. Several said the traffic multiples were more memorable than any product or service description on the page. These figures did the work of explaining what kind of agency this is.

> The case studies with named metrics — "20K to 204K monthly sessions in 8 months," "1,300% organic lift over 12 years" — gave me something concrete to hold onto rather than just vague "we do SEO" talk.
> 
> — CMO (Mid-Market SaaS), Cybersecurity, 201-500

> case studies with concrete numbers (20K to 204K sessions, +924% YoY)
> 
> — Head of Marketing, Developer Tools, 201-500

> the case studies (204K sessions, 1,300% traffic lift) are the only thing that would make me pick up the phone
> 
> — Chief Marketing Officer, Industrial B2B, 501-1000

> The case studies with traffic multipliers stuck with me more than any product description.
> 
> — Head of Marketing, Developer Tools, 501-1000

> The case studies with traffic multiples were the one thing that stuck, everything else read like standard agency positioning.
> 
> — Head of Marketing, Developer Tools, 201-500

> The case studies up top do the work: "20K to 204K monthly sessions," "20x by the end of the engagement" — I don't have to hunt, that's the pitch in the first screen.
> 
> — Senior CMO, Marketing Tech, 501-1000

### The industry list and case study categories tell buyers who this is for without any…

Nine respondents said the industry tags and case study headers at the top of the page immediately identified the target buyer and the problem being solved. Respondents in cybersecurity, dev tools, industrial B2B and growth marketing each recognised their own vertical in the list. No one had to dig or guess at fit.

> "Industries we know cold" up top lists B2B SaaS, Cybersecurity, Developer Tools, Industrial B2B, Marketing Tech, so I know immediately this is aimed at companies like mine
> 
> — CMO (Mid-Market SaaS), Cybersecurity, 201-500

> The "Industries we know cold" list at the top (B2B SaaS, Cybersecurity, Developer Tools, Industrial B2B, MarTech) plus the "Receipts" case studies (20K→204K sessions, +924% YoY) told me who they target and what problem they solve within the first screen
> 
> — Head of Marketing, Developer Tools, 201-500

> the problem (stalled organic growth, wasted PPC spend) and the buyer (a CMO-type deciding on agency spend) were both clear within the first screen or two
> 
> — Chief Marketing Officer, Industrial B2B, 501-1000

> the case study headers ("CASE 001 · B2B SAAS · DEVELOPER TOOLS," "CASE 003 · CYBERSECURITY") do double duty as both proof and audience signal
> 
> — Senior CMO, Marketing Tech, 201-500

> the "Industries we know cold" list up top (B2B SaaS, Cybersecurity, Developer Tools, Industrial B2B, MarTech) plus the case studies labeled "B2B SAAS · DEVELOPER TOOLS" told me immediately who this is for, and "Services" spelled out the problem: organic traffic/rankings, AEO visibility, and PPC spend efficiency.
> 
> — VP of Marketing, B2B SaaS, 501-1000

> SEO/PPC agency selling growth marketing services, one of our Industrial B2B case studies actually.
> 
> — Chief Marketing Officer, Industrial B2B, 201-500

> "Growth Marketing Consulting" and case studies for B2B SaaS, cybersecurity, industrial B2B flagged the audience. Growth-hungry marketers, not junior teams.
> 
> — Chief Marketing Officer, Industrial B2B, 201-500

> the dev tools case study (20K to 204K sessions in 8 months, 33% compound monthly growth) is the exact shape of problem I have, so it's directly relevant, not generic
> 
> — Head of Marketing, Developer Tools, 501-1000

> the industry tags right at the top ("B2B SaaS, Cybersecurity, Developer Tools, Industrial B2B, Marketing Tech") told me who they're chasing without me having to dig
> 
> — Head of Marketing, Developer Tools, 501-1000

> the "Industries we know cold" list (B2B SaaS, Cybersecurity, Developer Tools) and the case studies keyed to "B2B SAAS," "INDUSTRIAL B2B," "CYBERSECURITY" told me who they're targeting within the first screen
> 
> — CMO (Mid-Market SaaS), Cybersecurity, 501-1000

### Named founders doing the work themselves is the differentiator respondents could…

Five respondents named the two-partner, founder-led model — founders on calls and on the account rather than junior account managers — as what separates this from larger agencies. Two also credited the named partner bios and shared venture-backed history. This was the only differentiation claim respondents restated in their own words.

> "he'll be on your intro call, he'll also be on every monthly strategy call after that" — is the one thing that would tip me toward them over a competitor, because my actual complaint about most SEO agencies is a bait-and-switch where a senior person sells and a junior team executes.
> 
> — CMO (Mid-Market SaaS), Cybersecurity, 201-500

> "two partners, no junior reps" line combined with Tom and Ken's bios naming a specific shared history — "Director of Marketing at the same venture-backed PPC SaaS company before co-founding Measured SEM" — that's a concrete, checkable detail most agency pages don't bother with
> 
> — Head of Marketing, Developer Tools, 201-500

> The thing that would actually tip me toward them over a similar-sized agency is "Run by two partners. No junior reps" plus "The people you meet on the intro call are the people doing the work on your account"
> 
> — Senior CMO, Marketing Tech, 201-500

> The thing that would actually tip me toward this one over a competitor is "The people you meet on the intro call are the people doing the work on your account" plus two named founders with direct emails — that's a concrete structural difference from an agency where you pitch a partner and get handed to junior account managers
> 
> — VP of Marketing, B2B SaaS, 501-1000

### The industrial B2B case study landed as a direct vertical match

One respondent said the industrial B2B case study matched their own vertical and sales dynamics closely enough to function as differentiation, and another cited it as clarifying relevance. The specificity of the vertical, not the metric, is what did the work here.

---

## 04 · What the personas said

### The case study metrics are not verifiable, and respondents said so before they would…

Eight respondents flagged the same gap: anonymized case studies with no client names, no baselines, no methodology, and no company size. Several stated explicitly that they would need a named reference or verifiable GA/GSC data before taking this to a committee or committing budget. One added that a 12-year-old case study does not prove present-day capability.

> "anonymized snapshots" and no named client or reference I can check are the gap: before I'd take this past a first call I'd want to talk to Niru Raghavan or another named reference directly
> 
> — Head of Marketing, Developer Tools, 201-500

> I'd need to see that Case 002 client's actual vertical and starting traffic numbers before I believed the 1,300% figure applies to a company my size
> 
> — Chief Marketing Officer, Industrial B2B, 501-1000

> I'd want to hear a named reference client in Marketing Tech specifically before I'd take it further than a first conversation, since the case studies are anonymized and my category is oddly absent from the "receipts."
> 
> — Senior CMO, Marketing Tech, 201-500

> before I'd let it eat more of my quarter, I'd need them to show the actual before/after GA or GSC data behind one of those anonymized case studies and define whether siteFocusScore/contentEffort are real Google signals or their own framework
> 
> — VP of Marketing, B2B SaaS, 501-1000

> Traffic up, maybe leads up - but 12-year case study is no proof for us now. Not worth a meeting yet.
> 
> — Chief Marketing Officer, Industrial B2B, 201-500

> Them naming the actual client behind the dev tools case study, or at least letting me talk to a reference who confirms the 20K-to-204K number independently — without that it's just a story I can't bring to committee.
> 
> — Head of Marketing, Developer Tools, 501-1000

> how "20x" and "1,900%" were actually measured and over what baseline, because right now those numbers have no methodology attached
> 
> — CMO (Mid-Market SaaS), Cybersecurity, 501-1000

### The methodology and founder-involvement claims are asserted with nothing behind them

Three respondents said the methodology is described but never shown — no work samples, no artifacts, no proof. Two treated the founder-involvement promise as testable but currently unverified. One flagged that the long engagement duration implied by the case studies conflicts with a need for faster proof points.

> "1,300%... over a 12-year engagement" - too long to prove now, rules it out vs faster case studies.
> 
> — Chief Marketing Officer, Industrial B2B, 201-500

> "siteFocusScore," "clutterScore," "NavBoost" — sounds like it's reverse-engineering Google's internal signals with borrowed terminology, and if a competitor could show one client's before/after technical audit or a sample content piece that scored on their "contentEffort" claim, that proof would beat this page's naming-it-without-showing-it approach.
> 
> — CMO (Mid-Market SaaS), Cybersecurity, 201-500

### The Google signals terminology reads as expert to some and as unsourced jargon to others

Two respondents said naming contentEffort, NavBoost and similar signals demonstrated practitioner-level expertise. Three others could not tell whether terms like AEO, contentEffort and siteFocusScore are actual Google ranking factors or the agency's own proprietary labels, and noted the page offers no citation. The same copy produced opposite readings.

> the methodology section name-drops actual Google ranking signals (contentEffort, NavBoost, siteFocusScore) rather than staying at buzzword level, which signals they're talking to a practitioner, not a novice
> 
> — Head of Marketing, Developer Tools, 501-1000

> terms like siteFocusScore, siteRadius, and contentEffort are presented as if they're official Google metrics with no citation — I'd need to know if those are real ranking factors or the agency's own branding before I'd trust the methodology pitch.
> 
> — VP of Marketing, B2B SaaS, 501-1000

> the terms doing the heavy lifting — 'AEO,' 'contentEffort,' 'siteFocusScore,' 'NavBoost' — are dropped in as if they're established metrics without saying whether they're Google's actual named signals, third-party tools, or the agency's own shorthand
> 
> — CMO (Mid-Market SaaS), Cybersecurity, 501-1000

### The framework language makes some readers unsure whether this is a service or a product

One respondent had to work out that this is a services agency rather than a software platform, because the signals-framework terminology reads like product language. The distinction was resolvable but not stated.

> a boutique performance marketing/search agency, not a software tool or platform despite all the talk of "signals" like siteAuthority and contentEffort — that's their framework for describing SEO work, not a product I'd install. It's a services shop I'd hire, not a CMS or SaaS I'd buy a license for.
> 
> — Senior CMO, Marketing Tech, 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 most memorable asset is also its least credible one, so the strongest impression it leaves is one respondents refuse to act on.** *(high)*
  Ten respondents named the case study metrics — 20x, 10x, 1,300% — as the single most memorable thing on the page, while eight flagged those same case studies as unverifiable: no client names, no baselines, no methodology, no company size, and one dated 12 years back. The page's recall engine and its credibility failure are the same copy.
- **Nothing on the page survives committee scrutiny, so the page cannot advance a deal past the individual reader.** *(high)*
  Respondents explicitly stated they would need a named reference or verifiable GA/GSC data before taking this to a committee or committing budget. Three said the methodology is described but never shown — no work samples, no artifacts. Two treated founder involvement as testable but unverified. Every load-bearing claim on the page is an assertion.
- **The only differentiator respondents can restate rests on an unverified promise, which means the differentiation collapses under diligence.** *(high)*
  Five respondents named the founder-led, two-partner model as the separator from larger agencies, and it was the only differentiation claim they restated in their own words. Two of those same respondents treated the founder-involvement promise as testable but currently unverified. The page's one working differentiator has no proof behind it.
- **The technical vocabulary is a liability, not an expertise signal — more readers doubted it than were impressed by it.** *(high)*
  Three respondents could not tell whether AEO, contentEffort and siteFocusScore are real Google ranking factors or the agency's own invented labels, and noted the page offers no citation, against two who read the terms as practitioner-level expertise. One respondent also had to work out whether this is a services agency or a software platform because the signals-framework language reads like product copy. The same copy produces opposite readings and the negative reading is the majority one.
- **The case studies argue against the buying timeline they are meant to support.** *(medium)*
  One respondent flagged that the long engagement duration implied by the case studies conflicts with their need for faster proof points, and another noted a 12-year-old case study does not prove present-day capability. The evidence set signals slow, dated, unrepeatable results rather than current, near-term capability.
- **Vertical fit is doing the work the proof should be doing, and it only holds where a buyer's exact vertical is on the list.** *(medium)*
  Nine respondents said the industry tags and case study headers identified the target buyer immediately, and one respondent's relevance judgement rested entirely on the industrial B2B case study matching their own vertical and sales dynamics — the specificity of the vertical, not the metric, did the work. Recognition is carrying the page in place of substantiated capability, which leaves anyone outside the named verticals with nothing.

---

## 06 · Who answered

| # | Role | Industry | Company size |
| --- | --- | --- | --- |
| 1 | Head of Marketing | Developer Tools | 201-500 |
| 2 | Chief Marketing Officer | Industrial B2B | 501-1000 |
| 3 | Senior CMO | Marketing Tech | 201-500 |
| 4 | VP of Marketing | B2B SaaS | 501-1000 |
| 5 | CMO (Mid-Market SaaS) | Cybersecurity | 201-500 |
| 6 | Head of Marketing | Developer Tools | 501-1000 |
| 7 | Chief Marketing Officer | Industrial B2B | 201-500 |
| 8 | Senior CMO | Marketing Tech | 501-1000 |
| 9 | VP of Marketing | B2B SaaS | 201-500 |
| 10 | CMO (Mid-Market SaaS) | Cybersecurity | 501-1000 |
| 11 | Head of Marketing | Developer Tools | 201-500 |
| 12 | Chief Marketing Officer | Industrial B2B | 501-1000 |
| 13 | Senior CMO | Marketing Tech | 201-500 |
| 14 | VP of Marketing | B2B SaaS | 501-1000 |
| 15 | CMO (Mid-Market SaaS) | Cybersecurity | 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-25, then deleted along with the personas and their answers.

