Development Review
Artifact info
Title:

Holomovement App — Beta Readiness, Assessment System & Wave Planning

Engagement:

Holomovement App Ecosystem

Client:

Holomovement

Meeting Date:
March 16, 2026
Next Meeting Date:
April 6, 2026
Hide This
March 25, 2026
Hide This
March 26, 2026
Hide This
March 30, 2026
Hide This
March 9, 2026
Hide This
March 2, 2026
Hide This
February 25, 2026
Hide This
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 21, 2025
Hide This
November 14, 2025
Hide This
People
Michael Shaun Conaway
James Redenbaugh
Hera Rose
Mariko Pitts
Artifact Image
Meeting Summary

🗂️ Context & Funding Deck Preparation

Mariko opened the call with an immediate need: a concise, updated document summarizing what the Holomovement app ecosystem is, where it stands today, and where it's heading — something she can feed into funding decks for an upcoming appearance at the Global Philanthropy Forum in San Francisco (03:40). The original white paper that guided early phase planning no longer reflects how far the build has come, and she needs something investors and collaborators can actually absorb quickly.

James noted he already maintains a detailed backend description of the entire app written to keep Claude [tag="claude"] oriented throughout development — and offered to translate that into a human-readable document covering current state, forward vision, and what makes the platform genuinely unique (04:18). Mariko confirmed this would be the primary source material for the deck.

Hera suggested pairing the written summary with a visual roadmap slide — short, medium, and long-term phases represented through imagery rather than text-heavy timelines, consistent with how startup pitch decks typically communicate a product trajectory (07:05). She also mentioned having a pitch training checklist from her startup days that can be used to stress-test the deck against investor expectations, and committed to digging it out of her old email.

Notebook LM & AI-Generated Explainer Content

Mariko shared a live demo of Google's Notebook LM — a Gemini-powered research tool she's been using to transform dense source documents into investor decks, infographics, and explainer videos (08:10). She fed it the Holomovement Theory of Change document and it produced a polished, six-minute explainer video narrating the philosophy clearly enough that even team members heard the David Bohm origin story in a new light.

The team agreed this format is excellent for internal alignment — a unified reference that helps the whole core team explain what the Holomovement is in a consistent way — but James flagged that for any public-facing version, the stock imagery should be swapped out for actual brand assets, since Notebook LM outputs are becoming recognizable as a template (20:06). For now, using it internally and for investor conversations is the right call. Mariko's plan is to combine James's app description, the new homepage copy, and the Purpose Earth impact content into a single Notebook LM source, then prompt it to generate an investor deck hitting the key pitch checklist points Hera will provide.

---

🏗️ App Development Status

James walked through the current state of the build with a live screen share. All major structural components are now built and functional in Webflow [tag="webflow"], and the focus is on connecting the pieces and resolving remaining bugs before handing off to the core team for testing (22:25).

Member Wheel & Directory

The member wheel — the circular UI that displays connected users — is working and renders cleanly, with CSS-based staggering in progress to handle larger groups gracefully. The directory is functional with search and filter by individual, Holon, or domain. A few small polish items remain: hover-only button reveal, card text positioning, and a minor flip animation bug on card interaction (24:27).

[technology="Directory Systems"]

Connection Assessment

The assessment tool is one of the most notable pieces of new functionality. It presents users with a series of questions across five domains — each randomized in direction so answers can't be gamed by dragging everything one way — and produces a dynamic chart on the results page (25:06). Rather than a standard spider graph, James designed a custom radial visualization that's more expressive and interesting, mapping orientation across dimensions like ecological identity, time horizon, and collective focus.

Key behaviors worth noting:

  • Progress saves as soon as the user begins, so they can return and pick up where they left off
  • Completed assessments redirect to the user's connection profile
  • The results chart responds dynamically — green toward the integrative/transformational end, purple toward the analytical/independent end
  • Written analysis is generated from pre-authored statements mapped to each domain combination, with no AI processing required at runtime — making it extremely fast (28:34)

The data stored in Supabase [tag="supabase"] is lightweight: domain scores as simple numerical values, making it highly efficient for initial mathematical sorting before any agent-based matching logic runs (33:48).

[technology="Assessment Systems"]

The team discussed placement and surfacing. The consensus was:

  • An Assessments page should exist as a primary nav item, since additional assessments (numerology was floated as an early candidate) will follow
  • New users should be prompted to complete the assessment before matching begins, ideally through a floating onboarding checklist — similar to Mighty Networks' approach of a persistent, dismissible progress widget with dopamine-hit checkoffs for each completed step (36:47)
  • The checklist should be smart enough to not resurface for tasks already completed
  • MVP version: a simple pop-up reminder linking directly to the assessments page; the full gamified checklist with state tracking comes in a later pass
Holon Profile & Creation Flow

The Holon creation page has been updated and is nearly ready for team testing (42:01). James wants to add a few fields before opening it up:

  • Location toggle (remote vs. geographic, with city/region if local)
  • Social links (website, Instagram) that only render if populated
  • A join vs. request-to-apply toggle — for Holons that aren't open enrollment, a request flow would trigger an automated notification to Holon admins

On the Holon profile display, the team agreed to center the purpose statement prominently, with the join/request CTA moved lower (47:42).

