Building for One User

Offledger is a personal finance app that nobody will ever use except me. SQLite database in iCloud Drive, operated through Claude Code slash commands. No server, no subscription, no data leaving my machine. I built it because every finance app wants my bank credentials and I don't want to give them.

The workflow: download CSV from my bank, run /import, let Claude categorise the transactions against my existing patterns, review the edge cases. Budget planning, spending analysis, trend lines — all through natural language queries over my own data. The UI is Claude Code itself.

Obsi is similar. It's a CLI for my Obsidian vault. obsi "quick note" captures a thought. obsi find "search term" finds it later. obsi daily opens today's daily note. I could use Obsidian's built-in features for all of this but the CLI is faster when I'm already in the terminal, which is always.

Falcon wraps fal.ai for image generation. falcon "prompt" --og generates a social share image. falcon --vary creates variations of the last generation. falcon --up upscales it. Three commands that replace a whole web UI.

Sift sorts email. Bird posts tweets. Claudestatus checks my API usage across accounts. None of these tools have users. None of them need users.

The pattern is always the same: I find friction in my workflow, I build a CLI to eliminate it, and then I use it every day until it becomes invisible. The tools compound. Falcon generates images for Siteinspire posts. Obsi captures ideas that become notes on my personal site. Sift keeps my inbox clear so I can focus on building the next tool.

I think the best software comes from building for yourself first. You know the requirements because you live them. You know the edge cases because you hit them. And you have the most demanding user possible — someone who will actually switch back to the manual process if the tool isn't better.

Not everything needs to be a product. Sometimes a tool for one person is exactly the right scope.