The course launch losing sales at the finish line

Online course business · AWeber, Stripe, Zapier

The symptom: Strong ad click-through rates, far lower conversion than expected. Refund requests coming in from buyers saying they couldn’t access their course.

What the trace found: The payment confirmation webhook was firing correctly. But the CRM tag that triggered course access had a name mismatch introduced during a previous manual edit. Buyers were being logged as leads, not customers. No access was being granted automatically.

The outcome: Tag corrected. Automation tested end-to-end. Access restored for affected buyers. The pathway documented and added to the monthly check schedule. The issue had likely been present for 11 weeks.

The membership where the welcome sequence was silent

Membership community · AWeber, membership platform integration

The symptom: New members joining but not receiving their welcome sequence. The owner had been working with an email specialist for two months assuming it was a deliverability issue.

What the trace found: The welcome automation used a list-addition trigger. A platform update had changed how new members were tagged, they were going directly to the main list without triggering the list-addition event. The automation simply never started.

The outcome: Trigger updated to a tag-based entry point. Historical new members identified and manually entered into the sequence. Two months of onboarding had been missed entirely. Deliverability was never the issue.

The reporting that was quietly lying

Coaching business · CRM and reporting automation

The symptom: Monthly performance reports generated from the CRM. A long-standing client noticed a discrepancy between the numbers in the report and what they could see in their own data. Trust began to erode.

What the trace found: Three lifecycle stages had duplicate definitions from a migration 14 months earlier. Contacts were being counted twice in certain pipeline reports. The reports had never been validated post-migration.

The outcome: Duplicate stages merged. Historical contacts reassigned correctly. Report templates rebuilt. A full CRM audit was added to the quarterly schedule. The relationship was preserved.

Abandoned cart emails hitting buyers who had already paid

Online business · Stripe, Zapier, email automation

The symptom: Customers who had completed purchases were receiving abandoned cart emails days later. Some were confused. A small number were requesting refunds claiming they’d been charged for something they hadn’t ordered.

What the trace found: The purchased-customer suppression list had a sync delay that wasn’t accounted for in the automation timing. Customers who completed purchases during the delay window were still being entered into the abandoned cart flow. A second automation was adding recent buyers back into the browse abandonment sequence.

The outcome: Suppression logic updated with appropriate delay buffers. Conflicting automation corrected. Full flow tested with real purchase simulation. The abandoned cart flows left intact but functioning as intended, without touching existing customers.

The pre-launch review that caught four critical failures

Online coaching programme · Stripe, Zapier, WordPress

The situation: A high-ticket programme built across multiple platforms, ready to launch. The owner wanted a professional review before opening the cart.

What the review found, before a single sale was made: Payment confirmation webhook not connected to access sequence. Programme access set to manual approval instead of automatic. Onboarding email sequence had a broken conditional branch that would have stopped 40% of buyers mid-sequence. Checkout page had a Stripe test key still active in production.

The outcome: All four corrected before launch. The programme sold 23 places in the first 48 hours. Every buyer received access immediately and moved through onboarding without issue. Post-launch, the owner described it as the best investment in the build process.

Payment confirmed, student enrolled, but no course access

Online education business · LearnWorlds LMS, Stripe

The symptom: Students showing as enrolled inside LearnWorlds. Stripe showing payment confirmed. But students were contacting support saying they couldn’t access the course content. Everything looked fine on the surface.

What the trace found: LearnWorlds had a separate internal product access assignment that was not linked to the enrolment trigger. The Stripe integration was adding students to the school but not assigning them to the specific course. Enrolment and access were not the same thing, and the configuration had never separated them.

The outcome: Access assignment corrected and linked properly to enrolment. Affected students given immediate access. The configuration tested across multiple purchase scenarios before closing. A check for this specific pathway was added to the monthly review.

Three years of manual fixes had made everything fragile

Online education business · Multiple platforms, accumulated over 3 years

The symptom: Things were working, mostly. But every time something was changed, something unexpected broke elsewhere. The team were afraid to touch anything.

What the trace found: Three years of manual fixes had created a system where nothing was documented, automations referenced tags that no longer existed, several workflows were running in parallel doing conflicting things, and the CRM had over 200 redundant tags. Functional but one wrong edit away from something breaking badly.

The outcome: Full backend stabilisation over six weeks. Redundant tags removed. Automation conflicts resolved. All active workflows documented and simplified. Payment pathways tested and confirmed clean. The business had a system they could understand, edit confidently, and trust, and moved onto a Growth retainer to maintain it.