My Accidental Billionaire Husband (Katia and Julian) novel Chapter 73

Sparring Partiers

+25 Bonus

Sparring Partners

~Julian-

The session was scheduled for two hours.

We ran it for five.

Nobody mentioned the time. My assistant knocked twice, once at the two–hour mark and once at three and a half, and both times I waved her off without looking up from the whiteboard, and Katia didn’t look up either, which told me she was as deep in it as I was and had made the same unconscious decision to let the clock become someone else’s problem.

The Dubai expansion rollout was the agenda item that did it. Everything before that had been manageable, regional server integration, the London office infrastructure timeline, and the phase three brief she had delivered on Thursday as promised, which was as good as I had expected and better than I had planned for. We moved through those items with the brisk, efficient rhythm we had developed over months of working together, the kind that came from two people who thought at similar speeds and had stopped needing to explain their reasoning to each other halfway through the sentence.

Then we hit Dubai, and something shifted.

“The Al logistics module,” she said, pulling up the rollout timeline on her laptop. “Your team has scheduled it as a phase two implementation. It should be phase one.”

“Phase two makes sense given the infrastructure dependencies.”

“The infrastructure dependencies resolve faster if the AI module is in first. It maps the gaps before you build around them.” She turned the laptop toward me. “Look at the Singapore rollout. We did the infrastructure backwards there first, the module second, and spent four months correcting problems the module would have identified in the first two weeks.”

“Singapore was a different build environment.”

“The principle is the same.” She looked at me steadily. “Phase one.”

“Phase two is what the team agreed.”

“The team agreed before they had the Singapore data.” She reached for the printed brief and flipped to a page she had marked. I hadn’t noticed the marks when she first produced the document, but she had been in this meeting for three hours already, knowing exactly which pages she was going to need. “Page fourteen. The dependency chain.”

I looked at page fourteen.

She was right. I had read the brief twice and missed it, and she had seen it before she walked in the door. That happened sometimes with Katia, the specific, slightly irritating experience of being correct yourself about something and finding out she had been correct about it first and from a different angle.

“Fine,” I said. “Phase one.”

She didn’t look satisfied. She just moved on, which was somehow worse.

We went to the whiteboard at some point; I didn’t register the transition. We simply both ended up there, markers in hand, because the table wasn’t big enough for what we were mapping. The Dubai rollout had seventeen interdependencies, and Katia drew them out in the systematic, ruthlessly clear way she did everything, calling out the sequence while I tracked the timeline, and at some point the distance between us at the whiteboard had become something less than professionally necessary.

I was aware of it. I was aware of it in the specific way I had become aware of these things with her–not all at once, but gradually, like a temperature change you only noticed after it had already happened.

She was talking about server latency. The marker was moving across the whiteboard. Her voice had the particular quality it got when she was fully engaged with a problem–lower than usual, faster, and precise. I was listening to the content and also to the voice, and I was doing an adequate job of not making that obvious.

1/3

Sparring Partners

+25 Bonus

“The handoff window between the Invisible Shield and the logistics module is eighteen minutes,” she said. “That’s your vulnerability point. Anything that needs to happen in that window needs to be pre–staged.” She marked it on the board with a circle. “We close this before launch or we don’t launch.”

“Agreed.” I marked the timeline above it. Our markers were three inches apart on the whiteboard. “Pre–staging means the Dubai team has to be ready two weeks earlier than the current schedule.”

“Then move the schedule.”

“Moving the schedule affects the London parallel.”

“Only if you’re treating them as dependent.” She turned slightly. We were close enough that the movement brought her face into the edge of my peripheral vision. “They’re not dependent. They share resources on two nodes, and that’s it. Ring–fence those nodes and run them separately.”

She was right again. The solution was clean, and I had been treating a resource sharing issue as a structural dependency for no

reason I could defend.

“Ring–fence the nodes,” I said.

“Ring–fence the nodes.” She wrote it on the board.

My assistant knocked.

“Mr. Windsor, you have a dinner at eight. It’s currently seven forty.”

I looked at the clock on the wall. Then at the whiteboard covered in two people’s handwriting, the markers, the timeline, the dependency chain, and the seventeen things we had resolved and the three we hadn’t yet.

“I’ll be ten minutes,” I said

The door closed.

Katia was already stepping back from the whiteboard. The professional distance reasserted itself with the smooth efficiency of something that had been waiting to be reinstated. She set her marker down and picked up her jacket from the back of a chair and began gathering her files with the organized efficiency of someone who had been in this room for five hours and was leaving it exactly as ordered as she had found it.

She didn’t look at me.

“Good session,” she said, without looking up.

I watched her. The files going into the bag in the right order. The laptop closed and slotted in. Put the jacket on. Every movement was precise and contained and completely normal.

VERIFYCAPTCHA_LABELVerify