Your whole work life, on your own machine
A personal operating system that runs on your own machine
Contacts, projects, email, calendar, a meeting analyst, a decision journal — all working together, all stored on your own computer, all running on the Claude subscription you already pay for. No servers, no per-seat fees.
Most people run their work life on a pile of rented apps that each hold a slice of their data, don't talk to each other, and bill every month.
One local-first personal platform — contacts, projects, email, calendar, a meeting analyst, and a decision journal — all working together on your own machine, on a subscription you already have.
| Before | After | |
|---|---|---|
| Where your data lives | scattered across a dozen companies' clouds | on your own machine, owned by you |
| How the tools connect | they mostly don't — you copy between them | they share one foundation and feed each other |
| What it costs to run | a stack of monthly subscriptions | close to nothing, on a subscription you already have |
| Who controls it | each vendor, on their terms | you, locally |
| Getting more useful over time | each app improves in isolation | the pieces compound as they share more |
A personal setup that used to be a pile of subscriptions, with your data scattered across other companies' servers, becomes a single system you own and run yourself. The ongoing cost is close to nothing, and the pieces reinforce each other because they share one data layer — the meeting analyst can feed your contacts, your contacts can feed your decision journal — instead of each living in its own walled-off app.
What I built
Software of You — a local-first personal operating system. "Local-first" means it runs and stores your data on your own computer rather than in a company's cloud, so you own and control it.
- The pieces. Contacts (a personal CRM), project tracking, email, calendar, a meeting analyst (which makes sense of your meetings), and a decision journal (a record of choices and why you made them).
- One shared foundation. All of those sit on a single local data layer, so they genuinely work together rather than being six disconnected apps in a folder.
- They feed each other. Because they share that foundation, the meeting analyst can update your contacts, your contacts can inform the decision journal, and so on — no copy-pasting between tools.
- Runs on what you have. The intelligence runs on Claude Code (Anthropic's coding tool) using the Claude subscription you already pay for — there are no servers to rent and the ongoing cost is close to nothing.
- A real app on top. A native macOS desktop app sits over all of it, so it feels like proper software, not a pile of scripts.
It's a "hybrid" because it's two things at once: a Claude-native system (the intelligence and the workflows) and standalone software (the local platform and the desktop app).
Why it matters
You own your work life again — all of it, in one place, on your own machine, for almost nothing on top of a subscription you already have. Instead of renting a dozen tools that each hold a fragment of your data and refuse to talk to each other, you run one system where the parts reinforce each other and get more useful the more you use them.
Before AI, building a connected personal platform like this meant either stitching rented services together forever — fragile, endless work — or paying a team to build it. Now one person runs the whole thing locally, and because everything shares one foundation, the meeting analyst feeds the contacts, the contacts feed the decision journal, and the system compounds instead of fragmenting.
The hard part isn't building any single piece — plenty of apps do contacts or projects. It's getting all of them to genuinely work together without becoming a fragile mess of integrations. The usual way to connect tools is to wire their separate services together with glue code that constantly breaks; do that across six tools and you've built a maintenance nightmare. The answer here was to put everything on one shared local data foundation from the start, so the pieces don't have to be stitched together — they already speak the same language. That's what lets the meeting analyst feed the contacts and the contacts feed the decision journal, and it's why the whole thing compounds instead of fragmenting.
The real shift here is ownership plus interoperation at almost no ongoing cost — building a connected personal platform used to mean either gluing rented services together forever or paying a team to build it. Now one person runs the whole thing locally on a subscription they already have, and because everything shares one foundation, it only gets more useful the more it's used.
How the separate pieces share one local data foundation — so they genuinely work together instead of being a folder of disconnected apps — is the design that makes it more than the sum of its parts.