Posted in

My Ex-Husband Threw a “Freedom Party” the Night Our Divorce Was Final — Champagne, His Mistress, 60 Cheering Employees

My Ex-Husband Threw a “Freedom Party” the Night Our Divorce Was Final — Champagne, His Mistress, 60 Cheering Employees. When He Walked Into the Boardroom Monday Morning, His Two Biggest Clients Were Already Gone.

He spent Friday night on a rooftop in Seattle toasting his freedom from me. He spent Monday morning in a boardroom learning what that freedom actually cost. For eight years I had built the operational infrastructure of his company — the vendor contracts, the client systems, the retention protocols, the institutional knowledge that lived in my head and nowhere else. When I left in April, I didn’t take anything that belonged to him. I just stopped carrying what he never realized I was holding.

PART ONE: The Party I Wasn’t Invited To

The divorce was finalized on a Friday afternoon in October, in a brief proceeding at the King County Superior Court in Seattle that lasted approximately twenty-two minutes. My attorney, Sandra Lim of Lim & Associates Family Law on Fifth Avenue, sat beside me while the judge reviewed the consent agreement, signed the order, and said the specific, impersonal words that courts say when they are closing a legal chapter that took eighteen months and considerable documentation to reach. I shook Sandra’s hand in the hallway. I took the elevator to the lobby. I walked out onto Fifth Avenue in the October Seattle afternoon, which was doing what Seattle does in October — gray and damp with the particular quality of a city that has learned to be beautiful in the absence of sun — and I felt the specific, grounded stillness of a thing that is finished.

I drove home to the house in Laurelhurst. Not the house I had shared with my ex-husband — that house, the one in Medina with the Lake Washington view and the four-car garage, was his, had always been functionally his, and was now legally his per the settlement terms Sandra had negotiated with the specific, focused precision of eighteen months of work.

The Laurelhurst house was mine — a three-bedroom craftsman on a quiet street two blocks from the lake, purchased four months into the separation with the first distribution payment from the settlement, which Sandra had structured to arrive early specifically for this purpose. I had painted the living room in August. I had planted dahlias in the front garden in September. I had been living there alone for four months and it was, in the specific way of a space that a person has chosen entirely for herself, exactly right.

My name is Katherine Aldridge. I am forty-four years old, a former corporate attorney who had left practice eight years ago to serve as the Chief Operating Officer of Aldridge-Weston Technology Partners — the Seattle-based enterprise software company that my ex-husband, Marcus Weston, had founded in 2009 and that I had spent eight years building the operational infrastructure of, which is a sentence I want to be precise about, because the distinction between helping run and building the operational infrastructure of matters enormously in the context of what came next.

Marcus Weston was forty-seven years old, the founder and CEO of a company that had grown, over fifteen years, from a two-person startup in a SoHo-style office in the South Lake Union neighborhood to a 340-employee enterprise software firm with annual recurring revenue of $68 million and a client list that included four Fortune 500 companies. He was charming in the specific way of founders who have been told since their early thirties that they are visionaries — a charm that is real and functional and that coexists, without apparent tension, with a significant deficiency in the capacity to acknowledge other people’s contributions to their success.

The party was not a surprise. I had been told about it by our former CFO, David Park, who texted me on Friday evening at eight-seventeen p.m. with the specific, careful tone of a man who considers himself loyal to me and is providing intelligence rather than gossip: “He rented out the rooftop at the Charter Hotel for tonight. ‘Freedom party.’ About sixty people. Brittany is there.”

Brittany Nakamura was twenty-nine years old, a product marketing manager at Aldridge-Weston who had been with the company for eighteen months and with Marcus for approximately fourteen of them, which placed the beginning of their relationship at a time that overlapped significantly with the final phase of our marriage — a timeline that Sandra had documented carefully, with the specific attention to dating that matters in Washington State dissolution proceedings involving marital waste.

I read David’s text. I poured myself a glass of the Willamette Valley Pinot Noir I had opened for dinner. I sat on my Laurelhurst front porch in the October evening and thought about sixty people on a Charter Hotel rooftop toasting Marcus Weston’s freedom, and I felt — with some surprise, because I had expected something more jagged — almost entirely at peace.

Because I knew what Marcus did not yet know.

And what he did not yet know was going to arrive in a boardroom on Monday morning with the specific, irrevocable force of a thing that has been building for eight months and is no longer avoidable.

PART TWO: The Eight Months

I want to explain the eight months, because the Monday morning boardroom moment was not an accident and not a coincidence. It was the outcome of eight months of very specific, very deliberate work, and the work had a shape that I will try to describe as clearly as I can.

