BNI Charlotte Metro Growth Platform — Business Plan

Version: 2.1
Date: February 14, 2026
Authors: [Your Name] & Bryan
Chapter: BNI Westlake Select (Denver, NC)
Supersedes: bni-westlake-select-growth-plan.md (WordPress-based, single-chapter plan)
Companion documents: bni-professional-classifications-full-list.md, bni-classifications-simple-list.txt, bni-chapter-visit-schedule.md, bni-chapter-visits-charlotte-metro.ics

Table of Contents

1. Executive Summary
2. Problem Statement
3. Solution Overview
4. Target Market
5. Value Proposition
6. Product & Feature Set
7. Revenue Model
8. Go-to-Market Strategy
9. Operational Plan
10. Technology Stack
11. Key Metrics & KPIs
12. Risk Assessment
13. Phased Roadmap
14. Financial Projections
15. Exit & Scale Strategy
16. Appendix A — Seat Splitting Model
17. Appendix B — Go High Level Integration Architecture
18. Appendix C — Charlotte Metro BNI Chapter Landscape
19. Appendix D — Member Recruitment Playbook
20. Appendix E — Chapter Operations & Communication Workflows
21. Appendix F — Key Patterns & Habits for Members
22. Appendix G — Research-Based Best Practices for Chapter Growth
23. Appendix H — BNI Seat Classifications Reference

1. Executive Summary

The BNI Charlotte Metro Growth Platform is a web application designed to accelerate the growth of BNI chapters across the Charlotte metropolitan area by solving three core problems that BNI’s existing infrastructure does not address:

1. Cross-chapter collaboration — Members in the same professional category across different chapters have no infrastructure to share best practices, coordinate seasonal campaigns, or support each other’s growth.
2. Visitor engagement beyond the meeting — Visitors who attend a chapter meeting and don’t join immediately fall out of the funnel with no automated follow-up system.
3. Chapter growth tooling — Individual chapters lack modern tools for tracking open seats, managing recruitment pipelines, and amplifying member visibility through coordinated social media engagement.

The platform will be built on a modern, scalable technology stack (Elixir/Phoenix/Ash Framework with PostgreSQL), prove its value with Westlake Select as the founding chapter, then expand to a second chapter (likely Waxhaw), and subsequently roll out across the Charlotte metro area’s 29+ chapters.

Bryan brings Go High Level CRM expertise for email/SMS marketing automation. The platform will integrate with Go High Level via API/webhooks to handle visitor drip campaigns, meeting reminders, and cross-chapter event marketing.

Long-term vision: Package the platform as a deployable product for other BNI regions (Raleigh, Greensboro, Upstate SC) and potentially offer to BNI corporate.

2. Problem Statement

2.1 BNI Is Stuck in the Past

BNI’s organizational structure and technology are essentially the same as they were 20–30 years ago. BNI Connect provides basic member directories, PALMS reporting, and classification tracking, but it does not provide:

• Cross-chapter collaboration tools
• Visitor CRM or automated follow-up
• Social media coordination infrastructure
• Per-seat peer forums or best-practice sharing
• Modern chapter marketing websites with real-time seat availability

2.2 Chapters Operate in Silos

Each chapter in the Charlotte metro area operates independently. There is no mechanism for:

• A Medicare specialist in one chapter to share enrollment strategies with Medicare specialists in other chapters
• A chapter trying to recruit a roofer to connect prospective roofers with an existing BNI roofer for peer conversation
• Coordinated marketing pushes that benefit all participating chapters (e.g., “BNI Charlotte Lunch & Learn” events that draw from a shared pool of prospects)

2.3 Visitor Drop-Off

When a visitor attends a BNI meeting and doesn’t join immediately, the follow-up is typically manual and inconsistent. There is no system to:

• Automatically send weekly chapter highlights to past visitors
• Create FOMO by sharing TYFCB numbers, referrals passed, and high-fives
• Notify visitors when a seat they expressed interest in is about to be claimed
• Invite past visitors to cross-chapter events, lunch & learns, or social gatherings

2.4 Social Media Amplification Gap

When a BNI member posts on social media or a community member asks for a recommendation on Facebook, there is no coordinated response system. Individual members may or may not see the post in time. The WhatsApp screenshot workflow is a start, but it’s manual and doesn’t scale.

3. Solution Overview

A web application that serves as the growth operating system for BNI chapters in the Charlotte metro area.

Core Modules

Integration Layer

4. Target Market

Primary: BNI Chapters in Charlotte Metro Area

• 29 identified chapters across Lake Norman, Concord/Cabarrus, Charlotte proper, Belmont/Gastonia, Fort Mill/Rock Hill SC, and Hickory/Foothills
• Gap areas with no chapters: Kannapolis, Salisbury, Statesville, Waxhaw/Indian Trail/Matthews, Monroe — representing chapter formation opportunities
• Estimated total members: 500–800 across all chapters (average ~20–25 per chapter)

Secondary: BNI Regions in NC/SC

• Raleigh/Durham Triangle (BNI Triangle region)
• Greensboro/Winston-Salem
• Upstate South Carolina (Greenville, Spartanburg)
• Coastal NC

Tertiary: National BNI Market

• 10,000+ BNI chapters globally, ~2,500+ in the US
• If the Charlotte model proves out, the platform could be offered region-by-region or to BNI corporate

5. Value Proposition

For Individual Members

• Peer forums with others in the same profession across chapters — share what works, coordinate campaigns, get tactical advice from people who understand BNI + your industry
• Social media amplification — when you need a recommendation boost, your fellow BNI members across the metro area pile on
• Visibility — your profile appears in the cross-chapter directory, increasing referral opportunities from members in other chapters
• SEO benefits — dofollow backlinks to your website, LocalBusiness structured data, and content co-creation opportunities that directly improve your Google search visibility (§6.11)
• Referral incentive visibility — your referral incentive is displayed in the directory so other members know exactly what you offer to referred customers

For Chapters

• Digital visitor registration that replaces paper sign-in sheets — data flows directly to CRM with zero manual entry, sponsoring member tracked automatically
• Automated visitor follow-up that keeps prospects warm and creates urgency — SMS, email, and seat-scarcity triggers
• Modern website with real-time seat availability that helps visitors self-qualify and register
• Seat gap analysis that shows exactly which classifications to recruit for Power Team completion
• Recruitment accountability — members claim open seats with visible 60-day commitments
• Customizable membership requirements adopted from a shared library, with platform-tracked compliance
• Growth metrics beyond what BNI Connect provides

For the Charlotte Metro BNI Ecosystem

• Network effects — more chapters participating = more value per member
• Coordinated events — Metro-wide lunch & learns, content days, and education events that no single chapter could pull off alone
• Chapter formation pipeline — identify underserved geographies and build prospect lists for new chapters

For Us (Platform Operators)

• Recurring revenue from chapter subscriptions
• CRM/marketing services revenue from Go High Level campaigns
• Event revenue from metro-wide BNI education events and lunch & learns
• Exit potential — sell to BNI corporate or license regionally

5A. Competitive & Alternative Analysis

Before chapters invest time in adopting this platform, they’ll ask: “Why not just use what we already have?” This section answers that question.

BNI Connect (Official BNI Platform)

What it does well: - Official member directory (global, searchable) - Referral, TYFCB, and 1-on-1 tracking with electronic slips - PALMS reports and Chapter Traffic Light benchmarking - CEU tracking via BNI Business Builder - Visitor invitation emails - Mobile app for slip entry and directory lookup - Mentor/mentee pairing with automated 8-week email sequence - Classifications Not In Chapter report

What it does NOT do (our platform fills these gaps):

Positioning: The platform is complementary to BNI Connect, not a replacement. BNI Connect remains the system of record for official referral slips, TYFCB, PALMS reporting, and membership administration. Our platform adds the collaboration, automation, and community layers that BNI Connect does not provide. Members continue using BNI Connect for their official activity logging. They use our platform for everything else.

Generic Tools (Slack + Google Drive + Mailchimp + Spreadsheets)

Many chapters cobble together existing tools:

The fundamental problem with generic tools: They don’t talk to each other. Seat data in a spreadsheet can’t trigger a visitor follow-up email. Forum activity in Slack can’t feed an engagement score. A WhatsApp message can’t be tracked for reciprocity. File sharing in Google Drive can’t be gated by participation level. The platform integrates all of these into a single system where data flows between features.

Doing Nothing

The default for most chapters. Consequences:

• Visitors sign in on paper, leadership manually enters data (or doesn’t), no automated follow-up. Most visitors never hear from the chapter again after their visit.
• No cross-chapter collaboration. Each chapter operates as an island. A roofer in Westlake Select has no connection to a roofer in Waxhaw — they can’t share tactics, coordinate campaigns, or help each other recruit.
• No visibility into which seats are open across the metro. Recruitment is ad hoc and uncoordinated.
• No social media coordination. Members boost each other sporadically; no tracking, no reciprocity, no accountability.
• No engagement data beyond PALMS. Leadership can’t see who’s contributing to the broader ecosystem vs. just showing up to meetings.
• Members get zero SEO benefit from their BNI membership.
• Meeting the “40 members by 2027” goal requires sustained, coordinated effort that pen-and-paper processes cannot support.

The cost of doing nothing is not zero — it’s the difference between a 17-member chapter generating ~$600/member/week and a 40-member chapter generating ~$1,556/member/week. That’s roughly $50K in additional annual revenue per member left on the table.

6. Product & Feature Set

6.1 Chapter Hub (Public-Facing)

Each participating chapter gets its own subdirectory or subdomain on the platform. The chapter page includes:

• Seat Roster Grid — Visual display of all BNI classifications, color-coded: filled (green), open (white), claimed for recruitment (yellow with recruiter name and target date), applicant in process (blue), closed (grey), split seats shown as sub-rows
• Member Profiles — Photo, business name, BNI classification, brief bio, contact info, website URL, Alignable profile URL, “open to talking with prospective members” flag, testimonial snippets, video embeds, and an optional “Referral Incentive” free-text field where members describe what they offer to referred customers and/or the referring member (e.g., “10% off first service for BNI referrals; $25 gift card to referring member”). Referral incentives are visible in the cross-chapter directory and on the member’s public profile to help other members decide who to refer to. Members can self-submit and update their own profiles through authenticated LiveView forms (replaces the WordPress/Gravity Forms approach from the original plan).
• Visitor Registration — Form that feeds directly into Go High Level for automated follow-up. Captures: name, email, phone, business type, which seat they’d fill, how they heard about BNI
• Chapter Stats — TYFCB this year, total referrals passed last month, member count, years active
• Upcoming Events — Next meeting, upcoming Stack Days, social events, education moments

6.2 Seat Management System

This is the most complex domain model in the application. It must support:

• Official BNI Classifications — All ~290 classifications across 27 industries (seeded from the official BNI taxonomy, November 2020)
• Per-Chapter Seat Configuration — Each chapter independently decides which classifications to offer and how to split them
• Seat Splitting — A chapter can split “Insurance” into “Insurance — Property & Casualty” and “Insurance — Life & Disability.” Another chapter might not split it at all. A third might split it three ways. The system must be flexible enough to support arbitrary splits per chapter.
• Split Inheritance — When a seat is split, the sub-seats inherit the parent classification’s industry grouping and Power Team associations
• Seat Status Tracking — Each seat in each chapter has a status:
  • Open — no member, no one actively recruiting
  • Claimed for recruitment — a current member has committed to actively recruiting for this seat. The claim records: who claimed it, target date, and notes. If no progress after 60 days, the claim expires and the seat reverts to open. This creates visible accountability — the seat roster shows “Claimed by [Member Name], targeting [date]” so the whole chapter sees who’s working on what.
  • Applicant in process — a prospective member has applied or is in the visitor-to-member pipeline for this seat
  • Filled — linked to an active member
  • Closed — chapter decided not to offer this seat
• Recruitment Claiming Workflow — Any current member can claim an open seat they commit to recruiting for. Claims are visible on the chapter hub’s seat roster grid (yellow status). Multiple members can coordinate on the same seat (e.g., two people each working their network to find a CPA). The engagement scoring system (§6.7) awards points for active recruitment claims.
• Classification-Not-In-Chapter Report — Mirror BNI Connect’s report: show all classifications not currently filled in a given chapter, prioritized by Power Team fit

6.3 Cross-Chapter Member Directory

• Searchable by: Classification/seat, chapter, industry, “open to prospective member conversations” flag, geographic area
• Use case: Huntersville chapter is trying to recruit a therapist. They search the directory, find a therapist in Westlake Select flagged as “open to talking with prospective members.” They connect the prospect with that therapist for a peer conversation about the value of BNI.
• Privacy controls: Members opt in to the cross-chapter directory. They choose what contact info is visible.

6.4 Forums

The platform provides three types of forums: chapter forums, seat forums, and a metro-wide best practices forum. All support long-running topic threads with full search. WhatsApp remains the channel for real-time group messaging and Social Boost coordination (§6.6) — forums are for structured, persistent, searchable discussion.

6.4.1 Chapter Forums

• One forum per chapter. All members of that chapter are auto-subscribed.
• Threads are chapter-only by default. Only members of the chapter can see and participate.
• Moderator promotion to metro-wide visibility: Chapter forum moderators can promote any thread to metro-wide visibility. Once promoted, all platform members across all chapters can see and fully participate in that thread. This enables cross-chapter conversation when a chapter-local discussion turns out to be broadly useful.
• Use cases: Chapter-specific announcements, Stack Day planning discussions, leadership team coordination, education moment ideas, “who has a contact at [company]” requests.

6.4.2 Seat Forums

• One forum per parent BNI classification. All splits roll up to the parent forum (e.g., “Insurance — P&C” and “Insurance — Life” members both belong to the “Insurance” seat forum).
• Examples: “CLT BNI Medicare Specialists,” “CLT BNI Roofers,” “CLT BNI Financial Advisors”
• Content: Best practices for leveraging BNI for their specific business, education moment ideas, seasonal campaign strategies, what’s working in their chapter, coordinating on leads across geography.

Access model — open floor, not gated:

Seat forums are not restricted to seat holders. Anyone can browse to, search, post in, and reply in any seat forum. The difference is in what surfaces in your feed and what you get notified about:

Notification options for seat holders and forum followers:

1. Daily digest (default) — One aggregated notification per day summarizing all new threads and activity across your subscribed forums. Not per-thread; a single daily rollup.
2. Every new thread — Notified immediately when a new thread is created in the forum. Replies to existing threads are still daily digest unless you follow that specific thread.
3. Everything — Notified on every new thread and every reply. High volume; not recommended for most members.

Reply-to-follow prompt: When any member replies to a thread in a seat forum they don’t already follow, the platform prompts: “You replied to this thread. Would you like to be notified of new responses?” This captures ad-hoc interest without requiring members to manually manage subscriptions.

Why open, not gated: A marketing professional may have deep experience running campaigns for plumbers and can add enormous value to the plumbing seat forum. A CPA may have insight into how roofers should structure seasonal cash flow. Cross-pollination beats siloing. The seat holders are the primary audience and default subscribers, but the floor is open to all.

6.4.3 Forum Governance

• Each forum (chapter and seat) has one or more volunteer moderators from among its members.
• Moderators keep discussion collegial, on-topic, and focused on tactics (not competitive).
• Chapter forum moderators have the additional power to promote threads to metro-wide visibility.
• Moderator role is tracked in the platform with a small engagement score bonus.
• Moderators are appointed by chapter leadership (for chapter forums) or by platform admins (for seat forums, typically the most active seat holder across chapters).

6.4.4 Monthly/Quarterly Zoom Meetups by Seat

• 30-minute tactical video sessions where all members in a classification across chapters meet.
• Agenda: “What’s working,” “What I need help with,” “Seasonal planning.”
• Scheduled and tracked through the platform; Nextcloud CalDAV for calendar invites.
• Meetup summaries posted to the seat forum afterward for members who couldn’t attend.

6.4.5 Three-Legged Stool Networks (Cross-Seat Referral Clusters)

Beyond per-seat forums, the platform supports cross-seat referral clusters — groups of non-competing professions that naturally feed each other leads across chapter lines.

• Examples:
  • Home services: Roofer + Remodeler + Insurance Adjuster + Plumber + Electrician + Home Inspector
  • Financial services: CPA + Financial Advisor + Estate Attorney + Insurance (Life) + Mortgage Broker
  • Wedding: Florist + Caterer + Photographer + Travel Agent + DJ + Venue Manager
  • Health & wellness: Chiropractor + Massage Therapist + Personal Trainer + Nutritionist + Physical Therapist
• How it works: A roofer in Westlake Select, a remodeler in Waxhaw, and an insurance adjuster in Ballantyne form a cross-chapter referral cluster. They actively feed each other leads, meet biweekly (in-person or via Zoom), and coordinate on seasonal pushes.
• Platform support: The seat management system (§6.2) includes Power Team mapping that visualizes which clusters are complete vs. have gaps. Cross-chapter clusters can have their own forum thread or Nextcloud shared folder for coordination.
• Recruitment value: When pitching BNI to a prospective plumber, you can say “We have a home services cluster with a roofer, remodeler, and adjuster already actively referring to each other across three chapters — you’d slot right in.”
• Documentation: Successful clusters are documented as case studies on the platform (via Beacon CMS) to recruit more chapters and members into the network.

6.4.6 Metro-Wide Best Practices Forum

In addition to chapter forums and seat forums, the platform includes a single metro-wide best practices forum visible to all members across all chapters. This is the commons — where cross-cutting discussion happens that doesn’t belong to any one chapter or seat.

Purpose: - Discuss and debate potential membership requirements before chapters vote to adopt them - Share recruiting tactics: what’s working on LinkedIn, Alignable, Facebook, cold outreach - Share education moment ideas and scripts that worked well - Discuss Alignable strategy: profile optimization, review tactics, how to convert Alignable connections to BNI visitors - Coordinate metro-wide events (content days, lunch & learns, Stack Day scheduling) - Platform feedback: feature requests, bug reports, suggestions - Share success stories and wins that span chapters

Access model: - All platform members are auto-subscribed with daily digest notifications (default) - Members can adjust to every-new-thread or mute entirely - Anyone can post and reply - Moderated by platform admins (not chapter-level moderators)

Example threads: - “Draft requirement: Video recommendations during 1-on-1s — discuss before we propose to our chapter” - “LinkedIn invitation scripts that are actually getting responses” - “Alignable tips: how to turn a recommendation into a BNI visit” - “Stack Day coordination: who’s targeting what profession this month?” - “Content day planning for Q3 — who’s in?” - “Feature request: ability to tag a referral as ‘closed/completed’ to trigger review prompts” - “What referral incentives work for your industry? Share what you offer referred customers and referring members”

6.5 Visitor Pipeline & CRM Integration

6.5.1 Per-Chapter Visitor Registration Form

Every chapter gets a digital visitor registration form that replaces the paper sign-in sheet. The form is a public-facing LiveView page at a clean URL (e.g., bniclt.com/visit/westlake-select) that members can text or email to prospective visitors.

Fields captured: - Name, email, phone number, business name - Profession/industry (mapped to BNI classification for seat matching) - How did you hear about us? — dropdown: Invited by a member, Facebook, Google search, Alignable, BNI website, word of mouth, drove past/walk-in, other (free text). This tracks acquisition channel for marketing ROI analysis. - Invited by (optional) — if a member invited them, they can enter the member’s name. This links to the sponsoring member for engagement scoring and Power of One tracking. Left blank if the visitor found the chapter through ads, search, or word of mouth. - Which chapter meeting they plan to attend (date selector) - Optional: website URL, LinkedIn/Alignable profile

Why this matters: - Paper sign-in sheets are illegible, get lost, and never make it into a CRM - Digital capture feeds directly into Go High Level for automated follow-up — zero manual data entry - The optional “invited by” field enables accurate “visitors brought” tracking for engagement scoring and Power of One reporting, while still capturing visitors who arrive through ads, search, or word of mouth - Acquisition channel tracking shows which marketing efforts are actually producing visitors — Facebook ads vs. Alignable outreach vs. Google search vs. member invitations - Members can share the registration link via text message while they’re on the phone with a prospect: “I’ll text you the link right now, takes 30 seconds to register” - QR code generated for each chapter’s form — printed on table tents (folded cards that stand upright on the meeting table, like a restaurant dessert card, reading “Visiting today? Scan to register”). Walk-in visitors scan with their phone camera, the form opens in their browser, and they register in 30 seconds — no paper, no clipboard, no illegible handwriting. The same QR code can be printed on chapter flyers, business cards, or any marketing material.

Registration → CRM flow: - Visitor submits form → data pushed to Go High Level via webhook - GHL creates contact, tags with chapter name and acquisition channel, assigns to visitor drip sequence - Platform records the visitor, links to sponsoring member (if provided), matches to open seat classification - If the visitor’s profession matches an open seat, the chapter leadership gets an immediate notification: “A [plumber] just registered to visit — you have an open plumbing seat” - Acquisition channel data feeds into marketing ROI dashboard: “This month, 12 visitors came from Facebook ads, 8 from member invitations, 3 from Google search”

6.5.2 Visitor Portal (Public-Facing)

The platform includes public-facing content designed to convert visitors before they ever walk into a meeting:

• “Find a Chapter” page — Search by location, meeting day/time, or open seat. Shows which chapters have an open seat matching the visitor’s profession, with drive times.
• Seat category landing pages — “Thinking about joining BNI as a plumber in Charlotte?” with: what plumbers earn through BNI (TYFCB data), which chapters have an open plumbing seat, testimonials from BNI plumbers, what a typical meeting looks like, and a registration CTA.
• Visitor FAQ — “What to expect at your first BNI meeting,” addressing common objections (time commitment, cost, exclusivity).
• Seat forum preview — Visitors can see (but not post in) the seat forum for their profession. This gives them a taste of the cross-chapter community they’d be joining. Seeing active professionals in their field sharing tactics and supporting each other is a powerful conversion lever.
• Chapter stats — Each chapter’s public page shows aggregated stats: member count, total TYFCB this year, referrals passed last month, years active. Social proof at the chapter level.

6.5.3 Automated Follow-Up Sequences (Go High Level)

