Chapter 2
Chapter Two
Logan
The meeting should have ended twenty minutes ago.
I know this because I scheduled it for forty-five minutes, which was already ten more than it required, and because the man currently talking has now said the same thing three different ways without appearing to notice that I stopped responding after the first.
David Mercer is a competent enough regional director — his numbers are clean, his team performs, his instincts on the infrastructure rollout have been mostly sound.
But he has a habit of mistaking thoroughness for intelligence, and right now he is walking me through a contingency plan I identified the flaw in while he was still pulling up the slide.
"The secondary failover," I say, cutting across whatever point he is currently building toward.
"It's dependent on the Portland node. If Portland has a capacity issue during peak load — which, based on last quarter's data, it will — the entire contingency collapses."
Mercer stops. He looks at the slide. Then he looks at me with the particular expression of a man recalibrating in real time.
"I'll have the team run the load projections again."
"Have them on my desk by Thursday." I close the folder in front of me, which is the only signal anyone in this building needs that a meeting is over.
"The core strategy is sound. Fix the failover dependency and bring me the revised model."
He nods and gathers his materials with the efficiency of someone who has learned not to linger. The two analysts flanking him follow his lead without being told. I appreciate that about the people who last here — they learn to read a room quickly, and the ones who don't learn it don't last.
The conference room empties in under ninety seconds.
I stay at the table for a moment, reviewing the notes I made during the presentation — three lines, all of them actionable, none of them requiring further meetings to resolve.
Through the glass wall behind me, the floor operates at its standard tempo.
Forty-three people in this division alone, all of them moving with the focused efficiency of a workforce that understands what is expected and why meeting that expectation matters.
I built the culture of this office over the past several years with the same precision I apply to everything else — not through speeches or vision statements, but through consistent and unambiguous standards. People perform at the bar you set. Set it low and you get exactly what you deserve.
I push back from the table and walk toward my office at the far end of the floor.
Keith falls into step beside me before I've reached the halfway point — he has an instinct for timing that I've come to rely on without ever saying so directly.
Six years at Drake Industries, which in this industry qualifies as a full career.
He handles strategic partnerships with the kind of quiet competence that doesn't require managing, which is the only kind of competence I have patience for.
He's also one of the few people in my professional orbit who will say something I don't want to hear without dressing it up first, which I value more than I've ever told him.
"Mercer?" he asks, glancing at the folder under my arm.
"Fixable. Thursday."
"The Nakamura group called while you were in there. They want to move the quarterly review up a week."
I push open the door to my office. "Why?"
"Board scheduling conflict on their end." He follows me in, stopping at the threshold the way he always does — Keith has never once sat down in my office without being invited to, which is another reason he's lasted this long.
"I can push back if you want."
"Move it up. Reschedule whatever's in the way."
"Already done." He pauses, and I recognize the pause — it means there's something else. "The Vertex presentation is confirmed for the fourteenth. I'll send you the updated brief this afternoon. Also — Hargrove is pushing back on the licensing terms again. Third time this month."
I turn from my monitor and look at him directly.
"What specifically?"
"The exclusivity window. He wants eighteen months. We offered twelve."
"We offered twelve because eighteen gives him leverage he hasn't earned and exposes us if the partnership underperforms in the first year." I turn back to my screen.
"Tell him twelve is the ceiling. If he wants to keep negotiating, he can find another partner who has more patience for it than I do."
Keith absorbs this without reaction.
"I'll communicate that."
"Diplomatically."
The corner of his mouth moves — not quite a smile, but the closest approximation Keith allows himself in a professional setting.
"Always."
He leaves without filling the silence with anything unnecessary, which is something I've come to value from him.
Through the floor-to-ceiling windows behind my desk, San Francisco sits under a sharp November sky — the bay visible from this height, the morning light cutting clean angles across the Financial District below.
I've worked in this office for a long time.
The view has never stopped being a useful reference point.
There are days when the scale of what's out there is a productive reminder of what's still left to build.
I turn to my correspondence and work through it with the same methodology I apply to every morning — highest priority first, everything else in descending sequence, nothing left in a state of ambiguity.
Ambiguity is expensive. I made that determination early in my career and I've never had reason to revise it.
By 10:15 I'm on a call with our legal team regarding vendor agreement terms that need restructuring before the end of the quarter.
I identify three points of exposure they've missed, walk them through the revised language I want, and end the call in eighteen minutes.
My assistant — Rachel, who has managed my schedule and correspondence for three years with the precision of someone who treats her work as a craft — brings me a coffee without being asked and sets it at the edge of my desk without interrupting the call.
It's the last thing Rachel does for me as my employee.
She appears in my office doorway at 11:40.
I know from her expression before she speaks that this isn't a scheduling matter or a correspondence question.
She has the look of someone who has rehearsed what they're about to say, which means it's personal, and personal in a professional context almost always means one thing.
"Mr. Drake." She steps inside, her own folder in hand.
"I need to speak with you."
I set down my pen and give her my full attention.
It's the least I can do. She's leaving. Two weeks' notice, though she offers to extend if the transition requires it.
Her husband's company is relocating to Seattle.
She's been going back and forth on the decision for months — I believe her, because Rachel has never been someone who acts without deliberation.
She apologizes for the timing. She thanks me for the years.
I listen to all of it without interrupting.
When she finishes, I tell her that her work here has been consistently excellent and that her reference will reflect that accurately.
I mean both statements completely. I also feel nothing personal about either of them, which is not a contradiction — it's simply how I'm built.
Rachel has been an exceptional assistant.
She is also, as of this moment, a logistical problem that needs solving before the end of the business day.
Both of those things are equally true and I hold them with equal weight.
She leaves my office with the relieved expression of someone who expected the conversation to go worse. I pick up my phone before the door finishes closing.
"Patricia." My head of HR answers on the second ring.
"Rachel Simmons just gave notice. I need a replacement in place before she's out."
A brief pause on her end.
"I actually have something already in the pipeline that may be worth looking at. Can I come up in an hour?"
"Fine."
I set the phone down and return to the vendor agreement.
The operational gap Rachel's departure creates is real but manageable — two weeks is enough time to identify the right candidate and run an abbreviated onboarding if the person is capable enough to learn fast. I need someone who can manage the infrastructure of my professional life without requiring infrastructure of their own.
Rachel did that from the first month. The next person will need to do it at the same level or I'll be running the search again in sixty days, which is not a use of time I'm willing to accept.
I draft three items of correspondence, review the updated Vertex brief Keith sends through at noon, and flag two line items in the quarterly projections that need to be addressed before Friday's board call. At 12:45 I hear the knock I've been expecting.
Patricia enters with a single printed resume and the composed efficiency of someone who has worked for me long enough to know that I don't need context I didn't ask for. She sets it on my desk without preamble.
"This came in two weeks ago," she says.
"Referral through Caleb."
I look at the name at the top of the page. Sutton Kane.
The Caleb reference lands without surprise and without particular feeling.
My brother and I don't speak with any regularity — this is a fact of our relationship that neither of us has ever found urgent enough to address.
That the call went to Patricia rather than to me directly is consistent with how Caleb operates.
He uses the Drake name when it serves him and maintains his distance from everything attached to it otherwise.
I don't hold it against him. We made different choices a long time ago and we've both built our lives accordingly.
I set the Caleb reference aside and read the resume properly.