The Productivity Stack Nobody's Selling You
I run my agency, job search, book, and personal life from one VS Code window. Here's the orchestrator pattern that made it work.
Everyone's selling you a productivity stack. Notion. Linear. ClickUp. Monday. Superhuman. Pick your flavor, pay your monthly fee, sync your calendars, call it a system.
I tried most of them. And they all make the same assumption: your work life and your real life are two different problems that need two different tools.
They're not.
The Split That Doesn't Actually Exist
The way productivity tools are marketed quietly trains you to think of work and life as separate operating systems. Your work stack: Notion for docs, Linear for tasks, Slack for comms, Calendly for meetings. Your life stack: Apple Notes, Reminders, iCloud Calendar, the stock iPhone weather app.
When the two conflict - a client call that lands on a parent-teacher conference, a contract deadline that collides with a dentist appointment - you are the reconciliation layer. You hold the context in your head and translate between the two stacks manually.
That reconciliation is the cost nobody's pricing into your monthly subscription. It's invisible because you pay for it in attention, not dollars.
One Workspace, Eight Lives
So I built something different. A Claude Code workspace running inside VS Code on a Mac Mini in my home office. Self-hosted everything behind it. n8n for event-driven wiring. About forty custom scripts gluing the edges together. The interface I actually touch every day is a single VS Code window with the Claude Code panel open on the right.
Here's what it actually runs:
- My agency (Whtnxt): CRM, invoicing, contracts, proposals, client health checks
- My job search: scoring roles, tailoring resumes, tracking the application pipeline
- Content across four brands: drafting, scheduling, publishing, analytics
- A book I'm writing: voice notes become outlines become drafts
- A hardware product I'm researching: BOM, component sourcing, manufacturing partners
- A county data site for Texas tax exemptions: monthly SEO updates across 20+ counties
- Personal reminders, calendar, and daily planning
One workspace. Eight lives. Every domain is an agent that Claude can reach through the same conversation, which means I can hand off work to the system in plain English without context-switching between tools.
The Orchestrator Pattern (a Game of Telephone)
The thing that actually makes this work is the layering. There's a top-level orchestrator agent. It lives in the root CLAUDE.md file and has wide domain knowledge about every project and every sub-system. When I hand it a task, it doesn't try to do everything itself. It figures out which specialist sub-agent owns the work and hands it off.
Think of it like a game of telephone, except each person in the line actually knows their job. The orchestrator takes my intent. A specialist agent (project manager, marketing technologist, web developer, etc.) takes the handoff and executes. And if the work touches a specific project (say, a client site or the book), the orchestrator also pulls in the project-level agents defined in a .claude/properties/<name>.yaml file that has the routing, the conventions, and the context for that particular lane.
Progress gets tracked in NocoDB (which is just a fancy spreadsheet on a Postgres backend) so nothing falls through the cracks between sessions. Long-term memory lives in a Qdrant vector store so I can reference conversations from weeks or months ago without re-explaining.
It sounds heavy when I write it out, but in practice I type a sentence into the Claude Code panel and the whole handoff chain happens behind the scenes.
The Part Nobody Measures
When your work tool and your life tool don't know about each other, you are the integration layer. Every switch between contexts is a tax on your attention, not a big one, but they stack. By the end of the day you've paid hundreds.
Collapsing the boundary eliminates the tax. When the same system that processes client invoices also reminds me to pick up groceries, something shifts. The mental overhead of "which tool does this live in?" goes to zero. Context stops costing me.
The fragmentation of tools has only fragmented the way we think and work. If you can orchestrate out of one system, the flow state becomes all the more seamless. That's the subtraction nobody can sell you as a feature.
Why VS Code + Claude Code Was the Right Interface
I didn't start here. I tried web-based chat, I tried a raw terminal, I tried a custom dashboard. What made VS Code + the Claude Code plugin click was that it already had everything an orchestrator needs: a file tree, a terminal, git, an editor, and now a conversational agent that can reach all of it. I didn't need to build a UI. I just needed to write the agents and the plumbing. VS Code is the cockpit.
The practical effect: I can type a question into the Claude Code panel, watch it read files from the repo, call an MCP server, hit an API, and write the result back to NocoDB or Outline, all without leaving the same window.
Why Self-Hosted Mattered Less Than I Thought
I started down this path for the usual reasons: cost, privacy, control. Those were real, but they turned out to be the least interesting part.
The actual win was the unified API surface. When every tool is reachable through the same orchestrator, it doesn't matter whether it's running in a Docker container on my Mac Mini or behind an API call to a cloud service. What matters is that Claude can reach all of it from one conversation.
What It Cost to Build
- Hardware: $600 Mac Mini, already had the monitor and peripherals
- Software: $0, every component is open source or self-hosted
- Setup time: ~50 hours spread across several months, mostly on weekends
- Ongoing maintenance: roughly an hour a week, usually less
Compared to what I was paying in SaaS fees: Notion Team, Zapier Professional, Calendly Premium, a CRM, a scheduling tool, an email platform. This is cheaper every month and it does more.
The real moat isn't the savings. It's that I own the integration layer. When a vendor changes their API or kills a feature I depend on, I can rewrite my own glue in an afternoon.
Is This for You?
Honest answer: probably not, and that's fine. You need to be comfortable in VS Code, willing to debug your own automations when they break, and have the patience to invest a few weekends up front. If you're a tool-hopper chasing the newest shiny SaaS launch, this isn't the path.
But if you're tired of the integration tax and you're already living in an IDE, there's nothing on the market that touches this for leverage. Start with one domain, whichever one causes you the most daily friction, and wire it up. The rest will follow when you feel what it's like to stop switching tools.
I haven't opened a SaaS dashboard in three months. And I'm not going back.
What part of your life are you still running manually because nobody's made an app for it?
Edward Chalupa is a digital marketing specialist and founder of Whtnxt, a digital marketing and automation consultancy. Connect with him on LinkedIn or explore more at echalupa.com.