Strategy Meeting
Artifact info
Title:

Ecosystem Development and Strategic Vision

Engagement:

Holomovement App Ecosystem

Client:

Holomovement

Meeting Date:
January 19, 2026
Next Meeting Date:
February 16, 2026
Hide This
February 19, 2026
Hide This
February 9, 2026
Hide This
February 2, 2026
Hide This
January 26, 2026
Hide This
January 22, 2026
Hide This
January 14, 2026
Hide This
December 30, 2025
Hide This
December 23, 2025
Hide This
December 22, 2025
Hide This
December 12, 2025
Hide This
November 21, 2025
Hide This
November 14, 2025
Hide This
October 24, 2025
Hide This
People
James Redenbaugh
Hera Rose
Mariko Pitts
Michael Shaun Conaway
Artifact Image
Meeting Summary

Strategic Rebranding: From Movement to Living Ecosystem

Mariko Pitts led a crucial rebranding discussion that shifts how Holomovement positions itself (42:00). Rather than simply calling it a "movement," the team agreed to define Holomovement as a living ecosystem or operating system that catalyzes movements globally. This reframing emphasizes the tangible infrastructure being built rather than just the outcome, making the initiative more fundable and easier to understand.

The ecosystem serves as infrastructure for emergence, supporting complex living systems that foster higher frequency states and radical collaboration. As James Redenbaugh noted, "ecosystem" is the more accurate descriptor since "movement" is already embedded in the name. The team acknowledged that while these are still metaphors, they need to continue refining language to be as plain-spoken and inspiring as possible. Michael Sean referenced the Mark Twain quote about writing short letters requiring more time, emphasizing that simplifying complex ideas is an ongoing iterative process.

Ripple Tracker Integration and Emotional Technology

Hera presented the Ripple Tracker prototype, a global behavior-building tool designed to help reach 3.5% of humanity through daily gratitude practices (02:45). The tracker enables users to log gratitude, prayers, and moments of grace, operating on principles from David Hawkins' "Power vs. Force" work on emotional frequencies. The goal is to get 100 million people performing one action daily with zero friction, creating a ritual-driven ecosystem of emotional well-being.

The Ripple Tracker functions as an outward-facing activation layer complementing the Holomovement app. While the main app is inward-facing for already activated members (high context, high trust, optimized for depth and belonging), the Ripple Tracker serves newcomers with low friction entry points. Hera described it as "the garden before people get inside the house" with multiple pathways to different entry points.

Michael Sean recommended examining the app "Altered," which uses AI dialogue to engage users in psychedelic journaling and provides daily community snapshots (12:45). The key insight is using AI not to mimic humans but to provide perception we can't access otherwise, like synthesizing community emotional trends. This aligns with feeding AI collective consciousness data rather than just transactional requests.

[technology="Community Facilitation Tools"]

LMS Development Progress and Strategy

James Redenbaugh provided an update on the Learning Management System development using Webflow [tag="webflow"] (21:03). The team has successfully implemented authentication with login, signup, and user field editing capabilities. They're structuring content with three collection levels: courses, modules, and lessons, using relational fields in both directions.

A key technical consideration is that Webflow [tag="webflow"] CMS collections aren't built to be nested, so the hierarchy will be an illusion in URLs. However, as Michael Sean confirmed, meaningful URLs aren't necessary as long as breadcrumbs provide clear navigation on screen. The system includes draft mode, scheduled publishing, and content gating based on membership levels.

For membership management, the team discussed using expiration dates rather than tracking payment status directly (13:19). This approach simplifies the integration with Stripe [tag="stripe"], as the system only needs to know the expiration date, not whether someone missed a payment. Stripe [tag="stripe"] would simply extend the expiration date upon successful payment, making it easier to switch between monthly, semi-annual, or annual memberships.

Mariko emphasized bringing Michael Sean's expertise on course engagement beyond just the sale point, focusing on actual user experience and completion. They plan to use one of his existing courses as test content for development and design.

[technology="Online Learning Platforms"]

[technology="Custom Membership System"]

About Page Design and Messaging Refinement

