Build a Second Brain Free and Local Before Paying for Sync

Updated 29 October 2026 · obsidian, knowledge-management, small-business, note-taking

You can build a second brain for your small business with markdown files and a few tools, and the core of it costs nothing. Obsidian is free and local, so decide what stays local before you pay for Sync. That one decision shapes your storage bill, your privacy risk, and how your team handles shared client and process notes.

Most guides stop at the pricing table. This one starts there and then answers the question a team owner actually has. Which folders should leave the office laptop, which should never leave it, and what rules stop a shared folder of text files from turning into a mess?

What a Markdown second brain is for a small team

A second brain for a small business is a folder of plain text notes that holds what currently lives in people's heads. That means how you onboard a client, what each customer prefers, and which supplier to call when the printer dies on a Friday afternoon.

Markdown is ordinary text with light formatting. A hash mark makes a heading and an asterisk makes a list item. Any text editor on any computer can open these files, so your knowledge outlives whichever app you use to read it this year. That is the main reason to choose Markdown over a closed database.

Obsidian is the app most people pick for this job. According to Obsidian's own pricing page, checked on 26 to 27 October 2026, the app is free, needs no sign-up, and states no limit on note count or local storage. It reads a folder on your disk, which Obsidian calls a vault, and shows your notes with clickable links between them.

The "few tools" part of the promise is honest. For most small teams the stack is the editor, a way to move files between machines, and a backup. Everything else is habit.

How to build a second brain for your small business, step by step

Start with a single vault, a handful of top-level folders and a single note template, and hold off on plugins until the team has used the setup for a few weeks. The order below matters, because the folder structure decides what you can safely sync later.

1. Create the vault on one machine first, so the structure has an owner. Pick the person who writes the most process notes and let them set it up alone before anyone else joins.
2. Split top-level folders by sensitivity before topic, so sync choices stay simple later. A folder of internal how-tos and a folder of client records carry very different risks, and mixing them makes every later decision harder.
3. Write one template for clients and one for processes, so notes look the same no matter who wrote them. A client note might hold contact details, what they bought, their preferences and open issues. A process note might hold when to use it, the steps, who owns it and the date it was last reviewed.
4. Link notes instead of copying text, so a fix in one place fixes it everywhere. If your refund process changes, you update one note, and every client note that links to it stays correct.
5. Keep a single inbox note for quick capture, so nothing gets lost while someone is busy. Anyone can drop a rough line there, and the vault owner files it once a week.
6. Set up a backup before you set up sync, so a bad edit cannot wipe your only copy. Sync copies changes, including mistakes and deletions, to every device. A separate backup on a schedule protects you from that.

Decide what stays local before you pay for Sync

Sort every folder into one of three groups before anyone enters a card number: safe to sync, stays on one machine, or lives somewhere else entirely. This is the step the top search results skip, and it is the one that saves you money and trouble.

Notes that can safely sync

Notes that can safely sync are the ones that would be awkward to leak but not damaging. Process documents, templates, supplier lists, internal how-tos and general meeting notes usually fit here. These are also the notes your team needs on every device, so they are the ones that justify paying for sync at all.

Notes that should stay local

Notes that should stay local are anything a client trusted you with personally. Think of client records with personal details, health or financial information, contract terms, and staff matters like reviews or sick leave. If a client contract says data must stay on your own systems, it belongs here too.

The simplest way to guarantee a folder stays local is to keep it in a separate vault that you never connect to any sync service. Do not rely on remembering to exclude a subfolder. A separate vault makes the boundary physical, and anyone opening it can see it is different.

Passwords never belong in either vault. Put them in a proper password manager, and our guide to picking a password manager for a one-person business covers what to look for.

Files that should live somewhere else

Large files should live in the file storage you already pay for, with a link from the relevant note. Videos, raw photos, design files and scanned contracts eat sync storage fast.

The numbers explain why. Obsidian's help pages, checked on 26 to 27 October 2026, list a 5 MB maximum file size and 1 GB of total storage on Sync Standard. The same help pages say the storage limit is account-wide across vaults, and that attachments and version history both count toward it. A folder of scanned PDFs and a year of edits can fill a small plan long before your text notes do, so re-check those limits before you plan around them.

What Obsidian charges, as of October 2026

The Obsidian app is free, and you pay only if you want the vendor's Sync service (priced per user) or Publish (priced per site). Every figure in the table below comes from Obsidian's own pricing and Sync plan pages as checked on 26 to 27 October 2026, so confirm it on the official page before you buy.

Because Sync is priced per user, multiply the per-user figure by the number of people who actually need synced access. That is often fewer than your headcount. A part-time bookkeeper who reads a single process note a month may be fine with a printed copy or an exported file.

Treat anything you put on Publish as public unless Obsidian's own documentation tells you otherwise. Client material has no place there.

One more check belongs on your list before rollout. Third-party write-ups we read disagree about whether Obsidian requires a paid commercial license for company use, so read the vendor's current license terms yourself before you put it on staff machines.

When colleagues edit the same note

Plain text files have no built-in locking, so you need a team rule for shared edits instead of trusting software to merge them cleanly. The sources we checked do not describe how Obsidian Sync settles every conflict, so do not design your process around it.

