Strategy Meeting
Artifact info
Title:

Holomovement App — Onboarding Flow, Stripe Integration & Launch Readiness

Engagement:

Holomovement App Ecosystem

Client:

Holomovement

Meeting Date:
May 4, 2026
Next Meeting Date:
May 11, 2026
Hide This
April 27, 2026
Hide This
April 27, 2026
Hide This
April 27, 2026
Hide This
April 30, 2026
Hide This
April 20, 2026
Hide This
April 6, 2026
Hide This
March 25, 2026
Hide This
March 26, 2026
Hide This
March 30, 2026
Hide This
March 16, 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
People
Michael Shaun Conaway
James Redenbaugh
Hera Rose
Mariko Pitts
Artifact Image
Meeting Summary

🎯 Strategic Context

With the Lisbon Wave approximately three weeks out, the team focused this session on the critical path to launch: refining the onboarding flow, finalizing the Stripe donation integration [tag="stripe"], and preparing for a coordinated testing party to seed the platform with 100+ engaged users before the global broadcast. The team also surfaced unresolved questions around the Engine for Good nonprofit banking setup and the platform's eventual name.

💳 Engine for Good & Stripe Integration

Wise Bank Account Path Forward

The team opened with the urgent need for Engine for Good to establish a functional bank account to receive Stripe payouts. Michael Shaun recommended Wise as the fastest route — typically 2-3 days to open a nonprofit account with multi-currency capability (00:55). This would allow Stripe to hold currency in different denominations (EUR, GBP, USD) without forcing currency conversion at the gateway level.

Mariko committed to lighting a fire with Laura to get this moving, noting that existing Holomovement bank accounts (Wind Trust, Charles Schwab) don't integrate with Stripe. As an interim safety net, Michael Shaun offered to set up a Stripe account through Imaginal to avoid blocking the launch if the Engine for Good account isn't ready in time.

Donation Page Redesign

James walked the team through the current Stripe checkout experience, surfacing several decisions:

  • Redesign as one slider (1–$1000) with a toggle for monthly, annual, or one-time contribution
  • Set a minimum contribution of $12/year (or $1/month) — no fully free tier, since every user consumes operational resources
  • Add clear copy explaining the Engine for Good: 100% of contributions fund micro-grants back to the community via Purpose Earth
  • Reframe the language from "donation" to "contribution" or "gift" — charging the collective battery (00:59:55)
  • Implement profile creation in parallel with checkout so users don't wait for backend processing after payment (04:54)

[technology="Custom Membership System"]

Visibility of Contributions

James proposed pulling Stripe data back into the platform to make collective giving visible — showing monthly totals raised, where funds are flowing, and eventually showcasing funded projects from Purpose Earth. Michael Shaun cautioned that real-time contribution feedback only works once volume is sufficient, so this should be a post-launch enhancement.

📝 Onboarding Flow Redesign

Reducing Friction at Entry

The current sign-up flow asks four big questions upfront — bio, purpose, what you're seeking, what you're offering — which Alex's testing revealed as a significant barrier (05:51). The team aligned on splitting the flow:

  1. Minimum entry: name, password, photo, payment
  2. Profile depth questions moved to a deferred completion step
  3. Domain selection (12 domains) placed first as a low-barrier entry point before freeform bio writing

Michael Shaun emphasized that since this is a utility app, not entertainment, users should be told upfront: "This is going to take 10–15 minutes. You can put short answers and update later, but the quality of your connections depends on the quality of your profile" (36:18).

Floating Checklist & Persistent Reminders

Hera proposed a floating checklist UI inspired by Mighty Networks — a persistent but unobtrusive fixture reminding users of next steps: complete profile, take assessment, explore the map, contribute to Engine for Good. James suggested integrating this into the existing modal where the dark mode switch lived, with notifications surfacing the next 1–2 actions rather than the full list.

[technology="Assessment Systems"]

Profile Photo Requirement

The team agreed users must upload a photo (any image, not necessarily of themselves) before appearing in the directory. This prevents the degraded community experience of incomplete profiles and forces a moment of intentional choice during onboarding.

Pre-Sign-up Browsing

To reduce conversion friction, guests will be able to browse the directory and map before signing up, but with restricted depth:

  • Profile cards visible but click-throughs route to a demo profile (e.g., "Johnny Holomovement") or a short carousel/video preview
  • Holons, assessments, and connections grayed out with sign-up prompts
  • Demo experience showcases the assessment, matching, and Holon functionality before asking for commitment

🤝 Connection System Progress

James demonstrated the upgraded connection assessment matching system, which now visualizes alignment between members on a triangle/mosaic. Layer 1 (algorithmic matching) is working well and uses tags generated from members' seeking and offering responses, with semantic correlation (e.g., "seeking a mentor" matches "offering mentorship" even without exact word overlap). Layer 2 — the agentic response that generates plain-English explanations of why two people match — is close to completion.

