← Vault Index
business / marketing / campaigns / practice-builders-os / wip / waitlist-nurture-sequence.md
Source: business/marketing/campaigns/practice-builders-os/wip/waitlist-nurture-sequence.md

Build Waitlist Nurture Sequence

Audience: Subscribers who joined the Build waitlist from thepracticebuilders.ai/the-build Goal: Warm over 30 days so subscribers are ready for either (a) a Build announcement or (b) the PBOS founding open (~mid-May). Offer Practice Command Center as immediate action throughout. Platform: MailerLite automation, triggered after the Waitlist Welcome Email Cadence: 7 emails over 30 days From name/email: Kathryn Brown

Sequencing

After Email 7: subscriber sits on the broader Practice Builders list. Receives broadcast emails (launch announcements, PBOS open, next Build scheduled, occasional value pieces) but no further automated sequence.

Automation rules:

Email 1 — Day 2

Format: Descriptive Subject: What The Build actually builds

Preheader: A specific answer, in case "live event" was vague.

"Live event" covers a lot. Let me be specific about what The Build actually builds.

Three systems, installed on your machine, in one sitting, with real data from your practice.

Find. A system that scans your existing client base for expansion opportunities — clients using one service who could use three, relationships overdue for a conversation, referral paths nobody's acting on. Runs weekly. Surfaces what's sitting in plain sight.

Prove. A system that turns a completed engagement into a case study, a testimonial request, and a set of posts — in your voice. You finish the work, the system gives you the proof artifacts. You pick what to use.

Close. A system that turns a prospect conversation into a scoped, priced proposal with the relevant proof attached. Your pricing logic, your terms, ready to send the same day.

Each system is an assembly of skills working together on one outcome. Installing all three in one sitting means you leave with three new operational layers in your practice.

When the next Build is scheduled, you'll know before it goes public. Until then, if you want the five standalone skills that feed into these systems:

Get the Practice Command Center — $7 →

— Kathryn

Email 2 — Day 5

Format: Educational Subject: The thing that makes most AI output generic

Preheader: And the one fix that moves everything forward.

Most AI output in professional services practices is generic. Not because the tools are bad.

Because the tools don't know the practice.

The AI doesn't know what services you actually offer. It doesn't know your client base. It doesn't know how you price. It doesn't know how you write an email. It doesn't know what makes your practice different from five others in your city. It doesn't know what you would refuse to do on principle.

So it gives you answers that could apply to anyone — which is the same as answers that apply to no one.

Fixing this is what the Practice Brain is for. It's a one-time interview that builds 6 documents about your practice — services, clients, voice, pricing, outcomes, operating rules. Every skill or system you install after that reads from the Practice Brain. The output stops being generic, because the AI now has context.

In The Build, the Practice Brain is the first thing installed — before the three systems. In the Practice Command Center, it's included as the foundation for the five skills.

Either way, it's the single thing that moves AI output from "generic" to "specific to your practice."

If you want to install the Practice Brain plus five skills this week rather than wait for the next Build:

Get the Practice Command Center — $7 →

— Kathryn

Email 3 — Day 9

