nutrient-dense-life-email-sequence-automation-case-study-rellatech
    Back to Case Studies

    Setting Up Email Delivery for a Coaching Programme

    For Nutrient Dense Life, I organized course drafts into a branded email sequence and configured the delivery workflow. The founder received a simpler enrolment step and guidance for maintaining the sequence.

    Email AutomationCourse DeliveryBrand DesignWorkflow Build
    Valentina, founder of Rellatech

    Valentina Akpan: Founder of Rellatech, providing administrative and operations support to executives, founders, business owners and teams. Her background combines technical support, customer success, administration and operations.

    ·

    The Client

    Nutrient Dense Life is a health and wellness coaching practice. The founder runs The Metabolic Balance Method, a 12-week transformation programme. She had built the course content and recorded all of her video modules, but the client-facing delivery system did not exist yet. Every new client was being onboarded by hand.

    The Problem

    She needed the programme's emails sent on a schedule, so each client received the right module and check-in on the right day without her sending each one by hand. She had drafted the content but had no working sequence, no design system, and no clear picture of how the pieces fit together inside her email platform.

    In her own words, she liked simple, and the technical side was the part she did not know how to hand off.

    Course content written but living in scattered drafts

    No working sequence inside the email platform

    No design system, so every email looked different

    Onboarding every client meant sending emails by hand

    What I Did

    I took the project from loose drafts to a scheduled, on-brand sequence, and showed her how to run and edit it.

    Mapped the full 78-day journey

    19 emails: 12 weekly modules plus 7 personal check-ins and milestone notes, each timed to a specific day. The twelfth module goes out on day 78, so the delivery schedule ends there rather than on day 84.

    Designed every email on brand

    Each one laid out to match the clean, neutral look of her course workbook, with linked video thumbnails, branded buttons, and formatted checklists.

    Wired one automation, end to end

    A single workflow triggered by adding a client to one segment, with day-by-day delays so each client runs on their own 78-day schedule.

    Cut a tool she didn't need

    A planned review form was adding complexity. I swapped it for a simple reply-to-email, which removed friction for her and her clients.

    Caught the broken details

    Found and fixed a check-in channel that conflicted across emails, and a checkout link carried over from another account that would have sent clients to the wrong place.

    Made enrolment a one-step job

    She adds a new client to one segment and the schedule sends each email on its day, from day one to graduation. I showed her how to check and edit the sequence, since it needs maintaining when content or links change.

    The 78-Day Journey

    Nineteen emails: twelve weekly course modules, with seven personal check-ins and milestone notes in between, each tied to a specific day in the client's timeline. The twelfth module goes out on day 78, so that is where the delivery schedule ends. The programme is described as 12 weeks, and the last scheduled email lands on day 78 rather than day 84.

    Day 1 · Welcome + Module 1
    Day 7 · Personal check-in
    Day 8 · Module 2
    Day 15 · Module 3 + milestone
    ... · 9 more modules and check-ins
    Day 78 · Graduation

    Before and After

    Before

    • · Manually onboarding every client
    • · Course drafts sitting in documents
    • · No consistent email design
    • · Reliance on a planned review form and extra tool
    • · Broken checkout link from a previous account

    After

    • One-step enrolment: add the client to a segment and the schedule sends each email
    • Each module sent on its scheduled day
    • Branded, consistent emails across the 78-day schedule
    • Replies handled by email, no extra tool needed
    • Every link verified and pointing to the right place

    The Result

    A 12-week programme delivered on a schedule. She went from onboarding every client by hand to a one-step enrolment, with a branded sequence that takes each client from day one to graduation on day 78. I walked her through how to check, edit and maintain the sequence herself, since content, links and timing will need updating over time.

    • 19 branded emails scheduled across 78 days
    • Enrolment cut to a single step per client
    • Course modules, check-ins and milestones sent on their scheduled days
    • Two broken details caught before they reached a client
    • Founder shown how to maintain and edit the sequence herself

    She adds each new client to one segment. The schedule sends the emails from there, and she keeps the sequence up to date.

    The Takeaway

    This is the kind of work I do. I take something half-built and unclear, and turn it into a working system the owner can run and maintain. I handle the planning, the build, and the small details that make it work in practice.

    What I Used

    Email Automation PlatformCustom HTML Email DesignBrand Asset LibraryWorkflow Builder

    Who This Is For

    This case study is worth reading if you are:

    • ●Course creators and coaches with a multi-week programme they currently deliver by hand
    • ●Practices selling a transformation programme (12 weeks, 90 days, etc.) where pacing matters
    • ●Businesses and startups that recorded the modules but never built the email side of delivery
    • ●Anyone moving from cohort-based to evergreen course delivery

    Need help with similar work?

    Tell me which responsibilities or processes need attention, who is involved and any upcoming deadlines. I provide administrative and operations support, including the connected technical work within our agreed scope.

    Book a free call

    Share This Article

    Comments

    Join the conversation.

    Loading comments…

    Leave a comment