• Visitor-to-Member Pipeline: The entire visitor journey is modeled as a GHL pipeline with visual stages: Registered → Reminded → Visited → Second Visit → Application → Approved → Member → Lost/Declined. Each stage transition triggers stage-specific workflows automatically. Bryan and chapter leadership can see the full pipeline board inside GHL, filtered by chapter. See Appendix B.3 for the complete pipeline definition and stage-by-stage workflow triggers.
• Automated sequences triggered by Go High Level:
  • Immediate: Thank you email + “what to expect at your visit” guide
  • Day before: SMS reminder with meeting time and location
  • 2 hours before: SMS “see you soon” with parking/entrance details
  • Day after: Email with chapter highlights from the meeting they attended
  • Weekly: Chapter stats email (TYFCB, referrals, high-fives) for 8–12 weeks
  • Seat urgency: “The [profession] seat you expressed interest in has another candidate — don’t wait”
  • Application nudge: Visited twice but hasn’t applied after 14 days → email with application link and profession-specific testimonial
  • Seat reopened: A seat that was filled reopens → email to past visitors who matched that classification
• Appointment booking: Visitors can book a call with the membership committee or a 1-on-1 with a chapter member directly from follow-up emails, using GHL’s calendar system. Bookings trigger webhooks that update the platform automatically. See Appendix B.5.
• Conversion tracking: Visitor → Second visit → Application → Member. Track conversion rates per chapter, per acquisition channel, per seat category, and per pipeline stage. Pipeline analytics are pulled from GHL and displayed in the platform’s admin dashboard.

6.5.4 Visitor Communication History

Chapter leadership can view the full SMS and email conversation thread with any visitor directly in the platform’s admin dashboard — pulled from GHL’s Conversations API. No need to log into GHL separately. This surfaces alongside registration data, meeting attendance, pipeline stage, and engagement signals for a complete picture of every visitor’s journey. See Appendix B.6.

6.6 Social Boost System

WhatsApp remains the real-time coordination channel for social media boosting. The platform tracks and scores participation but does not replace WhatsApp for this workflow.

• Post a Request: Member shares a link to a social media post or recommendation thread to the platform’s Social Boost queue (or to WhatsApp for immediate action — the platform captures both).
• Boost Queue: Other members see pending boost requests, click through, comment/recommend, and mark it done.
• Reciprocity Tracking: The system tracks who boosts whom. Members who never boost others don’t get their own requests prioritized.
• Engagement Score Impact: Social boosts given and received factor into the member’s engagement score.
• Onboarding: Whether Social Boost participation is required of new members is a per-chapter decision, managed through the Membership Requirements Library (§6.10).

6.7 Engagement Scoring

Members earn engagement points for:

Members below a minimum threshold lose access to boost requests and forum visibility. This creates the “you must contribute to participate” dynamic discussed in the planning meeting.

6.8 CMS Pages (Beacon CMS)

Beacon CMS handles all published content pages:

• Blog posts (BNI tips, success stories, member spotlights)
• Education moment library (scripts, videos, slides)
• Event pages (lunch & learns, content recording days, chapter social events)
• Resource pages (how to join BNI, what to expect at a meeting, Power Team guides)
• Landing pages for advertising/marketing campaigns
• Visitor FAQ and “Find a Chapter” content (§6.5.2)
• Member success stories and case studies (§6.11.1)
• Seat category landing pages (§6.11.1)

Best Practices Guide Library:

A dedicated section of the site provides step-by-step guides for getting the most out of both BNI’s official tools and our platform. These are public-facing (indexable for SEO, contributing to topical authority) and serve double duty as onboarding resources for new members and as education moment material.

Getting the most out of BNI’s official tools: - “How to set up and optimize your BNI Connect profile” — step-by-step with screenshots - “How to use the BNI Connect mobile app effectively” — tips for logging slips, finding members, registering visitors - “How to navigate BNI Business Builder and complete your MSP training” - “How to read your chapter’s PALMS report and what the numbers mean” - “How to use the Classifications Not In Chapter report to find your next recruit” - “How to use the Chapter Traffic Light to benchmark against other chapters” - “How to enter cross-chapter referrals, TYFCB, and 1-on-1s in BNI Connect” - “How to register visitors through BNI Connect vs. our platform (and why we recommend both)”

Getting the most out of our platform: - “Quick start guide: setting up your profile in 5 minutes” - “How the seat forum works and why you should follow forums outside your seat” - “How to use the Social Boost system to amplify your chapter-mates” - “Understanding your engagement score and how to improve it” - “How to claim an open seat and recruit for it effectively” - “How to use the visitor registration form and QR code at your meeting” - “How to get the most SEO value from your member profile” — fill out every field, add your website, write a keyword-rich bio, add testimonials - “How to use Nextcloud for chapter file sharing from your phone” - “Guide to the Membership Requirements Library: what your chapter has adopted and what it means for you”

Cross-platform guides: - “BNI Connect vs. our platform: what to use when” — clear guide showing that BNI Connect is for official slip logging and PALMS, our platform is for everything else - “How to leverage Alignable alongside BNI for maximum referral growth” - “Social media playbook for BNI members: LinkedIn, Facebook, and Alignable tactics”

Flagship Content: “Best Practices for Running a Successful BNI Chapter”

A comprehensive, living guide published as a standalone Beacon CMS page (and linked prominently from every chapter’s dashboard). This is the platform’s signature content piece — designed to become the definitive resource for BNI chapter leadership in the Charlotte metro and beyond.

Content draws from three sources: 1. Existing BNI ecosystem knowledge — Dr. Misner’s published principles, BNI podcast episodes, regional director playbooks, and the research-based best practices compiled in Appendix G (chapter size math, surge growth model, contact spheres/Power Teams, Stack Days, visitor conversion, onboarding, pruning, Power of One, PALMS, social recruiting) 2. Platform-integrated tactics — how to use our platform’s features to operationalize each best practice. For example: the PALMS review best practice (Appendix G.9) is paired with guidance on posting weekly PALMS summaries to the chapter forum (requirement L-2), using the seat roster grid to identify recruitment priorities, and leveraging the engagement scoring dashboard to spot disengaged members before they become a problem 3. Real data from chapters on the platform — as chapters adopt the system, we collect anonymized data on what actually works. Which requirements correlate with faster growth? Do chapters that adopt P-9 (prospective member conversations) recruit faster? Does Social Boost participation predict chapter TYFCB? This section is updated quarterly with new findings, making the guide increasingly valuable over time.

Planned sections: - The math: why chapter size matters (with live data from platform chapters where available) - How to set growth targets and track them using the platform dashboard - Building and maintaining Power Teams using seat management and three-legged stool clusters - Running effective Stack Days with platform-coordinated recruiting claims - Converting visitors: from digital registration through the GHL drip sequence to application - Onboarding new members: the first 90 days using platform requirements and milestone tracking - Keeping members engaged: engagement scoring, requirements, and the “contribute to participate” culture - Pruning with data: using engagement scores and PALMS to have honest conversations - Cross-chapter collaboration: forums, Zoom meetups, and coordinated seasonal campaigns - Leveraging social media: Social Boost system, Alignable strategy, content days - Leading by example: leadership requirements (L-1, L-2, L-3) and how top chapters use them

Living document commitment: This page carries a “Last updated” timestamp and a changelog. Chapter leaders can subscribe to update notifications. As more chapters join and we accumulate more data, the guide evolves from “best practices based on BNI research” to “best practices proven by Charlotte metro data” — which is far more compelling for recruiting new chapters onto the platform.

6.9 Admin & Leadership Dashboard

• Chapter-level: Member count trend, visitor conversion funnel (from GHL pipeline data), seat fill rate, engagement leaderboard, upcoming Stack Day targets
• Metro-level: Chapter comparison, cross-chapter referral flow, forum activity by category, event attendance
• Seat analysis: Which classifications are most in-demand, which chapters have the most gaps, Power Team completion percentage
• Visitor pipeline view: Live pipeline stage counts pulled from GHL — how many visitors at each stage per chapter, conversion rate by stage, average time in each stage, drop-off points
• Communication history: View full SMS/email thread for any visitor or member, pulled from GHL Conversations API (Appendix B.6) — no need to switch to GHL
• Campaign performance: Email open rates, SMS response rates, workflow completion rates pulled from GHL — helps Bryan and leadership refine campaigns
• Acquisition channel analysis: Visitor counts and conversion rates by source (Facebook ads, Google search, Alignable, member invitations, walk-ins) — shows which marketing investments are producing members

6.10 Membership Requirements Library

Each chapter independently decides what additional membership requirements (beyond BNI’s own rules) apply to their members. The platform provides a shared library of requirements that any chapter can browse, adopt, or contribute to.

How it works:

1. Any chapter can create a new requirement. Once created, it enters the metro-wide library automatically with metadata: the requirement text, which chapter created it, when, and how many chapters have adopted it.
2. Any other chapter can browse the library and adopt any requirement for their own chapter. Adoption is a per-chapter decision — a chapter’s leadership team votes to adopt, and it becomes binding for their members.
3. Chapters can also write their own custom requirements that don’t yet exist in the library. Once created, these are also available for other chapters to adopt.
4. Per-chapter configuration: Each chapter has its own active requirements list. This is visible to prospective members during the visitor/onboarding process so expectations are clear before they join.

Data model:

Requirement (library-level)
  ├── title: string
  ├── description: text (detailed expectation)
  ├── created_by_chapter_id: reference
  ├── created_at: timestamp
  ├── category: onboarding | ongoing | leadership | optional
  ├── measurable: boolean
  └── metric_description: text (nullable — what platform metric tracks compliance)

ChapterRequirement (per-chapter adoption)
  ├── chapter_id: reference
  ├── requirement_id: reference
  ├── adopted_at: timestamp
  ├── enforced: boolean (is it mandatory or recommended?)
  └── custom_notes: text (chapter-specific notes on how they implement it)

Platform integration: - The onboarding flow (§G.6) shows new members their chapter’s active requirements during their first login - Engagement scoring (§6.7) can be configured to track compliance with adopted requirements - The admin dashboard (§6.9) shows requirement adoption rates and compliance per chapter - Chapters considering platform adoption can browse the requirements library to see what participating chapters expect — this demonstrates the value and seriousness of the network

Draft Requirements (Pre-Loaded in Library at Launch)

The following requirements ship with the platform as pre-authored drafts. No chapter is required to adopt any of them — they serve as a starting menu that chapters can activate, modify via custom notes, or ignore entirely. Each is designed to be measurable through the platform.

Onboarding Requirements:

Ongoing Participation Requirements:

Leadership Requirements:

6.11 Site Authority & Member SEO Benefits

The platform should be built from day one with a deliberate strategy to accumulate domain authority (DA) and then share that authority with members through backlinks and structured data. This is a tangible, measurable benefit of platform membership — every member’s business gets an SEO boost simply by having a complete profile.

6.11.1 Building Site Authority (Domain Authority Strategy)

The platform’s DA grows through a combination of topical authority (deep, niche content about business networking in Charlotte) and quality backlinks. Strategy:

