Would it have devoted the same resources to the complaint of a teacher traveling to visit her grandchildren, a warehouse worker flying home after a night shift, or a college student using savings to purchase a premium ticket for the first time?
Nathan did not know.
He would not claim to know.
But the question would remain with him until the airline's actions provided a meaningful answer.
The Favor Nobody Had Counted
By Tuesday morning, the first internal review had produced a spreadsheet containing more than three hundred entries.
Daniel Harper placed it on the screen in Nathan's office.
"These are the requests we could identify from the previous eighteen months," he said. "They're not all outside the contract. We're still classifying them."
Nathan scanned the columns.
Date.
Requesting department.
Service category.
Response time.
Contract reference.
Billing status.
The last column contained a surprising number of blanks.
"Why are so many unclassified?"
"Because the work was handled through email, direct messages, and informal calls. The team often completed the task without creating a formal service ticket."
"How much time are we talking about?"
"We don't have a reliable total yet."
"Then we don't have a reliable total."
Daniel nodded.
"I know."
Nathan moved closer to the screen.
"Start with the largest categories."
Daniel filtered the spreadsheet.
Additional reporting requests.
Emergency staffing models.
Maintenance analytics.
Custom dashboard adjustments.
Executive presentation support.
The first category contained dozens of entries. The second contained several dozen more. The remaining categories were smaller but involved more specialized engineering work.
"Some of these are legitimate support issues," Daniel said. "A client can ask questions about a product. We expect to help them understand it. That's part of the relationship."
"Agreed."
"But some requests are essentially consulting projects. A manager wants a new analysis, a new report, or a different model for a particular meeting."
"And we provided it."
"Often."
"Why?"
Daniel gave a small, uncomfortable shrug.
"Because the account team believed responsiveness protected the renewal."
Nathan looked at him.
"Did it?"
"We haven't established that."
"Then the team was paying an unmeasured cost to protect an unmeasured benefit."
Daniel sighed.
"When you put it that way, it sounds irresponsible."
"It sounds incomplete. That's why we're reviewing it."
Nathan did not enjoy humiliating employees any more than he enjoyed being humiliated himself. The account team had not created the entire problem alone. For years, senior leadership had praised employees who went beyond expectations. Nathan had personally congratulated engineers who had solved urgent client problems after hours.
He had encouraged initiative.
He had encouraged generosity.
He had encouraged the company to care about its clients.
Those were not mistakes.
But a leader could create a harmful incentive without intending to do so.
If employees learned that every extra hour would be praised but never measured, they would eventually stop recognizing the difference between exceptional service and unpaid labor.
And if a client repeatedly received something without paying for it, the client might eventually forget that the service had ever been optional.
The result was not necessarily greed.
Sometimes it was simply habit.
Habits, however, could become expectations.
"Who manages the Blue Ridge account?" Nathan asked.
"Laura Bennett."
"Bring her in."
Daniel sent a message.
Ten minutes later, Laura entered the office.
She was thirty-eight, an experienced account director who had worked with Blue Ridge for four years. She carried a notebook and appeared prepared to discuss the data.
Nathan invited her to sit.
"Laura, this isn't a disciplinary meeting."
She relaxed slightly.
"Thank you."
"We're trying to understand how the account developed. I want your honest assessment, even if it means identifying decisions that should have been handled differently."
"All right."
Daniel displayed the spreadsheet.
"How would you describe our relationship with Blue Ridge?"
Laura considered the question.
"Collaborative. Fast-moving. Sometimes demanding, but generally productive."
"Do they request work outside the contract?"
"Yes."
"How often?"
"More often than some clients."
"Do they pay for it?"
"Sometimes."
"What happens when they don't?"
Laura looked down at her notebook.
"Usually, we absorb the smaller requests."
"Who decides what's small?"
"That depends on the request."
"Is there a written threshold?"
"No."
"Is there a consistent approval process?"
"Not one that covers every situation."
Nathan nodded.
"Then how do you decide?"
Laura took a breath.
"If the request is something an engineer can handle in fifteen minutes, we usually just do it. If it takes longer, we discuss it internally. If it's urgent, we may do the work first and work out the billing later."
"And if the request comes from a senior executive?"
Laura hesitated.
"Then it's harder to push back."
"Why?"
"Because the account relationship matters."
"Does that mean the request becomes contractually included?"