Chapter 1 — The Opportunity Meeting

At 10:14 the night before, Rob was standing in the kitchen in socks, trying to decide whether the better use of the next hour was for sleep or for another podcast he would have half-listened to while worrying about work.

The worrying had a specific object that night. He had a dashboard open on the laptop on the counter, the one that collapsed the whole company's cloud spend into a single line

, and the line was doing what it did every quarter, which was climb. Up thirty percent year over year against a business that was up nine. A run rate that had started to read like a phone number. Down underneath it, where nobody upstairs was looking, sat the Mercato and Atlas overlap he had been modeling quietly for six months. Two platforms that did the same thing. Two platforms the company was paying for twice over, costing an arm and a leg, while nobody at the company was willing to have the conversation about why they had both. That conversation was Rob's job. He was the one who was supposed to walk into a room full of people who already knew and make them pretend they didn't, using a cost sheet they would later claim they hadn't seen. He was not going to fix any of it before bed. He watched the line anyway. It was blood red and it moved up and to the right, and he couldn't look away from it.

He was scanning his podcast subscriptions, another episode about the day's latest disaster or a panel of people agreeing that things were bad and getting worse, when his phone lit up with a new calendar invite for tomorrow.

Subject: Crunch Time for Cloud — please attend in person.

Sender: Jack Aboud.

Recipients: 11 vice presidents, one chief counsel, and Rob, the director-level surprise guest whose name appeared in the bcc field, a field only Rob could see, which was how he knew he was that person.

Rob stared at the invite. It had no agenda, no pre-read, and a conference room in the Network Operations Center, which was where executives booked meetings when they wanted charts behind them that looked serious. He had already started constructing the version of the next day that ended with him on Zoom, camera on, wearing a shirt and tie selected entirely to look serious. He was bcc'd, which usually meant Jack did not expect him to rush to the airport. Surprise guests were normally there for thirty minutes, long enough to say the prepared thing, then asked to leave before the meeting became interesting.

He had run this morning before. Two or three times a year, for the better part of a decade, Jack or Jack's predecessor or his predecessor before that would wheel him in to run the same forty minutes on a different cloud bill — flown in, walked through, thanked, sent home. He had a private name for the cycle.

Groundhog Day. The shirt and the tie were the same shirt and tie he had bought for the first one. Someone two levels below everyone else in the room showed up to politely hold executives accountable because Jack couldn't do it himself.

And Rob had some meaningful content at the ready: a duplication overlap between Mercato and Atlas he had been running quietly for six months, a vendor-consolidation analysis Finance had requested and then treated like a rumor. Rob was ready to have a real conversation about cloud cost, but his assumption was that tomorrow's meeting wasn't that. He would be dialed into another fire drill. He was the first responder. The guy who got the call, showed up at a room full of people several levels above him, and held up the scary graph. That was the job, and that was exactly what Jack was using him for.

Then the second email arrived.

Rob — Jack needs you onsite for this one. Travel can book first available out of YVR, which is 5 AM, sorry. Given the situation we're in, he'd like for you to be in person. Thanks, Marisol.

Rob read the sentence three times. Not the meeting. Not the discussion. The situation. Suspicious.

At 5:04 the next morning he was at Vancouver International with a roll-aboard and a coffee that tasted like plastic, and by lunch he was at the San Jose office badging into a building he had not seen in eight months. At 12:48 in the afternoon Pacific time he was standing in the corridor outside the Network Operations Center, looking at his reflection in the glass and trying to look like someone Jack would summon to send a message on cloud spend.

Rahul met him at the elevator. Rahul looked, as he always looked, like he had already decided how the meeting was going to go and was letting everyone else figure it out at their own pace.

"You ate?"

"On the plane."

"That's not eating."

"I had a wrap."

"That's not eating either."

Rob laughed once and stopped, because his stomach had been a fist since the descent into San Jose had been bumpier than usual. He had spent the last two hours running through the deck on his phone, opening it and closing it. He had not opened the speaker notes. He had not opened the appendix. He had not read any of the comments from anyone who had reviewed the document.

"NOC?" Rob said.

