"Some of our other accounts make similar requests."
"Then we should examine those relationships too."
"That could create a lot of friction."
"Probably."
Nathan met her eyes.
"But friction isn't automatically evidence that a process is wrong. Sometimes it means we've stopped allowing an unspoken assumption to do the work of an agreement."
Laura absorbed that.
Then she nodded.
"I understand."
After she left, Daniel remained standing beside the screen.
"You realize this is bigger than Blue Ridge."
"Yes."
"We could uncover the same pattern across several accounts."
"Then we'll have to decide what to do about it."
"Some clients may not like the changes."
"Some employees may not like them either."
Daniel looked at the spreadsheet.
"You're not worried about losing revenue?"
"Of course I am."
"That isn't how you sound."
Nathan leaned back.
"Revenue matters. Profitability matters. Relationships matter. But if we build a business model that depends on our employees quietly absorbing costs because they're afraid to disappoint a powerful customer, we haven't built a sustainable business model."
Daniel crossed his arms.
"What if Blue Ridge walks away?"
"Then we need to understand why."
"And if the answer is that they don't want to pay for what they use?"
"Then we will have learned something important."
Daniel was silent.
Nathan knew the decision was not easy.
Blue Ridge represented years of work. The relationship involved engineers who understood the airline's systems, account managers who had built trust with its operations teams, and support specialists who had become familiar with the rhythms of its business.
A contract was never just a number.
It was a network of people, expectations, and accumulated knowledge.
Changing the relationship could create uncertainty for both companies.
But keeping an unhealthy arrangement simply because it was familiar would not protect anyone in the long term.
Nathan looked again at the spreadsheet.
"Let's make sure we get the data right," he said. "No exaggeration. No assumptions. If the work was included, we classify it as included. If it was paid, we record the payment. If it was a courtesy, we call it a courtesy."
"And if we can't determine what happened?"
"We mark it unknown."
Daniel nodded.
"All right."
"Then we'll decide what the numbers mean."
That afternoon, the review team expanded its scope.
They examined service records, billing histories, account emails, support tickets, and internal time logs. They interviewed employees who had handled Blue Ridge requests. They compared the airline's contract with the agreements Whitmore had signed with other clients.
The results were more complicated than anyone had expected.
Some of the extra work had been trivial.
Some had been genuinely urgent.
Some had been provided because Whitmore's own documentation was inadequate and the company had failed to distinguish product support from consulting.
Other requests had been handled informally because a client executive wanted a quick answer and no one wanted to be the person who slowed the process down.
There was no single explanation.
There was, however, a recurring pattern.
When the client had influence, the cost of refusing a request felt greater than the cost of accepting it.
The actual cost was then distributed across engineers, analysts, and managers who were rarely included in renewal discussions.
That was how a favor disappeared from the record.
Not because no one had done the work.
Because the work had become so familiar that nobody thought it needed to be counted.
By Wednesday evening, the team had enough information to identify several areas requiring change.
Nathan reviewed the preliminary report at home.
His dinner sat untouched on the kitchen counter.
He had expected to find some unbilled work. He had not expected to find so many different reasons for it.
The report did not prove that Blue Ridge had deliberately exploited Whitmore.
It did not prove that every extra request had been inappropriate.
It showed something less dramatic and more useful: the relationship had evolved beyond the clarity of its written terms.
The airline had learned that additional help was often available.
Whitmore's employees had learned that refusing it could create friction.
Over time, both sides had adapted.
One side had come to expect responsiveness.
The other had come to fear the consequences of drawing a boundary.
Nathan closed the report.
He thought of the cabin on Flight 418.
Emily Parker had asked him to move because another passenger preferred his seat.
Ryan Brooks had treated the request as a matter of customer satisfaction.
Calvin Reed had escalated it into a question of authority.
Each person had taken the previous person's decision as a reason to continue.
No one had stopped to ask the simplest question.
Was the request fair?
That was the danger of a system built around informal expectations.