Email 4 — the $97 product · Saturday 2026-08-15

Channel: MailerLite broadcast · Slot: the pair's sell half, following 8/11 Audience: Practice Builders broadcast audience, segment 194625513368585544 Status: BLOCKED — cannot be finalized. The product has no settled name. Voice pass is done; the copy is not shippable. Copy written by: Kathryn, 2026-08-11. Voice pass + QC gate: Sloane, 2026-08-11. Brief: briefs/2026-08-11-you-answered-it-for-them.md

Voice pass on Kathryn's own copy, not a draft. Every change is listed under What I changed. Everything not listed is hers, untouched.

Send date is inferred, not set. The track's rhythm is Tuesday/Saturday (STATUS.md), so the Saturday after 8/11 is 8/15. Kathryn did not name a date for this one. Rename the file if she sets a different slot.

Two blockers:

1. [PRODUCT NAME] is unresolved. Candidates: The Prospect Call System / The Sales Conversation System. See What changes when the name lands below.
2. [LINK] has no URL. No sales page can be verified for a product without a settled name.

Subject lines

Lowercase, per the track's register.

1. what to do with what you found
2. the part that runs on Tuesday ← recommended
3. your sales conversation, start to finish

Option 1 is Kathryn's option 1 with one word removed. She wrote "What to do with what the audit told you." Two problems: the product is no longer called an audit and the word was retired, and it asserts the reader ran something. Her shape survives; the assertion and the retired word are gone.

Option 2 recommended. It is the body's own promise ("something to run on Tuesday"), it is plain, it invents no curiosity gap, and it stays clear of the sales-training register.

Option 3 is accurate and matches the body's "start to finish." It is also the most sales-flavored line in the pair. Keep it as the fallback if the product lands as The Sales Conversation System, and retire it if the product lands as The Prospect Call System — the mismatch between "prospect call" in the product name and "sales conversation" in the subject would read as two different products.

Preheader:

1. Nothing to fill in from scratch. ← recommended
2. $97. Nothing on your calendar.

Option 1 is Kathryn's verbatim body line and it names the actual differentiator: the output is her reader's version, not a template they have to populate. Drawing the preheader from the body's pattern line is the golden's own practice.

Agreement test: subject says there is a part that runs on Tuesday; preheader says you do not build it yourself. They agree, and the preheader carries information the subject does not. Neither implies the fix cannot work.

From / reply-to: Kathryn Brown | Creating Your Plan / kathryn@creatingyourplan.com.

Body

Hi {$name},

Run Question Set Builder on one of your calls and you get the set back, marked up.
You see which questions died and where you handed over the answer.

Knowing that is not the same as having something to run on Tuesday.

[PRODUCT NAME] is what you run.
6 stages, start to finish:

- Take the lead — how you open so the call belongs to you
- Set the stage — why now, and who else decides
- Dig deeper — the question bank, and the reflect-back that makes your recommendation theirs
- Cost of inaction — what staying put costs them in their own dollars, and the first win that covers your fee
- Name it — your price as a range, said out loud, on the call
- Close — book the next call from the call. Never "I'll send you a quote."

You answer questions about your business and it returns your version — your stages, your language, your numbers, your objection lines.
Nothing to fill in from scratch.

$97. Nothing to attend, nothing on your calendar.

[LINK]

— Kathryn

What I changed, and the rule that forced it

Seven edits. Everything else is Kathryn's, verbatim.

Does the fix to the opener depend on segmentation?

No — that is the point of it. Her original asserts the reader ran the skill, which is only true if this send goes to people who clicked email 3. My version asserts nothing about the reader's past, so it is safe on the full broadcast audience.

If she does segment on the email-3 click, her original past tense becomes defensible and is the stronger open, because it starts inside something the reader actually did. In that case the line becomes You ran Question Set Builder on one of your calls. — the word audit still has to go either way.

Not changed, and why:

• Knowing that is not the same as having something to run on Tuesday. → [PRODUCT NAME] is what you run. This is the closest thing in the pair to twinning, and I checked it hard. copy-qc.md Pattern 1 needs two consecutive sentences with the same sentence structure; these are a gerund-subject comparison and a copular identification — different structures, separated by a paragraph break. Pattern 3 needs a root word in reversed positions; run sits in the same position doing the same job in both, which is deliberate linkage, not a mirror. The copy-gate twinning patterns do not fire (verified against the regexes and against the live gate run below). Kept. It is the hinge of the email and cutting it would gut the send.
• Dig deeper. It is the one stage name that leans coachy, and dig deep is on the coach-language ban list for client emails. Renaming a product's stages is not a voice pass, so I did not touch it. Flagged for her only.
• your stages, your language, your numbers, your objection lines. Four items with an identical opener — Pattern 2 and Pattern 11 both fire on the count. Both carry the same documented exception: keep the repetition when the repetition is the mechanism. Here the whole product claim is that the output is customized to the reader, and the four yours are that claim. Kept.
• it returns your version — it reaches back past the 6-item list to [PRODUCT NAME]. The reader has just read that product's stages, so the antecedent holds. Flagged, kept.
• 6 bullets as one thought-group. make-paste-ready.py will warn. Enumerations are that check's documented exception.
• No reply CTA. The golden ends Hit reply — I read every one. This one ends on a link. That is correct for a send with one action — a sell email with two asks gets neither. Not a defect.