"NOC. Jack wants the screens. He wants the live customer traffic numbers behind us, in case anybody wants to argue about whether the business is growing. And Ambica's joining for the first ten minutes. There's a legal agenda item."

"Ambica's in a budget meeting?"

Rahul held his badge against the reader without pressing it through. The reader's green light blinked.

"Do you know about the deal?" Rahul said.

"What deal."

"The deal... no one has read you... never mind, I'll talk to Jack."

Rob looked at him. Rahul was a VP who still thought of himself as a senior engineer, which was the half of his job he actually liked. But the other half, the half that mattered in moments like this, was that Rahul was connected. Not connected like everyone at that level was connected, not in the LinkedIn, golf-outing, strategic-partnership sense. Rahul knew things before the people who weren't supposed to tell him knew them. He knew which executive assistants were moving meetings before the meetings had names. He knew what the backchannel was saying before the official channel admitted there was anything to discuss. Rahul was so connected it was almost a problem. If Rahul was raising the topic at all, people were already talking about it.

"Rahul," Rob said, "I have spent the last six hours telling myself that all I have to do today is talk for thirty-eight minutes about empty databases and route replay systems. Please do not put a deal in my head right before I have to walk in there."

Rahul pressed his badge through. The reader clicked open.

"Forget I said anything," he said. "I have to tell Jack not to mention the situation in front of you."

"Lovely."

"Jack's right hand," Rahul said.

"What?"

"The empty seat on his right is for you."

The NOC was not the bunker people imagined, but it had made an effort. Rows of desks stepped down toward the screen wall in the familiar mission-control arrangement, as if someone had once seen NASA footage and decided customer support needed more launch-abort energy. The desks held monitors, backpacks, protein bars, badge lanyards, and the exhausted people who kept the official story green.

The wall itself was a mosaic of dashboards Rob had argued about on and off for the better part of a decade. The company moved vaccines and critical medical supplies. That was the business. Not software, not ads, not engagement metrics — medicine. Insulin, chemo, vaccines. Freight where a late truck or a warm fridge doesn't show up as a dip in a quarterly report. It shows up at a pharmacy that ran out. It shows up at a hospital that had to improvise. It shows up as a patient who didn't get their medication on time, and sometimes that patient dies. That was what was on the wall. But the NOC made it look like a systems health check. Green ribbons, exception queues, batch trace coverage. The language of machinery. Work around it long enough and you stopped seeing the people. The metrics replaced them. The green ribbon at the bottom said regional continuity normal, which was the NOC's way of saying nobody died today because something went cold or went missing or went to the wrong depot. It always felt like an emergency in that room even when the ribbon stayed green.

Behind glass at the far end sat the official conference room, a long table under a secondary wall of screens. Most NOCs looked like the set of 24 or the third act of a spy thriller, and this room had embraced the genre. It wanted to be a James Bond movie.

There were two seats left when he came in: one at Jack's right hand and one at the head of the table. The right-hand seat would tell the room that Rob had been brought in to swing a hammer. That was usually why Rob got invited to Jack's executive meetings anyway, the times Jack wanted to wheel out cloud cost to motivate the room. Rob took the seat at Jack's right hand and heard, exactly as he had known he would, a voice from halfway down the table say look at Rob, special FinOps prosecutor, and another voice say is court in session yet. Ambica from Legal neither laughed nor looked up. Rob had heard every version of that joke for years. FinOps prosecutor. Cost cop. The cloud sheriff. It was getting old. It was an odd ritual: he would show up, press the panic button, and right before the meeting started everybody always wanted to joke. But what he had to say wasn't funny. The company was wasting a serious amount of money. Decisions needed to be made today, and those decisions were going to affect the teams in this room. The jokes were a defense mechanism. The people making them knew they were about to be called out, and the easiest way to pretend that wasn't happening was to make Rob the punchline before he'd opened his mouth. People were friendly to Rob. None of them were particularly happy he was at this meeting.

Before he opened the lid, Rob ran the silent inventory everyone ran before plugging a laptop into a room full of executives. Tabs. Windows. Slack previews. Anything currently on his screen that he should not, under any reading, be sharing with every executive at once. He closed two windows he was reasonably sure were fine, because reasonably sure was not the standard for this room.

