Obsidian, the note-taking app beloved by developers and knowledge workers, is reportedly valued at $350 million. The company has three engineers. Not three hundred. Three. This is one of the most efficient value-per-employee ratios in software history, and it reveals something important about how modern software companies can scale without headcount.
How Three People Built a $350M Product
Obsidian’s core product is a local-first markdown editor with bidirectional linking, a plugin ecosystem, and near-zero latency because everything runs on your machine. There are no servers processing your notes. No AI models running inference on your data. No complex backend infrastructure to maintain. The app is essentially a very sophisticated file editor, and that simplicity is the business strategy.
By keeping the architecture local-first, the team eliminated the operational overhead that devours engineering time at companies like Notion (400+ employees) and Evernote (now owned by Bending Spoons). No server scaling problems. No database migrations at 3 AM. No incident response teams. The three engineers spend their time building features, not fighting fires.
The plugin ecosystem handles feature requests that would otherwise require dozens of engineers. Community developers have built over 1,800 plugins covering everything from calendar integration to AI assistant functionality. Obsidian provides the platform; the community provides the features.
The Revenue Model That Funds It
Obsidian is free for personal use. Revenue comes from two paid add-ons: Obsidian Sync ($4/month for end-to-end encrypted syncing across devices) and Obsidian Publish ($8/month for hosting notes as a website). Commercial use requires a $50/year license per user.
These are high-margin products with minimal support overhead. Sync is built on standard infrastructure. Publish is static site hosting. Neither requires a large team to maintain. With millions of active users and a passionate community willing to pay for premium features, the revenue likely places Obsidian well into profitability without venture capital pressure.
What Other Startups Can Learn
The Obsidian model works because of two deliberate choices: local-first architecture and platform-as-ecosystem. Both reduce the team size needed to deliver a competitive product.
Local-first means your users’ devices do the computing. You do not pay for their CPU cycles, storage, or bandwidth. Platform-as-ecosystem means your community builds features you would otherwise need to staff for. Both strategies require excellent core software, which is where the three engineers focus their time.
This approach does not work for every product. Social apps need servers. Real-time collaboration needs infrastructure. But for tools where the user’s own data and own device are central, the Obsidian playbook is worth studying.
The Bigger Trend
Obsidian joins a growing list of small-team, high-valuation software companies. Basecamp has stayed deliberately small for decades. Figma reached a $20B valuation with a relatively lean team. The pattern suggests that the “hire 500 engineers” approach to software building is not the only path to significant enterprise value.
For developers deciding what to build next, Obsidian is proof that a focused product, clean architecture, and respect for users’ data can outperform bloated competitors with 100x the headcount. Three engineers, $350 million. The math speaks for itself.
If you value privacy-first software that keeps your data on your own devices, Obsidian is worth trying. The free tier is genuinely complete, and you may never need the paid add-ons.
