Loading video...

Video Failed to Load

Go Home

A developer opened a law firm’s token bill and realized 20 users were burning $61,920 just to ask questions their files could answer offline. $61,920 cloud TCO. $23,180 local TCO. 4.12-month break-even. 20 employees. 0 client files uploaded. The old RAG pitch breaks when legal files, medical notes, and...

25,799 views • 2 months ago •via X (Twitter)

34 Comments

marfin's profile picture
marfin2 months ago

it's called an alpha move

Gusler's profile picture
Gusler2 months ago

20 employees, 0 client files uploaded, thats the whole compliance moat

0xSlyth's profile picture
0xSlyth2 months ago

this is how you build real value

Fluixo's profile picture
Fluixo2 months ago

local nodes are lowkey a game changer for privacy

shiqway92's profile picture
shiqway922 months ago

this is a strong business case

kvinsi's profile picture
kvinsi2 months ago

good figure for local tco

Muhammad Ali's profile picture
Muhammad Ali2 months ago

$61K cloud vs $23K local looks compelling until you price in the engineer maintaining the local stack, handling model updates, and debugging sync failures at midnight. The TCO calculation is missing the human ops line item that makes or breaks the break-even math.

量化不玄学's profile picture
量化不玄学2 months ago

全自动量化交易工具,多个AI部署,自动下单平仓,稳定收益,需要的可以联系

Muhammad Ali's profile picture
Muhammad Ali2 months ago

The $61K vs $23K math shifts when you add ops cost. The real break-even is month 8 once you include hardware failures and the engineer fixing things at midnight. What's the actual uptime on self-hosted RAG setups?

Sandra Clark's profile picture
Sandra Clark2 months ago

the way this was put together shows real skill

Dekos's profile picture
Dekos2 months ago

He's a cool employee if he managed to notice that.

XXI's profile picture
XXI2 months ago

The firm paid to ship its own secrets through someone else's data center. the local box shipped nothing. same question, opposite side of the compliance memo.

wast3's profile picture
wast32 months ago

Is this yet another second brain?

Muhammad Ali's profile picture
Muhammad Ali2 months ago

Ran something similar and the real savings weren't in tokens but in liability. Once client files never leave the building, compliance audits go from nightmare to checkbox. Has anyone actually calculated the hidden GDPR exposure cost of cloud RAG setups for legal firms?

Mura's profile picture
Mura2 months ago

i didn't believe it's possible

ALEXYZ's profile picture
ALEXYZ2 months ago

$61K burned. Local wins. Math settled it.

Ridark's profile picture
Ridark2 months ago

Real alpha in the post, thanks, are you planning a stream on the topic?

monokern's profile picture
monokern2 months ago

its very smart system

unchosen.eth's profile picture
unchosen.eth2 months ago

data privacy will drive local ai adoption

shmidt's profile picture
shmidt2 months ago

this is the move, local-first infrastructure actually pencils out

Mikadzyki🌙's profile picture
Mikadzyki🌙2 months ago

privacy finally has ROI

Muhammad Ali's profile picture
Muhammad Ali2 months ago

$61K cloud vs $23K local is compelling math until you factor in the ops cost of maintaining local infrastructure. The real break-even shifts to month 8 when you include the first hardware failure and the engineer who has to fix it at midnight. What's the actual uptime on self-hosted setups?

Nekt0's profile picture
Nekt02 months ago

alpha bro

Gipp 🦅's profile picture
Gipp 🦅2 months ago

local node here is on topic

Spivach's profile picture
Spivach2 months ago

thing that pays off a million times more than you invested in

John Anderson's profile picture
John Anderson2 months ago

if procrastination had a mascot it would be me watching this

Muhammad Ali's profile picture
Muhammad Ali2 months ago

$61K cloud versus $23K local looks compelling until you price in the engineer who maintains the local stack, handles model updates, and debugs Obsidian sync failures at midnight. The break-even is real but the total cost of ownership calculation is missing the human ops line item.

Anthony Campbell's profile picture
Anthony Campbell2 months ago

i know something about this video that most people don't...

Fokki's profile picture
Fokki2 months ago

smart move

kaminoontee's profile picture
kaminoontee2 months ago

the biggest AI opportunity isn't replacing employees, it's replacing information friction

