top of page
Business & Enterprise
Collaboration & Productivity
Collaboration Software
Campfire
Re-entered team chat by rejecting subscription SaaS in favor of a simple, self-hosted, open-source product, appealing to organizations that value data control and predictable ownership over Slack’s breadth and Microsoft Teams’ suite lock-in.
1
MODEL
BUSINESS MODEL
Open Source Commercialization
- Campfire launched in 2006 as a persistent, business-oriented real-time chat room, deliberately moving away from an initial idea of $5-per-event temporary chats. [238][233] - 37signals operated it as part of a broader suite alongside Basecamp, Highrise, and Backpack, then deprioritized it in 2014 to focus on Basecamp. [239][240] - In 2024, it rebuilt Campfire as a self-hosted group-chat system sold once for $299, including source code and at least three years of bug and security fixes. [235][241][236] - It simplified the product around rooms, DMs, mentions, file sharing, search, bots, and mobile PWA support rather than competing on Slack’s feature breadth. [235][237] - In 2025, 37signals open-sourced Campfire under MIT, shifting from license revenue toward ecosystem, credibility, and ONCE infrastructure value. [235][242][243]
1. Identify a workflow where buyers dislike recurring subscription costs, data residency risk, or vendor dependency. 2. Build a deliberately narrow product that performs the core job reliably rather than matching a category leader’s breadth. 3. Package the software for self-hosting with a simple installation path and clear ownership terms. 4. Monetize through an upfront license, support, managed hosting, or adjacent infrastructure—not perpetual seat fees. 5. Open-source selectively when community adoption, trust, or distribution creates more value than license revenue. 6. Keep the product maintainable with a small surface area; open source does not remove the cost of security and compatibility. The common mis-build is giving away software without a credible path to support, updates, or adjacent revenue.
DISTRIBUTION MODEL
37signals launched Campfire in 2006 as a hosted real-time group-chat product, later stopped selling it to new customers as it focused on Basecamp, then relaunched it in 2024 under the ONCE line as a $299 self-hosted, one-time-purchase product. In 2025, it made Campfire free and open source under MIT. [233][234][235][236][237]
HOW THEY BUILT IT
HOW TO ARCHITECT IT
Community-Led, Developer/API-Led, Direct Sales, Content Marketing
HOW THEY OPERATIONALIZED
HOW TO REPLICATE WHAT WORKED
dm
- 37signals used its own audience, blog, and founder social channels to announce Campfire’s ONCE relaunch. [241][236][244] - GitHub distribution made the source code inspectable and attracted self-hosting, developer, and open-source communities. [235][245][246] - The ONCE CLI and one-command installation reduced the technical barrier to self-hosting. [235] - Positioning against Slack and Teams targeted buyers seeking simplicity, ownership, and lower long-term chat costs. [235][236][247]
What worked: Use a strong founder brand and open-source credibility to reach buyers who are already skeptical of subscription software and vendor lock-in. Trap if copied blindly: Open-source distribution without installation simplicity or a support model attracts technical hobbyists but not paying organizations; it fails when self-hosting burden exceeds the buyer’s willingness to operate software.
| PATTERNS OF THIS MODEL
PATTERNS IN OPEN-SOURCE COLLABORATION SOFTWARE: 1. OWNERSHIP IS THE DIFFERENTIATOR. Self-hosting appeals when data control, compliance, cost predictability, or vendor independence outweighs convenience. 2. SIMPLICITY CREATES A DISTINCT BUYING REASON. A smaller feature surface can win buyers overwhelmed by enterprise chat platforms. 3. OPEN SOURCE SHIFTS VALUE TO ADJACENT LAYERS. When the application is free, monetization must come from hosting, support, enterprise controls, or infrastructure. THE WEAKNESS: Open-source collaboration tools can struggle to convert community adoption into revenue because the core product is freely copyable and self-hosting removes recurring billing.
What companies with this model reveal
| OPPORTUNITY INTELLIGENCE
GOLDMINE 1 — SELF-HOSTED AI WORKSPACES. Organizations want AI assistance without sending sensitive chat and document data to third-party clouds; the gap is local or private-cloud AI that works within an owned collaboration environment. GOLDMINE 2 — COMPLIANCE-READY TEAM COMMUNICATION. Regulated organizations need retention, audit, e-discovery, and access controls without adopting a full enterprise suite; a focused, self-hosted communication layer can serve this need. GOLDMINE 3 — OWNED COLLABORATION STACKS. The opportunity is bundling chat, docs, tasks, and file sharing into a self-hosted alternative for organizations that want to exit per-seat SaaS. THE PIT — FEATURE DEFICIT VERSUS SLACK. A simple chat tool may attract idealists but lose teams that rely on workflows, integrations, search, threads, and enterprise administration. THE SECOND PIT — OPEN-SOURCE REVENUE GAP. Making the core product free removes the most direct monetization path unless the company sells hosting, support, enterprise features, or infrastructure. MOVE WITH CAUTION — Do not launch an open-source chat tool expecting broad enterprise conversion from community adoption alone; Slack and Teams benefit from suite distribution, integrations, and organizational habit, while self-hosted tools require operational capability from the buyer. [235][242][236][237][247]
Untapped Business Model / Gaps / Goldmines / Pits
Patterns & Insights
2
MARKET
mkt mt es
Campfire competed against Slack and Microsoft Teams, both of which have far larger distribution, integration ecosystems, and enterprise adoption. Its counter-position was a simple, self-hosted, open-source chat system with no subscription and full customer control. [235][236][247]
MARKET TYPE
Red Ocean
ENTRY STRATEGY
Brownfield Entry
WHY THEY WON
Team chat is a mature red ocean dominated by Slack and Microsoft Teams, with Google Chat and open-source alternatives also present. The structural opening was buyer fatigue with per-seat pricing, data residency, and feature complexity. Campfire attacked by reframing the purchase from “which chat platform has the most capabilities?” to “who should own the communication system and its data?” Its simplicity, one-time ownership, and open-source code created a distinct decision criterion. The transferable lesson is that a challenger against a suite incumbent should change the ownership and cost model, not attempt feature parity. [235][236][247][248]
EXECUTION
Campfire re-entered by replacing or complementing existing Slack and Teams deployments for organizations seeking self-hosting and subscription independence. It rebuilt a 2006 product for modern infrastructure and packaged it for one-command installation on the customer’s server. The critical bet was that enough organizations would accept operational responsibility in exchange for data ownership and predictable cost. This required a simple installer, stable core functionality, source-code access, and a credible maintenance commitment. The approach would fail where teams depend on Slack’s integrations, workflows, or enterprise ecosystem, or where they lack the capability to operate their own chat infrastructure. [235][241][236][247]
FOOTHOLD STRATEGY
Beachhead Strategy
Campfire’s beachhead was technical teams, developers, and self-hosting-oriented organizations already comfortable running their own infrastructure. The pain was subscription cost, data control, and vendor dependency; these buyers were reachable through GitHub, founder channels, and self-hosted communities. From there, Campfire could expand to privacy-sensitive and cost-conscious organizations seeking an owned communication stack. [235][245][236][237]
GROWTH CAMPAIGN
CAMPAIGNS THAT WORKED
SO WHAT: Campfire’s launch converted a product decision into an ideological and economic choice: rent a feature-rich SaaS platform or own a simpler system outright. KEY LEARNING: A strong price-model contrast can create attention and differentiation even in a saturated category. HOW TO USE: If your category is dominated by subscriptions, test a clearly framed ownership alternative—self-hosted, perpetual license, or usage-owned infrastructure—but only if you can support the operational burden it creates.
KEY LEARNING
THE STANDARD: In a red ocean dominated by suite incumbents, a challenger must change the ownership model or buyer criterion rather than compete on features. RULE 1 — BUYERS ARE COST- AND CONTROL-SENSITIVE. They evaluate total cost, data residency, vendor dependency, and operational burden. RULE 2 — PRICING BECOMES A POSITIONING WEAPON. A one-time price contrasts sharply with per-seat SaaS, but must be supported by a sustainable update model. RULE 3 — SUCCESSFUL ENTRANTS SIMPLIFY. A narrow, reliable product can win buyers overwhelmed by enterprise feature sprawl. RULE 4 — FAILURE IS FEATURE PARITY. Trying to match Slack or Teams feature-for-feature is capital- and distribution-intensive. MARKET TYPE: Red Ocean (category).
gc
Market Context
| MARKET INTELLIGENCE
PATTERNS IN FOUNDER-LED OPEN-SOURCE DISTRIBUTION: 1. IDEOLOGY AMPLIFIES DISCOVERY. Anti-subscription and software-ownership narratives attract attention beyond the immediate product category. 2. GITHUB IS A TRUST AND DISTRIBUTION SURFACE. Public source code signals transparency and reaches developer-led buying processes. 3. SIMPLE INSTALLATION CONVERTS CURIOSITY INTO USAGE. A one-command installer reduces the gap between interest and deployment. 4. THE WEAKNESS: Founder-led distribution can create attention without a scalable commercial engine if the product is free and the company lacks adjacent monetization.
| MARKET ENTRY PLAYBOOK
THE STANDARD: Brownfield entry is appropriate when buyers already use a dominant SaaS tool but have a concrete reason to own or self-host an alternative. RULE 1 — Prove that subscription cost, data control, or vendor dependency is material to the buyer. RULE 2 — Make installation and operation dramatically simpler than typical self-hosted software. RULE 3 — Offer source access and a maintenance commitment to reduce perceived risk. RULE 4 — Reject this approach when the incumbent’s integrations and network habits are more valuable than ownership. [235][241][236][247]
How to enter
| FOOTHOLD STRATEGY PLAYBOOK
THE STANDARD: A beachhead strategy targets the segment most able and willing to operate the product independently. RULE 1 — Start with technical buyers who can self-host and evaluate source code. RULE 2 — Prove reliability, security, and low operational burden before expanding to non-technical organizations. RULE 3 — Expand into managed hosting or enterprise support only when demand justifies the service cost. RULE 4 — In collaboration software, a beachhead must create daily communication habit; otherwise it remains an experiment.
How to get the first strong position
MARKET PATTERNS & PLAYBOOK
3
MONEY
money rev pri
Campfire’s ONCE model initially monetized through a $299 one-time license with at least three years of fixes, avoiding per-seat subscriptions. In 2025, 37signals made Campfire free and open source, effectively ending direct license revenue and relying on the broader 37signals/Basecamp/ONCE business and ecosystem strategy. [235][236][243][237]
REVENUE MODEL
Licensing Fees, Product Sales, Service Fee
PRICING MODEL
Flat Rate Pricing, Freemium
WHY THEY WON
Campfire initially generated revenue through a one-time self-hosted license rather than recurring seats. After open-sourcing, direct product revenue became zero; potential monetization shifts to ONCE infrastructure, managed hosting, support, enterprise services, or the broader 37signals product portfolio. [235][242][236][237]
Campfire launched under ONCE at a flat $299 one-time price for self-hosted use, including source code and at least three years of bug and security fixes. It is now free and open source under MIT, eliminating the direct license fee. [235][241][236][237]
TARGET AUDIENCE
Technical teams and developers (self-hosted; want control, simplicity, and no subscription); privacy- and data-residency-sensitive organizations (self-hosted; want communication data on their own infrastructure); cost-conscious small and mid-sized teams (self-hosted; want predictable software ownership); 37signals ecosystem users (Basecamp/HEY/ONCE; want a simpler owned collaboration stack). [235][236][237][247]
CUSTOMER BUYING BEHAVIOUR
A buyer evaluates Campfire when subscription cost, data control, or vendor dependency becomes a concern. Technical evaluators inspect the code, test installation, assess server requirements, and decide whether self-hosting is preferable to Slack or Teams; purchase historically involved a one-time license rather than procurement-led subscription negotiation. [235][241][236][237]
| PRICING INTELLIGENCE
What makes this model effective & make customers pay
Buyers pay for ownership, privacy, and freedom from per-seat rent—not for another chat interface. RULE 1 — PRICE THE EXIT FROM SUBSCRIPTION. A one-time license competes against cumulative per-seat SaaS cost, not just rival software list prices. RULE 2 — SELL CONTROL AS A FEATURE. Self-hosting, source access, and data residency address procurement, security, and vendor-risk concerns. RULE 3 — MAKE THE TOTAL COST HONEST. The license may be low, but server, administration, backup, security, and upgrade costs shift to the buyer. RULE 4 — AVOID FREE WITHOUT A BUSINESS ENGINE. Once the core product is open source, the vendor needs hosting, support, infrastructure, or portfolio economics to sustain investment. The buyer is really buying software ownership and data control, proven by an IT infrastructure or software-procurement budget rather than a per-employee collaboration budget. [235][242][236][237][248]
PRICE & REVENUE
| Revenue Risk - The biggest threat to revenue stability
No recurring revenue: A one-time license creates a revenue cliff unless the company sells support, hosting, or adjacent products. Open-source commoditization: MIT licensing allows anyone to copy, modify, and host Campfire, limiting direct monetization. Incumbent gravity: Slack and Teams benefit from suite distribution, integrations, and organizational habit. Operational burden: Self-hosting shifts server, security, backup, and upgrade work to customers, narrowing the addressable buyer. Maintenance cost: Even free software requires security patches, compatibility work, and community support. Campfire was originally sold at $299 under ONCE and became free and open source in 2025; standalone revenue and ARR are not publicly disclosed. [235][242][236][243][237]
Where the model can break
4
MOTION
motion ge cs
37signals used its existing audience, founder channels, ONCE positioning, and a low-friction $299 one-time purchase to reach early self-hosting customers. Campfire was already in the hands of a few customers before broader release, and GitHub plus the ONCE CLI reduced adoption friction. [235][241][236][244]
GROWTH EXPANSION MODEL
Product Line Expansion, Ecosystem Expansion
HOW THEY EXPAND
37signals expanded Campfire from a retired SaaS product into the first ONCE product, then into an open-source self-hosted application. The expansion strategy was to use Campfire to validate the ONCE model—buy-once, self-hosted software—and to extend the 37signals ecosystem beyond Basecamp and HEY. Open-sourcing broadened distribution but shifted monetization toward the broader ONCE infrastructure and portfolio. [250][249][235][242][236]
COMPETITIVE STRATEGY
Bypass Attack
HOW THEY COMPETE
Campfire bypassed Slack and Teams’ feature-and-integration battleground by attacking their subscription and data-ownership model. It offered a simple self-hosted alternative for buyers whose primary concern was control and cost rather than ecosystem breadth. [235][236][247]
GROWTH ENGINE
GTM
Content Flywheel
Founder-led announcements create attention among buyers skeptical of SaaS subscriptions. GitHub and the ONCE CLI convert attention into installations; self-hosters share configurations, discuss requirements, and contribute to community visibility. Open-source adoption can expand awareness and credibility for the broader ONCE ecosystem, though it does not automatically create recurring revenue. The engine depends on technical usability, maintenance credibility, and a clear reason to choose ownership over convenience. [235][241][245][236][237]
Campfire’s GTM is community-led and founder-led, with a direct self-hosted purchase path rather than a conventional enterprise-sales motion. Buyers discover it through 37signals’ audience, GitHub, social commentary, and self-hosting communities; the ONCE CLI and one-command install convert interest into deployment. The commercial model initially relied on a one-time license, then shifted to open-source distribution. This requires a strong developer audience, credible maintenance, and a simple operational path; it is unlikely to work for organizations that need Slack-level integrations, compliance workflows, or managed support without a services offering. [235][241][236][246][237]
SUSTAINING MOATS
High Customer Lock-In
moat
The moat is community loyalty created by 37signals’ brand, open-source transparency, and alignment with buyers who value software ownership. Campfire’s community includes self-hosters, developers, and buyers who see the product as an ideological alternative to subscription SaaS.
| MOAT INTELLIGENCE
THE STANDARD: Open-source loyalty lasts when the community believes the vendor shares its values and maintains a usable product. RULE 1 — IDEOLOGICAL ALIGNMENT. Campfire’s anti-subscription, pro-ownership positioning attracts buyers who distrust per-seat SaaS. RULE 2 — TRANSPARENCY BUILDS TRUST. MIT-licensed source code allows inspection, modification, and self-reliance. RULE 3 — SIMPLICITY CREATES ADVOCACY. A focused product is easier to recommend than a sprawling enterprise suite. THE SIGNAL: Campfire’s GitHub repository, ONCE CLI, and self-hosting community discussions show active technical interest beyond conventional SaaS buying. The moat does not protect revenue if the community uses the free product without purchasing support, hosting, or adjacent 37signals offerings. [235][245][236][246][237]
Why this company remains defensible
ARR & TAKEAWAY
ARR Journey - what to do at each stage
PRE-$1M ARR — VALIDATE PERSISTENT CHAT. Campfire launched in 2006 as a hosted real-time chat product after rejecting a temporary $5-per-chat model. WATCH: Chat requires daily habit and reliability, not occasional event usage. $1–5M ARR — BUNDLE WITH THE 37SIGNALS SUITE. Campfire operated alongside Basecamp, Highrise, and Backpack, reaching developer and small-business teams. WATCH: A secondary product can lose investment focus when the flagship grows. $5–10M ARR — NOT PUBLICLY VERIFIED. Public sources do not disclose Campfire-specific revenue at this stage. $10–50M ARR — NOT PUBLICLY VERIFIED. 37signals deprioritized Campfire in 2014 and stopped selling it to new customers while focusing on Basecamp. $50–100M ARR — NOT REACHED AS A STANDALONE PRODUCT. Campfire was relaunched in 2024 as a $299 one-time self-hosted product, not a scaled standalone SaaS. $100M+ ARR — NOT REACHED. Campfire became free and open source in 2025, ending its direct license-revenue path. Rule: A focused product can create strong community loyalty, but a buy-once or open-source model needs an adjacent revenue engine before it can sustain standalone scale. [238][233][240][235][236][237]
COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid
THE STANDARD: Challenge a subscription-dominated category with an ownership-based alternative, but only if you can make self-hosting simple and sustain investment through an adjacent revenue engine. SEQUENCE: 1. Identify buyer frustration with subscription cost, data control, or vendor dependency. 2. Build a narrow, reliable product that performs the core job without feature sprawl. 3. Make installation, updates, and security maintenance dramatically simpler than typical self-hosted software. 4. Establish hosting, support, enterprise, or infrastructure revenue before giving away the core product. WORKED: Campfire’s $299 one-time model and open-source code created a sharp contrast with Slack and Teams; its simplicity attracted self-hosting-oriented buyers. CAUTION: Do not open-source a product without a monetization engine; do not assume technical buyers represent the broader enterprise market. Campfire’s shift to free MIT licensing increased reach but removed its most direct revenue mechanism. [235][241][242][236][237]
bottom of page