This story condenses a source-backed brief. Some historical details and internal metrics are not established. [Inference] marks analysis. Source numbers keep the numbering of the full case, and the evidence is from the 10 Nov 2026 research edition. Read the research method.
The founders already knew how to collaborate
In a Ness Labs interview, Erica Xu says she and Shida Li began Obsidian during the 2020 quarantine after working together on projects including Dynalist. They distributed private builds and collected feedback through Discord. Xu connected that choice with Li’s prior experience moderating gaming communities on the platform. [1]
The record does not identify the first paying customer or an original founder-led contract.
[Inference] The private beta establishes a setting for observing a strong personal knowledge-management need, but beta participation should not be counted as willingness to pay. Its early value is the opportunity to learn what people actually capture, organize and try to retrieve.
Chat was useful until requests became difficult to manage
Xu describes a suggestion bot becoming unwieldy after more than a thousand requests, prompting the addition of a Discourse forum. Users answered one another’s questions and community members became moderators. Plugins were an intentional architectural choice from the beginning. These are specific product and community decisions rather than an unspecified claim that community caused growth. [1]
[Inference] Different communication surfaces support different work. Chat can help someone solve an immediate problem, while persistent requests need to remain searchable and comparable. Moving feedback into a forum can preserve founder learning as participation increases. It also requires judgment about which requests represent a shared need rather than the preferences of the most vocal users.
The mobile roadmap changed through use
Xu says feedback changed the mobile plan from a limited companion into a fuller application. That is a documented example of customer input altering the product direction. It does not establish a measured retention lift or prove that every requested capability should be built. [1]
[Inference] Personal knowledge tools depend on whether an individual can reach useful information in the situations that matter. A feature can therefore affect continuity of use even when it appears secondary in a desktop demonstration. The adoption question should examine the whole working context, while recognizing that personal preferences can create considerable variation in what users regard as essential.
Workplace adoption and paid accounts are different counts
On February 20, 2025, Obsidian announced that its Commercial license was optional, explaining that the prior terms created confusion. Sync, Publish and support licenses remained funding sources. The announcement reported use in more than 10,000 organizations. That is an adoption statement, not a count of paying enterprise customers or negotiated contracts. [2]
[Inference] A clearer workplace permission can reduce uncertainty for individual adopters while shifting the funding burden toward optional capabilities and supporters. The economic question becomes how many users value those paid services enough to sustain development and support. Organizational presence alone cannot answer it, particularly when the core product remains available without a mandatory commercial license.
A helpful community still requires stewardship
The record establishes peer assistance and recruited moderators, but not named account executives, customer-success managers, service costs or renewal ownership. Historical price details, CAC, margin, payback and retention cohorts remain incomplete. The evidence therefore supports a community operating account more strongly than a conventional enterprise expansion narrative. [1][2]
[Inference] Local storage changes the service context, but does not remove development and assistance obligations. Obsidian’s transferable lesson is to assign community mechanisms specific jobs and make the payment boundary understandable. A stronger assessment would connect useful recurring habits, moderator effort and optional-service conversion, asking whether broad free adoption supports a durable business without treating either user enthusiasm or workplace reach as sufficient economic proof.
Obsidian: the full GTM case
The complete case holds the named people, the economics, the available historical evidence, the critique and the open research questions.
Read Obsidian’s full GTM caseTerms in this story
Questions behind the story
How do I choose between product-led and sales-led growth?Why does the site leave CAC and retention blank for some companies?All 104 GTM questions answered
Sources
Numbers match the source list of the full Obsidian case. A source’s publication date and the date of the event it reports can differ.
- Exploring the power of note-making with the co-founder of Obsidian nesslabs.com
- Obsidian is now free for work Obsidian · 2025-02-20