Skip to main content
Message Testing evaluates a draft against your buyer personas and brand voice. You see what’s landing, what’s not, and why — tied back to research. Use it to pressure-test messaging before it goes to market, not after impressions are already coming in.

​
Why this matters

Two patterns from real PMM teams show up constantly: You don’t always own the surface you’d use to test. Landing pages live with product. Email lives with demand gen. By the time you can test in the wild, you’ve already shipped. Message Testing gives you a place to validate before anything goes live. Even when you can test, the results aren’t trusted. Fast digital tests feel directional. Surveys feel hollow. Internal sign-off devolves into competing opinions. Message Testing combines real research interviews with your defined persona, so the feedback comes back tied to what buyers in that segment have actually said.

​
How it works

You provide:
  1. Content — paste the text or import it from a URL
  2. Target persona(s) — pick one or more from your saved Personas
  3. Goal — optional context about what you’re trying to accomplish
GetWhys pulls research interviews that match your persona, combines them with the persona description and your Brand Voice, and runs the content through an evaluation. You get back annotations on what works, what doesn’t, and why.

​
Why every Message Test asks for the same setup

Persona, brand voice, goal, and content type all change the feedback. The same email tested against a CFO persona and a CISO persona should produce different results. The setup is what lets GetWhys pick the right lens.

​
Why Message Testing doesn’t write suggested revisions for you

LLMs are great at evaluation. They’re weaker at preserving the human voice and specificity that makes good content good. We deliberately leave the writing to you — GetWhys does the grunt work of comparing your draft to a large body of research about your audience and your stated voice, so you can stay focused on the strategic and creative call.

​
What content you can test

Anything written. Email, ad copy, landing pages, blog posts, sales decks, social posts, scripts, product copy. If it has words, it can be tested.

​
Supported inputs

  • Pasted text — paste content directly into the form
  • URL import — give GetWhys a URL and it will fetch the page text for you

​
What you get back

An annotated view of your content with:
  • Persona-specific reactions (does this audience care? does it speak their language?)
  • Brand voice alignment (which characteristics match, which don’t, where the drift is)
  • Specific lines that work and lines that don’t, with the reason for each
  • A downloadable annotation report

​
For PMM and marketing leaders

Message Testing is also a governance layer. Sales is writing outbound. Product is writing release notes. AI tools across the team are generating drafts on every surface. Message Testing gives everyone the same check before things ship — your defined personas and your brand voice become the standard, applied consistently.

​
Setting up before your first test

You need at least one Persona and a Brand Voice before you can run a Message Test:

Set up Personas

Build buyer profiles that sharpen every Message Test.

Set up Brand Voice

Encode how your organization writes.
The quality of the feedback follows the quality of the setup. Thin personas and vague brand voice produce thin, vague feedback. Specific personas and opinionated brand voice produce specific, opinionated feedback.

​
Where Message Tests live

All past Message Tests are saved under Message Test → History in the left navigation. Open any past test to revisit the original content and the feedback.