Strategy Meeting
Artifact info
Title:

Learning Mangagement System Sync Up

Engagement:

Holomovement App Ecosystem

Client:

Holomovement

Meeting Date:
December 12, 2025
Next Meeting Date:
December 23, 2025
Hide This
December 22, 2025
Hide This
November 21, 2025
Hide This
November 14, 2025
Hide This
August 31, 2025
Hide This
October 24, 2025
Hide This
July 28, 2025
Hide This
People
Hera Rose
Mariko Pitts
James Redenbaugh
Michael Shaun Conaway
Jill Robinson
Artifact Image
Meeting Summary

Custom LMS Platform Strategy 🏗️

James proposed building a custom learning management system instead of using Kajabi or similar platforms (04:55). The custom system would be built directly into the existing Webflow website, offering modules, lessons, progress tracking, and user login capabilities while maintaining full design control and integration with the broader Holomovement ecosystem.

[tag="webflow"]

Key Platform Advantages

Building on Webflow provides several strategic benefits:

  • All content lives in one place with the synergist map, directory, and other community tools
  • No separate profile creation or platform switching for users
  • Full customization capability without vendor lock-in
  • Ability to export and own all code if needed in the future
  • More cost-effective long-term than subscription platforms

The system integrates with communication automations based on user behavior (06:25). Automated responses can trigger based on assessment data, lesson completion, call attendance, or engagement patterns—sending personalized encouragement, connection recommendations, or check-in offers from Jill when participants fall behind.

[technology="Online Learning Platforms"][technology="Custom Membership System"][technology="Communication Automations"]

Michael-Shaun's LMS Development Experience 🎓

Michael-Shaun shared extensive background building learning management systems and expressed both enthusiasm and caution about custom development (07:25). His experience with Boldly and other platforms highlighted important considerations around complexity, timeline, and infrastructure requirements.

Platform Complexity Concerns

Michael-Shaun outlined the full scope of components needed beyond just course delivery:

  • Landing page systems
  • Email campaign platforms
  • Billing and payment processing
  • User database management
  • API integrations for triggering membership status and course access

He acknowledged Kajabi's all-in-one appeal despite not loving the platform personally (08:18). Hot Mart Latin America successfully processes $50 million in annual course sales using Kajabi—demonstrating the platform works at scale even if it's not innovative.

User Experience Design Priority

The most important piece is user experience design according to Michael-Shaun's course development experience (18:31). Most LMS platforms use horizontal accordion-style architecture that "people hate"—it's efficient to replicate like worksheets in school, but nobody enjoys the experience.

His Boldly platform uses a screen-based philosophy versus endless scrolling (20:17):

  • All actions and materials replace on the same stage sequentially
  • Feels like a defined space rather than a list
  • Enables direct jumping back to specific learning spaces
  • Provides instantaneous feedback throughout the journey

Course completion is a bigger challenge than course sales (19:35). Anything compelling continued engagement matters more than flashy features. Live cohorts help with completion rates since people show up even if they don't complete homework between sessions.

James's Technical Approach and Timeline 🔧

James has built "tons of learning management systems" primarily using Learndash on WordPress but is transitioning everything to Webflow in 2025 (10:01). Many of his clients have generated millions in revenue on these platforms. IRIS is now building a reusable system deployable across multiple client projects simultaneously.

[tag="learndash"]

Development Strategy

The approach starts with lowest-hanging fruit for rapid testing and iteration (10:01). Rather than building everything at once, the team will get core features working with real users and build from there based on actual needs and feedback.

James confirmed the system can scale to mobile apps when needed (32:23). Webflow generates clean HTML, CSS, and JavaScript that can be exported entirely or used to build parallel native apps syncing with the same databases. The key is determining app-specific use cases and excluding unnecessary web features.

Regarding timeline, James expressed confidence in delivering a functional system by February with his team's support (46:35). It will be a busy month but achievable for getting the first cohort into the platform.

Membership System Architecture 🗄️

