Issue #30 — $90M ARR with ADHD: The Systems That Actually Scaled

🎯 TL;DR
An ADHD founder scaled Holywater from zero to $90M annual revenue — and left a paper trail of exactly how. This isn't a motivation post. It's a systems autopsy: which operational structures worked, which ones broke, and which ones are transferable to any ADHD-wired business.
This week: What scaling actually looks like when your brain is wired for starting, not sustaining.
Read time: 6 minutes
🚀 The Part They Leave Out of Founder Stories
Most ADHD founder success stories go like this: "I struggled in school, failed a bunch, then my 'chaos energy' turned out to be an asset, and now I run a successful company."
Inspiring. Useless.
What they leave out is the operational reality of getting from zero to something that works without you having to white-knuckle your way through every quarter. Because that's where ADHD founders break down — not at the start, but at the scale.
The Holywater story, covered in depth by Crunchbase, is different because the founder documented the specific systems and cognitive strategies that made $90M ARR possible with an ADHD brain. Not the narrative arc. The actual mechanisms.
Let's go through the five that matter.
🔧 Five Systems That Scaled With an ADHD Brain
1. Hyperfocus as a Sprint Protocol, Not a Personality Trait
Most ADHD founders treat hyperfocus as something that happens to them — a gift when it arrives, a problem when it doesn't. The Holywater founder operationalized it.
The approach: identify the two or three problems in the business that genuinely deserve hyperfocus-level attention right now. Make them explicit. Then create the environmental conditions — blocked time, no Slack, clear "why this matters" — to reliably trigger the state.
This is the difference between hyperfocus as accident and hyperfocus as scheduled resource. The business got better outcomes from high-intensity founder attention deployed intentionally than from sustained moderate attention spread across everything.
| Reactive Hyperfocus | Scheduled Hyperfocus |
|---|---|
| Triggered by urgency or novelty | Triggered by intentional setup |
| Often misdirected (fires, not strategy) | Directed at highest-leverage problems |
| Leaves other areas unattended | Paired with delegation structures for everything else |
| Draining; recovery needed | Still intense, but purposeful |
2. Executive Function Delegation Before Hiring
The standard advice for ADHD founders is to "hire for your weaknesses." The Holywater approach was more precise: before hiring anyone, build external systems for every executive function that the founder couldn't reliably self-generate.
This meant: documented processes for recurring decisions (so the founder didn't have to re-derive them each time), structured weekly reviews (to compensate for time blindness), and an explicit "operating manual" for the business that didn't live only in the founder's head.
The logic: if you hire someone to compensate for a gap before you've understood the gap, you've just made a human responsible for a poorly-defined problem. If you understand the gap first, you can hire precisely — or discover that a system is actually better than a person.
3. Self-Awareness as a Leadership Tool, Not Just Self-Help
This is the one that sounds soft but isn't. The founder built culture explicitly around cognitive transparency: being honest with the team about which tasks the founder was reliable for, which ones needed structure or backup systems, and which decisions shouldn't wait for founder bandwidth.
The result: the team stopped expecting neurotypical consistency from a founder who was never going to provide it. Instead, they built around the actual cognitive strengths available. High-judgment, high-stakes decisions: founder. Execution and follow-through: systems + team.
"The moment I stopped pretending I was going to become someone who naturally loves operational details, the business actually started running better. The team stopped waiting for me to do things I was never going to do."
4. Interest-Based Work Design at the Organizational Level
ADHD brains run on genuine interest, not obligation. The Holywater founder designed the company structure so that the founder role was almost entirely composed of tasks that triggered natural engagement — product strategy, culture, key relationships, high-stakes decisions — with operational execution delegated completely.
This sounds obvious, but most founders don't do it. They hold onto tasks they hate because they feel responsible for them, or because they haven't built the trust to hand them off. The result is a founder spending 40% of their time in a low-engagement state — and an ADHD brain in low-engagement mode makes bad decisions and produces poor work.
The disciplined version: audit your task list quarterly and ruthlessly eliminate anything that doesn't require your specific judgment or generate genuine engagement. If it can be delegated, it must be.
5. Treating Failure as a Data Collection System
ADHD founders often have a complicated relationship with failure — either catastrophizing it (RSD) or dismissing it too quickly and repeating it. The Holywater approach built explicit review rituals for failures: not blame sessions, but structured analysis of what the failure revealed about the system, the assumption, or the execution.
This converted a natural liability (ADHD and impulsive decision-making) into an accelerated learning loop. The pace of iteration got faster because failures were processed instead of buried.
⚡ The ADHD Angle
Here's what the $90M ARR story actually proves, at a systemic level.
The ADHD founder advantage isn't just that you're brave enough to start companies or creative enough to find new markets. It's that when you build the right operating infrastructure around your brain — rather than fighting your wiring — the company gets an amplified version of your cognitive strengths with the operational gaps covered by design.
Neurotypical founders often build companies that depend on the founder's ability to do everything adequately. ADHD founders, when they succeed, build companies that depend on the founder to do a few things extraordinarily well — because adequacy was never on the table.
That's not a consolation prize. That's a different and often more scalable organizational design.
🎯 This Week's Challenge
-
List the five tasks you spent the most time on last week. Circle the ones that genuinely engage your ADHD brain. Draw a line through the ones you could delegate if you built the right systems or made the right hire. The ratio tells you something important.
-
Pick one executive function gap in your business — one thing that regularly fails because it requires consistent follow-through you don't reliably provide. This week, design the system or identify the person who owns it instead of you.
-
Schedule one hyperfocus sprint for the highest-leverage problem in your business right now. Two to three hours, no interruptions, clear problem statement. Don't wait for it to happen to you.
See you Tuesday, L-P
P.S. — The Crunchbase piece is worth reading in full. It's one of the rare founder interviews that skips the hero narrative and gets into the operational specifics. The systems section alone is worth the ten minutes.
Divergent — Strategy for brains that don't do boring.