That was the beginning. Not the polished version Emma later told reporters about pivoting our company into software, but the real beginning: me writing code on a secondhand workstation in a room full of discarded parts while Mom brought microwaved leftovers in ceramic bowls and told me not to let my coffee go cold. The first year after graduation, I did everything. Product design, onboarding, support, demos, implementation, bug fixes, billing follow-ups, weekend data migrations for clients who could not afford downtime. Dad kept the repair side alive while I slowly built out the software business. Then I hired our first engineer, a former classmate named Luis who had turned down a bigger salary because he believed the product solved a real problem. Then our first account manager. Then two more developers. I learned how to interview for skill and steadiness, how to fire quickly when someone lied, how to reassure a panicked client at five in the morning before the East Coast workday began. The business did not explode. It grew the way healthy things do—through repetition, credibility, and a thousand invisible corrections.
Those early years demanded a kind of stamina that never photographs well. There were stretches when I worked fourteen hours a day for weeks at a time and considered a ten-minute walk around the parking lot a luxury. I missed weddings, birthdays, and entire weekends. I learned to keep flats under my desk because sometimes a client dinner ended at ten and a server outage began at ten-fifteen. When people say they built something from nothing, what they usually mean is that they survived the period when nobody was impressed. They survived before the valuation, before the logo redesign, before the conference panels and flattering headlines. That was my life. Every meaningful piece of Chen Technologies had my fingerprints on it before the name was ever worth repeating at a networking event.
Emma, meanwhile, thrived in the world she had always wanted. She attended an elite business school, spent summers interning at firms with views of Manhattan, and sent home holiday cards that looked like professional headshots. At family dinners, Dad read her LinkedIn updates out loud. “Senior analyst by twenty-six,” he would say with wonder, as if my shipping a stable product to paying clients somehow counted less because it happened in our own office instead of a tower with marble floors. I told myself comparison was pointless. I was building something concrete. She was building an image. The trouble with images, though, is that families are often more loyal to what flatters them than to what feeds them.
Five years after I launched that first product, Chen Technologies crossed one million dollars in annual recurring revenue. We had moved out of the strip mall into a modest office with a glass entryway, open workstations, and a server room that no longer doubled as storage for broken printers. We had real benefits. A growing engineering team. Clients in four states. Renewal rates strong enough to make investors begin returning Dad’s calls. It should have been the most satisfying season of my life. Instead it was the season Emma came home. She announced her resignation from a prestigious consulting firm during Sunday dinner as if she were granting us a royal favor. “I’ve done what I needed to do out there,” she said, setting down her wineglass. “Now it’s time to professionalize the family business before it hits a ceiling.” Dad’s face lit up with the kind of pride I had spent years learning not to chase. Mom looked at me immediately, already worried.
I remember the exact sensation in my body when Dad said, “That’s wonderful, princess. We could use your expertise.” It was not shock. It was something flatter and colder: recognition. A realization that all my years of labor could be reframed in a single sentence as groundwork waiting for Emma to arrive and make it legitimate. I tried to object carefully. I said software was not the same as management consulting. I said our clients valued continuity and domain knowledge. I said leadership should come from demonstrated contribution, not pedigree. Dad heard only resistance. Emma heard insecurity. “Sarah,” she said, with that maddening combination of pity and superiority, “no one is taking anything from you. The company just needs someone who can speak the language of investors and growth strategy.” As if the language of growth were not the codebase, the clients, the roadmap, and the people who had stayed because I had earned their trust one unglamorous day at a time.
Within a month, Emma was named co-chief executive officer. There was no formal search, no real board process, no performance review, no measurable case made beyond Dad’s faith in her credentials and his growing embarrassment that the public face of our company was a woman who preferred product review meetings to stage lighting. He told me it would be good for the brand. He said investors liked polished stories. He said I should be relieved to focus more on what I was good at. I remember going home that night, sitting in the dark at my kitchen counter, and staring at the wall for almost an hour before realizing I had not taken off my shoes. The company that carried my ideas, my risks, and my exhaustion had just been split at the top like an inheritance I was lucky to share.
