A course business's email finally knows who bought what

Representative examplesEvery case study in this library is an illustrative composite of the kind of engagement we deliver — written to show our method and standards, not to name clients.

Where they started

Three product lines — a starter course, a practitioner programme, and an advanced certification — are sold by a two-person team through launch campaigns: quiet months, then a two-week burst of webinars, emails, and cart-open urgency. The funnels were built at different times by different contractors, and each generation wired its buyer tracking in its own way. The email list has grown into tens of thousands of contacts collected across those launches, and the owner knows it contains people who already own every product — the sends just cannot tell them apart.

What it was costing

Three funnels tagged buyers differently — some by product, some by campaign, some not at all. The email list sent launch emails to people who already owned the course, refund-window buyers got upsell emails, and segmentation was guesswork.

What they could see

• A launch email for the practitioner programme goes to dozens of people who bought the practitioner programme at the last launch.
• Buyers still inside their refund window receive upsell emails for the next tier.
• The same customer carries three different tags across the three funnels, or none at all.
• Nobody can answer a straightforward question: how many customers own more than one product line?
• Launch week begins with an evening of manual list-cleaning performed with rising resentment and falling accuracy.

The constraints we worked inside

• The account's CRM capability had to be verified in-app before design — the plan's features defined the ceiling.
• The existing tag mess couldn't be mass-deleted; live automations depended on it.
• The owner ran launches quarterly; cleanup had to fit between launches.

What had been tried before

Before each launch, the owner spent two evenings hand-cleaning the send list against purchase records.

Hand-cleaning at launch pace guaranteed misses in both directions — owners excluded from previews, refund-window buyers kept in for the upsell.

A freelancer was hired to reorganise the tags across the three funnels.

The work added overlapping tags on top of the old ones; nothing was removed, so the account now disagreed with itself in more ways.

Buyers were asked via email to flag which products they owned through a preference link.

A fraction responded, the responses decayed as new buyers arrived, and the data could never be trusted as a suppression source.

What we proposed

The plan was to clean the account's logic before its list: first verify in-app what the plan's CRM can actually do, then design a written tag taxonomy — product, lifecycle stage, source — and migrate the existing tag mess onto it incrementally, pausing live automations branch by branch rather than trusting them through surgery. Launch sequences get rebuilt on that truth, with suppressions that exclude owners of the promoted product and anyone inside their refund window. The result is not a bigger system; it is the same plan, finally telling the truth about who owns what.

Just as important is what we ruled out, and why:

• Migrating to a dedicated email platform — Live automations, three funnels, and a launch calendar allow no safe window; the ceiling was the plan's features, not the platform itself.
• Mass-deleting the legacy tags — Running automations still depend on old tags; deleting them mid-flight breaks sending in ways that surface during launches, when damage is most expensive.
• Rebuilding all three funnels on one template — Weeks of funnel work the launch calendar cannot absorb, and the tracking problem sat in the account's tags, not the funnel pages.

How the work ran

Delivered by the growth pod — strategist + automation specialist over 5 weeks, with working increments reviewed with the client every week.

The stack, and the reasoning

ClickFunnels CRM

The funnels, list, and purchase history all live here; migrating before a launch risked the quarter's revenue on a platform move it did not need.

Tag architecture

A written schema — product, stage, source — turns tags from residue into structure; the taxonomy is the actual product of this engagement.

In-app capability verification

The plan's real features define the design ceiling; testing them first cost a day and saved a rebuild designed against the brochure.

Email suppressions

Suppression at send time protects owners and refund-window buyers without fragmenting the list; exclusion is cheaper and safer than deletion.

What went wrong

How we worked together

Cadence

Twice-weekly 30-minute calls with the owner, plus a written tag-schema document reviewed asynchronously against the launch calendar.

Client side

The owner made every send-affecting decision; the VA executed list tasks and tag application under the written schema.

Decisions

Anything touching live carries a 48-hour decision rule with the owner; the schema itself was signed off in writing before migration began.

They provided

Admin access to the account, a map of the three funnels and their automations, the launch calendar, and historical send logs for validation.

What changed

The headline: launch emails sent to existing owners of the promoted product, measured across two launches — −88%, read from Send logs versus purchase records. A second check: launch revenue per email (fewer wasted sends, cleaner list) at +9%.

Launch week lost its hygiene panic: the send list is ready when the campaign starts, not the night before. The owner reads reply emails without dread, because the replies come from people the email could plausibly have been written for. Unsubscribes became information rather than injury — they cluster where the product fit ends, which is where the next product decision lives.

The result was read from Send logs versus purchase records against the pre-engagement baseline over the stated window, with a guardrail check on launch revenue per email (fewer wasted sends, cleaner list). Where platform-reported numbers and business outcomes differ, this record says which layer it is quoting.

What they own now

• The written tag schema — product, stage, source — with rules for how new tags get created.
• The suppression rule set behind every launch sequence, explained in one page.
• A capability notes document recording exactly what the plan can and cannot do.
• A launch runbook covering list readiness, suppression checks, and the branch-pause procedure.
• An automation map showing every live sequence, its triggers, and the tags it depends on.