[technology="Custom Membership System"]

Payment Integration

Stripe [tag="stripe"] and PayPal are both integrated and currently in sandbox mode. The team needs to finalize which features sit behind payment before going live (48:12). Mariko's current thinking:

  • The Holomovement introductory course — likely a suggested donation model, low barrier, to maximize reach
  • The Choose Love course and others — one-time payments, priced with a minimum regardless of membership status
  • Courses are not included in the base membership automatically; they're standalone purchases

[technology="Online Learning Platforms"]

---

🚀 Beta Testing & Launch Timeline

The immediate plan is to get the core team into the app for real profile creation — not test entries, but actual profiles, Holon builds, and completed assessments — so there's meaningful data in place before matchmaking development begins (52:30). James confirmed that matchmaking is the next major development priority and estimated it could be completed within about a week of focused work, with a target of end of next week (53:58).

[technology="Intelligent Matching Algorithms"]

Proposed milestones:

  1. This week — James sends updated links; Mariko and Hera test for blocking bugs; core team begins real onboarding
  2. End of next week — Matchmaking feature complete
  3. Week of April 6 — Internal team review and final bug sweep
  4. April 9–13 — Public beta launch, framed explicitly as a public beta (not a full release), opening the door for Holon groups to create profiles and apply for micro grants (01:03:34)

The Holon onboarding pathway is being designed around grant incentive: groups applying for micro grants must complete their profiles, build their Holon, do the assessments, and actively use the system — not just fill out a form. The first round of awardees will be announced at the Wave event in May, and at least some recipients will be selected in advance with the expectation that a member attends in person to receive the award (58:03). Hera will connect with Jill to retrieve the existing grant application materials so James can see the form structure and determine how it integrates into the Holon profile page — likely as a simple "Apply for Micro Grants" CTA with a first-round deadline noted.

---

🌊 Wave 2026 — App Integration & Event Experience

The Wave event in May surfaced as a significant activation moment for the platform. Several ideas were discussed:

  • Wave 2026 page within the ecosystem — a members-only view for registered attendees showing who else is coming, who they're matched with, and relevant event info. Distinct from the public-facing Wave page (01:05:12)
  • Wave-specific pre-event assessment sent to attendees to surface connection recommendations before they arrive, so people can identify who they want to find in the room (01:04:30)
  • Holons created for each track or workshop, so attendees can post reflections, follow-up questions, and continue conversations that started in sessions — addressing the recurring reality that there's never enough time to talk at conferences (01:10:40)
  • Monday Activation Day structured as parallel working sessions across tracks (tech, conscious business, impact, etc.) — with the potential for visual facilitation capturing real-time themes across tables, possibly through a digital artist or word cloud display. Stonehouse, who did visual animation at the first Wave, was mentioned as a candidate (01:13:58)
  • James raised the idea of creating pathways for community members to eventually build their own assessments or contribute features — framing the ecosystem as genuinely community-driven over time (01:09:22)

James was confirmed as a core team attendee for the Wave, bringing his partner Emily. Mariko indicated he'll receive core team pricing: a private room at the partner rate plus the standard symbolic donation contribution.

[technology="Community Facilitation Tools"]

---

Action Items

James Redenbaugh

  • Generate human-readable app description document — current state, forward vision, what makes it unique — for Mariko's deck work; deliver today (04:18)
  • Fix member wheel, directory card layout, and flip animation bug; link new profile and directory pages into the live environment tonight (22:25)
  • Test profile creation end-to-end; confirm it's stable before core team onboarding begins (45:19)
  • Add location toggle, social links, and join/request flow to Holon creation and profile pages (46:18)
  • Center purpose statement on Holon profile display, move CTA lower (47:42)
  • Finalize Stripe [tag="stripe"] / PayPal sandbox setup; confirm paid vs. free/donation structure for courses with Mariko (48:12)
  • Send updated app links to Mariko and Hera as soon as profile and directory pages are connected (51:35)
  • Begin matchmaking development as next primary focus; target completion by end of next week (53:58)
  • Share matchmaking feature requirements and tagging needs with the team so preparation can happen in parallel with profile population (53:49)

Mariko Pitts

  • Compile Notebook LM source documents (James's app description, new homepage/about copy, Purpose Earth impact content) and generate investor deck draft; integrate Hera's pitch checklist once received (08:10)
  • Review onboarding page copy and provide stronger call-to-action language for the final section (42:36)
  • Test updated app links with Hera once James sends them; confirm no blocking bugs before core team is invited in (51:35)
  • Coordinate core team onboarding communications — get everyone creating real profiles, building Holons, and completing assessments this week (52:30)
  • Define and communicate grant application timeline to Emmanuel: open to Holons early April, award announcements at the Wave in May (01:01:04)
  • Confirm micro grant budget allocation and round structure (first round at Wave, second round ~July) (59:30)

Hera

  • Locate pitch training checklist from startup background and share with Mariko for deck integration (17:40)
  • Contact Jill to retrieve complete grant application materials; share in the Holomovement Slack for team reference (56:24)
  • Note Wave core team accommodations: James + Emily, private room, core team rate — 100 donation each + 200/night for three nights (01:06:30)
Relevant Initiatives
No items found.
Transcript