brand

Messaging Ab Tester

Generate 3-5 messaging variants for a value proposition, design structured A/B tests, and analyze results to determine which framing resonates most with ICP. Tests can run via LinkedIn organic posts, cold email subject line splits, or both. Pure reasoning for variant generation and analysis — the user deploys the tests through their own tools. Use when a team can't decide between messaging angles and needs data, not opinions.

Gooseby Athina AI
Install
Terminal
npx gooseworks install --all

# then, in Claude Code, Cursor, or Codex:
/gooseworks use the messaging-ab-tester skill
About This Skill

Messaging A/B Tester

Stop debating which message is better — test it. Generate messaging variants, deploy them through real channels, and measure which framing actually resonates with your ICP.

Core principle: At seed/Series A, you don't have enough traffic for website A/B tests. But you do have enough LinkedIn impressions and cold email sends to test messaging angles fast.

When to Use

  • "Which of these value props should we lead with?"
  • "Test our messaging angles and tell me which works"
  • "I can't decide between [message A] and [message B]"
  • "What messaging resonates most with [ICP]?"
  • "Run a messaging test for [product/feature]"

Phase 0: Intake

What to Test

  1. Core value prop — The claim or positioning you want to test (e.g., "We help growth teams run outbound 10x faster")
  2. Test goal — What are you deciding? (Headline for website, cold email angle, LinkedIn content strategy, ad copy direction)
  3. ICP — Who should this resonate with? (Title, company type, stage)
  4. Current messaging — What are you using today? (Baseline to beat)

Test Channel

  1. Where to test:
    • LinkedIn organic — Post variants across consecutive days, compare engagement
    • Cold email — A/B test subject lines or opening hooks via Smartlead
    • Both — Run in parallel for fastest signal
  2. Sample size available:
    • LinkedIn: followers/typical impressions per post
    • Email: list size available for testing

Constraints

  1. Number of variants — 3-5 recommended (more = slower signal)
  2. Test duration — How long to run? (Default: 1 week for LinkedIn, 3-5 days for email)

Phase 1: Generate Messaging Variants

Create 3-5 variants that test different angles, not just different words. Each variant should represent a distinct strategic bet:

Variant Types

TypeWhat It TestsExample
Outcome-drivenLeading with the result"3x your pipeline in 30 days"
Pain-drivenLeading with the problem"Tired of spending 4 hours a day on manual prospecting?"
Identity-drivenLeading with who they are"Built for growth teams who move fast"
Proof-drivenLeading with evidence"How [Customer] went from 10 to 50 demos/month"
Contrast-drivenLeading with what you're not"Not another CRM. An outbound engine."

Variant Template

For each variant:

VARIANT [N]: [Type — e.g., "Outcome-driven"]
 
Hypothesis: This framing will resonate because [reasoning tied to ICP psychology]
 
LinkedIn post version:
---
[Full post copy — 100-200 words, native LinkedIn format]
---
 
Email subject line version:
[Subject line — max 50 chars]
 
Email opening hook version:
[First 2 sentences of an email]
 
Headline version:
[Website headline — max 10 words]

Phase 2: Deploy Tests

Option A: LinkedIn Organic Test

Setup:

  1. Schedule variants as consecutive posts (1 per day, same time of day)
  2. Each post should be similar length and format (control for post structure)
  3. Don't boost any posts — organic only for clean comparison

Measurement (after 48 hours per post):

  • Impressions
  • Reactions (likes, celebrates, etc.)
  • Comments
  • Comment sentiment (positive/negative/neutral)
  • Profile visits (if trackable)
  • DMs received mentioning the post

Option B: Cold Email A/B Test

Setup via your outreach tool (Smartlead, Instantly, Lemlist, or any tool with A/B testing):

  1. Create campaign with all variants as A/B test sequences
  2. Split list evenly across variants (minimum 50 per variant for signal)
  3. Same send time, same sender, same CTA — only the messaging changes

Measurement (after 5 days):

  • Open rate (tests subject line)
  • Reply rate (tests full message resonance)
  • Positive reply rate (tests conversion quality)
  • Click rate (if link included)

