Build vs. Buy for Community Platforms: When to Invest in Custom Tooling
Jono Bacon warns against "Communication Fetishism" — the tendency to over-invest in platforms and under-invest in content. Don't build a custom community portal. Don't add a fifth communication channel. Here's the minimum tool stack for up to 100 partners, and the three triggers that justify custom investment.
The founder had spent four months and $47,000 building a custom partner portal. It had member profiles, a discussion forum, a resource library, a referral tracking system, event registration, and a gamification layer with badges and leaderboards. It was technically impressive.
Six months after launch, the portal had eleven active users. Out of thirty-eight partners.
The other twenty-seven partners were communicating in Slack — the channel they'd been using before the portal existed. They hadn't abandoned the custom tool out of spite. They'd abandoned it because it added friction without adding value. Opening a separate portal to do what Slack already did felt like extra work, not progress.
Jono Bacon coined the term "Communication Fetishism" to describe this exact pattern: the tendency to over-invest in platforms and under-invest in the content and relationships those platforms are supposed to support. Building a beautiful house doesn't help if nobody comes to dinner.
The build-vs-buy decision for community platforms isn't a technology question. It's a timing question. And the answer, for most ecosystems at most stages, is: don't build. Not yet.
The Minimum Stack for Up to 100 Partners
Five Tools, Zero Custom Development
For a community of up to 100 partners, the tool stack should be laughably simple:
Async communication: Slack or Microsoft Teams. One workspace. Not two. Not Slack AND a WhatsApp group AND a Facebook group AND a Discord server. Every additional channel fragments attention and guarantees that nobody reads everything. Pick one and commit.
Video calls: Zoom or Google Meet. For monthly partner calls, quarterly reviews, and one-on-one coaching. Nothing fancy. A calendar invite with a consistent link that partners can find without searching.
Content library: Google Drive, Notion, or a simple wiki. Methodology documents, case study templates, sales playbooks, proposal templates, and training materials. Organized by function, not by date. Partners should be able to find what they need in under sixty seconds.
Partner directory: A shared spreadsheet or your existing website. Partner names, specializations, geographies, and contact information. When a referral opportunity emerges, partners need to know who to contact — fast. The directory doesn't need to be beautiful. It needs to be accurate and current.
Event management: Calendar invites with consistent cadence. The monthly call is every first Tuesday at 4 PM UTC. The quarterly review is the second Thursday of each quarter's final month. The annual summit date is announced twelve months in advance. Predictability beats sophistication.
Total cost: effectively zero beyond the subscriptions your team likely already has. Total setup time: one afternoon. Total maintenance overhead: minimal.
This stack isn't a compromise. It's appropriate infrastructure for the stage. Using five general-purpose tools that everyone already knows how to operate is dramatically more effective than building one custom tool that requires training, maintenance, and the ongoing hope that people will actually log in.
The Three Triggers for Custom Investment
When General-Purpose Tools Actually Break
There are legitimate reasons to invest in custom tooling. But they're specific, and they don't appear until the ecosystem reaches a certain scale and complexity. Here are the three triggers — and none of them should fire before you have 100+ active partners.
Trigger 1: Coordination overhead exceeds administrative capacity. When you have 150 partners across multiple time zones and specializations, manually matching clients to the right partner takes hours per week. The spreadsheet that worked at 30 partners becomes unmanageable at 150. This is the point where automated client-partner matching — a system that considers geography, specialization, availability, and satisfaction scores — saves more time than it costs to build.
Trigger 2: Data aggregation demands centralization. When your diagnostic tool has produced thousands of assessments across multiple industries and geographies, the benchmarking data becomes a strategic asset. But extracting insights from distributed spreadsheets and isolated assessment reports is painfully slow. This is the trigger for a centralized diagnostic platform — one that aggregates all assessment data, computes benchmarks automatically, and generates industry reports that make the entire ecosystem more valuable.
Trigger 3: Partner-requested infrastructure. This is the most important trigger. When partners themselves start asking for specific capabilities — "Can we have a shared pipeline dashboard?" or "Can we see our collective referral flow?" — the demand is coming from the people who'll actually use the tool. Building for articulated partner demand is fundamentally different from building for hypothetical founder vision.
Bacon's principle applies to all three triggers: build in response to documented need, not in anticipation of imagined need. The $47,000 portal failed because it was built for a problem that didn't exist yet. The partners were perfectly functional with Slack. The portal solved the founder's anxiety about "looking professional," not the partners' need for better tools.
Custom tooling isn't wrong. Premature custom tooling is wrong. The timing matters more than the technology.
The Real Platform Investment
Where to Spend Before You Spend on Technology
The irony of the build-vs-buy debate is that the highest-value investments for community platforms aren't platforms at all. They're content and relationships.
Invest in the monthly call agenda. A monthly partner call with a thoughtful agenda — peer case study sharing, methodology deep-dive, cross-referral spotlight, open Q&A — generates more community engagement than the most sophisticated portal. Partners don't attend calls because the Zoom interface is pretty. They attend because the content is valuable and the conversation is real.
Invest in sales enablement content. Proposal templates, objection-handling guides, question libraries, pricing frameworks, email sequences for referral requests. These documents, stored in a Google Drive folder, generate more partner revenue than any community platform feature. When a partner can download a proven proposal template, customize it in thirty minutes, and send it to a prospect the same day — that's infrastructure that pays for itself.
Invest in community management. By Year 2, hire someone whose job is logistics: call scheduling, follow-up communications, metric tracking, partner check-ins, content curation. Bacon describes this as the "operational enabler" that frees the founder to focus on vision and strategy. A skilled community manager with a Slack workspace and a Google Drive is more valuable than a custom portal without one.
Invest in the annual summit. Nothing replaces in-person connection. Priestley's "Remarkable Budget" principle applies: the money you spend delighting partners at the annual gathering is the most effective community investment you can make. The relationships formed over shared meals and hallway conversations sustain engagement for the other eleven months of the year.
The build-vs-buy decision is really a prioritization decision. With limited resources, where do you get the most return? In nearly every case, the answer is: content, relationships, and community management — not technology.
Don't build a portal nobody uses. Build a community everyone values. The tools will catch up when the community demands them.