Strategy Meeting
Artifact info
Title:

App Sync

Engagement:

Holomovement App Ecosystem

Client:

Holomovement

Meeting Date:
November 21, 2025
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 19, 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 14, 2025
Hide This
October 24, 2025
Hide This
People
Hera Rose
Mariko Pitts
James Redenbaugh
Laura Rose
Emanuel Kuntzelman
Michael Shaun Conaway
Alex Melnyk
Artifact Image
Meeting Summary

Platform Vision and Blueprint Presentation

James Bolden (Redenbaugh) presented a comprehensive visual blueprint mapping the entire Holomovement digital ecosystem, organizing features by development status (built, in development, planned) and phases (12:28).

Existing Assets:
  • Interactive community map with profile system already live and serving as foundation
  • Profile directory and search functionality in active development
  • Color-coded visualization showing full ecosystem from community features to video rooms to calendar systems

[technology="Directory Systems"]

Core Feature Categories Identified:
  • Community Infrastructure: Profile editing capabilities, directory interfaces, messaging systems via TalkJS [tag="talkjs"] integration
  • Group Coordination: Holon pages, alliance directories, group chat, facilitation features using N8N [tag="n8n"] automation
  • Live Connection: Video meeting rooms using Daily.co [tag="daily-co"] SDK with radial interface designs, themed weekly lounges
  • Event Management: Community calendar with member-created events, recurring schedules, "add to calendar" functionality
  • Collaboration Tools: Flow sessions inspired by Flow Club for co-working throughout the day

[technology="Community Facilitation Tools"][technology="Video Conferencing Solutions"]

The blueprint serves as both a planning document and creative space for the committee to visualize interconnections and prioritize development phases.

Design Philosophy and User Experience Priorities

Michael Shawn Conaway emphasized critical UX principles: simplicity over complexity, building from user certainty rather than clever ideas, and ensuring features are modular for future app integration (18:35, 21:47).

Key Strategic Questions Raised
  • Which features have highest certainty of user engagement versus risk of being unused?
  • Can each feature be explained compellingly in one or two sentences?
  • How do we separate what's useful from what's clever?
  • What's the narrative that makes someone want to try each feature?

Laura Rose raised questions about clear user pathways through the platform and avoiding overwhelming users with too many options simultaneously (23:46). The team acknowledged the need to focus rather than "throw 50 things at people and ask what engages them."

User Journey Framework Emerging

The conversation converged on a simple, powerful flow: Individual Discovery → Connection → Collaboration → Action → Funding. This became the throughline for prioritizing features, with assessments serving as entry point and micro-grants as culmination.

Assessments as Strategic Entry Points

James Bolden demonstrated how the AI-powered assessment prototype already automates personalized recommendations based on user responses and synergist profile data (40:15).

[technology="Assessment Systems"]

Current Capabilities and Potential
  • Matching algorithm draws from ~100 existing synergist profiles to create immediate connections
  • System recommends 4-6 aligned individuals based on purpose, worldview, development stage, skills, timezone
  • Can be expanded to form cohorts, breakout groups, buddy systems for Wave attendees
  • Automation enables follow-up communication, meeting facilitation, progress tracking via N8N [tag="n8n"] workflows

[tag="claude"]

Hera Rose clarified assessments function as lead magnets with multiple pathways: forming holons, joining courses, connecting with individuals, participating in purpose lab groups, or downloading partner apps (46:38). Each assessment result can trigger different user journeys based on their orientation toward collaboration, leadership, or community building.

Mariko Pitts emphasized these aren't just new features but responses to years of community feedback asking for connection and belonging mechanisms (31:13). The assessments deepen existing synergist profiles by adding numerology data, AI-generated recommendations, and purpose archetype information visible on the community map.

Technology Stack and Development Approach

The platform leverages modern tools enabling rapid prototyping without heavy engineering overhead: [tag="webflow"], [tag="airtable"], [tag="daily-co"],[tag="talkjs"], [tag="n8n"] automation, and [tag="claude"] AI integration.

Demonstrated Prototypes

James showed working video meeting room prototype with participants joining simultaneously, dynamic circular layouts adjusting to participant count, and customizable backgrounds/themes (01:01:51). He also demonstrated an asynchronous group introduction tool where members answer questions via text and audio, creating engagement before in-person gatherings.

Mariko highlighted the transformative shift: "A lot of the stuff we're scheming up and dreaming is now possible because of AI and was not possible a few months ago" (55:04). Features can be tested cheaply through N8N [tag="n8n"] automations, evaluated for stickiness, and removed without significant cost if unsuccessful.

Modular Architecture Principles

Michael Shawn stressed building features that remain evergreen and can bolt into future systems without redevelopment (21:47). The team agreed to design with eventual full app migration in mind, ensuring current web-based features translate cleanly to native mobile experiences.

The database architecture will support both desktop collaboration tools and mobile communication features accessing the same data with device-appropriate interfaces.

Strategic Positioning and Unique Value

The platform addresses a specific gap: activists and synergists already in action need collaboration infrastructure, not motivation to act (01:16:23).

Target User Reality

Mariko clarified that Holomovement attracts people already doing permaculture, planting trees, running initiatives who want to find aligned collaborators and access a unified ecosystem (01:18:23). Wave events spawn holons and hubs that currently lack a home platform to coordinate and amplify their work.

