What He Cannot Control

The Cost Of Speaking

Leah’s POV

The room goes very still. This is not how things work in a Steele Corporation presentation. Presentations are monologues delivered by people in positions of authority. You listen. You take notes. You absorb the information. You ask clarifying questions only when you're invited to do so, and only if those questions are constructive and don't challenge the fundamental premise of what's being presented.

Kenneth stops mid-sentence, his hand frozen halfway through a gesture. He looks at Leah like she's just made an error—or like she's about to make one. His eyes flick toward James. James's jaw tightens slightly. His eyes shift toward Adrian.

Adrian looks at Leah with an expression that suggests mild curiosity mixed with something else. Irritation, perhaps. The kind of expression someone makes when they're being interrupted in the middle of something they consider important. A small crease appears between his eyebrows—not deep, just a subtle indication that her hand-raising has caused some kind of disruption in his mental processing.

"I apologize for the interruption," Leah says. Her voice sounds smaller than she intended, but she keeps speaking because if she stops now, she won't have the courage to continue. She can feel every eye in the room on her now. She can sense the collective intake of breath—this is unusual, this is not protocol, this is someone breaking the unspoken rules that govern how presentations function. "But I noticed something in the numbers that I wanted to clarify before you move forward with the campaign approval. I want to make sure I'm understanding the methodology correctly."

"The numbers are preliminary," Kenneth says quickly. He's nervous—Leah can see it in the way his hands tighten on the presentation remote, in the way his shoulders have tensed. He's also defensive, anticipating attack. "They're based on historical data and conservative estimates. We can adjust them as needed once we have more recent performance data."

"I'm not questioning the estimates themselves," Leah says, and she means this genuinely. She's not trying to undermine Kenneth or make him look bad in front of Adrian. She's trying to help ensure that the company doesn't make a decision based on flawed financial modeling. "I'm just noticing an inconsistency in how the numbers are being applied. You're projecting 96,600 new customer acquisitions at a $324 lifetime value, which should equal approximately 31.3 million in customer value. But you're projecting Q1 revenue of only 14.7 million. That's significantly less than half the expected value from those acquisitions. I'm wondering if there's something in the methodology I'm not understanding, or if there's a different calculation being applied to the revenue projections."

Kenneth's face has gone very red. A vein is visible in his neck, pulsing with his elevated heart rate. He's clearly not used to being corrected publicly, especially not by someone as junior as Leah. Especially not by someone who's been at the company for nine days.

"The 31.3 million is theoretical customer value," Kenneth says, and now his voice has an edge to it. He's trying to sound authoritative but mostly sounds defensive. "The actual revenue collected in Q1 would be lower because not all customers will make purchases immediately. The timeline for customer acquisition and value realization is staggered. The 14.7 million is the conservative estimate based on typical payment cycles and customer onboarding timelines."

Leah looks at the slide again. She studies it carefully, trying to find the explanation for the discrepancy. But the methodology section doesn't clearly explain how the payment cycle adjustment is being calculated. The slide shows the numbers but not the assumptions that led to those numbers.

She also understands that she's now in a position where she's either right or she's embarrassed Kenneth in front of the CEO, and she can see which one everyone in this room is banking on. If she backs down now, she becomes the person who questioned authority without basis. If she continues, she has to be absolutely certain she's right.

But she is certain. She's looked at enough spreadsheets, analyzed enough business models, to know when numbers don't align with the story being told about those numbers.

"May I?" Leah says, and she stands up. Her legs are slightly shaky, but she pushes the feeling down. She walks toward the presentation materials with as much confidence as she can summon. "If the 14.7 million is the Q1 collection based on payment cycles, then the annual projection of 58.8 million doesn't make mathematical sense either. That would assume only 318,000 annual customer value from 96,600 customers, which is significantly lower than the stated $324 lifetime value per customer."

She points to the slide, her finger steady even though her heart is racing. "Either the lifetime value needs to be recalculated to reflect the actual expected revenue, or the revenue projections need to be adjusted upward to reflect the stated lifetime value. As currently presented, this strategy proposal contains contradictory financial assumptions. Which means we don't actually have a reliable understanding of whether this campaign will be profitable or not. We're making a decision based on numbers that don't internally align."

The room is completely silent. The kind of silence that feels heavy, that makes Leah acutely aware of every sound—the hum of the air conditioning, the quiet electrical buzz of the presentation equipment, her own breathing.

Adrian Steele is watching her with an expression that Leah can't immediately read. She's learned enough about him in nine days to know that this expression—completely neutral, completely controlled, absolutely unreadable—is the one he uses when he's processing something that disrupts his expectations.

"Show me the detailed breakdown," Adrian says. His voice is quiet, which somehow makes it more authoritative than if he'd spoken louder. "Kenneth, I want to see the actual methodology. Not the summary, the actual step-by-step calculation."

Kenneth fumbles for the next slide. His hands are shaking slightly as he navigates to the detailed breakdown section of the presentation. He's clearly flustered, losing the smooth rhythm he had before. The detailed breakdown appears on screen, and once it's visible, Leah's concern becomes immediately and obviously apparent. The lifetime value calculation is being applied inconsistently across the different time periods. The model assumes customers will be acquired over time and will generate value over time, but the revenue projections are treating them as if they're all paying up front. It's a fundamental logical inconsistency.

"This needs to be corrected," Adrian says. He's not angry—his tone is almost clinical, like he's observing a mechanical failure. "The underlying logic is sound, but this financial model is broken. It's broken enough that we can't approve it as currently presented. We can't allocate budget based on assumptions that don't internally align."

Leah feels a small wave of relief wash through her. She was right. The numbers were wrong. And more importantly, she was right to say something about it.

But relief is quickly replaced by concern and uncertainty. She's just corrected the CEO in front of an entire presentation team. She's just made Kenneth look incompetent. She's just violated the implicit rule that you don't challenge authority, especially not publicly in front of senior leadership.

"Kenneth," Adrian continues, "I want you to rebuild this financial model. Work with our analyst team. Get the numbers right, actually verify the assumptions, and come back when you can show me actual clarity on what this campaign will generate. I need reliable data, not theoretical projections with internal contradictions."

Kenneth nods, his face still very red. He looks miserable.

"Leah," Adrian says, and her heart jumps at the sound of her name in his voice. He's never spoken her name before. She didn't think he knew her name. "Come to my office when this meeting is over."

The meeting continues, but Leah stops processing the content. She's focused on controlling her breathing, on not panicking, on maintaining a neutral expression. She's focused on the reality that she's just potentially made a career-limiting mistake on her ninth day of employment. She's corrected the CEO publicly. She's embarrassed a senior executive in front of his peers. She's broken protocol.

She should have stayed quiet.

Except she shouldn't have. The numbers were wrong.

The other junior employees file out quickly after the meeting concludes, avoiding eye contact with her. Kenneth gathers his materials without looking at anyone, his jaw clenched, his entire posture suggesting barely controlled frustration. James follows him out, offering Leah a small nod that might be supportive or might be sympathy for what's about to happen.

By the time the conference room emptied, Leah understood that one interruption had become something larger: a test she had not known she was taking.