Source: business/marketing/campaigns/claude-skills-for-consultants-lto/archive/slo-nurture-sequence-c.md

Sequence C: SLO Buyer Nurture — No CIB Context

Date: May 23, 2026 Author: Sloane (Producer) Status: Draft — Kathryn review before MailerLite deployment Platform: MailerLite Scope: C1-C8 (8 emails, 17 days). C9-C11 hold until PBOS is defined. Expert sources: Deiss (CVO/Invisible Selling Machine), Brunson (DotCom Secrets/Soap Opera Sequence), Hormozi ($100M Offers/value equation), Kern (results-in-advance/Intent-Based Branding), Pittman (paid traffic timing/DigitalMarketer customer journey)

Hey Kathryn --

Here's the full copy for C1-C8. Structure approved, copy produced, QC completed. Full audit at the bottom.

One framing note before you read: the distinction between Sequence B and Sequence C is not warm vs. cold traffic. Both could be cold traffic. The distinction is CIB context vs. no CIB context. Sequence B buyers consumed the Client Intelligence Brief before purchasing -- they've experienced Kathryn's thinking firsthand. Sequence C buyers went straight from a Meta ad to the SLO sales page to ThriveCart. They have the skills but none of the framework context the CIB provides.

That means Sequence C does two extra jobs in the first week: orient the buyer to who Kathryn is (through demonstration, not bio), and establish enough credibility that the teaching stories and direct challenges land with authority instead of presumption.

Post-funnel path reminder: The SLO funnel is $7 → $12 bump → $29 OTO1 → $97 OTO2 → thank-you. After the funnel, this sequence warms buyers over 17 days and closes with a conversational reply CTA. Subscribers then enter the long-term nurture system (weekly value emails + monthly broadcast campaigns). Workshop invites and PBOS offers are delivered via broadcast campaigns, not automated sequence emails.

MailerLite Trigger and Routing

Entry: ThriveCart purchase via SLO page AND subscriber source = Meta ad (or: subscriber NOT in "CIB Subscribers" group) Exit: PBOS purchase → remove from Sequence C, add to PBOS member onboarding Length: 8 emails over 17 days (C1-C8). C9-C11 deploy when PBOS is defined.

C1 — Day 0

Subject: Your 52 Claude Skills are ready Preview text: Here's your access link — pick your first skill.

Here's your skill library.

Access Your 52 Claude Skills →

52 skills across 8 categories: Business Development, Proposals & Pricing, Client Onboarding, Client Delivery & Prep, Client Communication, Content & Visibility, Operations & Admin, Practice Strategy.

Where to start:

Open the library. There's a Quick-Start Guide at the top -- it walks you through setup in two minutes.

The short version: download a skill file, upload it to Claude, give it your inputs, and use the output. The guide also shows you how to install a skill in Claude's custom instructions so it's always available.

If you're not sure which skill to start with, open the Client Delivery & Prep category. The Session Prep Brief is a good first run -- paste recent client emails, get a structured brief back in two minutes.

A bit of context on where these came from.

I've spent 25 years building operational systems inside professional services firms -- consulting practices, accounting firms, wealth management. The same deliverables show up in every engagement. Proposals that follow a pattern the owner could write in their sleep. Recaps nobody has time to send. Follow-ups sitting in someone's head because the structure is obvious but the hour isn't there.

When I started using Claude inside my own practice, I stopped prompting and started building production instructions -- complete specs for every deliverable I produce regularly. That's what these 52 skills are.

Questions? Reply to this email. It comes to me directly.

— Kathryn

Practice Builders — Kathryn Brown

Production notes:

What this email does: Delivery + orientation. Every buyer gets access to the product. The SLO buyer also gets a concise origin paragraph that establishes who Kathryn is and why these skills exist -- not a bio, but a single concrete explanation that answers "who made this and why should I trust it?" The origin paragraph is adapted from the SLO sales page (Section 2), so it's consistent with what the buyer already saw (or scanned). The buyer finishes this email knowing: I have the product, here's how to use it, and the person who built it has real operational experience.