Format: Pattern reveal Subject: You are the bottleneck (and it's not your fault)

Preheader: The structural pattern most practice advisors never name.

A pattern I've watched in dozens of professional services practices over the last decade:

The owner is the bottleneck.

Not because they're slow. Not because they're disorganized. Because every piece of meaningful work — the SOW, the advisory note, the follow-up, the scope negotiation, the content, the referral intro — requires their judgment. And their judgment only exists in their head.

This isn't a process problem. It's a knowledge-architecture problem.

If the owner's judgment is the raw material for every output, and the only place that judgment lives is between their ears, then the owner becomes the rate-limiter for the whole practice. Every additional client adds friction. Hiring doesn't fix it (because the new person doesn't have access to the judgment). Systems don't fix it (because most systems capture process, not judgment).

What does fix it: moving the judgment out of the owner's head into a form that can be referenced and reused.

That's what the Practice Brain does — in miniature. Six documents that make the owner's operating logic accessible to any AI tool the practice runs.

Not a full solution. But the first structural move. Once the judgment is externalized, you can build systems that leverage it instead of systems that bypass it.

Get the Practice Command Center — $7 →

— Kathryn

Email 4 — Day 14

Format: Story / use case Subject: 3pm on a Tuesday

Preheader: What this actually looks like, not in the abstract.

It's 3pm on a Tuesday.

You just finished your third client call of the day. You have a 4pm with a prospect, and the discovery notes from last week's conversation are somewhere in your inbox. You open the thread, start scrolling back, and realize the only way to prep is to re-read twenty minutes of back-and-forth.

You don't have twenty minutes. You have forty-five.

Two of those forty-five minutes go to opening the Client Intelligence Brief in Claude (or whichever AI tool you use), pasting in the last five emails from the prospect thread, and running the skill.

What comes back is a structured brief:

You skim the brief. You walk into the call prepared.

This is one skill, run on one client thread, in two minutes.

Now imagine the same rhythm for a weekly scan of every client's inbox (Hidden Revenue Scan), for turning prospect conversations into scoped proposals (Scope-to-SOW), for generating content from finished engagements (Content-from-Delivery), for surfacing unclaimed referrals from your roster (Referral Activator).

That's the Practice Command Center. Five skills. One Practice Brain. $7.

Get it here →

— Kathryn

Email 5 — Day 19

Format: Punchy positioning Subject: Prompts are not the answer

Preheader: And if they've been failing you, this is why.

The AI conversation in professional services has been stuck on prompts for two years.

Copy this prompt. Paste that prompt. Save this prompt. Share that prompt.

A prompt is a request. You type it. The AI answers once. The thread is gone.

That's fine for a one-off. It's useless for a practice.

Because the work in a practice is recurring. Every week has call prep. Every month has proposals. Every engagement has a follow-up. Every quarter has renewal conversations. If your operating rhythm requires re-typing a prompt every time the work comes up, the AI isn't in your practice — it's a tool you occasionally visit.

A skill is different. A skill is a structured instruction set that you install once and run whenever the work comes up. The output is consistent because the instructions don't change. The context is specific because the Practice Brain feeds it real data about your practice.

Skills compound. Prompts evaporate.

This is why most of the AI content you've seen for "small business owners" or "service providers" hasn't moved your practice. The unit of delivery was wrong.

Skills are the right unit. Five of them plus the Practice Brain, $7, install in five minutes:

Get the Practice Command Center →

— Kathryn

Email 6 — Day 25

Format: Authority / POV Subject: 25 years of watching practices try to scale

Preheader: The pattern that separates the ones that do from the ones that don't.

I've spent 25 years watching professional services practices try to scale.

The ones that succeed aren't the ones with more clients, better marketing, or bigger teams. In the early years, everyone has some of that.

The ones that succeed are the ones where the owner figured out how to move their judgment into a form the practice can run on without them in the room.

That sounds abstract. Concretely, it looks like this:

Client selection. The owner has an internal filter — who they take on, who they don't. In a stuck practice, that filter lives in their head. In a scaling practice, it lives in a written criteria that the rest of the intake process runs against.

Scope. The owner knows what a project should cost. In a stuck practice, every scope conversation is from scratch. In a scaling practice, there's a documented pricing logic that produces consistent proposals without the owner writing each one.

Delivery. The owner has opinions about what "done" looks like. In a stuck practice, that opinion is only checked when the owner reviews the work. In a scaling practice, that opinion is encoded into templates, checklists, and review gates that the work passes through on its own.

Retention. The owner knows which client relationships are healthy and which are drifting. In a stuck practice, that knowledge surfaces when something breaks. In a scaling practice, that knowledge is systematized — a weekly scan, a monthly brief, a quarterly review that surfaces drift before it breaks anything.

What makes this hard is that moving judgment out of the owner's head requires the owner to articulate what they know. Most owners haven't ever had to. The knowledge is tacit.

AI — specifically skills that read structured data about the practice — is the first tool I've seen that makes articulating this work tractable. Not because AI captures the judgment (it doesn't). Because AI gives the owner a forcing function to externalize enough of it that the practice can run on it.

The Practice Brain is the externalization layer. The five skills in the Practice Command Center run on that layer. The Build builds three full systems on top of it. Practice Builders OS adds a new one every month.

Every layer is the same strategic move: judgment out of the head, into a form that can be referenced.

— Kathryn

Get the Practice Command Center — $7

Email 7 — Day 30

Format: Direct + founding capture Subject: What's coming (founding cohort update)

Preheader: Practice Builders OS — founding cohort opening soon.

Two things worth knowing.

One: The next Build isn't scheduled yet. I'll send the date as soon as it's set. No earlier, no placeholder.

Two: Practice Builders OS is opening for founding members in the next few weeks.

Practice Builders OS is a monthly membership where we build a new system together every month. A live Workshop session to build it. A Bench week to implement with support. A Walkthrough where one member shares their build for group feedback. A Review to refine it. Plus the full Toolkit, growing every month with each new Build.

It's the ongoing version of what The Build is as a one-off event. If The Build is three systems in three days, Practice Builders OS is twelve builds a year with the space to actually integrate each one.

Founding cohort opens soon. First 20 members lock in at 50% off their membership, as long as they stay.

If you want first access when founding opens, reply to this email with the word "founding" and I'll send you the details before it goes public.

If not — you're still on the list for the next Build, and I'll be in touch when it's scheduled.

— Kathryn

In the meantime, the Practice Command Center is still live: 5 skills + Practice Brain, $7.

Placeholder inventory

Before loading into MailerLite, verify:

Copy QC notes

What this sequence does NOT do

If PBOS launches during the 30-day window

Rough per-email word counts

Total: ~2,050 words across 7 emails. Reading time for full sequence: ~10 minutes spread over 30 days.