The harder technical challenge is membership logins, not content delivery (26:46). James has extensive experience with Member Stack and Outseta on Webflow. While Webflow's built-in membership capability is limited, IRIS identified an opportunity to build something more customizable and cost-effective long-term.

[tag="memberstack"]

Minimum Viable Features Discussion

Michael-Shaun requested specification of all minimum viable features for proper evaluation (29:15):

  • Real database for user progress (not cookies)
  • Journal entry capture capability
  • API triggers for membership status and course purchases
  • Progress tracking across sessions

James emphasized that simply displaying content is relatively easy—creating lesson layouts poses fewer technical hurdles than building the synergist map (27:15). The membership authentication and user management systems require the deeper architectural work.

AI-Powered Engagement Features 🤖

Mariko highlighted AI components as key for engagement and support (12:44). The system can now leverage data and automation in sophisticated ways that weren't possible before, particularly for personalization and proactive outreach.

[tag="claude"][tag="n8n"]

Intelligent Response Systems

James described the integration as "a box of crayons" where colors blend beautifully (13:40). User data from assessments, clicking patterns, lesson completion, and call attendance feeds into automation workflows. The system can send:

  • Immediate tailored emails after lesson completion based on user profile
  • Weekly personalized updates to all participants with individual progress information
  • Connection recommendations based on assessment responses
  • Proactive check-in offers when engagement drops

[technology="Assessment Systems"][technology="Intelligent Matching Algorithms"]

Michael-Shaun noted too many AI possibilities exist and emphasized giving users things they actually like to do versus impressive features (15:34). Custom assessment feedback and predictive learning journeys hold huge value, but require well-developed teaching systems to deliver on those predictions.

Predictive learning remains premature for current Holomovement stage (16:48). This approach requires extensive content libraries and learning paths that don't yet exist. Michael-Shaun cautioned against over-engineering for theoretical future capabilities.

Course Structure and Content Development 📚

Jill has been developing course templates, homework structures, and exercises drawing inspiration from sources like The Artist's Way (38:10). She created frameworks offering multiple exercise options to accommodate different learning styles—introverts versus extroverts, reflective versus active learners.

Template Structure

Initial templates include:

  • Meditation components
  • Journal prompts
  • Embodiment exercises
  • Real-world implementation activities

Jill called homework "quests" to make engagement more playful (38:10). Each week includes suggested readings separate from interactive exercises and personal practices. She's working with presenters to incorporate their specific resources and expand wisdom offerings.

Live-to-Evergreen Workflow Challenge

Mariko emphasized the critical distinction between live delivery and evergreen product creation (34:14). The live cohort can flow organically through Zoom sessions, but the evergreen version requires precise chunking, structure, and technical formatting for global sales.

"We have to think technical first, get this right, and then plug what we do live into it" (34:48). The most efficient approach structures everything for long-term evergreen sales rather than just getting live content out quickly.

Script Development Process with Michael-Shaun 📝

Michael-Shaun offered to collaborate directly on digital course scripting (36:01). He emphasized that Jill shouldn't have to learn this complex process alone—he can jump into documents immediately to provide suggestions and guidance.

Scripting Methodology

Scripts function as detailed recipes for CMS authoring (45:23). Michael-Shaun's approach writes everything as if someone could take the course directly from the script:

  • Specifies exact interactivity types (checkbox, multiple choice, etc.)
  • Details all interaction flows
  • Leaves nothing to imagination
  • Makes editing easy on paper before time-consuming CMS building begins

He requested Jill align activities with content flow for session one (40:03). Rather than listing separate homework sections, the script should show: content section → relevant interactive activity → meditation → next content section. This mirrors how digital courses actually sequence rather than live session structure.

Michael-Shaun estimated 4-5 hours of authoring time per chapter with more time spent on editing and design than technical authoring (23:15). Building in parallel systems (both Kajabi and custom platform) remains feasible during development phase.

Emmanuel as Primary Host Decision 🎯