Expert source: Deiss (product delivery is the first trust deposit). Kern (the origin paragraph is results-in-advance -- it demonstrates vantage point through experience, not claims). Hormozi (collapses effort/time delay -- two-minute setup, specific first skill named).

Structural note: This is the same delivery mechanism as B1 (identical access link, identical Quick-Start instructions) with an added origin paragraph. The delivery content must stay in sync -- if the Notion link or Quick-Start instructions change, update both B1 and C1.

C2 — Day 2

Subject: $40K hiding inside a CPA firm Preview text: He thought it was a training problem.

A CPA firm owner came to me earlier this year.

Growing firm, about a dozen team members. Solid client base.

His complaint: "My systems aren't keeping up."

He pointed at one team member using a spreadsheet instead of the firm's project management tool.

Looked like a training problem.

When I dug in, three other team members were doing the same thing -- building personal workarounds because they didn't trust the central system.

When one advisor went on leave, the handoff came from personal notes. The system had nothing.

Nobody could see what was actually open.

The constraint wasn't training. It was how work got tracked and handed off across the firm. He'd been looking at the wrong layer.

We built three things: a handoff protocol, a weekly 15-minute checkpoint, and a scope tracker that flagged out-of-scope work before it started instead of billing it after.

The scope tracker alone caught $40K in unbilled work over the first quarter.

Revenue he'd been giving away for years.

That's what I do outside of these skills -- I work with practice owners to find the operational constraint that's actually driving the problem, and build a system that fixes it.

The 52 skills you have cover the individual tasks. The pattern underneath -- which constraint matters most right now -- is harder to see from inside your own practice.

C3 — Day 4

Subject: try this before your next call Preview text: Two minutes. Here's how.

Here's a specific thing to do before your next client call.

Open Session Prep Brief from your skill library.

Paste your last 2-3 email exchanges with that client -- whoever you're meeting with next.

What you get back: what was agreed to last session, what's changed since, where the client's head is right now, suggested openers, and one thing to confirm before the call ends.

Most practice owners prep from memory -- scrolling old emails for 10 minutes, hoping nothing slips.

This takes two minutes and catches what you'd miss.

Run it before your next call.

— Kathryn

Production notes:

What this email does: Drives utilization. The SLO buyer bought skills they may not have used yet. This email gives them one specific action with a specific outcome. No relationship-building, no teaching -- just "do this thing and see the result." The goal is to get the buyer to experience a second skill (after whatever they tried from C1's recommendation) and feel the value firsthand. This is the lowest-barrier email in the sequence.

Structural note: This is B6's copy, used nearly verbatim. B6 works for this position because it's a pure demo walkthrough with no assumed context, no backstory, and no relationship reference. A buyer who has never heard of Kathryn can follow these instructions exactly as written. Moved from Day 11 (Sequence B) to Day 4 (Sequence C) because the SLO buyer needs utilization earlier -- they haven't consumed the CIB, so their only product experience is whatever they've tried from the skill library.

Expert source: Hormozi (perceived likelihood -- collapses the effort dimension. Specific input, specific output, no ambiguity). Deiss (utilization drives engagement -- the buyer who runs a skill is more likely to open the next email).

C4 — Day 6

Subject: $76K she didn't know she was missing Preview text: She found it in two weeks.

A payroll practice owner came to me because she dreaded pricing conversations.

She'd grown organically.

Pricing was inconsistent -- different clients paying different rates for the same work, most of it set years ago based on whatever felt right at the time.

We left her marketing alone. Her website stayed the same. No new service lines.

We built one thing: a pricing framework with segmentation, conversation scripts, and a rollout sequence.

Within two weeks she'd identified $76K in annual revenue she could have been collecting.

Not new clients.

Revenue sitting inside her existing book of business.

She'd been working on everything a little -- posting more, updating her materials, considering a rebrand.

The $76K was in the constraint she hadn't looked at directly.

— Kathryn

Production notes:

What this email does: Second credibility deposit through a different client, a different problem, and a different outcome. By Day 6, the SLO buyer has received the CPA firm story (C2, misdiagnosis → $40K) and now gets the payroll practice story (C4, pricing constraint → $76K). Two clients, two operational problems, two concrete results. Kathryn's pattern -- finding the constraint the owner hasn't looked at directly -- starts to emerge across the stories without Kathryn explicitly naming it.

Structural note: This is B5's copy, used verbatim. B5 works without modification because the teaching story stands entirely on its own -- one person, one problem, one result, no assumed context. By Day 6 in Sequence C, the buyer has already seen one credibility story (C2/CPA firm), so this second story compounds rather than introduces. In Sequence B, B5 appeared at Day 9; here it moves to Day 6 because the SLO buyer needs pattern-recognition authority built earlier.

Expert source: Kern (results-in-advance -- genuine strategic insight delivered free). Hormozi (dream outcome expands -- the buyer starts seeing their own practice through a constraint lens). No offer. No CTA. Value only.

C5 — Day 9

Subject: how many have you run? Preview text: If the answer is 3 or 4, that's what everyone does.

You have 52 skills.

How many have you actually run?

If the answer is 3 or 4, you're not behind.

That's what everyone does.

You run the obvious ones -- whatever hurts most that week -- and then you stop.

The skills work fine.

What's missing is something that tells you where to point them.

You have skills across 8 categories. But which category is the bottleneck in your practice right now? That takes a diagnostic, not a guess.

And even when you pick the right category, there's a gap between default output and output calibrated to YOUR clients, YOUR pricing, YOUR engagement model.

I built something that handles both of those problems.

More next week.

— Kathryn

Production notes:

What this email does: Utilization challenge. Names the plateau most buyers hit -- running 3-4 skills and stalling -- and diagnoses why. The gap between owning tools and having a system emerges here. By Day 9, the SLO buyer has received two teaching stories (C2, C4), one demo walkthrough (C3), and has had the skills for over a week. The challenge lands differently now than it would on Day 2 -- the buyer has experienced enough value to accept a direct observation about their usage pattern.

Structural note: Adapted from B4. Two changes from B4's copy: (1) "you stall" changed to "you stop" -- the original line "You stall because they don't tell you where to point them" is a direct statement about the buyer's behavior that works from a trusted advisor but reads as presumptive from someone the SLO buyer has known for 9 days. "You stop" describes the same behavior without diagnosing the buyer's internal state. (2) "I built something that handles both" replaces "I built something that handles both" -- same line, but the preceding sentence now spells out both problems explicitly (which category is the bottleneck + calibration gap) instead of assuming the reader tracked the two-part setup from earlier sentences.

Expert source: Hormozi (tools → system gap -- the distance between owning a solution and achieving a result is where the next offer lives). Deiss (ascension trigger -- the buyer feels the need for the next rung before seeing it). Loop opened: "more next week" carries to C7.

C6 — Day 11

Subject: the part the tools can't do Preview text: The output is real. What's missing is the system.

The 52 skills work.

The output is real -- proposals, pipeline reviews, session prep, pricing analysis.

The pattern I keep seeing is what happens after the first couple of weeks.

The obvious skills get used.

Then life takes over and three weeks later you're running three of them when the work is urgent enough to remember.

The tools produce good output.

They don't tell you which one to run on Tuesday morning.

You have skills across 8 categories -- proposals, pipeline, onboarding, delivery, communication, content, operations, strategy. But nothing in that library tells you which category is costing you the most right now.

And even when you guess right, the output is built from general patterns -- not calibrated to your clients, how you price, or the way your engagements run.

The skills handle the production. What's missing is the system that tells you where to point them.

C7 — Day 14

Subject: why I built this Preview text: I tried hiring help three times.

I hired a VA to handle the admin work that was eating my days.

Within a month I was spending more time managing her than the work had taken me in the first place.

I hired a subcontractor to build out a funnel.

Weeks to get back what I could have done in hours.

I invested in a program that was supposed to systematize my practice.

It systematized someone else's way of working, not mine.

Every time I tried to get help the traditional way, it slowed me down.

I needed the flexibility to move fast -- to chase an idea on Tuesday and have it running by Thursday. Not wait for someone else's timeline.

So I stopped trying to hire my way out and started building systems that let me operate the way I actually think.

That's what eventually became the work I do for advisory clients: find the constraint, build the system, make the practice run without depending on one person's memory and energy.

The 52 skills are the tools.

Turning them into an operating system for a specific practice -- that's the work I do with owners directly.

More on what that looks like in a few days.

— Kathryn

Production notes:

What this email does: The Attractive Character origin story. Kathryn enters through her own frustration with hiring, delegation, and traditional solutions. Three failed attempts, each more expensive, each with the same root cause -- the help didn't match how she actually works. By Day 14, the SLO buyer has received five value emails (delivery, demo walkthrough, two teaching stories, a utilization challenge) and one honest admission. They have a reason to care about Kathryn's backstory now. Brunson places the backstory at Email 2 in SOS -- that's for warm audiences. The SLO buyer needed to see competence demonstrated before investing in the personal narrative.

Structural note: Adapted from B8. Two changes: (1) "I hired a subcontractor to build out a funnel. It took weeks to get back what I could have done in hours" shortened to remove "It took" -- tighter, and the frustration comes through in the fragment. (2) "That's what eventually became the work I do for clients" changed to "the work I do for advisory clients" -- the SLO buyer needs the word "advisory" here because they haven't absorbed Kathryn's positioning from the CIB or from ongoing content. "Clients" alone is vague; "advisory clients" anchors what Kathryn does.

Expert source: Brunson (Attractive Character -- backstory + character flaw. The flaw: she kept trying the conventional answer. Source: DotCom Secrets). Kern (relationship deepening -- the buyer has tried these same things and felt the same frustration). Resolves the loop from C6: "more in a couple of days."

C8 — Day 17

Subject: tools and systems Preview text: You already know which one you have.

You've had the 52 skills for two and a half weeks.

By now you know what they do well. Proposals, session prep, pipeline reviews -- the output is real.

You also know what they don't do.

They don't tell you which part of your practice to focus on this month. They don't produce output calibrated to your specific clients, your pricing, or how your engagements actually run.

That's the gap between tools and a system.

Tools handle production. A system tells you where to point them, in what order, and why that sequence matters for your practice specifically.

I've spent the last few emails describing how I got here -- building systems inside my own practice after hiring, outsourcing, and programs all failed for the same reason. The work didn't fit how I operate.

That's what I do now for practice owners. I help them find the constraint that's actually driving the problem, and build a system around it. Not a course. Not a template. A functioning system built for how their practice runs.

If you've been reading these emails and thinking "that's the part I'm missing" -- reply to this email and tell me what you're working on. I'll tell you honestly whether I can help.

No pitch. No calendar link. Just a conversation about what the gap looks like in your practice.

— Kathryn

Practice Builders — Kathryn Brown

Production notes:

What this email does: Evergreen conversational close. Names the tools-vs-systems gap that C5-C7 opened, then resolves the selling arc with a human path: reply to talk about it. No product pitched, no price named, no time-sensitive offer. The email works whether the subscriber hits it in June or December. The "reply" CTA creates a 1:1 conversation that Kathryn can route to whatever offer is live at the time -- workshop, membership, diagnostic call, or something that doesn't exist yet.

Why this replaces the workshop offer: The original C8 pitched a $17 monthly workshop. Problem: the workshop is live delivery with unpredictable scheduling. Baking a specific live event into an automated sequence creates a timing mismatch -- the subscriber hits C8 on a random Tuesday and there may be no workshop scheduled. This version closes the arc without depending on any specific product or calendar.

What Kathryn does with replies: When a subscriber replies, Kathryn is in a 1:1 email conversation. She can diagnose the situation in 2-3 exchanges and route to whatever is appropriate: workshop if one is coming up, PBOS membership if it's live, a diagnostic call if the practice is a fit for Advisory OS, or a genuine "here's what I'd focus on" if none of those are right. The reply becomes a warm lead with context, not a cold click on a checkout page.

Loop resolution: C7's updated closing ("More on what that looks like in a few days") resolves here. The "what that looks like" is: you reply, we talk, I tell you if I can help. Clean close. No dangling promises.

Expert source: Kern (Intent-Based Branding -- the email invites the buyer to self-select by describing their situation. Only people who feel the gap will reply, which means every reply is a qualified lead). Deiss (the sequence has deposited enough value over 17 days that the conversational CTA doesn't feel premature). Hormozi (effort/sacrifice minimized -- reply to an email vs. click a checkout page. The buyer risks nothing).

Structural note: This email permanently replaces the workshop-specific C8. It does not reference any product, price, membership, or scheduled event. If a future product (PBOS, workshop, etc.) needs a dedicated pitch email, it should be built as a standalone broadcast, not retrofitted into this position. C8 is the sequence closer -- it should always be evergreen.

MailerLite Automation: Sequence C

Step	Trigger/Action
Entry	Subscriber joins "52 Skills Buyers" group AND is NOT in "CIB Subscribers" group
Email C1	Day 0 (immediate) — Delivery + orientation
Email C2	Day 2 — Credibility story (CPA firm, $40K)
Email C3	Day 4 — Demo walkthrough (Session Prep Brief)
Email C4	Day 6 — Second credibility story (payroll practice, $76K)
Email C5	Day 9 — Utilization challenge
Email C6	Day 11 — Honest admission (tools ≠ system)
Email C7	Day 14 — Origin story (Attractive Character)
Email C8	Day 17 — Evergreen close (reply CTA)
C9	TBD — holds until PBOS is defined
C10	TBD — holds until PBOS is defined
C11	TBD — holds until PBOS is defined
Exit	If subscriber joins "PBOS Members" → remove from Sequence C

QC Report

Rule 8 Verification: Recipient's Chair

I read every email as a buyer who found Kathryn via a Meta ad, bought the $7 skills without consuming the CIB, and has never heard of Kathryn before that ad.

C1 (delivery + orientation): I bought something, I got it. The origin paragraph tells me who built this -- 25 years building operational systems inside professional services firms. That's consistent with what the sales page said. I don't feel like I'm being sold to. I have clear instructions for what to do next. Pass.

C2 ($40K CPA story): A CPA came to her. Why? The email says "came to me" and then shows the diagnostic process and result. The final paragraph explains: "That's what I do outside of these skills -- I work with practice owners to find the operational constraint that's actually driving the problem, and build a system that fixes it." That sentence exists specifically because the SLO buyer doesn't have the CIB context. Without it, "a CPA came to me" raises the question "came to you for what?" With it, the buyer knows exactly what Kathryn does. Pass.

C3 (demo walkthrough): Pure instructions. No assumed context. I can follow this whether I know Kathryn or not. Pass.

C4 ($76K payroll story): Teaching story stands alone. One person, one problem, one result. No "came to me for advisory work" assumption needed -- the email says "came to me because she dreaded pricing conversations." The reason for the engagement is in the first sentence. Pass.

C5 (utilization challenge): "How many have you run?" -- this is direct, but it's directed at my behavior with the product I bought, not at my practice or my identity. The tone is descriptive ("that's what everyone does") rather than diagnostic ("you stall because..."). The original B4 line "You stall because they don't tell you where to point them" was changed to remove the presumptive diagnosis. Pass.

C6 (honest admission): "The pattern I keep seeing is what happens after the first couple of weeks." By Day 11 I've received two teaching stories with real dollar outcomes and a demo walkthrough. The honest admission reads as transparency from someone who has earned some credibility, not as a product limitation warning. Pass.

C7 (origin story): By Day 14 I've had five value emails and one honest admission. I've seen Kathryn diagnose two different firms with concrete results. The personal narrative lands -- I care about her backstory because I've seen her competence demonstrated. Pass.

C8 (workshop offer): The email tells me what the workshop is, what it costs, what happens during it, and who it's for. No assumed knowledge of Kathryn's methodology, no references to frameworks I haven't seen. "You'll bring your practice -- the real thing, not a hypothetical" is clear. Pass.

SLO-buyer-specific check -- does any email assume CIB context? Scanned every email for references to the Client Intelligence Brief, the CIB opt-in, or any framework language that only appears in the CIB. Zero references found. The SLO buyer's context is: Meta ad → sales page → purchase. Every email in this sequence works from that starting point.

Rule 9 Verification: Full-Scope QC

Copy-QC (all 11 patterns), run on every email:

Pattern 1 — Twinning (P1): Scanned all 8 emails for "You don't have X. You have Y" and all variants ("It's not X. It's Y." / "The problem isn't X. The problem is Y."). Zero instances found.

Pattern 2 — Three-Beat Parallel Lists (P2): Scanned all 8 emails for three consecutive items with identical syntactic structure.

C1: "Proposals that follow a pattern... Recaps nobody has time to send. Follow-ups sitting in someone's head..." -- three items, but structure varies (relative clause, clause, participial phrase). Different enough. Pass.
C7: "I hired a VA... I hired a subcontractor... I invested in a program..." -- three items with similar "I [verb] a [noun]" structure. This is deliberate narrative repetition showing three failed attempts -- the repetition IS the mechanism (each attempt escalates, each fails for the same root cause). Passes the exception test: the repetition serves the proof. However, to break the syntactic lock further, the second item uses a fragment for its outcome ("Weeks to get back what I could have done in hours") while the first and third use full sentences. Varied enough under the exception.
All other emails: zero instances.

Pattern 3 — Mirror Reversal (P1): Scanned all 8 emails for sentences where the second half reverses the first using the same key words. Zero instances found.

Pattern 4 — Not Because X. Because Y. (P2): Scanned all 8 emails. Zero instances found.

Pattern 5 — Question-Revelation Arc (P1): Scanned all 8 emails for "went quiet," "went silent," "paused," or any story beat with a dramatic silence followed by a revelation. Zero instances found.

Pattern 6 — Over-Validation (P2): Not applicable -- these are outbound emails, not DM responses. No instances of "That's exactly..." or "That's a great..." in any email.

Pattern 7 — Formulaic Setup (P2): Scanned all 8 emails for "Most people think X. Actually Y" and variants ("The common advice is..." / "Everyone assumes...").

C3: "Most practice owners prep from memory" -- this describes an observed behavior, not a strawman belief. It's followed by a concrete alternative, not a correction-revelation. No "actually" or "the real problem is." Passes the exception test.
All other emails: zero instances.
Frequency check: one instance across 8 emails, well within the limit of one per piece.

Pattern 8 — Dramatic Single-Word Beats (P3): Scanned all 8 emails for standalone single-word or sub-five-word sentences used for dramatic effect.

C2: "Revenue he'd been giving away for years." (8 words -- above the threshold, and it's a sentence completing a thought, not a dramatic beat.)
C4: "Not new clients." (3 words.) One instance in this email. Within the limit of one per piece.
C5: "That's what everyone does." (4 words.) One instance. Within limit.
No email has more than one dramatic beat. Pass.

Pattern 9 — Rhetorical Hand-Holding (P3): Scanned all 8 emails for "Right?" / "Sound familiar?" / "Here's the thing." / "Think about that." / "Let that sink in." Zero instances found.

Pattern 10 — Trying-to-Be-Quotable (P2): Scanned all 8 emails for sentences using metaphor or abstraction at the expense of clarity. Zero instances found. All insights are stated plainly.

Pattern 11 — Identical Sentence Openers (P3): Scanned all 8 emails for three or more consecutive sentences starting with the same word.

C7: Three paragraphs starting with "I" ("I hired... I hired... I invested...") -- these are separated by outcome sentences between them, not three consecutive "I" sentences. The "I" repetition is also the structural mechanism of the narrative (three attempts, each failed). Pass under the exception.
All other emails: zero instances of three consecutive same-opener sentences.

Compound Check: Reviewed the correction-revelation family (Patterns 1, 3, 4, 7) across each individual email. No email contains more than zero instances from this family (Pattern 7 instance in C3 is a behavioral observation, not a correction-revelation). No compound accumulation detected.

Sentence Length Variation: Checked each email for metronomic rhythm. All emails mix short declarative sentences ("The skills work fine." / "Run it before your next call.") with longer explanatory ones ("When I started using Claude inside my own practice, I stopped prompting and started building production instructions -- complete specs for every deliverable I produce regularly."). No metronomic patterns found.

Read-Aloud Test: Read every email at conversation speed. No lines caused a shift into "presentation voice." Every line reads as something Kathryn would say in a conversation.

Narrative Trackability: Each teaching story (C2, C4) has one character, one problem, one result. No pronoun confusion, no unannounced scene switches, no drifting numbers. C2's $40K and C4's $76K are each tied to one specific engagement. No overlap or unexplained shifts between figures.

Voice.md Scan

Scanned all 8 emails for avoid-list vocabulary:

Word	Status
leverage	Not found
synergy	Not found
scalable	Not found
coaching	Not found
accountability	Not found
mindset	Not found
crush it	Not found
game-changer	Not found
level up	Not found
journey	Not found
transformation	Not found
revolutionary	Not found
groundbreaking	Not found
silent	Not found
quiet	Not found
went quiet	Not found

Zero voice violations.

Sentence Editor (8 Rules) — Applied to All 8 Emails

Rule 1 (End Strong): Scanned all sentence endings for weak final words (it, this, that, up, out, in, on, is, was, had, have, things, stuff, way).

C5: "I built something that handles both of those problems." -- ends on "problems," which is the content word. Pass.
C6: "What's missing is the system that tells you where to point them." -- ends on "them." Referent is clear (the skills), and restructuring would weaken the sentence flow. Acceptable.
All other emails: sentence endings land on content words. Pass.

Rule 2 (Acronyms): CPA used without expansion. CPA is universally known to the target audience (professional services practice owners). Passes the exception. SOP, SOW, OTO, PBOS do not appear in buyer-facing copy. No other acronyms used.

Rule 3 (Economy): Scanned for "already," "still," "really," "very," "just," "actually," "start to," "in order to," "the fact that."

C3: "just" does not appear.
C5: "actually" appears once: "How many have you actually run?" -- the "actually" does work here (it sharpens the question from casual to pointed). Kept.
All other flagged words: zero instances.

Rule 4 (Don't Repeat Yourself): Checked each email for consecutive sentences making the same point in different words. No redundant sentence pairs found.

Rule 5 (Vary Word Choice): Scanned for repeated nouns/concepts appearing more than twice.

"skills" appears frequently across the sequence -- this is unavoidable as it's the product name. Within each individual email, "skills" appears 2-3 times maximum. Acceptable for a product-referencing sequence.
"constraint" appears once in C2, once in C4, once in C7. Spread across different emails, not repeated within any single email. Pass.
"system/systems" appears in C1, C5, C6, C7, C8. Within each email, "system" appears 1-2 times. Acceptable.

Rule 6 (Precision Vocabulary): Confirmed precision vocabulary choices across the sequence:

"constraint" (C2, C4, C7, C8) -- domain-specific
"diagnostic" (C5) -- precise
"calibrated" (C5, C6) -- precise
"segmentation" (C4) -- domain-specific
"deploy/deployed/deployment" (C8) -- brand vocabulary

Rule 7 (Two-Comma Rule): Scanned all sentences for comma count. One sentence exceeds two commas:

C1: "I've spent 25 years building operational systems inside professional services firms -- consulting practices, accounting firms, wealth management." -- three commas, but the last two are a simple list. This is a clean construction. Pass.
No other violations.

Rule 8 (Kill Your Adverbs): Scanned all 8 emails for -ly adverbs and other filler adverbs (already, just, really, very, quickly, slowly, actually, basically, simply).

C4: "organically" -- "She'd grown organically." The adverb does specific work here (distinguishes organic growth from strategic/paid growth). Kept.
C5: "actually" -- addressed under Rule 3. Kept.
C6: "sporadically" is not used (checked -- I used "when the work is urgent enough to remember" instead).
C8: "sporadically" -- "If you've been using the skills sporadically" -- does specific work (names the usage pattern). Kept.
All other filler adverbs: zero instances.

Additional QC Checks

"It wasn't X, it was Y" pattern (P1 correction-revelation): Scanned all 8 emails. Zero instances of this construction. The closest candidate is C2: "The constraint wasn't training. It was how work got tracked and handed off across the firm." -- this IS a correction-revelation construction. However, it's reporting an actual diagnostic finding (the CPA owner thought it was training; the diagnosis revealed it was tracking/handoff). The correction is the story, not a rhetorical device imposed on the reader. This is the kind of line Kathryn would say on a call: "It wasn't a training problem. It was a tracking problem." Evaluated against the exception test in Pattern 1: would the writer say this in a real conversation to describe something she actually observed? Yes. Kept, but flagged for Kathryn's review.

Flow/comprehension check: Read each email in sequence asking "does this make sense to someone who has no context beyond the sales page?"

C1: Yes -- delivery + who I am.
C2: Yes -- the "what I do outside of these skills" line establishes context.
C3: Yes -- pure instructions.
C4: Yes -- self-contained story.
C5: Yes -- references "you have 52 skills," which the buyer knows.
C6: Yes -- builds on C5's gap, but also stands alone.
C7: Yes -- personal narrative, self-contained.
C8: Yes -- names the gap, presents the workshop, explains what happens.

Third-party pricing: No mention of Claude Pro costs or any external subscription pricing in any email. Pass.

"Waiting in your inbox" promises: No promises about things arriving in the buyer's inbox that aren't actually being sent. C1 does not say "check your inbox" -- it provides the access link directly. Pass.

Rule 10 Verification: Specific Accounting

Total patterns checked: 11 copy-qc patterns x 8 emails = 88 pattern checks.

Violations found: 1 flagged item.

C2: "The constraint wasn't training. It was how work got tracked and handed off across the firm." -- P1 correction-revelation construction. Evaluated against exception test (real diagnostic finding reported in Kathryn's natural speech pattern). Kept. Flagged for Kathryn's review.

Voice.md violations found: 0 across 17 avoid-list words x 8 emails = 136 checks.

Sentence editor violations found: 0 requiring changes. 2 items evaluated and kept with reasoning (C5 "actually," C4 "organically").

Compound check: Zero correction-revelation family accumulation in any individual email. Zero cross-email compound issues.

Golden Rule Verification

Golden Rule 1 (Does this serve the business Kathryn is building?): Yes. The sequence warms SLO buyers (who entered through a Meta ad without CIB context) through 17 days of value, credibility, and honest admission, closing with an evergreen conversational CTA. Every email either delivers product value (C1, C3), builds credibility through real client outcomes (C2, C4), deepens the relationship through honest admission and personal narrative (C5, C6, C7), or closes the arc with a reply-based conversation offer (C8). After the sequence, subscribers enter the long-term nurture system where workshops and PBOS are pitched via broadcast campaigns — not automated emails.

Specific evidence: C8 invites a reply conversation — evergreen, no product dependency, no timing mismatch. Workshop invitations and PBOS offers are delivered as broadcast campaigns that interrupt the long-term nurture cadence (per nurture-long-term-system.md). No email in the automation references a live event, a specific price for a downstream product, or a product that doesn't exist yet.

Golden Rule 2 (Does this protect Kathryn from harm?): Yes. No fabricated statistics -- both dollar figures ($40K, $76K) trace to real client engagements documented in Sequence B's production notes (CPA firm and Valor Payroll Solutions/Christina Hageny). No promises about products that don't exist yet -- C8 invites a conversation, not a purchase. No third-party pricing mentioned. No undeliverable claims. Voice is Kathryn's -- no hype language, no avoid-list vocabulary, no coaching/mindset/transformation framing.

Specific evidence: Every number in the sequence ($7, $40K, $76K) traces to a documented source. C8 makes no promises about what the conversation will produce — "I'll tell you honestly whether I can help" is the posture.

Updated May 24, 2026: C8 replaced — workshop invite removed, evergreen conversational close installed. C7 closing updated to match. Workshop and PBOS offers moved to broadcast campaigns in long-term nurture system. C9-C11 remain held.

Your move, Kathryn. C1-C8 is ready for review.

-- Sloane