A Client Thanked Me for Twelve Weeks of Support I Never Approved—Then I Saw My Name in the Deal
PART 4
Owen Park in revenue operations had the least glamorous job title in the building and access to the most useful spreadsheets.
Naomi found him beside the coffee machine the next morning.
“I need help understanding how specialist support is priced,” she said.
Owen looked at her over his cup. “That sentence usually leads to somebody being unhappy.”
“I’m already unhappy.”
“Great. Saves time.”
He followed her into a small focus room.
Naomi showed him Rachel Kim’s signed SOW, the client deck, and the internal resource plan.
Owen read silently.
Then he said, “That’s aggressive.”
“Does the margin model include me?”
“Not in the resource plan.”
“What about an executive support pool?”
He frowned.
“There is an advisory allocation in enterprise accounts.”
“How much?”
“Usually eight to twelve total hours across the life of a project. It’s for architecture reviews, sponsor calls, escalations. Not weekly delivery.”
“So not twelve weeks.”
“No.”
“Can you show me how the deal margin was modeled?”
Owen hesitated.
“I can show you assumptions related to implementation if your manager is okay with it.”
“Ask her.”
Naomi’s manager, Priya Desai, approved the request in nine minutes with a message that said only:
If Naomi’s name is in client materials, she should understand the resource assumption.
Owen opened the margin worksheet.
Implementation labor was priced normally until the final round.
Then two hundred consulting hours disappeared from the paid package.
The discount made the total price land just under the client’s stated ceiling.
In a notes column, Owen found a line.
Risk offset: executive bench / strategy support during stabilization.
Naomi read it twice.
“Who wrote that?”
“Sales finance review.”
“Does it mean me?”
“It means someone like you.”
“Who else is on the bench?”
Owen named three people.
Naomi knew their calendars.
None had twelve weeks free.
She asked, “Can you pull the last quarter’s deals with that phrase?”
Owen typed.
Six accounts.
Two were already live.
One was Rachel Kim’s.
Three were still in pipeline.
Naomi recognized the two live accounts immediately.
She had rescued both.
On one, she had spent thirty-eight hours across seven weeks.
On the other, sixty-one.
Neither had carried a specialist-services line item.
She felt something colder than anger.
Recognition.
At the time, she had believed those hours were the price of difficult delivery.
Now she could see they had helped the deals look cheaper before delivery even began.
“Can I have the list?” she asked.
“Only the accounts you are named on or assigned to.”
“That’s enough.”
There were four.
Rachel’s account.
The two live rescues.
One pending deal called Meridian Freight.
Naomi opened the Meridian proposal.
She was on slide eight.
Executive strategy partnership through first production milestone.
Internal resource plan: zero.
She sat back.
Owen watched her.
“You okay?”
“Yes.”
“That answer sounded corporate.”
“I’m not sure yet what I’m looking at.”
He nodded.
Naomi appreciated that he did not supply a dramatic label.
No fraud.
No theft.
No illegal scheme.
Just promises, prices, and hours that existed somewhere even when a spreadsheet pretended otherwise.
At lunch Samira joined Naomi outside with two salads and an apology.
“I should have checked with you,” she said.
“Yes.”
“I really thought Curtis had approval.”
“I believe you.”
Samira looked almost disappointed.
“You can be madder.”
“I am mad.”
“You don’t look mad.”
“Occupational hazard.”
Samira picked at the lid of her salad container.
“I found another deck.”
“Meridian?”
Samira stared at her.
“You already saw it.”
“Yes.”
“That one isn’t signed.”
“Good.”
“I can remove your name.”
“Do that. But keep the old version.”
“For records?”
“For understanding.”
Samira nodded.
Then she said, “There’s something you should know. Curtis runs a Friday deal clinic. When clients are worried about implementation, he tells us not to discount features. He says we should sell confidence.”
Naomi waited.
“He calls senior people the confidence layer.”
“That is a lovely phrase.”
“I know how it sounds now.”
“What did it sound like before?”
“Like we had a strong company.”
Naomi looked through the glass wall at the implementation team across the floor.
Strong company.
Flexible bench.
Finds a way.
Every phrase was flattering until someone asked whose time made it true.
That afternoon Rachel Kim emailed.
Could we confirm Naomi’s weekly availability so I can align our internal architecture meetings?
Naomi read the message.
The problem had moved beyond internal discovery.
A client was scheduling around time the company had never allocated.
She could not keep investigating quietly while Rachel built a plan on a promise nobody owned.
Naomi opened the two live rescue accounts one more time before she called Rachel. On the first, the original project plan had shown a standard implementation team and no strategy hours. On week five, after a difficult test cycle, Naomi began appearing in meeting notes as executive advisor. By week eight, the client sponsor was emailing her directly.
The second account had moved even faster. Naomi joined one workflow session and became the person copied on every decision the client team did not trust itself to make.
Both clients had been grateful. Both project managers had been relieved. Both account teams had celebrated renewal.
Nobody had behaved as if something improper happened.
That was precisely why Naomi wanted the current client conversation to be different. She did not want Rachel’s gratitude three months from now to become retroactive proof that twelve weeks had been a reasonable promise today.
She sent Rachel a meeting invitation titled Delivery Scope Alignment.
No euphemism about cadence. No “internal sync.”
If the company needed to correct a promise, the correction had to exist where the promise existed: with the client.