Option C: Both (Recommended)

Run LinkedIn and email in parallel. Different channels may show different winners — that's valuable signal about where each message works best.

Phase 2B: Collect Results

After the test has run for the planned duration, gather your results:

How to provide data:

  • Paste metrics — Copy open rates, reply rates, engagement numbers directly into the chat
  • CSV export — Export campaign analytics from your outreach tool and share the file
  • Screenshot — Take a screenshot of your dashboard/analytics and share it
  • Manual input — Just tell the agent the numbers: "Variant A got 45% open rate and 3% reply rate, Variant B got 52% open rate and 5% reply rate"

For LinkedIn tests: Go to your post analytics (click "View analytics" on each post) and share impressions, reactions, comments, and profile visits per post.

For email tests: Export or screenshot your campaign's variant/A-B test results showing sends, opens, and replies per variant.

The agent will normalize whatever format you provide into the scoring framework below.

Phase 3: Analyze Results

Scoring Framework

MetricWeight (LinkedIn)Weight (Email)
Engagement rate30%
Comment quality30%
Open rate30%
Reply rate40%
Positive reply rate30%
Impressions20%
Profile visits / clicks20%

Statistical Significance Check

For email tests:

  • Minimum sends per variant: 50 (for directional signal), 200+ (for confident decisions)
  • Minimum difference to call a winner: >20% relative difference in primary metric

