They fired me effective immediately; the new female ceo said, barely looking up from her tablet, “hand over the smart factory system, all of it”; i smiled calmly: “i’m afraid i can’t… not yours to take.”

George was old-school. He had come up through the ranks, spent years running production before moving into management. He understood that behind every clean dashboard and automated report, there was physical equipment that had to function flawlessly. When I walked into their main facility that first day, the chaos was immediately obvious. Production lines stopped and started with no coordination. Quality control was running blind because their vision systems couldn’t talk to their assembly robots. Predictive maintenance alerts were going nowhere because nobody knew how to interpret the data.

“We’ve got seven different software platforms that don’t communicate,” George explained, walking me through the production floor. “Assembly uses one system. Quality control uses another. Maintenance scheduling is basically manual. Every shift change, we lose two hours just trying to synchronize operations.”

I spent the next eighteen months building them a real system. Not some off-the-shelf package that kind of works if you bend your entire operation to fit it. Custom control algorithms that learned the specific rhythms of their twelve facilities. Predictive maintenance that actually predicted failures before they happened. Real-time quality monitoring that caught defects at the source, not at final inspection. Eighteen thousand lines of code, every algorithm, every database structure, every hardware interface built from scratch and tested until it ran without failure.

The results were immediate and measurable. Zero unplanned downtime. Defect rates dropped from 2.3 percent to 0.08 percent. OEE metrics that made their OEM customers actually compliment them. George would send me detailed quarterly reports, not corporate thank-you notes, but substantive analyses of efficiency improvements and cost reductions.

The contract was crystal clear because I had learned this lesson the hard way years earlier. They licensed operational access to my system. I retained complete ownership of all source code, algorithms, and infrastructure. George signed without hesitation because he understood the difference between using something and owning it. For five years, everything ran perfectly. Monthly payments arrived on schedule. The system performed exactly as designed. George would call occasionally with questions about capacity expansion or new equipment integration, always respectful of the boundaries we had established.

Then George retired. Olivia Matthews arrived three weeks later with her MBA from Stanford and her tablet that probably cost more than most people’s monthly mortgage. Her first communication wasn’t a greeting or an introduction. The subject line read, “Third-Party Vendor Cost Analysis.” The email was pure corporate optimization language about recurring expenditure structures and dependency risk reduction. My invoice hadn’t changed in five years. Same amount, same delivery schedule, same scope of work. But Olivia saw a line item on a budget sheet and immediately assumed there was fat to trim.

I replied professionally, attaching the original contract and a summary of system performance metrics over the past sixty months. Her response came back within two hours.

“Need to schedule comprehensive review of all external service dependencies. Please prepare full documentation for internal assessment of operational systems.”

Operational systems. That phrase told me everything I needed to know about Olivia Matthews. She was the type who thought complex manufacturing infrastructure could be understood by reviewing slide decks and reading executive summaries. Four days later, the email arrived that confirmed my suspicions. The subject line was “System Architecture Documentation Request.” Olivia wanted a complete copy of the system for internal assessment and potential transition planning. She didn’t want to review our service agreement. She wanted to take my system and eliminate the monthly payment.

I sent back a response that was technically accurate and deliberately unhelpful. “Happy to provide all materials included under your current operational license.”

Then I walked out to my garage workshop, sat down at the master control panel I had built specifically for Sterling’s system, and started preparing Olivia Matthews’s education in the difference between access and ownership.

Three days after my documentation response, another email landed. Subject line: “Intellectual Property Clarification.” Olivia wanted written confirmation that all operational software logic belonged to Sterling Automotive Parts. Operational software logic. That was what she called five years of custom manufacturing algorithms, predictive maintenance protocols, and real-time coordination engines, like it was a commodity asset she could inventory and reassign.

I took a screenshot of the relevant contract clause and sent it back, the bold text impossible to misinterpret: “All system architecture, source code, design logic, and operational infrastructure remains the exclusive property of Harold Peterson. Licensed for operational use only. No transfer, replication, or derivative development permitted without explicit written authorization.”

George Whitman had understood that clause perfectly when he signed it five years earlier. You don’t buy a custom manufacturing system like you’re purchasing office equipment. You license access to infrastructure that took years to develop and requires constant maintenance from the person who built it.