The Holomovement is building toward The Wave—a gathering in Cascais, Portugal in late May 2026 where the energy of in-person connection meets the infrastructure needed to sustain it. Our work is the digital ecosystem that makes that possible.
The core user journey is simple: Discovery → Connection → Collaboration → Action → Funding. Assessments serve as entry points, matching algorithms create meaningful connections, collaboration tools support holon formation, and micro-grants culminate the journey from inspiration to funded action.
We're building this with modern, modular tools—Webflow, n8n, Airtable, Claude AI—that reduce costs while maintaining flexibility. The Holomovement owns all member data. No platform lock-in. Full sovereignty over community relationships.
Development happens in four phases. Foundation (through January) establishes assessments, membership, and communication automations. Connection (February–March) builds the directory, matching algorithms, and community facilitation tools. Collaboration (March–April) adds custom video lounges and project coordination. Polish (May) refines the visual layer and prepares for Wave integration.
The harder design problem is the user architecture. The network includes both individuals (Synergists/Ambassadors) and collectives (Holons/Alliances) that range from informal study groups to established nonprofits. The matching system needs to account for development level, current project, skills, needs, and offers—actionable data that supports real collaboration rather than personality typing that requires belief to feel relevant. Profiles are designed as "player cards" scannable in three seconds, answering "what's your jam?" immediately while feeding the algorithms that surface who should meet whom.
By The Wave, the platform will support pre-event buddy matching, cohort formation, breakout group optimization, and the first Purpose Earth micro-grants demonstrating the Engine for Good model—where activated community members create sustainable impact through small contributions flowing to aligned projects.
The Holomovement is building toward The Wave—a gathering in Cascais, Portugal in late May 2026 where the energy of in-person connection meets the infrastructure needed to sustain it. Our work is the digital ecosystem that makes that possible.
The core user journey is simple: Discovery → Connection → Collaboration → Action → Funding. Assessments serve as entry points, matching algorithms create meaningful connections, collaboration tools support holon formation, and micro-grants culminate the journey from inspiration to funded action.
We're building this with modern, modular tools—Webflow, n8n, Airtable, Claude AI—that reduce costs while maintaining flexibility. The Holomovement owns all member data. No platform lock-in. Full sovereignty over community relationships.
Development happens in four phases. Foundation (through January) establishes assessments, membership, and communication automations. Connection (February–March) builds the directory, matching algorithms, and community facilitation tools. Collaboration (March–April) adds custom video lounges and project coordination. Polish (May) refines the visual layer and prepares for Wave integration.
The harder design problem is the user architecture. The network includes both individuals (Synergists/Ambassadors) and collectives (Holons/Alliances) that range from informal study groups to established nonprofits. The matching system needs to account for development level, current project, skills, needs, and offers—actionable data that supports real collaboration rather than personality typing that requires belief to feel relevant. Profiles are designed as "player cards" scannable in three seconds, answering "what's your jam?" immediately while feeding the algorithms that surface who should meet whom.
By The Wave, the platform will support pre-event buddy matching, cohort formation, breakout group optimization, and the first Purpose Earth micro-grants demonstrating the Engine for Good model—where activated community members create sustainable impact through small contributions flowing to aligned projects.
Course content development and delivery strategy. Strategic pivot to postpone Amendment course and prioritize Choose Love Spoon Bending course in collaboration with Light Net Zinka and Choose Love Movement. This experiential course teaches participants to bend silver spoons through consciousness techniques rather than force, with over 90% participant success rates in previous sessions. Choose Love operates in 120 countries, potentially expanding Holomovement's reach considerably. Course will feature mix of pre-recorded and live elements to accommodate experiential nature. Timeline shifted to late February or early March. Emmanuel confirmed as primary consistent host for all sessions. Jill developing course templates with multiple exercise options (meditation, journal prompts, embodiment exercises, real-world implementation). Framework accommodates different learning styles. All Wave attendees receive course for free. 17 people already on waiting list. Michael-Shaun providing scripting collaboration and methodology for digital course authoring.
Assessment system with AI-powered engagement features feeding automation workflows. Data from assessments, clicking patterns, lesson completion, and call attendance triggers personalized communication including immediate tailored emails, weekly progress updates, connection recommendations based on profile matching, and proactive check-in offers when engagement drops. Guatemala-specific assessment page created requiring customized copy. Current synergist directory demonstrates existing assessment capabilities: members complete form triggering automated n8n and Claude AI analysis of responses about purpose, projects, and ancestral wisdom influences. System generates personalized feedback and recommends connections to other synergists based on compatibility, facilitating introductions via email without exposing addresses. Also suggests relevant podcast episodes. No-login approach removes participation barriers while enabling intelligent matching and communication. Strategic shift to progressive engagement model: members start with basic five-minute profile setup (name, website, purpose statement, location), then complete more detailed assessments later. Each completed assessment adds elements to profile and unlocks new features. Gamification includes AI-generated icons, tarot card archetypes, or numerology graphics appearing on profiles as users complete different assessments. Incremental assessment launch strategy releasing new assessments every week or ten days leading to Wave event, using Ripple gatherings and Miracle Club to promote participation. Partnership opportunities with experts for themed assessments (Don Beck for Spiral Dynamics, Vedic astrologer for astrology, iOS Zone of Genius team for their assessment). Critical reassessment of assessment strategy prioritizing basic intake form capturing most important factors: development level, experience, life stage, purpose, and current needs as primary assessment for matching foundation. Systems like Gene Keys and numerology recognized as requiring belief in astrology/numerology to feel relevant, limiting universal applicability. Focus shifting to actionable, practical data enabling computational matching based on clear criteria rather than archetypal personality typing. When matching collaborators, users need to understand skills, experience, current needs, and project involvement rather than personality scores. AI-driven matching requires developmental stage, experience level, project involvement, and specific needs to avoid misaligned matches like pairing serial entrepreneurs with college freshmen. Meeting confirmed approach of using simple 1-to-10 scale assessments for numerical scoring and spider graphs but deferring complex compatibility scores for MVP. AI interpretation via Claude for free-text fields and nuanced alignment, direct computation for explicit matches like shared affiliations or complementary skill requests. Michael coordinating with Emmanuel on potential assessment questions to gauge user alignment.
European localized landing page for Wave event targeting European ticket buyers. Based on Portugal sales page structure with customized copy for European audience. Europeans typically purchase tickets closer to event dates requiring different marketing approach. Mockup being developed with screenshots and finalized copy for January 6th team review with Matilda before implementation handoff to Ivan. Not urgent priority given European purchase behavior patterns.
Custom membership system architecture for user authentication, progress tracking, and database management using Supabase for backend. Requirements include real database for user progress (not cookies), journal entry capture, API triggers for membership status and course purchases, and progress tracking across sessions. Decision made to build custom solution on Supabase rather than Member Stack. Includes Stripe integration for subscription management and automatic access revocation when subscriptions lapse. Multiple products may connect to same membership tier with bundled offerings granting multiple memberships from single purchase. Part of Phase One development with $16K-$29K budget. Requires hiring Supabase specialist for implementation. Timeline aligned with LMS development for February 10th launch. Authentication spike will establish foundation with Supabase login functionality on MAST template, implementing user profiles, password management, and session handling. System will sync membership status between Stripe and Supabase for automated access control. Backend successfully operational with membership login and content gating complete using Supabase and Stripe. Profile editing integration in progress to connect with directory system. Backend approximately 90% complete with primary goal to deliver working version on Holomovement site for team testing this week allowing account creation, login, and profile data editing. Front end minimal at this stage consisting mainly of login pages until profile pages developed.
Strategic enhancement of directory system integrating with membership capabilities to enable member profile management, progressive assessment completion, and intelligent matching. Members can log in and edit their profiles directly with information stored in Supabase for flexible content management. Progressive engagement model starts with basic five-minute setup (name, website, purpose statement, location), then enables detailed assessments later. Each completed assessment adds profile elements and unlocks features including AI-generated visual representations (icons, tarot archetypes, numerology graphics). Integration with Claude AI enables sophisticated queries like 'who should I collaborate with on this project?' or 'who can provide funding?' across network assessment data. Advanced features include weekly emotional mapping interface with six-axis emotional space (excitement, nervousness, grief, etc.) aggregating into community climate visualizations. Reimagined map interface using flat Earth projection with layered filtering showing member locations, funding flows, collaborative connections, project relationships. Multiple view modes from simplified default to complex multi-layered 'Arcturian' views. Integration with Engine for Good grant program where applications link to member profiles, creating incentive structure for profile completion. Team pivoted to prioritize directory system over LMS development. Player card approach focuses on game-like profiles emphasizing what someone is doing (project/mission) and what help they need for AI-powered matching. System summarizes lengthy inputs into concise scannable formats. MVP launch target February 15 with login capability, profile editing, and integrated assessments. Beta testing program follows to identify next priority features. Critical development discussion revealed MapBox visualization provides initial visual interest but limited practical value beyond local connections - intelligent matching algorithms represent the true 'killer app' rather than map visualization. Profile data strategy shifting from personality assessments to actionable information: developmental stage, experience level, current project involvement, specific skills, and active needs. Visual consistency issues identified with user-uploaded images requiring standardization. Question emerged whether Holons function as independent entities or collections of individual members, requiring data architecture decisions. Simplified terminology 'members and groups' proposed over 'Holons' for newcomer clarity. Basic intake form planned capturing development level, experience, life stage, purpose, and current needs as primary assessment for matching foundation. Player card UI concept introduced featuring icons to symbolize key information, AI-generated summaries to condense lengthy responses, and achievement badges displaying completed courses, assessments, and accomplishments. Design iteration process planned where team scans test cards to validate information hierarchy. Sandbox database creation for core team to fill out profiles and review each other's player cards as real-world test. Prototype development progressing with profile creation, editing, viewing, and password resets functional in Supabase. Munia developing first draft UI designs. Team agreed to reduce text density, create more visual/scannable interfaces. Multiple views prototyped: alliance view, profile editing, directory search (list and map-based), member profiles, holon profiles. Core intake fields defined: name, date of birth, email, phone/SMS/WhatsApp, location, purpose/mission, gifts and requests, alliance affiliations, short bio (150 words max), photo. Matching deferred from numerical compatibility scores to simpler connection signals: complementary skills, matching needs/offers, alliance overlap, geographic proximity, shared purpose domains. AI interpretation via Claude for free-text fields, direct computation for explicit matches. App functionality to be hosted on separate subdomain (app.holomovement.net) with member-specific navigation, syncing public profile data to main site member globe. End of February target for core team interactive prototype.
Strategic rebranding initiative shifting how Holomovement positions itself from simply a 'movement' to a 'living ecosystem' or 'operating system' that catalyzes movements globally. Reframing emphasizes tangible infrastructure being built rather than just outcome, making initiative more fundable and easier to understand. Ecosystem serves as infrastructure for emergence, supporting complex living systems that foster higher frequency states and radical collaboration. 'Ecosystem' recognized as more accurate descriptor since 'movement' already embedded in name. While these are still metaphors, team committed to continuing refinement of language to be as plain-spoken and inspiring as possible. References Mark Twain principle that simplifying complex ideas is ongoing iterative process requiring time. Applies across all communications, website copy, pitch materials, and partner conversations. Foundation for how Holomovement describes itself to funders, partners, and new community members.
Comprehensive redesign of About page focusing on clear value proposition and ecosystem messaging. Key objectives include answering 'What is Holomovement?' immediately in hero section for first-time visitors from ad campaigns with concise statement explaining Holomovement as global network of gatherings, initiatives, and collaborators. Replace 'Underview Effect' section with 'Holomovement Effect' content focused on collective higher frequency states, emotional scale awareness, and conscious choice. Underwater wave imagery relocated to Wave page where more appropriate. Animation development showing text transitions incorporating logo movement connected to scroll. Visual hierarchy improvements to balance Purpose Earth partnership integration without overwhelming Holomovement branding. Creation of partners CMS collection for logos displayed in random order to avoid hierarchical implications as partnerships grow. Refinement of copy emphasizing 'living ecosystem' or 'operating system' positioning rather than just 'movement,' making initiative more fundable and easier to understand. Ecosystem serves as infrastructure for emergence, supporting complex living systems fostering higher frequency states and radical collaboration. Ongoing iteration to make language as plain-spoken and inspiring as possible. Potential renaming of page from 'About' to 'Manifesto' to better reflect content nature. About page redesign nearly complete with Iván and Melina tag-teaming final design elements. Once design reaches 100% approval, development should take no more than one or two days to implement on live site.
Define data architecture and entity management approach for organizational units within the system establishing framework for how users, individuals, and groups are categorized. Core user model establishes everyone enters system as Individual first ensuring platform's primary impact centers on connecting people rather than organizations. After creating individual profile, users can join or create Holons (project-based groups with specific outcomes and impact goals) and affiliate with Alliances (mission-aligned organizations sharing values with Holomovement but may not have active projects within system). Holons are project-oriented requiring three administrators for security and continuity - if one administrator becomes inactive, two others maintain access to manage Holon profile. Multi-step creation process: one person drafts Holon and identifies two other administrators by email, those two individuals receive confirmation emails, and once they confirm participation (creating individual profiles if needed), Holon profile goes live. Founding three administrators have full editing access with ability to elevate additional members to administrative status later. Alliances represent mission-aligned organizations where users can self-declare affiliation similar to LinkedIn company profiles without formal approval. Team using themselves as first test group creating individual profiles, registering businesses as Alliances, and forming Holons based on actual project work. This validates system architecture with real-world use cases, demonstrates transparency showing how Holomovement operates internally, and dissolves inside-versus-outside dynamic that often exists in community platforms. Sandbox database initially with core team members to test system before expanding to broader team and migrating existing user data. Matching hierarchy established: Individual to Individual (priority 1), Individual to Holon (priority 2), Holon to Individual (priority 3), Holon to Holon (priority 4). Alliance-to-Alliance connections happen primarily through leadership conversations rather than software. Hybrid taxonomy strategy combining fixed high-level categories with AI-generated flexible sub-tags. Seven to nine fixed categories each with icon and visual identity providing newcomers clear 'lay of the land.' AI agent may automatically generate and organize categories based on how people describe their Holons allowing adaptive evolution as community grows. Key matching information includes developmental level, life stage, purpose, needs and offers, domain focus, formalization level, activity level, and geographic location. Critical filtering categories for initial launch: domain/focus (what group works on), what group needs (funding, visibility, structure), what group offers (projects, learning, mentorship, impact, belonging), activity level (active, dormant, occasional), formalization level (informal, loose, institutional). Self-assessment data like Human Design and numerology incorporated into player cards providing deeper understanding beyond skills and experience. Meeting confirmed simplified explanations for onboarding: 'a holon is a group of people with a shared project or outcome' rather than full theoretical framework. Alliance affiliations limited to community-relevant entities. Core intake fields finalized: name, DOB, email, phone/SMS/WhatsApp, location, purpose/mission, gifts and requests, alliance affiliations, short bio (150 words max), photo.
Establish sprint methodology and weekly planning discipline to improve estimation accuracy, development velocity tracking, and pricing confidence. Current project management creating less clarity than previous ClickUp system with daily prioritization uncertainty. First development phase showed 40% cost variation suggesting unclear feature definitions or development paths. Implement weekly planning sessions establishing goals, tracking actual hours against estimates, and building understanding of development patterns. Create simple Kanban view or text document showing current priorities, in-progress work, and needed items with estimated effort hours and comparison to previous estimates. Focus on manual curation rather than relying on auto-generated AI initiatives which have proven unreliable. Weekly meetings start with priority and dependency review, address critical decisions first, then review completed work if available. Shorter meetings preferred ending early when objectives met. Decision-making process: someone identifies need, stakeholders propose solutions in Slack, proceed with single unopposed proposal rather than indefinite ideation cycles. Addresses Holomovement pattern of extended ideation without reaching polished execution.
Comprehensive architectural framework document defining how individuals, Holons, and Alliances function within the platform. Document establishes philosophical and technical considerations for user categorization and organizational structures. Framework clarifies that everyone enters as Individual first, can then join/create project-based Holons, and affiliate with mission-aligned Alliances. Includes detailed specifications for three-administrator Holon security model, confirmation workflows, matching hierarchy priorities, taxonomy strategies combining fixed categories with AI-generated tags, and critical filtering categories. Document serves as foundational reference for all platform development ensuring consistent implementation across directory, matching, and profile systems. James created document and shared with team for feedback in Slack. Team will use document to guide sandbox database creation and real-world testing with core team members as first users. Meeting confirmed simplified onboarding language: holons explained as 'group of people with shared project or outcome.' Alliance affiliations limited to community-relevant entities. Core intake fields finalized. Framework being actively implemented in prototype development.
Collaboration with DJ Taz to curate diverse digital content including meditations, yoga classes, and playlists. Some content designed to complement courses while other material exists independently. Content organized in Airtable with direct CMS connection so DJ Taz and others can manage database while changes appear automatically on site. Content strategy includes both course-specific materials and standalone offerings available to members. Supports broader platform engagement beyond structured courses.
Digital course scripting for evergreen product creation with Michael-Shaun's methodology. Scripts function as detailed recipes for CMS authoring, specifying exact interactivity types (checkbox, multiple choice), interaction flows, and content sequencing. Format aligns activities with content flow rather than separate homework sections. Michael-Shaun estimates 4-5 hours authoring time per chapter. Process enables editing on paper before time-consuming CMS building. Focus on live-to-evergreen workflow ensuring technical structure supports global sales rather than just live delivery.
Experiential course teaching participants to bend silver spoons through consciousness techniques rather than force, developed in collaboration with Light Net Zinka and Choose Love Movement. Course demonstrates over 90% participant success rates in previous sessions. Partnership with Choose Love provides access to network operating in 120 countries, potentially expanding Holomovement's reach considerably. Course structure will feature mix of pre-recorded and live elements to accommodate experiential nature of practice. All Wave attendees receive course for free. Launch timeline late February or early March 2026. Course serves as first major content implementation for custom LMS platform. Content development requires coordination with Light Net Zinka and Choose Love Movement for materials, methodology, and co-branding. Testing phase will use actual course content to validate LMS functionality before launch.
Global behavior-building tool designed to reach 3.5% of humanity through daily gratitude practices. Enables users to log gratitude, prayers, and moments of grace, operating on principles from David Hawkins' 'Power vs. Force' work on emotional frequencies. Goal is 100 million people performing one action daily with zero friction, creating ritual-driven ecosystem of emotional well-being. Functions as outward-facing activation layer complementing Holomovement app. While main app is inward-facing for already activated members (high context, high trust, optimized for depth and belonging), Ripple Tracker serves newcomers with low friction entry points. Described as 'the garden before people get inside the house' with multiple pathways to different entry points. Integration considerations include examining 'Altered' app which uses AI dialogue for psychedelic journaling and provides daily community snapshots. Key insight is using AI not to mimic humans but to provide perception we can't access otherwise, like synthesizing community emotional trends. Aligns with feeding AI collective consciousness data rather than just transactional requests. Requires review of pitch deck and prototype video to determine integration strategy with Holomovement platform.
Migration from Gmail and Constant Contact to ActiveCampaign for newsletter and automation capabilities. Replaces client's current Constant Contact setup with more robust automation platform. Includes evaluation of ChatGPT playbooks with Atlas browser approach for high-volume email management as alternative or complement to ActiveCampaign. Integration with LMS and membership system for triggered communications based on user behavior and engagement.
Micro-grants program rewarding Holons demonstrating transformative action. Grant range established at $1,500 to $5,000 per award with flexibility based on first Wave project budget and potential matching grants from partners like Kinship Earth. Strategic reframing positions these as angel grants to startups rather than just community project funding, opening possibilities for convertible notes or return mechanisms where successful projects could return 2x, 3x, or 5x the initial grant. Key principle is that generosity should feed the Engine for Good, creating sustainable funding cycle for ecosystem. Some grants awarded at Wave event in Portugal with program continuing beyond Wave with quarterly grant cycles. Directory system supports grant application process with applications linked to member profiles. Creates incentive structure: members join directory, complete assessments and profile information, apply for grants, potentially receive funding at Wave event. Beta testing for directory bootstrapped by grant program, driving engagement while collecting usage data. Program partially funded by membership revenues creating virtuous cycle where membership fees support transformative projects across network, visible to all members through platform. Initial strategy selects three exemplary model projects to set standards and ensure system tells good story while technical infrastructure develops. Integration with directory system and profile completion tracking required for application management.
Cross-platform interoperability vision enabling different organizations running similar LMS and membership systems to share content and profiles seamlessly. Architecture allows organizations to run courses on their platform while making them available to Holomovement members who experience content as native to Holomovement while connecting with learners from both communities. Single user identity exists across multiple platforms with relevant information sharing automatically while maintaining privacy boundaries. Modular, pluggable components (assessments, content management, user profiles) designed so improvements to one part benefit all implementations. When better AI models release, can swap into existing assessments immediately without rebuilding functionality. Represents fundamental reimagining of how online communities and educational platforms could break down silos without centralizing control.
Build custom LMS infrastructure on Webflow for January 27 launch
February 1, 2026
Develop core LMS features including modules, lessons, progress tracking, and user login. Prioritize lowest-hanging fruit for rapid testing. Team expects functional system by February with support from IRIS team.
Create infrastructure development Slack channel and invite Michael-Shaun
December 23, 2025
Set up dedicated infrastructure development channel within Holomovement workspace (not IRIS workspace). Invite Michael-Shaun as single-channel guest for collaboration. Separate from general homepage/website discussions.
Finalize membership system approach for team review next week
December 27, 2025
Decide between Member Stack or custom solution. Present phase one and phase two proposal for membership portal features. Meeting scheduled next week focused on membership system architecture decisions.
Update Guatemala assessment page with provided copy changes
December 20, 2025
Update Guatemala-specific assessment page with copy from Mariko including title change and first-click description. Add Guatemala-specific header description above the fold per Hera's confirmation.
Document all LMS parts and pieces needed for course operation
December 27, 2025
Share course script templates with Jill showing authoring format
December 23, 2025
Provide script examples demonstrating detailed recipe format for CMS authoring. Show how to specify interactivity types, interaction flows, and content-to-activity sequencing. Enable Jill to start scripting process.
Collaborate with Jill on scripting session one with content-to-activity flow
January 10, 2026
Work directly with Jill on session one script. Align activities with content flow rather than separate homework sections. Show: content section → relevant interactive activity → meditation → next content section sequencing.
Provide feedback on minimum viable features specification
December 30, 2025
Review James's specification of all minimum viable LMS features when available. Evaluate based on experience with Boldly and other platforms. Ensure critical components included: real database, journal capture, API triggers, progress tracking.
Meet with Emmanuel Monday to discuss course finalization and host structure
December 23, 2025
Relay team decision that Emmanuel must be sole consistent host for all course sessions. Discuss content finalization and presenter coordination. Emmanuel was absent from meeting where decision was made.
Align session one activities with content flow for scripting process
January 3, 2026
Restructure session one to show content-to-activity sequencing rather than separate homework sections. Prepare for Michael-Shaun's scripting collaboration. Format for digital course delivery rather than live session structure.
Continue developing exercise options for different learning styles
January 20, 2026
Expand framework with multiple exercise options (meditation, journal prompts, embodiment exercises, real-world implementation) accommodating introverts vs extroverts, reflective vs active learners. Use 'quests' terminology for playful engagement.
Coordinate with presenters to integrate their resources and wisdom offerings
January 20, 2026
Work with course presenters to incorporate their specific resources, teachings, and materials into course structure. Expand wisdom offerings beyond core content. Ensure presenter contributions align with evergreen format.
Review phase one and phase two proposal for membership portal features
December 22, 2025
Schedule meeting next week focused on membership system architecture decisions
December 26, 2025
Meeting to discuss membership system architecture (46:45)
Provide Guatemala-specific copy for assessment page header
December 26, 2025
Copy needed for Guatemala assessment page (56:14)
Continue to support infrastructure development coordination and Slack channel organization
December 26, 2025
Forward invoice to Emanuel for payment processing
December 27, 2025
Process invoice covering June through December for ongoing work and new development activities. No invoices have been processed since May.
Send comprehensive update to Emanuel and Laura regarding Phase One investment
December 27, 2025
Include details on invoice approval, Phase One investment commitment at higher budget range ($16K-$29K), deposit payment structure, and milestone schedule. Communicate decision to front-load investment for LMS/membership development.
Coordinate European Wave landing page mockup with Hera and prepare for Matilda meeting
January 6, 2026
Review mockup based on Portugal sales page structure with screenshots and finalized copy. Meeting with Matilda scheduled for January 6th to get feedback before implementation handoff to Ivan.
Forward invoice directly to Emanuel
December 27, 2025
Send invoice covering June-December work directly to Emanuel for processing. Coordinate with Mariko's communication about Phase One investment.
Finalize Phase One pricing details with deposit and milestone schedule
December 27, 2025
Add specific pricing breakdowns by phase to proposal document. Include deposit amount and milestone payment schedule throughout development. Budget range $16K-$29K with commitment to higher end.
Continue LMS and membership system prototyping per six-week timeline
January 25, 2026
Execute development timeline: Supabase foundation-building, user dashboard connected to Webflow CMS, Stripe integration for membership, n8n communication automations. Weeks four and five focus on testing and email integrations. Polish and testing complete by January 25th for February 10th launch.
Hire Supabase specialist and design support for project execution
January 3, 2026
Bring in Supabase specialist for authentication and data management architecture. Hire additional design support (designer who worked on most of Hollow Movement site) to ensure strong brand design across platform. Budget approved at higher range to support team expansion.
Review project management system and provide feedback on features
December 28, 2025
Review AI-powered project management system features including meeting summary generation, action item assignment, live task editing, and conversational agent plans. Provide input on Kanban board views and simplified overview options. Share experience from previous tech company product and customer work.
Complete European landing page mockup with screenshots and finalized copy
January 5, 2026
Create mockup based on Portugal sales page structure. Include screenshots and finalize copy already drafted. Prepare for review with Matilda on January 6th before handoff to Ivan for implementation.
Begin authentication spike with Supabase integration on MAST template
January 10, 2026
Implement Supabase login functionality on MAST template in IRIS Webflow workspace. Establish foundation for user profiles, password management, and session handling that entire membership system depends on. This is the initial development work to validate approach and establish core authentication architecture.
Provide Ivan access to Webflow account using extra client account
January 3, 2026
Grant Ivan access to IRIS Webflow workspace using the extra client account slot. This account is occasionally used by German-based client but will work for Ivan's primary development work. Confirmed Ivan has existing Webflow account that needs workspace access.
Create Supabase account and grant Ivan access
January 3, 2026
Set up Supabase project for Holomovement and provide Ivan with necessary access credentials. This is required before authentication spike can begin.
Provide Ivan access to n8n, GitHub, and Airtable as needed
January 10, 2026
Grant Ivan access to n8n workflows, GitHub repositories, and Airtable bases as development progresses. Access will be provided based on what's needed for specific tasks rather than all upfront.
Duplicate MAST template and prepare as starting point for LMS development
January 3, 2026
Create duplicate of MAST framework template in IRIS workspace as foundation for Holomovement LMS. This template includes component-based architecture, automatic color/class naming, light/dark mode, slot functionality, and custom scripts for style guide management. Will serve as starting point for both Holomovement and future client projects.
Begin authentication spike with Supabase integration on MAST template
January 10, 2026
Implement Supabase login functionality on MAST template in IRIS Webflow workspace. Establish foundation for user profiles, password management, and session handling that entire membership system depends on. This is the initial development work to validate approach and establish core authentication architecture.
Provide Ivan access to Webflow account using extra client account
January 3, 2026
Grant Ivan access to IRIS Webflow workspace using the extra client account slot. This account is occasionally used by German-based client but will work for Ivan's primary development work. Confirmed Ivan has existing Webflow account that needs workspace access.
Create Supabase account and grant Ivan access
January 3, 2026
Set up Supabase project for Holomovement and provide Ivan with necessary access credentials. This is required before authentication spike can begin.
Provide Ivan access to n8n, GitHub, and Airtable as needed
January 10, 2026
Grant Ivan access to n8n workflows, GitHub repositories, and Airtable bases as development progresses. Access will be provided based on what's needed for specific tasks rather than all upfront.
Duplicate MAST template and prepare as starting point for LMS development
January 3, 2026
Create duplicate of MAST framework template in IRIS workspace as foundation for Holomovement LMS. This template includes component-based architecture, automatic color/class naming, light/dark mode, slot functionality, and custom scripts for style guide management. Will serve as starting point for both Holomovement and future client projects.
Update script registry when new scripts are added to template
February 15, 2026
Maintain script registry tool tracking external scripts used across websites. Currently requires manual JSON updates. When new scripts are added to MAST template or Holomovement LMS, update registry documentation.
Report any blockers encountered during initial setup and development
January 10, 2026
Communicate any technical blockers, access issues, or questions that arise during authentication spike and initial LMS development. Ensure smooth coordination between Ivan and James during onboarding and early development phases.
Review knowledge base structure and contribute documentation as work progresses
February 1, 2026
Familiarize with GitHub knowledge base organization (Development, Design, Operations, Platform categories). Contribute documentation for technical decisions, implementation details, and learnings during LMS development. Focus on documenting why architectural choices were made, not just what was built.
Begin authentication spike with Supabase integration on MAST template
January 10, 2026
Implement Supabase login functionality on MAST template in IRIS Webflow workspace. Establish foundation for user profiles, password management, and session handling that entire membership system depends on. This is the initial development work to validate approach and establish core authentication architecture.
Provide Ivan access to Webflow account using extra client account
January 3, 2026
Grant Ivan access to IRIS Webflow workspace using the extra client account slot. This account is occasionally used by German-based client but will work for Ivan's primary development work. Confirmed Ivan has existing Webflow account that needs workspace access.
Create Supabase account and grant Ivan access
January 3, 2026
Set up Supabase project for Holomovement and provide Ivan with necessary access credentials. This is required before authentication spike can begin.
Provide Ivan access to n8n, GitHub, and Airtable as needed
January 10, 2026
Grant Ivan access to n8n workflows, GitHub repositories, and Airtable bases as development progresses. Access will be provided based on what's needed for specific tasks rather than all upfront.
Duplicate MAST template and prepare as starting point for LMS development
January 3, 2026
Create duplicate of MAST framework template in IRIS workspace as foundation for Holomovement LMS. This template includes component-based architecture, automatic color/class naming, light/dark mode, slot functionality, and custom scripts for style guide management. Will serve as starting point for both Holomovement and future client projects.
Update script registry when new scripts are added to template
February 15, 2026
Maintain script registry tool tracking external scripts used across websites. Currently requires manual JSON updates. When new scripts are added to MAST template or Holomovement LMS, update registry documentation.
Report any blockers encountered during initial setup and development
January 10, 2026
Communicate any technical blockers, access issues, or questions that arise during authentication spike and initial LMS development. Ensure smooth coordination between Ivan and James during onboarding and early development phases.
Review knowledge base structure and contribute documentation as work progresses
February 1, 2026
Familiarize with GitHub knowledge base organization (Development, Design, Operations, Platform categories). Contribute documentation for technical decisions, implementation details, and learnings during LMS development. Focus on documenting why architectural choices were made, not just what was built.
Continue LMS backend development at reduced pace while prioritizing directory system
February 15, 2026
Maintain momentum on LMS backend while shifting primary focus to directory system enhancement. Backend infrastructure operational with Supabase and Stripe integration complete.
Connect Synergist functionality with membership capabilities for profile editing
February 10, 2026
Integrate existing Synergist directory features with new membership login system so members can edit their profiles directly. Part of directory system MVP.
Build assessment integration so completed assessments populate user profiles
February 10, 2026
Create system where assessment results automatically add elements to user profiles. Progressive engagement model where users complete assessments over time and see their profiles enhance with each completion.
Create automation for generating profile graphics based on assessment results
February 20, 2026
Develop system generating AI-created icons, tarot card archetypes, or numerology graphics that appear on profiles as users complete different assessments. Gamification element to incentivize deeper engagement.
Set up Airtable integration for DJ Taz digital content curation
January 25, 2026
Configure Airtable base for digital content management with direct CMS connection. Enable DJ Taz and others to manage database while changes appear automatically on site.
Implement feature backlog system for capturing ideas from beta testing
February 15, 2026
Create system for capturing and prioritizing feature requests and ideas generated during beta testing period following MVP launch. Process for tracking ongoing development priorities.
Complete directory system MVP by February 15 with login, profile editing, and assessment integration
February 15, 2026
Deliver minimum viable product including login capability, profile editing functionality, and integrated assessments where completed assessments populate user profiles. Results visible to user and potentially others in network.
Prepare to show LMS progress in future meeting
January 27, 2026
Prepare demonstration of LMS backend progress including Supabase and Stripe integration, membership login, and content gating functionality for upcoming team meeting.
Coordinate with Munia on front-end design for LMS and directory systems
January 25, 2026
Engage Munia (designer who worked on most of Holomovement site) for front-end design work on both LMS and directory system interfaces. Budget approved for additional design support.
Finalize short-form and long-form assessment question sets for directory profiles
February 1, 2026
Define questions for five-minute basic profile setup (name, website, purpose statement, location) and longer detailed assessments. Support progressive engagement model.
Contact iOS Zone of Genius team about partnership for assessment integration
January 31, 2026
Reach out to iOS Zone of Genius team regarding partnership to integrate their assessment into Holomovement platform. Assessment received strong positive response during previous retreat. Technical barriers previously preventing iOS from offering as software now removed by AI capabilities and current infrastructure.
Review and address website copy issues raised by Ali in Slack
January 20, 2026
Address copy issues or concerns Ali raised in Slack regarding website content. Requires review and response.
Organize thoughts on Engine for Good grant program details for Friday discussion
January 17, 2026
Prepare detailed thoughts and framework for Engine for Good grant program including application process, selection criteria, award structure, and integration with directory system for discussion with Hera on Friday.
Prepare detailed thoughts on Engine for Good integration for Friday call with Mariko
January 17, 2026
Develop framework for how Engine for Good grant program integrates with directory system, profile completion incentives, and beta testing strategy. Prepare for Friday discussion.
Share previous Holomovement app work with James to identify features for current build
January 25, 2026
Provide James with documentation, designs, or materials from previous Holomovement app development work to identify features and functionality that should be incorporated into current platform build.
Coordinate with James on project management support and blocking issue resolution
February 15, 2026
Support James by helping track deliverables and identifying any blockers from Holomovement team's side. Ensure smooth communication and rapid response to requests.
Send meeting invites for Monday weekly sessions
January 17, 2026
Send calendar invites for weekly Monday meetings. First meeting January 20 at 10am Eastern, subsequent meetings at 2pm Eastern to accommodate Mariko's schedule.
Review and provide raw data and prompts for Zone of Genius assessment if partnership proceeds
February 15, 2026
If iOS Zone of Genius partnership moves forward, provide raw assessment data and prompts to enable integration into Holomovement platform.
Begin using Airtable for organizing digital content with DJ Taz
February 1, 2026
Team should begin using Airtable for organizing DJ Taz digital content once structure is set up. Content management workflow to be established.
Develop incremental assessment launch schedule leading to Wave event
January 31, 2026
Create schedule releasing new assessments every week or ten days leading to Wave event. Use Ripple gatherings and Miracle Club to promote participation. Plan assessment topics and partnership opportunities.
Design weekly feeling query interface for emotional mapping
March 1, 2026
Create interface where users drag point within six-axis emotional space to indicate current state across dimensions like excitement, nervousness, grief, etc. Data aggregates into visual representations showing emotional climate of community over time.
Send Ripple Tracker pitch deck and prototype video to Michael Sean for review
January 22, 2026
Provide materials for Michael Sean to review and provide integration feedback on how Ripple Tracker connects with Holomovement platform strategy.
Explore adding completion line to Purpose block on About page
January 25, 2026
Add statement to Purpose block clarifying modes of action (gatherings, initiatives, collaborators) to immediately answer 'What is Holomovement?' for first-time visitors.
Create iMessage group for core team communication
January 21, 2026
Set up iMessage group for team since most participants are iPhone users and find it easier to track than WhatsApp.
Update project milestones reflecting directory system prioritization over LMS - Edit 2
January 22, 2026
Schedule meeting within one week to discuss directory system and player card design
January 23, 2026
Set up dedicated meeting with Michael Sean (and potentially others) to dive deeper into directory system questions and player card approach. Thursday 2pm Eastern suggested as option.
Develop partner CMS for dynamic logo display with random ordering
January 27, 2026
Create Webflow CMS collection for partner logos that displays them in random order to avoid hierarchical implications as partnerships grow. Addresses Purpose Earth logo sizing and positioning issues.
Continue LMS authentication, gating, and course content structuring work
February 10, 2026
Maintain development momentum on authentication system, content gating based on membership levels, and three-tier collection structure (courses, modules, lessons) while directory system becomes primary focus.
Refine About page animation with logo movement integrated to scroll
January 27, 2026
Develop text transition animation incorporating logo movement connected to scroll position. Early draft presented in meeting shows direction.
Review Ripple Tracker materials and provide integration feedback
January 25, 2026
Review pitch deck and prototype video from Hera. Provide feedback on how Ripple Tracker integrates with Holomovement platform strategy, particularly around AI implementation and community engagement model.
Lead microgrant program refinement and Engine for Good integration
February 1, 2026
Refine angel grant positioning, convertible note structure, return mechanisms (2x, 3x, 5x), and three model project selection strategy. Ensure program tells good story while technical infrastructure develops.
Improve About page visuals and animations to express higher frequency themes
February 1, 2026
Refine visual design elements and animations to better express collective higher frequency states, emotional scale awareness, and conscious choice themes for Holomovement Effect section.
Provide LMS course content for testing and development
January 27, 2026
Share one of Michael Sean's existing courses to use as test content for LMS development and design validation. Focus on actual user experience and completion rather than just sale point.
Review and simplify copy across About page emphasizing living ecosystem positioning
January 30, 2026
Edit and refine copy throughout About page to emphasize 'living ecosystem' or 'operating system' positioning rather than just 'movement.' Make language as plain-spoken and inspiring as possible.
Draft Holomovement Effect content to replace Underview Effect section
January 27, 2026
Create content focused on collective higher frequency states, emotional scale awareness, and conscious choice to replace underwater wave imagery and Underview Effect section which will move to Wave page.
Provide partner logos for CMS implementation
January 27, 2026
Gather and provide logos for partners to populate new partners CMS collection for dynamic random-order display on About page.
Determine first Wave project budget and grant amounts
January 31, 2026
Finalize budget for initial Wave project grants within $1,500-$5,000 range and determine how many grants to award. Consider matching grant opportunities with partners like Kinship Earth.
Create proposal for matching system strategy distinguishing individuals from groups/Holons
January 30, 2026
Develop strategy clarifying how to think about individuals versus Holons in matching system. Define matching criteria prioritizing actionable information: developmental stage, experience level, current project involvement, specific skills, and active needs rather than personality assessments. Post question in Slack for team input and stakeholder proposals.
Create simple Kanban view showing current priorities with effort estimates
January 27, 2026
Build Kanban view or simple text document listing current priorities, in-progress work, and needed items. Include estimated effort hours and comparison to previous weeks' estimates. Doesn't require elaborate tooling - even five active initiatives with effort estimates would suffice. Focus on manual curation rather than auto-generated AI initiatives.
Post matching system strategy question in Slack for team input
January 24, 2026
Post question about individual versus Holon matching approach in Slack channel. Enable stakeholder proposals following decision-making process: identify need, gather proposals, proceed with single unopposed solution. Address architectural questions about Holon entity management and matching criteria.
Update initiatives to reflect agreed priority plan focusing on directory and membership systems
January 27, 2026
Revise initiative priorities and descriptions to reflect directory system and membership system as top priorities. Deprioritize LMS and communication automation features until directory completion. Update status and timelines accordingly.
Review weekly priorities and identify resource needs or dependencies
January 27, 2026
Provide ongoing feedback on weekly priorities during Monday meetings. Identify resource needs, dependencies, or blockers requiring team decisions. Ensure development work aligns with strategic priorities and business model clarity.
Design basic intake form capturing development level, experience, life stage, purpose, and current needs
February 8, 2026
Create streamlined intake assessment focusing on actionable matching criteria rather than personality typing. Include: developmental stage, experience level, life stage, purpose statement, current project involvement, specific skills, and what person is actively seeking. This serves as primary assessment everyone completes for matching foundation.
Address profile image standardization to resolve visual consistency issues
February 10, 2026
Resolve visual inconsistency in directory card display caused by users uploading non-square images that get truncated. Establish image requirements, provide guidance to users, or implement automatic cropping/formatting to ensure consistent card-based profile appearance.
Clarify business model regarding paid vs free memberships and beta period
February 1, 2026
Define membership pricing model and whether free introductory memberships will be offered through May as beta period. Clarify this before completing Stripe integration and membership system features. Discussion referenced offering potentially free memberships initially.
Establish sprint planning and weekly goal-setting process
January 27, 2026
Implement weekly sprint planning sessions establishing development goals, tracking actual hours against estimates, and building understanding of development velocity. Document first sprint outcomes showing estimated vs actual effort. Use to improve future estimation accuracy and pricing confidence.
Deliver working membership system on Holomovement site for team testing by end of week
January 31, 2026
Backend is 90% complete. Deploy working version allowing team to create accounts, log in, and edit profile data. Front end will be minimal at this stage with mainly login pages until profile pages are developed. Primary goal for this week.
Add LMS initiative back to Airtable Kanban board
January 26, 2026
Move LMS back to active priority to support Choose Love course launch. Ensure initiative is visible on Kanban board for tracking.
Share User & Group Architecture document in Slack for team feedback
January 27, 2026
Document outlines philosophical and technical considerations for how users, individuals, and groups are categorized within the system including Individual/Holon/Alliance structure, three-admin model, matching hierarchy, and taxonomy approach. Team needs to review and provide feedback.
Create sandbox database with core team as first test users for profiles, holons, and alliances
February 3, 2026
Set up sandbox database with core four team members to test individual profiles, Holon creation with three-admin model, and Alliance affiliations. This validates system architecture with real-world use cases before expanding to broader team and migrating existing user data. Team will create their own profiles, register businesses as Alliances, and form Holons based on actual project work.
Implement three-admin confirmation system for Holon creation
February 9, 2026
Build multi-step process where one person drafts Holon and identifies two other administrators by email, those two individuals receive confirmation emails, and once they confirm participation (creating individual profiles if needed), the Holon profile goes live. Ensures all Holons have three administrators for security and continuity.
Develop player card UI with icons and AI summaries for scannable profiles
February 10, 2026
Create player card interface featuring icons to symbolize key information, AI-generated summaries to condense lengthy profile responses, and achievement badges displaying completed courses, assessments, and accomplishments. Design iteration process where team can scan test cards to validate information hierarchy. Goal is making discovery process feel intuitive like scanning game card where you can immediately grasp someone's vibe, interests, and needs without reading extensive text.
Add Boldly course content to LMS as second priority this week
January 31, 2026
Implement embed codes for four Boldly course videos as test content to validate LMS functionality and understand development timelines before committing to Choose Love course schedule. Michael Shaun Conaway will provide the embed codes.
Provide embed codes for 4 Boldly course videos to James
January 29, 2026
Share embed codes for four existing Boldly course videos to use as test content for LMS development and design validation. This will allow team to validate LMS functionality and understand development timelines before committing to Choose Love course schedule.
Review and provide feedback on User & Group Architecture document in Slack
January 30, 2026
Review comprehensive architecture document covering Individual/Holon/Alliance structure, three-admin model, matching hierarchy, taxonomy approach, and filtering categories. Provide feedback on framework before implementation begins.
Review and provide feedback on User & Group Architecture document in Slack
January 30, 2026
Review comprehensive architecture document covering Individual/Holon/Alliance structure, three-admin model, matching hierarchy, taxonomy approach, and filtering categories. Provide feedback on framework before implementation begins.
Review and provide feedback on User & Group Architecture document in Slack
January 30, 2026
Review comprehensive architecture document covering Individual/Holon/Alliance structure, three-admin model, matching hierarchy, taxonomy approach, and filtering categories. Provide feedback on framework before implementation begins.
Create individual profiles, holons, and alliances as first test group in sandbox database
February 7, 2026
Once sandbox database is ready, create own individual profile, register business as Alliance, and form Holons based on actual project work. This real-world testing validates system architecture and demonstrates how Holomovement operates internally.
Create individual profiles, holons, and alliances as first test group in sandbox database
February 7, 2026
Once sandbox database is ready, create own individual profile, register business as Alliance, and form Holons based on actual project work. This real-world testing validates system architecture and demonstrates how Holomovement operates internally.
Create individual profiles, holons, and alliances as first test group in sandbox database
February 7, 2026
Once sandbox database is ready, create own individual profile, register business as Alliance, and form Holons based on actual project work. This real-world testing validates system architecture and demonstrates how Holomovement operates internally.
Share updated Iris app prototype link with the team for review
February 10, 2026
Share the current working prototype URL so team can see progress on member profile and directory system. Discussed at 03:22.
Integrate profile creation, editing, and authentication into refined UI by end of week
February 14, 2026
Move from basic functional prototype to more polished interface with profile creation, editing, viewing, and password reset functionality integrated into the improved UI hosted on Holomovement site. Discussed at 09:35.
Coordinate with Munia to finalize first draft UI designs and share for team feedback
February 14, 2026
Munia is developing the first draft UI for the member profile and directory system. Expected within next few days. Once complete, share with team for review before moving into full development. Discussed at 01:00:15 and 01:00:46.
Build simple functional prototype for core team testing by end of February
February 28, 2026
Create working prototype that core team can interact with meaningfully - not just viewing but actually creating profiles, testing features, and providing feedback. Discussed at 24:55.
Create profile image preview function to standardize uploads and prevent display issues
February 21, 2026
Build preview functionality that helps users upload appropriately sized square images and avoid issues with horizontal logos or pixelation. Address visual consistency issues in directory card display. Discussed at 58:29.
Set up app at separate subdomain (app.holomovement.net) to host member-only functions
February 21, 2026
Host app functionality on app.holomovement.net rather than integrating into main website. Enables member-specific navigation for logged-in users while syncing public profile data to main site's member globe. Follows common SaaS patterns accommodating courses, member directory, and other app functionality. Confirm approach with Mariko who was traveling. Discussed at 01:04:00.
Help refine initial feature set and provide necessary materials to Munia for UI finalization
February 14, 2026
Support UI design process by refining feature priorities and providing Munia with necessary context, content, and materials for the directory/profile system UI. Discussed at 01:00:25.
Outline 2-3 concrete project milestones between now and first user testing phase
February 14, 2026
Define clear milestones for the period between now and when broader user testing begins. Help team track progress and identify dependencies. Discussed at 01:00:48.
Clarify biggest unknowns and assumptions with James to understand potential timeline impacts
February 14, 2026
Work with James to identify the biggest unknowns that could push the timeline and clarify assumptions being tested in the current development sprint. Discussed at 01:03:09 and 01:03:24.
Lead discussion on minimum viable intake form fields and assessment design
February 14, 2026
Define and finalize minimum viable intake form keeping system simple. Core fields agreed: name, DOB, email, phone/SMS/WhatsApp, location, purpose/mission, gifts and requests, alliance affiliations, short bio (150 words max), photo. Discussed at 27:15.
Coordinate with Emmanuel regarding potential assessment questions to gauge user alignment
February 21, 2026
Work with Emmanuel on developing assessment questions that help gauge user alignment for matching purposes. Discussed at 40:20.
Define initial recommendation logic focused on purpose, needs/offers, complementary skills, and location
February 21, 2026
For MVP, focus on simpler connection signals rather than complex numerical compatibility scores: complementary skills, matching needs and offers, alliance/affiliation overlap, geographic proximity, shared purpose domains. AI interpretation via Claude for free-text fields, direct computation for explicit matches. Discussed at 44:00.
Review onboarding language to ensure clarity and simplify key concepts for new users
February 21, 2026
Keep explanations simple for onboarding: 'a holon is a group of people with a shared project or outcome' rather than introducing full theoretical framework upfront. Review all user-facing language for accessibility. Discussed at 54:30.
Oversee affiliation management strategy limiting to community-relevant entities
February 21, 2026
Define and manage the approach to alliance affiliations within the system, ensuring affiliations are limited to community-relevant entities rather than open-ended. Discussed at 56:40.
