“I want recognition for my work,” I finally said. “I want to continue creating and innovating without betrayal hanging over me. I want… I want to build something that’s truly mine, where my contributions can’t be stolen or denied.”
Dr. Winters nodded. “Then let’s start there. Not with what you’ve lost, but with what you’re going to create next.”
That conversation marked the beginning of my strategic rather than emotional response. The next morning, I called Patricia Hernandez, the intellectual property attorney I had consulted earlier. “I won’t be signing their severance agreement,” I told her, “and I want to discuss options for protecting my innovations.”
Patricia’s assessment was blunt but clarifying. “Based on the documentation you’ve provided, there are clear instances of intellectual property theft and corporate malfeasance. The question isn’t whether you have a case. You do. The question is whether a prolonged legal battle with your family is how you want to spend the next two to three years.”
She outlined my options: an aggressive legal strategy that would likely result in a favorable settlement but consume my energy and focus for the foreseeable future, or a more targeted approach that would protect my most significant personal innovations while allowing me to move forward professionally.
“They’re expecting you to either accept their terms out of family loyalty or fight them on everything out of anger,” Patricia explained. “A selective, strategic response will catch them off guard.”
I chose the strategic path. Rather than contesting everything, I focused on documenting and legally protecting specific innovations that I had clearly developed on my own time. I authorized Patricia to send a precisely worded letter refusing the severance package, rejecting the non-compete as unenforceable, and demanding the immediate return of my personal engineering notebooks and intellectual property.
“This is just step one,” Patricia warned. “Be prepared for them to escalate before they consider compromise.”
While the legal wheels began turning, I received an unexpected call from Bernard Holton, the CEO who had warned me about Lawrence’s comments months earlier. “I just had the most baffling technical meeting with your brother,” he said without preamble. “Amanda, he presented specifications for an updated control system that violated basic physics principles. When our engineers questioned the discrepancies, he couldn’t provide coherent answers. What’s happening at Sullivan?”
This was the first of what would become a steady stream of similar calls from clients, suppliers, and industry partners. Lawrence was attempting to maintain the façade that nothing had changed, but his profound lack of technical knowledge was becoming increasingly apparent in every interaction.
Meanwhile, something remarkable was happening within Sullivan Industries. Two weeks after my termination, Rachel submitted her resignation. The day after, Michael and three other senior engineers from my team did the same. By the end of the month, eleven key technical staff had left the company.
“No one wants to work for someone who doesn’t understand what they’re doing,” Michael told me during a lunch meeting. “And no one trusts leadership that would discard the person who built the entire technical foundation of the company.”
The exodus created an unexpected opportunity. With a core group of experienced engineers who shared my vision for technical excellence, I began considering the possibility of starting my own firm—not just as a response to betrayal, but as the chance to build something aligned with my grandfather’s original values: innovation, integrity, and long-term thinking.
I leased a small office space and invited my former team members to discuss the possibility. The response was overwhelming. Not just enthusiasm for the venture, but immediate commitments to join once non-compete periods expired. Within three weeks, I had drafted a business plan for Pathway Aerospace Engineering, focusing on next-generation control systems for commercial and defense applications.
The first call from my father came exactly one month after he had fired me. I let it go to voicemail. “Amanda, we need to discuss some technical questions about the Raytheon implementation,” he said, his voice lacking its usual confidence. “Call me back when you get this.”
I didn’t. Three more calls followed over the next two days, each message increasingly urgent. Finally, I received a text directly from Lawrence. “Can’t make sense of your notes on the S-500 redundancy systems. Client meeting tomorrow morning. Need your input ASAP.”
I forwarded the message to Patricia with a brief note: “Documentation of ongoing use of my intellectual property.”
The real shock came two days later when Rachel called with news from inside Sullivan Industries. “They lost the Anderson Aerospace contract,” she said. “Lawrence couldn’t answer technical questions during the quarterly review, and when the client asked to speak with the engineering team, he couldn’t produce anyone with more than three weeks of experience on the project. They pulled forty million dollars of business on the spot.”
I felt a complex mix of emotions: vindication tinged with sadness for the company my grandfather had built; satisfaction at the natural consequences of my parents’ choices, alongside concern for the employees who remained. But mostly, I felt a growing clarity about my path forward.
That clarity strengthened when I received a call from Westfield Technology Partners, a venture capital firm specializing in aerospace and defense startups. “We’ve been following your work at Sullivan for years,” said the managing partner. “Several of your former clients mentioned you might be establishing your own venture. We’d be very interested in discussing investment possibilities.”
Within days, I had meetings scheduled with three different investment groups, all eager to back an engineering firm led by the innovator behind Sullivan Industries’ most successful products. The irony wasn’t lost on me: the very expertise my parents had devalued was now my most valuable asset.
Six weeks after my termination, I made my first public appearance at the National Aerospace Engineering Conference. I had debated attending, knowing I would encounter industry colleagues who would question my departure from Sullivan Industries. But Patricia had been adamant. “Hiding creates the impression you’ve done something wrong,” she said. “Appearing confident and focused on the future controls the narrative.”
She was right. At the conference, I was approached continuously by colleagues expressing support and clients inquiring about my future plans. Several mentioned concerning quality issues that had emerged in Sullivan products since my departure. Most significantly, two major clients took me aside to explicitly state they would follow me to any new venture.
The most satisfying moment came during Lawrence’s presentation on next-generation control systems, a session I attended incognito in the back row. He stumbled through slides I had created months earlier, unable to answer basic technical questions from the audience. When an engineer from Boeing asked about the adaptive response algorithms, a feature I had personally designed, Lawrence’s answer was so incoherent that several attendees actually walked out.
As I quietly exited the session, my phone buzzed with yet another call from my father. This time, I answered.
“Amanda.” His voice carried an unfamiliar note of anxiety. “We need to talk about the Johnson implementation. There are issues.”
“I don’t work for Sullivan Industries anymore,” I replied calmly. “Remember? I was too expensive.”