Topical authority through content depth: - Beacon CMS blog publishes 2–4 articles per month on BNI-related topics: “How to maximize referrals as a Charlotte plumber,” “Building a Power Team in the Lake Norman area,” “What to expect at your first BNI meeting in Charlotte.” These are long-tail, locally targeted keywords with low competition and high relevance. - Education Moment library — every education moment script becomes a public, indexable page. Over time this becomes the most comprehensive BNI education resource on the web, drawing organic traffic and backlinks from BNI members and chapters worldwide. - Member success stories — detailed case studies (with member permission) published as public content. Each story naturally includes mentions of the member’s business, industry, and service area — creating keyword-rich, locally relevant pages. - Chapter landing pages — each participating chapter gets a public-facing page with meeting time, location, seat roster, and chapter stats. These pages target “[chapter name] BNI” and “[city] BNI chapter” searches. - Seat category landing pages — public pages for each BNI classification with descriptions, typical referral patterns, and links to members in that category across chapters. These target “BNI [profession] Charlotte” searches.

Quality backlink acquisition: - Member websites link back to the platform. Every member profile links to the member’s website (dofollow — see §6.11.2), creating a natural incentive for members to link back to the platform from their own sites (“Proud member of the Charlotte Metro BNI Network” badges, footer links, etc.). This creates a virtuous cycle: the more members link to the platform, the higher the platform’s DA grows, the more valuable the platform’s backlinks to member sites become. - Chapter websites and BNI regional pages — seek backlinks from official BNI regional sites, chapter Facebook pages, and any existing chapter websites. - Local business directories and chambers of commerce — list the platform in Charlotte Chamber, Lake Norman Chamber, Denver-Huntersville Chamber, and other local business directories. - Guest posts on local business blogs — contribute articles about business networking, referral marketing, and BNI to local Charlotte business publications. - Press coverage — as the platform grows, pitch local media (Charlotte Business Journal, Charlotte Observer, Lake Norman Citizen) on the cross-chapter collaboration story. Each press mention with a link is a high-value backlink. - BNI podcast and blog — if the platform produces measurable results, pitch Dr. Misner’s podcast or BNI’s national blog for a feature. A backlink from bnipodcast.com or bni.com would be extremely high value.

Technical SEO foundation: - Fast page loads (Phoenix/LiveView renders server-side, no SPA hydration delay) - Mobile-first responsive design - Proper canonical URLs, sitemap generation, robots.txt - SSL everywhere (Let’s Encrypt) - Clean URL structure: /chapters/westlake-select, /members/jane-doe-roofer, /seats/insurance-property-casualty - Internal linking strategy: every member profile links to their chapter page, their seat category page, and their Power Team cluster page

6.11.2 Member SEO Benefits (Dofollow Backlinks)

Every complete member profile on the platform includes a dofollow backlink to the member’s business website. This is a direct, measurable SEO benefit of platform membership.

How it works: - Member completes their profile (requirement O-1) including their business website URL - The platform renders their profile as a public, indexable page with a dofollow <a> tag pointing to their website - As the platform’s DA grows, the SEO value of that backlink grows with it - Members with complete profiles on a DA 30+ site get a meaningful boost to their own site’s authority

Why this matters to BNI members: - Most BNI members are small business owners who struggle with SEO - A single backlink from a niche-relevant, locally authoritative site can be worth hundreds of dollars (industry average for a quality backlink is ~$500) - This is a benefit they get simply by being an active member with a complete profile — it costs them nothing extra - It’s a compelling recruiting pitch: “Join our chapter and your business gets a backlink from the Charlotte metro BNI network”

Conditions for dofollow link (tied to engagement): - Member must have a complete profile (O-1) - Member must maintain engagement score above the platform minimum (P-4) - If a member’s engagement drops below threshold for 60+ days, their profile page is de-indexed (noindex meta tag) and the backlink becomes nofollow until they re-engage - This creates a powerful incentive loop: participate → keep your backlink → benefit your business SEO

6.11.3 Schema.org Structured Data

Every member profile page and chapter page includes JSON-LD structured data to help search engines understand and display the content:

Member profile pages — LocalBusiness schema (using the most specific subtype available):

{
  "@context": "https://schema.org",
  "@type": "Plumber",
  "name": "ABC Plumbing Services",
  "description": "Residential and commercial plumbing serving Lake Norman and Charlotte metro.",
  "address": {
    "@type": "PostalAddress",
    "addressLocality": "Denver",
    "addressRegion": "NC"
  },
  "telephone": "+1-704-555-1234",
  "url": "https://abcplumbing.com",
  "image": "https://bniclt.com/members/john-doe/photo.jpg",
  "memberOf": {
    "@type": "Organization",
    "name": "BNI Westlake Select",
    "url": "https://bniclt.com/chapters/westlake-select"
  },
  "sameAs": [
    "https://facebook.com/abcplumbing",
    "https://linkedin.com/company/abcplumbing"
  ]
}

This means a member’s business may appear as a rich result in Google — with name, address, phone, and organization affiliation displayed directly in search results. Many small business owners don’t have structured data on their own sites, so the platform profile may actually generate richer search results than their own website.

Chapter pages — Organization schema with member array and event references for upcoming meetings.

Seat category pages — ItemList schema listing all members in that classification across chapters.

Blog/education content — Article schema with author, datePublished, publisher for rich snippets in search results.

6.11.4 Additional SEO-Adjacent Member Benefits

Google Business Profile enhancement: - Member profiles include a link to their Google Business Profile (GBP). The platform’s structured data, consistent NAP (Name, Address, Phone), and niche-relevant context reinforce the signals Google uses for local pack rankings. - Education content on the platform teaches members how to optimize their own GBP and ask for reviews.

Social proof amplification: - Member testimonials collected through the platform are published on public profile pages with Review structured data. This can generate star ratings in search results for the member’s profile page. - Social Boost system activity generates real, organic social media engagement that search engines treat as trust signals.

Content co-creation: - Members can publish guest blog posts on the platform’s Beacon CMS blog (education moments, industry insights, case studies). Each post includes an author bio with a dofollow backlink to their website — a second, context-rich backlink from a different page. - Members who contribute content get additional engagement score points and a “Content Contributor” badge on their profile.

Local citation consistency: - The platform’s member directory serves as an additional high-quality local citation for each member’s business. Consistent NAP data across the platform, the member’s own website, Google Business Profile, and other directories strengthens local SEO signals.

“Powered by” badge for member websites: - Offer members an embeddable “Member of Charlotte Metro BNI Network” badge with a backlink to the platform. Members place it on their website footer or about page. This creates reciprocal linking that further strengthens both the platform’s DA and the member’s local relevance signals.

6.11.5 SEO Metrics & Targets

7. Revenue Model

Phase 1: Free / Value-First (Months 1–6)

No charge. Build the platform, prove it with Westlake Select and one additional chapter. Demonstrate value.

Phase 2: Chapter Subscriptions (Months 7–12)

Phase 3: Additional Revenue Streams (Year 2+)

• Go High Level setup & management: $200–500/chapter one-time setup + $50/month managed campaigns (Bryan’s lane)
• Metro-wide events: Lunch & learns, $20–25/ticket, 50–100 attendees, 4x/year = $4,000–10,000/year
• Content recording days: $50/person, 20–30 people, quarterly = $4,000–6,000/year
• Premium member features: Enhanced profiles, priority boost requests, advanced analytics = $10/member/month
• Regional licensing: $500–1,000/month per metro area for the platform template

Revenue Projection (Conservative, Year 1–3)

This is a lifestyle business at Charlotte scale. It becomes significant at multi-region scale.

8. Go-to-Market Strategy

Phase 1: Prove with Westlake Select (Now → April 2026)

1. Build MVP with Westlake Select as the founding chapter
2. Configure all seats, build member profiles, set up visitor registration
3. Connect Go High Level for automated visitor follow-up
4. Run for 6–8 weeks, measure visitor conversion improvement
5. Document results: before/after visitor conversion rate, member growth, engagement metrics

Phase 2: Expand to Second Chapter (May → July 2026)

1. Approach Waxhaw chapter (strong leadership team, go-getter culture, existing relationships)
2. Onboard Waxhaw onto the platform
3. Demonstrate cross-chapter features: directory, peer forums, shared event marketing
4. This is the critical proof point — if two chapters collaborating through the platform generates measurably more value than either alone, the model works

Phase 3: Charlotte Metro Rollout (Aug 2026 → End of 2026)

1. Visit remaining Charlotte metro chapters (calendar already built — 29 chapters, 1/week)
2. Present the platform and results from Westlake Select + Waxhaw
3. Focus on chapters with strong leadership teams willing to adopt new tools
4. Target: 10 chapters onboarded by end of 2026

Phase 4: Monetize & Scale (2027)

1. Introduce paid tiers for chapters beyond the founding group
2. Launch metro-wide events (lunch & learns, content days)
3. Begin packaging for other regions
4. Present to BNI Southeast regional leadership

9. Operational Plan

Team & Roles

Weekly Operations

• Monday: Review weekend social boost requests, clear the queue
• Tuesday–Thursday: Respond to forum posts, monitor visitor pipeline, follow up on stalled conversions
• Friday: Weekly chapter stats push to all participating chapters, admin review of engagement scores
• Ongoing: 1 cross-chapter visit per week (per the calendar)

Hosting & Infrastructure

• Hosting: Fly.io (Elixir-native, multi-region, built-in PostgreSQL) for the Phoenix app; dedicated VPS or Docker host for Nextcloud
• Nextcloud: Docker Compose deployment (Nextcloud + MariaDB/PostgreSQL + Redis + Collabora/OnlyOffice for in-browser editing). $5–10/mo VPS (Hetzner, DigitalOcean, or self-hosted). Can colocate on same VPS initially.
• Database: PostgreSQL (managed) for Phoenix app; Nextcloud manages its own database
• Email transactional: Swoosh with SendGrid or Postmark adapter
• Email marketing/SMS: Go High Level (via Bryan’s agency account)
• File sync & collaboration: Nextcloud (WebDAV, CalDAV, CardDAV)
• Domain: bniclt.com or charlottebni.com or similar (check availability); Nextcloud at files.bniclt.com or similar subdomain
• SSL: Let’s Encrypt / Fly.io managed (Phoenix); Let’s Encrypt / Caddy (Nextcloud)

10. Technology Stack

Mobile-First Design Requirement:

The platform must be designed mobile-first. BNI members are small business owners — they’re at jobsites, in their cars, between client meetings. Every platform feature (forums, social boost queue, profile updates, visitor registration, engagement dashboard) must work flawlessly on mobile browsers with no horizontal scrolling, appropriately sized touch targets, and fast load times.

Phoenix LiveView renders server-side HTML with WebSocket-driven interactivity, which works well in mobile browsers without the bundle-size penalties of client-side SPA frameworks. All LiveView components should be designed responsive-first using Tailwind CSS breakpoints.

Future mobile considerations: - Progressive Web App (PWA): Add a service worker and web app manifest so members can “install” the platform to their home screen and receive push notifications. This is a lightweight path to an app-like experience without building native iOS/Android apps. - LiveView Native: The Elixir ecosystem is developing LiveView Native, which renders native iOS/Android UI from LiveView server code. If this matures during our development timeline, it could provide native mobile apps with minimal additional codebase. Monitor for production readiness. - Nextcloud mobile apps already provide native file access on iOS and Android — no additional work needed for file workflows.

See the companion Technical Development Plan document for the complete package breakdown, architecture diagrams, and implementation guide.

11. Key Metrics & KPIs

Chapter Growth Metrics

Engagement Metrics

