I started a new project last month. A cool new app. Revolutionary, obviously. The kind of idea that hits you at 11 PM and has you standing at your desk by midnight with a fresh repo and a head full of architecture decisions.
I went hard. Hours. Days. Skipping meals, forgetting to reply to messages, operating in that beautiful tunnel where the code just flows and every problem has a solution you can almost see before you finish typing the question. I built the core. I solved the hard parts. I got it to the point where the remaining work was clear, scoped, and totally achievable.
And then I stopped caring about it.
Not consciously. I didn't decide to abandon it. I just woke up one morning and the pull was gone. The dopamine faucet turned off. What was left was finish work. Polish. Edge cases. The kind of steady, unglamorous effort that turns a prototype into a product. And my brain had already moved on to the next interesting problem.
If you're neurodivergent and you've built anything, you know this exact feeling. The graveyard of 80%-done projects. The guilt. The frustration of knowing you're capable of extraordinary output but somehow can't make yourself do the last 20%.
This is not a discipline problem
I run a solo software studio called Built By Dusty. I build tools for animal breeders. I'm also a breeder myself. Crested geckos, and before that, American Bullies and APBTs going back to when I was five years old. I have 9+ years of professional engineering experience across fintech, healthcare, and government. I've shipped production software for CBP, ICE, and FEMA. I'm not lacking in ability or work ethic.
What I am is wired differently.
My neurodivergency looks like completing work exceptionally fast. Thriving in the go-go-go. Actually enjoying context switching, which I know sounds like heresy to the deep-work crowd. I can juggle three codebases, a client call, and a breeding record update in the same afternoon and feel energized by it.
The cost is that project timelines get muddled. Tasks asked of me in the throes of a hyperfixation vanish from my memory like they never existed. Someone sends me an important email while I'm three hours deep in a database migration, and that email might as well have been addressed to someone else. It's gone. Not because I don't care. Because my brain physically was not available to receive it.
The tool graveyard
I tried everything. I really did.
AI calendars that promised to organize my day. They'd generate a beautiful schedule by 8 AM. By 8:45 I'd already blown past it because I got pulled into something more interesting, and the rest of the day's plan became fiction.
Pomodoro timers. Twenty-five minutes on, five minutes off. The problem is that when I'm locked in, a timer going off doesn't make me take a break. It makes me angry. And when I'm not locked in, no timer is going to manufacture focus.
Written planners. I own a genuinely embarrassing number of notebooks with exactly twelve pages of neat, hopeful planning followed by nothing.
Task management apps. I've signed up for most of them. The ones that require manual input fall apart because updating the system is exactly the kind of low-stimulation maintenance task my brain deprioritizes. The ones that try to automate everything make assumptions about how I work that don't match reality.
The common thread: none of these tools could keep up with the speed of my brain. They all assumed a pace and a pattern that isn't mine. They wanted me to slow down, break things into small pieces, follow a linear path. That's not how I operate. I operate in bursts. I need a system that can match that.
What changed
I started using Claude as a rubber duck.
Not for code generation. For thinking. I'd be deep in a FastAPI project and I'd ask, "What are the security drawbacks of JWTs versus session tokens for this use case?" Or I'd be structuring a new service and ask, "What's the best way to organize routes in this API if I know I'm going to add multi-tenancy later?" Technical questions where I didn't need someone to write the code. I needed someone to think through the problem with me.
That was the first thing that felt different. Every other tool I'd tried wanted to manage me. Claude just showed up and matched whatever speed I was moving at. I could fire off three questions in two minutes, get useful answers, and keep building. Or I could slow down and have a long back-and-forth about architecture tradeoffs. It met me where I was instead of asking me to be somewhere else.
Claude Code came much later. The connectors to Jira and Confluence came later still. But the foundation was that first experience of having a thinking partner that didn't try to change how I work. It just worked the way I already do.
That distinction matters more than any feature list. Every productivity tool I'd tried before was built on the assumption that I needed to be reformed. Slower. More methodical. More consistent. Claude doesn't assume any of that. It just holds the thread.
The morning context reload
Here's what a typical morning looks like now. I sit down. I open Claude. And I say something like: "I'm picking back up today. What was I working on Thursday?"
That's it. No digging through browser tabs. No scrolling through Jira trying to reconstruct what I was doing three days ago. No reading old commit messages hoping they jog my memory.
Claude has my Jira board connected. It has my Confluence docs. It can see my project tickets, my outreach pipeline, my content calendar. So when I ask what I was doing Thursday, it doesn't guess. It checks. It tells me I was halfway through writing RLS policies for tenant isolation on Breed Ledger, that I had a follow-up email to send to a breed club, and that I'd left a note about a failing CI pipeline on a ReptiDex ticket.
For a neurotypical person, this might sound like a convenience. For me, it's the difference between a productive morning and an hour of floundering while I try to remember where I left off. That context reload used to cost me real time every single day. Sometimes it cost me the whole day, because by the time I'd reconstructed the state, the motivation window had closed.
Thinking out loud without losing the thought
As I started trusting Claude with technical questions, I started trusting it with harder ones. Business decisions. Strategy. The kind of thing a solo founder normally processes alone in the shower and then forgets half of by the time they sit back down.
Here's a recent example. I have two products. ReptiDex, a breeding records app that's live, stable, and has paying subscribers. And Breed Ledger, a platform for breed clubs and registries that's earlier stage. I'd just lost my first pitch for Breed Ledger. The breed club chose a different tool for their immediate need. My second prospect was promising but months away from a decision.
My brain wanted to go back to ReptiDex. I had a list of features that were genuinely exciting to build. Fun problems. The kind of work that would let me hyperfixate for a week and feel productive the whole time.
So I talked it through with Claude. Not a polished strategy prompt. Just: "I'm torn between pushing ReptiDex features or continuing to build out Breed Ledger even though the first deal didn't land. What do you think?"
Claude told me Breed Ledger was the smarter play. ReptiDex is in a good, stable place. Users are on it. I can watch how they interact with what's already there and let that data inform the next set of features in a few months. Meanwhile, Breed Ledger needs a working demo. When the next breed club conversation happens, showing a real, functional platform is worth more than any pitch deck. Building the demo now means I'm ready when the opportunity shows up instead of scrambling to build it after.
That answer saved me from a classic neurodivergent trap: chasing the dopamine of fun work instead of doing the strategic work that actually moves the business forward. I knew that. Somewhere in the back of my mind, I knew it. But knowing something and having someone lay it out clearly, with the context of your actual business situation, are two different things.
This is the rubber duck that talks back. And for someone whose brain generates ideas at a pace that outstrips their ability to evaluate them, having a patient, context-aware sounding board is transformative. I can externalize my thinking without worrying that the thought will disappear before I finish processing it. It's captured. It's in the conversation. I can come back to it.
Then came Claude Code
Claude Chat was the thinking partner. Claude Code, when it arrived, became the momentum keeper.
I want to be honest about this part because it's the part that matters most.
There are days where executive function is just low. Where starting feels impossible. Not because the work is hard. Because the activation energy required to go from "sitting in my chair" to "writing the first line of code" might as well be infinite.
On those days, Claude Code is the difference between shipping and stalling. I don't have to create from zero. I can describe what I need, and Claude produces a first draft I can react to. A set of database migration files. A test suite skeleton. An API endpoint with the boilerplate already handled.
Reacting is easier than creating when your brain is fighting you. Editing a draft takes less activation energy than staring at a blank file. This is not laziness. This is a real, practical accommodation for how my brain works on its worst days. And it means those days still produce output instead of guilt.
And on the good days? When hyperfocus is locked in and the code is flowing? Claude Code keeps me there. I can stay in the zone and let it handle the boilerplate so my attention stays on the hard parts. I run multiple Claude Code instances reviewing each other's work while I focus on architecture and direction. The momentum doesn't break.
The connectors tied it all together
First it was the chat. Then Claude Code. Then the connectors came online, and that's when the whole system clicked.
The MCP integrations let Claude reach into Jira, Confluence, and Google Drive without me having to copy-paste context into a chat window.
I run my entire business through Jira. Every outreach conversation. Every content piece. Every product feature. Every bug. When I say "what's the status on the GSGC deal?" I don't have to navigate to the board. Claude checks the ticket and tells me.
When I'm mid-hyperfixation on a code problem and someone asks me about a content deadline, I can say "when is that breeder website article due?" without leaving my editor. The answer comes back with the actual status from the actual ticket.
This matters because the organizational overhead of running a solo business is the silent killer for neurodivergent founders. It's not the core work that breaks you. It's the meta-work. The tracking. The updating. The remembering. Every minute you spend maintaining your project management system is a minute you're not building. And for people like me, that maintenance is exactly the kind of low-stimulation task that gets deprioritized until something falls through the cracks.
The connectors mean less maintenance. Less context switching to update a system. Less "I'll do it later" that turns into "I forgot it existed."
What actually changed
I want to be specific because vague claims don't help anyone.
Follow-ups that used to slip now have a system catching them. I can ask Claude every morning if anything in my outreach pipeline has gone quiet, and it checks the actual tickets instead of relying on my memory.
Feature scope conversations happen in writing. When I talk through a product decision with Claude, that conversation exists. I can reference it. It doesn't mutate in my memory the way verbal decisions do.
Bad days don't mean lost days. Even when executive function is low, I can still move tickets forward because the barrier to entry is lower. Describe what you need. React to what comes back. Ship.
I spend less energy on "what should I be doing right now" and more energy on the work itself. That question used to eat an hour some mornings. Now it takes thirty seconds.
This is not a Claude ad
I want to be clear about what I'm saying and what I'm not.
I'm not saying Claude fixed my brain. My brain works the way it works. I'm not saying Claude is the only tool that could do this. I'm saying it's the first tool that matched the way I actually operate instead of asking me to operate differently.
The speed. The context awareness. The ability to pick up where I left off without me having to reconstruct the state. The patience to answer the same question I asked three days ago without making me feel bad about it. The connectors that reduce the organizational tax of running a business.
For me, as a neurodivergent solo founder, that combination turned out to be the thing that finally worked.
If this sounds like you
If you're neurodivergent and freelancing or running a solo business, the best tool isn't the one that makes you more disciplined. It's the one that makes discipline less necessary.
Stop trying to fix the way your brain works. Find tools that work with it.
That's what I did. And for the first time, the projects are getting finished.
Top comments (0)