[technology="Intelligent Matching Algorithms"]

The team also confirmed that Holon creation now auto-generates a group chat [tag="talkjs"], with members automatically added/removed as the Holon roster changes. Michael Shaun requested a direct chat-access button on the Holon page itself for easier navigation.

[technology="Community Facilitation Tools"]

📞 Customer Support Approach

For launch-phase support, the team agreed on a lightweight setup:

  • Support email and WhatsApp business number added to app feedback area
  • Support avatar in the messaging system so users can message support directly inside the app [tag="talkjs"]
  • Michael Shaun flagged a potential team member (Amy) who could monitor support during the wave window
  • Long-term: build an AI agent for first-line support, especially to handle predictable issues like password resets

[technology="Communication Automations"]

🧪 Testing Party Plan

Hera proposed a coordinated live testing session where participants test the app together on a single call, guided through a defined journey to surface bugs and UX issues consistently. The team agreed this is the only realistic way to get meaningful feedback from invited testers.

  • Target: Wednesday or Thursday this week, ~12 participants
  • Repurpose the former Pro-Social call slot (now ended) for testing before the core team call
  • Goal: 100 users onboarded before the wave event, prioritizing near-community members and wave registrants

🌐 Domain & Launch Sequencing

The team confirmed the priority sequence for this week:

  1. Finalize sign-up + contribution flow (highest priority)
  2. Move app to app.holomovement.net (5-minute change once GoDaddy access is sorted)
  3. Update the map before going wider
  4. Begin invitations to near community + wave registrants
  5. Add a link from the main Holomovement site when ready

💡 Ecosystem Vision: Projects, Holons & Hubs

Michael Shaun shared evolving thinking from conversations with Kevin Triplett about deeper orchestration capabilities:

  • Project post type — members can post projects that are visible across the ecosystem
  • Holons can contain multiple projects; projects can seek Holons and vice versa
  • Hubs = collections of Holons + projects (e.g., Kevin's Project Weave as a hub)
  • Project intelligence layer: AI surfacing duplicate efforts, complementary work, and cross-Holon collaboration opportunities

Michael Shaun strongly advocated for no walled gardens — hubs should benefit from the broader ecosystem, not silo themselves. Mariko and James agreed: multi-tenant in the sense of organizational structure, but everyone shares the same connective fabric. "Nobody offers that feature, but nobody even thinks that way. Normally competitive groups would never want to share their work product" (01:09:50).

[technology="Collaboration Management Tools"]

🏷️ Naming Discussion

The naming conversation continued without resolution. Current candidates include HolosHolon OS, and Holomovement App as fallback. Mariko raised concern that "Holos" reads as "holo S" rather than the intended Greek word for "whole." James suggested the name will become clearer once the platform is in active use: "I feel like a name will be easier to align around once we can see it in action and feel it" (01:14:25).

The team will continue brainstorming async and consult the core team before finalizing.

Action Items

Michael Shaun Conaway

  • Walk Laura through Wise nonprofit bank account setup tomorrow, with Revolut as backup option (01:02:50)
  • Set up interim Stripe account through Imaginal as fallback if Engine for Good banking isn't ready in time (01:07:15)
  • Continue async naming brainstorm and bring options to core team (01:13:15)
  • Pull copy from this discussion for the donation page articulating the micro-grant funding model (19:17)

James Redenbaugh

  • Redesign donation page: single slider $1–$1000, monthly/annual/one-time toggle, $12/year minimum (17:30)
  • Implement parallel profile creation during Stripe checkout to eliminate wait time (04:54)
  • Restructure sign-up flow: minimum entry first, deferred profile depth questions (10:24)
  • Add support email + WhatsApp links to app feedback area (39:06)
  • Add direct chat-access button on Holon pages (51:10)
  • Cap directory map display at top 50 once member count grows (48:28)
  • Move app to app.holomovement.net once GoDaddy access available (57:31)
  • Send demo of Layer 2 agentic matching response to team (43:30)
  • Add notification indicators for Holon invitations and updates (56:01)

Mariko Pitts

  • Follow up with Laura immediately on Wise bank account urgency (01:08:18)
  • Coordinate communication strategy for inviting near community and wave registrants (01:00:30)

Hera Rose

  • Update onboarding email with corrected profile creation links (13:48)
  • Organize the testing party logistics — proposed Wed/Thu this week with ~12 participants (53:59)
  • Draft floating checklist UI concept for post-signup engagement (07:00)
  • Send follow-up to core team with focused testing areas based on this week's updates (52:00)
Relevant Initiatives
No items found.
Transcript