“This is serious, Amanda. The system is showing anomalies in testing. The client is threatening to reject the entire shipment.”
“That sounds like a problem for your engineering team,” I said.
“You know damn well we don’t have an engineering team anymore.” His composure cracked. “Half the department resigned, and the new hires don’t understand your designs.”
“My designs?” I couldn’t help but press the point. “According to company communications, Lawrence is the engineering visionary behind all Sullivan innovations. Surely, he can resolve these technical issues.”
The silence on the other end was telling.
“If Sullivan Industries wants to hire Pathway Aerospace Engineering as a consultant, you can contact our business office to discuss rates,” I continued. “Otherwise, I wish you luck with your technical challenges.”
I ended the call feeling neither triumph nor bitterness, just a clear-eyed recognition that I was finally establishing appropriate boundaries with people who had never respected mine.
My mother’s response came through a different channel. Three days later, a mutual family friend forwarded me a link to her private Facebook post describing how her ungrateful daughter had abandoned the family business after everything they did for her and was now actively trying to destroy her brother’s success out of jealousy. The post included childhood photos of Lawrence and me, carefully selected to show him as the loving brother and me as perpetually dissatisfied.
It was a masterclass in manipulative narrative, and it would have wounded me deeply just weeks earlier. Now, I simply forwarded it to Patricia with a note: “Potential defamation to discuss.”
By the two-month mark after my termination, Pathway Aerospace Engineering had secured initial funding, leased permanent office space, and begun the process of patenting my newest innovations—designs I had conceptualized but not documented within Sullivan Industries. Former team members were preparing to join as soon as their notice periods or non-competes allowed. Most significantly, three major clients had indicated they would transfer business to my new company once we were operational.
The contrast between my forward momentum and Sullivan Industries’ deterioration became increasingly apparent. Industry gossip reported production delays, quality control issues, and client dissatisfaction. The company’s stock value had dropped twenty-three percent. Lawrence had been conspicuously absent from recent industry events, and rumors circulated about emergency board meetings.
Then came the call that confirmed everything. Sullivan Industries’ largest military contractor requested an urgent meeting with me, not to discuss future business, but to address concerns about systems already in production.
“We’ve identified critical failures in the latest S-500 implementation,” the procurement director explained. “The documentation indicates you were the principal engineer, but Sullivan claims they can’t consult with you due to conflicting business interests. We’re considering invoking the safety override clause in our contract to bring you in directly.”
The safety override was a standard provision in military contracts allowing manufacturers to consult with the original designers regardless of current employment status when public safety was potentially compromised. Its potential invocation represented a worst-case scenario for Sullivan Industries: a public admission that they couldn’t maintain the quality of their own signature product.
As I ended the call, I realized that the company my grandfather had built, that I had helped transform into an industry leader, was now facing an existential threat. Not because I had sought revenge, but because my parents and brother had fundamentally misunderstood what actually made the business valuable.
The next day, my father called again. This time, I could hear genuine fear in his voice. “We need to talk, Amanda. Not as Sullivan Industries and a former employee. As family.”
The consequences of my parents’ decision unfolded with the inexorable logic of an engineering failure analysis—one compromised component leading to system-wide collapse. Two days after my father’s desperate call, Sullivan Industries lost its cornerstone military contract. The client cited “critical personnel changes affecting product integrity” in their termination letter. Corporate language for: “You fired the only person who understood how this technology actually works.”
The contract had represented thirty percent of Sullivan’s annual revenue. News of the termination leaked to industry publications within hours. Sullivan Industries stock dropped eighteen percent in a single trading day. Financial analysts began questioning the company’s viability without its core technical leadership. Suppliers tightened credit terms, demanding payment up front where they had previously offered sixty-day terms.
I watched these developments with complicated emotions. The company still employed people I respected—engineers, production staff, and support personnel who had done nothing to deserve this instability. Yet, there was undeniable vindication in seeing the natural consequences of my parents’ choices unfold.
The morning after the stock plunge, Lawrence called me directly for the first time since my termination. “This is your fault,” he began without greeting. “You turned our military clients against us.”
“I haven’t spoken to your military clients,” I replied truthfully. “They reached out to me with safety concerns, which I referred back to Sullivan Industries as required by regulation.”
“You know exactly what you’re doing,” he continued, his voice slurring slightly despite the early hour. “You’ve always been jealous that Dad wanted me to take over eventually.”
“Lawrence, are you drinking at nine in the morning?”
The silence confirmed my suspicion. When he spoke again, his tone had shifted from accusation to something closer to desperation. “Just tell me how to fix the stabilization issue in the S-500. I have the technical team working around the clock, but no one understands the adaptive calibration sequence.”
“That’s because I designed it specifically to prevent unauthorized modification,” I explained. “It’s a security feature for a system with military applications, Lawrence. It’s functioning exactly as intended.”
After I hung up, I sat for a long moment considering the implications. Sullivan Industries was imploding faster than I had anticipated. While my strategic focus had been building Pathway Aerospace, circumstances were creating an unexpected opportunity and responsibility.
That afternoon, I convened a meeting with my core team at Pathway. “Sullivan Industries is failing,” I told them bluntly. “We need to consider what that means for our industry, their employees, and our future plans.”
Michael, my former lead engineer, asked the question everyone was thinking. “Are we accelerating our timeline to capture their market share?”