Platform Metrics

12. Risk Assessment

12A. Data Governance & Privacy Policy

This is a draft framework to be refined through discussions with chapter leadership during onboarding of the first few chapters. The goal is to establish trust from day one while remaining practical about the data we need to operate.

Data Ownership Principles

1. Members own their personal data. A member can request export or deletion of their profile, forum posts, and activity history at any time. This follows GDPR-style principles even though we’re not legally required to in the US — it builds trust.
2. Chapters own their chapter-level data. If a chapter leaves the platform, they receive a full export of: member roster, seat configuration, visitor registration records, chapter forum content, adopted requirements, and aggregated engagement data. The chapter can take their data and walk away.
3. The platform owns aggregated, anonymized analytics. Metro-wide trends (average chapter growth rate, most popular seat categories, engagement benchmarks) are platform property and may be used in marketing, presentations to BNI leadership, and public reporting — always anonymized.
4. Visitor data is shared with the visitor’s target chapter and Go High Level. Visitors are informed during registration that their data will be used for follow-up communication. They can opt out of GHL sequences at any time via standard unsubscribe.

Data Categories & Retention

Member Departure

When a member leaves BNI or their chapter leaves the platform: - Member can request full data export (profile, activity history, forum posts) in JSON/CSV format - Member can request deletion — profile page is removed, forum posts are anonymized (author shown as “[Former Member]”), engagement data is purged - If member simply leaves BNI but chapter remains on platform, profile is marked inactive and de-indexed after 30 days. Data retained for 12 months in case of return, then auto-purged.

Chapter Departure

When a chapter leaves the platform: - Full data export from the platform provided within 7 days: roster, seat config, visitor records, forum content, requirements, engagement data - Chapter’s public pages are taken down - Cross-chapter forum posts by that chapter’s members remain visible (attributed to “[Chapter Name — departed]”) unless the chapter requests deletion - Go High Level data handling: Because all chapters share a single GHL account with per-chapter tags (not sub-accounts), the departing chapter’s contacts are intermingled with metro-wide contacts. The departure process: 1. Export all GHL contacts tagged with the departing chapter’s tag → provide CSV to chapter leadership 2. For contacts tagged only with the departing chapter (not also tagged for other chapters): archive or delete per the chapter’s preference 3. For contacts tagged with the departing chapter and other chapters (e.g., a visitor who visited multiple chapters): remove the departing chapter’s tag but retain the contact for the other chapters’ sequences 4. Deactivate any GHL workflows/campaigns specific to the departing chapter 5. If the departing chapter wants to continue using GHL independently, they set up their own separate GHL account and import their exported contacts. We cannot transfer a “slice” of our shared account.

Security

• All data encrypted in transit (TLS) and at rest (PostgreSQL encryption, Nextcloud server-side encryption)
• Member authentication via AshAuthentication (bcrypt password hashing, optional OAuth)
• Role-based access control: platform admin, chapter admin, member, visitor (read-only public content)
• GHL API authentication via Private Integration Token with webhook signature verification
• Regular backups: daily database snapshots, Nextcloud file backup
• No member data sold to third parties. Ever.

Consent & Transparency

• Members agree to the data policy during account creation (requirement O-6 ensures acknowledgment)
• The data policy is published on a public page (Beacon CMS) — no hidden terms
• Any material changes to the data policy are communicated to all members via email and platform notification, with 30-day notice before taking effect
• Members can email the platform admin to request data export or deletion at any time

12B. Chapter Onboarding Playbook

Repeatable process for onboarding a new chapter onto the platform. Designed to get a chapter from “yes, we’re interested” to “fully operational” in 2–3 weeks.

Phase 0: Discovery & Decision (1–2 Meetings)

Meeting 1: Intro presentation to chapter leadership (President, VP, Secretary, Membership Committee Chair)

• Demo the platform using Westlake Select as the live example
• Walk through the value proposition: digital visitor registration, automated follow-up, seat management, cross-chapter forums, SEO benefits for members
• Show the competitive analysis (§5A): what the platform does that BNI Connect doesn’t
• Show the requirements library — let leadership browse and discuss which requirements might be relevant
• Answer questions about data privacy (§12A), cost (free in Phase 1), and time commitment
• Leave behind: one-pager summary, link to Westlake Select’s chapter page on the platform

Meeting 2: Leadership team decision

• Chapter leadership votes to join (or not)
• If yes: assign a Chapter Champion — one member who serves as primary liaison with the platform team during onboarding. Ideally the VP or Membership Committee Chair.
• Sign the data governance agreement (simple, one-page)
• Schedule the onboarding kickoff

Phase 1: Setup (Week 1)

Platform team tasks: - [ ] Create chapter entity in the platform database - [ ] Configure seat map: import BNI Connect roster → map to classification taxonomy → configure any seat splits the chapter uses - [ ] Create chapter forum (chapter-only) - [ ] Generate visitor registration form URL and QR code - [ ] Set up chapter in Go High Level: create tags, import existing visitor contacts (if any), activate drip sequences - [ ] Create chapter folder structure in Nextcloud with appropriate permissions - [ ] Create chapter’s public-facing page on the platform (Beacon CMS)

Chapter Champion tasks: - [ ] Provide current member roster (export from BNI Connect or manual list): name, email, phone, business name, classification, website URL - [ ] Identify any custom seat splits the chapter currently uses - [ ] Provide chapter meeting details: day, time, location, address for chapter page - [ ] Provide chapter logo and any existing marketing assets → upload to Nextcloud

Phase 2: Member Onboarding (Week 2)

Chapter Champion announces the platform at the weekly meeting: - 5-minute presentation: “We’re joining the Charlotte Metro BNI Network platform. Here’s what it does for you and what we need from you.” - Distribute the platform signup link (or project QR code on screen) - Set expectation: “Complete your profile this week”

Member onboarding flow (per member): 1. Receive email invitation with signup link 2. Create account (AshAuthentication — email + password) 3. Complete profile: photo, business name, bio, contact info, website URL, Alignable URL, referral incentive (optional), “open to prospective member conversations” flag 4. Acknowledge chapter requirements (requirement O-6) 5. Subscribe to seat forum (auto-subscribed if classification is set) 6. Platform sends welcome email with: quick-start guide, link to chapter forum, link to metro-wide best practices forum, Nextcloud invitation

Target: 80% of members with complete profiles within 14 days.

Phase 3: Activation (Week 3)

• Chapter leadership reviews adopted requirements — select from library or defer
• First visitor registers through the digital form (retire the paper sign-in sheet)
• First Social Boost request posted by a member
• Chapter Champion posts first thread in chapter forum (e.g., “Welcome to the platform — introduce yourself and share what you’re looking for in referrals this month”)
• Leadership reviews their seat roster grid on the platform — verify accuracy
• Members begin claiming open seats for recruitment

Phase 4: Steady State (Week 4+)

• Chapter Champion provides feedback after first month — what’s working, what’s confusing, what’s missing
• Platform team adjusts based on feedback
• Chapter added to cross-chapter event calendar
• Chapter members begin participating in seat forums and metro-wide best practices forum
• Chapter stats begin appearing in metro-wide dashboard

Onboarding Checklist (Summary)

13. Phased Roadmap

Phase 1: Foundation (Feb–Apr 2026)

• Research BNI seat classifications — full taxonomy compiled
• Research Charlotte metro chapters — 29 chapters identified + visit calendar
• Research BNI growth best practices — comprehensive playbook compiled
• Finalize tech stack and development plan
• Build MVP: chapter hub, seat management, member profiles, visitor registration
• Integrate Go High Level: visitor webhook, initial drip campaign
• Deploy with Westlake Select as founding chapter
• Set up Go High Level sandbox (Bryan — account created)
• Begin weekly cross-chapter visits

Phase 2: Prove & Expand (May–Aug 2026)

• Measure and document Westlake Select results (6-week minimum)
• Onboard Waxhaw chapter
• Build peer forums (3–5 initial categories)
• Build social boost system
• Build engagement scoring
• Demonstrate cross-chapter value (Westlake Select ↔︎ Waxhaw)
• First metro-wide event (lunch & learn or content recording day)

Phase 3: Scale (Sep 2026–2027)

• Onboard 10+ chapters
• Launch all planned peer forums (10+ categories)
• Introduce paid tiers
• Build admin/leadership dashboard
• Present to BNI Southeast regional leadership
• Begin packaging for other regions
• Explore BNI corporate partnership or acquisition

14. Financial Projections

Startup Costs

Revenue vs. Cost (Monthly, Steady State Year 2)

This is a high-margin SaaS play with very low infrastructure costs thanks to the Elixir/Fly.io stack.

15. Exit & Scale Strategy

Option A: Regional Expansion

License the platform to BNI operators in other metro areas. Charge $500–1,000/month per metro area for the platform + initial setup fee.

Target markets: Raleigh-Durham, Greensboro, Greenville SC, Columbia SC, Nashville, Atlanta

At 10 metro areas × $750/month average = $90,000/year recurring.

Option B: BNI Corporate Partnership

Present the platform and results to BNI corporate. Offer to integrate with BNI Connect or license as an official BNI tool. This is the “sell to BNI” play.

Option C: Franchise Model

Train other BNI members in other regions to operate their own instance of the platform. Charge a franchise fee + ongoing percentage.

Option D: SaaS for Non-BNI Networking Groups

Generalize the platform beyond BNI to serve other referral networking organizations (LeTip, Rotary business councils, etc.).

Appendix A — Seat Splitting Model

The Problem

BNI’s official taxonomy has ~290 classifications across 27 industries. Most chapters have 15–40 members. The standard model is one member per classification.

However, chapters often find that some classifications are too broad. “Insurance” could reasonably be split into:

• Insurance — Property & Casualty (Home, Auto)
• Insurance — Life & Disability
• Insurance — Commercial
• Insurance — Supplemental (AFLAC-type)
• Insurance — Medicare/Health

Different chapters will split differently (or not at all). The platform must support this flexibility while maintaining data integrity for cross-chapter features.

Data Model

BNI Classification (Official)
  └── Chapter Seat (per-chapter configuration)
       ├── status: open | claimed_for_recruitment | applicant_in_process | filled | closed
       ├── is_split: boolean
       ├── parent_seat_id: nullable (if this is a sub-seat)
       ├── custom_label: string (e.g., "Insurance — Commercial")
       ├── member_id: nullable (if filled)
       ├── claimed_by_member_id: nullable (if claimed for recruitment)
       ├── claim_target_date: nullable
       ├── claim_expires_at: nullable (auto-set to 60 days from claim)
       └── claim_notes: text (nullable)

Rules:

1. If a chapter does NOT split a classification, they have one seat for it with the default label.
2. If a chapter splits a classification, the parent seat becomes inactive and N sub-seats are created with custom labels.
3. Sub-seats inherit the parent’s industry grouping and Power Team associations.
4. Cross-chapter features (peer forums, directory search) match on the parent classification, not the custom label. A “Insurance — Commercial” member in Chapter A and a “Insurance — P&C” member in Chapter B both appear under the “Insurance” peer forum.
5. A chapter can un-split a classification (merge sub-seats back), which requires handling the members currently in sub-seats.

Example

All members in any insurance sub-seat across all chapters would appear in the “Insurance” peer forum and be searchable under “Insurance” in the cross-chapter directory.

