Community Building

Community Building for B2B Marketers

Overview

This skill covers community strategy, launch sequencing, platform selection, member engagement, event design, moderation, metrics, and organizational positioning for B2B communities. All practices are sourced exclusively from Exit Five podcast guests across 28 unique episodes. Where guests disagree, those disagreements are surfaced explicitly rather than resolved.

Before You Build: Foundational Questions

Distinguish Between Audience and Community

Understand that "community" exists on a spectrum. Broad community building means growing the number of people interested in a topic — this can happen through content, social media, events, and newsletters. A specific community platform (e.g., a paid Circle community) is a more defined, gated space for a specific subset of people. Both are valid, but they serve different purposes. Do not conflate the two when planning strategy. (Source: Matt Carnevale, Episode #320)

Separately, distinguish between audience (passive observers consuming content) and community (active participants who contribute, refer, and participate in exclusive experiences). Audience is the top of the funnel; community is a behavioral engagement tier below it. CMOs often conflate the two or focus only on small on-property customer forums, missing the larger audience-building opportunity. (Source: Anthony Kennada, Episode #145)

Use the TRIBE framework to evaluate whether you have a true community or just an audience. TRIBE stands for: Togetherness, Rituals, member Identity, Belonging, and Engagement. All five elements must exist for something to qualify as a community. An audience (e.g., Instagram followers) fails this test because engagement drops to zero if you stop posting. Apply this framework when evaluating new community initiatives before investing. (Source: Greg Isenberg, Episode #146)

Validate Before You Launch

Most internal company communities fail because: (1) leadership doesn't fully commit and measures success by short-term pipeline impact rather than long-term brand building; (2) the company doesn't allocate sufficient resources (full-time manager, real budget); (3) the community is treated as a marketing channel rather than a product; and (4) success metrics are misaligned. Before starting a community, ensure leadership alignment on all four points. (Source: Dave Gerhardt, Episode #320)

Most private communities (Slack groups, Circle, etc.) fail because they become spam or noise within weeks. Only launch a private community if you have clear product-market fit signals: existing audience demand, engaged members, and a specific reason members want to connect with each other — not just consume your content. If you lack these signals, focus on building broader audience and brand through content and education first. (Source: Dave Gerhardt, Episode #307)

Before launching a community, confirm that you have an existing audience that is engaged with your content and willing to join. If you lack an audience, focus on building one first through content, social, or other channels. Launching a community without an audience to funnel into it will result in a ghost town and wasted effort. (Source: Matthew Carnevale, Episode #213)

Do not launch a community if your team is under immediate revenue pressure. Community building is a long-term play that requires sustained effort and patience. If short-term results are required, focus on faster-moving channels first (sales enablement, email, paid ads) and launch community once you have a stable foundation. (Source: Matthew Carnevale, Episode #213)

Validate product-market fit for a community before going full-time. Launch as a side project (e.g., on Patreon) while maintaining other income. Look for signals like organic growth, member requests for features (e.g., "let us talk to each other"), and recurring revenue. Once you have product-market fit (e.g., 1,000+ members, $10k+ MRR) and financial flexibility, transition to full-time. (Source: Dave Gerhardt, Episode #214)

Define and align on a clear, specific goal for the community (e.g., customer support, lead generation, brand advocacy) and get stakeholder buy-in before launch. Communicate realistic timelines for success. This prevents misalignment later and helps the community manager push back on unrealistic expectations. (Source: Matthew Carnevale, Episode #213)

Rather than assuming what community should look like, directly ask customers: "What does community mean to you? Where do you want to hang out? Where can we support you?" Use their answers to inform your community strategy. (Source: Dan Cmejla, Episode #134)

Building the Audience Foundation First

Build audience as the building block of community growth. Before asking people to join a paid or free community, you need an existing audience that knows who you are and what you stand for. Grow audience first through a four-step process: develop a clear point of view, choose a platform where your customers hang out, create and post content on that platform, and analyze what works best to double down on those topics. For B2B, LinkedIn is typically the platform where customers concentrate. (Source: Matt Carnevale, Episode #233)

Use the ACP funnel — Audience, Community, Product — and build in this order: first establish an audience on a rented platform (e.g., Twitter, LinkedIn, Instagram) with niche content until you reach approximately 10,000 followers. Then convert the most engaged subset (50–100 people) into a community using scarcity tactics (waitlist, invite-only, private access). Finally, layer products on top of the community. This funnel prevents building community in a vacuum and ensures credible distribution before asking people to join a gated space. (Source: Greg Isenberg, Episode #146)

For teams without a strong founder social presence, create a standalone media asset (e.g., job board, resource library, benchmarking tool) that solves a problem for your target audience and attracts them independently. Use this asset to build an engaged audience first, then funnel them into a community later if they request it. This decouples community growth from founder brand and creates a sustainable acquisition channel. (Source: Matthew Carnevale, Episode #213)

Build community around a broader professional interest or problem that your target audience cares about — not your product. For example, instead of a "Databox Users" community, build a community for business intelligence professionals. Position your company as a steward of that conversation and knowledge domain. This attracts members who are genuinely interested in the topic and creates more authentic, valuable interactions. (Source: Dave Gerhardt, Episode #307)

When selecting a niche for your community, use the concentric circle model to understand the depth of your addressable market. The innermost circle is your core (e.g., co-founders of a product), expanding outward to employees, power users, casual users, and finally people who've never heard of it. Niching down makes your job easier, but evaluate whether the niche will remain relevant in 12–24 months. Avoid niches with short hype cycles where you risk building in a space that becomes saturated or irrelevant. (Source: Greg Isenberg, Episode #146)

Launch Strategy

Seeding and Scarcity

When launching a community, identify and recruit 3–10 recognized experts in your space and offer them free access (for a year or lifetime). Tag them in relevant member questions to encourage participation and signal to new members that quality answers are available. This prevents the common problem of communities becoming inactive shortly after launch. (Source: Matthew Carnevale, Episode #213)

When converting your audience into a community, make the community waitlist-only and private (even if free) to create scarcity and FOMO. This drives commitment and ensures you onboard only the most engaged members initially. Reference the Studio 54 model: "a dictatorship at the door, but a democracy on the dance floor" — be exclusionary at entry, but fully inclusive once members are in. This allows you to validate the community with a small, engaged cohort before scaling. (Source: Greg Isenberg, Episode #146)

Platform Selection

(Note: platform choice is contested — see Where Experts Disagree)

For paid communities, avoid Slack (per-user costs, limited search history) and Facebook (ephemeral feed, poor data access). Use a dedicated community platform like Circle that offers: persistent searchable content library, white-labeled experience, mobile app, automation/workflow capabilities, and no per-user fees. Budget $20–30k annually for the platform and hire a dedicated community manager to treat it as a core product. (Source: Dave Gerhardt, Episode #225)

When building a branded community on Reddit, assign a full-time community manager (or social media manager at enterprise scale) to manage the subreddit. Companies like Stripe and Twilio have successfully used this approach to build engaged communities and own the narrative around their product. (Source: Ross Simmonds, Episode #200)

Onboarding

During community onboarding, systematically collect information about each member's role, experience level, challenges, and expertise. Use this data to tag and surface relevant members when questions arise, creating a forcing function for engagement. This transforms passive membership into active participation by connecting members with peers who can help solve their specific problems. (Source: Matt Carnevale, Episode #320)

When transitioning a community from an engagement-focused model to a membership/access model, use the onboarding process (ideally a call with a community manager) to explicitly set expectations. Explain what the community is about and what members should expect. Members who onboard under the new model will have different behavioral expectations and will be less likely to churn. (Source: Greg Isenberg, Episode #146)

When users sign up for your product or community, ask them three questions: (1) Why did you sign up? (2) What's your role? (3) How did you hear about us? Pipe this data into a shared Slack channel so the team can see patterns in real time. Use these insights to double down on high-performing channels and topics. (Source: Dave Gerhardt, Episode #141)

Community Management and Engagement

Daily Operations

Treat community management as a full-time, always-on role. The community manager must read every post, respond to comments, and ensure that whenever a member logs in, they have a good experience. Members don't visit frequently — when they do, they need to encounter a well-maintained, responsive space. Inconsistent or part-time management will result in churn. (Source: Matt Carnevale, Episode #320)

Maintain a daily presence in the community by logging in and responding to every post and comment, even if just with brief acknowledgment. This signals to members that the community is actively managed, encourages continued participation, and helps the community manager stay aware of trends and member needs. Spend at least one hour daily on this. (Source: Matthew Carnevale, Episode #213)

Commit to daily engagement in communities where your target audience hangs out — commenting on 10–12 posts per day in a Slack community, Discord, or LinkedIn. Over time, this consistent engagement trains your brain to recognize patterns in what topics people care about most. (Source: Matt Carnevale, Episode #155)

Driving Engagement

When members post questions in the community, proactively tag relevant experts (other members or team members) who can answer. This ensures questions get answered, shows members that experts are active and responsive, and encourages future participation. Tag experts almost daily — not just monthly — to create a pattern where members see that if they ask a question, knowledgeable people will engage. (Source: Matt Carnevale, Episode #233)

Design at least one recurring monthly event or program that gives members a concrete reason to log in. Examples include expert-led teardowns (website, ad strategy, etc.) where members submit work for feedback, or automated matchmaking programs that pair members for one-on-one conversations. Align the frequency with your billing cycle so members have a reason to return each month they're paying. (Source: Matthew Carnevale, Episode #213)

Create a formal matchmaking program where members opt in monthly based on their stated challenges or interests, and the system automatically pairs them with other members who share similar roles or needs. Use a matchmaking tool (e.g., Matcha) to handle the pairing automatically. This removes friction from networking and ensures members get direct value from the community beyond passive content consumption — including members who don't actively post or comment. (Source: Matt Carnevale, Episodes #320 and #233)

Recruit community members to host and lead events rather than creating all content internally. Members raise their hand to lead sessions on topics they're expert in; you handle the logistics and promotion. This reduces your workload, increases member investment in the community, and provides consistent reasons for members to return monthly. Schedule events in advance to create predictable engagement touchpoints. Promote new events like product launches across your external channels. (Source: Matt Carnevale, Episode #233)

Regularly review your community platform's analytics to see which posts and topics generate the most engagement. Use these insights to inform both your external content strategy (e.g., LinkedIn posts) and your community programming (e.g., events). If members are asking many questions about a specific topic, create external content on that topic to attract more audience, and consider hosting a community event on it. This creates a feedback loop between community signals and audience-building. (Source: Matt Carnevale, Episode #233)

Actively monitor your community for recurring questions and discussion threads. When you see the same question asked multiple times or a thread gaining significant engagement, that's a signal that the topic is valuable to your audience. Use these signals to inform your content calendar, product decisions, and marketing priorities. (Source: Dave Gerhardt, Episode #225)

Run community events (webinars, live sessions, etc.) with your audience and pay attention to which topics generate the most engagement and discussion. Use this real-time feedback to inform your broader content strategy. If a live session topic generates lots of chat activity, create more content around that topic. (Source: Dave Gerhardt, Episode #139)

Moderation and Quality

Define the specific profile of members your community is designed for, and actively reject or remove members who don't fit that profile or have misaligned incentives. This prevents bad actors (e.g., aggressive salespeople, spammers) from degrading the community experience and maintains the trust and quality that makes the community valuable. Acknowledge that this will make some people unhappy, but it's necessary for long-term community health. (Source: Matt Carnevale, Episode #320)

Create written guidelines that explicitly address gray-area behaviors (e.g., self-promotion, thought leadership, solicitation) rather than leaving them ambiguous. Frame these guidelines around the core principle of the community (e.g., "we want people talking to each other, not at each other"). Use concrete examples to help members understand what is and isn't acceptable, reducing confusion and enforcement friction. (Source: Dave Gerhardt, Episode #320)

Eliminate dedicated spaces for self-promotion and actively remove any self-promotional content (or have members report it for removal). Self-promotion clutters the community feed and degrades the experience for members trying to find valuable peer-to-peer discussions. By removing this friction, members spend more time in the community and encounter higher-quality content, which improves retention and engagement metrics. (Source: Matt Carnevale, Episode #233)

Focus on creating an environment where members feel confident asking specific questions and receiving thoughtful answers from people they trust — even if this means lower post volume. Note: trust is difficult to measure directly; use member retention rate and qualitative feedback as proxies. (Source: Matt Carnevale, Episode #320)

Measuring Community Success

(Note: the right success metrics are contested — see Where Experts Disagree)

Measure community performance across the full funnel: new trial signups per month, trial-to-paid conversion rate, and churn rate. Additionally, measure engagement health with monthly active users (MAU) percentage, post volume, comment volume, and post-to-comment ratio. This holistic view treats community as a revenue-generating business unit. (Source: Matthew Carnevale, Episode #213)

Aim for at least 40% of your community members to have meaningful engagement (e.g., posting, commenting, attending events) at least once per month. This benchmark places a community in the top tier of performance on platforms like Circle and indicates strong overall health and member retention. (Source: Matthew Carnevale, Episode #213)

Monitor the average number of comments per post each month as a key engagement metric. A healthy ratio indicates that posts are generating discussion and members are actively engaging with each other's content. Track this ratio month-over-month to identify trends; an increasing ratio signals improving engagement quality. (Source: Matthew Carnevale, Episode #213)

Survey customers on how they first heard about your company, grouping responses into awareness channels (events, social media, community, etc.). Use this directional attribution to validate community efforts when direct attribution is difficult to track. Complement with impression metrics (LinkedIn impressions, reach) and share-of-voice measurements across competitors to demonstrate brand lift. (Source: Dan Cmejla, Episode #134)

Community as a Product

Treat community as a standalone product with dedicated ownership, a product roadmap, feature planning, and regular feedback loops. Assign a product owner/community manager, conduct NPS surveys, track engagement metrics, and hold regular community meetings to review metrics and plan iterations. This transforms community from ad-hoc content distribution into a measurable business asset. (Source: Dave Gerhardt, Episode #307; Matt Carnevale, Episode #233)

Apply product management principles to community building. Start with a hypothesis about what will improve engagement, test it with a small launch, collect feedback, and iterate. Use member feedback loops — one-on-one calls, analyzing popular posts, and direct member requests — to inform your product roadmap. Implement features that members explicitly ask for, and treat new feature launches like product launches with public promotion. (Source: Matt Carnevale, Episode #233)

If you have a large paid community, identify a specific subset of members (e.g., marketing leaders, VPs, directors) and create a separate, limited-time cohort-based program (e.g., 8-week accelerator) targeting that niche. Charge a premium price for this focused offering. This allows you to generate additional revenue from your existing community while providing specialized value to a smaller, more targeted group. (Source: Matt Carnevale, Episode #233)

As the community and company grow, gradually shift content creation and community leadership responsibilities away from the founder to other team members. Transition the newsletter from founder-written to team-written, or have other team members lead community initiatives. This reduces burnout on the founder and builds resilience if the founder becomes unavailable. (Source: Matthew Carnevale, Episode #213)

Hiring for Community

When building a community, it's more important to hire someone with deep knowledge of your audience and industry than someone with prior community management experience. A person who understands your audience can learn community management skills on the job, but a community manager without subject-matter expertise will struggle to create meaningful content and connections. The expertise is the foundation; the management skills can be developed. (Source: Dave Gerhardt, Episode #320)

Events as Community Infrastructure

In-Person Events

When planning events, add at least one activity-based session outside the conference room — a poker night, pickleball game, hike, or similar informal format. These formats facilitate genuine human connection rather than just information exchange. (Source: Kieran Flanagan, Episodes #318 and #257)

Position events as a community enabler and networking tool, not as a primary revenue source. When events are positioned as community value-adds (e.g., for existing members or customers), they become more manageable and sustainable. Revenue should come from other sources (sponsorships, memberships, media). (Source: Jason Lemkin, Episode #142)

The real ROI of an in-person event is the community and relationships built — attendees may meet people who live in their town, have kids the same age, or share deep professional challenges. These connections compound over time and drive word-of-mouth growth for future events. This is harder to measure than ticket sales but more valuable long-term. (Source: Dave Gerhardt, Episode #294)

Event Design for Connection

Design events to emphasize peer-to-peer networking and roundtables alongside talks. Include structured roundtable sessions where attendees can discuss challenges with people in similar roles, industries, or revenue tiers. The hallway conversations and informal networking are often the highest-value part of the event. Allocate time and space for this intentionally. (Source: Dave Gerhardt, Episode #147)

Have attendees fill out a form with questions about their role, interests, and challenges. Use this data to match them into small breakout groups (e.g., "all CMOs" or "all early-career marketers"). These groups don't require speakers or stage space — just an hour of facilitated peer discussion. This reduces speaker load, increases intimate connection, and often becomes one of the most valued parts of the event. (Source: Dave Gerhardt, Episode #294)

Create programming outside the conference room — excursions like pickleball, hikes, yoga, bike rides, and boat trips — that serve as "third spaces" where attendees can connect as humans rather than just professionals. These spaces are not about learning but about belonging and building genuine relationships. Morning excursions before formal programming starts can also create spontaneous bonding moments that strengthen community. (Source: Anna Vermillion, Episode #294)

Pair new/first-time attendees with experienced attendees during the first activity or mixer at an event. This helps newcomers feel welcomed and ensures they know at least one person, reducing the cliquiness that can occur in established communities. Use a simple mechanism like a hat draw or name-based matching to facilitate introductions. (Source: Sydney Sloan, Episode #289)

After an event (especially intimate dinners or VIP gatherings), create a dedicated Slack channel and invite attendees to join. Use this channel to continue conversations, share follow-up resources, and maintain relationships beyond the event. (Source: Kristina DeBrito, Episode #227)

Grassroots and Hybrid Event Strategy

After running webinars, some attendees will naturally want to meet in person and continue the conversation. Rather than forcing top-down event strategy, enable and support these grassroots efforts. Support organic community pods by providing resources, content, and light coordination, while also running larger top-down events to complement them. This creates a two-way event strategy: bottom-up community pods driven by attendees, and top-down larger events run by the company. (Source: Eoin Clancy, Episode #326)

Establish a community platform and dedicate team members to manage it and program events. Host community events for existing users to deepen engagement, gather feedback, and create advocates. These events can range from virtual meetups to in-person gatherings and serve as a lower-cost alternative to sponsored events while providing direct access to power users who can help shape product direction. (Source: Holly Xiao, Episode #270)

Creator and Contributor Programs

Create a structured creator program with multiple tiers: entry-level creators (who apply, show existing content creation on LinkedIn, and use your product), mid-tier experts (freelancers and agencies building businesses on your product), and enterprise partners (top agencies). Provide benefits including affiliate links, co-created content assets, paid ad promotion of creator profiles, and product feature access. This approach turns users into a distributed content marketing force while maintaining quality control through application requirements. (Source: Bruno Estrella, Episode #180)

When building a creator program, focus on service providers like freelancers and agencies who use your product to serve clients. These users have a built-in incentive to create content because they need it to market their own services. They're already creating content on LinkedIn and other channels — you just need to enable and amplify them. (Source: Bruno Estrella, Episode #180)

When recruiting experts to lead events, courses, or programming in your community, offer monetary compensation plus exposure to your engaged audience. Be clear about what you can offer; only recruit experts who see value in that combination. Acknowledge that your audience's relevance may substitute for conference-level fees. (Source: Matthew Carnevale, Episode #213)

Organizational Structure and Internal Positioning

Organize social media, customer marketing, field marketing, events marketing, evangelism, and PR under a single community function rather than splitting them across separate teams. This allows these functions to work seamlessly together and creates alignment around shared brand goals. (Source: Dan Cmejla, Episode #134)

Before committing to a channel strategy, survey customers on which podcasts they follow, which social platforms they use, which influencers they respect, and which events they attend. Build an influence map from this data. Use this map to determine where to deploy customer voices and company content. (Source: Dan Cmejla, Episode #134)

Where Experts Disagree

1. Should you charge for community access or keep it free?

Support summary: 3 vs 3 — evenly split

Position A: Charge for access Dave Gerhardt (Episodes #146, #225) and Greg Isenberg (Episode #146) argue that communities should charge for access. Gerhardt explicitly stated "do not build free communities" — free communities attract low-commitment members, spam, and self-promotion. He compared paid membership to a gym membership dynamic: because members are paying, they're more committed and have higher expectations. Isenberg added a structural argument: when a community generates its own MRR, leadership views it as a business unit with high margins rather than a lead generation asset to be exploited — protecting the community from internal sales pressure.

Position B: Platform and pricing model matter less than engagement Matthew Carnevale (Episodes #213, #320) and Chris Walker (Episode #139) push back on the paid-only default. Carnevale advised launching on any platform and focusing on engagement over platform or pricing model choice, noting you can migrate later. He also distinguished between broad community building (which can be free) and specific community platforms, arguing that quality curation and active management — not charging — are the real solutions to spam. Walker argued that the most successful communities grow organically from genuine passion and value creation, not from forced monetization goals, and that measuring success by repeat engagement (not revenue) is the right frame.

Context dependency: The paid model advice is most clearly aimed at standalone community products or media companies. The platform-agnostic advice may apply more to early-stage community validation. However, Gerhardt and Isenberg both argue against free communities as a general principle, making this a genuine disagreement on default approach — not just a context difference.

Why it matters: Choosing a free vs. paid model fundamentally shapes who joins, how they behave, and how the community is perceived internally. Getting this wrong can doom a community to spam or kill it before it gains traction.

2. Should you measure community success by engagement activity or by membership retention and access?

Support summary: 4 vs 2 — majority favor engagement metrics

Position A: Optimize for engagement activity (majority) Matthew Carnevale (Episodes #213, #320) and Chris Walker (Episode #139) argue that community health should be measured by active participation metrics: monthly active users (targeting 40%+), post volume, comment volume, post-to-comment ratio, and daily engagement. Carnevale recommends spending at least one hour daily responding to all posts and comments, and designing monthly engagement hooks so members have a concrete reason to return each billing cycle. Walker argues that the right question is "do people come back next week?" — not conversion or revenue metrics.

Position B: Optimize for access and yearly retention Greg Isenberg (Episode #146) and Dave Gerhardt (Episode #146) argue the opposite: stop optimizing for daily engagement metrics. Isenberg explicitly argued to shift KPI from engagement to access — optimize for yearly retention, not daily activity. He described the failure mode of chasing viral posts and engagement metrics that become unsustainable as community grows. Gerhardt recommended designing community as a resource hub optimized for searchability and reference value rather than daily discussion. A member who logs in once every 60 days but finds critical resources when needed is more valuable than a daily commenter who derives no lasting value.

Context dependency: The access/retention model may apply more to resource-library-style communities, while engagement metrics may suit peer-discussion communities. However, both sides are making general claims about what community success should look like.

Why it matters: The metric you optimize for shapes every community management decision. If you chase engagement, you may create noise; if you optimize for access, you may miss early warning signs of member disengagement.

3. Should community be built as a standalone product or can it serve as a marketing/lead generation channel?

Support summary: 6 vs 2 — strong majority favor standalone product framing

Position A: Community as standalone product (strong majority) Matt Carnevale (Episode #320), Dave Gerhardt (Episodes #320, #307), Chris Walker (Episode #139), Anthony Kennada (Episode #145), and Brian Kotlyar (Episode #118) all argue that community should be treated as a standalone product with its own manager, roadmap, and success metrics — completely separate from marketing's demand generation goals. Carnevale explicitly stated not to default to building a Slack group as a marketing tactic. Gerhardt identified that most internal company communities fail precisely because leadership measures success by short-term pipeline impact rather than long-term brand building. Walker argued that when you try to build community as a sidecar to your product, you introduce competing objectives (nurturing audience vs. converting them to customers) that undermine authenticity. Kennada argues that CMOs should treat audience and community as distinct strategic assets requiring intentional investment — not as demand generation byproducts. Kotlyar added that walled community platforms without underlying shared identity tend to die — organic identity formation is the prerequisite.

Position B: Community as business unit with funnel metrics Matthew Carnevale (Episode #213) and Andrew Davies (Episode #195) argue that community can and should be measured as a full business unit with acquisition, conversion, and retention metrics — including new trial signups, trial-to-paid conversion rate, and churn rate. Davies described running an accelerator program with community (Slack, Zoom calls) explicitly designed to acquire early-stage customers and generate a halo effect — directly using community as a customer acquisition channel.

Context dependency: The standalone product argument is strongest for media companies or communities built around a professional identity (like Exit Five). The business unit/acquisition framing may apply more to product-led companies using community to drive trials. However, both sides are making general claims about how to approach community.

Why it matters: How you frame community internally determines resourcing, metrics, and whether it survives the first quarter of disappointing pipeline numbers. This framing question is cited as the primary reason most B2B communities fail.

4. Does platform choice matter when launching a community, or should you just start anywhere?

Support summary: 2 vs 1 — slight majority favor dedicated platform for paid communities

Position A: Platform matters — use a dedicated tool Dave Gerhardt (Episode #225) argues that for paid communities, platform choice matters significantly. Avoid Slack (per-user costs, limited search history) and Facebook (ephemeral feed, poor data access). Use a dedicated platform like Circle that offers persistent searchable content, white-labeling, mobile app, and automation. Budget $20–30k annually for the platform.

Position B: Platform-agnostic — start anywhere Matthew Carnevale (Episode #213) and Brian Kotlyar (Episode #118) argue that the specific platform matters less than getting members actively talking to each other. Carnevale advised that Facebook, Slack, Circle, etc. are all acceptable starting points and explicitly said to avoid analysis paralysis on platform selection — you can migrate later as the community matures. Kotlyar argued for building community through shared identity across open channels rather than investing primarily in walled platforms, suggesting that platform is secondary to identity.

Context dependency: Gerhardt's advice is specifically for paid communities. Carnevale's platform-agnostic advice may apply more to early-stage or free communities. However, both are giving general launch advice, and the conflict is real for anyone deciding where to start.

Why it matters: Choosing the wrong platform can create technical debt, limit data access, and increase costs as the community scales — but over-engineering the platform decision can delay launch and prevent learning.

What NOT To Do

• Do not treat community as a marketing channel or lead generation tactic. If the goal is to nurture prospects or drive sales, a newsletter or social media might work better. Using community as a demand generation tool introduces competing objectives that undermine authenticity and cause most communities to fail. (Source: Matt Carnevale, Episode #320; Dave Gerhardt, Episode #320; Chris Walker, Episode #139)

• Do not launch a community without an existing engaged audience. Launching a community without an audience to funnel into it will result in a ghost town and wasted effort. Build audience first. (Source: Matthew Carnevale, Episode #213; Dave Gerhardt, Episode #307)

• Do not launch a community under immediate revenue pressure. Community building is a long-term play. If short-term results are required, focus on faster-moving channels first. (Source: Matthew Carnevale, Episode #213)

• Do not measure community success by short-term pipeline impact. This is cited as one of the primary reasons most internal company communities fail. (Source: Dave Gerhardt, Episode #320)

• Do not allow self-promotion to go unmoderated. Self-promotion clutters the community feed and degrades the experience for members trying to find valuable peer-to-peer discussions. Eliminate dedicated spaces for self-promotion and actively remove self-promotional content. (Source: Matt Carnevale, Episode #233)

• Do not hire a community manager based solely on community management experience. Subject-matter expertise in your audience and industry is more important. A community manager without subject-matter expertise will struggle to create meaningful content and connections. (Source: Dave Gerhardt, Episode #320)

• Do not manage community as a part-time or side responsibility. Inconsistent or part-time management will result in churn. Treat it as a full-time, always-on role. (Source: Matt Carnevale, Episode #320)

• Do not build a community around your product. Build it around a broader professional interest or problem your target audience cares about. Product-centric communities attract members who are less engaged and create less authentic interactions. (Source: Dave Gerhardt, Episode #307)

• Do not conflate audience with community. Audience is a broader set of passive observers; community is a subset of active participants. Treating them as the same leads to misaligned strategy and metrics. (Source: Anthony Kennada, Episode #145; Matt Carnevale, Episode #320)

• Do not build a walled community platform without first establishing a shared identity. A walled community without underlying identity tends to die. Build the identity first through open channels, then move it into a gated space if needed. (Source: Brian Kotlyar, Episode #118)

• Do not build a community in a niche with a short hype cycle. Evaluate whether the niche will remain relevant in 12–24 months before investing. (Source: Greg Isenberg, Episode #146)

• Do not scale an accelerator program too large. Paddle's second cohort of 170 founders was described as too large; the optimal cohort size was around 70. (Source: Andrew Davies, Episode #195)

Sources

Note: episode_count reflects 28 unique episode numbers. The sources table lists all guest appearances, with some episodes featuring multiple guests.