A Client Thanked Me for Twelve Weeks of Support I Never Approved—Then I Saw My Name in the Deal
PART 1
Naomi Price knew the kickoff had gone wrong before the client finished thanking her.
“We were especially relieved to see the twelve weeks of hands-on support from you included,” Rachel Kim said from the large video square on Naomi’s screen. “That was one of the reasons we felt comfortable moving forward.”
Naomi kept her face neutral.
Across the conference room table, Samira Holt, the account executive, glanced down at her notes.
“Twelve weeks?” Naomi asked.
Rachel smiled. “The executive implementation support. Architecture, workflow design, launch readiness. The deck says you’ll stay attached through go-live.”
Naomi had approved a two-hour architecture review.
Not twelve weeks.
Not go-live.
Not hands-on implementation.
She clicked the kickoff deck open on her second monitor while Rachel continued describing the client team. There it was on slide six.
Executive Implementation Support — Naomi Price, Implementation Strategy.
Twelve-week engagement.
Weekly architecture office hours.
Launch readiness review.
Escalation support through production.
Naomi looked at Samira again.
Samira gave a tiny movement of her head that could have meant not now or I didn’t know or please don’t blow this up in front of the client.
Naomi chose the only statement she could make without lying.
“I want to make sure our delivery plan and your expectations match,” she said. “I’m going to review the signed scope after this call and confirm exactly how my role is staffed.”
Rachel’s expression changed slightly.
“Is there a question?”
“There’s a staffing detail I want to verify.”
Naomi had spent eleven years in implementation. She knew how quickly a client could hear staffing detail and translate it into bait and switch.
She also knew how quickly an internal team could hear client concern and translate it into Naomi will fix it.
Rachel nodded. “All right. We’d rather clarify now.”
That answer made Naomi like her immediately.
The rest of the kickoff was ordinary. Integration owners. Data deadlines. Test environments. Executive checkpoints. Naomi took notes while her mind kept returning to slide six.
When the call ended, Samira closed the conference room door.
“I thought Curtis cleared that,” she said.
“Cleared what?”
“The executive support package.”
“With whom?”
Samira hesitated.
Naomi opened her calendar.
The next twelve weeks were already full. Two launches. Three architecture reviews. A process redesign for a client that had delayed testing twice. Mentoring time with two newer strategists. Internal product workshops. No weekly block for Rachel’s company.
No hidden reserve of twelve weeks.
“Show me what you sold,” Naomi said.
Samira pulled up the signed statement of work.
The document was sixty-three pages, most of it standard language. Naomi searched for her own name.
Nothing.
She searched strategic implementation support.
One sentence appeared in the services description.
Vendor will provide strategic implementation guidance from senior resources as reasonably required during the implementation term.
Naomi read it twice.
“That is not twelve weeks of me.”
“I agree.”
“But the client deck says it is.”
“Curtis wanted the deal team to show the executive bench.”
“The executive bench is not a person’s calendar.”
“I know.”
Naomi opened the internal resource plan.
Project manager: one hundred eighty hours.
Integration consultant: two hundred forty.
Training specialist: eighty.
Implementation strategy: zero.
She pointed to the screen.
“Where are my hours?”
Samira leaned closer.
Her face lost color.
“I thought they were in a shared support pool.”
“There is no shared support pool.”
“I have heard Curtis call it that.”
Naomi looked back at the signed scope.
The client had been shown twelve weeks.
The internal plan had assigned her zero hours.
Somewhere between the sales promise and the delivery plan, Naomi’s time had disappeared while her name remained.
She closed the conference room laptop.
“I’m not asking who made a mistake yet,” she said. “I’m asking what the company expects me to deliver.”
Samira looked uncomfortable.
“I’ll get Curtis.”
“No. First send me every client-facing version of this deck and every resource plan attached to the deal.”
“Why?”
“Because I want to know whether twelve weeks was added before or after the price was final.”
Samira stared at her.
Naomi had the answer ten minutes later.
The final client deck promised twelve weeks of Naomi Price.
The final resource plan promised none of her.
Before she left the conference room, Naomi opened the project-risk register too. Rachel’s company had marked architecture continuity as a high concern during sales discovery. Next to it, a response had been copied from the proposal deck: senior strategy support through launch. No owner. No hours. No dates.
Naomi had seen vague risk language before. Usually it meant somebody would decide later. This was different. The client had already decided what it meant because the deck had given the vagueness her name.
She remembered a launch the previous winter when a client had called at six on a Friday because an integration sequence was failing. Naomi had stayed on until nine, returned Saturday morning, and rebuilt the decision tree with the project manager. The account had gone live. Sales had sent her a gift card and a note that said, Knew you would save us.
At the time, she had been pleased.
Now she wondered whether the story had traveled farther than the thank-you note.