Rob set the laptop down carefully so that the lid did not snap, opened it, plugged in the HDMI dongle that did not work in this room, swapped it for the dongle that did, watched the secondary display flicker on, and pulled up his deck. The title slide read FY26 Health Logistics Cloud Cost Review — Optimization Opportunities by Org. Jack's chief of staff had retitled the file at some point in the previous twenty-four hours; the original file Rob had submitted on Monday was called Cloud Cost Status, FY26 Month One.

He had noticed. He had not said anything.

Jack came in last. He took the head of the table, looked at his phone for ten seconds, and muttered, to the screen or the person currently ruining his day from a safer location, "Well, that has to wait until after I get through this." Rob had seen this exact performance a dozen times. Jack always walked into a meeting muttering about something. Someone needed his time, something couldn't wait, he was too busy for this. It was part of the act. Jack wanted everyone in the room to understand that he was a man in constant demand, and that anyone who had the privilege of being in a meeting with him was lucky to be there. Rob had stopped buying it years ago.

Marisol Reyes, Jack's chief of staff, had slipped in behind Jack and taken the seat by the door. She had a laptop open on her lap and a small spiral notebook on top of the laptop, and the notebook was open to a page on which Rob could see, even from across the room, the words exec summary — Claude

. Her laptop screen showed a slide deck that was not Rob's slide deck. It was a summary, a paraphrase, something that had been built on top of his work by someone who had not asked him about it. He looked at the words once and did not look again.

Jack set his phone face down with the care of a man creating evidence he would later deny having seen. Executives had a gift for looking overwhelmed without looking out of control; they made preoccupation seem like a credential.

Jack started the meeting. "All right. Ambica's got one item, then we get into it. Ambica."

Ambica did not stand. She did not flip open a folder. She looked at Jack, then at Rob, then back at Jack. The glance at Rob was not casual. She was uncomfortable, and she was trying to say something without saying it. She shifted in her seat, tapped her pen once against the notebook, and said, "Counsel will be sending an email this afternoon with some communications guidance. All discussions related to cloud spend are highly sensitive right now. Highly sensitive. I want you all to read the email." She paused. "I want you all to read it before you forward anything from this meeting."

"Anything specific you can share now?" said David.

"I will send the email," Ambica said. Her eyes moved to Rob again, just for a second, and then away. She couldn't say what she needed to say with him in the room.

David looked at Jack, annoyed. "Is this about the —"

"Read the email, David," Jack said.

"Jack," Ambica said, in a voice that was both very polite and entirely not friendly, "we have a guest in the room." She gathered her things and left.

Rob did not look up from his laptop, but his stomach tightened. Rahul at the elevator: do you know about the deal? No one has read you in. Ambica glancing at him, then away. Jack cutting David off before David could finish the sentence. Everyone senior to him was working from information he did not have, and whatever it was, it had something to do with his work. With cloud cost. With him.

That was almost never good news.

"All right," Jack said. "We're up thirty percent year over year on cloud. The business is up nine. Run rate is four hundred and eighty million on cloud alone, and we are projecting a fifty-five percent increase next year if nobody in this room does anything different. I have explained this to people upstairs and they have explained back to me, in some detail, that the math doesn't work. So we're going to do something different today."

He turned to Rob. "Rob's flown in. Let's let him drive. We're going to hand the mic to Rob and he's going to tell us what to do next."

Rob looked up at the wall screen, properly, for the first time.

Oh, crap. That was not his deck. Someone had run his deck through an AI and put the output on the wall. The first bullet said cloud run rate was down thirty percent year over year. Jack had just told the room it was up thirty. And there it was, in yellow, on a screen the size of a wall, in front of eleven vice presidents. Marisol's notebook. "Exec summary — Claude." Jack had told her to improve the deck. She'd run it through Claude, and Claude had hallucinated.

Of course. Of course this happened.

Rob turned to Marisol. Gently. The annoyance wasn't hers to carry.

"Can we switch to my slide deck? The one I sent on Monday."

