The Hermes + Obsidian + Claude Code Trinity: The Full System for Running a One Person Company

There is a specific moment that tells you whether someone is running a real one person company or just using a lot of apps.

It is the moment they get asked a question about their own business and they have to go dig for the answer. Check three different tools. Scroll back through old messages. Try to remember which note they wrote that idea down in.

A real system does not make you dig. It already knows.

This article is about the three tools that, stacked together correctly, remove the digging entirely. Obsidian holds everything you have ever thought, decided, or captured. Claude Code reads that vault and turns it into something you can actually talk to. Hermes Agent runs continuously in the background, gets better at its own job over time, and lives wherever you already are instead of demanding you open a new tab to use it.

Individually, each of these is a good tool. Stacked correctly, they become something closer to a company you run by yourself, with most of the operational weight carried by systems instead of willpower.

Here is the honest version of why this matters now and not two years ago. Earlier AI tools could each do one piece of this in isolation. A note app with AI search. A chatbot you could paste context into manually. A simple automation that ran the same script every day regardless of what actually happened. None of those pieces talked to each other, and none of them got better at their job over time. What changed is that Claude Code can now hold and act on an entire vault’s worth of context reliably, and agent frameworks like Hermes Agent can run unattended for real stretches of time while actually learning from what they did. The connective tissue between memory, processing, and action finally got strong enough to build a real system on top of it, not just a collection of clever individual tools.

The Problem With Running Solo

Every solo operator eventually hits the same wall. You are the founder, the marketer, the support team, the bookkeeper, and the person who has to remember everything, all at once. There is no second brain in the building except the one in your skull, and that one forgets things, gets tired, and cannot work while you sleep.

Most people respond to this by buying more tools. A project manager here, a note app there, a separate AI subscription for writing, another one for research. Now you have five places where knowledge about your own business lives, none of which talk to each other, and you have added a sixth job: remembering which tool has the thing you need.

The Trinity approach inverts this. Instead of more tools that each hold a slice of your business, you build one connected system where knowledge accumulates in a single place, gets processed by an agent that understands context, and gets acted on by a second agent that runs even when you are not looking at a screen.

Layer One: Obsidian as the Memory

Obsidian is the foundation, and its job is simple. Hold everything.

Every source you consume, every decision you make, every idea you have half formed in the shower, goes into the vault. Not organized perfectly. Not filed into the right folder immediately. Just captured, because captured beats perfect every time.

The structure that actually works in practice is deliberately minimal. A raw folder for anything you have not processed yet, articles, transcripts, screenshots of conversations, voice memo transcriptions. A wiki folder for the processed, linked, permanent version of your knowledge. And a single CLAUDE.md file at the root that tells Claude Code exactly how this vault works and what to do with anything dropped into it.

This structure matters because it creates a clear boundary between input and output. Raw is messy by design. Wiki is clean by design. The thing that moves content from one to the other is not you manually retyping notes at midnight. It is the next layer.

Layer Two: Claude Code as the Processor

This is where the system stops being a notebook and starts being intelligence.

Open your Obsidian vault in Claude Code and you have given an agent direct read and write access to everything you have ever captured. Drop a podcast transcript into raw and tell Claude to ingest it. It reads the transcript, pulls out the genuinely new ideas, checks whether they connect to anything already in your wiki, and either extends an existing note or creates a new one with proper backlinks.

This is fundamentally different from summarizing a document and forgetting it the moment the chat ends. Every source you feed it makes the next source easier to process, because Claude is working against an ever growing map of what you already know, not starting fresh every time.

The compounding effect here is the entire point. Month one, your vault is thin and Claude’s connections are obvious. Month six, you have hundreds of linked notes and Claude starts surfacing connections you would never have made yourself, an idea from a marketing book linking to a comment a customer made three weeks ago, both filed under the same underlying principle neither source named directly.

Practically, this layer handles three kinds of work for a one person company.

Knowledge capture. Every article, video, or conversation that touches your business gets distilled and filed automatically instead of read once and forgotten.

Decision logging. When you decide something, pricing, positioning, a process change, that decision and the reasoning behind it gets written down in a place you can actually find it again, instead of living only in your memory until it quietly contradicts itself six months later.

Drafting. Claude Code, working from your actual vault instead of a blank page, can draft emails, proposals, content, and documentation that already sound like you because it has your actual writing and decisions to draw from.

Layer Three: Hermes Agent as the Operator

Obsidian remembers. Claude Code processes. Hermes Agent acts, continuously, without you opening a laptop.

Hermes Agent is the open source AI framework behind tools like MaxHermes, and the detail that separates it from a typical assistant is the built-in learning loop. After completing a task, it evaluates its own process and, when the task was complex enough to be worth it, generates a reusable skill from that experience and stores it permanently. The skill list starts empty. A week of real use later, it has built a meaningful library of its own skills, and every repeated task after that runs faster because the agent is drawing on a method it already worked out for itself.

The other detail that matters for a solo operator specifically is where it lives. MaxHermes runs inside Telegram, not a separate browser tab you have to remember to open. Your operating agent exists in the same place you already spend time, with the same context available no matter which device you are on. Setup is a single click at agent.minimax.io, no server, no API keys, no terminal configuration.