These rules keep shared Markdown calm:

1. Give every note a single owner, so there is always someone who decides. Put the owner's name in the template. Others add suggestions to the inbox note and the owner merges them.
2. Make client history append-only, so nobody overwrites anyone else. Each person adds a dated line at the bottom of the client note and never rewrites earlier lines.
3. Let a single person write up each meeting, so you get one clean record. If your meetings already go through an AI note taker, paste its summary into a fresh dated note. Our comparison of AI meeting note takers for small teams covers which ones export clean text.
4. Review process notes on a schedule, so stale steps get caught. The "last reviewed" field in the template turns this into a quick search instead of a guessing game.

This discipline is the real operating cost of a Markdown second brain. The software is cheap, and the habits are what make it work.

Pros and cons of a Markdown second brain

The short version is that you get ownership and low cost, and you pay for it with setup work and discipline.

What works in its favor:

1. Your files stay readable without the app. If Obsidian vanished tomorrow, every note would still open in a basic text editor.
2. The core costs nothing. Obsidian's pricing page, checked on 26 to 27 October 2026, lists the app as free with no sign-up, so you can trial the whole structure before spending anything.
3. Local vaults keep sensitive notes off third-party servers. A separate vault you never sync is the clearest privacy boundary a small team can set.
4. Plain text works well with AI assistants. You can paste a process note into any chat assistant and get a usable answer, though you should keep client data out, as our piece on how far to trust an AI chatbot with customer data explains.

What works against it:

1. Structure is entirely your job. The vendor material we read describes notes, sync and publishing, and nothing resembling client records, staff permissions or task assignment.
2. Attachments hit storage limits fast. Obsidian's help pages, checked on 26 to 27 October 2026, count attachments and version history toward an account-wide limit.
3. Per-user pricing adds up as you grow. Each new teammate who needs synced access adds a seat at the per-user rate on Obsidian's pricing page, so re-check it as of the day you hire.
4. Shared editing depends on team habits. Without owners and append-only rules, two edits to the same note can leave you unsure which version is right.
5. Someone has to tend it. A vault nobody files and reviews becomes another inbox nobody reads.

Who should not build it this way

Some teams are better served by a hosted workspace than by a folder of Markdown files.

You should look elsewhere if you need per-person permissions on client folders, because nothing in the vendor material we read describes that. You should also look elsewhere if your team thinks in databases with statuses, filters and board views. A tool like Notion fits that style better, and our Notion AI review for solo founders covers what it does well and where it costs more.

A Markdown vault is also a poor fit if nobody on your team will own it. The system is only as good as the weekly filing session. Finally, if your work is mostly large media files, the notes are a small part of your problem, and your storage plan matters far more than your note app.

FAQ

Is Obsidian really free for a small business?

The app itself is free and needs no sign-up, according to Obsidian's pricing page checked on 26 to 27 October 2026. You pay only for optional Sync or Publish. Third-party sources disagree on whether company use requires a commercial license, so read the vendor's current license terms before rolling it out to staff.

Do I need Obsidian Sync to share notes with my team?

You need some way to share the vault folder, and Obsidian Sync is the vendor's own option for that. Because a vault is an ordinary folder of files, other folder-sharing methods can work too. If you go that route, you take on the conflict and backup questions yourself.

How much storage does a Markdown second brain need?

Text notes are tiny, so attachments and version history decide how much you use. Obsidian's help pages, checked on 26 to 27 October 2026, list 1 GB on Sync Standard and 10 GB on Sync Plus, with both attachments and version history counting toward the limit. Keep large files in your existing storage and link to them from notes.

Can I use AI tools with my Markdown notes?

Yes, because plain text pastes cleanly into any chat assistant, which makes process notes easy to summarize or rewrite. Keep client personal data out of those chats unless you have checked how the provider handles it. Process notes from your synced vault are the safer material to use.

What should never go into a shared second brain?

Passwords, payment details, ID numbers and anything a client contract says must stay on your systems should stay out of a synced vault. Passwords belong in a password manager. The other items belong in a local-only vault or the system of record your contract names.

Related reading

1. n8n vs Zapier for small business automation, if you want notes to trigger tasks later.
2. How to turn meeting transcripts into action items with n8n, for teams whose notes start as calls.
3. Best AI writing tools for small business, for drafting the process notes themselves.

Verdict

A Markdown vault in Obsidian is the cheapest durable way for a small team to write down what it knows, as long as someone owns it and the team follows simple editing rules. Spend the first week sorting folders into synced, local-only and stored-elsewhere, and only then look at the per-user Sync price on Obsidian's pricing page as of the day you buy. Obsidian is free and local, so decide what stays local before paying for Sync, and you will build a second brain for your small business with markdown files and a few tools without paying for storage you never needed.

About the author

The Tool Signal is written by a small team that runs AI automation for its own publishing every day and reviews tools for owners of small businesses. Nobody on the team ran Obsidian Sync for this piece. Every price and limit above is the vendor's word, and each one is listed with its source and check date in the box below this article. The setup advice describes how plain Markdown files behave and how small teams keep shared documents in order, with no invented test results. We re-check vendor pages when prices move, so you can trust the figures here to be dated and sourced as you build a second brain for your small business with markdown files and a few tools.