A Client Thanked Me for Twelve Weeks of Support I Never Approved—Then I Saw My Name in the Deal
PART 5
Naomi called Rachel before responding in writing.
Samira joined.
Curtis was invited and declined because he was in a pricing call.
Naomi did not reschedule around him.
“Thanks for making time,” Rachel said. “I’m trying to build our working calendar.”
“That’s why I wanted to talk,” Naomi said. “The client deck described a level of my involvement that was not reflected in the staffed delivery plan. I’m correcting that internally.”
Rachel’s expression became careful.
“What does that mean for us?”
“It means I’m committed to the architecture review currently scheduled. After that, we need to define whether you need ongoing strategic support, what deliverables it includes, and how it is staffed.”
Rachel looked at Samira.
“We were told it was included.”
Samira said, “You were. That was the representation in the deck.”
Naomi appreciated that she did not hide behind contract language.
Rachel asked, “Are you saying the company won’t honor it?”
Naomi chose her words.
“I’m saying we need to determine what was promised, what is in the signed scope, and what delivery capacity exists. I don’t want to promise you twelve weeks today and then give you scattered rescue calls because we never staffed the work.”
Rachel leaned back.
“That is actually what I’m trying to avoid.”
Naomi nodded.
“So am I.”
Rachel was quiet for a moment.
“Here’s our real need,” she said. “We don’t need you in every working session. We need someone senior at architecture decisions, before test, and before go-live. If that’s four checkpoints, fine. If it’s weekly, fine. I need to know what I can plan.”
The specificity changed the conversation.
Naomi opened a blank page.
“Let’s list the decisions.”
They identified five.
Data model review.
Workflow exception design.
Test-entry checkpoint.
Production-readiness review.
Go-live escalation plan.
“That is not twelve weeks of hands-on support,” Naomi said.
“No,” Rachel agreed. “It’s what we actually need.”
Samira looked relieved.
Naomi was not.
A cooperative client did not erase the company’s promise.
It simply gave them a workable path.
After the call, Curtis appeared at Naomi’s desk.
“You told the client we have a scope issue.”
“We do.”
“You could have solved that internally first.”
“They asked for my weekly calendar.”
“You tell them you’re flexible.”
“I’m not.”
Curtis lowered his voice.
“This is what I mean. We are creating anxiety over something we can manage.”
“Who is we?”
He gave her a tired look.
“Implementation.”
“Implementation did not price the promise.”
“That is not how a company works. Sales does not sell little sealed boxes from separate departments.”
“Agreed. Which is why departments have to agree on the box.”
Curtis leaned against the partition.
“Rachel seems fine.”
“She is fine because she told us what she needs and I did not pretend my calendar was open.”
“Great. So problem solved.”
Naomi looked at him.
“Meridian Freight has me in its deck too.”
Curtis stopped moving.
“That isn’t signed.”
“Why am I in it?”
“Same reason. Senior confidence.”
“Do they have hours for me?”
“We’re still shaping the package.”
“Owen’s resource plan says zero.”
Curtis’s face changed.
“You pulled deal margin?”
“I pulled the implementation assumptions for deals using my name.”
“You’re not in sales operations.”
“I am in the proposal.”
Curtis pushed away from the partition.
“Naomi, be careful about turning a normal sales motion into something sinister because one deck got specific.”
“I haven’t called it sinister.”
“You’re acting like it.”
“I’m asking why my labor is in the client story and absent from the price.”
He looked around, aware of people nearby.
“Let’s not do this on the floor.”
“Agreed.”
They booked a meeting for the next morning with Priya and Owen.
That night, Naomi sat at her dining table with her laptop open and pulled her time reports from the two rescued accounts.
Thirty-eight hours.
Sixty-one hours.
Ninety-nine total.
She remembered every one of those projects.
She had been proud to help.
One project manager had sent her a handwritten thank-you note.
Another client had renewed early.
Good outcomes.
Valuable work.
The problem was not that she had done it.
The problem was that the organization seemed to have learned the wrong lesson from her willingness.
Naomi opened a new spreadsheet.
Client Promise.
Signed Scope.
Priced Hours.
Staffed Hours.
Actual Specialist Hours.
She entered Rachel’s account first.
Then the two rescues.
Then Meridian.
For the first time, she was not asking whether someone had overpromised her time.
She was asking whether her time had become part of how the company priced deals without ever pricing her time at all.
Before bed, Naomi added one more column to the sheet.
What moved because I helped?
On the first rescue account, she had canceled two mentoring sessions and pushed a product workshop. On the second, another strategist had taken over an architecture review Naomi had been scheduled to lead. No disaster had followed. The costs were small enough to disappear individually.
Together they revealed the part Curtis never had to see when he said the company would adjust.
Adjustment had names.
It was junior staff losing development time. It was another client getting a different advisor. It was Naomi answering messages at seven because she had protected the visible commitments and squeezed the invisible ones around them.
Her old system made all of those trades after the sale, when everyone already had a reason to call them necessary.
The next morning she printed the page for Priya.
“I don’t want this to become a complaint about being busy,” Naomi said.
Priya read the list. “It isn’t.”
“I’ve said yes to most of this work.”
“After the client needed it.”
“Yes.”
“That distinction is the issue.”
Naomi nodded.
It was useful to hear someone else say it before the meeting.
