Turning your engaged audience into more booked intakes.

The plan in one view

How this plan drives the one thing you want most: more booked intakes

Lifecycle is your lowest-cost route to booked intakes. It converts demand you've already earned (inquiries, consults, past clients, and your organic visitors) instead of buying more. Every intake it produces lowers your blended cost per intake and pays back almost immediately.

Your funnel today, in your own numbers: a cost per intake of about $585, heading toward ~$400 as paid spend tightens; inquiries convert to intakes at about 18.5%, and consults close at about 50%. This program is built to lift each of those, and to add intakes that cost essentially nothing in media.

Where things stand today

Your funnel, as you described it

A lead reaches out → your welcome team books a paid intake (card on file + appointment = a "booked intake"); if the card isn't captured on the call, they offer a free 15-minute consult with a clinician. Lifecycle adds an automated layer of nurture at every step, so fewer people fall out between them.

Your content already earns the traffic; it just isn't converting yet

Your service and modality pages convert well, while the high-traffic blog explainers earn big audiences but almost no leads.

Email capture is on, but passive

Today there's a subscribe form only in the site footer (no inline prompt, no pop-up), so only a small fraction of those visitors ever join the list. Upgrading that is one of the recommendations below.

Every contact sits in one stage

A contact's stage decides which flow they're in, and when it stops. There are two phases: before someone becomes a client (based on what they've done) and after (based on how recently they've been in).

Before they're a client

Once they're a client

When a booked intake attends their first session, they become an active client. From there we track two simple signals (the date of the last session and whether a next one is booked) and group clients by recency. These segments are computed from those dates, not a separate stored stage:

From contact form to the right flow

Your CRM stays the source of truth. Here's the end-to-end path, and the fields that make the segmented journeys possible.

1. Someone reaches out through a Contact Us form (which is a callback request) or a call to the number on the page. The form captures name, email, phone, format, location, preferred contact method, age, a short "what brought you here," out-of-network acknowledgment, and SMS consent right away; callers give the same details to the welcome team.
2. The welcome team logs the lead into Therapy Flow and sets the taggable fields, most importantly SERVICE_INTEREST, which the form doesn't capture in a structured way. This logging step is the linchpin: if a field isn't set, the contact simply runs the generic path.
3. The fields trigger the right flow and route the modality content and proof points.
4. As the person advances (welcome-attended, then booked-intake, then client), the stage updates and flows advance or stop automatically.

The fields we recommend adding

Some of these you have already met as stages above; the rest power the personalization in the next section. They are grouped here so it is clear which does which.

Every field is non-clinical: no diagnoses, notes, or session content ever leave the CRM.

Depth where the data supports it, a clean generic path where it doesn't

One principle keeps this from becoming a maze: the funnel stage sets the email's job, the service line sets the substance, and format is just logistics. Modality never changes the job; it swaps in the right education, proof, and prep.

The rule that resolves the nuance: if there's no appointment scheduled, we persuade (modality-rich content and proof); the moment an appointment is booked, we switch to prepare, affirm, and remind (modality-light, no more selling). And when SERVICE_INTEREST is unknown (most contacts at first), the generic path runs, with modality content activating only once it's known.

What personalizes, and by which field

Out-of-network status and pricing are not personalization axes: CCG is out-of-network for everyone, and session fees are consistent across service lines (they vary only slightly by individual therapist, with group therapy the one exception), so both are standard copy in every email rather than dynamic blocks.

Send priority (so no one is over-emailed)

1. Appointment / transactional (confirm, prep, remind for a booked session). Always sends, exempt from the cap.
2. Active conversion flow. Welcome → Booked outranks Inquiry Nurture; only one runs at a time.
3. Continuity (existing clients).
4. Reactivation (dormant). Any re-engagement promotes them out of it.
5. Newsletter. Lowest priority; suppressed while a contact is in any active flow, and capped at ~2 marketing emails per week.