When Marcus and I separated in April of the previous year, I left the COO role at Aldridge-Weston on a Friday afternoon with the professional courtesy of two weeks’ notice, a comprehensive transition document I had spent three weeks preparing, and the specific, clear-eyed understanding of a corporate attorney who knows what her departure means for an organization and has documented accordingly.

I left behind the vendor contracts I had negotiated, the operational systems I had designed, the HR frameworks I had implemented, the client relationship management protocols that were responsible for a client retention rate of ninety-four percent over three consecutive years. I left behind eight years of institutional knowledge that was, as I had always known and as I had been careful never to let Marcus forget, not in the org chart but in my head.

What I took with me was my laptop — my personal laptop, which contained no company files — and a legal pad of handwritten notes that I had been making for approximately six weeks before the separation, which documented the specific operational dependencies that would become relevant when I was no longer there to manage them.

I also took something less tangible: the professional relationships I had built, in eight years of running a company’s operations, with the clients, vendors, and partners who knew me specifically and personally, who had my cell phone number and my personal email, and who associated the quality of their relationship with Aldridge-Weston with me rather than with Marcus, because I was the person they called when something needed to be solved and Marcus was the person they saw at the annual sales conference.

Sandra Lim’s advice, given in our second consultation, was simple: “Do not sabotage, do not interfere, do not touch anything that belongs to the company. Build your own life. Let the operational gaps speak for themselves.”

I had followed that advice with the specific, disciplined precision of someone who had spent eight years running a company and understood what operational gaps looked like and how long they took to become crises.

What I had additionally done, which Sandra knew about and had advised on, was this: in June — two months into the separation — I had formed a new entity, Aldridge Technology Consulting LLC, registered with the Washington Secretary of State, with a business address at a shared office space in South Lake Union.

The business had a simple website, a LinkedIn company page, and a service offering that was, in Sandra’s careful framing, “an entirely legitimate consulting practice offering the same operational expertise you have spent fifteen years developing as an independent professional.” I had three clients by August. I had seven by October. Three of the seven were former Aldridge-Weston clients who had reached out to me directly, on their own initiative, after the quality of their service experience at Aldridge-Weston had declined in ways they found worth calling about.

I had not solicited any of them. I want to be absolutely precise about this, because it is both legally and ethically important. I had not called any former Aldridge-Weston client. I had not emailed. I had not suggested, directly or indirectly, that they consider moving their business. My non-solicitation obligations under the separation agreement were specific, and I had observed them with the rigor of someone who understands the consequences of not doing so. What I could not control — and what Sandra had advised me I was not responsible for — was the quality of service that Aldridge-Weston delivered after I left, or the decisions that clients made in response to that quality.

The operational gaps had spoken for themselves.

By October — the Friday of the Freedom Party — Aldridge Technology Consulting had seven clients generating approximately $2.1 million in annual contract value, and three of those clients had recently informed Aldridge-Weston that they would not be renewing their contracts at the end of the current term. I knew this because two of those clients had told me directly, and one had mentioned it in the context of explaining why they were expanding their engagement with my new firm.

David Park’s text arrived at eight-seventeen. The Freedom Party was in progress at the Charter Hotel rooftop.

The board meeting was scheduled for Monday morning at nine a.m.

I went to bed at ten-thirty and slept very well.

PART THREE: Monday Morning

The Aldridge-Weston Technology Partners boardroom was on the fourteenth floor of a building in South Lake Union, with floor-to-ceiling windows facing Lake Union and, on a clear day, a view that extended to the Olympic Mountains in the west. I know this room well. I had sat in it for eight years of quarterly board meetings, annual reviews, and the specific, recurring negotiations of a company’s governance that become, over time, as familiar as furniture.

I was not in that room on Monday morning. I want to be clear about this, because what happened there is something I know from two sources — David Park, who was present, and the board chair, Eleanor Finch, who called me at eleven-forty-seven that morning and whose account I consider authoritative.

What happened was this:

Marcus walked into the boardroom at nine-oh-five — five minutes late, which David noted was consistent with the pattern of the previous six months, before which Marcus had been punctual for the same board meetings for nine years, and the shift in the pattern was something David considered informative. He had the specific, relaxed quality of a man who had spent the previous evening being celebrated and had not yet recalibrated to the demands of a Monday morning board meeting that he was not fully prepared for.

Eleanor Finch, who had been on the Aldridge-Weston board for six years and who I had known professionally for most of that time, called the meeting to order. She presented three items. The first was the quarterly financial review. The second was the client retention report. The third was a letter that the board had received the previous week from the company’s two largest clients — who together represented thirty-one percent of annual recurring revenue — notifying Aldridge-Weston of their intent not to renew their contracts when they expired in February.

