With the Barrett contract secured, Sullivan Industries began its transformation. Our workforce grew from twenty engineers to over one hundred and fifty employees within eighteen months. We opened a second facility, tripled our production capacity, and invested in cutting-edge testing equipment. Revenue climbed steadily from two million annually to over forty-five million. Each quarterly meeting showed greater profitability, and trade publications began featuring Sullivan Industries as an emerging aerospace powerhouse.
At the center of this growth was my most significant innovation, the Sullivan S-500 aircraft control system. Revolutionary in its design, the S-500 offered unprecedented precision, reliability, and energy efficiency. I had conceptualized it during a rare weekend off, sketching initial designs on napkins at a coffee shop. Eighteen months of intensive development followed, with me personally leading the engineering team through countless iterations and testing phases.
When we unveiled the system at the International Aerospace Expo, it generated immediate interest from commercial and military clients alike. “The S-500 will be Sullivan Industries’ legacy,” I told my father proudly after three major manufacturers requested implementation specifications on the same day.
He nodded, seeming pleased, but said only, “Let’s see if it actually delivers the projected revenue.”
It did. The S-500 and its derivatives eventually accounted for sixty percent of company revenue. I created a dedicated engineering division focused solely on advancing the technology, and it became our most profitable business unit. Industry recognition followed. I accepted innovation awards on behalf of the company, gave keynote addresses at engineering conferences, and was profiled in Aviation Technology Monthly as one of the industry’s 40 Under 40 rising stars.
Throughout this period of unprecedented growth, my personal life remained entirely subordinated to company needs. My seventy-hour work weeks were the norm, not the exception. I purchased a modest home five minutes from the office to minimize commute time. Vacations consisted of weekend trips that could be canceled if problems arose. When friends from MIT invited me to join their successful tech startup, I declined without hesitation, my loyalty to Sullivan Industries never wavering.
As the company prospered, my father gradually stepped back from day-to-day operations, though he maintained his title as CEO and never failed to take credit for innovations that had been entirely my creation. During client visits, he would casually mention “our design philosophy” when discussing features he had initially opposed. At industry events, he positioned himself as the visionary behind advances he had barely understood when I first proposed them.
Meanwhile, Lawrence’s role in the company remained ambiguous at best. After several failed attempts to establish himself in sales, he was given the title of Executive Vice President of Business Development, a position that seemed to primarily involve taking clients to golf outings and expensive dinners.
His technical knowledge remained so limited that engineering staff developed a coding system to simplify concepts when he needed to be included in discussions. “Just nod and say it sounds promising,” I overheard one engineer instructing Lawrence before a client meeting. “Amanda will handle the actual details.”
Despite his minimal contributions, Lawrence excelled at one crucial skill: currying favor with our parents. He praised my father’s mentorship during family dinners, consulted my mother on business decisions that should have been operational matters, and positioned himself as the loyal child who prioritized family above all.
Those performances seemed harmless at first. Lawrence had always been the family charmer. But they were laying groundwork I didn’t yet recognize.
As Sullivan Industries approached its thirtieth anniversary, subtle but concerning changes began appearing in company dynamics. My mother, whose business experience was limited to basic accounting, inserted herself increasingly into technical decisions. My father began excluding me from financial meetings while including Lawrence.
When I purchased my modest three-bedroom home with my own savings, my parents commented that it was practical but small, while they helped Lawrence finance a sprawling five-bedroom house in the city’s most exclusive neighborhood. “Lawrence needs to project success to our clients,” my mother explained when I questioned the different treatment.
The more recognition I received from the industry, the more I sensed a cooling from my family. When Aviation Technology Monthly featured me on its cover with the headline, The Engineering Mind Revolutionizing Aerospace, my father’s only comment was to ask whether I had mentioned Sullivan Industries’ founding story prominently enough. When I was invited to join the prestigious Aerospace Innovation Roundtable, the first person from our company ever included, my mother wondered aloud if attending the quarterly meetings would distract from “actual work.”
The most telling moment came during a family dinner celebrating a record-breaking quarter. As we toasted the company’s success, my father raised his glass. “To Sullivan Industries’ bright future under the next generation of leadership.”
His eyes rested not on me, who had designed the products generating ninety percent of our revenue, but on Lawrence, who smiled with unexpected confidence. “I won’t let the family down,” Lawrence said, returning the toast.
Something in his tone made me uneasy, but I dismissed the feeling. After all, the company’s trajectory was undeniable. My position seemed secure, and surely my parents recognized who was truly driving our success. I couldn’t have been more wrong.
The first concrete sign that something was shifting came when my father’s assistant scheduled a quarterly strategy meeting without including me. When I mentioned the oversight, she looked uncomfortable. “Mr. Sullivan said this one is just for family leadership,” she explained.
“I’m family leadership,” I replied, confused.
“I meant your father, mother, and Lawrence,” she clarified, not meeting my eyes.
I confronted my father afterward, trying to keep my tone casual. “Was there a reason I wasn’t included in today’s strategy meeting?”
He waved dismissively. “Just financial planning. Nothing engineering related. Lawrence needs to understand the business side more thoroughly if he’s going to take over someday.”
The phrase “take over” lingered in my mind. Take over what? The entire company? Wasn’t I already running the most critical and profitable division?
This exclusion became a pattern. Financial reviews, long-term planning sessions, meetings with our corporate attorneys. Suddenly, these were “non-technical matters” that didn’t require my presence.
Meanwhile, Lawrence began appearing in my territory with increasing frequency, asking questions about our engineering processes and client relationships that seemed more like intelligence gathering than genuine interest.
During a family dinner that spring, Lawrence casually mentioned an innovative approach to the Raytheon contract that I had developed the previous week. “I was thinking we could modify the control architecture to incorporate redundant fail-safes,” he said, using terminology I knew he didn’t understand. “It would give us a competitive edge.”
My father nodded approvingly. “That’s exactly the kind of forward thinking we need.”
I stared at Lawrence, recognizing my exact words from a team meeting he hadn’t even attended. He must have been reading my project notes or getting information from someone on my team. When I tried to clarify that this was already being implemented, my mother interrupted to ask about Lawrence’s recent client dinner.