Skip to main content
Empirical logoEmpirical

Bring your notes

Your notes already exist.
Empirical should meet them there.

If you already keep a second brain in Obsidian, Logseq, Markdown, or Notion, the right move is not starting over. The right move is turning the durable parts of that system into reusable AI context.

Create account firstSign in and come back

Setup is gated behind signup. You can read the plan here, but actual workflow links stay locked until you have an Empirical account.

What this page does

  • Show the fastest workable paths for the note tools people already use.
  • Separate what is available now from what is only planned.
  • Send signed-in users into setup docs instead of vague product promises.

Watch the flow

Show the product with a staged walkthrough.

This demo is intentionally controlled. It shows the exact story we need: note capture, memory extraction, chat payoff, and coding payoff, without pretending the note sources are already wired into a live connector.

Video spec

`9:16`, `1080x1920`, `30s`

Beat structure

Obsidian -> Empirical -> ChatGPT -> CLI -> end card

Open staged walkthroughRead the voiceover script
Empirical link: selected line -> saved memory

Capture the note

Notes can come from anywhere.

voice note

captured

phone transcript · 8:14 AM

When I don’t know

the next action,

I keep thinking

about it all day.

meeting note

chosen

typed during review

Deadline moved

to Thursday, need

to cut two slides.

travel plan

captured

trip checklist · reminder

Need one shared plan

for flights, hotel,

and arrival timing.

obsidian vaultdaily/2026-06-27
local note

selected from your notes

Deadline moved to Thursday, need to cut two slides from the deck.

Save for reuse

Staged walkthrough

Short vertical concept demo for notes -> Empirical -> ChatGPT -> CLI

Open live demoRead the script

Best pathway

Start with docs now.
Add hosted connectors later.

This is the right scope. A clean setup hub plus source-specific guides gives users a usable path immediately. Hosted connectors can come after we prove which workflows people actually use and which parts should be automated.

Current rule

Only Obsidian, Logseq, plain Markdown, and a manual Notion path should be live here today. Apple Notes and Google Docs should stay marked as coming soon until there is a workflow worth shipping.

Available now

Pick the notes system you already trust.

Obsidian

Local workflow

Best fit today. Keep your vault where it is, decide what is durable, and move the right notes into Empirical on purpose.

Sign up to continue

Logseq

Local workflow

Useful if your graph already contains project decisions, research, and reusable context you want available in AI tools.

Sign up to continue

Plain markdown

Folder workflow

The cleanest lowest-friction path. Works well if your notes already live in files and you want a simple repeatable routine.

Sign up to continue

Notion

Manual workflow

Supported as a deliberate export-and-curate path for now. No one-click hosted sync yet.

Sign up to continue

Coming soon

Not every notes source deserves a rushed connector.

Waiting for a cleaner path

Apple Notes

Coming soon

Worth supporting, but not practical to promise until we have a clean extraction and refresh model.

Google Docs

Coming soon

Coming later. We need a workflow that is actually useful, not just an API connection that creates more cleanup work.

Read first

Why second-brain users need this

The blog post frames the problem correctly: people who already keep notes are the exact users who should not have to re-explain themselves to every AI tool.

Open the blog

Setup docs

Keep the instructions clean

Source-specific docs let us explain the workflow clearly without bloating the landing page or faking product depth.

Browse docs

Product stance

Avoid fake one-click magic

The first useful version is a guided workflow hub. Once those paths are proven, we can automate the parts that are repetitive instead of automating the wrong thing first.