"No."
"Does it mean the work becomes less expensive?"
"No."
"Then what changes?"
Laura looked at him.
"The consequences of saying no."
Nathan waited.
She continued.
"If a regional director asks for a report before a meeting with the chief operating officer, we know that refusing might create frustration. If the request comes from someone who participates in renewal discussions, the team worries that a small disagreement could become a larger issue."
"Has that happened?"
"Not always. But people remember the times when it has."
"Can you give me an example?"
Laura opened her notebook.
"Last winter, Blue Ridge asked for an analysis of crew availability during a period of unusually high cancellations. The original request was reasonable. It became more complicated when the operations team wanted several alternative staffing scenarios. We estimated that the additional work would take two days."
"Did we quote the work?"
"Yes."
"What happened?"
"They said the analysis was essential to the existing service."
"Was it?"
Laura shook her head.
"Not according to the contract."
"Then?"
"We completed it."
"Who authorized that?"
"I did."
Nathan did not react.
"Why?"
"Because the client was under pressure, and I believed it was better to preserve the relationship than argue about a few days of engineering time."
"How much time did the work take?"
"Approximately thirty-six hours across three employees."
"And did the client renew?"
"Yes."
"Did the extra work affect the renewal decision?"
"I don't know."
Nathan nodded.
That answer mattered.
It was honest.
Too many business decisions were justified after the fact by outcomes that could not actually be linked to them.
The account director had provided thirty-six hours of additional work. The client had renewed. It was tempting to conclude that the extra work had helped secure the renewal.
But perhaps the client would have renewed anyway.
Perhaps the additional analysis had been valuable enough that the client would have paid for it if given a clear choice.
Perhaps the renewal had depended on factors entirely unrelated to the request.
No one knew.
"Laura, did you ever feel that Blue Ridge expected us to do this work?"
She was quiet for a moment.
"Sometimes."
"What made you feel that way?"
"The way requests were phrased. Not always. Some people were considerate. Others would say things like, 'You know how important this relationship is,' or, 'We need you to take care of this for us.'"
"Did anyone explicitly say the work was included when it wasn't?"
"Yes, on a few occasions."
"Did you challenge that?"
"Sometimes."
"And when you did?"
"It depended on the person. Some accepted the explanation. Others escalated the issue to my manager."
"Did your manager support you?"
Laura looked uncomfortable.
"Usually. But not always."
Nathan let the silence continue.
He was not looking for a villain.
He was looking for the point at which a reasonable practice had become an unhealthy one.
"Thank you for being candid," he said. "I want you to understand something. We're not going to punish people for trying to help a client. But we need a process that makes the cost visible and gives employees permission to say no when a request is outside the agreement."
Laura nodded.
"That would help."
"What would you change?"
She thought carefully.
"First, define what routine support includes. Second, establish a threshold for additional work. Third, require written approval for requests outside that threshold. And fourth, make sure account managers aren't evaluated only on client satisfaction and renewal rates."
Daniel looked up.
"What else should be included?"
"Whether the account is profitable. How much unplanned work it generates. Whether the client respects the process. Whether the relationship can function without relying on a few employees who are always willing to stay late."
Nathan wrote down the last sentence.
It was a better summary than several pages of financial analysis.
"One more question," he said. "Have you ever been told to provide special treatment because a client contact had influence?"
Laura paused.
"Not in those exact words."
"But?"
"There are people who receive faster responses because everyone knows they can call an executive."
"Is that always inappropriate?"
"No. A genuine emergency may require escalation. A senior executive may be responsible for a critical decision. But influence isn't the same as urgency."
Nathan nodded.
"That's an important distinction."
Laura closed her notebook.
"May I ask something?"
"Of course."
"Is this because of what happened to you on the flight?"
Nathan considered how to answer.
"The flight made me ask different questions. It reminded me that informal hierarchies can become invisible to the people who benefit from them."
Laura looked at the spreadsheet.
"Blue Ridge isn't the only client that does this."
"I know."