Issue #1: I Didn't Build a Productivity System. I Built Survival Infrastructure.

For a long time, I thought the problem was me.

The Actual Problem: Tools Built for Someone Else’s Brain

For me, the challenge was getting conventional productivity tools to work for a brain that doesn’t think linearly. I tried everything: calendars that promised organization, journals claiming to unlock potential, and apps designed for "productivity".

None of it stuck. Most of it was expensive. That's because most advice assumes you follow a linear, step-by-step process. It assumes you sit at a desk, follow a list, timebox your calendar, and think in steps.

But I don’t think that way. I think in systems and connections. I am managing a home, a family, business ventures, constant learning, all while navigating a recovery journey I never expected. Conventional systems failed me because they required compartmentalization—keeping work separate from personal life and one project isolated from another. Every "system" I tried asked me to keep my brain in a box.

I beat myself up about it. I thought I wasn't disciplined enough. I thought I wasn't trying hard enough. I thought there was something wrong with how I approached work and life.

The Shift: Architecting Survival Infrastructure

At a certain point, I stopped trying to fit into someone else’s system and started building my own. What began as an attempt to keep complex responsibilities from unraveling turned into survival infrastructure. This isn't just a methodology; it is the right tools connected in the right ways so that instead of fighting how my brain naturally works, the system supports it.

In this infrastructure, the natural tendency to make connections across different domains is a feature, not a bug. Instead of a system that forces compartmentalization, this ecosystem connects everything in my tech stack in a way that integrates my real, day-to-day life, allowing for a state of flow rather than constant friction.

Along the way, I built some tools of my own to help me actually take stock of where I was and what I truly needed. The next few blog posts will feature an interactive tool currently in the toolbox, the logic behind each one, and how you can use it, with more tools coming soon. You can access the toolbox here -->

The Heavy Lifters: A Unified Ecosystem

To make this work, I built a custom digital ecosystem where platforms are integrated and communicate effectively. Most systems fail because nothing talks to each other—your calendar is here, your tasks are there, and your notes are somewhere else entirely. Or, you get all of that in one platform, but something is also either behind a paywall or it's ridiculously tedious to use because of feature bloat, too many clicks to do one simple thing. Building this took some trial and error, and more than a few accounts were opened only to be closed again; but what I was doing was distilling what I actually needed from what I tried, then further selecting platforms that checked off my must-haves. This gave me a tech stack that became easier and easier to connect and use, all while avoiding the horrific digital sprawl I'd continuously orchestrated in the before-times.

The Stack:

• Claude: The primary point of entry and "thinking partner." Claude handles strategy, research, and problem-solving, acting as a "Jarvis" or "Alfred" to bridge the gap between idea and execution. Claude also manages my LifeBase; I applied the concept of a wiki or knowledge base to my basic daily flow, and set up the infrastructure to allow Claude to add, recall, edit/update, execute, organize, research, and save any item of any type across my digital life. This, along with other architecture I've patched together over time (and use!), gives me one point of contact for everything to manage my day and life.

• ClickUp: The central task and project hub where all execution lives. Claude seeds ClickUp with the to-dos and information I need to keep life running; he also oversees the team of agents within the ClickUp interface who are responsible for processing, organizing, auditing, and managing the content there. Again, one point of contact.

• NotebookLM: The knowledge base where learning and study come together. It allows for non-linear, conversational thinking while preventing scattered notes. A couple of key features for me are the source lists for each notebook, and the study aids available for output. I use this notebook for my own learning and to provide information to others, whether that be an infographic or flashcards for easy reference. While Claude isn't integrated here, I do use him to create curricula or topic briefs for study, as well as artifacts from chats that can be uploaded as a source; he also tracks my learning goals, next curriculum steps, and the media output slotted for my blog or newsletter. If I need to transfer any files, it's a simple download and/or upload. This keeps me aligned with the one point of contact theme.

• The Development Stack: I utilize React/React Native, Replit, and Netlify to build and deploy custom resources like my capture app, with Supabase managing data and GitHub storing code. GoDaddy hosts my domains, Wix hosts my website, and BeeHiiv hosts my newsletter. Claude has access to these platforms, and I use Pushover to send proactive, Claude-generated messages to my devices with prompts for immediate action, allowing me to click directly into whichever task needs attention. Say it with me: one point of contact

• The Glue: Zapier, MCPs, and APIs ensure that Gmail, Drive, and Calendar flow into the central system without manual overhead. Setting these up became a learn-as-I-go process, and I relied heavily on Claude and various platform developer docs to get things connected and understand what I was doing. I'm still learning, but my system works, and that's powerful motivation.

Believe it or not, 70% of the platforms I use are no-cost or on the free tier. For once, instead of wantonly subscribing and upgrading in a mad attempt to make everything finally work by getting every available feature (although, I promise you, I typically only used maaaybe half of them), I could begin building at no cost and upgrade where it really mattered, on the platforms that were doing the heavy lifting and doing it the way I needed it to. Boom. Money saved.

Documentation in Progress

The BrainflowOS blog is a built-in-public journal. It is not a "5-step routine" or a "productivity hack". It's me being honest about what it took to build this system from the ground up, and it's documentation of the frameworks and workflows that make it possible to go from scattered to connected, for anyone who wants better flow in their day.

Tbh, I'm documenting this because I know others are beating themselves up trying to make standard advice work for them. The goal isn't to be more disciplined; it’s to build infrastructure that works with your brain. This is the story of how the infrastructure was built and how it finally started working with my brain instead of against it.