Will Revieu

Localization sent me a contract comparison showing our French terms gave customers 30 years to cancel. I asked her how that happened. The English version said 30 days. The translation tool read “d” as “décennies.” She said the French text was still “semantically close.” I said three decades is not close to one month in any language. She changed it manually to 30 jours. Then the Japanese version turned “reasonable notice” into “notice that causes no emotional disturbance.” I asked whether humans were reviewing these. “Only flagged sections.” The tool had flagged neither. She asked whether any customers had complained yet. Not yet. “Then we’re early.” Customer Success had already sent both versions to 240 accounts. A project retro said Legal had introduced a manual-review bottleneck. Contracts are now reviewed locally. Time has resumed normal dimensions.

A $25 “correction processing fee” appeared on an analyst’s paycheck under a new policy from the Payroll Director. I called her. “Why is he paying us to fix our mistake?” “It discourages unnecessary tickets.” The original error was a missing $40 reimbursement. She corrected it and charged $25. Then the fee itself posted twice. The analyst reported that error. The system automatically charged another $25 for the new correction request. I explained that employees cannot be charged simply for asking the company to pay them correctly. She asked whether $5 would be more reasonable. The amount was not the issue. She renamed it “pay accuracy co-pay.” No. By afternoon, 91 fees had been reversed. A note to Finance said Legal had eliminated a self-funding support model. The final payroll correction was correcting the correction fee.

Trust & Safety launched a “pre-violation” suspension program. I learned about it when a customer appealed a ban for something he had not done yet. The model gave him a 94.7% probability of violating the rules within 30 days. I asked her what rule. “Unknown future abuse.” I explained that we can enforce actual terms and credible safety risks, but not punish users for hypothetical breaches invented by a score. She lowered the threshold to 99%. I said the percentage was not the problem. She asked whether a warning before the suspension would make it due process. No. The first new suspension hit our own demo account. She called that evidence the model was unbiased. Sales called it evidence the demo was broken. A calendar invite titled LEGAL FRICTION appeared for Friday. The program is paused pending an event that actually happens.

FOLLOWER TRANSFER appeared as a new field on the Social Media Manager’s offboarding checklist. I asked her what that meant. A departing VP had 83,000 LinkedIn followers. She wanted him to change his name to the company’s name on his last day. I explained that a personal social account does not become company property because someone built an audience while employed here. She proposed transferring only followers acquired during business hours. I asked how she planned to identify them. “Analytics.” No. Then she offered him 10,000 followers from the intern account as replacement inventory. He declined. She asked whether we could at least keep his likes from Q3. No. A complaint reached the CMO saying Legal had “stranded valuable audience assets.” The checklist no longer contains FOLLOWER TRANSFER. The 83,000 followers have remained with the human.

Helpdesk posted a new SLA saying any ticket marked ATTORNEY-CLIENT PRIVILEGED would receive priority support. I asked him why. “Legal risk.” Within an hour, every broken monitor in the company became privileged. One employee submitted “PRIVILEGED: mouse feels weird.” Another marked a forgotten Wi-Fi password as work product. Someone claimed the coffee machine was protected by common-interest privilege. I explained that privilege depends on confidential legal communications, not whatever subject line gets someone faster IT. He removed the priority rule. Then employees started copying me on tickets to “make them privileged.” I received 73 emails about keyboards before lunch. One person copied outside counsel on a printer jam. A service review said Legal had become an unexpected routing dependency. I removed myself from the queue. Privilege now has the standard 3–5 business day response time.

At 8:14, the Sustainability Lead dropped a carbon-offset certificate on my desk and said our permit issue was “net zero now.” I asked what she offset. “The violation.” We had exceeded an emissions limit at one facility for 11 days. She bought 14,000 tree credits and attached them to the incident file. I explained that voluntary carbon offsets do not erase a regulatory exceedance or the obligation to report it. She bought another 14,000. “For conservatism.” I said twice the trees still did not change the permit. She asked whether the regulator accepted carbon credits. Not as a substitute for compliance. She added a slide showing “200% remediation coverage.” Compliance removed it. An executive survey later said Legal was obstructing market-based solutions. The regulator still wants the incident report. The trees remain outside the jurisdiction.

Internal Audit announced that the expense review had achieved a 100% pass rate. I asked to see the sample. Every transaction over $10,000 had been excluded. So had cash withdrawals. Weekend charges. International vendors. And anything containing the words “consulting” or “miscellaneous.” I asked what remained. “Low-risk spend.” I explained that an audit sample designed to avoid suspicious transactions cannot prove suspicious transactions do not exist. She added one $12,400 charge back in. It was office chairs. Pass. Then she declared the methodology validated. I asked about the excluded $86,000 wire labeled SPECIAL PROJECT. She said including it would distort the trend. A retro memo later said Legal had “expanded scope after testing.” The pass rate is now 61%. The final memo calls the 39-point drop a legal adjustment.

A VC board observer forwarded me a deck with “VOTE CAST” stamped across the cover. I called him. “You know you don’t have a vote.” “I know, but I have conviction.” He had been emailing directors his preferred vote before every meeting and marking anyone who agreed as “delegated.” I explained that an observer does not acquire voting power because directors happen to like his answer. He sent me a spreadsheet showing 4.6 votes. I asked about the decimal. “One director is only mostly aligned.” He asked whether he could at least break ties. I said he could observe them. He updated the sheet to call the votes “influence units.” The Chair later complained that Legal had made investor participation feel ceremonial. The board materials now distinguish votes from influence. He still has 4.6 influence units. They remain legally weightless.

Privacy Counsel sent me a flowchart titled “Consent Optimization.” The green path said ACCEPT in one click. The gray path said MANAGE PREFERENCES and opened 17 screens. I asked why rejecting cookies required a ZIP code. “Localization.” And a date of birth? “Verification.” I explained that refusing consent cannot be deliberately harder than giving it. She removed the ZIP code. Then she added six confirmation screens asking whether the user was “sure about privacy.” I said no. She replaced them with a five-second countdown before Reject appeared. “What if it only happens once per device?” Still no. By lunch, Product had data showing acceptance up 23%. A Slack recap said Legal had “reduced conversion upside.” The test was rolled back. Accept and Reject now sit beside each other. Conversion has encountered equal protection.

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.