For LinkedIn tests:

  • Minimum posts per variant: 1 (you're testing with limited data — treat as directional)
  • Minimum impressions: 500 per post to be comparable

Winner Selection

WINNER: Variant [N] — [Type]
 
Primary metric: [X] (vs average of [Y] across other variants)
Relative improvement: [Z%] over baseline
 
Why it won:
[1-2 sentences on what this tells us about ICP messaging preferences]
 
Runner-up: Variant [N]
[1 sentence on when this might work better — different channel, different segment]

Phase 4: Output Format

# Messaging A/B Test Results — [DATE]
Value prop tested: [description]
ICP: [target audience]
Test duration: [dates]
 
---
 
## Test Design
 
| Variant | Type | Hypothesis |
|---------|------|-----------|
| A | [Type] | [Hypothesis] |
| B | [Type] | [Hypothesis] |
| C | [Type] | [Hypothesis] |
 
---
 
## Results
 
### LinkedIn Test
 
| Variant | Impressions | Reactions | Comments | Engagement Rate | Score |
|---------|------------|-----------|----------|----------------|-------|
| A | [N] | [N] | [N] | [X%] | [weighted] |
| B | [N] | [N] | [N] | [X%] | [weighted] |
| C | [N] | [N] | [N] | [X%] | [weighted] |
 
### Email Test
 
| Variant | Sends | Opens | Open Rate | Replies | Reply Rate | Positive | Score |
|---------|-------|-------|-----------|---------|------------|----------|-------|
| A | [N] | [N] | [X%] | [N] | [X%] | [N] | [weighted] |
| B | [N] | [N] | [X%] | [N] | [X%] | [N] | [weighted] |
| C | [N] | [N] | [X%] | [N] | [X%] | [N] | [weighted] |
 
---
 
## Winner: Variant [N] — "[Headline]"
 
**Why it won:** [Analysis — what does this tell us about how our ICP thinks?]
 
**Recommended deployment:**
- Website headline: "[adapted version]"
- Sales deck opening: "[adapted version]"
- LinkedIn bio: "[adapted version]"
- Cold email default: "[adapted version]"
 
---
 
## Variant Details & Copy
 
### Variant A: [Full copy used in test]
### Variant B: [Full copy used in test]
### Variant C: [Full copy used in test]
 
---
 
## What to Test Next
 
Based on these results, the next messaging test should explore:
1. [Angle suggested by results — e.g., "test more specific proof points since proof-driven won"]
2. [Segment test — e.g., "test winning message against different ICP segment"]

Save to the current working directory or wherever the user prefers.

Cost

ComponentCost
Variant generationFree (LLM reasoning)
LinkedIn postingFree (organic)
Email testingIncluded with your outreach tool's plan
Results analysisFree (LLM reasoning)
TotalFree

Tools Required

None. Pure reasoning for variant generation, test design, and result analysis. The user deploys tests through their own tools:

  • LinkedIn organic — post variants manually or via scheduling tool
  • Cold email — set up A/B tests in whatever outreach tool they use (Smartlead, Instantly, Lemlist, etc.)
  • Results — user provides metrics (screenshots, CSV exports, or manual input) for analysis

Trigger Phrases

  • "Test which messaging angle works best for [ICP]"
  • "Run a messaging A/B test for [value prop]"
  • "Which of these messages should we lead with?"
  • "Help me decide between these positioning options"

What's included

·
"Which of these value props should we lead with?"
·
"Test our messaging angles and tell me which works"
·
"I can't decide between [message A] and [message B]"
·
"What messaging resonates most with [ICP]?"
·
"Run a messaging test for [product/feature]"
You Might Also Like

Render VO Anchored Motion Listicle

Assemble an expert/educator motion-graphic LISTICLE video ad from a config — a spoken authoritative voiceover carries a numbered listicle while N web-animated hyperframe beats (HTML plus the Web Animations API, one branded design system of alternating tiles, big hero numerals, and glass-pill callouts) are rendered frame-by-frame via Playwright and anchored to the VO's word-level timestamps, periodic color-graded B-roll windows give visual breath, and captions burn ONLY inside those B-roll windows (2-word chunks, ASS Format header carrying a Name field so none drop) with the VO mixed under a low music bed. This is the FREE deterministic assembly stage (Playwright beat render plus ffmpeg concat plus window-masked caption burn plus VO-and-music mix plus final composite) — the VO, the music bed, and the stock B-roll come from create-vo-elevenlabs, create-music-elevenlabs, and media-proxy. Use for the vo-anchored-motion-listicle format.

Render Stopmotion Hand Swatch Cycle

Assemble a stop-motion hand-swatch-cycle product-demo ad from a config — a sequence of still PLATES (one hand swiping a single-barrel cosmetic across a cream skin-patch, the barrel + swatch changing per plate while the hand, background, crop, and lighting stay locked) is PNG→mp4 loop-encoded at each plate's own stop-motion hold (fast motion frames 150–250ms, per-shade ~380ms, hero beats 1100–1800ms), concat-demuxed with HARD cuts into a silent master, closed on a Playwright HTML-rendered branded end card (serif tagline + sans subtitle + real logo SVG over a hero BG, never AI-rendered text), and muxed with a pre-sourced music track playing under the end card with a fade tail (no VO). This is the FREE deterministic assembly stage (loop-encode + concat-demux + end-card render + music mux); the master-anchor plate, shade plates, and end-card BG come from create-image-gpt-image-fal and the track from create-music-elevenlabs. Use for the stopmotion-hand-swatch-cycle format.

Render Split Screen Creator

Assemble a split-screen creator ad from a config — a two-zone vertical composite where a supplied AI-creator lip-sync take fills the BOTTOM ~48% while real 16:9 product/demo clips run uncropped in the TOP ~52%, each top clip contain-fit with a darkened blurred cover-scale fill of the same clip (never black bars), a 3px brand-color divider between the zones, the creator slice cover-fit per the per-scene VO timing, scenes hard-concatenated with the body audio being the concatenated creator VO slices, an end card held on the last sharp frame ~3s, then the ASSEMBLED cut transcribed with local Whisper (not the raw VO — concat drops inter-scene silence) and word-level captions burned in the chosen style. This is the FREE deterministic assembly + caption stage (two-zone composite + blurred fill + divider + hard-concat + end card + captions); the VO comes from create-vo-elevenlabs, the anchor from create-image-gpt-image-fal, and the whole-VO lip-sync from a paid VEED Fabric 1.0 take (a no-atom upstream input). Use for the split-screen-creator format.

Newsletter

Learn to build Growth systems with AI

2-3 compounding systems per week using Claude Code, OpenClaw, and more.