The letter had been sent to the board directly, not to Marcus, which was itself a communication.

Marcus looked at the client notification letter with the specific expression of a man encountering information that his internal model of the situation had not predicted. He said the client relationships were being managed. He said the departures were part of a normal churn cycle. He said the Q4 pipeline would more than compensate. He said several other things that Eleanor listened to with the composed attention of a board chair who has already formed a view and is giving the CEO the professional courtesy of being heard before that view is communicated.

Then Eleanor said: “Marcus, the board has been observing the operational quality metrics since Katherine’s departure in April, and we are concerned about the trend. We’d like to discuss the COO position and the timeline for a permanent replacement, which has now been vacant for six months.”

Marcus had been operating with an interim COO — a senior director named Paul who had been doing the role in addition to his own responsibilities and who was, as Paul himself had told David in August, not the right person for the position and knew it. The interim arrangement had been Marcus’s choice, based on a belief that he could run operations himself with Paul’s support, which was a belief that the previous six months of client feedback and operational metrics had not confirmed.

The board discussion that followed lasted ninety minutes. David described it to me as “the most specific and uncomfortable conversation I have seen in six years of sitting in that room.” Eleanor asked questions that had answers in the financial data and the client retention numbers, and Marcus’s answers were the answers of a man who had been operating on the assumption that his vision and his relationships were the company’s primary assets, when the data in front of the board indicated that the operational infrastructure — the thing I had built — had been the primary asset, and its absence was now measurable.

At the end of the ninety minutes, the board did not fire Marcus. That is not what boards do in first conversations of this kind, and it would not have been appropriate. What the board did was issue a formal performance improvement framework — a sixty-day operational recovery plan with specific, measurable milestones, supported by a board-appointed operational advisor who would report directly to Eleanor rather than to Marcus. The advisor’s name, which Eleanor presented with the specific clarity of someone who had made this decision carefully, was me.

I had not sought the appointment. Eleanor had called me in September — two weeks before the divorce was finalized — and asked whether I would be available for a consulting engagement with the board on an advisory basis. I had discussed it with Sandra. Sandra had advised that a board-level engagement, properly structured, was distinct from any non-solicitation obligations related to former clients or employees, and that I was free to accept board advisory work from the company’s independent directors. I had accepted.

Marcus was informed of my appointment at nine-oh-five on a Monday morning, while he was still processing the client departure letters, while the Freedom Party champagne presumably still had some echo in his system, while Brittany Nakamura — who, David reported with the specific economy of someone choosing not to editorialize — had not been seen in the office that morning or, as it emerged, for several days thereafter.

PART FOUR: The Week That Followed

I want to be fair about what the board appointment was and was not. It was not revenge. I want to say that clearly and without the qualification that would make it sound like I am protesting too much. I had spent eighteen months building Aldridge Technology Consulting because I had a specific, valuable professional skill set and I intended to use it, and the board engagement was a natural extension of that. Eleanor Finch had called me because I was the most qualified person she knew for the work she needed done, and the fact that the work happened to be at a company whose CEO had thrown a Freedom Party forty-eight hours earlier was a coincidence of timing that I had not engineered.

What I did bring to the engagement was the specific, comprehensive knowledge of Aldridge-Weston’s operational infrastructure that eight years of building it had produced — knowledge that was, as the first two weeks of the advisory engagement demonstrated, both more extensive and more irreplaceable than the previous six months had made apparent to anyone who had not been paying the kind of attention Eleanor had been paying.

Marcus and I had two professional interactions in the first week of the engagement, both in formal settings with other people present. They were civil, brief, and conducted with the specific, mutual courtesy of two people who have agreed, implicitly and completely, that the work is the only thing that matters in the room. I do not know what Marcus felt in those interactions. I can tell you what I felt: the particular, unencumbered clarity of someone who is doing a job she is good at, in a room she knows well, with nothing to prove to anyone.

Brittany Nakamura had, as David had indicated, disappeared with a speed that the office had noted and was discussing with the specific, focused interest that offices bring to the personal situations of senior leadership. She had submitted a resignation letter by email on the Sunday after the Freedom Party — forty hours after the party ended — citing “a personal decision to pursue other opportunities,” which is the language that people use when they have assessed a situation and determined that the upside has been substantially revised downward. Her LinkedIn was updated by Tuesday to show her as “open to opportunities.”

I heard about all of this through David, who provided updates with the professional discretion of a CFO who has concluded that his loyalty in this situation runs in a specific direction and has acted accordingly. I did not ask for the updates. I did not encourage the dynamic. But I listened, because information is information, and because understanding the operational context of an engagement is part of doing the engagement well.