Muhammad Ali's profile picture
Muhammad Ali2 months ago

Ran something similar with a legal client and the real savings weren't in tokens but in liability. The moment client files never leave the building, your compliance audit goes from a nightmare to a checkbox. Has anyone calculated the hidden cost of GDPR exposure with cloud RAG setups?

Midwest Products, Inc.'s profile picture
Midwest Products, Inc.2 months ago

Where was thsi filmed it looks like a whole movie set

Jiji Hardt's profile picture
Jiji Hardt2 months ago

👍🙌💯

Kum Mehtani's profile picture
Kum Mehtani2 months ago

if you had to show one video to prove x is worth it, would this be it

Related Videos

THIS GUY BUILT AN AUTONOMOUS AI AGENT OUT OF CLAUDE CODE + OBSIDIAN and this is way more interesting than another “use AI to take notes” demo the trick is simple: Obsidian is not the writing app here. it becomes the agent’s memory, task board, and context folder. Claude Code is not just answering prompts. it reads the vault, edits files, follows instructions, and keeps moving through the work like a junior operator with a filesystem. the reusable setup looks like this: 1. create an Obsidian vault for one project 2. keep goals, rules, tasks, decisions, and references as markdown files 3. point Claude Code at the folder 4. give it a clear operating loop: read context → choose next task → execute → write back what changed 5. use the notes as persistent memory instead of re-explaining the project every chat that’s the part people miss. the “agent” is not magic. it’s the boring combination of: - local files - explicit rules - task state - write access - a model that can run through the repo/vault Obsidian makes the memory human-readable. Claude Code makes the memory executable. that combo is why the video worked: it turns a notes app into an operating surface for actual work. best use cases: - content systems - research vaults - coding projects - client ops docs - personal knowledge bases that need actions, not just storage the caveat: if your vault is messy, your agent becomes messy too. folders, naming, “done” criteria, and forbidden actions matter more than the prompt. but once the structure is clean, this is one of the easiest ways to build an agent that remembers what happened yesterday without paying for a full custom app.

kocer

30,403 views • 2 months ago

THIS GUY BUILT A BUSINESS SECOND BRAIN WITH CLAUDE CODE + OBSIDIAN IN 3 STEPS Most teams do not need another Notion workspace. They need a place where the company can remember how it works. The video shows a simple setup: 1. Create one empty folder called second brain. 2. Split it into 3 buckets: raw new knowledge wiki 3. Let Claude Code turn messy company material into connected notes. The useful part is the separation. Raw is where your existing stuff goes: SOPs, sales docs, process notes, client delivery checklists, old Loom summaries, onboarding docs. New knowledge is where fresh outside material lands: articles, clips, tactics, examples, market notes. Wiki is the cleaned version: concepts, roles, processes, SOPs, gaps, reusable decisions. That is where Claude Code becomes more useful than a normal chat window. Instead of asking it to remember random context forever, you give it a folder it can read, edit, and reorganize. Then Obsidian becomes the human interface. The Obsidian Web Clipper captures useful pages into the vault. Claude Code ingests them. The wiki gets updated. Then you can ask questions like: “Does my current workflow actually hold up?” That is the real point. Not “AI notes.” A business memory system that can compare what you do today against new information tomorrow. The caveat: this is not magic company intelligence. If your raw docs are vague, outdated, or full of tribal knowledge, Claude will organize weak inputs into cleaner weak outputs. You still need naming rules, review habits, and someone responsible for deleting junk. But the setup is refreshingly practical. Folder first. Clipper second. Claude Code as the maintainer. No giant knowledge base migration. No complex setup. Just a local vault that can slowly turn scattered business memory into something searchable, editable, and actually reusable.

kocer

16,698 views • 2 months ago

