Seven People, One Cat: Why Obsidian Built a Global Product Without Becoming a Big Company

A lot of people did not really pay attention to Obsidian as a company until a hiring post started circulating online.

What stood out was not the salary. It was the team size. Obsidian was openly saying it was growing from three engineers to four. For a product widely believed to serve a monthly active audience in the millions, that number felt almost absurdly small.

Then people clicked through to the company’s About page and realized this was not a clever line in a recruiting post. Obsidian really is a very small company.

That is what makes it so interesting. It is not a product held up by a giant sales org, a massive funding round, or a sprawling management structure. It looks much more like something else: a company built on sharp product judgment, a disciplined architecture, a strong community, and an unusual level of leverage per person.

And none of that appears accidental. The shape of Obsidian today was embedded in the choices it made from the beginning.

What kind of company is Obsidian?

Obsidian was founded in 2020 by Shida Li and Erica Xu, who had already built Dynalist together. That background matters. Obsidian did not come from nowhere. It came from founders who had already spent years thinking about information structure, knowledge work, and the habits of demanding users.

Its official manifesto still offers the cleanest explanation of the company:

• Yours
• Durable
• Private
• Malleable
• Independent

In plain English, that means:

• your notes belong to you, not the platform,
• your files should outlast the software you use today,
• your data should not be casually harvested,
• tools should adapt to how people think,
• and the company should answer to users, not investors.

That is not decorative brand language. It directly explains the product.

Obsidian chose a local-first architecture from the start. Notes live on the user’s device. Files are stored in open formats like Markdown. The core product does not require an account just to begin. That one decision shaped everything else, including trust, cost structure, product boundaries, and the kind of company Obsidian could remain as it grew.

How small is the team, really?

This is still the fact people return to first.

On the official About page, Obsidian presents a small core group across co-founders, engineering, and customer success, plus the office cat Sandy. Many people summarize the company as roughly seven full-time employees and one cat, which broadly matches the tiny-team reality users see on the site. The exact number can vary depending on how outside writers count former versus current members still shown publicly, but the core point does not move: Obsidian is genuinely small.

More importantly, it is small by choice.

From public comments, Steph Ango has made that philosophy clear. The goal is not to grow into a large, meeting-heavy, management-dense organization just because the market rewards that story. The company appears to prefer a size where everyone is still a direct contributor.

That gives Obsidian several advantages at once:

• lower coordination overhead,
• less management drag,
• clearer product judgment,
• stronger consistency,
• and more room to preserve the craft side of building software.

It is hard to imagine Obsidian keeping the same feel if it had become an 800-person company.

How does Obsidian make money, and what should be written carefully?

This is the easiest part of the story to exaggerate.

Because the narrative is so attractive, tiny team, loved product, strong community, no venture capital, people quickly jump from that to ARR charts, valuation talk, and revenue-per-employee mythology.

But this is exactly where the writing should be most precise.

What can be confirmed

From Obsidian’s official public materials, at least four monetization layers are clear.

1. Sync

This is Obsidian’s paid sync product.

The official pricing page shows: - Sync Standard: $4 per user per month, billed annually - Sync Plus: $8 per user per month, billed annually

It combines end-to-end encryption, version history, cross-platform sync, and offline-first behavior into a premium service that makes obvious sense for serious users.

2. Publish

Publish turns notes into websites.

That may sound like a side product, but it is actually important. It extends Obsidian from a private knowledge environment into a public-facing publishing system.

3. Commercial License

The official license page is explicit: the core app is free for everyone, including commercial use. Commercial licenses are optional, positioned as a way for organizations to support the company and help it remain independent.

4. Catalyst

Catalyst is a paid support tier for individuals who want to back the company and get access to insider benefits.

What should not be presented as confirmed fact

A widely repeated estimate places Obsidian at around $25 million in ARR. That number appears often enough that it has become part of the broader conversation around the company.

But based on the official public sources reviewed here, Obsidian has not formally published that ARR figure on its own site.

So the careful version is straightforward:

• Obsidian clearly has a real and mature revenue model,
• outside observers estimate ARR in the $25 million range,
• but that estimate should still be labeled as an estimate unless the company itself confirms it.

That distinction is worth preserving. Obsidian’s appeal is tied to trust and clarity. Writing about it carelessly would miss the point.

Why does Obsidian’s efficiency seem so extreme?

