Chương 5
His face went still.
Not shocked.
Not confused.
Still.
That was worse.
“You need to be careful with accusations.”
“I’m being careful.”
I opened the folder.
“I’m being more careful than the person who changed the risk assessment.”
A door opened behind him.
Thomas stepped out.
He looked between us.
For a moment, nobody spoke.
Then Thomas said, “Megan.”
“Mr. Reed.”
Ryan forced a smile.
“Thomas, I was just explaining the situation.”
Thomas looked at him.
“No.”
The word was calm.
Not aggressive.
That made it stronger.
“You were explaining your version of the situation.”
Ryan’s smile disappeared.
The conference room behind him became quiet.
People had noticed.
Not everyone.
Not enough.
But enough.
Thomas turned toward me.
“Come inside.”
Ryan stepped forward.
“Thomas, before we do anything, I think we need to remember that Megan is no longer with the company.”
Thomas looked at him.
“I remember.”
“Then I’m not sure why—”
“Because the contract is with your company.”
He paused.
“But the work product was created by people.”
Nobody moved.
Ryan looked uncomfortable for the first time.
Not embarrassed.
Not defeated.
Just uncertain.
And uncertainty was something I had never seen on him before.
Thomas opened the door wider.
“Megan, bring the documents.”
I walked past Ryan.
For a second, I smelled the coffee from the conference room.
The same expensive coffee he ordered during every important meeting.
The same coffee he always forgot to drink because he was too busy talking.
A small, stupid detail.
A normal detail.
And somehow it made the whole thing feel real.
I entered the room.
Eight people turned toward me.
Some recognized me.
Some did not.
One person looked surprised.
Another looked uncomfortable.
Ryan entered last.
He closed the door behind him.
Then Thomas placed a printed copy of the submitted proposal on the table.
“We have a problem.”
Nobody spoke.
Thomas looked at Ryan.
“Before we discuss the contract, I want to understand why the final submission differs from the technical package originally approved.”
Ryan leaned back.
“Differences happen during final preparation.”
“Do they?”
“Yes.”
Thomas opened a document.
“These are not formatting differences.”
Ryan looked at the pages.
“They are strategic adjustments.”
I watched him say it.
The confidence was still there.
But something underneath it had cracked.
Because now he was not speaking to employees who needed him.
He was speaking to people who could decide whether he walked away with eight hundred million dollars.
And they were not impressed by confidence anymore.
They wanted answers.
And they were not impressed by confidence anymore.
They wanted answers.
Ryan folded his hands on the table.
It was a small movement.
Almost invisible.
But I had spent enough time around him to recognize it.
Whenever Ryan felt in control, he leaned forward.
Whenever he felt threatened, he created distance.
“Thomas,” he said, keeping his voice steady, “I think we need to be careful about making assumptions.”
“I agree.”
“Good.”
“But assumptions are exactly why we are here.”
The room stayed quiet.
A woman from Henderson’s legal department looked through the pages in front of her.
A senior engineer named Mark Caldwell tapped a pen against his notebook.
He had always been quiet during our previous meetings.
The kind of person who listened so carefully that people sometimes forgot he was there.
Now he looked at Ryan differently.
Not with anger.
With calculation.
Ryan noticed.
“Let me explain the context,” he said.
Nobody stopped him.
That was probably what bothered him most.
Ryan was used to being interrupted by people who wanted to please him.
Silence made him nervous.
“The original proposal was technically strong,” he continued.
“However, we had concerns about how conservative the language was.”
I almost laughed.
Not because it was funny.
Because I had heard that argument before.
Every time Ryan wanted something changed, he called caution a weakness.
“The client wanted confidence,” he said.
“And we adjusted accordingly.”
Thomas looked down at the document.
“Who approved those adjustments?”
Ryan hesitated.
Just for a second.
“Leadership.”
“That is not a name.”
Nobody moved.
Ryan looked around the table.
“Megan was responsible for the technical package.”
His eyes landed on me.
“She created the original material.”
There it was.
The first attempt to move the weight.
Not denying the change.
Not explaining it.
Redirecting responsibility.
I placed my hands on the table.
“Ryan.”
He looked at me.
“If I was responsible for the technical package, why was I removed before the client presentation?”
The room changed.
Not dramatically.
Not like movies.
Real rooms did not freeze.
People simply stopped pretending they were not paying attention.
Ryan looked away.
“Megan, that decision was unrelated.”
“Then what was the reason?”
“I already told you.”
“No.”
My voice stayed calm.
“You told Patricia to read a script.”
His expression hardened.
“You are making this personal.”
“I am asking a professional question.”
Thomas watched both of us.
Ryan leaned back.
“This is exactly the issue.”
“What is?”
“You have difficulty separating your emotions from business.”
The sentence landed harder than I expected.
Not because it was true.
Because I had spent years wondering if it was.
Maybe that was his favorite weapon.
Making people question whether they were too sensitive to notice what was happening.
I looked at the documents.
Then at Thomas.
“Ask him about the access history.”
Ryan’s face changed.
Small.
Quick.
But everyone saw it.
“What access history?”
Thomas answered.
“The system records.”
Ryan exhaled.
“Everyone knows those records exist.”
“Yes.”
Thomas opened his laptop.
“Which is why I am asking why the final file was accessed from your account at 8:37 AM, and why Megan’s account was removed two minutes later.”
Ryan looked irritated now.
Not worried.
Irritated.
The way someone looked when a meeting was not following the script they prepared.
“That does not prove anything.”
“No.”
Thomas nodded.
“It does not.”
The agreement seemed to surprise Ryan.
“But it raises a question.”
May you like
“What question?”
“Why was the person responsible for the technical package removed before a final submission that changed technical assumptions?”
