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.”

At 11:03 a.m., my phone started ringing. An unknown number with Sterling’s area code. I let it go to voicemail. Then another call from a different number, then a third. The panic was beginning.

I pulled up the system connection logs and watched failed authentication requests hammering uselessly against the demonstration package Olivia’s IT team was trying to operate as live infrastructure. Hundreds of failed handshake attempts. Every request bounced back empty because there was no actual system behind the interface. They were trying to run a factory using only a photograph of the control room.

By 11:25 a.m., the situation had deteriorated significantly. Production gridlock at fourteen major choke points across four states. Quality-control conflicts at twenty-three different inspection stations. Assembly schedules falling behind by an average of seventy-three minutes across the network. And somewhere in a corporate office, Olivia Matthews was probably staring at user-interface screens that still showed everything functioning normally, wondering why reality didn’t match her data.

At 11:32 a.m., an email arrived with red priority flags. Subject line: “URGENT—Critical System Failure.”

“Multiple operational conflicts. No response from coordination controls. Quality assignments completely desynchronized. This is affecting OEM contracts and delivery schedules. Need immediate support. Please respond ASAP. Brad Coleman, IT Director.”

The corporate politeness was cracking. They were starting to understand this wasn’t a minor technical issue. I closed the email without reading the rest and checked the impact calculator I had built into my monitoring tools. Conservative estimate: $2.3 million in daily losses from halted production, missed schedules, and quality violations. The real number was probably higher once you factored in OEM penalties and contractual breaches.

My phone buzzed with a text from Olivia. “Emergency situation. Call immediately.”

I deleted the message. At 11:46 a.m., the phone rang again. This time, the caller ID showed Sterling Legal Department. I declined the call and watched it roll to voicemail. Then another call from a blocked number. Declined.

By noon, I had sixty-seven missed calls and thirty-four unheard voicemails. The twelve-facility manufacturing network was experiencing what Ford would have called a cascading systems failure. Nothing was coordinating with anything else. Assembly workers were making decisions based on stale information. Floor supervisors were issuing conflicting instructions. Production managers were trying to manually assign station schedules while their computers insisted everything was running smoothly.

I opened a new document on my laptop and started typing: “Emergency System Restoration Proposal.” The terms were straightforward. Payment due via wire transfer before reactivation. Rate: three times the standard monthly fee for immediate restoration service. Duration: a forty-eight-hour emergency window. Conditions: full acknowledgment of service terms and intellectual property ownership.

I attached the document to an email addressed to Olivia Matthews, legal counsel, and the operations director. Subject line: “Emergency Restoration Services Available.” Then I hit send and ordered another cup of coffee. The education phase was complete. Now came the negotiation.

At 12:53 p.m., the calendar invite arrived: “Emergency Conference Call. 1:00 p.m. Eastern. Immediate Response Required.” No polite language, no corporate pleasantries, just panic and capital letters.

I joined the call at 12:57 p.m. Professional appearance, calm demeanor, sitting in my home office with my engineering certifications visible in the background. The screen filled with stressed executives in various stages of crisis management. Alan Brooks, some kind of senior VP, joined first, sleeves rolled up, wearing the expression of a man who had spent the last three hours in emergency meetings. Then came legal counsel: two attorneys, one taking rapid notes, the other reviewing documents on a second monitor.

Tony Martinez, the floor supervisor I had worked with during the original implementation, appeared next. Former military like me, he understood systems thinking. He looked exhausted but unsurprised, like he had been expecting this conversation for weeks. Olivia Matthews was already in the call when I connected, positioned in a small window at the bottom of the screen. Muted microphone, tight body language that suggested she had been removed from leadership of her own crisis.

Nobody said hello. Alan cleared his throat and launched straight into damage control.

“Harold, appreciate you joining on short notice. We’re dealing with what appears to be a significant operational disruption. Our entire network is essentially paralyzed, and we need to understand our options for immediate restoration.”

I nodded once. “Your service agreement was terminated yesterday. If you want operational access restored, the terms are outlined in my emergency proposal.”

One of the attorneys leaned into her camera. “Harold, we’ve reviewed your proposal. Some of the financial terms seem disproportionate given the circumstances.”

“Emergency-response pricing,” I replied. “Standard practice when critical infrastructure fails during business hours.”