The initial implementation had been modest. Over time, the relationship had expanded.
Blue Ridge added maintenance forecasting, workforce allocation, delay analytics, and executive reporting. It purchased additional modules and negotiated support commitments for critical operational periods.
The contract was substantial, but it was not Whitmore's largest agreement.
What made it valuable was the opportunity to work with a complex transportation network.
What made it difficult was the amount of attention Blue Ridge had come to expect.
"Here," Daniel said, pointing at a paragraph. "This is the weekend response provision."
Nathan read it.
The language was straightforward. Whitmore guaranteed a specified response window for defined severity levels. Critical system failures received immediate escalation. Routine issues were handled according to a published schedule.
Nothing unusual.
"Now look at this."
Daniel opened another document.
It was an internal service log.
The entries were brief.
Friday, 8:47 p.m. — Blue Ridge requests additional analysis for Monday executive briefing.
Saturday, 6:12 a.m. — Engineering provides preliminary report.
Saturday, 11:35 a.m. — Operations requests revised staffing model.
Sunday, 9:18 a.m. — Additional review completed.
Nathan scanned the entries.
"How many of these were included in the agreement?"
"Some were. Most weren't."
"How many?"
"We're still counting."
"Then don't give me an estimate."
Daniel nodded.
"I asked the team to separate contractual obligations from discretionary support. We should have the first complete pass by Wednesday."
Nathan turned another page.
The pattern repeated itself.
A manager needed a dashboard adjusted before an executive presentation. An operations director requested a late-night analysis. A regional vice president wanted a staffing scenario reviewed before a meeting with the board.
Some requests were legitimate emergencies.
Others were ordinary business needs that had become urgent because someone had waited too long.
Whitmore's teams had often helped.
Sometimes they had charged for the additional work. Sometimes the request had been small enough that no one bothered to create a separate billing entry. Occasionally, an employee had simply stayed late because a client relationship mattered and the company had trained its people to take pride in being useful.
Nathan did not consider generosity a weakness.
He had built Whitmore Systems through relationships in which people helped one another solve difficult problems.
But generosity became dangerous when one party began treating it as an entitlement.
"Who approved these exceptions?" he asked.
"Usually the account director. Sometimes engineering managers. In a few cases, senior leadership."
"Did anyone ask the client to approve additional charges?"
"Yes. Several times."
"And when the client declined?"
Daniel glanced at his notes.
"In most cases, we continued with the work anyway."
Nathan raised his eyes.
"Why?"
"Because the requests came from people who controlled the renewal discussions. The account team didn't want to be perceived as difficult."
"Did they tell the client the work was outside scope?"
"Sometimes."
"Did they document that the work was being provided as a courtesy?"
"Not consistently."
Nathan looked back at the report.
There it was.
Not necessarily misconduct. Not necessarily exploitation. But a relationship that had become blurred around the edges.
The contract defined what Blue Ridge had purchased.
The informal habits defined what Blue Ridge had learned to expect.
And the two were no longer the same thing.
"Daniel, I want three categories," Nathan said. "First, work we are contractually required to provide. Second, work we have explicitly agreed to provide through written amendments or paid add-ons. Third, work we've provided because someone asked, because we wanted to be helpful, or because we were worried about what might happen if we said no."
"That third category could be substantial."
"Then we need to know how substantial."
Daniel wrote the categories on his legal pad.
"What happens after we identify it?"
"We honor every existing obligation. We fulfill every active commitment. We don't deliberately degrade the service, delay a ticket, or create a problem to make a point."
"Agreed."
"We also stop making new promises that aren't part of the agreement. If Blue Ridge wants additional work, we price it, document it, and let them decide whether they want to purchase it."
Daniel looked at him.
"That's a significant change in how the account operates."
"It's a significant change in how we understand the account."
"Those aren't always the same thing."
"No," Nathan said. "But they should be."
Daniel closed the contract folder.
"I'll brief the account team today. Carefully."
"Good."
"And the flight?"
Nathan's expression remained steady.
"Document it. Preserve the details. If we contact the airline, we do so through the proper channels. I don't want anyone making threats or using the contract as a weapon."
"Understood."
"One more thing."
Daniel waited.
"Don't tell the team this is about punishing Blue Ridge. If that's how they understand the decision, they'll make the wrong decisions for the wrong reasons."