My three most expensive mistakes.

Mistake one: assuming other people will use judgment.

High-functioning operators have a specific blind spot: we project our own competence, work ethic, and logic onto everyone around us. You hire a developer and assume he cares about uptime. You hire a chatter and assume basic social intelligence. You engage a vendor and assume a deadline means something without supervision.

That assumption is the fastest way to burn a business down. The uncomfortable reality is that most people are not thinking about your enterprise value, are not thinking three steps ahead, will not solve problems autonomously, and—if there is a mathematically possible way to execute a simple task incorrectly—will find it.

Early on I lost hundreds of thousands of dollars handing average people “operational freedom.” I asked someone to optimize the ad banner layout on a new niche site. I assumed they would check it on a phone, watch click-through, and make sure banners did not overlap the navigation. Instead they broke the CSS, broke the mobile layout, wrecked the experience, and cost me three days of ad revenue before I noticed.

The fix: build tracks, not goals.

You cannot run an operation on the expectation of good judgment. You build one that works despite its absence—and, to be fair to the people you hire, most failures are the result of an ambiguous instruction rather than a bad person.

Stop giving goals and start giving explicit tracks. You do not tell a chatter to “sell PPVs.” You give them a decision tree: if a fan says this, send script A; if he says that, send script B; if he asks for a custom, send price sheet C. Remove discretion from the parts of the job where discretion produces damage.

Isolate access like a submarine isolates compartments. No employee or contractor ever gets master admin on your registrar, primary servers, or banking portals. They get the specific dashboard needed for their actual task and nothing beyond it. And automate verification: if a task is marked done, do not take the word for it—have a software check or a QA step confirm the output.

Decision trees over instructions

Every recurring judgment call becomes an if-this-then-that script with an escalation path. Ambiguity is where money leaks.

Least-privilege access

Registrar, servers, and banking stay with you. Everyone else gets a scoped dashboard. This also protects the business at exit.

Verified completion

An automated alert or QA check confirms output. “Done” is a claim, not evidence.

Mistake two: falling in love with dollar units.

Here is the trap that catches almost every operator who reaches five figures a month. You build an asset—a creator account, a niche portal—and it nets $30,000 a month. A buyer offers a million in liquid cash. Your brain does amateur arithmetic: why sell for a million when three years of holding pays a million and I still own the thing?

So you decline. Then reality arrives. Six months later an algorithm shifts, your primary creator retires into a relationship, a processor changes compliance rules, and the smooth operation becomes a fourteen-hour-a-day fire drill. You are arguing with banks, losing sleep, and watching $30,000 a month become $12,000.

That is the difference between dollar units and energy units. Every morning you wake with a finite account of energy. Arguing with an insecure creator spends it. Fixing a database at 2 a.m. spends it. Merchant account holds spend it. A business can pay extremely well in dollars while draining every unit of energy you have, and that combination is a toxic asset regardless of the revenue line.

I held high-maintenance, drama-heavy operations far too long because the monthly cash flow felt good. If I had taken the cash exit sitting on the table, I would have walked away with liquid capital and, more importantly, all of my energy back—which I could have deployed straight into automated traffic real estate that never calls me at midnight. When someone offers a serious lump sum for a business that requires your daily sanity: take the cash, hand over the keys, do not look back.

Mistake three: underestimating the insecure partner.

If you manage creators you will eventually meet the most destructive force in this business, and it is not a platform. It happens with predictable regularity.

You sign a talented creator who was making a few hundred dollars a month alone. You plug her into the traffic machine, structure the DM sales approach, fix her subscription tiers, and within about six weeks the account is doing $20,000 a month. She is thrilled. Then her partner—who works a mediocre job and has no ambition of his own—realises she is rapidly outgrowing him financially, and his ego breaks.

He will not admit insecurity, so it arrives disguised as business oversight. He reads over her shoulder while she messages your team. He nitpicks the contract. Her pricing is too low, her boundaries are too explicit, your chatters are too aggressive. Before long he is sabotaging shoots, starting arguments two hours before filming, and demanding to sit in on management calls to play executive.

If you argue with him logically you lose every time. You are a business operator using logic; he is emotionally invested and sleeps in her house. She will side with him to keep peace at home, and a $20,000-a-month pipeline evaporates in a weekend.

Two ways to defuse it.

Strategy A is the executive promotion. You do not fight the ego, you feed it. On a production call, address him directly and give him something real to own: the lighting and camera setup for shoots, with a title to match. As long as he feels like a valued partner in her success, he stays out of your backend, leaves your chat team alone, and the cash keeps moving. It costs you nothing and it frequently improves the content.

Strategy B is cleaner and it is what I recommend at scale: remove yourself from his radar entirely. An insecure partner reads a successful male agency owner as a direct threat. Put a sharp, professional female account manager as the sole front-facing contact for your roster. When she is the one discussing schedules, deliveries, and DM strategy, his alarm never goes off, the creator stays happy, and you stay invisible in the background running traffic and banking.

Two honest notes. Hire that manager because she is genuinely good at the job, not as a prop—this only works when the person is competent and treated as a real professional. And watch the leading indicator: a sudden drop in creator communication or content output is almost always partner interference starting, not laziness. Catch it early, address it calmly, and never let someone else’s fragile ego stand between you and a working revenue pipeline.

The law.

Law #17: Never rely on employee intuition, never hold an energy-draining asset out of greed, and never trigger a partner’s ego.

Operator’s checklist.

Pick the problem in front of you. Do something about it.

• Convert every task that currently relies on employee judgment into an explicit SOP or decision tree.
• Audit access: registrar, servers, and banking portals stay with you—everyone else gets scoped permissions.
• Add automated verification or a QA step so “done” is confirmed rather than assumed.
• Score each asset on energy drain as well as revenue. High dollars plus high drain means look at exiting.
• When a fair offer arrives on a high-friction business, take the liquidity and redeploy into automated assets.
• Watch for sudden drops in creator communication or output as an early sign of partner interference.
• Put a competent, professional account manager between yourself and roster communications.

Common questions