Marisol looked up. Then at the wall. She did three things on her laptop. The yellow summary disappeared. His title slide came up.

"Thank you," Rob said.

He looked over at Jack. Jack's face didn't move. Of course it didn't. Jack had decided the mistake was cheaper if nobody mentioned it. Rob caught his eye for half a second, long enough to say we'll talk about this later, and moved on. He had a job to do.

He turned back to the room.

"Okay. Forget what was on that slide. Pay attention to what Jack just told you. We are up thirty percent. We don't have time for the nice stuff. I want to skip straight to the problems, because if we're going to get our spend under control, we need to start by agreeing on what the problems are. Slide six."

That was the moment in which Rob understood, properly, what he had been brought in to do.

He had thought, on the plane, that he was here for the standard ritual: walk through the deck, name the worst offenders politely, watch Jack pretend to be furious at things he had already approved, fly home. That was how these meetings usually worked. Once or twice in the middle of the year, leadership invited FinOps in to run through a well-worn script meant to convince a few executives to look up from their roadmaps. Everyone performed concern. Jack asked tough questions in a tone calibrated for the notes. Someone promised an action plan by Friday. Someone else blamed tagging, the same complaint Rob had been hearing for nine years.

Tagging was the small, boring, ungovernable labor of attaching ownership labels to every line of cloud spend, so that Rob's team could tell which team owned what. Without it the cloud bill came in as one long undifferentiated number, and FinOps could complain about the total but could not point at anyone in particular. Most teams tagged badly because tagging was tedious. A few teams tagged badly on purpose, because being unreadable was, in certain ways, a kind of safe anonymity. We don't have the tags right; can you come back next quarter was the oldest deflection in the book. For the most part, Rob was there to remind people who weren't paying attention to pay closer attention, and Jack was there to pretend that there were serious consequences.

Usually, the stakes were partly theatrical. The waste was real, but the ritual around it gave everyone a place to stand while pretending they had not helped build the problem.

This was different.

Rob could feel it the moment he stood up. Usually people only paid half attention. Someone was always checking a phone, someone was always half-watching the screen while thinking about something else. Today nobody reached for a phone. Nobody whispered to the person next to them. The room was quiet, and every chair was angled toward Rob, and that alone told him more than anything Jack had said. Something specific had happened between last quarter and this morning, and the spend problem was no longer theater. It was an actual limit. A budget that couldn't be revised. Jack needed the room to understand that this couldn't be nodded at, assigned a Friday action plan, and quietly survived.

Rob didn't start with the Worst Offenders slide. He started with what mattered.

"Listen. I can explain why we're up thirty percent," he said. "The business is up nine. Cloud is up thirty. The gap isn't waste. It's not tagging. It's not orphaned databases." He clicked to slide four. Two names, side by side, with their run rates highlighted. "It's these two. Atlas and Mercato. Two platforms that do the same thing. One of them was supposed to retire the other. That was the plan three years ago. Three years, and it never happened. Instead we're running both, and the combined cost has quadrupled what it should take to run this business."

The room was still. Rob glanced at Jack. Something shifted in Jack's face, something closer to discomfort. Jack looked like he was about to say something, started to form the words, then stopped. Well, but that's — and then nothing. He caught himself. Whatever he was about to say, he couldn't say it in front of Rob. Not yet. Rob didn't know why, but he could see it plainly: Jack had hit a wall in his own sentence. It was the same look Ambica had. Jack had it now too. Rob had just put his finger on the biggest cost in the business, the thing that was actually driving the spend up, and somehow that was the thing nobody was supposed to talk about.

David broke the silence. "Well, that's going to be a problem for everyone."

He said it without inflection, but Rob caught the look David exchanged with Nancy. It was a look about something bigger than a slide deck.

Rob didn't press it. Not yet. He'd put his finger on the wound — two platforms, same function, quadrupled cost — and the room had reacted like he'd pulled a thread that was attached to something none of them wanted to look at. He didn't know what was on the other end of that thread. He didn't know that the Atlas and Mercato overlap, the thing he'd been modeling quietly for six months, was one of the reasons the company was about to be acquired.

