Engine 03 · Email & sequences

Test the send before it goes out.

300 agents take every variant from inbox to landing page and decide: open, click, reply or delete. Back in 30 minutes: what’s working, what’s broken, and what to fix.

300 agents, 60 per reader. Every variant scored, per reader.
EMAIL · /inboxLive
Email Campaign Simulation interface
Runs against
Subject + body variants
Models
Inbox to page
You get
A per-role winner
Ground Reality

You don’t write the personas. Your buyers already did.

Before they meet you: review sites, community threads, competitor complaints, and how all of it shifted over 18 months. After they meet you: call recordings, CRM notes, win/loss reasons.

Most tools get one half. A persona doc gets neither. How Ground Reality works

The process

Inbox, body, page.

Three decisions, run across every variant and every reader.

01

The inbox

Subject and preheader only. Open or ignore.

02

The body

Judged against the subject’s promise. Click, reply or leave.

03

The destination

The page lands the promise. Convert or bounce.

04

Rank the matrix

Every variant against every reader. The winners surface.

Why it breaks

Why a good send underperforms.

You find out after it lands, if at all.

Failure 01

Two seconds in the inbox

120+ emails a day. Your subject line gets two seconds to look worth opening.

Every subject line scored per reader, before you send.
Failure 02

The body breaks the promise

The subject earns the open. The body opens with “Hope you’re well!”

The body is judged against the subject, with each reader’s reason.
Failure 03

Written for nobody

One email to the VP, the architect and the engineer wins for none of them.

A winner per reader shows who you gain and who you lose.
What you get

The Per-Persona Winner, and everything around it.

Weeks of A/B cycles and subject-line guessing. Gone.

variant synthesis
Variant matrix · per role
EngCFOSec
A · “Cut rollback 60%”winmissweak
B · “Reduce TCO”weakwinweak
C · “Quick question”missmissmiss
Winner: A for Eng, B for CFO. Split the send, drop C.

Per-Persona Winner

The subject, body, and CTA that win per role.

Variant matrix

Ranked performance across every combination.

Link heatmap

Which CTA each role clicked.

Objection replies

The likely pushback, so SDRs can prep.

Drafted subjects

Replacements when a variant is below baseline.

Who it is for

Built for whoever owns the send.

Email Campaign Simulation

Demand gen

Know which subject earns opens before the full send.

Email managers

Pick the winning body without a live A/B test.

SDR leaders

Make the first cold email land. Prep the objections.

Product marketing

Validate a launch email for practitioner and buyer.

Automatic runs

The send is fine. The page it opens changed.

An email keeps its promise only as long as the page behind the link does. WhyUser watches that page and re-runs the send when it changes, at 20 credits per subject, body and link combination.

Daily check

The landing pages your live sends point at, on a schedule you set.

Did the landing promise change?

What the click was promised, against what the page now says.

Yes → re-run the combination

~30 min · 20 credits per combo, at 300 agents.

No change → skip. No run, no credits.

Slack digest

The reader who now drops at the handoff, and the line to change.

Not a trigger

Dates, counters and prices moving in the copy. Cosmetic edits do not spend your credits.

Unreachable

You get an alert instead of a silent failure. No run, no charge.

Need it today

Run it now from the policy, without waiting for the next scheduled check.

Guardrails

Policies cap what automatic runs can spend. Monthly and per-user limits are next.

One send, three readers, and a page that keeps moving.

Get started

Test the next send before it goes out.

Send us the subject lines and the body. We score every combination.