A customer’s GC copied me on an email titled “Does our contract die with Greg?” I called the Sales Director who had written the underlying message. “What did you tell them?” “That the aggressive terms were tied to me.” “They aren’t.” He had promised that every unfavorable provision would “basically expire” if he left the company. I explained that contracts bind the company, not whichever salesperson happens to own the account. He said it was mostly reassurance. Then he got promoted to another territory. The customer immediately emailed asking whether the indemnity had vanished. I said no. He suggested temporarily moving back to the old territory. I said geography was not the issue. He blamed Legal for making his transition awkward. The contract survived his promotion. Greg did not achieve force majeure.

An outside counsel partner sent me a $96,000 invoice for a memo largely drafted by AI. I called him. “Why are there 1,842 entries for prompt refinement?” “Iterative legal analysis.” “And 611 entries for reviewing the answers?” “Human oversight.” The memo was eleven pages. I asked what exactly the AI had saved. “Associate time.” The invoice was 18% higher than the same project last year. I explained that efficiency is difficult to credit when every machine interaction becomes a billable event. He offered a 5% technology discount. Then added a 7% “AI supervision allocation.” I rejected it. He offered to have an associate manually review the discount. I declined. He blamed Legal for discouraging innovation. The revised invoice no longer mentions AI. It still costs $96,000.

The FP&A director posted a forecast note saying our lawsuit exposure had been “budgetarily resolved.” I called him. “What happened to the $6 million reserve?” “We reduced it to $1.” “Why?” “The model doesn’t accept zero.” I asked whether the underlying claim had changed. No. I explained that changing a planning assumption does not change the company’s actual legal exposure. He said the lower number improved the downside case. Then he moved the remaining $5,999,999 into “unmodeled optimism.” He also changed the litigation probability from 70% to “unlikely-ish.” The auditors found it in eleven minutes. He blamed Legal for introducing volatility into the forecast. The reserve is back. Unmodeled optimism has been removed from the balance sheet.

The Chief of Staff forwarded me a new executive policy called “Decisionless Decisions.” I opened it. Every executive decision would be phrased as a question so nobody could later be identified as the person who decided it. “Should we close the office?” “Could pricing increase 20%?” “Might we terminate Greg?” I called him. “This does not do what you think it does.” He said questions were inherently nonbinding. I explained that records are interpreted by what actually happened, not punctuation. He changed every question mark to “for discussion only.” Then leadership executed all nine items. He added “no final decision taken” to the log after each one. The board asked who approved them. He blamed Legal for making documentation confusing. The decision log now contains no decisions. It is extremely decisive.

Nothing warms my heart like watching BigLaw discover “these are our standard terms” from the other side of the table.

A 7:30 calendar invite from the Head of Partnerships was titled “Contractor Optimization.” I joined and found a diagram with six LLCs orbiting one employee. “What am I looking at?” “Optionality.” He wanted the employee to resign Friday, invoice us through six companies Monday, and rotate entities monthly so “no single contractor becomes too dependent.” I explained that multiplying LLCs does not change who is actually doing the work or how the relationship functions. He removed five LLCs. Then proposed paying the sixth in airline miles. I said the payment method was not the issue. He suggested making the employee CEO of the LLC instead. Still the same person. He blamed Legal for eliminating flexibility. The employee remains employed. The six LLCs are apparently “strategic reserves.”

The Director of Data Science announced that customer records were now anonymous because the model only saw embeddings. I asked whether the company could reverse them. “Not easily.” “That wasn’t my question.” He admitted the lookup table still connected every vector to a customer ID. I explained that converting personal data into another representation does not make it anonymous if we can still reconnect it to a person. He deleted the lookup table. Then discovered the production pipeline recreated it every four minutes. He renamed it NOT_PII.csv. I stared at him. He said naming conventions matter for audits. I said facts matter more. He blamed Legal for moving the definition of anonymous. The file is now called PLEASE_DELETE_THIS.csv. It regenerates beautifully.

A Billing Ops manager’s ticket landed in my queue after one customer disputed the same $750 fee five times. I opened the history. Every dispute automatically triggered a $750 “dispute processing fee.” The customer disputed that. Another $750 appeared. Then another. I called him. “Did we build a fee that reproduces when challenged?” “It discourages frivolous disputes.” I explained that a billing system cannot manufacture new charges merely because a customer contests old ones without contractual authority. He disabled the automation. The balance had already grown from $750 to $4,500. He asked if we could collect the generated fees anyway. No. Then he suggested waiving one as goodwill. I said we should waive all of them. He blamed Legal for rewarding complaints. The original dispute is still open. It now has six children.

I walked into a Revenue Accounting review where the VP had moved 14 unpaid invoices into a column called “verbally collected.” I asked what that meant. “The customers said they’d probably pay.” “That isn’t collected.” She showed me a $380,000 invoice marked PAID IN PRINCIPLE. I explained that hopeful conversations do not turn receivables into cash or settle contractual disputes. She changed the column to “commercially complete.” Still unpaid. Then one customer formally rejected the invoice. She moved that one to “payment timing variance.” I asked where actual payments went. A separate tab called Cash. She said Legal was being overly literal about the word collected. The board deck now says 96% collection. The bank account remains more nuanced.