David did not wait.

"That's not even an accurate read," David said. "Those are development environments for the Helios refresh. That refresh is on the roadmap I gave you, Jack. We talked about it in October."

"I remember October," Jack said. "That was a good conversation. October was exciting, but it was also six months ago. We're at the end of April, and you've spent how many millions on development environments that have not developed into anything."

"So what are you saying, Jack?" David said. "That the Helios team should stop developing software?"

"No," Jack said. "Maybe you're missing the point. We don't have two million dollars a month to make your team feel good about having a development database. You don't have to explain it now. I want an answer from you and Rob tomorrow."

David sat back. He did not look at Rob. "Of course," he said, not quite under his breath, to no one who was supposed to answer. Looking at Rob would have been a concession. He looked at the dashboard wall instead, the green ribbon at the bottom, the customer edge graph, and Rob watched David start to search for excuses. Everyone knew David was going to interrupt and derail the meeting in five minutes, and Rob was surprised no one bothered to set a timer.

"Nancy," Jack said. He almost smiled when he said it, a small, tired smirk that told Rob Jack was closer to finished with David than anyone in the room was supposed to know. Whatever fight Jack and David were having, it had started before this meeting.

"While David's thinking about his next excuse."

Nancy did not need an invitation. "I am over budget by four percent. That's it. Four. And I am being held over a barrel for four percent while we are about to be told we need forty new people on the AI logistics side — allocation simulations, outbreak modeling, automated regional prioritization — that I have zero plan to fund."

Rob had been sitting quietly for long enough. He was tired. He was three levels below every VP in this room, and he was tired of the routine where he showed up, said the scary thing, and then sat back while everyone negotiated around it like it was someone else's problem. He was tired of the yes-sir, thank-you-sir of it. He clicked to a slide he hadn't planned on showing.

"Okay, great," he said. "That was wonderful. I have learned there are a lot of things we can't talk about in this room. One of them is the Atlas and Mercato overlap. One of them is why David needs development databases that haven't developed anything. So let's talk about AI."

The slide came up on the wall. The title read, in large type: We're Drunk on AI.

Nancy made an audible sound, not quite a gasp, more like the intake of breath from someone who had just been told a joke at her expense in front of people she was trying to impress. "Oh, come on."

"Listen," Rob said. "I know AI is the most important thing in the world. I know it's the future. I know we need it. But you are all suspending two hundred percent over what anyone told me you were going to spend on AI. Two hundred percent. And that problem is not getting better. It's getting much, much worse. Every quarter I come in here and show you the numbers, and every quarter the numbers are worse, and every quarter we have the same conversation about why." He knew he was pushing it. He could feel Jack's chair creak. "Something has to be done about it. Maybe this is the meeting where we finally do some management on this topic."

He regretted it the moment he said it. "Management" was a word that implied the people in the room hadn't been managing. Eleven vice presidents and a CTO, and a director-level FinOps guy from Vancouver had just told them they weren't doing their jobs. He could feel the room recalibrate around him — the slight shift in posture, the exchange of glances. He'd crossed a line, and he wasn't sure he could uncross it.

But he was also tired of pretending the numbers weren't real.

There it was. Nancy's org. Mercato: The Future of Always-On Sales, according to an internal launch page that had survived three reorgs and one brand review. One point four million a month in cloud. About a million a year of that flagged red. Rob hated the red. He'd tried to soften it once — asked his designer to find something less aggressive, something that didn't look like a crime scene. She found a nice amber. Jack killed it. "Bring back the bloodbath

," he said. "These meetings are supposed to make people uncomfortable."

"Mercato is at one point four million per month," Rob said. "What we've flagged is roughly a million a year on instance classes that haven't seen a customer request in the trailing ninety days. Not saying they're dead. Saying they don't appear to be in the request path."

"Define request path," Nancy said.

"I'm ready for your cross-examination," Rob said. "Any inbound, internal or external. We pull from your own observability stack. Your team set the thresholds."

"That can't be right."

"Your senior staff signed off on the methodology last quarter, Nancy. Sarah and Devesh. I have the email."