The service lines we segment by

CCG offers many named modalities; for clean, maintainable journeys we group them into a small set of service lines, keeping the specific modality as an optional tag. Nothing is dropped; here's the full mapping:

Six flows, one goal

A quick index of the six flows and when each fires. Full email-by-email detail follows below.

Each trigger's journey, and what every email contains

For each trigger, here's the visual journey of touchpoints we'd send, followed by the detailed contents of each email. Copy below is directional and goes through founder and compliance review before launch.

How real couples move through the flows

We use couples therapy (Gottman Method) as the running example here because it makes the segmentation easy to see; the same structure applies to every service line. Each example is one couple on one path, and names the exact flow they enter. The job of each flow is the same for every service line; only the couples-specific substance changes.

A longer path (illustrative): one couple, in and out of several flows

This is an illustrative example, not real client data. Real contacts don't sit in one flow, so here's how a couple like Priya and Marcus might move across the system over about four months, and which dynamic blocks fire each time. They started as a Maryland contact who prefers virtual sessions.

The point: one contact can touch four or five flows over time, and at every step the content adapts by the fields we log, without a separate flow for each combination.

Every other service line (individual, teen & child, trauma/EMDR, DBT) runs the same paths: same flows and jobs, its own education, proof, and prep.

A value-first newsletter, ramped to weekly

Your open rates are excellent; the opportunity is clicks. Every issue leads with genuinely useful content and ends with one clear call to action pointing to a high-converting service or location page, never the homepage. When it launches, it runs bi-weekly for about two months, then moves to weekly once the rhythm and engagement hold. In the roadmap the newsletter is the later priority, after the automations are live and proving out.

Content territories

How the territories rotate

The four territories run on a fixed wheel, T1 → T2 → T4 → T3, so each issue is deliberately different from the last and every territory returns on a predictable beat: lead with expertise (T1), answer the biggest question (T2), build trust with the people and places (T4), then a timely hook (T3). Bi-weekly, one full turn of the wheel takes about two months; at weekly, the wheel completes about once a month, so each territory lands roughly monthly. T3 uses the live seasonal moment when there is one (new-year reset, back-to-school, Mental Health Awareness Month), and an evergreen wellbeing topic otherwise.

The calendar at a glance

The dates above are an illustrative cadence; actual kickoff follows the roadmap, where the newsletter is the later priority. Cadence guardrails: we hold the move to weekly if unsubscribes, spam complaints, or open rates move the wrong way, protecting the deliverability that makes everything else work.

One number per flow, laddering to booked intakes

Program rollup: total booked intakes influenced by lifecycle, and the effect on blended cost per intake, reported monthly.

The foundation the flows need

The build order

The widget is the only piece with no setup, so it goes first. Everything else waits on the foundation above: no flow runs safely until the stage and suppression fields exist. Once they do, we build the flows one at a time, lightest to launch and highest value first. Pieces can still run in parallel where capacity allows.

1. Website capture widget. Independent, so it starts immediately and grows the list while the rest is being set up.
2. The data foundation. The BAA, the one-way feed, and the stage plus suppression fields (LIFECYCLE, the booking signal, NEXT_BOOKED). This is the gate: nothing below runs safely until it is in place.
3. Reactivation (E), the first flow. Once the fields exist it is the lightest to launch, since it runs off a one-time segmented export with no live trigger to build, and the fastest payback, recovering booked intakes from a list you already own.
4. Welcome → Booked (B), then Inquiry Nurture (A). The conversion core and the highest-value flows, lifting the consult-to-intake and inquiry-to-welcome steps directly. These need the live feed, and B needs the service line logged.
5. Pre-first-session prep (C), then Continuity (D). Added as their data pipes come online: appointment date and time for C, session recency for D.
6. Newsletter cadence and deeper personalization. Last, and can run in parallel once the flows are proving out, since its effect on intakes is not yet measurable.