What changes when the product name lands

The name appears once in the body, so the swap is a one-line edit either way. What else moves:

If it lands as The Prospect Call System:

• Body line becomes The Prospect Call System is what you run.
• Retire subject option 3. "Prospect call" in the product and "sales conversation" in the subject read as two different products.
• Email 3's copy already primes it — every prospect call is its opening line. The pair reads as one thing.
• Recommended subject stays option 2.

If it lands as The Sales Conversation System:

• Body line becomes The Sales Conversation System is what you run.
• Subject option 3 becomes the natural match and is a live candidate for recommended.
• New risk to re-check before shipping: the product name plus the stage names (Take the lead, Name it, Close) together push the send toward the sales-training register the brief bans. Nothing in the current body crosses that line on its own; the name is what would tip it. If she picks this name, the send needs one more read against that specific constraint — say the word and I will run it.

Unaffected either way: every copy-gate rule. I checked both names against the twinning patterns and the spelled-number pattern; neither name fires anything. The gate result below therefore holds for both.

Length

Body: 186 words, as counted by make-paste-ready.py, against the golden's 158. Within range and no judgment call needed. The 6 stage bullets are the bulk of it, and they are the product.

Source trace — line by line

Stated plainly: I did not open the 7/27 Otter transcript. Everything below traces to a document I actually read. Where a line is Kathryn's own assertion I could not verify, it says so.

Claims cut for lack of a source

• Any outcome from running the 6 stages — more closes, higher prices, fewer quotes sent. The email describes what the product contains and stops. Nothing promises a result.
• Any claim the reader already ran Question Set Builder. Removed in edit 2. This is the single substantive claim I took out of her copy.
• Any delivery detail — format, length, whether it is a skill file, a document, or a page. Not in any source I read, and the email does not need it.
• Any comparison to what else is on the market. Not claimed. feedback-never-lift-competitor-offer-language.
• Any figure for what "cost of inaction" produces. The bullet says the reader computes it in their own dollars, which is true of the mechanic and asserts no number.

QC run — in order

1. Recipient-first. The reader gets a named process with 6 stages, a price, and one action. Passes.

2. Pride Gate. Passes — it hands over a runnable thing rather than teaching.

3. copy-qc.md — the 11 patterns.

• P1 twinning — zero. The one borderline construction is analyzed in full above and kept with reasoning. Never "I'll send you a quote." is a single prohibition, not a mirrored pair.
• P1 mirror reversal — zero. run repeats in the same position, not a reversed one.
• P1 question → silence → revelation — zero.
• Correction-revelation family — zero. No "most people think," no "not because X."
• P2 three-beat parallel — one instance, kept under the documented exception (your stages, your language, your numbers, your objection lines — the repetition is the mechanism). Nothing to attend, nothing on your calendar is 2 items, not 3.
• P2 quotable reach — none.
• P3 dramatic beat — one (Nothing to fill in from scratch.). Under the limit.
• P3 rhetorical hand-holding — none.
• P3 identical openers — the 4 your items, same exception as Pattern 2. No 3 consecutive sentences share an opener.
• Numerals — applied. 6, $97. one of your calls stays spelled per STATUS.md.
• Compound check. One P2 and one P3, both inside documented exceptions, no correction-revelation instances. Under the compound threshold.
• Trackability. One reader, direct address. it flagged above. Two numbers (6, $97) measuring different things, no drift.
• Mobile scannability. One sentence per line, groups of 1–2 outside the enumeration.
• Read-aloud. Passes.

4. linkedin-sentence-editor.md — the 8-rule audit.

5. Banned sweep. No audit (removed), no tape, no walk through, no honest, no quiet/quietly, no carry, no in the room, no held/landed/sit with, no job, no bare block, no practice owner, no hashtags, no hype, no builder jargon. Dig deeper does not match the dig deep ban pattern (no word boundary after "deep") and is flagged for her judgment, not changed.

6. Vertical stripped. No CPA, tax, returns, IRS, or software brand. Every stage name is generic service-provider language.

7. Client clearance. No client appears in any form.

8. Not a repurposed post. Kathryn wrote this as an email. Social overlap checked mechanically by the gate — result recorded below.

Open items for Kathryn

1. The product name. Nothing else about this send can be finalized until it lands. Effects of each choice are spelled out above.
2. The link. No verifiable URL exists.
3. Sequencing dependency. This email opens on Question Set Builder. If email 3's Notion page is still unpublished when this goes out, it opens on something the reader was never able to get. Email 3 has to land first, with a live link.
4. Dig deeper is the one stage name that reads coachy. Flagged, not changed — the stages are yours.
5. Bold the 6 stage names in the MailerLite editor. The markdown is stripped from the body on purpose so literal asterisks cannot ship.
6. The $97 price matches the existing front-end tier. If this is a separate SKU, the checkout needs its own verification before the link goes in.
7. The .txt artifacts do not exist yet. make-paste-ready.py parses this file correctly (186-word body, subject and preheader read out clean), but stops on its brief gate: the Confirmed by Kathryn: line in briefs/2026-08-11-you-answered-it-for-them.md is blank. That is hers to fill, not mine. Nothing would be generated for this send anyway until the product name lands.