top of page
Business & Enterprise
Collaboration & Productivity
Collaboration Software
Campsite
Attempted to replace fragmented async collaboration by combining posts, docs, chat, and calls in one calm workspace, but wound down after buyer enthusiasm did not convert into daily end-user behavior against entrenched Slack, Notion, Zoom, and Google Docs habits.
1
MODEL
BUSINESS MODEL
SaaS
- Started in spring 2022 as a nights-and-weekends project to help design teams share work, gather feedback, and archive explorations. [262] - Raised a $2.6 million seed round in 2022 led by Nat Friedman, with Caffeinated Capital and Cursor Capital. [265] - Expanded from design feedback into an all-in-one communication workspace with posts, notes, chat, audio/video calls, integrations, and AI call summaries. [266][267][268][269] - Sold to design leaders and team leads through freemium, per-member subscriptions, and custom Business plans with SSO and migration support. [270] - Wound down the product in 2025 after realizing that buyer-level adoption did not translate into broad end-user daily behavior. [263][264]
1. Identify a collaboration behavior that leaders want but individual contributors do not naturally perform. 2. Validate daily user behavior before expanding from one workflow into a multi-product suite. 3. Design for the person who must change their habit, not only the manager who approves the purchase. 4. Keep the first product narrow enough to become habitual before adding adjacent communication modes. 5. Use integrations to reduce switching friction rather than asking users to abandon established tools at once. 6. Treat enterprise contracts as validation only when they produce sustained seat usage and retention. The common mis-build is selling a broad “future of work” suite before proving that one behavior creates repeatable daily value.
DISTRIBUTION MODEL
Campsite began in 2022 as a design-team tool for sharing work in progress and async feedback, then broadened into company-wide posts, chat, docs, and calls. Despite early fans and six-figure contracts, founder Brian Lovin said individual contributors did not adopt work-in-progress posting at scale; the product wound down on February 28, 2025, and its founders joined Notion. [262][263][264]
HOW THEY BUILT IT
HOW TO ARCHITECT IT
Product-Led Growth, Self-Serve / Website, Content Marketing, Community-Led
HOW THEY OPERATIONALIZED
HOW TO REPLICATE WHAT WORKED
dm
- Campsite used self-serve signup and a free entry point to reach distributed teams and design-led organizations. [270][266] - Founder posts on LinkedIn and X demonstrated product use cases, including call recording, AI summaries, public notes, and connected posts. [271][267][268] - The seed-round announcement and founder narrative reached design, startup, and remote-work communities. [265][272] - Product-led onboarding encouraged teams to try posts, calls, docs, and chat in one workspace rather than requiring a sales-led implementation. [270][266]
What worked: Founder-led product storytelling can attract design-led and remote-first buyers who respond to a calm, integrated collaboration vision. Trap if copied blindly: Founder distribution without daily-use validation creates attention and design-community goodwill but not retention; it fails when end users perceive the workflow as extra work rather than a replacement for existing habits.
| PATTERNS OF THIS MODEL
PATTERNS IN ASYNC COLLABORATION SUITES: 1. MANAGER-DESIRED BEHAVIOR DOES NOT EQUAL USER HABIT. Leaders may want visible work-in-progress, but contributors resist posting to broad audiences without clear personal benefit. 2. BROAD SUITES RAISE SWITCHING COSTS. Replacing chat, docs, meetings, and knowledge management simultaneously demands too much behavior change at once. 3. DESIGN QUALITY CREATES AWARENESS, NOT RETENTION. A polished experience can win trials and design-leader interest but cannot substitute for a daily workflow advantage. THE WEAKNESS: Async collaboration products often become optional archives unless they are embedded in an existing daily trigger such as code review, project delivery, or customer communication.
What companies with this model reveal
| OPPORTUNITY INTELLIGENCE
GOLDMINE 1 — AI-NATIVE DECISION RECORDS. The opportunity is not another feed but a system that turns meetings, threads, and documents into searchable decisions, owners, deadlines, and follow-ups. GOLDMINE 2 — WORKFLOW-EMBEDDED ASYNC REVIEW. Async collaboration works when attached to an existing trigger—code review, design handoff, sales deal review, or clinical case review—rather than asking users to post voluntarily. GOLDMINE 3 — MEETING-TO-KNOWLEDGE CONVERSION. AI can convert calls into decisions, action items, and shareable updates, but value depends on integrating with the tools where work already happens. THE PIT — BUILDING A SUITE TOO EARLY. Campsite combined Slack, Notion, Zoom, and Google Docs-like functionality before proving that one core behavior could retain users; broad scope increased switching friction and diluted focus. THE SECOND PIT — PSYCHOLOGICAL ADOPTION BARRIER. Asking contributors to share unfinished work publicly can trigger self-presentation anxiety; private channels then recreate the silos the product intended to remove. MOVE WITH CAUTION — Do not enter collaboration software with a broad all-in-one vision before proving a single daily behavior; Slack, Notion, Zoom, Google Workspace, and Microsoft Teams already own the default habits, and buyers may purchase selectively rather than migrate fully. [262][266][263][264]
Untapped Business Model / Gaps / Goldmines / Pits
Patterns & Insights
2
MARKET
mkt mt es
Campsite initially targeted design teams sharing work in progress, then broadened to entire companies. The mismatch became clear when design leaders bought the vision but individual contributors resisted posting work publicly; the company responded by adding private channels, effectively rebuilding Slack-like silos. [262][263][264]
MARKET TYPE
Red Ocean
ENTRY STRATEGY
Direct Entry
WHY THEY WON
Team collaboration is a red ocean dominated by Slack, Microsoft Teams, Google Workspace, Notion, Zoom, and Asana. Campfire—er, Campsite—entered with a differentiated calm-communication thesis but faced entrenched daily habits and multi-tool switching costs. Its structural blind spot was assuming that a leader’s desire for visibility would overcome contributors’ reluctance to share unfinished work. The company tried to solve this by adding private spaces, but that reduced differentiation and recreated the fragmentation it aimed to eliminate. The transferable lesson is that in collaboration markets, the buyer who signs the contract is often not the user whose behavior determines retention. [262][266][263][264]
EXECUTION
Campsite entered with its own product and channels, beginning as a design-collaboration tool and expanding into a broader communication workspace. It targeted remote and distributed teams through self-serve signup, founder-led content, and product-led onboarding. The critical bet was that teams would consolidate posts, docs, chat, and calls in one calm environment. This required excellent product experience and a clear daily-use case, but it did not initially require integration into an incumbent platform or a partner-led route. The approach would fail when the target behavior was voluntary, psychologically uncomfortable, or already served adequately by existing tools. [262][270][266][265]
FOOTHOLD STRATEGY
Beachhead Strategy
Campsite’s beachhead was design teams at remote-first companies that needed to share work in progress, collect feedback, and preserve design explorations. The pain was fragmented feedback across Slack, Figma, Zoom, and documents; the buyers were reachable because design leaders valued structured critique and archives. However, the foothold did not create durable daily behavior among individual contributors, limiting expansion into broader company-wide collaboration. [262][266][265][264]
GROWTH CAMPAIGN
CAMPAIGNS THAT WORKED
SO WHAT: Campsite’s campaigns effectively attracted design leaders and remote-work enthusiasts, but they did not establish a repeatable end-user behavior loop. KEY LEARNING: Awareness among economic buyers is not product-market fit; the decisive evidence is whether the person who must change behavior uses the product without prompting. HOW TO USE: Before expanding a collaboration product, measure voluntary weekly active usage among the end user—not only demo interest, pilot approval, or contract value.
KEY LEARNING
THE STANDARD: In a red ocean of collaboration suites, entrants must attach to an existing daily workflow rather than ask users to adopt a new all-in-one habit. RULE 1 — BUYERS AND USERS DIVERGE. Leaders buy visibility and alignment; individual contributors decide whether the tool becomes part of daily work. RULE 2 — PRICING FOLLOWS SEATS, BUT RETENTION FOLLOWS HABIT. Per-member pricing can produce revenue temporarily, but weak end-user activity leads to churn. RULE 3 — SUCCESSFUL ENTRANTS NARROW FIRST. They win one workflow, then earn permission to add adjacent modes. RULE 4 — FAILURE IS VOLUNTARY POSTING. A collaboration tool that depends on users choosing to share unfinished work faces a psychological adoption barrier. MARKET TYPE: Red Ocean (category).
gc
Market Context
| MARKET INTELLIGENCE
PATTERNS IN FOUNDER-LED PRODUCT STORYTELLING: 1. FOUNDER NARRATIVE CREATES EARLY AWARENESS. Personal product demonstrations can reach design, startup, and remote-work audiences efficiently. 2. SELF-SERVE ONBOARDING REDUCES INITIAL FRICTION. Free access lets teams experiment without procurement delay. 3. PRODUCT VISION CAN OUTRUN BEHAVIORAL EVIDENCE. A compelling all-in-one story may win interest before daily-use data validates retention. 4. THE WEAKNESS: Founder-led distribution can create a biased signal because early adopters may share the founder’s values rather than represent the broader end-user base.
| MARKET ENTRY PLAYBOOK
THE STANDARD: Direct entry is appropriate when the company can reach users directly and the product offers a clear improvement over an existing workflow. RULE 1 — Start with a workflow that users already perform and can perform more easily in the new product. RULE 2 — Validate end-user retention before expanding into a multi-product suite. RULE 3 — Use founder-led distribution to create awareness, but do not treat it as evidence of product-market fit. RULE 4 — Reject direct entry when the target behavior requires users to abandon several entrenched tools simultaneously. [262][266][263][264]
How to enter
| FOOTHOLD STRATEGY PLAYBOOK
THE STANDARD: A beachhead strategy requires a segment where the product becomes part of an existing daily workflow. RULE 1 — Choose a segment with a recurring, mandatory workflow rather than an optional sharing behavior. RULE 2 — Prove weekly active usage and retention before expanding beyond the initial use case. RULE 3 — Expand only when the first workflow creates a reason to adopt adjacent capabilities. RULE 4 — In collaboration software, a beachhead fails when the buyer wants visibility but the end user avoids participation.
How to get the first strong position
MARKET PATTERNS & PLAYBOOK
3
MONEY
money rev pri
Campsite validated willingness to pay through freemium conversion and paid contracts, including a six-figure deal cited by its founder. However, payment by design leaders did not establish durable end-user adoption; the company ultimately wound down the product. [270][263][264]
REVENUE MODEL
Subscription
PRICING MODEL
Freemium, Tiered Pricing, Custom Enterprise Pricing
WHY THEY WON
Teams paid recurring per-member subscriptions for collaboration features, with higher tiers adding call recording, AI summaries, unlimited guests, SSO, custom SLAs, and migration support. Revenue scaled with seats, but retention depended on whether members used posts, docs, chat, and calls regularly. [270]
Campsite offered a free entry point, Essentials at $8 per member per month, Pro at $16 per member per month, and custom Business pricing for advanced needs. Pro added call recording and AI summaries; Business added SSO, custom SLA/MSA, private support, and migration support. [270]
TARGET AUDIENCE
Design teams at remote-first companies (Essentials/Pro; want structured feedback and work-in-progress archives); startup and product teams (Pro; want posts, docs, chat, and calls together); distributed companies (Business; want SSO, migration, and a unified communication workspace); design and engineering leaders (Business; want visibility into team work and decisions). [262][270][266]
CUSTOMER BUYING BEHAVIOUR
A design or remote-work leader evaluates Campsite after frustration with fragmented feedback and communication tools. The buyer trials the product, may purchase a team or enterprise plan, but adoption depends on whether individual contributors voluntarily post work and use the workspace daily. [262][270][266][264]
| PRICING INTELLIGENCE
What makes this model effective & make customers pay
Buyers pay for visibility, alignment, and fewer tools—but only when the end user receives a personal workflow benefit. RULE 1 — SELL THE MANAGER’S OUTCOME, DESIGN FOR THE CONTRIBUTOR’S HABIT. Visibility must not create extra self-promotion work for contributors. RULE 2 — PRICE PER MEMBER, BUT MEASURE ACTIVE MEMBERS. Seat revenue without active usage is a leading indicator of churn. RULE 3 — MONETIZE A MANDATORY WORKFLOW. Review, approval, handoff, or decision documentation is more durable than voluntary sharing. RULE 4 — AVOID SUITE OVERREACH. A broad all-in-one pitch can win interest but increase the behavioral change required to adopt it. The buyer is really buying better team alignment and a calmer communication system, proven by the design or operations budget—but sustained only by contributor usage. [262][270][266][264]
PRICE & REVENUE
| Revenue Risk - The biggest threat to revenue stability
End-user adoption failure: If contributors do not post, comment, or use calls, seats become inactive and renewal risk rises. Suite bundling: Notion, Slack, Zoom, Google Workspace, and Microsoft Teams already cover overlapping jobs, reducing the need for another standalone workspace. High switching cost: Replacing chat, docs, and meetings simultaneously is difficult for teams. Behavioral resistance: Contributors may avoid sharing unfinished work with a broad audience. Narrow buyer concentration: Design-led purchasing can create dependence on a small set of enthusiastic champions. Campsite raised $2.6 million in 2022, wound down on February 28, 2025, and its founders joined Notion; standalone ARR was not publicly disclosed. [262][273][265][263][264]
Where the model can break
4
MOTION
motion ge cs
Campsite used self-serve signup, founder-led content, and design-community distribution to reach early teams. It converted interest into paid plans and larger contracts, including a six-figure deal, but ultimately found that revenue did not prove durable end-user adoption. [270][265][264]
GROWTH EXPANSION MODEL
Horizontal Expansion, Product Line Expansion
HOW THEY EXPAND
Campsite expanded from design work-in-progress sharing into company-wide posts, notes, chat, calls, AI summaries, integrations, and enterprise controls. The expansion aimed to make Campsite a full communication workspace, but it increased the behavioral change required from users and moved the company into direct competition with multiple entrenched suites. [262][266][267][268][264]
COMPETITIVE STRATEGY
Differentiation
HOW THEY COMPETE
Campsite differentiated through a calm, integrated alternative to fragmented Slack, Zoom, Notion, and Google Docs workflows. Its differentiation emphasized connected posts, docs, calls, and chat, plus AI summaries and a rich work-in-progress archive. [262][266][267][268]
GROWTH ENGINE
GTM
Content Flywheel
Founder-led posts and design-community visibility brought teams into self-serve trials. Teams experimented with posts, feedback, docs, and calls; paid plans converted some buyers. The intended loop was that shared work created organizational visibility, which encouraged more participation and knowledge accumulation. In practice, psychological barriers and entrenched tool habits weakened the loop, leading to low end-user adoption and eventual wind-down. [262][266][265][264]
Campsite’s GTM was product-led and founder-led, targeting design-led and remote-first teams through self-serve onboarding and social storytelling. Design leaders evaluated and purchased the product, while individual contributors were expected to adopt posting and collaboration behavior. The company later added enterprise features such as SSO and migration support, but the core motion remained self-serve. This approach requires a daily-use behavior that users voluntarily adopt; it is unlikely to work when the product asks users to replace several entrenched tools at once. [262][270][266][263][264]
SUSTAINING MOATS
High Customer Lock-In
moat
Campsite’s intended moat was a connected product ecosystem: posts, docs, chat, calls, AI summaries, and integrations in one workspace. The theory was that cross-linking communication and knowledge would create switching costs as teams accumulated context in one place.
| MOAT INTELLIGENCE
THE STANDARD: A collaboration ecosystem lasts only when users accumulate context and return daily. RULE 1 — CONNECTED CONTEXT CREATES VALUE. Posts, docs, calls, and chat can become more useful when linked in one searchable workspace. RULE 2 — AI SUMMARIES INCREASE ARCHIVE VALUE. Recorded calls and summaries can turn ephemeral communication into reusable knowledge. RULE 3 — INTEGRATIONS REDUCE FRICTION. Apps and custom integrations can connect Campsite to existing work systems. THE SIGNAL: Campsite’s public notes, call summaries, and connected posts demonstrated the intended knowledge ecosystem. The moat did not last because contributors did not voluntarily create enough context, and the product wound down in 2025. [262][266][267][268][263]
Why this company remains defensible
ARR & TAKEAWAY
ARR Journey - what to do at each stage
PRE-$1M ARR — VALIDATE DESIGN-COLLABORATION WEDGE. Campsite began in 2022 as a design-team tool for sharing work in progress and feedback. WATCH: Voluntary posting may not become a daily habit. $1–5M ARR — EXPAND THE COMMUNICATION SUITE. After raising $2.6 million in 2022, Campsite broadened into posts, notes, chat, calls, integrations, and AI summaries. WATCH: A broad suite increases switching friction and competitive exposure. $5–10M ARR — NOT PUBLICLY VERIFIED. Public sources do not disclose Campsite-specific ARR at this stage. $10–50M ARR — NOT REACHED. Campsite did not publicly demonstrate reaching this stage before winding down. $50–100M ARR — NOT REACHED. The company announced wind-down in December 2024 and ceased operations on February 28, 2025. $100M+ ARR — NOT REACHED. Campsite’s founders joined Notion rather than scaling the standalone company. Rule: Validate end-user daily behavior before expanding a collaboration product into a multi-tool suite; paid contracts do not substitute for retention. [262][273][265][263][264]
COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid
THE STANDARD: Validate one daily end-user behavior, then expand into adjacent collaboration modes only when that behavior creates retention. SEQUENCE: 1. Choose a mandatory workflow where the end user already needs to act, such as review, handoff, or approval. 2. Prove weekly active usage and retention before adding chat, docs, meetings, or knowledge features. 3. Design for the contributor’s personal benefit, not only the manager’s desire for visibility. 4. Use integrations to enter existing workflows rather than asking users to abandon multiple tools at once. WORKED: Campsite’s design-led positioning and founder storytelling created early awareness and paid interest. CAUTION: Do not treat a large contract as product-market fit; Campsite closed six-figure deals but did not generate enough end-user activity. Do not build a Slack-Notion-Zoom-Google Docs replacement before proving one core behavior; the suite was too broad to change at once. [262][270][266][263][264]
bottom of page