For a one person company, this is the layer that actually buys back hours. You hand it a task before bed; it is finished by morning, and it has gotten a little better at that category of task than it was the day before. Customer inquiries get a first response without you being awake. Routine research gets compiled overnight. Follow ups go out on schedule without living on a sticky note.

How the Three Layers Actually Connect

The Trinity only works because each layer feeds the next one, not because the three tools happen to coexist.

Obsidian captures the raw material. A customer conversation, a competitor’s new feature, an idea you had on a walk.

Claude Code, with vault access, processes that raw material into structured knowledge and can draft the response, document, or content piece that the situation calls for, informed by everything else already in the vault.

Hermes Agent takes the routine, repeatable version of that workflow and runs it without a human in the loop, learning a faster path through it every time it repeats.

In practice this looks like a morning routine that takes ten minutes instead of two hours. You ask your vault for a status update across every active project, pulled from notes you actually wrote, not from memory. You review what Hermes handled overnight while you slept. You feed yesterday’s new information into raw and let Claude Code do the filing. Then you spend your actual working hours on the parts of the business that genuinely need a human, which by this point is a much shorter list than it used to be.

What This Replaces

It is worth being specific about what a properly built Trinity setup actually removes from your day, because the value is easy to understate in the abstract.

It replaces the morning spent rereading old notes to remember where a project left off, because the vault already has the answer and Claude Code can summarize it in seconds.

It replaces hiring a virtual assistant for routine inbox triage and follow ups, because Hermes Agent handles the repeatable slice of that work and gets faster at it the longer it runs.

It replaces the slow creep of knowledge loss that happens when a solo founder’s best thinking lives only in their head, vulnerable to a bad week, a bad memory, or simply moving on to the next shiny idea before writing the last one down properly.

It does not replace judgment. Pricing decisions, hard conversations with customers, the actual creative or strategic core of your business, those still need you. The Trinity exists to clear everything else off your plate so that judgment is the thing you are spending your time on, rather than the thing you are too exhausted to apply properly by the time you get to it.

Where This Breaks If You Build It Wrong

The Trinity fails in predictable ways, and almost all of them trace back to skipping the order above or skipping the boring maintenance that keeps each layer healthy.

The most common failure is treating Obsidian as a dumping ground with no eventual processing step. Raw piles up. Nothing moves to wiki. Six months later you have a thousand unprocessed notes and the vault has become exactly the kind of mess it was supposed to prevent. The fix is not a better folder structure, it is a standing habit, even just once a week, of actually running the ingestion step on whatever piled up.

The second failure is giving Claude Code vague instructions in CLAUDE.md and assuming it will infer your preferences. It will not, not reliably, and the cost of that ambiguity compounds the same way the benefit does. A CLAUDE.md that says “organize notes well” produces inconsistent filing. A CLAUDE.md that says exactly which folder structure to use, how to handle duplicate topics, and when to create a new note versus extend an existing one produces a system you can actually predict.

The third failure is handing Hermes Agent a task with no real verification step and assuming overnight autonomy means unattended trust. The learning loop makes the agent better at tasks it has done before, but that is a reason to start with low stakes, reversible tasks, not a reason to skip checking its work for the first few weeks. Build trust the same way you would with a new hire. Review closely at first. Loosen the leash as the track record earns it.

What This Looks Like Running for Real

Picture a solo course creator running this stack three months in.

A student leaves a confusing piece of feedback on a video. It gets dropped into raw that night. Claude Code reads it, checks the wiki, and finds two earlier notes where similar confusion came up around the same topic, something the creator had genuinely forgotten flagging before. The note gets updated with a clear pattern, not just one isolated complaint, and a suggested script fix gets drafted alongside it.

The next morning, Hermes Agent has already sent a personalized reply to the student overnight, drawing on the tone and structure the creator has used in past replies, because that pattern was something it learned in its first two weeks of running. The creator reviews it, makes one small edit, and moves on with their day in under two minutes, a task that used to take fifteen and a moment of full attention they did not have to spare.

None of this required a team. It required three tools that were actually talking to each other, built in the right order, given a few months to accumulate enough history to be useful.

That is the entire bet behind the Trinity. Not that AI replaces the founder. That a founder who is the entire company finally gets a memory that does not forget, a processor that does not get tired, and an operator that works the night shift, so the only thing left requiring a human is the part that actually needed one in the first place.

You do not need all three layers running perfectly on day one. Build them in order, because each one makes the next one more useful.

Start with Obsidian. Create the vault. Build the raw and wiki folders. Spend a few days just capturing, badly if necessary, until the habit of dropping things into raw feels automatic.

Add Claude Code once you have something worth processing. Write the CLAUDE.md file that tells it how your vault is structured and what ingestion should look like. Feed it your first real source and watch what it does with it before you trust it with more.

Bring in Hermes Agent last, once you know which of your routine tasks are actually repeatable enough to hand off. The temptation is to automate everything immediately. Resist it. Automate the task you already do the same way every single time, prove the loop works, then expand.

The compounding only shows up if you stay with it past the first week, when the vault is still thin and the agent has not built any skills yet. That early period feels like more setup than payoff. It is not a sign the system does not work. It is the system before it has anything to compound on top of.

By month two or three, the gap between this setup and running everything manually stops being subtle. That is the point where a one person company starts to feel less like one exhausted person and more like an actual operation, even though the headcount never changed.