“You used to own the relationship.”
“I used to lead the project.”
“Heartland heard you joined us. Their CIO requested a meeting.”
“Legal first.”
She raised an eyebrow.
“You don’t want the meeting?”
“I want the meeting clean.”
Our counsel confirmed that Heartland could choose to engage Forge Point independently, but I could not use Eastbridge proposals, internal pricing history, or protected account strategy.
I had no interest in doing that.
Mark Delaney, Heartland’s CIO, walked into our conference room the following Monday carrying the same black notebook he had used during our Eastbridge implementation.
“Well,” he said, shaking my hand. “This is awkward.”
“It doesn’t have to be.”
“Eastbridge says they can still support phase two.”
“They may be able to.”
He looked at me.
“You’re not going to tell me they can’t?”
“No.”
“Why not?”
“Because you didn’t come here to hear about my old employer. You came here because you need a plan.”
That made him relax.
For two hours, Rachel and I presented Forge Point’s approach using requirements Heartland had provided directly.
We proposed a slower migration than Eastbridge.
More validation.
More rollback checkpoints.
More operational testing.
At the end, Mark closed his notebook.
“Eastbridge is cheaper.”
“Then evaluate whether the price difference justifies the scope difference.”
“You’re terrible at pretending to be a salesperson.”
“I sleep better.”
Four days later, Heartland signed a letter of intent with Forge Point.
A little over two million dollars across implementation and support.
I had been there nine business days.
That afternoon Dana messaged me.
Not bad for a guy who missed his bonus.
I responded:
Working.
That evening Elaine called.
“Michael.”
“Elaine.”
“I hear you’re already working Heartland.”
“Heartland requested a Forge Point proposal.”
“You know what that account means to us.”
“I know what it meant while I worked there.”
Her voice tightened.
“Some of the projects you handed off are struggling.”
“I left complete handoffs.”
“I’m not accusing you. Transitions are difficult.”
“I agree.”
“Would you be willing to help Noah with a few calls? We can pay a consulting rate.”
“No.”
“Michael, this isn’t about pride.”
“Correct.”
“Then why not help?”
“Because I work full-time for another company. Because Eastbridge approved my departure. And because Noah needs authority, not a former manager appearing whenever executives get nervous.”
“We can structure it.”
“I’m sure you can.”
“You’re colder than I expected.”
“I’m clearer than I used to be.”
I ended the call politely.
Ten minutes later, Rachel appeared at my office door.
“You need to see this.”
She showed me an email forwarded by a contact at Sterling Electronics.
Victor Hale, Eastbridge’s sales director, had written that I left Eastbridge after performance concerns and that customers should be cautious about following a former employee who had not met internal expectations.
I read the email twice.
Rachel watched me.
“Want me to send this to legal?”
“Yes.”
“Want to call Victor?”
“No.”
“Why not?”
“Because if he says it in writing, he can explain it in writing.”
The easiest response to a lie is outrage.
The useful response is documentation.
Forge Point’s counsel asked for records I already legally possessed.
My performance reviews downloaded from my personal HR portal.
Exceeds Expectations.
The previous year: Outstanding.
Eastbridge’s public case study for Sterling quoted me by name as implementation lead.
Two public conference recordings showed Daniel introducing me as “the person we send into our hardest accounts.”
That was the problem with rewriting history after spending years publicly praising someone.
The original version leaves evidence.
Our attorney sent Eastbridge a narrow preservation letter.
No press statement.
No online argument.
No threat-filled language.
Just a request that relevant communications be preserved and that Eastbridge stop making unsupported statements about my performance.
Two days later, Sterling’s COO called me.
“Mike, I received an interesting email from your old company.”
“I know.”
“You have a legal issue?”
“Our lawyers are handling it.”
“I’m not calling because I believed them.”
I waited.
“I’m calling because I don’t want Sterling dragged into a circus.”
“Neither do I.”
“Good.”
Then he changed subjects.
Sterling was acquiring two plants.
They needed one data platform across three facilities.
Forge Point had been trying to enter the account for almost a year.
I could have used Eastbridge’s behavior to attack them.
Instead, I asked, “What changed operationally since phase one?”
The conversation moved where it belonged.
Work.
Ten days later, our proposal went in.
Eastbridge offered a twelve-week rollout at a price nineteen percent below ours.
We proposed sixteen weeks.
During the client presentation, Sterling’s COO frowned.
“Why are you slower?”
Our technical director answered.
“Because you have three plants with different master-data conventions, and we’re refusing to pretend that doesn’t matter.”
The room went quiet.
Then the COO looked at me.
“You let your technical people talk to clients like that?”
“I encourage it.”