The team unanimously decided Emmanuel must be the consistent host for all course sessions (42:13). Initial plans involved rotating hosts alongside rotating presenters, but this approach creates too many problems.

Rationale for Single Host

Multiple practical and strategic reasons support this decision:

  • Limited time constraints: One-hour sessions can't afford 10 minutes on dual introductions (43:40)
  • Trust and continuity: Participants need consistent container-holding presence (44:05)
  • Authority establishment: Guests lack built-in credibility without Emmanuel's introduction (44:08)
  • Structural control: Host must understand bigger structure to keep things on track or make necessary cuts (42:13)

As Mariko noted, "This is essentially his course. It can't be me or something. It has to be him" (43:24). Emmanuel is trained in their process for holding containers and knows exactly what needs to happen within time limits.

The decision was made while Emmanuel was absent: "He should have been on this call. You've been outvoted and you're the sole host" (44:32). Jill will relay this decision at their Monday meeting.

Evergreen Product Access Strategy 💎

All Wave attendees receive the course for free as a gift regardless of when they purchase tickets (36:47). This includes anyone buying tickets in March or beyond—there's no deadline cutoff for this benefit.

Jill confirmed this messaging starts rolling out Tuesday and has 17 people already on the waiting list (48:02). The course simultaneously launches as both a live cohort experience and a sellable evergreen product, with new participants able to start anytime.

Mariko emphasized the importance of having systems ready for the January 27 launch (46:45). The first cohort needs direct access to the membership portal with the course and other initial resources already available, creating seamless onboarding.

Infrastructure Development and Slack Organization 📋

The team needs dedicated Slack channels for focused infrastructure development (48:12). Michael-Shaun requested a project specifically for web infrastructure development to enable easy document collaboration with James visible to relevant team members.

Slack Architecture

The discussion revealed complexity around Slack Connect integration:

  • IRIS Cocreative's internal Slack has a Holomovement project channel (HMI-I002)
  • Single-channel guest access creates invitation limitations
  • Infrastructure development needs its own dedicated channel within Holomovement's workspace
  • Phase one development (including LMS) should be grouped together rather than fragmented

James committed to creating appropriate channel structure and inviting Michael-Shaun as a single-channel guest for infrastructure collaboration (50:13). This separates sprint-specific LMS development from general homepage and website discussions.

App Development Considerations 📱

Michael-Shaun raised critical questions about eventual app architecture (30:11). While web development can sprawl with extensive menus and features, mobile apps face severe interface constraints. Planning now for how web systems translate to app experiences prevents future rebuilding.

Hybrid App Strategy

Michael-Shaun's platforms used hybrid development allowing simultaneous desktop and app creation (30:56). This approach avoids building everything twice—the same codebase responds to different contexts if architected properly from the start.

James confirmed Webflow exceeds WordPress and Kajabi for app compatibility (31:25). Webflow generates clean foundational code (HTML/CSS/JavaScript) that can be taken off the platform entirely or used to build parallel apps syncing with the same databases.

The key question: What's the app use case? (32:31). Not all website features belong in mobile apps—successful mobile experiences carefully select essential functions rather than cramming everything in.

Guatemala Assessment Page Customization ✏️

James created a specific assessment page route for Guatemala participants requiring tailored copy (56:14). Currently it uses general Synergist Program language, but the team can edit it themselves now that access is configured.

Mariko provided James with updated copy via text including the assessment title change and first-click description. Hera confirmed they still need the Guatemala-specific header description above the fold.

Relevant Initiatives

Assessment Development

Priority: 
Medium
Size: 
Creation Stage

Phase 2 of Community Engagement

Priority: 
High
Size: 
L
Creation Stage

Holomovement App

Priority: 
Very High
Size: 
XXL
Creation Stage

Membership Authentication System

Priority: 
Very High
Size: 
L
Creation Stage

Course Script Development

Priority: 
High
Size: 
M
Creation Stage
Transcript