top of page
Won a niche inside an already-crowded work-chat market by refusing to be real-time — building an async, designer-first feed specifically for teams tired of Slack's always-on interruption model.
1
MODEL
BUSINESS MODEL
SaaS
model bm
HOW THEY BUILT IT
- Founded by Brian Lovin, a designer with prior experience at Meta/Instagram and GitHub, who built Campsite out of his own frustration with feedback scattered across Slack messages and Google Docs.
- Raised $2.6M in early funding to build a product for centralizing design feedback, calls, docs and chat in a single async-first feed.
- Repositioned over time from a design-team feedback tool into a broader work-communication platform for distributed teams (adopted internally at companies like Coinbase and Copilot for cross-team visibility).
- Built a public API (2024) specifically because customers were being blocked from switching to Campsite without integration parity to existing tools — the API became a condition of enterprise adoption, not a bonus feature.
HOW TO ARCHITECT IT
1. Start from a founder's own acute pain (Lovin as a designer drowning in scattered feedback) rather than a market-sizing exercise — the product's earliest, most differentiated features (a Figma plugin, a public design channel) came directly from that lived frustration.
2. Launch narrow (design teams specifically) before broadening to all-company communication — a wedge persona is easier to win decisively than 'everyone at the company' on day one.
3. Build integrations reactively based on what blocks a specific deal from closing (start with the cheapest option, e.g. a Zapier integration, before committing to a full public API), so integration investment tracks proven demand rather than guesswork.
DISTRIBUTION MODEL
Content Distribution, Community Distribution
dm
HOW THEY OPERATIONALIZED
- Grew initial adoption through the design community specifically — a built-in public design channel let non-customers see and engage with real work being shared on the platform, functioning as organic top-of-funnel content.
- Word of mouth inside design-forward companies (Coinbase, Copilot) where a single design lead introduces the tool and it spreads to adjacent product and engineering teams via the 'Digest' feature that surfaces a week's work to stakeholders.
HOW TO REPLICATE WHAT WORKED
What worked: the 'Digest' feature that automatically summarizes a person's or team's week of work for stakeholders — it turns the tool into a reporting-up mechanic that individual contributors have a personal incentive to keep using.
Trap if copied blindly: positioning purely as 'Slack but calmer' invites direct comparison to an entrenched, deeply-integrated incumbent — Campsite only avoided a head-on feature war by first winning a specific persona (designers) where Slack's real-time model was a proven liability, not by trying to out-Slack Slack broadly.
| PATTERNS OF THIS MODEL
PATTERNS IN FOUNDER-PAIN PRODUCTS FOR DISTRIBUTED TEAMS:
1. START FROM ACUTE PERSONAL FRUSTRATION. The most differentiated early features come from lived experience, not market research.
2. LAUNCH NARROW ON ONE FUNCTION BEFORE BROADENING TO THE WHOLE COMPANY. A wedge persona is winnable; "everyone at work" is not.
3. BUILD INTEGRATIONS REACTIVELY, IN RESPONSE TO SPECIFIC BLOCKED DEALS. Start with the cheapest option and commit to a full API only when it is provably a purchase condition.
4. INTEGRATION PARITY IS OFTEN A GATE, NOT A DIFFERENTIATOR. Buyers will not switch to a better product that cannot connect to what they already run.
What companies with this model reveal
| OPPORTUNITY INTELLIGENCE
GOLDMINE 1 — START FROM THE FOUNDER'S OWN ACUTE PAIN.
Standard: a designer drowning in feedback scattered across Slack and Docs produced the most differentiated early features — a Figma plugin, a public design channel — because they came from lived frustration rather than market sizing.
GOLDMINE 2 — LAUNCH NARROW BEFORE BROADENING.
Standard: design teams specifically, then all-company async communication. A wedge persona is winnable decisively; "everyone at the company" is not.
GOLDMINE 3 — BUILD INTEGRATIONS REACTIVELY, CHEAPEST OPTION FIRST.
Standard: Campsite shipped a public API in 2024 only because integration parity was blocking specific deals. Let blocked revenue, not a roadmap, decide integration investment.
THE PIT — ASYNC COMMUNICATION IS THE MOST CROWDED AND MOST BUNDLED CATEGORY IN WORK SOFTWARE.
Slack, Teams, Notion and Loom all occupy the space, and $2.6M raised cannot fund a fight for a habit that already has a default. Being better than Slack for design feedback does not displace Slack.
THE SECOND PIT — BROADENING FROM DESIGN TO ALL-COMPANY ABANDONS THE ONLY DEFENSIBLE POSITION.
MOVE WITH CAUTION — NO DISCLOSED REVENUE OR CURRENT STATUS; VERIFY BEFORE CITING.
Untapped Business Model / Gaps / Goldmines / Pits
Patterns & Insights
2
MARKET
mkt mt es
MARKET TYPE
Red Ocean
WHY THEY WON
Workplace communication is dominated by Slack, Microsoft Teams and a wave of well-funded challengers — a genuinely crowded, well-served market. Campsite carved out room by explicitly rejecting the real-time chat paradigm that defines the category and building for async, feed-based visibility instead, a positioning choice that resonated specifically with design and product teams frustrated by constant interruption. Transferable principle: in a red ocean, don't fight on the incumbent's terms — find the specific behavior (always-on notifications) that a vocal subset of users actively resents and build the anti-pattern.
ENTRY STRATEGY
Greenfield Entry
EXECUTION
Campsite launched directly to design teams via its own website and a Figma plugin rather than through any platform or channel partner, the only viable path for a still-unproven challenger in a category owned by Slack and Teams.
FOOTHOLD STRATEGY
fs
Beachhead Strategy
Design teams at product-led tech companies were the beachhead — a well-defined, reachable persona (in-house designers at companies like Coinbase and Copilot) with an acute, specific pain (feedback scattered across Slack/Docs) and a founder (Lovin) who was credibly one of them. From that beachhead, adoption expanded outward as designers used Campsite to solicit feedback from product managers and engineers, pulling adjacent roles onto the platform organically rather than through a top-down company-wide rollout.
GROWTH CAMPAIGN
CAMPAIGNS THAT WORKED
Figma plugin integration: let designers upload work directly into Campsite from their existing workflow, removing the friction of a separate upload step that kills adoption for feedback tools.
Public design channel: created a visible, browsable feed of real design work that functioned as organic content marketing to the broader design community, not just paying customers.
Public API launch (2024): unblocked enterprise deals that had stalled specifically because prospects couldn't replicate integrations they relied on in Slack, resulting in 100+ customer-built integrations post-launch.
KEY LEARNING
If you're entering a category with an entrenched, feature-rich incumbent, don't compete on feature parity — find the specific behavioral pattern the incumbent optimizes for (real-time interruption, in Slack's case) that a reachable persona actively resents, and build the deliberate opposite. Layer in a lightweight integration (a plugin) before a full API, and only invest in the API once real deals are being blocked without it.
gc
Market Context
| MARKET INTELLIGENCE
THE STANDARD: In a red ocean, find the specific behaviour a vocal subset actively resents and build the anti-pattern.
RULE 1 — RESENTMENT IS A SHARPER SIGNAL THAN DISSATISFACTION. Constant notification interruption is a felt harm, not a missing feature.
RULE 2 — REJECTING THE CATEGORY'S CORE MECHANIC IS THE POSITIONING. Async, feed-based visibility is a refusal to be a better chat tool.
RULE 3 — ANTI-PATTERN PRODUCTS WIN A COMMITTED MINORITY AND FEW ENTERPRISE DEALS. The organisations most in need of the fix are least likely to change habits.
RULE 4 — WHEN THE INCUMBENT IS BUNDLED AND FREE, PREFERENCE RARELY JUSTIFIES A SECOND TOOL. Adoption requires replacing something, not adding to it.
MARKET TYPE: Red Ocean (workplace communication).
| MARKET ENTRY PLAYBOOK
THE STANDARD: LAUNCHING INSIDE THE TOOL YOUR USERS ALREADY WORK IN IS THE ONLY VIABLE ENTRY AGAINST ENTRENCHED COMMUNICATION PLATFORMS.
RULE 1 — DISTRIBUTE THROUGH THE PLUGIN, NOT THE WEBSITE.
Design teams live inside their canvas; appearing there removes the requirement to adopt a new destination.
RULE 2 — TARGET THE WORKFLOW THE INCUMBENT HANDLES BADLY.
Asynchronous design feedback is poorly served by real-time chat, which buries visual context.
RULE 3 — COMMUNICATION TOOLS FACE THE HARSHEST BUNDLING RISK IN SOFTWARE.
Without becoming the standard for one discipline, the general platform absorbs you by default.
How to enter
| FOOTHOLD STRATEGY PLAYBOOK
THE STANDARD: Build for the craft community you belong to, then let their collaborators pull adjacent roles in.
RULE 1 — DEFINE THE BEACHHEAD BY DISCIPLINE AND SCATTERED PAIN. In-house designers losing feedback across chat and documents are a precise, reachable persona.
RULE 2 — FOUNDER MEMBERSHIP OF THE COMMUNITY IS THE CREDENTIAL. Craft audiences trust practitioners and dismiss vendors.
RULE 3 — LET THE ORIGINAL USERS RECRUIT THE ADJACENT ONES. Designers requesting feedback bring product managers and engineers in without a rollout.
RULE 4 — A SINGLE-DISCIPLINE TOOL MUST BECOME CROSS-FUNCTIONAL OR STAY SMALL. The expansion path is the people already in the conversation, not a new market.
How to get the first strong position
MARKET PATTERNS & PLAYBOOK
3
MONEY
money rev pri
REVENUE MODEL
Subscription
PRICING MODEL
Freemium
WHY THEY WON
Freemium subscription: a generous free tier (unlimited posts, projects, desktop app and Figma plugin) to seed team-wide adoption, with a Pro plan charging for unlimited members/projects, private projects and larger upload limits — monetizing the point where a team's usage outgrows what a single free workspace can hold.
The free tier is intentionally full-featured for individual and small-team use so that adoption spreads unrestricted within a company first; the paywall sits at organizational scale (private projects, unlimited members) — targeting the point where an engineering or design lead needs company-wide rollout, not the point where an individual contributor needs more features.
TARGET AUDIENCE
CUSTOMER BUYING BEHAVIOUR
tg cb
In-house designers at product companies (free tier, want centralized feedback); design and product leads at scaling tech companies (Pro tier, want cross-team visibility via Digests); executives and stakeholders at those same companies (indirect users, consuming Digest summaries rather than posting).
Bottoms-up and trial-first: an individual designer adopts free, invites collaborators organically, and a team lead converts to Pro once the team outgrows the free workspace's limits — self-serve throughout, with no evidence of a heavy enterprise sales motion.
| PRICING INTELLIGENCE
What makes this model effective & make customers pay
A free tier for small teams is a bet that the tool becomes indispensable before the team can afford it.
RULE 1 — FREE MUST DELIVER A COMPLETE WORKFLOW, NOT A SAMPLE.
For team products, partial function produces abandonment rather than upgrade pressure.
RULE 2 — ASYNCHRONOUS COLLABORATION COMPETES WITH FREE CHAT TOOLS ALREADY IN PLACE.
Differentiation must be in the workflow — structured updates, decisions, context — not in messaging.
RULE 3 — BUNDLING RISK FROM LARGE PLATFORMS IS THE PERMANENT THREAT.
Any category a suite can adequately absorb has no independent price floor.
RULE 4 — SMALL TEAM TOOLS RARELY DISCLOSE METRICS; TREAT SCALE AS UNKNOWN.
The structural lesson is the transferable content.
Distributed teams are buying fewer meetings and less interruption. That is a genuine need with an unstable price, because the platforms they already pay for keep shipping approximations of it.
PRICE & REVENUE
| Revenue Risk - The biggest threat to revenue stability
A generous free tier seeds team-wide adoption and means monetisation depends entirely on a workspace outgrowing limits — a threshold many teams never cross.
Async team-update products compete with the chat platform the team already pays for, which can ship the same feature at zero marginal cost.
Design and product-team tools have small buyer populations and low willingness to pay for communication layers.
Free tiers with unlimited posts carry real storage and infrastructure cost.
Early-stage; no revenue or customer figures published, and current status should be verified.
Where the model can break
4
MOTION
GROWTH EXPANSION MODEL
COMPETITIVE STRATEGY
motion ge cs
Market Development (New Customer Segments)
HOW THEY EXPAND
Campsite expanded from a design-team feedback tool into a broader work-communication platform for entire distributed companies — repositioning its core primitives (posts, chats, docs) as a general alternative to Slack rather than a design-specific tool, a shift the team described explicitly as moving 'from a specialized communication tool for designers to a general communication tool for entire organizations' starting in early 2024.
Focus Strategy
HOW THEY COMPETE
Rather than attempt to out-feature Slack across every use case, Campsite focused narrowly on async, feed-based visibility for creative and product work — a sequencing logic that required first proving product-market fit with one clearly underserved persona (designers) before the team judged it credible to reposition as a general communication tool for the whole company.
GROWTH ENGINE
GTM
ge n gtm
Community-Led Growth, Product-Led Growth
The loop: a designer posts work in Campsite and tags a product manager or engineer for feedback; that person, previously not a user, now has to log in to respond, experiences the async feed model firsthand, and often starts posting their own updates. It's self-reinforcing because each cross-functional feedback request pulls a new adjacent-team member into active use. It would break down in a company culture that fundamentally prefers synchronous meetings over written async feedback, where the core value proposition simply doesn't land.
Product-led adoption starting inside design teams via a free tier and Figma plugin, expanded through internal word of mouth (a design lead invites product/engineering counterparts) and reinforced by content distribution via the public design community channel; enterprise deals unlocked specifically once the public API let prospects replicate integrations they'd built into Slack.
SUSTAINING MOATS
Switching Costs, High Customer Lock-In, Brand Power, Technology Advantage (complex enterprise scenarios)
moat
Once a team's design history, feedback threads and 'Digest' archive of weekly work live inside Campsite, that record becomes an institutional memory competitors can't easily replicate — a new team member can scroll back through months of context that would otherwise be scattered across Slack, email and Google Docs, making the cost of switching not just about re-training but about losing a searchable project history.
| MOAT INTELLIGENCE
THE STANDARD: Asynchronous updates only stick when they replace a meeting. If they add to the schedule rather than removing something, adoption decays quietly.
RULE 1 — THE PRODUCT MUST DELETE A RECURRING CALENDAR EVENT. Written standups that supplement live standups become another chore. Ones that eliminate the meeting produce time savings people defend.
RULE 2 — THE SEARCHABLE RECORD IS THE COMPOUNDING ASSET. Months of written decisions and context become an institutional archive that spoken meetings never produce.
RULE 3 — ADOPTION IS DRIVEN BY MANAGEMENT MANDATE AND SUSTAINED BY INDIVIDUAL BENEFIT. Where only the manager gains, participation falls to compliance-level quality within a quarter.
THE SIGNAL: this capability sits one feature away from every chat platform in existence. The defensible version is the structured record and its usefulness to whatever reads it later — a workflow tool alone will be bundled away.
Why this company remains defensible
ARR & TAKEAWAY
ARR Journey - what to do at each stage
PRE-$1M ARR — NAME AMBIGUITY, STATED FIRST
Multiple small products use this name across asynchronous team updates, design collaboration and link-in-bio tooling. No figures can be reliably attributed; all band placement is inference.
The content below covers the asynchronous-communication wedge.
$1–5M ARR — REPLACE THE MEETING, DO NOT ADD A TOOL
Async standups and updates only work if a recurring meeting is genuinely cancelled. Sell the removed calendar time.
WATCH: posts per team per week — silence means the habit failed.
$5–10M ARR — ADOPTION IS TEAM-WIDE OR NOTHING
One enthusiast in a team produces no value. Onboarding must convert the whole group.
$10–50M ARR — THE COLLABORATION SUITES ABSORB THIS CATEGORY
Slack, Teams and Notion all ship async update features. Independent tools in this space have repeatedly been acquired or shut down.
Treat that as the base rate.
$50–100M ARR — NOT IN EVIDENCE
State it plainly.
$100M+ ARR — NOT APPLICABLE
Rule: products that depend on a behaviour change inside a customer's organisation need an executive sponsor. Bottom-up adoption of a discipline rarely survives the first busy quarter.
COPY PLAYBOOK : What Worked → What Failed → What to Replicate → What to Avoid
THE STANDARD: A feature that gives individual contributors a personal incentive to keep using the tool — reporting upward automatically — is stickier than any team mandate.
SEQUENCE:
1. Find the recurring task your user does for someone above them.
2. Automate it so using your product makes them look good with no extra effort.
3. Win one persona where the incumbent's model is a proven liability before broadening.
WORKED: An automatic weekly work summary turning the product into a reporting-up mechanic individuals personally wanted to maintain.
CAUTION:
1. POSITIONING AS "THE CALMER VERSION OF X" INVITES DIRECT COMPARISON TO AN ENTRENCHED, DEEPLY INTEGRATED INCUMBENT. That is survivable only by first winning a specific persona where the incumbent's real-time model genuinely fails — not by competing broadly.
2. COMMUNICATION TOOLS FACE THE HARSHEST BUNDLING RISK IN SOFTWARE.
bottom of page