I am not particularly good at keeping up with my own reminders. This is not a confession I'd make to most people, and it's not one I'd have made publicly a few years ago. But it's true, and it matters for what comes next.
I'm neurodivergent. I've known this for a while, and I've spent a lot of time thinking about what that means in practice — not philosophically, but operationally. How does it change what I build? What I need? What breaks if I'm not careful?
The answer I eventually landed on wasn't better willpower or a new productivity system I'd use for two weeks and abandon. It was interceptors.
What an interceptor is
An interceptor is a system that catches something before it can become a problem — without requiring you to remember to catch it. It runs in the background. It fires whether or not you're having a good brain day. It doesn't care whether you remembered to check the dashboard this morning.
The term comes from software. In programming, an interceptor is a piece of code that runs automatically when something specific happens — before the request gets through, before the response goes out. It doesn't interrupt the flow. It monitors it. It catches the things that could go wrong before they do.
I started calling my own systems interceptors because that's exactly what they are. Not reminders. Not checklists. Systems that run whether or not I'm paying attention to them.
What this looks like in practice
Picture a founder who reviews cash every Monday. Not because she schedules it — because a report lands in her inbox every Monday at 7am, formatted exactly the way she needs to see it, with the three numbers that actually tell her where she stands. She doesn't go looking for the information. The interceptor brings it to her.
Picture a business owner with a team of contractors where invoices sometimes arrive in unexpected formats and occasionally get missed. An interceptor catches every invoice submission, tags it, routes it to the right approval queue, and sends a flag if it hasn't been approved within 48 hours. Nobody remembers. The system handles it.
These aren't AI magic. They're designed workflows — but designed around how the business actually runs and how the owner's brain actually works, not around how the software expects you to work.
Why willpower is the wrong tool
Most of the "solutions" sold to neurodivergent business owners are willpower prosthetics. Better apps. Better habits. Better morning routines. These can help at the margin, but they have a fundamental problem: they require the brain to work correctly in order to work at all.
If the thing you need to do requires you to remember to do it, and remembering is the exact function that's impaired, the tool has failed before you opened it.
I stopped trying to fix my brain and started designing around it. The interceptors don't ask me to be a different kind of thinker. They run while I'm thinking about other things.
"I stopped trying to fix my brain and started designing around it."
This is not a small distinction. Most productivity advice assumes a neurotypical baseline and adds tools on top. Interceptors start from a different premise: what would this system look like if we assumed the person using it would sometimes miss things — and built around that reality from the beginning?
The business version is the same idea
Here is what I noticed as I started building interceptors into my own practice: the businesses I work with need them too. Not because every owner is neurodivergent — though more are than will say so publicly — but because every business has the equivalent problem.
Things fall through. Not because people are careless. Because the volume of things that need tracking is higher than any human system can reliably hold. A payment term that was supposed to reset. A quarterly review that got pushed back three times. A margin erosion that's been happening slowly enough that nobody flagged it as a crisis — it just became normal.
These aren't personal failures. They're system gaps. And the answer is the same whether the owner is neurodivergent or not: build the interceptor. Make the system catch it automatically.
"Every business has things that fall through. The question is whether you find them, or they find you."
What I actually build
When I embed with a client, one of the first things I do is map the gaps — not the financial gaps, though those matter, but the system gaps. Where are the things that depend on someone remembering? Where does the close get delayed because something wasn't tracked? Where does a decision not get made because the information isn't surfaced at the right moment?
Then I build interceptors for those gaps. Some are simple: an automatic report that lands in the right inbox at the right time. Some are structural: a dashboard with alerts built in so a dangerous cash position is flagged before it becomes a crisis. Some are embedded in the close process: review steps that can't be skipped because the system won't let the month close without them.
None of these require the owner to be vigilant. They require the system to be vigilant, which is a very different ask. Systems can be designed to be consistently vigilant. Humans can't.
The ND founder has an advantage
Here's the thing I've come to believe: the neurodivergent founder who builds interceptors into their business is operating at a higher level than the neurotypical founder who relies on memory and discipline.
Not because ND is better — because the ND founder, by necessity, has been forced to think clearly about what the system needs to do without human intervention. That thinking produces better infrastructure. Better documentation. Better design. A business that runs more cleanly because it was built for the reality of human fallibility rather than the fiction of perfect execution.
The thing you built to manage your wiring ends up being the thing that makes your business more resilient, more transferable, and ultimately worth more to a buyer.
I've watched it happen. The interceptors I built for myself have compounded into something real. The ones I've built for clients have done the same thing. Not because the owners are better people — because the systems are better designed.
One more thing
I am mid-process on a lot of this. The ND operating system I've built works well for me — but I'm still building it. I don't claim to have this figured out, and I don't present it as a completed method I'm now teaching. I'm a peer who's done the work and is still doing it.
That's exactly the posture I bring to the ND clients I work with. Not expertise handed down from the other side of a credential. Real-time navigation, shared in real time.
If you're building a business with a brain that doesn't always cooperate — or even if you're not — the interceptors work. The systems beat the willpower. And the business you build when you stop relying on heroics is the one worth owning.
Systems that run themselves
make the business worth more.
Interceptors aren't just about staying organized — they're infrastructure. A business that catches problems automatically is more resilient, more transferable, and more valuable. Tell me where yours are leaking.
Start the Conversation The ND CFO Lane →