Subject: FOUNDER SIGNATURE AUTHORITY landed in my inbox from our founder-advisor. He had signed a $2.4 million vendor agreement as “Founder, Forever.” I called him. “You know you’re not an authorized signatory anymore.” “I founded the company.” “That is historical information.” He said customers found the title reassuring. I explained that founding a company does not create permanent authority to bind it after the board changes signing powers. He updated the signature block. Founder, Forever, Authorized Spiritually. I said no. He changed it to Founder Emeritus and signed two more agreements. Procurement blamed Legal for confusing vendors about his status. His email signature now says “Founder, not an authorized signatory.” He says it looks hostile. It is unusually accurate.

The VP of Brand sent me a screenshot of our new trademark enforcement bot firing its first warning. “Who did it warn?” “Us.” The bot had found our old logo on 846 archived help-center pages and generated cease-and-desist letters to our own web team. I told her trademarks are supposed to stop confusing third-party use, not launch an internal civil war. She paused the bot. Then she narrowed the rule to “unauthorized external use.” It immediately flagged our investor deck because it lived on Dropbox. She asked if Legal could whitelist the company. I said the company should probably be allowed to use the company’s logo. She blamed Legal for weakening automated enforcement. The bot is now in review. Our website has until Friday to respond.

Engineering pinged me, “Can we keep an admin account alive just for the SOC 2 screenshot?” I said no. The account was named DO_NOT_DELETE_TEST_GUY. Engineering called it “legacy evidence.” I asked whether it could access production. “Yes, but only for audits.” I explained that keeping an unnecessary admin account to prove access controls exist is the opposite of proving access controls work. They disabled it. The auditor requested a new screenshot. Someone recreated the account so the screens would match last year. I watched this happen. The CTO blamed Legal for inconsistent evidence. We disabled it again. Both screenshots are unfortunately authentic.

Recruiting’s new moonlighting form produced its first conflict alert before breakfast on Monday morning. It was an engineer who sold a couch on Facebook Marketplace for $80. HR flagged it as a potential competing business. I asked whether we now competed in used furniture. They said revenue was revenue. I explained that conflict policies should target actual conflicts, not every occasion when an employee receives money. By lunch, disclosures included babysitting, fantasy football winnings, and a $12 Venmo refund. HR blamed Legal for narrowing visibility. The couch has been cleared.

A Support L1 ticket marked HIGH PRIORITY landed in my queue: CUSTOMER SAYS LEGAL WAIVED $42K FEE. The escalation queue was named Legal Department and staffed entirely by Support. I had never spoken to the customer. Support had built a macro signed WILL, GENERAL COUNSEL. I explained that impersonating the General Counsel is not a customer-service technique. They changed the signature to LEGAL TEAM. Then to LEGAL-ADJACENT RESOLUTION SPECIALIST. I deleted the macro. Support blamed Legal for increasing escalations. The queue is back to Customer Support. I am no longer scalable.

Growth sent a 15-minute invite titled “Referral Program Edge Case.” I joined and learned one customer had referred himself 312 times. Same name. Same card. Same apartment. Email addresses ran from kevin1 through kevin312. Growth said the rules did not expressly prohibit multiple identities. I explained that a referral program does not require paying one person $50 each time he introduces himself to us. Growth froze the account. Kevin emailed demanding his $15,600. Then Growth asked Legal to draft an anti-Kevin clause. I declined. The program now requires unique customers. Kevin remains our most productive ambassador.

Treasury opened 26 accounts at the same bank during its quarterly risk review. The Treasurer called it diversification because “one account can fail.” I explained that twenty-six accounts at one institution are still exposed to one institution. Treasury said the account numbers were different. Then they distributed cash evenly across all 26. The bank froze twelve for unusual activity. Payroll nearly missed. Treasury blamed Legal for insisting on formal banking relationships instead of “agility.” We consolidated the accounts. The risk register now lists one bank. Treasury calls that concentration. I call it counting.

I walked into a Legal Ops review and found a new invoice rule on the projector. It automatically rejected any line containing the word research. I asked why. “Efficiency.” One firm responded by billing 63 hours for “thinking.” Another used “targeted knowledge acquisition.” A third billed $18,400 for “looking into stuff.” I explained that renaming legal work does not make the work disappear or the invoice easier to evaluate. Legal Ops expanded the banned-word list. Research. Review. Analyze. Draft. By Friday, one invoice contained only partner initials and dollar amounts. Finance rejected it as insufficient detail. Legal Ops blamed me for encouraging creative billing. The rule has been suspended. Outside counsel has rediscovered verbs.

Investor Relations forwarded me a screenshot of a thumbs-up emoji and wrote, “Board approval?” I said no. The Chair had reacted 👍 to a Slack message saying, “Thinking about increasing the buyback by $75M.” IR had already treated that as authorization. I explained that an emoji reaction is not a substitute for the approval process required for a corporate action. The Chair added a second 👍. IR asked if two changed anything. No. Then a VC observer added 🔥. Finance began preparing the trade. I stopped it. IR blamed Legal for ignoring modern communication norms. The board later approved it properly. The minutes do not contain emoji.