Even without turning outside ARR estimates into hard fact, Obsidian’s perceived efficiency is striking.

That is not because something mysterious is happening. It comes down to three structural advantages.

First, the core product is not a heavy cloud infrastructure business

Tools like Notion, Slack, or Figma depend heavily on centrally operated systems. More users usually mean more backend load, more infrastructure, more operational complexity, and eventually, more headcount.

Obsidian is different.

Its most important interactions happen locally. Users write notes, connect ideas, and build personal knowledge systems on their own devices. That means user growth does not automatically drag the company into the same cost curve as a cloud-native collaboration product.

Second, it monetizes the highest-intent layers

Obsidian does not try to force every user into a paid plan.

Instead, it makes the free core strong enough to earn trust, then monetizes the parts that users are most willing to pay for: sync, publishing, and organizational support.

That is a much cleaner model than artificially degrading the core product just to create upgrade pressure.

Third, the community amplifies the product far beyond payroll

If you only look at the employee count, Obsidian seems impossibly small.

If you look at actual productive output, it becomes easier to understand. Plugins, themes, documentation, templates, workflows, and tutorials all expand the platform’s value. The company is small, but the ecosystem around it is not.

In practice, the structure looks more like this:

a tiny core team plus a very large layer of community leverage.

That is why the company’s output feels so disproportionate to its size.

Obsidian is more than a note-taking app

Calling Obsidian a Markdown note app is not wrong. It is just incomplete.

A better way to understand it is as a system built around the movement of knowledge assets.

Layer 1: the local-first knowledge core

This is the foundation: - Markdown plain text, - local files, - no mandatory account to begin, - bidirectional links, - graph views, - long-term portability.

This is where trust starts.

Layer 2: the plugin system

One of Obsidian’s smartest choices was not trying to build every feature itself.

Instead, it built a platform that other people could extend. Once the plugin ecosystem matured, the company no longer had to personally cover every workflow. It only had to keep the foundation strong and the boundaries clear.

Layer 3: theme and workflow malleability

Power users do not just like Obsidian because it is powerful. They like it because it can be reshaped around how they already think.

Layer 4: Sync

Sync connects local-first ownership with modern multi-device continuity.

Layer 5: Publish

Publish turns the same knowledge assets into outward-facing websites, documentation, or public resources.

Together, these layers make Obsidian more than a note tool. It becomes a knowledge environment that can capture, organize, extend, synchronize, and publish.

What are Obsidian’s real advantages?

Its strength is not one feature. It is the way several strengths reinforce one another.

1. Architectural advantage

Local-first storage and open files create a rare mix of trust, portability, and lower central infrastructure burden.

2. Principle advantage

Many companies talk beautifully about values and then quietly build against them. Obsidian’s manifesto, privacy posture, monetization model, and licensing choices line up more than most companies’ do.

3. Community advantage

Its community is not ornamental. It actively expands what the product can do.

4. Brand advantage

“Your thoughts are yours.” “Files over apps.” “100% user-supported.” These are sharp ideas, easy to remember, and backed by real product choices.

5. Organizational advantage

A very small, highly asynchronous team with little meeting overhead can preserve clarity in ways that many larger companies cannot.

Why haven’t more companies built something like Obsidian?

This is one of the most revealing questions in the whole story.

On the surface, very little about Obsidian is impossible. Markdown is not proprietary magic. Backlinks are not mysterious. Graph views are not secret technology. Plugin systems are hard, but they are not unheard of.

What is hard to reproduce is the full combination.

First, most companies do not want to give up platform control

Obsidian’s core premise is that users keep their files and the platform does not own their knowledge assets.

That is admirable, but it also means giving up many of the incentives that modern software companies are built around:

• less direct data extraction,
• less lock-in,
• less dependence on server-side control,
• fewer ways to force growth through platform capture.

For many companies, that is not a technical barrier. It is a business model they simply do not want.

Second, most companies are not built to tolerate slow-burn products

Obsidian is not an instant mass-market product in the usual sense. It takes some learning. It asks users to develop habits. It becomes more powerful over time. It also benefits from a community that grows gradually.

A lot of startups and investors prefer products that are easier to standardize, easier to sell fast, and easier to scale through familiar growth narratives.

Obsidian is not that kind of product.

Third, most teams do not truly treat community as a co-building layer

Many companies say they have a community. What they really mean is that they have users and a forum.

