Strategy Meeting
Artifact info
Title:

Strategic Partnership & Operational Alignment with Ashle

Engagement:

Iris Website Redesign

Client:

Iris Cocreative

Meeting Date:
April 30, 2026
Next Meeting Date:
May 12, 2026
Hide This
April 22, 2026
Hide This
People
Ashle Gilreath
James Redenbaugh
Artifact Image
Meeting Summary

🎯 Meeting Context

James and Ashle met to walk through Ashle's notes on the operational strategy document and define what a strategic partnership between her and IRIS Cocreative [tag="iris"] could look like. The conversation flowed between platform updates, business structure, creative philosophy, and concrete next steps for a trial engagement.

🌊 Hollow Movement Platform Update

James opened with progress on the Hollow Movement platform, which is being prepared for activation day at the upcoming wave (01:30). Core features — sign-up, profiles, assessments, and matching — are nearly online, and the platform currently lives at a temporary domain without an official name.

[technology="Custom Membership System"]

Ashle proposed turning the naming process into a collaborative activation moment (04:14), letting early users contribute name ideas during the launch session. This would relieve pressure from the core team, deepen community ownership, and stay on-brand for Hollow Movement's participatory ethos. The team has been jokingly calling it "Jeff" (or the European spelling, "Goeff") in the meantime.

[technology="Assessment Systems"]

📊 Business Structure & Financial Visibility

Ashle's first orienting questions were practical: how is IRIS Cocreative formed, and what accounting system is in use? (07:14). James confirmed IRIS operates as a sole-proprietor LLC and uses Bonsai to manage clients, expenses, and project-level profit/loss, with a spreadsheet backup for the past year.

Ashle emphasized the value of treating IRIS as its own ecosystem for budgeting and resourcing purposes, even within the sole-proprietor structure. While historical projection is difficult given how rapidly the team, processes, and AI tooling are evolving, James shared that the studio has already exceeded last year's full-year profit, largely thanks to last year's investments in tooling and team refinement (12:00).

🤝 Client Support & Team Involvement

A recurring theme was how to bring more team members into client work without exponentiating costs (20:45). Several clients — including Hermit of Hermitage World and Tess (Gaia Warriors) — are moving slowly through onboarding tasks like brand questionnaires and Airtable [tag="airtable"] population because the work feels technical or overwhelming.

[technology="Directory Systems"]

Ashle proposed engaging team members like Lauren as a lower-cost technical/admin support presence for working sessions. This approach would:

  • Free James from being the sole point person
  • Help clients feel supported by a team rather than an individual
  • Introduce more perspectives into client relationships
  • Keep portfolio hygiene and onboarding tasks moving

James affirmed the desire for more collaborative and cross-project check-ins internally, while honoring that team members like Munia (Bali) prefer asynchronous involvement and stay connected through shared meeting recordings.

[technology="Collaboration Management Tools"]

🎨 Shared Creative Foundations

A long stretch of the conversation revealed deep alignment in backgrounds (25:11). Ashle shared her path through fine arts, an art space in Memphis, two master's degrees (including cognition and culture), research at the University of Oxford, work alongside David Sloan Wilson, and a recently completed PhD on collaborative photography practices with victims and survivors groups in Northern Ireland.

James shared his own arc through architecture and sculpture, Being Design in Philadelphia, Montaya (the messier, more sprawling predecessor to IRIS), and the four-year evolution of IRIS Cocreative [tag="iris"] alongside the WordPress-to-Webflow [tag="webflow"] transition. He also shared that his wife is moving into art therapy, and Ashle offered to connect him with Amand, a former intern doing ecological activism through improvisational drama.

The "Bad Cop" Offer

Ashle named a useful pattern from her work with Jeff: she's comfortable playing the "bad cop" role on overdue invoices and accountability nudges so James can preserve warm client relationships (35:30).

🏛️ Pattern Language & Action Process

James introduced two frameworks shaping his thinking:

Digital Pattern Language

