Insights on AI, automation, and building the future of work

Seven systems for shipping with Claude Code

Your Zettelkasten is a museum

Persistent memory across every Claude session

7 tools built for AI memory, not workspaces

Seven templates worth installing

A second brain that lives in your terminal

Tools, courses, and configured systems compared

Why every "Obsidian + Claude Code" tutorial is solving the wrong problem

Why the prompt isn't the unit of work anymore

You're still spending Monday morning re-explaining your role, clients, and preferences to an AI that can't remember you from last week. Here are 20 specific things a configured Second Brain does that your current setup cannot.

After helping 108 people build their AI work system, I rebuilt everything.

Access is not understanding

Adapted from my fireside chat at South Summit Brazil 2026

A day inside the system that runs my business

CRM, email automation, blog publishing, client delivery, accounting, content creation. 30 systems. 12 connections. One terminal.

A real case study: 1,001 transactions, 5 bank accounts, one session.

After 1,164 days of daily AI use, I cut from $600/mo to $20. Output went up. The counterintuitive lesson: context depth beats tool breadth every time.

Two layers. Most people build one.

A software engineer's memo on 20+ papers about AGENTS.md, context files, and AI agent productivity

You can solve a problem in 20 minutes that stumps your entire team for a week. Then you spend three hours unable to start a simple email. This is the ADHD paradox.