Appendix B — Go High Level Integration Architecture

B.1 Overview & Integration Philosophy

Go High Level (GHL) is the CRM and marketing automation layer. The Phoenix platform is the source of truth for member data, seat status, engagement scores, and chapter configuration. GHL is the communication engine — it handles email, SMS, voice, appointment booking, and pipeline automation. Neither system should require the other’s admin UI for daily operations; each should surface the data it needs from the other via API.

Design principle: bidirectional sync with clear ownership. The platform owns the data model; GHL owns the communication channels. When data changes on either side, it propagates to the other via API calls or webhooks processed through Oban background jobs.

B.2 Integration Model: Single GHL Account, Multi-Chapter via Tags + Custom Fields

Per the planning conversation with Bryan: all chapters share a single GHL account (not sub-accounts). Contacts are segmented by tags and custom fields.

Tag structure:

• chapter:westlake-select, chapter:waxhaw, etc.
• role:visitor, role:member, role:leadership
• seat:insurance-property-casualty, seat:plumber, etc.
• status:registered, status:visited, status:second-visit, status:application, status:approved, status:member, status:inactive
• source:website, source:facebook-ad, source:google-search, source:alignable, source:member-invitation, source:walk-in, source:word-of-mouth
• engagement:high, engagement:medium, engagement:low, engagement:at-risk
• claim:active-recruiter (member currently has an active seat recruitment claim)

Custom fields on GHL contacts (synced from platform):

• platform_member_id — links GHL contact to platform member record for bidirectional sync
• engagement_score — numeric, synced daily from platform
• seat_classification — text, the member’s BNI classification
• chapter_name — text, the member’s home chapter
• profile_complete — boolean, whether the member has completed requirement O-1
• days_since_last_activity — numeric, synced daily
• recruitment_claims — text, comma-separated list of seats the member is actively recruiting for
• visitor_invited_by — text, name of the member who invited this visitor (if any)
• visitor_seat_match — boolean, whether the visitor’s profession matches an open seat in the target chapter
• visitor_pipeline_stage — text, current stage in the visitor-to-member pipeline

B.3 Visitor-to-Member Pipeline (GHL Opportunities)

The full visitor journey is modeled as a GHL pipeline with stages, giving Bryan and chapter leadership a visual funnel inside GHL and enabling stage-based workflow triggers.

Pipeline: “Visitor to Member”

Each stage transition can be triggered from the platform via the GHL Opportunities API (PUT /opportunities/{id} with new stageId). Bryan can also move contacts manually in GHL’s pipeline board when needed.

Value: Bryan gets a visual pipeline board showing every visitor across every chapter, filterable by chapter tag. Leadership can see at a glance: “We have 3 visitors in the Visited stage, 1 in Application, and 2 were Lost this month.” Conversion rate by stage and by chapter is automatically calculable.

B.4 Bidirectional Data Flows

Platform → GHL (Push via API)

GHL → Platform (Push via Webhooks)

B.5 Appointment Booking Integration

GHL’s calendar system provides a booking experience we can embed in the platform without building our own scheduling logic.

Use cases:

1. Visitor intro call: After a visitor registers, the follow-up email includes a “Book a quick call with our membership committee” link. This is a GHL calendar booking link. When the visitor books, GHL creates the appointment, sends confirmations, and our webhook handler logs it on the platform.

2. 1-on-1 scheduling: Members can use GHL calendar links in their platform profiles — “Book a 1-on-1 with me.” This is optional and supplementary to however members currently schedule 1-on-1s, but provides a frictionless booking experience with automatic reminders.

3. Cross-chapter visit booking: Each chapter’s public page can include a GHL calendar widget: “Want to visit our chapter? Pick a date.” The visitor (or visiting member from another chapter) picks a meeting date, GHL sends a reminder, and the platform logs the visit intent for engagement scoring credit.

Implementation: GHL Calendar API endpoints: - GET /calendars — list available calendars (one per chapter, one for membership committee, etc.) - GET /calendars/{id}/free-slots — query available time slots - POST /calendars/{id}/appointments — create booking programmatically - Alternatively, embed GHL’s hosted booking page via iframe or link — lower effort, still triggers webhooks

B.6 Conversation Visibility in Admin Dashboard

GHL’s Conversations API provides full access to the message thread between GHL and any contact. The platform’s admin dashboard can surface this without chapter leadership needing to log into GHL.

Implementation: - GET /conversations/{contactId}/messages — retrieve full SMS/email thread for a visitor or member - Display in a “Communication History” panel on the visitor’s record in the platform admin dashboard - Read-only by default (leadership views the thread); optionally allow sending messages via POST /conversations/{contactId}/messages directly from the platform UI

Value: Chapter leadership checks a visitor’s record on the platform and sees: registration data, meeting attendance, pipeline stage, engagement signals, and the full communication history — all in one place. No context-switching to GHL.

B.7 Campaign & Workflow Management

GHL workflows are the automation engine. The platform can trigger them programmatically and monitor their results.

Platform-triggered workflows:

Monitoring: The platform can query GHL’s workflow and campaign analytics to display in the admin dashboard: email open rates, SMS response rates, workflow completion rates. This data helps Bryan and chapter leadership refine campaigns without trial and error.

B.8 Event-Driven Architecture (Technical)

All GHL API calls from the platform are processed asynchronously through Oban jobs to ensure reliability and respect rate limits.

Platform Event (e.g., visitor registers)
  → Ash Reactor / Notifier creates Oban job
    → Oban job calls GHL API via Req HTTP client
      → On success: log result, update platform record
      → On failure: retry with exponential backoff (max 5 retries)
      → On permanent failure: log error, notify platform admin

Rate limit management: GHL allows 100 requests per 10 seconds and 200,000 per day. For daily batch syncs (engagement scores for all members), spread requests over time using Oban’s scheduled jobs. For real-time events (visitor registration), process immediately — these are low-volume.

Idempotency: Every GHL contact created from the platform stores the GHL contactId on the platform record. Before creating a new contact, check if ghl_contact_id already exists → if so, update instead of create. This prevents duplicate contacts from retry logic.

B.9 API Authentication

GHL V2 API uses Private Integration Tokens for single-account access (which is our model — single GHL account, not marketplace app).

• Create Private Integration in GHL Settings → Integrations → Private Integrations
• Select scopes: contacts (read/write), opportunities (read/write), calendars (read/write), conversations (read/write), workflows (read), webhooks (read/write)
• Store token in Phoenix config/secrets (never in source code)
• Use Req HTTP client with Authorization: Bearer <token> header
• Token does not expire but should be rotated periodically as a security practice

B.10 Webhook Endpoint

The Phoenix app exposes a webhook endpoint that GHL calls for inbound events:

POST /api/webhooks/ghl
Headers: x-ghl-signature: <HMAC-SHA256 signature>
Body: { "type": "ContactCreate", "locationId": "...", "data": { ... } }

• Verify webhook signature using the Private Integration’s webhook secret (HMAC-SHA256 of request body)
• Return 200 immediately; process payload asynchronously via Oban job
• Store raw webhook payloads for debugging (7-day retention, then auto-purge)
• Register webhook subscriptions programmatically via POST /webhooks with desired event types

Subscribed webhook events: - ContactCreate, ContactUpdate, ContactTagUpdate, ContactDndUpdate - OpportunityCreate, OpportunityStageUpdate - AppointmentCreate, AppointmentUpdate (includes show/no-show) - ConversationMessage (inbound replies) - FormSubmission - NoteCreate

B.11 Custom Fields Setup

The following custom fields should be created in GHL during initial setup (one-time, via API or GHL admin UI):

B.12 Phased GHL Rollout

Not all of the above needs to ship at once. Recommended implementation order:

Phase 1 (MVP — launch with Westlake Select): - Platform → GHL: Visitor creation with tags + custom fields - Pipeline: Visitor-to-Member with basic stages (Registered → Visited → Application → Member) - Workflows: Visitor welcome, meeting reminder, post-visit follow-up - Webhooks: Contact replied, appointment booked

Phase 2 (after Westlake proves out): - Bidirectional member sync (engagement scores, profile data as custom fields) - Event-driven workflow triggers (engagement drop → re-engagement; seat claimed → recruiter drip) - Appointment booking for visitor intro calls - Conversation visibility in admin dashboard

Phase 3 (scale to metro): - Full workflow library (seat reopened, quarterly engagement reports, monthly chapter digest) - Campaign analytics surfaced in platform dashboard - Cross-chapter event announcements via GHL - Advanced pipeline analytics (conversion rate by acquisition channel, by chapter, by seat category)

Appendix C — Charlotte Metro BNI Chapter Landscape

Identified Chapters (29)

Concord / Cabarrus (5 min from home base): Cabarrus Referral Links, University Morning Breadwinners

Mint Hill (25 min): Mint Hill Breakfast Champions

Charlotte Uptown / SouthEnd (25 min): Center City, SouthEnd, Uptown Charlotte

Lake Norman / Huntersville / Mooresville (30–35 min): Cornelius Action Alliance, Morning Pacesetters, Professional Connections, Mooresville Winner’s Circle

Charlotte SouthPark / South (30–35 min): Business Links, South Park Producers, SouthPark Power Lunch, Charlotte Business Partners, Charlotte Champions, Strategic Partners, Waverly Business Connection

Charlotte Ballantyne (40 min): Providence Business Partners, Ballantyne @ 9, Ballantyne Business Network

Belmont / Cramerton / Gastonia (45–55 min): Business Builders, Networth Network, Referrals Unlimited

Fort Mill / Rock Hill SC (50–55 min): Fort Mill Business Connections, Olde English Networkers

Hickory / Foothills (65 min): Catawba Valley Business Builders, Foothills Referral Network, Unifour Success Network

Shelby (70 min): Shelby

Gap Areas (No Chapter Found)

• Kannapolis — 10 min from Concord
• Salisbury — 25 min from Concord
• Statesville — 40 min from Concord
• Waxhaw / Indian Trail / Matthews / Monroe — may be under a different BNI region or newly forming

Key Relationship Targets for Early Adoption

1. Waxhaw — Strong leadership team, go-getter culture, existing relationships with VP and marketing lead
2. Concord chapters — Closest to your home base, easiest to visit regularly
3. Ballantyne chapters — High-activity area, multiple chapters, likely strong business owners
4. Fort Mill — Growing area, SC border captures different market

This document is a living plan. It will be updated as the platform develops and as we learn from the Westlake Select founding deployment.

Appendix D — Member Recruitment Playbook

This appendix captures the operational playbook for recruiting new members into BNI chapters. The platform (§6) automates and scales many of these workflows, but the human tactics remain essential.

D.1 Direct Outreach

• Alignable & LinkedIn scripts — Source from marketing contact; adapt UK scripts for local market. Store in the platform’s shared file repository (Beacon CMS resource page or chapter admin section).
• Facebook recommendation mining — Post “looking for a great [trade]” → engage every respondent → invite to visit. The platform’s Social Boost system (§6.6) formalizes this.
• Cold outreach to local businesses in open seat categories — use the Seat Management system (§6.2) to generate a list of open seats per chapter, then target LinkedIn/Facebook profiles matching those professions.
• Invite cold sales emailers and LinkedIn pitchers — Instead of deleting, invite them to visit your chapter. They’re already prospecting; BNI gives them a better system.
• Invite your vendors and suppliers — People you already do business with are pre-qualified referral partners.

