I didn't build Khloe because I was disorganized. If anything, the problem was the opposite — I had too many things organized in too many places, and no single view of what actually mattered on any given day.
As a consultant, I'm usually running several client engagements at once, alongside the side businesses, the parenting, the ideas I don't want to lose, and the relationships I want to make sure I'm actually tending to. Every morning started with the same three questions:
Not because I'd forgotten. Because the answer lived in six different places and I had to go find it every single morning before I could actually start working.
I didn't need another task manager. I needed something that understood the context behind my work — not just what was on the list, but why it mattered, what it connected to, and what was quietly at risk of falling through the cracks.
So I built Khloe.
How Khloe actually works
Every Sunday, Khloe and I hold what I've started calling an executive planning meeting. We go through everything on my plate — clients, priorities, commitments I've made, things that are moving, things that have stalled. We identify what matters most for the week ahead and build the plan together.
Then each morning, Khloe prepares my executive dashboard. Not a task list. A daily briefing — the kind a good chief of staff would walk into your office with.
I still make every decision. Khloe doesn't tell me what to do — she makes sure I'm starting from a clear picture rather than a scattered one. That distinction matters more than it sounds.
Then my friend built Lex
A few weeks after I started using Khloe consistently, a friend who'd attended one of my AI workshops decided to build her own version. She named it Lex.
She's a team of one responsible for learning initiatives across an entire school district. Every day she's fielding requests from multiple schools, managing long-term programs, communicating with administrators, and trying to stay ahead of a backlog that never fully empties. The scale of it would be a lot for anyone.
She adapted the pattern — the Sunday planning session, the daily briefing, the context-first approach — to her own work. Different job title. Different industry. Completely different set of pressures.
Within days she told me something had shifted. Not because Lex was doing her job. Because she no longer felt like she had to hold every project in her head at the same time.
- Balancing several client engagements at once
- Tracking commitments across relationships
- Surfacing the work with the biggest impact
- Protecting space for the side businesses and the family
- Starting each day from clarity, not chaos
- Managing initiatives across multiple schools simultaneously
- Keeping stakeholder communication consistent and timely
- Prioritizing faster when everything feels equally urgent
- Reducing the mental overhead of never-ending context switching
- Finding confidence in a role that can feel isolating
That was the moment I realized this wasn't really about Khloe. It was about a pattern — one that anyone could adapt to their own work, their own pressures, their own version of "too much context to hold in my head."
What Lex taught me about what I'd actually builtThe real problem it solves
The problem Khloe and Lex solve isn't time. Both my friend and I had enough time. The problem was cognitive load — the invisible tax of managing context across too many competing priorities at once.
Traditional productivity tools are good at capturing tasks. They're not good at capturing the context around those tasks — why this one matters more than that one today, what happened yesterday that changes the shape of this morning, which relationship has been quietly neglected for three weeks.
That's the layer an AI Chief of Staff operates on. Not the task. The context around the task.
The best AI systems don't replace your judgment. They reduce the cognitive load around it. AI isn't most valuable when it creates more work. It's most valuable when it creates more clarity — so you can spend less energy remembering everything and more energy deciding what actually matters.
Who this is actually for
Khloe was built for a consultant juggling multiple clients. Lex was built for a solo learning leader supporting an entire district. The pattern works for both because the underlying problem is the same: too many priorities, too many decisions, too much context to carry alone.
The goal isn't to think less. It's to spend less energy remembering everything so you can spend more energy on the decisions that actually need you.
That's the kind of AI I'm excited to keep building.