A Client Thanked Me for Twelve Weeks of Support I Never Approved—Then I Saw My Name in the Deal

PART 10

The consequence arrived before lunch.

Samira forwarded a note from Meridian’s procurement lead. The revised options were above the number the client expected, and they wanted to delay the decision while comparing another vendor.

Curtis read the same message and walked past Naomi’s desk without looking at her.

Naomi felt the old rescue reflex immediately.

She could offer thirty hours. Maybe twenty-five. She could join two pre-sale calls, help redesign the implementation model, make the middle package feel richer. She knew exactly how to narrow the price gap without changing the written price.

For ten minutes she drafted possibilities in her head.

Then she deleted the unsent message window.

The point of deal desk had not been to make hard tradeoffs visible only until they became uncomfortable.

At two, Samira called.

“I’m not asking you to fix it,” she said before Naomi spoke.

“Good opening.”

“I am asking whether you’d review the three options for factual delivery risk. One hour. Pre-sale support code. Curtis approved.”

Naomi checked the request. It had a work code, owner, and sixty-minute block.

“Yes.”

Samira exhaled. “That feels weirdly formal.”

“It will stop feeling weird.”

They reviewed the packages. Naomi recommended one wording change and removed a redundant readiness workshop. She did not add herself.

Meridian still delayed.

The company survived the afternoon.

Sales missed the quarterly target by a small amount.

Nobody sent Naomi a bill for it.

The first real test of the new rule came four days later, before anyone had stopped complaining about it.

An account executive named Leo asked for thirty strategy hours on a manufacturing deal that was already in final negotiation.

“Client needs executive confidence,” his request said.

Under the old system, Naomi would have taken a call, heard the risk, and probably found a way to help.

Under the new one, the request forced three questions into the open.

What work was actually needed?

Who would do it?

What would move if Naomi did?

Leo joined Naomi and Priya for a fifteen-minute capacity review. He arrived irritated and left less so.

The client did not need thirty hours of Naomi.

They needed two architecture reviews, one executive readiness call, and an escalation path during cutover.

Nine hours if the project was healthy.

Eighteen if a named contingency triggered.

Naomi could take the first architecture review. Mateo could own the second with Naomi shadowing. Priya could authorize the contingency only if the project hit the defined risk.

Leo looked at the revised plan.

“So I can still tell them they have senior strategy support?”

“You can tell them exactly what they have,” Naomi said.

“That is not as simple.”

“No.”

He tapped the page.

“What if they ask for you by name?”

“Then we price or fund me by name.”

Leo sighed.

“This makes us sound less flexible.”

Priya said, “It makes our flexibility finite.”

The deal closed with the nine-hour package.

Three weeks later, the client hit one of the cutover risks.

The escalation path activated.

Naomi joined for ninety minutes, Mateo did the analysis, and the implementation lead kept ownership of the decision.

No one searched Naomi’s calendar for gray space.

No one told the client a favor had become a feature.

The problem took a day and a half to resolve.

It was not elegant.

It was staffed.

Naomi realized that transparency had not removed urgency from the business. It had removed the fiction that urgency created capacity.

That distinction mattered on the hard days more than it did in a policy document.

For two weeks, however, several people behaved as if they might.

A sales manager joked in the elevator that implementation had discovered a new product called paperwork.

Another account executive asked Samira whether Naomi now required “papal approval” before joining a client call.

Samira answered, “No, just consent and a calendar,” which traveled through the office faster than any policy memo.

Naomi did not enjoy being the story.

She had not wanted to become a symbol of anti-sales bureaucracy.

At the same time, she noticed something useful.

Requests began arriving earlier.

Can Naomi join a forty-five-minute discovery session next Thursday?

Can strategy reserve six hours across two design checkpoints if the deal closes?

Could we price a ten-hour architecture package for this client?

The requests were easier to answer because they were requests.

Sometimes Naomi said yes.

Sometimes she said no.

Sometimes Priya assigned another strategist.

Nothing about that felt revolutionary after the first week.

Rachel Kim’s project moved more slowly than the kickoff deck had implied and more cleanly than Naomi feared.

At the second architecture checkpoint, Rachel brought three decisions instead of nine open questions.

Naomi spent ninety minutes with the team and left with no hidden follow-up list.

At the test-entry checkpoint, one integration assumption failed.

The old pattern would have been an urgent Naomi rescue.

The assigned solution lead owned it with Naomi advising for twenty minutes.

The project slipped four days.

Rachel accepted the new date because the team could explain why.

“Honestly,” she said on the call, “this is less stressful than a fake green status.”

Naomi wrote the sentence down.

Meridian returned six weeks later.

They chose the middle package.

Twenty strategy hours.

Not seventy-five.

Not zero.

The price was higher than the first proposal and lower than the full stabilization package.

Samira closed the deal.

Curtis congratulated her in the team channel.

He did not mention the delayed quarter.

That was another form of moving on.

Naomi’s relationship with him remained cool.

They still worked together.

He still asked hard questions about pricing.

She still told him when implementation was overengineering a package.

Trust did not fully return because the original problem had not been a misunderstanding between two people. It had been a system Curtis believed was smart.

He had changed behavior before he changed philosophy.

Naomi could live with that for now.

Priya formalized Naomi’s role as a strategy advisor with a quarterly capacity cap visible to sales.

It was not a promotion.

Naomi did not want one.

The cap made her work less mysterious.

Forty client-advisory hours per month.

Named exceptions required approval.

Architecture packages had price options.

Emergency support still existed.

But emergency stopped being the default explanation for work everyone could have predicted.

One Friday, Samira came by with coffee.

“I have a confession,” she said.

Naomi looked suspiciously at the cup.

“Does this contain seventy-five hours?”

“Only caffeine.”

“Proceed.”

Samira sat.

“I used to think the best salespeople were the ones who could pull internal favors.”

“Sometimes they are.”

“That is not the answer I expected.”

“Favors are real. Relationships matter.”

“So what changed?”

Naomi considered.

“A favor should still surprise the plan.”

Samira frowned.

“If the plan depends on it, it isn’t a favor.”

Samira nodded slowly.

“That’s annoyingly good.”

“I charge for strategy now.”

Samira laughed.

They drank coffee and reviewed a new proposal.

The client wanted senior support during a complicated data migration.

Samira had added a twelve-hour strategy package.

Named resource: TBD pending approval.

Naomi looked at it.

“Beautiful.”

“Do not get emotional.”

“I’m trying.”