D.2 Cross-Chapter Visits

• Visit one other Charlotte-metro chapter per week (see companion bni-chapter-visit-schedule.md and bni-chapter-visits-charlotte-metro.ics for the 29-chapter, 48-week rotation)
• Goals of each visit:
  1. Build relationships with members in complementary seats
  2. Identify prospects on the fence — connect them with the cross-chapter directory (§6.3) to find a peer in their profession willing to talk
  3. Pitch the platform and cross-chapter collaboration model
  4. Log visit in the platform’s visit tracking feature
• Visit log fields: Chapter visited, date, contacts made, follow-ups needed, open seats identified, interest level in platform adoption

D.3 Visitor Strategy

• Bring guests to chapters where their seat is open (not just your own)
• “You’re the guy until they get the guy” — visitors fill a gap and get a taste of BNI simultaneously
• Track visitor → member conversion rate in the platform (§6.5)
• The platform’s Go High Level integration (Appendix B) automates the post-visit follow-up sequence that historically falls through the cracks

D.4 Social Proof & Content

• Record short video testimonials during 1-on-1s and after successful referrals
• Organize a quarterly content day — rent a small studio or use a member’s office; batch-record intro videos, testimonials, and social clips for all participating members (~$50/person split)
• Post consistently: educational → engagement → promotional cadence
• Teach members to use AI tools to draft posts in their own voice
• Platform integration: Content library managed via Beacon CMS (§6.8), member spotlight posts auto-generated from profile data

D.5 Seasonal Campaign Coordination

From the Bryan planning conversation: coordinate per-seat seasonal campaigns across chapters. Example:

• Medicare enrollment season: All Medicare specialists across participating chapters get a coordinated social media push. Every chapter member knows to boost their Medicare person. The peer forum (§6.4) shares what’s working. The platform tracks engagement.
• Tax season: All CPAs and bookkeepers get coordinated referral focus in Q1.
• Spring home season: Roofers, remodelers, landscapers, painters get coordinated push.

The platform’s peer forums and engagement scoring make this operationally feasible. Without the platform, this level of coordination is impossible across 29 chapters.

Appendix E — Chapter Operations & Communication Workflows

These are the day-to-day operational patterns that each chapter should run, supplemented by the platform and Go High Level integration.

E.1 Event Registration & Reminders

• BNI’s built-in chapter page handles official meeting registration — use it as the primary registration path rather than rebuilding this
• The platform supplements with:
  • Visitor registration that feeds directly into Go High Level for automated follow-up (§6.5)
  • Automated text + email reminders the day before each meeting (via Go High Level SMS/email campaigns)
  • Calendar feed — Nextcloud CalDAV for live two-way sync (see §E.2); static .ics exports remain available for members who prefer one-time imports

E.2 File Sharing & Resource Library

Two systems serve different file needs. The boundary is simple: published content goes in Beacon CMS; working files go in Nextcloud.

Beacon CMS (Published Content — Read-Mostly)

Content pages that members and visitors consume but don’t collaboratively edit:

• Education Moment scripts and presentations (published library)
• Blog posts, member spotlights, success stories
• “How to join BNI” guides and visitor info pages
• Landing pages for events and marketing campaigns
• Resource pages with embedded links, videos, and downloads

Beacon CMS pages are managed by platform admins and chapter content contributors through the Phoenix app’s admin interface.

Nextcloud (Working Files — Read/Write/Collaborate)

Living documents, templates, and files that members actively create, edit, share, and sync:

• Recruitment scripts (LinkedIn, Alignable, in-person, Facebook) — editable templates members customize
• Marketing templates and brand assets (logos, flyers, social media graphics, Canva source files)
• Meeting agendas and minutes — collaboratively edited before/during/after meetings
• Power Team meeting notes — shared within Power Team groups
• GAINS Exchange worksheets — blank templates members download or fill in
• Visitor Experience Checklists — working documents updated by leadership
• Stack Day planning docs — target professions, Bulldog assignments, invitation tracking sheets
• One-sheet explainers — Word/PDF templates chapters can customize with their own branding
• Photo/video uploads — content day raw footage, member headshots, event photos (uploaded directly from mobile)
• Seasonal campaign materials — working drafts shared across chapters in the peer forums

Nextcloud Folder Structure

/BNI Charlotte Metro/
├── _Metro-Wide/                    ← Shared across all chapters
│   ├── Brand Assets/
│   ├── Recruitment Scripts/
│   ├── Education Moments Library/
│   ├── Event Materials/
│   └── Seasonal Campaigns/
│       ├── 2026 Medicare Enrollment/
│       ├── 2026 Tax Season/
│       └── 2026 Spring Home/
├── Westlake Select/               ← Per-chapter folders
│   ├── Meeting Agendas & Minutes/
│   ├── Member Photos & Videos/
│   ├── Power Teams/
│   │   ├── Home Services/
│   │   └── Financial/
│   ├── Stack Day Planning/
│   ├── Leadership/               ← Restricted to chapter officers
│   └── Onboarding/
├── Waxhaw/
│   └── ...
└── [Additional chapters]/

Nextcloud Permissions Model

Nextcloud Mobile Workflow

Key use case: a member is at a networking event, meets a potential BNI candidate, snaps a photo of their business card → uploads directly to [Chapter]/Onboarding/Prospects/ via the Nextcloud mobile app → leadership sees it immediately. No “I’ll email it later” friction.

Other mobile workflows: - Upload content day photos/videos from phone immediately after recording - Access recruitment scripts while on a sales call - Review meeting agenda on the drive to the meeting - Share files via Nextcloud link in WhatsApp/SMS without attachment size limits

Nextcloud Calendar Integration (CalDAV)

Nextcloud’s CalDAV server provides live two-way calendar sync that static .ics imports cannot:

• Chapter meeting calendar — Members subscribe once; any schedule changes (location, time, cancellation) automatically propagate to their phone/desktop calendar app
• Cross-chapter visit calendar — Evolves from the current static .ics file to a live-updating shared calendar
• Stack Day schedule — Shared calendar with target professions and Bulldog assignments
• Power Team meeting schedule — Per-team recurring events
• Metro-wide events — Lunch & learns, content days, education events visible to all subscribed members

Members subscribe via any CalDAV client (Apple Calendar, Google Calendar, Outlook, Thunderbird) — no app installation required beyond the Nextcloud mobile app they already have for files.

Each chapter gets its own resource section. Shared metro-wide resources are available to all participating members.

E.3 WhatsApp / Social Boost Workflow

The original WhatsApp workflow evolves into the platform’s Social Boost system (§6.6):

Current (manual): 1. Member sees a Facebook recommendation request 2. Screenshots it → posts to chapter WhatsApp group 3. Members go to Facebook and comment recommending the relevant BNI member 4. No tracking of who participated

Platform-enabled: 1. Member posts the link and a brief description to the Social Boost queue 2. All participating members across chapters see pending boost requests 3. Members click through, recommend, and mark it done 4. Platform tracks reciprocity — members who never boost others don’t get their own requests prioritized 5. Engagement scoring (§6.7) captures participation automatically

E.4 Meeting Metrics Pipeline

Currently: PALMS data lives in BNI Connect. Chapter presidents manually review it.

Platform-enhanced: 1. After each meeting, chapter leadership enters key metrics into the platform: attendance, referrals passed, TYFCB, visitors, 1-on-1s completed 2. Platform auto-generates the weekly summary 3. Go High Level pushes the summary email to all chapter members and all past visitors from the last 12 months 4. Past visitors see the buzz and feel FOMO — drives re-engagement 5. Metro-level dashboard aggregates across all participating chapters

Appendix F — Key Patterns & Habits for Members

These recurring practices support everything the platform enables. They should be taught during onboarding and reinforced in Education Moments.

During 1-on-1s: - Record a short video recommendation for each other; post it to social media - Complete the GAINS Exchange worksheet: Goals, Accomplishments, Interests, Networks, Skills - Discuss which open seats you could each help recruit for

After 1-on-1s or referrals: - Leave a Google / Alignable review for each other - Log the referral in the platform (feeds engagement scoring)

On Alignable: - Connect with and review anyone you meet through the network

On social media: - When a chapter-mate shares a referral request, boost it immediately (via platform Social Boost or manually) - When you see a recommendation request on Facebook for a service a BNI member provides, share it to the platform’s boost queue - Your comment on a recommendation post lives forever in the search history — long-term value

At meetings: - Tag someone in a live social post asking for a referral — do it from the table - If a visitor is present, connect them with a member in their contact sphere during the networking period

Weekly platform engagement: - Check the Social Boost queue — respond to at least 2 pending requests - Post or reply in your seat’s peer forum - Review any visitor follow-up tasks assigned to you

Appendix G — Research-Based Best Practices for Chapter Growth

The following recommendations are drawn from BNI’s official content (bni.com blog, the Official BNI Podcast with Dr. Ivan Misner, BNI Connect support documentation), regional director playbooks, and experienced chapter leaders. They inform the platform’s design and should guide chapter operations.

G.1 — The Math: Why Chapter Size Matters

BNI Connect data shows a near-linear relationship between chapter size and income generated per member per week:

(Source: BNI Podcast Episode 921 — “Why Time and Chapter Size Matter”; Episode 72 — “Generating More Referrals”; Episode 239 — “Bigger Is Better”)

Key takeaways: - Critical mass is ~20 members — that’s where referral momentum begins. - 30–40 is the power zone — contact spheres fill up, Power Teams form, and one referral often becomes two or three. - Chapters of 40–50 pass 2–3x the referrals and generate 2–3x the revenue per member compared to chapters of 15–18. - The jump is not just proportional; it’s geometric because of Power Team effects and filled contact spheres.

Platform integration: The platform’s admin dashboard (§6.9) will display these benchmarks alongside real chapter data, making the case concrete for every chapter leader.

Action for Westlake Select: Use these numbers in Education Moments and when pitching visitors. “Going from 17 to 40 members isn’t just about more people — the data says each of you will generate roughly 2.5x more closed business per week.”

G.2 — Growth in Surges, Not Sprints

BNI’s chapter lifecycle research shows that trying to go from 15 to 40 in one push overwhelms members. Instead:

1. Set incremental goals: aim for +2–3 net members per month, or +3 new members every 6 weeks.
2. Surge → Assimilate → Surge: add a batch of members, then take 2–3 weeks to onboard them (1-on-1s, Passport to Success, Power Team introductions), then push again.
3. Sequential Stack Days work well for this rhythm — each surge targets a specific open seat category.

(Source: BNI blog — “Chapter Goal Setting for Leadership Teams”; “Leadership Teams — Do You Understand Your Chapter’s Lifecycle?”)

Action for Westlake Select: Frame the goal as 6 surges of 3–4 members each, with onboarding pauses between them. Track net membership monthly (new members minus attrition).

G.3 — Grow Strategically with Contact Spheres and Power Teams

Dr. Misner’s core insight: growth is a tool, not the goal. The purpose of adding members is to strengthen contact spheres so every member has equal referral opportunity.