The team reviewed the About page design with emphasis on making the value proposition immediately clear. Hera raised the important question of whether the hero section alone answers "What is Holomovement?" for first-time visitors arriving through ad campaigns (38:30). She suggested adding a concise statement that directly explains Holomovement as a global network of gatherings, initiatives, and collaborators.

Michael Sean provided feedback on visual hierarchy and the Purpose Earth integration (33:00). While the pop of color from the Purpose Earth logo is valuable, it was sized too prominently, making it feel like visitors had landed on a Purpose Earth page rather than Holomovement's About page. The team agreed to create a partners CMS collection [tag="webflow"] for logos that can be displayed in random order to avoid hierarchical implications as more partnerships develop (36:03).

Discussion of the "Underview Effect" section led to recognition that this underwater wave imagery and concept better fits the Wave page than the About page (26:17). The team agreed to replace it with content about the "Holomovement Effect" focused on collective higher frequency states, emotional scale awareness, and conscious choice. James presented an early animation draft showing text transitions that will incorporate logo movement and can be connected to scroll (40:27).

Mariko proposed potentially renaming the "About" page to "Manifesto" to better reflect the nature of the content (01:01:40).

Directory System and Player Card Approach

The team shifted priorities to emphasize the directory system over LMS development in the near term (55:05). Michael Sean advocated for a video game perspective on user profiles, calling them "player cards" rather than bio pages (56:29). This gamification approach focuses on information that enables AI-powered matching rather than what individuals want to express about themselves.

The key data points identified are: what someone is doing (their project/mission) and what help they need. With this information, AI [tag="claude"] can facilitate meaningful connections. The system should summarize even lengthy user inputs into concise card formats to maintain scannability and enable effective matching algorithms. James agreed to schedule a separate meeting within the week specifically to discuss directory system questions and player card design (56:02).

[technology="Intelligent Matching Algorithms"]

[technology="Directory Systems"]

Microgrant Program Strategy

The microgrant program discussion revealed an important strategic pivot (58:20). The team established a range of $1,500 to $5,000 per grant, with flexibility based on the first Wave project budget and potential matching grants from partners like Kinship Earth.

Michael Sean shared a transformative reframing from a conversation earlier that day: positioning these as angel grants to startups rather than just community project funding (59:14). This perspective opens possibilities for convertible notes or return mechanisms where successful projects could return 2x, 3x, or 5x the initial grant. The key principle is that generosity should feed the Engine for Good, creating a sustainable funding cycle for the ecosystem. The team plans to select three exemplary model projects initially to set standards and ensure the system tells a good story while technical infrastructure develops (01:00:58).

Team Communication and Coordination

The team discussed communication tools, ultimately deciding on iMessage as the primary channel since most participants are iPhone users and find it easier to track than WhatsApp groups (19:40). They scheduled a follow-up meeting for Thursday at 2pm Eastern for James and Michael Sean to dive deeper into directory system details, which Mariko won't need to attend as she'll be traveling in Charleston, South Carolina.

Action Items

Hera

  • Send Ripple Tracker pitch deck and prototype video to Michael Sean for review (12:00)
  • Explore adding completion line to Purpose block stating modes of action on About page (50:00)
  • Create iMessage group for core team communication

James Redenbaugh

  • Update project milestones reflecting directory system prioritization over LMS and share with team (55:20)
  • Schedule separate meeting within one week to discuss directory system and player card design (56:02)
  • Develop partner CMS for dynamic logo display with random ordering (36:03)
  • Continue LMS authentication, gating, and course content structuring work (21:21)
  • Refine About page animation with logo movement integrated to scroll (40:27)

Michael Sean

  • Review Ripple Tracker materials and provide integration feedback
  • Lead microgrant program refinement and Engine for Good integration (57:00)
  • Improve About page visuals and animations to express higher frequency themes (40:10)
  • Provide LMS course content for testing and development (19:10)
  • Review and simplify copy across About page emphasizing "living ecosystem" positioning

Mariko Pitts

  • Draft Holomovement Effect content to replace Underview Effect section on About page (26:17)
  • Provide partner logos for CMS implementation
  • Determine first Wave project budget and grant amounts (58:58)
Relevant Initiatives

Holomovement App

Priority: 
High
Size: 
XXL
Planning Stage
Transcript