Obsidian is different because the ecosystem actually extends the product. That requires openness, confidence, and unusually strong boundary-setting.

Fourth, it is hard to stay both restrained and complete

A local-first product can become too niche. A mass product can lose its principles. A platform can become too complicated. A privacy-first product can become commercially awkward.

Obsidian is unusual because it has managed to balance several of those tensions at once.

So it is not that no one thought of making something like Obsidian. It is that very few companies are willing to carry the full set of tradeoffs required to make the whole system work.

Can Obsidian’s success be replicated?

Yes, but not by copying it literally.

If someone says, “I’ll just build a Markdown, local-first, plugin-based app and become the next Obsidian,” they are probably misunderstanding the case.

Obsidian’s success is not the result of a feature checklist. It comes from several layers moving in the same direction:

• a stable product philosophy,
• an architecture that matches that philosophy,
• a user base that values ownership and control,
• a community with room to build,
• founders willing to stay disciplined,
• and an organization that resists the standard pressure to expand.

Remove any one of those and the outcome could look very different.

Still, parts of the model are clearly transferable.

What can be replicated?

• local-first architecture,
• user ownership over data,
• ecosystem leverage instead of building everything in-house,
• small-team consistency,
• monetizing value-added layers instead of monetizing data.

What is much harder to replicate?

• deep user trust,
• a strong community culture,
• years of consistent restraint,
• founder temperament,
• and the refusal to let funding logic rewrite the company’s direction.

So Obsidian is not a template so much as a signal. It shows that another kind of software company is possible, but only if a team is willing to accept the constraints that come with that choice.

Its core idea is bigger than note-taking

A lot of people describe Obsidian in terms of PKM, backlinks, or graph thinking.

Those are real parts of the product, but they do not quite reach the center.

The deeper idea is simpler:

knowledge should belong to the user, and software should help it grow without taking ownership of it.

That is why the product resonates so strongly with writers, researchers, developers, students, and serious knowledge workers. People are not only responding to features. They are responding to the feeling that the tool respects them.

Obsidian is not trying to own the user’s intellectual life. It is trying to support it.

That difference matters.

What is Obsidian’s core workflow?

Seen as a full system, the workflow is unusually clean.

1. Capture

Users create Markdown files locally with almost no startup friction.

2. Connect

Backlinks, tags, folders, and graph views turn isolated notes into a knowledge network.

3. Extend

Plugins and themes gradually transform the environment into a personalized workspace.

4. Sync

When multi-device continuity matters, Sync bridges that need without abandoning the local-first model.

5. Publish

When ideas need to go public, Publish turns notes into websites and outward-facing knowledge pages.

6. Reinvest

New workflows, templates, and plugins feed back into the ecosystem and make the platform stronger over time.

What makes this workflow powerful is that knowledge is not trapped at any one stage. The same asset can move across capture, organization, synchronization, and publishing without losing its identity.

Why does Obsidian matter so much in the AI era?

One of the most practical questions in software today is simple: how many people does it actually take to build and sustain a meaningful product company?

Obsidian offers a compelling real-world answer.

It did not rise because of AI. In fact, it had already demonstrated the power of a small, disciplined, highly leveraged company before AI tools dramatically lowered the cost of software production.

That makes the case more interesting, not less.

As code generation, testing assistance, design support, and workflow automation keep improving, the ceiling for what a small team can ship will keep rising. What once required 20 people may increasingly be done by five, eight, or ten.

From that perspective, Obsidian is not just a product success story. It is an early example of a future company shape.

A small team does not always have to be a temporary stage. Sometimes it can be the intended long-term form.

Closing thought

The most interesting thing about Obsidian is not the headline that seven people built a product used by more than a million people each month.

The real story is the unusual alignment underneath it.

• Because it is local-first, it does not need to turn user data into its main corporate asset.
• Because it does not depend on extracting data, it can make stronger privacy promises.
• Because its cost structure is different, it does not need to expand headcount linearly with growth.
• Because it is user-supported, it does not have to distort the product around venture expectations.
• Because the team stays small, product judgment remains unusually concentrated.
• Because the community is treated as real leverage, the platform keeps expanding beyond what payroll alone would allow.

Obsidian is not proof that fewer people are always better.

It proves something more useful:

when architecture, business model, organization, and product philosophy are all built on the same logic, a very small company can create something genuinely large.

That is why Obsidian is worth studying.