Dear person who thinks they know what's broken in their business,
You don't discover what's actually broken by looking at it. You discover it by having something to compare it to.
I had nine things I needed fixed on my website. I knew about them because they bothered me enough to write them down. A list I'd been sitting on for months, waiting until I had the bandwidth. I reached out to a developer. His quote to audit the scope of work, not to fix anything, just to look at it, was $750.
I sat with that for about thirty seconds. Then it occurred to me. This is exactly what I would do myself, if I stopped avoiding it. I opened Claude.
What I thought was a nine-task project became a hundred and fifty tasks. Then close to three hundred. The number wasn't the surprise. The list was.
I'd been running this business for two years. I thought I knew my site. What I actually knew was a version of it filtered through two years of rationalizations. I'd made compromises and forgotten I made them. I'd looked at broken things so many times they stopped registering as broken. When I started auditing it properly, without my own assumptions running interference, the picture was completely different from what I'd been telling myself.
Here's the specific thing I had to look at clearly. I'm selling jewelry at the price point of a Mac computer. Something you save for. Something you deliberate over. That's the product. The experience I was giving people before they bought it was the UI equivalent of walking into Forever 21. Chaotic, cluttered, nothing quite where you'd expect it to be. The store and the price tag were in direct contradiction. Of course there was friction. I just couldn't see it, because I'd built it, and I'd long since convinced myself it was fine.
The changes I've made since have had a significant impact on revenue.
This all started in February, before any of it. I was going offline for ten days. A Vipassana meditation course, silent, no phone. My team is small. I had no process for handing anything off, because I'd never needed one. So before I left, I built infrastructure for the people who would need to hold things without me. A complete knowledge base for our client experience person, covering every question a customer might ask, answered and organized, so she could handle anything that came in. Templates and SOPs for everyone around her too. Not because I didn't trust anyone. Because going offline for ten days required me to build the systems that made it possible.
I came back expecting the pile. Every founder knows it. The backlog of decisions held in place while you were away, waiting to land back in your lap the moment you're reachable. It didn't happen. My team hadn't held anything. They'd taken what I built before I left and wrapped real processes around it. The work didn't come back to me. It stayed with them.
I had time I hadn't planned for. And I used it to audit the website.
Here's what I've since understood about that sequence. The systems you build for a crisis don't disappear when the crisis ends. They become infrastructure. I built those guides because I was going offline for ten days and I was scared. That fear is what made me actually build something, instead of just intending to. And the thing I built out of fear became the thing that changed how the business operated permanently. My team doesn't need me the way they used to. That wasn't the plan. It was the byproduct of being forced to document what only I knew.
AI didn't reduce my workload. It made my workload legible. And once something is legible, you can actually do something about it.
The nine tasks I thought I had were the symptom. The three hundred I found were the diagnosis. I couldn't have written that list without something that didn't share my blind spots.
The problem isn't that you don't know your business. The problem is that you know it too well to see it.
