Strategy Meeting
Artifact info
Title:

ILALI Tech Stack Strategy and Website Coordination Kickoff

Engagement:

New Landwell + ILALI Website

Client:

Innovative Learning and Living Institute

Meeting Date:
May 5, 2026
Next Meeting Date:
February 3, 2026
Hide This
People
James Redenbaugh
Gabi Jubran
Amanda Nagai
Artifact Image
Meeting Summary

Opening Context

Gabi shared reflections from the Buckeye Ancestral Skills Gathering near Chico, where ILALI is collaborating closely with one of the event's co-founders to absorb the cultural and educational exchange spirit into their work. James caught the team up on his current build work and his collaboration with the Revillage Earth team — having created the brand for Grayton Station Coffee and now developing the Re Village website (02:24).

🗄️ Tech Stack Strategy: Airtable, Supabase, and Tool Consolidation

Settling on Airtable as the CRM Foundation

The team has been exploring Airtable [tag="airtable"] as their CRM and wanted a fuller picture of what's possible — particularly whether project management could live there alongside contacts, forms, and an eventual member directory (04:23). Amanda emphasized the goal of using as few tools as possible, given they're currently working in Todoist and Twist for project management and trying to build adoption momentum across the team.

James's Recommendation on Project Management

James advised against using Airtable as a primary project management tool — calling it "one step up from Google Sheets" for that purpose and a bit hacky compared to Todoist or ClickUp (07:23). The advantage only emerges if you want database management and project management living in the same place. He recommended researching how Airtable PM has evolved in 2026 before fully ruling it out, since the landscape changes quickly.

Replacing Google Forms with Airtable Forms

A clear, immediate recommendation: stop using Google Forms and switch to Airtable forms, since they're functionally similar but data flows directly into a manageable Airtable base (13:06). Google Drive and Docs should remain for documents and shared files, but Airtable is well-suited for resource libraries — PDFs and files can live inside records rather than scattered across folders.

[technology="Directory Systems"]

Supabase as the Future Horizon

James introduced Supabase [tag="supabase"] as his preferred tool for more complex builds, walking through a sophisticated app his team is developing — featuring user profiles, AI-generated banner images and summaries via Claude [tag="claude"], a values-based matching system, an integrated assessment tool, messaging, group chats (Holons), an interactive global map using Mapbox-style functionality, project management, and Stripe-powered [tag="stripe"] participatory contribution tracking (16:46). The front end runs on Webflow [tag="webflow"] with custom code hosted on GitHub [tag="github"].

[technology="Custom Membership System"]

[technology="Intelligent Matching Algorithms"]

[technology="Assessment Systems"]

Key takeaway: ILALI doesn't need Supabase yet. Airtable can be synced to Supabase later if more complex functionality becomes necessary, and Airtable data can always be exported — there's no lock-in (11:45). Supabase is also remarkably affordable (~$9/month for the bases James uses).

Decision

The team agreed to stay with Airtable for now, fully adopt it for forms and CRM, and reassess once it's being used more deeply (25:05). Supabase remains a known option for the future.

🤖 AI, Automation, and Research Augmentation

James demonstrated how Airtable paired with Claude [tag="claude"] becomes a powerful research engine — sharing a directory he built of conscious artists and musicians worldwide where Claude found ~95% of the entries, generated descriptions, and applied tags. Through MCP (Model Context Protocol) connections, Claude can now interact directly with Airtable to populate research, find similar leads, or organize information at scale (28:35).

He also showed an n8n [tag="n8n"] automation that pulls his Fireflies transcripts, analyzes them, extracts action items, generates custom-styled meeting summaries, and creates illustrative imagery — all triggered by a single button (35:03). The summaries use embedded technology references and project context so each output reflects the specific client and engagement.

[technology="Communication Automations"]

For ILALI specifically, this opens up a path to:

  • Automate transcript processing from Fathom into Google Docs or Todoist
  • Auto-update task statuses based on what's discussed in calls
  • Send post-meeting summary emails to the team

💭 Theory of Action and Status Design

James shared his team's action process as a philosophical layer worth building into any system: Idea → Planning → Coordination → Creation → Completion → Reflection (46:30). The "coordination" stage acts as a gate — once a date is set or a commitment made, the work crosses from idea-territory into committed action. Importantly, there are two completion states: when something is technically done, and when it's integrated (published, communicated, signed off). Reiko's recent task illustrated this — done in reality, but not marked done, so not really done.

He encouraged ILALI to consciously articulate their own theory of change, coordination, and commitment so the project management system reinforces those values structurally rather than just verbally.

[technology="Collaboration Management Tools"]

🔄 Workflow Challenges and Commonwheel Integration

Amanda named the ongoing challenge of integrating with — or appropriately circumventing — Commonwheel's systems (Salesforce and others) without losing critical data, especially around donors, funding, and expenses (33:30). The team is still finding the right boundary between what needs to flow through Commonwheel versus what ILALI can manage independently.

🏗️ Website Project: Moving Into Coordination

Both teams aligned that the main website is ready to move from planning into active coordination (48:45). Gabi noted that Reiko has been holding space for emerging clarity, and that more pieces are now coming into coherence.

James's Capacity and Timing
  • New project manager and new designer/developer just hired and ready for work
  • James is heads-down on a Portugal app launch at the end of May, then on vacation
  • Travel dates: Departing May 27, returning June 12
  • Target: ILALI delivers updated wireframes and additions to James by the week of May 18 so he can hand off to the team before traveling
Digital Pattern Language

James shared that recent work with Revillage has him applying Christopher Alexander's pattern language work to digital design — developing a framework for "living websites" focused on equity, harmony, generativity, honesty, beauty, and effectiveness while avoiding manipulative anti-patterns (50:30). He'll share an early version of the site explaining this philosophy, as he wants the framework to be developed collaboratively. The orientation feels especially aligned with ILALI's mission.

[technology="Parametric Geometric Interfaces"]

Action Items

Gabi Jubran

  • Connect with Reiko after this call to align on website timeline and next steps (48:45)
  • Coordinate the team to deliver updated wireframes and new additions to James by the week of May 18 (55:20)
  • Begin transitioning Google Forms workflows over to Airtable forms [tag="airtable"]

Amanda Nagai

  • Continue building team adoption of Todoist and Twist for project tracking
  • Evaluate, with Gabi, the potential to automate meeting documentation using n8n [tag="n8n"] and AI tools

James Redenbaugh

  • Share the early version of the digital pattern language website for collaborative input (51:20)
  • Onboard new project manager and developer, preparing them to support the ILALI website build
  • Be ready to receive wireframes by the week of May 18 before departure on May 27
  • Optionally advise on transcript-to-Todoist automation if ILALI wants to pursue it

All

  • Reflect on ILALI's theory of change, coordination, and commitment so it can be structurally embedded into the eventual project management system (46:30)
Relevant Initiatives

Website Redesign

Priority: 
Very High
Size: 
L
Coordinating

Ecosystem Directory & CRM

Priority: 
High
Size: 
M
Planning Stage

Meeting Automation & Documentation

Priority: 
Medium
Size: 
S
Planning Stage
Transcript