• A contact sphere is a group of non-competing professions that serve the same clients (e.g., wedding: florist + caterer + photographer + travel agent + DJ).
• A Power Team is a contact sphere in action — members who have committed to actively generating referrals for each other, meeting at least biweekly.
• Chapters with 3–4 active Power Teams generate substantially more referrals than average.
• When deciding who to recruit, ask: “Which new seat would create or strengthen a Power Team?” — not just “who’s available.”

(Source: BNI Podcast Episodes 151, 272, 593, 775; Ivan Misner — “Target Markets, Contact Spheres, & Power Teams”)

Platform integration: The Seat Management system (§6.2) will include Power Team mapping — visualize which contact sphere clusters are complete vs. have gaps, and prioritize recruitment for gap seats.

Action for Westlake Select: 1. Map current members into contact sphere clusters. Identify which clusters have gaps. 2. Prioritize recruitment for seats that complete or strengthen a cluster. 3. Stand up 2–3 formal Power Teams with biweekly meetings and a simple agenda: “I Have / I Need / I Will.” 4. Show visitors which Power Teams they’d slot into.

G.4 — Stack Days / Focused Invite Days

A Stack Day is a regular meeting where every member invites someone from one specific profession — the goal is to interview multiple candidates for that open seat and pick the best fit.

Best practices from BNI Greater Los Angeles, Hawaii, and Heartland regions:

1. Pick 2–3 target professions, plus 1–2 backups.
2. Assign “Bulldogs” — 1–2 members with strong personalities who call everyone 2 days before and again the day before to confirm invitations were made.
3. Use the GRIP invitation framework:
   • Grow — “Would you like to grow your business?”
   • Referrals — “Through referrals?”
   • Introductions — “Let me make some introductions for you.”
   • Place — “At [day/time/location].”
4. It takes ~10 invitations to get 1 visitor. If you want 3 candidates for a seat and have 17 members, each member needs to make ~2 calls.
5. Make every meeting a focused invite day until you hit target membership.
6. Let visitors know you’re interviewing for the seat — this creates healthy scarcity.

(Source: BNI4Success — “Use Stack Days to Grow Your BNI Chapter”; BNI Heartland — “Successful Stack Day”; BNI Podcast Episode 572 — “Focused Invite Days”)

Platform integration: The platform can track Stack Day targets, invitations made, visitors arrived, and applications per event.

Action for Westlake Select: Schedule one Stack Day per month targeting the highest-priority open seat from the contact sphere analysis. Assign two Bulldogs. Track invitations made vs. visitors arrived vs. applications submitted.

G.5 — Visitor-to-Member Conversion

Getting visitors in the door is only half the battle. BNI Education Slots expert Darren Jamieson identifies three feelings a visitor must experience to apply:

1. Desire — They see real value. Showcase success stories, mention specific referral and TYFCB numbers, and have members engage warmly (not perfunctorily).
2. Scarcity — They understand that each seat is exclusive: one member per profession. If their seat is open, it won’t be forever.
3. Urgency — Give them a reason to act today. “We have two other [profession] candidates coming next week” or “Applications from today’s meeting are reviewed this week.”

Additional conversion tactics: - Drop “visitor orientation” language — it sounds bureaucratic. Call it “a quick intro to how the meeting works.” - Address the visitor directly during the meeting: connect BNI benefits to their specific profession. - Assign a visitor host buddy (not just the formal Visitor Host role) — a member in their contact sphere who sits with them, answers questions, and follows up within 48 hours. - Send a handwritten thank-you card after the visit regardless of whether they apply.

(Source: BNI Education Slots — “How to Transform BNI Visitors into Engaged Members”; BNI blog — “5 Best Practices for Inviting Visitors”)

Platform integration: The visitor pipeline (§6.5) automates the post-visit follow-up via Go High Level. The platform can also auto-assign a visitor host buddy based on contact sphere match.

Action for Westlake Select: Brief the Visitor Host and all members before any Stack Day. Create a simple “Visitor Experience Checklist” and walk through it at a Chapter Success Meeting.

G.6 — New Member Onboarding (The First 90 Days)

BNI’s own data shows that members who don’t feel connected in their first 90 days are significantly more likely to drop. The formal program is the Passport to Success, paired with the Member Success Program (MSP) training.

Critical onboarding steps: 1. Assign a Mentor Coordinator immediately. They pair the new member with a mentor and track progress through the Passport to Success. 2. Complete MSP within 30 days — this is foundational training on referrals, 1-on-1s, and the BNI system. Available online via BNI Business Builder. 3. Schedule 1-on-1s with 10 key members in the first 60 days — prioritize members in the new person’s contact sphere and Power Team. 4. Use the GAINS Exchange worksheet at every 1-on-1: Goals, Accomplishments, Interests, Networks, Skills. 5. BNI Connect mentoring program sends automated weekly emails for 8 weeks guiding both mentor and mentee. 6. Quarter-the-new-members event — some regions invite all new members (and their partners) to a casual networking evening each quarter to build community.

(Source: BNI member resources pages; BNI Podcast Episode 841 — “Member Retention”; BNI Connect — “Assigning a Mentor/Mentee Pair”)

Platform integration: The platform can track new member onboarding milestones (MSP completion, 1-on-1s scheduled, mentor assigned) and surface alerts when someone is falling behind.

Action for Westlake Select: Ensure every new member gets a mentor within their first week. Add “New member 90-day check-in” to the Membership Committee’s recurring agenda. Consider hosting a casual social each quarter for members who joined in the last 3 months.

G.7 — Addition by Subtraction (Pruning)

A counterintuitive but well-documented BNI principle: removing disengaged members accelerates growth.

• If 25%+ of members regularly miss meetings, the chapter is in trouble regardless of headcount.
• Disengaged members drag down energy, reduce referral quality, and signal to visitors that the chapter isn’t serious.
• The PALMS report (Present, Absent, Late, Medical, Substitute) and the CATS score (Chapter Accountability Tracking System) are the objective measures.
• Enforce attendance policies: more than 3 absences in a rolling 6-month period should trigger a Membership Committee conversation.
• “The way to grow a healthy chapter is to get rid of the members who don’t show up or don’t participate.” — Dr. Ivan Misner

(Source: BNI blog — “Addition by Subtraction: When Less is More”; BNI Podcast — Accountability tag)

Platform integration: Engagement scoring (§6.7) extends BNI’s PALMS with platform-specific metrics. Members below threshold lose Social Boost and forum access — the same pruning principle applied to the digital ecosystem.

Action for Westlake Select: Before aggressively recruiting, review the current roster. Are all 17 members engaged? If 2–3 are not, have the Membership Committee hold caring but honest conversations. Opening a classification held by a disengaged member may be the fastest path to a productive replacement.

G.8 — The Power of One (Minimum Engagement Standard)

BNI’s Power of One is the baseline commitment that makes everything else work:

• 1 meeting attended per week (100% attendance target)
• 1 referral given per week
• 1 1-on-1 per week
• 1 visitor brought per month
• 1 CEU (Continuing Education Unit) recorded per week

If every member in a 20-person chapter achieved Power of One, the chapter would receive 20 referrals per week and 20 visitors per month. That alone would fuel rapid growth.

Platform integration: The engagement scoring system (§6.7) is the digital extension of Power of One. Platform activities (forum posts, social boosts, visitor referrals) add to the member’s contribution score.

Action for Westlake Select: Make Power of One the chapter’s mantra. Report on it weekly in the VP report. Celebrate members who hit it consistently. Gently coach those who don’t.

G.9 — Using the PALMS Report as a Chapter GPS

The PALMS report tracks: Presence, Absences, Lates, Medical/Managed absences, and Substitutes — plus referrals given/received, 1-on-1s, visitors, TYFCB, and CEUs.

Best practices: - Review PALMS weekly in the VP report — not just attendance, but referral and 1-on-1 trends. - Use the Chapter Traffic Light system (Green/Yellow/Red/Grey) to benchmark against other chapters in the region. - Export the “Classifications Not In Chapter” report from BNI Connect to identify high-demand open seats in your region — this directly feeds recruitment priorities. - Monthly Chapter Success Meeting: deep-dive into PALMS, adjust goals, assign action items.

(Source: BNI Connect Support — “Summary PALMS Report”; BNI blog NZ — “The ABC of PALMS Reporting”; “PALMS in BNI — What Do All the Acronyms Mean?”)

Platform integration: The admin dashboard (§6.9) mirrors and extends PALMS with platform-specific data. The “Classifications Not In Chapter” report is built natively into the Seat Management system (§6.2).

Action for Westlake Select: If not already running monthly Chapter Success Meetings, start. Use PALMS data to set specific, measurable goals.

G.10 — Recruiting from Social Media and Everyday Interactions

Several top BNI recruiters share repeatable tactics:

1. “Visitor Queen” Christine Cheng’s method (200+ visitors, 52 sponsored members): Post to social networks: “In search of a [profession] that covers [area] and can take on referrals.” Follow up with every recommendation. Also: instead of deleting cold sales emails and LinkedIn pitches, invite the sender to visit your chapter.
2. Darren Jamieson’s social media targeting: Identify members of the target profession on social media in your chapter’s city. Mention existing members in their contact sphere in your post to make it relevant.
3. The “birthday party” invitation (Shawn Yesner): Keep it simple — “Hey, I’m meeting with 20 of my referral partners next [day]. Can you join us?” Don’t try to explain BNI in detail; let them experience it.
4. Lady’s/Gentleman’s Day or diversity-focused invite days — if your chapter skews heavily one way, dedicate a Stack Day to inviting underrepresented demographics. It opens new referral networks.
5. Invite your vendors and suppliers — people you already do business with are pre-qualified referral partners.

(Source: BNI Podcast — Visitors tag, Christine Cheng episode; BNI blog NZ — “How Do You Grow Your Chapter Quickly and Efficiently?”)

Platform integration: The Social Boost system (§6.6) is the digital infrastructure for tactics #1 and #2. Recruitment script templates stored in the CMS resource library (§6.8).

Action for Westlake Select: Add a “social media invite template” to the shared drive. Have the Education Coordinator run a 3-minute slot on one of these tactics each month.

G.11 — Key BNI Resources to Leverage

These are official resources chapters should be actively using:

G.12 — Recommended BNI Podcast Episodes

For Education Moments, leadership team prep, or personal development:

Appendix H — BNI Seat Classifications Reference

Full classification list: See companion document bni-professional-classifications-full-list.md.

• Source: BNI Global, LLC official Professional Classifications list (updated 11/23/2020) — the most recent publicly available comprehensive taxonomy
• 27 industries, ~290 named classifications, plus a “Specialist:” custom slot and an “(Other)” catch-all per industry
• 27 most common professions flagged with ★ — prioritize recruiting for any your chapter is missing
• The platform’s Seat Management system (§6.2) will be seeded with this taxonomy. Each chapter configures their own seat selections and splits on top of it.

Additional live data: BNI Connect’s “Classifications Not In Chapter” report compares your chapter’s filled seats against regional popularity in real time. Use it alongside the platform’s built-in seat gap analysis.

Plain text copy/paste version: See bni-classifications-simple-list.txt for manual tracking and note-taking.

Note: BNI has been gradually updating classifications as members renew. Check with your Director Consultant for any additions since November 2020.

This document is a living plan. It will be updated as the platform develops and as we learn from the Westlake Select founding deployment.