I'll never forget walking into a sourcing and trading firm doing $7M a year. The founder was brilliant — he could look at a swatch of 200 GSM cotton jersey and quote the exact FOB price within five cents, no spreadsheet needed.
What he didn't have was a system. His entire operation lived in a stack of legal pads and a WhatsApp group that buzzed 24/7.
One weekend he flew home for a family wedding in a remote area with terrible reception. For four days the business simply stopped. Three production runs in Vietnam froze because the factory needed a final "go" on a lab dip color. The shipping agent didn't know which 3PL to route the Los Angeles container to. His team was paralyzed — every decision, every rule, every exception lived only in his head.
When he landed and opened his phone, it was a disaster. Orders delayed, customers angry, containers sitting on the dock racking up demurrage.
"I thought I was the one holding it all together. Turns out I was the one breaking it."
— The founder, voice cracking, over coffee weeks later.That moment crystallized everything for me: if your business can't survive you getting the flu for a week, you don't have a business. You have a very expensive, very stressful job.
Twenty years across manufacturing, general trading, ecommerce, and supply chain management taught me three lessons about building systems that actually work. None of them are about technology. All of them are about what happens when a founder tries to hold everything together personally — and what changes when they finally let go.
A fashion brand we worked with was exploding — going from 50 orders a day to 300 almost overnight. The inbox became a war zone. The founder did what any logical person would do: he hired four VAs from the Philippines and a part-time manager.
Within weeks the chaos got worse. No SOPs existed, so every VA developed their own approach. One gave full refunds for "change of mind." Another offered 20% discounts. The third demanded customers pay return shipping. Customers started getting wildly different answers to the same problem.
"I'm working more now with five people than I did when it was just me."
— The founder, exhausted, after weeks of babysitting his own team.This is the pattern I've seen dozens of times across every industry I've worked in. A founder hits a capacity wall. They hire people to absorb the volume. But because no documented process exists — no SOPs, no escalation rules, no quality standards — the new hires create more coordination overhead than they remove.
Hiring people to fix a broken process is like pouring more water into a bucket with a hole in it. You just end up with a bigger mess on the floor. The bucket — the system — has to be fixed first.
Document the process. Define the rules. Build the SOP. Then hire people to execute the system, not to guess their way through it.
I watched two very similar bedding brands at the same time.
The difference wasn't intelligence or luck. Both founders knew their product inside out. Both had strong supplier relationships. The difference was the size of the decisions they were making. Founder A spent his days on $10 problems. Founder B reserved his time for $10,000 decisions.
You can't make $10,000 decisions when your brain is full of $10 problems. The system exists to handle the $10 problems so you can focus on the decisions that actually move the business forward.
This is the lesson most people get wrong about AI in operations.
Ami and I were auditing a 40-page tech pack for a high-performance activewear line. We fed the grading table into our Claude and Make.com workflow.
That moment was the perfect illustration of what we're building. The AI caught the mathematical error at scale — scanning a 40-page document in seconds with a precision that the human eye would struggle to match. My experience caught the physical, real-world consequence — something the AI had no way of knowing because it's never touched fabric.
Neither of us could have done it alone. The AI without the judgment is fast but dangerous. The judgment without the AI is accurate but slow. The combination — AI speed plus seasoned human experience — is what lets us build systems that actually work in the messy, physical world of real products.
Ami and I were sitting in a coffee shop staring at a client's "operations map." It was a spiderweb of twelve different apps that didn't talk to each other and three freelance teams pointing fingers at one another over a shipping delay.
The frustration hit us at the same time. The market was broken. Founders could either hire cheap VAs who didn't understand their business, or pay $15,000 a month for consultants who delivered a beautiful PDF strategy but never actually moved the boxes.
That was the birth of Opevion. We didn't want to build another agency. We wanted to build infrastructure — the operational utilities for a DTC brand. You turn us on, the lights come on, the operations just work. And the founder finally gets their Monday mornings back.
Everything I learned in twenty years — the systems that failed, the hires that backfired, the founders who scaled and the ones who stayed stuck, the AI that catches what humans miss and the judgment that catches what AI can't — all of it went into the design of the Operations Pod. It's the operations partner I wished existed when I was the one drowning in WhatsApp threads at 2:00 in the morning.
Want to Stop Being the Bottleneck?
Book a free 15-minute Operations Audit. We'll look at how your operations are structured today, identify the three biggest systems gaps, and show you what it looks like when the founder steps out of the daily chaos and into the director's seat. No pitch. No obligation. Just clarity.
Book Your Free Operations Audit →