Strategy Meeting
Artifact info
Title:

Iris Operations & Strategy Alignment with Ashle

Engagement:

Iris Website Redesign

Client:

Iris Cocreative

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

🎯 Setting the Foundation for Collaboration

This session between James Redenbaugh and Ashle Bailey-Gilreath focused on establishing the operational scaffolding for their working relationship — covering communication channels, tool access, pricing strategy, project management systems, and the broader vision for how Iris Cocreative [tag="iris"] sustains itself while pursuing meaningful work. The conversation moved fluidly between tactical setup decisions and deeper strategic questions about Iris's business model and James's capacity.

📧 Communication & Access Setup

Email, Slack, and the Iris Ecosystem

James decided to set Ashle up with an Iris Gmail address [tag="gmail"] so she could operate from within the Iris ecosystem rather than as an external collaborator (17:47). After thinking through the trade-offs, James leaned back into Slack as the primary internal communication channel, recognizing its advantages for automation — including potential notifications for meeting summaries, proposal opens, new leads, and inter-team coordination with Munia and Sean (20:12). Most client communication will continue on WhatsApp or email.

Tool Access

Google Drive access will come automatically through the new Gmail account. James will share his Airtable [tag="airtable"] login directly (since adding paid users isn't worth the cost) and will eventually grant Bonsai access for invoicing support. ClickUp access was also flagged for setup.

💰 Pricing Strategy & Revenue Modeling

From Monthly Retainers to Project-Based Thinking

James walked Ashle through last year's Rhythm/Prism/Flow retainer model — a system built on doubling scales of engagement frequency rather than hours (29:30). While that model was set aside in favor of project-based work, Ashle reframed it as potentially valuable for post-launch continued support, where the main deliverable is complete but clients still want ongoing care and iteration. This reframe resonated strongly with James.

Building Sustainable Continued Support

Hollow Movement emerged as the ideal test case: a large app build that will require ongoing maintenance, iteration, and eventual handoff to team members like Sean as primary point of contact (40:36). The structure Ashle proposed:

  • Taper support pricing over time (e.g., 3 months at $4K, then $1K/month maintenance)
  • Build the "tail" of support into projects from the beginning
  • Free James's time for new project onboarding while preserving client relationships
Pricing Calibration & Hidden Costs

Ashle raised concern that James may be undervaluing his work, particularly in the $5–8K website tier (01:05:39). The plan is to track real project cost data over the next month — including hidden time costs like email, Claude [tag="claude"] iteration, and team coordination — to calibrate accurate pricing. James floated a vision of a near-fully-automated lower-tier offer where Claude generates initial sites from branding questionnaires and meeting transcripts, with Munia and Sean adding custom design and Webflow [tag="webflow"] builds.

Ashle emphasized that any automation investment requires accounting for the upfront build time, which can be subsidized by properly-valued larger projects. The goal: a model where 70% of projects are priced sustainably, leaving 30% capacity for passion projects, sliding-scale work, or in-kind contributions.

[technology="Communication Automations"]

🌊 Hollow Movement as Strategic Anchor

James shared that Hollow Movement represents the kind of work he wants to do more of — emblematic of a broader ecosystem of interoperable technologies (44:55). The app integrates the 12 technologies James identified last year as his focus areas, and the codebase is being organized with replication in mind. A similar directory system is being designed for Gaia Warriors, and upgrades will flow between projects.

[technology="Directory Systems"]

James envisions a future where he potentially takes on fewer outside projects to dedicate more time to evolving the Hollow Movement platform, with the possibility of cross-platform connections exposing users across communities. He'll be speaking on the main stage at this year's wave about the app.

The app will be in a good enough state for beta launch by end of week, allowing James to step away during his upcoming travel (27th onwards).

🗄️ Project Management & Operational Vision

Current State: James's Personal Workflow Tool

James demoed his custom "James Today" prototype — a workflow tool combining day/week views, time tracking, project urgency sorting, daylight visualization for team time zones, and even Vedic astrology context (01:41:12). Key qualities he values:

  • Unified day + week view
  • Quantitative and qualitative time awareness (pie chart of remaining day)
  • Drag-and-drop task scheduling that auto-updates status
  • Data capture that can feed into Claude [tag="claude"] for retrospective analysis

He's intentionally prototyping it on himself before scaling to the team — recognizing that if he doesn't use a tool, no one else will.

[technology="Collaboration Management Tools"]

Vision: An Iris Internal Dashboard

Beyond project management, James articulated a longer-term vision for an Iris dashboard that represents engagements as an organism — showing not just task lists but the energetic and temporal space each project holds, even when active hours are low (01:53:30). This would enable:

  • Forecasting of project timing and team availability
  • Better retrospective analysis
  • Team visibility into all active engagements

[technology="Time-Aware Toolsets"]

Offers and Requests

A key conceptual shift: James wants Iris to move from a request-only model (clients ask, team responds) to one that also surfaces offers — both from Iris to clients (proactively identifying needs) and from team members to projects (following their bliss, proposing involvement, suggesting features) (01:55:37). Munia in particular is hardest to coordinate with due to time zones but easiest in terms of trust and creative autonomy.

🚨 Capacity, Sustainability & The Bigger Question

James was candid about the pressure point: with family planning underway and his wife Emily having scaled back from a $150K virtual assistant role, James recognizes he needs to be making significantly more than he currently is — ideally $250K+ given the value Iris delivers (01:28:10). He's weighing scaling Iris up versus pursuing a salaried role elsewhere.

Ashle offered a reframe: this isn't about becoming a profit-driven capitalist venture, but about sustainability — enough to support James's family, keep the studio running, and preserve intentional space for projects that don't pay well but matter. She floated the nonprofit model as a possible long-term structural fit given Iris's values, while noting it doesn't need to be decided now.

Last Year's Investments

James reflected on last year's investments that didn't pay off as hoped — particularly an agency in Kosovo whose quality dropped after engagement scaled up, and a consultant whose final deliverable was a "50-page mostly AI-generated document" disconnected from studio operations (01:21:11). These were costly lessons, but James feels this year is on more solid ground and that Ashle's involvement represents the right kind of investment now.

⏱️ Working Rhythms & Focus

James shared he's experimenting with the "three things" technique — limiting daily commitments to three priorities to combat overwhelm from longer lists (01:36:31). He works more than 8 hours most days, often late at night, with efficiency varying widely. The goal is to track time more rigorously to understand actual productivity patterns.

Action Items

Ashle Bailey-Gilreath

  • Observe and take notes on Iris systems, continue asking strategic questions, and co-sketch the evolving project management vision with James (01:52:05)
  • Draft a contractor agreement template, using herself as the test case (01:50:47)
  • Review the existing client agreement template (currently in InDesign) and propose a more editable, standardized format (01:51:36)
  • Support invoicing and client subscription follow-ups, copied on James's communications initially (52:38)
  • Coordinate with Munia on project management workflows and Figma access issues (01:15:40)
  • Add a "proposal links" column to the project tracking spreadsheet (01:59:35)
  • Begin developing real cost/pricing data for 1–2 representative project types over the next month (01:13:00)

James Redenbaugh

  • Set up Ashle's Iris Gmail account and add her to Slack within the Iris workspace (17:47)
  • Share Airtable login and grant Google Drive access via the new Gmail (24:16)
  • Share the InDesign client agreement template with Ashle for review (01:51:07)
  • Update the project tracking spreadsheet with proposal links, total budgets, and progress estimates per project (01:59:22)
  • Advance Hollow Movement app to stable beta state by end of week (57:44)
  • Continue prototyping personal workflow tool with eye toward eventual team adoption (01:39:00)
  • Apply the "three things" daily focus method during the high-intensity pre-travel period (01:36:31)
  • Share studio context generously with Ashle as it arises (01:58:37)

Both

  • Meet again next Wednesday at the same time to continue alignment before James's travel (01:48:55)
Relevant Initiatives

Operations & Financial Structure

Priority: 
Very High
Size: 
L
Planning Stage

Contract & Scope Templates

Priority: 
Very High
Size: 
S
Creation Stage

Client Support & Team Delegation

Priority: 
High
Size: 
M
Planning Stage

Iris Portal

Priority: 
Very High
Size: 
XXL
Planning Stage

Modular Platform Ecosystem

Priority: 
High
Size: 
XXL
Planning Stage

Continued Support Model Development

Priority: 
Very High
Size: 
M
Planning Stage

AI-Assisted Website Generation

Priority: 
Medium
Size: 
L
Idea Stage

Team Communication Infrastructure

Priority: 
High
Size: 
S
Coordinating

Project Tracking & Analytics

Priority: 
High
Size: 
M
Planning Stage
Transcript