Inspired by Christopher Alexander's architectural pattern language, James is articulating a digital pattern language that maps generative and anti-patterns across scales — ecosystem, platform, product, space, component, interaction, micro-moment (45:00). Anti-patterns include endless scrolls, manipulative urgency, and what Alexander called "deadness." James wants this to live as a collaborative library, not a solo project.

Action Process

Drawing from Fernando Flores's action language (which is also how James's parents met), James described a fractal action process that runs from idea → exploration → commitment → execution → completion → integration (50:10). He emphasized that successful projects move cleanly through portals of completion and coordination, while unsuccessful ones lose sight of the whole and either over-complete or never fully define done.

Ashle affirmed these frameworks are foundational and should be interwoven into IRIS's internal operations and client engagements, not treated as side rabbit holes.

🛠️ Project Management Tool Decision

Ashle pushed back gently on framing the PM tool [tag="airtable"] as a binary "keep or kill" decision (58:30). Her recommendation:

  • Don't abandon it — significant work and data already live there
  • Don't pour more resources into it right now either
  • Park it for ~6 months while focusing on low-hanging fruit
  • Look for a simpler plateau the team can actually use day-to-day

James demonstrated a personal task app he built for himself in a day, noting that what the team and clients need is likely simpler than the current Airtable build but could be reached with relatively low effort given existing data structures. Engagements, clients, meeting artifacts, initiatives, and tasks are all already tracked.

[technology="CRM System Templates"]

📄 Contracts & Operational Gaps

Ashle identified two immediate gaps:

  • Inconsistent client contracts — IRIS has a strong contract template but doesn't always deploy it
  • No subcontractor contracts currently in place

She offered to own contract drafting and scope-of-work creation, with James reviewing on a light-touch approval cycle.

🤝 Trial Engagement Terms

The two aligned on a part-time contractor trial:

  • 10 hours/week for the next few months (potentially scaling to 20 later)
  • $70–$75/hour, reflecting strategic partnership and stewardship work
  • Month-long trial with concrete, actionable deliverables
  • Built-in time for Ashle to excavate and onboard through targeted questions
  • Re-evaluate fit and scope at the end of the trial period

Ashle is also navigating a move and her husband finishing his PhD, so the 10-hour cap holds firm in the near term.

Action Items

Ashle Bailey-Gilreath

  • Draft contract, scope of work, and articulated role description based on the discussed domains of value (1:09:50)
  • Frame up roles & responsibilities document for James's review (1:09:30)
  • Begin onboarding excavation — targeted questions to James to deepen understanding of IRIS operations (1:08:30)
  • Explore engaging Lauren (or similar team member) for client-facing technical/admin support sessions and portfolio hygiene (58:30)
  • Be available to play "bad cop" on overdue invoices and client accountability when needed (35:30)

James Redenbaugh

  • Share Obsidian folder on digital pattern language with Ashle (48:50)
  • Share action process documentation with Ashle (50:10)
  • Send Amand's profile to Ashle for his wife's art therapy/drama interests (33:50)
  • Follow up with Hermit of Hermitage World on stalled onboarding (16:50)
  • Answer outstanding questions in Ashle's strategy document asynchronously (15:50)
  • Review draft contract and scope of work from Ashle and provide timely feedback (1:10:30)
  • Consider parking the current PM tool [tag="airtable"] development for ~6 months and identifying a simpler near-term plateau (1:00:00)
Relevant Initiatives

Operations & Financial Structure

Priority: 
Very High
Size: 
L
Planning Stage

Iris Portal

Priority: 
Very High
Size: 
XXL
Planning Stage

Modular Platform Ecosystem

Priority: 
High
Size: 
XXL
Planning Stage

Digital Pattern Language

Priority: 
Medium
Size: 
L
Planning Stage

Action Process Framework

Priority: 
Medium
Size: 
M
Planning Stage

Contract & Scope Templates

Priority: 
Very High
Size: 
S
Creation Stage

Client Support & Team Delegation

Priority: 
High
Size: 
M
Planning Stage
Transcript