"And of course you do."

There was a small, awful pause in which Rob felt the room understand that he had just trapped Nancy with the same instrument Jack was about to use on her.

He did not enjoy doing this. But this was his job in the meeting: to remind people that there was a process, and the process produced evidence. He was ready to remind people that they had not responded to emails, paid attention, or, in Nancy's case, even bothered to attend the meetings back in April.

"If you had attended the initial meetings in April, you would have —"

"Nancy," Jack said, "if you need forty people for AI logistics, and you've got a million a year in run rate on Mercato priority services that have not served a live allocation window in ninety days, I'd like to think one of those numbers funds part of the other."

It was not helping that Jack was starting to enjoy this.

"Jack —"

"That's what I'd like to think."

David came back in. He had finished selecting. "I want to know who's auditing Rob."

"Excuse me?" Jack said.

"He's a director. He's auditing senior vice presidents in a staff meeting. Who's auditing him."

"David, don't be ridiculous," Jack said.

"No. I'm asking the question. Rob, who in Finance has signed off on this methodology? Because the last time we did this I had three months of cleanup on Helios — three months — because of one of his slides."

Rob recognized the accusation before David finished it. He had heard it before, in other people's voices. Three years ago, almost exactly. A Savings Opportunity deck. A team everyone liked working with. A failover nobody cared about until it failed. Rob's signature on the slide.

He kept his face still.

"Finance signed the methodology in November," Rob said. "We revised it again in January after your team raised the developer environment concern. I have your feedback from then, and I'm happy to resend it."

David kept his eyes on Jack and gave Rob only a side glance. "You don't have to resend."

"I'd be happy to send."

Jack cut in. "Rob. Let's keep going."

Rob did not, in the end, keep going through slides seven through nineteen the way the deck had been built. He took the room through five slides. Two more people tried to buy themselves room with phrases that had survived other budget meetings: roadmap dependency, shared platform obligation, approved exception pending review. A third started to turn the conversation toward next year's funding gap, saw Jack's face, and discovered a sudden respect for the agenda. The room was not short on arguments. Most of the people in it were smart enough to know this was not the meeting to start a fight or ask for budget.

Rob named numbers. He named orgs. He did not name people. When he reached the end of the formal deck he closed the laptop a quarter of an inch.

He looked at Rahul.

Rahul looked back at him, resigned, very faintly amused. He knew exactly what Rob was about to do and would have preferred Rob did not.

"I want to say one more thing," Rob said.

"By all means," Jack said.

"There is one VP in this room whose org is not on the slide. Rahul, you don't have to do anything with this. The reason you're not on the list is not that your footprint is small. It's that your team owns it."

There was a silence Rob had not expected.

He had expected a laugh, maybe, or at least the small procedural nod people gave when they wanted a meeting to move past them. There was neither. The FinOps prosecutor jokes from before the meeting started were gone. Nobody was smirking. The room looked pretty somber.

Rahul, the man Rob had thanked, did not look pleased. Rahul looked at his hands.

Jack let the silence go for a beat too long, and then said, quietly, "Team, talk to Rob. I usually end these meetings telling you we'll find a way through a budget crisis. This time is different. If Rob has shown you something today, I expect answers by tomorrow."

David said, "My team has a process for —"

Jack cut him off without raising his voice. "Tomorrow."

David's typing started up again, audible across the table.

"David," Jack said, "I can read your inbox in your glasses. Pay attention."

There was a small, scattered laugh from the back of the room. Rob did not laugh. Nancy did not laugh.

Jack looked across the table at Rob.

"Thanks again for all the great work, Rob."

"Sure."

It was Jack's favorite move: the polite thank-you that meant you were finished and should leave. Rob understood the cue. He picked the laptop up, unplugged the dongle, wrapped the cord, made eye contact with Rahul for exactly long enough to read that Rahul was not angry at him, just tired in a particular Rahul way, and walked to the door.

Ambica was in the hallway.