The sixty-day performance improvement framework produced, in its first thirty days, the following: a full operational audit of the six months since my departure, which identified seventeen specific process breakdowns that had contributed to the client dissatisfaction behind the contract non-renewals. A revised COO job description that Eleanor and I developed together, posted to the executive search firm she retained in week two. A client retention outreach program that I designed and that Marcus’s team implemented, which produced three of the seven departing clients agreeing to extend their contracts pending the operational improvements the board had committed to.

The fourth client — one of the two who had sent the board letter — had already signed a contract with Aldridge Technology Consulting. That was a separate matter, properly disclosed to the board, and properly handled.

The board was satisfied with the progress. Eleanor was satisfied. Marcus was navigating a situation that required him to acknowledge, in the specific, daily, professional way that boardroom realities require acknowledgment, that the infrastructure he had been celebrating his freedom from was the infrastructure that had been holding the company together, and that its absence had cost him thirty-one percent of annual recurring revenue and a sixty-day performance review.

PART FIVE: The Laurelhurst House in January

The sixty-day engagement extended to ninety days, by mutual agreement and at Eleanor’s request, and I completed it in January. The permanent COO — a woman named Diane Torres from a Denver-based software company who had been found by the executive search firm in November — started her role in February and I handed off my documentation to her with the comprehensive, organized completeness of someone who has done this before and understands what a good handoff looks like.

My last formal interaction with Marcus in a professional capacity was a board presentation in January, in which I summarized the operational recommendations of the engagement and the status of each initiative. Marcus sat across the table and listened with the professional attention of a CEO who has internalized, over the previous three months, that the board is watching him watch the person across the table, and that how he manages this moment is part of what the board is evaluating.

He was professional. He asked two good questions. He thanked me at the end with the specific, calibrated courtesy of someone who has decided that courtesy is the only viable option and is executing it correctly. I thanked the board. I packed my materials. I rode the elevator down from the fourteenth floor of the South Lake Union building for the last time, walked out onto the street where the January Seattle rain was doing what January Seattle rain does, and got in my car.

I drove to Laurelhurst. I made tea. I sat in the living room I had painted in August, on the couch that I had chosen because I liked it rather than because it matched anything else, and I looked out the window at the street that was now mine — the dahlias long dormant, the Japanese maple in the front garden having done its autumn thing and now bare and clean against the January sky.

Aldridge Technology Consulting ended its first full fiscal year with eleven clients and $3.4 million in annual contract value. I had three employees — a senior operations consultant, a client services manager, and an office manager — who worked out of the South Lake Union shared office and whom I paid at rates I considered appropriate because I remember what it felt like to be compensated below market for indispensable work. The business was profitable in its first year, which is not the norm for consulting practices, and which I attribute to the specific advantage of having spent eight years building relationships in an industry I know very well.

Marcus. I think about him occasionally, with the specific neutrality of someone who has moved entirely into a different chapter. The company has stabilized under Diane Torres, who by all accounts is doing the role well and who I hear positive things about from Eleanor, who calls occasionally with the professional warmth of a board chair who considers me a valued contact. The Freedom Party was the last time Marcus and I occupied the same social world. I attended a client dinner in November where he was also a guest — a small technology industry event in the Eastlake neighborhood — and we said hello with the specific, mutual calibration of two people who have navigated something significant and arrived at the functional courtesy that comes after.

Brittany Nakamura started a new role at a tech company in Bellevue in December. I know this from LinkedIn, which I checked once and then closed with the specific finality of someone confirming a fact they did not particularly need. That is all I know about her situation and all I need to know.

The Freedom Party. People ask me about it — how it felt to know it was happening, whether I was angry, whether the Monday morning boardroom moment felt like justice. I have thought about these questions with the honest attention they deserve, and my honest answer is that the Freedom Party was a man celebrating the end of a marriage he had already effectively ended fourteen months earlier, in front of people who were applauding because applauding the boss is easier than telling him the truth. The party was not about me. The Monday morning meeting was not about me either. They were both about the specific, convergent consequences of a set of decisions that Marcus had been making for fourteen months, and they arrived in the sequence they arrived in because consequences have their own timing.

What I had done was build something. I had built it quietly, with the documentation and the attorney consultations and the client relationships and the operational expertise that I carried out of that South Lake Union building in April — not as a weapon, not as a plan, but as the only thing I knew how to do when the life I had built inside someone else’s company was over: build my own.

The dahlias will come back in the spring. They always do.

I planted them knowing that.

Leave a Reply

Your email address will not be published. Required fields are marked *