Running a Coaching Practice With a Neurodivergent Brain
A lot of brilliant coaches are quietly drowning in admin, and a fair number of them are neurodivergent. If you are ADHD, autistic, AuDHD, or simply running on a brain that resists routine paperwork, you already know the pattern. The coaching is the easy part. It is everything around the coaching, the booking, the notes, the invoices, the follow ups, the logged hours, that piles up until it starts crowding out the work you are actually good at.
I want to reframe that pattern, because the usual framing is wrong and the wrong framing keeps people stuck.
The overwhelm is a design problem, not a character flaw
There is a useful idea from disability studies called the social model. The short version: a person is not disabled by their body or their brain so much as by an environment built for someone else. A building with only stairs does not disable a wheelchair user, the missing ramp does. Change the environment and the so called limitation often disappears.
Apply that to coaching admin. The standard practice software stack was designed around a particular kind of attention: linear, routine tolerant, comfortable with switching between six apps and holding the thread across all of them. If your brain does not work that way, the stack does not flex to meet you. It just quietly punishes you for the mismatch, and then you internalize the punishment as "I am bad at the business side."
You are not bad at the business side. You were handed a set of tools with no ramp.
This matters because the two framings lead to completely different solutions. "I am disorganized and need more discipline" leads to shame, another planner you will abandon, and a new system you will maintain for nine days. "My tools do not fit how I work" leads to changing the tools. One of those is a dead end. The other actually works.
Where the standard stack fails a neurodivergent coach
It helps to name the specific failure points, because they are predictable once you see them as design mismatches rather than personal ones.
Working memory gets treated as free. Most tools assume you arrive at a session already holding the full context: where this client is, what they committed to last time, what is still open. For a lot of neurodivergent coaches, holding that in your head between sessions is exactly the thing that does not happen reliably. So you rebuild it from scratch every time, opening five tabs before each call, which is both exhausting and easy to get wrong.
Initiation is the hard part, and the tools demand it constantly. Sending the follow up, chasing the unpaid invoice, logging the hour. None of these are difficult. They are just tasks that require you to start them, and task initiation is precisely where an ADHD brain stalls. A lead goes cold not because you decided to drop it, but because "follow up with Avery" lived only in your intentions and never became a thing the system did on its own.
Context switching is treated as costless. Six apps means six logins, six interfaces, six places a piece of information could be. Every switch is a chance to lose the thread, and for a brain that is already paying a context switching tax, the stack multiplies the cost.
Routine maintenance is assumed. Spreadsheets and manual logs only work if you tend them consistently. Consistency on dull, repeating, low stimulation tasks is, famously, not the neurodivergent strength. The system that depends on you remembering to update it is the system that will quietly fall out of date.
None of these are moral failures. They are four places where a tool made an assumption about your brain that does not hold.
What a brain friendly system does instead
Flip each failure point around and you get a design brief for practice software that actually fits:
It externalizes memory, so you do not have to hold context between sessions. The right view puts the whole picture in front of you when you open a client: where you are together, what they committed to, what is outstanding, last session's notes, all loaded before you start. That is what CoachTide's prep view is built to do. You walk in ready without having reconstructed anything, because the system kept the thread for you. Commitments a client makes during a session get captured in the moment and then resurface at the top of your next prep, so your session opening review is already done.
It removes the initiation step from routine follow through. Reminders go out before every session without you sending them. Invoices chase themselves when they go unpaid. On a drag and drop pipeline, moving a prospect one column forward can fire that stage's follow up, the booking link, the agreement, the intake, with a single confirm. The task still happens, you just do not have to be the one who starts it. For a brain that stalls on initiation, moving the starting line off your plate is the entire game.
It collapses six apps into one. When booking, notes, invoices, hours, and follow ups live in a single system, there is one place to look and one thread to hold. Fewer context switches, fewer dropped balls, less of the tax you were paying just to keep everything in view.
It updates itself from the work, so there is no maintenance to forget. Your ICF hours total from completed sessions. Your client record builds itself when someone signs your intake. The follow up email writes itself from the commitments you logged live. The system stays current because staying current is not a separate task you have to remember to do.
The point is not automation for its own sake. It is that every one of these removes a specific load that a neurodivergent brain finds expensive, and puts it on the software, where it is cheap.
I built this because I needed it
I should be honest about where this comes from. I am a working coach, and I am neurodivergent, and I built CoachTide because the patched together stack I was running my practice on was quietly eating the part of the week I actually trained for. Five tools, none of them talking to each other, every one assuming a kind of attention I do not reliably have. The certification chase, logging every hour, tracking CCEUs, keeping records straight, was the breaking point.
So I stopped duct taping tools together and built the one I kept wishing for: a system that holds the context so I do not have to, that does the chasing so I do not stall on starting it, and that counts my hours from the work I already did. It is the tool I wish I had on day one.
I am not telling you this to pitch you. I am telling you because if you have spent years assuming the admin overwhelm is a discipline problem you keep failing to fix, I want you to consider that it was a fit problem the whole time, and fit problems are solvable.
A few changes you can make regardless of tools
Even before you change software, you can change the design around yourself:
- Externalize ruthlessly. Anything you are holding in your head, put somewhere the system will show back to you at the right moment. Your memory is for coaching, not for storage.
- Make follow through automatic, not intentional. Wherever a task depends on you remembering to start it, look for a way to make it fire on its own. Intentions are where tasks go to die.
- Reduce the number of places. Every app you can collapse into another is one less context switch and one less surface to lose something on.
- Stop maintaining what can update itself. If a record only stays accurate when you tend it, it will drift. Prefer systems that stay current as a byproduct of the work.
You did not choose a brain that finds admin expensive, and you do not owe anyone an apology for it. You just need an environment with a ramp. Build it, and the coaching gets to be the thing you spend your days on again.
CoachTide is the practice that runs itself, so the admin stops depending on you remembering it: booking, prep, pipeline, invoicing, follow ups, and ICF hours handled in one place, with your client data private by design. Request beta access while we are in private beta.