She had not gone back to her office. She was standing by the window at the far end of the corridor with her phone to her ear, back to him, voice low. He could not hear her words. He could hear that the voice on the other end of the call had been talking for some time, and that Ambica was responding in clipped, lawyerly affirmatives. Yes. Yes. I understand. We will. Yes. Her notebook was tucked under her arm. The notebook was open. The page he could see from the door was blank.

He did not interrupt her. He let the NOC door close behind him.

As it closed he heard, over his shoulder, Ambica from inside the room — she must have walked back in through a side door without his noticing — saying something in the cadence she used with Jack and only with Jack, the cadence in which one professional lets a client know, without raising her voice, that a legal situation is developing.

Rob caught two sentences.

"…after the acquisition closes, the buyer's first priority is going to be cloud efficiency

. So I want to be very careful about what gets put on a board slide between now and the vote."

Rob stopped walking.

He stood in the hallway, his hand on the strap of his bag, the laptop's lid still slightly warm against his side. Then the obvious thing finally dawned on him.

The first thing was that there was an acquisition.

The second thing was that Jack had needed him to say the numbers out loud in front of witnesses.

Now Jack had the deck. He had a room full of people who had heard Rob walk through it. He had red boxes, dollar amounts, and a list of teams that could be discussed with a buyer in language that sounded careful enough for Legal.

Rob would not be in that room. He would not be there when low-utility became waste, or when a slide about unused systems turned into a question about whose team still needed to exist.

He had said, three years ago, never again. Never again would a

savings deck of his become the polite first draft of a layoff. It was not fair to frame savings as waste, and yet the slide always traveled faster than the distinction.

He looked at the door. The door was closed.

He walked to the elevator.

In the elevator the laptop chimed in his bag, then chimed again before the floor number changed. Evidence that the meeting had already escaped the room despite Ambica's direction. David, Nancy, maybe Jack himself were forwarding, warning, softening, asking for defensible language, and Rob's people were catching the ricochet in real time. He did not open his laptop because opening it would have meant a wave of questions from people expecting immediate responses. He watched the floor numbers count down. At the lobby he badged out, walked across the parking lot to his rental, and sat in the rental for a minute without starting it.

He started the car and was immediately overwhelmed by the music the previous renter had been listening to on the radio of all things. He fumbled for the volume and killed it.

He drove to the airport.

That had been the plan all along. Fly in, present the deck, absorb the damage, fly home. The return flight was booked for early evening because tomorrow morning he had a vendor meeting he could not move without creating three new meetings about why the vendor meeting had moved. Procurement would attend. Finance would attend. Someone from the vendor would say partnership five times, show a cost comparison chart full of lies, and then say something concerning about the renewal cost.

Rob had told himself, when Jack's office booked the same-day turn, that the arrangement was evidence that this situation wasn't an actual crisis. A real crisis would have probably required him to stay through the weekend.

He did not call Anne, who would have known from the first word that something had gone sideways and would have asked the right questions. He did not call Joaquin, his deputy, who would have started problem-solving before Rob finished the sentence. He did not call Rahul, who would have excused himself from the meeting and picked up.

On the way to the airport, two miles before the rental return, his phone buzzed once on the passenger seat. It was a calendar invite, from Ambica's assistant, for ninety minutes from now. Subject line, Quick sync. No agenda. No attendees other than the two of them. Conference room booked under a different name than Ambica's.

He accepted the invite at the next stoplight and put the phone face down on the seat.

Ambica did not do casual calendar invites. Ambica did not book anonymous rooms near airport departure windows because she wanted to hear how the meeting went. Ninety minutes meant: change the flight. It meant the vendor could get Rob on video from a hotel desk tomorrow and complain politely about the conference room audio.

He was still at the light, thumb hovering over the airline app, when another email came in.

Rob — Jack would like you available onsite first thing tomorrow. Please hold on travel until after we connect. I have already asked Travel to preserve a tomorrow morning return option in case your plans need to adjust. Thanks, Marisol.

Not please stay. Not Jack needs you. Nothing that would look interesting in a forwarded thread. Just availability, travel, and plans needing to adjust.

The light turned green. He did not move for a full second after it did. The car behind him gave one short honk.

He pulled into the rental lot, drove past the return lane, and went back the way he had come.

Back to the office.