This insight shifts development priorities from broad spiritual seeker tools toward targeted collaboration features serving groups and movements already generating impact.

Micro-Grants as "Killer App"

Michael Shawn identified the potential power of the full user journey: "Come find out about yourself, connect to other people, propose a project together, and actually get funded to do that project" (50:58).

Even without immediate funding available, the promise of micro-grants motivates participation. Start with small pilots testing ideas in local contexts over a weekend, build evidence of success, and create pathways to larger funding. This prepares groups to raise real money externally by demonstrating traction.

The grants can be gated behind membership and participation requirements (joining holons, engaging in conversations), creating intrinsic motivation loops while building community health metrics.

Movement of Movements Architecture

James emphasized the platform must serve groups and communities as primary users, not just individuals (37:54). Holomovement is positioned as a "movement of movements" providing home and resources for diverse projects to interconnect.

Beyond Online Platform

The product includes in-person Wave events as integral components, not separate from digital features. Development should increase value for Wave attendees before, during, and after events through:

  • Pre-event assessment and buddy matching
  • During-event group formation using collected data
  • Post-event project continuation and resource access

Mariko referenced the "Mycelium network" vision where sovereign projects maintain independence while feeding and fueling the interconnected whole (55:04). Years of feedback inform this direction, but technology now exists to actually build it.

Leadership Pathway Integration

The platform will incorporate leadership development courses (Holomovement Course, Choose Love Movement, Purpose Lab) as evergreen offerings behind the membership paywall (58:48). These resources support users evolving from personal discovery to collective leadership roles.

[technology="Online Learning Platforms"]

James expressed interest in creating tools for collaboration and action timing, showing a project management prototype built on Webflow [tag="webflow"] where teams can visualize work over time, not just in feeds (01:08:08). This reflects broader vision of helping groups coordinate and track their collective impact.

[technology="Time-Aware Toolsets"]

Desktop vs. Mobile Strategy

Laura Rose asked whether advancing web capabilities might reduce need for separate native app (01:11:34). The team clarified the multi-layered answer:

Platform-Appropriate Features

Michael Shawn explained an app is simply "a thing on my phone I click a button on" - web features can be containerized for app stores (01:11:39). The key is understanding which features belong on which platform:

  • Desktop: Collaboration, building, creating, project management
  • Mobile: Communication, messaging, learning, lightweight engagement

Alex Melnyk emphasized global accessibility requires strong mobile optimization since many international users primarily access via phones (01:15:57). Demographics skew toward activists already using computers for work, but reaching younger, broader audiences demands excellent mobile experience.

The architecture will share databases between desktop and mobile with tailored interfaces per platform, avoiding duplicate development while serving different use contexts.

Next Steps and Development Priorities

The team aligned on need for focused product roadmap defining top 2-3 features for immediate build with clear timeline and cost estimates (01:22:44).

Immediate Priorities Identified
  1. Refine Layer 2 blueprint into specific, phased development plan
  2. Integrate Holomovement course timeline into platform roadmap
  3. Define membership/donation platform specifications
  4. Prepare investor packages alongside development
  5. Establish clear user personas (Wave attendees, synergists, donors) and map detailed journeys

James committed to delivering recommendations based on discussion, including technical scopes and tangible timelines for features he's confident can be built effectively (01:25:43). Cost estimates and development phases will be shared with Emanuel, Laura, Hera, and Mariko for resource planning.

Mariko emphasized starting with James's assessment of what's doable and sticky, combined with necessary enhancements to existing website features (01:25:37). The goal is tight development sprints with clear milestones leading to beta testing before the Wave.

The team acknowledged need for continuous feedback loops throughout development, installing multiple mechanisms to gather usage data and iterate rapidly (29:55). This adaptive approach prevents overbuilding while maintaining focus on high-impact outcomes.

Action Items

James Bolden

  • Create refined product roadmap with top feature recommendations based on meeting discussion, including specific phases and technical scopes (01:25:43)
  • Provide detailed cost estimates and timelines for proposed Layer 2 development to Mariko, Emanuel, Laura, and Hera (01:26:03)
  • Share development recommendations for both essential website enhancements and new sticky features based on prototypes and technical feasibility (01:25:37)

Mariko Pitts

  • Send Holomovement course documents and timeline to James and Michael Shawn for integration into platform development roadmap (01:25:37)
  • Schedule next committee meeting post-Thanksgiving to review product roadmap and finalize phase priorities (01:22:44)
  • Coordinate with James on membership/donation platform specifications and investor package development (01:25:59)

Hera Rose

  • Support detailed user persona development and customer journey mapping for primary user types (Wave attendees, synergists, donors) (29:55)
  • Continue mapping feedback loops and engagement optimization strategies to inform iterative development (29:55)

Michael Shawn Conaway

  • Review Holomovement course timeline and materials when shared by Mariko (01:25:37)
  • Provide ongoing UX guidance and validation approaches for feature development

Laura Rose

  • Review product roadmap, development costs, and scope recommendations from James when delivered (01:26:03)

Emanuel Kuntzelman

  • Review technological scope and provide feedback on vision and investment planning with Mariko and James (01:26:03)
Relevant Initiatives

Assessment Development

Priority: 
High
Size: 
Planning Stage

Holomovement App

Priority: 
High
Size: 
XXL
Planning Stage
Transcript