How to Use This Document
This document outlines your community strategy and the plan to bring it to life.
It is organized into two sections:
- •Strategy Overview – This section explains how your community is designed to function, including its purpose, structure, and the principles that drive engagement
- •Execution – This section outlines exactly what to do, in what order, to build, activate, and maintain the community
Start with the Strategy Overview to understand the thinking behind the system. Then move into the Execution section to begin implementing it step by step.
As you work through execution, refer back to the Strategy Overview for clarity and direction. This document is designed to be used continuously, not just as a one-time plan.
Strategy Overview
This Is the Community's Purpose in Your Value Ladder
The community lives at the center of your entire ecosystem.
At the entry level, the community and coursework are the product together. They are designed to work side by side, giving members both the structure to learn and the space to apply that learning in real time.
As members move into higher-level offers like the cohort and inner circle, they continue to operate inside the same community. These offers add depth through structured experiences, but the community remains the shared environment where members ask questions, apply what they're learning, and learn from each other.
The goal of the community is not for members to rely on Brian for answers. It is designed for members to engage directly with each other, bringing real challenges, sharing experiences, and learning through conversation, all under the umbrella of his thought leadership.
This means the community is not a separate add-on at any stage, nor is it dependent on Brian being present to guide every interaction. It is a self-sustaining environment where members are expected to engage with each other, think critically, and work through challenges together, using Brian's frameworks without relying on his constant input or hand-holding.
The Community's Core Objective
Integrator Arena: Where prospective and developing integrators ask real questions, share real experiences, and challenge one another's thinking so that they can sharpen their judgment, apply the work with confidence, and grow into the seat without doing it alone.
What Success Looks Like
If this community is working, members are consistently:
- ✓Asking real, specific questions about challenges they're facing
- ✓Sharing how they are applying W3 concepts in real situations
- ✓Responding to and challenging each other's thinking
- ✓Sharing wins and lessons learned from real-world experience
- ✓Engaging in discussions sparked by W3 content, both from within their membership (coursework, cohort, inner circle) and from publicly available sources (podcasts, webinars, events)
What This Community Is Not For
This community is not:
- ✗A place to rely on Brian for answers or direct support
- ✗A shortcut around the coursework or structured learning by asking others to fill in gaps without doing the work first
- ✗An outlet for unproductive venting or complaints without a willingness to work toward solutions
- ✗A place to ignore or miss out on. It's where the real growth happens
Conversation Types & Why They Exist
Within this community, conversations fall into a few core categories:
How Engagement Is Prompted
Engagement is guided by prompting the right conversations at the right time.
Prompts are based on:
- •Content (coursework, cohort, podcasts, events)
- •Member activity
- •Member journey stage
- •Operational touchpoints
Member Context
Engagement is personalized based on:
Where they are in the program
→ Determines what and when to prompt
Their identity (Aspiring, Fractional, Full-Time)
→ Determines how to prompt
Roles & Responsibilities
Additional Strategy Details
Community Engagement Prompt Opportunities to Leverage
Chronological
Public Keynotes
Topics such as "EOS Life Workshop" and "Land a Consulting Client Now," often featuring guest speakers.
Prompt before events: "Hey! We're super excited to have Amy coming onto our EOS Life Workshop in a couple weeks. We'll be discussing ABC, what are your biggest burning questions for her? We want to know so you get the most out of it. Start it like this: 'When Amy presents, I would love to learn about ____'"
Prompt during/after events: "Did you all hear Amy talk about how important it is to document your ABCs? This is so key, so we want to make sure you're absorbing her expertise here. I want all members to post a picture of how you document your ABCs before EOD tomorrow!" And then schedule a follow-up email, too.
W3 Content
Both public and membership-based, such as podcasts, new course content feedback, upcoming content ideas such as reflections/lessons (like Ricky's San Diego memories) or meeting highlights/lessons for all.
Calendar Events
W3 anniversaries, holidays (especially military-related holidays), and times of year relevant to EOS/W3 industry like annual or quarterly meetings.
Personal
- •Course progress
- •Career arc updates
- •Buddy system or temporary groups in the future
- •Wins / struggles / questions
- •Personal shares
Operations
- •Planned customer service check-ins
- •Incoming customer service
- •Private/manual prompts to standouts — lulls, demonstrations
- •Private/manual prompts to regular members — back-end good/bad stats, CM knows their data and happenings best, so privately ask for a public post
- •Program feedback
- •Testimonials
- •Introduction to group and to each other
Opportunities to Acquire and Update Member Data
Course & Community Progress & Engagement
Onboarding
- •Aspiring, Fractional, or Full-Time
- •# of years using EOS
- •# of businesses you've been a part of
If aspiring, tell us the short story of how you got inspired to make change in your life. Aspiring = you wanted to do something big with your life, you're in the right place, we're here for you. Conversations about this is not easy work but it is incredibly rewarding.
- •Veterans get a discount code, 3 months free, brave career changers
- •Add to onboarding emails: "Since you are a [aspiring, fractional, full-time] here's how you can get value."
Customer Service Check-ins
Every 6 months:
- •Are you still [fractional…]?
- •Would you like to change that? If so, tell us more.
- •What's your favorite part & why?
- •What's your least favorite part & why?
Every other 6-month email: add NPS questions — not required to fill out, just nice to have.
Other
Webinars, reports, workshops — always ask:
- •Are you Aspiring, Fractional, or Full-Time?
- •Are you a veteran?
Execution
Phase 1: Set the Foundation
Build and configure the community and systems based on the agreed-upon strategy
Timeline: 3–4 weeks
Review and Refine Community Setup
- •Jade records a video reviewing the current UI/UX (User Interface: what it looks like; User Experience: what the experience feels like in practice), including tech setup notes and recommendations
- •Brian reviews and agrees/disagrees with Jade's suggestions, as well as adding his own suggestions for needed updates
- •Jade implements UI/UX updates after review
Set Up Beta Tester Offers
Create 2 checkout options for the beta testers:
- •Lifetime (1 year upfront)
- •Half-off for life
Build Workflows and Campaigns
Jade creates Workflow wireframes and Campaign templates:
- •Onboarding
- •Course progress
- •Customer service check-ins
- •Events and content
- •Holiday/industry messaging
Note: Include notes for prompts to include with copy
W3 team fills in the copy
Align Marketing with Community Strategy
- •Guide marketing team on positioning and messaging to ensure expectations and value are clearly communicated
- •Jade updates website and funnels
Phase 2: Activate the Community
Introduce the community and begin shaping behavior
Prepare the W3 Team
- •Provide SOPs, task lists, and calendars
- •Focus on relationship building and systems
Prepare Beta Testers
- •Set expectations for engagement and participation
- •Prepare them to act as covert yet foundational contributors
Open to the Public and Begin Selling
- •Begin marketing and sales
- •Manager and beta testers to help reinforce expectations as new members join
Phase 3: Maintain the Rhythm
Sustain engagement through consistent execution, defined roles, and systems
Maintain Prompting
Based on real-time content, activity, and member journey — both automated and manually
Facilitate Conversations
Encourage peer interaction and deeper discussion
Maintain Relationships and Data
Track engagement, progress, and identity
Execute Campaigns and Check-Ins
Run workflows and communication
Reinforce Standards
Highlight strong engagement and maintain quality
Phase 4: Measure and Improve
Evaluate and optimize through consistent execution of defined roles and systems
Track Performance and Insights
Manager and Moderator track activity, KPIs, sentiment, and effectiveness
Review and Optimize Quarterly
- •Meet quarterly using provided agenda
- •Adjust and improve based on results
Proposal
Here is the proposal for Jade Olivia's implementation support as outlined above.
Phase 1 Implementation
Set the Foundation — full setup and configuration
Ongoing Consulting
Available upon request