Andrej Karpathy keeps his entire second brain in Obsidian 1 folder of plain text files, nothing else. Here’s the exact setup, free, that turns 1 vault into a brain you can actually query. Why most “second brains” die: Notion is a database you forget to open, ChatGPT memory wipes itself after 30 messages, and both lock your notes inside their cloud. Karpathy rule is the opposite: your notes are the 1 dataset nobody else on earth has, so keep them in plain markdown, own them forever, and let the AI read them later. 3 phases. Phase 1 — Capture with 0 friction. Install Obsidian free, local, 1 hotkey to a daily note. Dump everything into it: ideas, links, quotes, 2-line thoughts, no folders, no tags, no system. Target is 5 notes a day. Phase 2 — Let the graph connect itself. Install Smart Connections and it runs embeddings on every note you’ve ever written, so 2 notes you wrote 4 months apart and never linked by hand suddenly surface as neighbors. That’s the fireworks in the 3D graph each burst is a cluster of ideas your brain forgot it owned. Phase 3 — Query your brain. Point Claude at the vault and ask: “What did I actually think about X across all my notes?” It answers from 1,200 of your own notes, not the internet your taste, your edge, your dataset. The realistic curve looks like this: Week 1 — 40 notes, graph looks empty, feels like a waste. Month 1 — 300 notes, first real cluster forms. Month 3 — 1,200 notes, and the embeddings start surfacing links you’d long forgotten. Month 6 — you stop googling your own past ideas and just ask the vault. Before — 9 tabs, 3 note apps, 0 memory. After — 1 folder, 1,200 notes, 1 brain that compounds. The gap between people who consume and people who compound isn’t talent, it’s architecture. You build your own life so choose the right path.

Spike 1%

16,390 views • 2 months ago

Obsidian + Claude Code turned a 4,300-note vault into a second brain that answers back. Most people use Obsidian as a graveyard. You save 40 highlights a week, link nothing, and reread maybe 2% of it. The knowledge is there the retrieval is dead. Claude Code fixes the retrieval, because your vault is just a folder of markdown files and Claude Code lives in folders. The whole setup takes 20 minutes: Open a terminal inside your Obsidian folder and run Claude Code no plugins, no API glue, no export step. It reads all 4,300 files natively. Then drop a CLAUDE.md at the vault root explaining your structure: where daily notes live, how you tag, what your MOCs are. Now every session starts with context instead of chaos. From there you just talk to your vault: > "find every note where I mentioned churn and write a summary with backlinks" > "read my last 30 daily notes and list the 5 ideas I keep circling but never ship" > "build a MOC for everything tagged startup-ideas and link the orphan notes into it" It writes new notes straight into the vault with proper [[wikilinks]], and they show up in your graph view 10 seconds later. The boring layer automates too one command cleans broken links, one merges duplicates, one turns 6 months of meeting notes into a single decisions log. Work that used to eat a Sunday now runs while you make coffee. Before: 4,300 notes, 900 orphans, search by keyword and prayer. After: an agent that read everything you ever wrote and drafts in your own voice, from your own sources, with receipts. People pay $30/month for AI note apps with 10% of this. You already own the other 90%. Your notes stopped being storage. They started being staff.

Spike 1%

18,223 views • 2 months ago

THIS GUY CONNECTED HIS AI AGENTS TO HIS OBSIDIAN AND BUILT A BRAIN THAT LEARNS ON ITS OWN. HERE'S HOW TO BUILD IT Obsidian is just markdown files sitting in a folder. That turns out to be the perfect memory for an AI agent, because an agent can read and write those files directly. He wired his agents into the vault so they pull context from it, do the work, and write what they learned back. The notes aren't the point. The loop is, and it gets sharper every cycle How to build it: 1. Point an agent at your vault. The fastest way, no plugins, no API keys: open a terminal and run npx obsidian-mcp /path/to/your/vault. That exposes your Obsidian folder to Claude as a tool it can read, search, and write to. Add it to your Claude Code or Cowork config and restart 2. Confirm it can see the brain. Ask it: "list the notes in my vault and summarize what's in them." If it reads them back, the connection is live. Now it starts every task with everything the vault already holds instead of from zero 3. Give each agent one job and a write-back rule. Tell it: "research this, then save what you found as a new note in /brain with links to related notes." One agent researches, one summarizes, one plans. Each writes its output back into the vault 4. Close the loop. Add one line to every agent's instructions: "read /brain before starting, write your result back when done." Now each task leaves the vault richer, and the next run reads that before it works. It compounds instead of resetting 5. You only steer. Review what the brain produces, point it at the next thing. The agents handle the reading, writing, and connecting The edge isn't better notes. It's a brain that feeds itself, so the work gets sharper every cycle instead of starting over Bookmark this

Yarchi

58,549 views • 3 months ago