I asked for $500/month and got turned down. The company spent $470K on an AI platform instead. Then I quit.
A story about what $500 couldn't buy, what $470K couldn't fix, and an 87-day countdown on a door that wouldn't open again.
Your company bought AI this year. How much did it cost?
Are you sure that money bought technology — or did it buy a "we're doing AI too" slide deck, and a nicer-looking résumé for someone else?
I asked for $500/month and got turned down. The company spent $470K on an AI platform instead. Then I quit.
1
The pay cut notice went out to the whole department by email.
Red title bar. Three lines of body text. "Optimizing cost structure — evaluating role efficiency." My name was seventh on the list. Not first. Not last.
30%.
I closed the email and went back to fixing the log.
Mike, at the desk next to mine, pushed his keyboard away. "Thirty percent? Are they serious?"
I didn't answer.
He turned to look at me. "You're not mad?"
"I was mad," I said. "Past tense."
— I wasn't mad today. I was mad three months ago, when the VP announced at an all-hands meeting that the company was buying an AI platform for $470K a year. Someone checked quietly — similar platforms on the market cost about a third of that.
After the meeting I followed the VP to his office and put a budget request on his desk.
Cloud servers: $500/month. A model validation pipeline. Stress tests, evaluation runs, regression checks — the full stack. Two pages, every line item accounted for.
The VP flipped through it for three seconds.
"Not needed. The AI platform comes with built-in validation."
"That's black-box testing. Feed in data, get a score. A pipeline needs traceability — which model layer, what parameters, what version of the eval script."
"I hear you. But the budget won't clear." He slid the request back across the desk, like he was mentioning something that didn't really involve him. "Run a prototype on your own account first. Get some results, then we'll talk about budget."
I looked at him.
He knew those words were empty. I knew he knew. Neither of us said anything else.
For the next three months, the entire floor was busy with the vendor's platform deployment. Nobody paid attention to what I was doing. I spent a weekend putting the pipeline together and the rest of the time feeding it data.
"We'll talk about budget" — the VP never brought it up again.
2
The VP hired someone to take over the AI platform — Mark. The whole engineering team's AI work was reassigned to him, including mine. In his first week, he put up a slide deck on the big screen.
Three slides. First one: market size. Second one: customer logos. Third one: one sentence.
"— Covers approximately 72% of the engineering team's routine development work."
That evening I came back to my desk and found Mark standing next to it — holding a piece of paper.
"Unauthorized Systems List." He set it down next to my keyboard. One line was highlighted in yellow: Model Validation Pipeline / Registered Under: Personal Account / Budget Allocation: None.
"From the IT audit. No purchase record, no license, personal account — I'm guessing you haven't read the company's compliance policy."
"You can check with the VP," I said. "He told me to run the prototype three months ago."
Mark didn't respond to that.
He glanced at my screen — the stress test I'd been running for the last twenty minutes.
"The VP resigned," he said. Quietly. Like he was stating something that had nothing to do with him.
The VP left without a goodbye email, without a handover meeting. One day he was at his desk. The next day it was empty.
I didn't react.
"You registered this on a free personal tier?"
I didn't look up.
He stood there for two seconds, folded the paper, and put it back in his pocket. He took three steps toward the door, stopped, and said without turning around:
"You can keep it around. As a reference."
Then he walked out.
I watched him disappear around the corner.
The platform had been live for a month. Every week, Mark sent out a progress email with a dashboard screenshot — model accuracy at 98.7%, response latency under 200ms, coverage climbing steadily. The numbers looked better every time.
But every number was the platform testing itself. Its own test set, on its own models, producing its own report. Not a single data point from actual production feedback.
The only data set in the whole company that could independently validate whether a model actually worked — that was on my cloud server. The test suite had been built from five years of production failures, one incident at a time. Every label hand-reviewed. Every model that passed it, you knew exactly how it would perform on real traffic.
Mark knew how important this thing was — it was outside his audit list, and that's exactly why he needed it. He was auditing my pipeline. What he really needed was five years of my mistakes.
I closed my laptop and went to the rooftop.
Two empty chairs and a waist-high wall. I sat there for fourteen minutes. The wind was strong enough to keep my shirt collar flapping.
My phone rang. I thought it was a delivery.
It wasn't. It was a recruiter.
"Simon? This is Kate. Mia suggested I reach out — she said you might be exactly who we're looking for."
Mia. A recruiter I'd worked with six months ago. She'd put me forward for two positions, neither worked out. But she said better opportunities would come in three months.
Three months.
"What kind of role?"
"AI infrastructure. VP level."
"And the comp?"
She said a number.
Then she said: "Want to think about it?"
"Don't need to. Send me the JD."
I hung up and stood on the rooftop for a long time. You could see the whole campus from up there. Four buildings. I was in Building Two, fourth floor, west side — one of those windows was my desk for five years. Five years. How many PRs had I written? How many bugs had I fixed? How many internal tools had I built? I'd lost count. But the company remembered a different number: what percentage of my work could be automated.
72%.
One number erased every line of code I'd written in five years.
I didn't look at the windows again. I walked back down to my desk.
The keyboard was still warm. The log was still running.
A few days later, I took a half-day off.
3
The interview was in a small conference room at the new company.
No slide decks, no market sizes. The engineering director pushed a laptop across the table with a production incident reproduced on screen: an AI model's recommendation accuracy had dropped from 93.7% to 68.2% over two weeks. No errors in the inference logs. No memory leaks. No latency changes.
He asked: "How would you investigate this?"
I looked at it for three minutes. Three layers.
First, the feature computation pipeline. A text processing library the pipeline depended on had received an auto-patch two weeks earlier. The patch fixed an edge-case bug — but it also changed the vector mapping for those inputs. The edge cases had been a tiny fraction of traffic, barely affecting overall accuracy. But after the patch, the routing shifted. More and more inputs got mapped to the new feature space, and accuracy drifted down, slowly, invisibly.
Second, the input monitor — was the online pipeline running a real-time feature distribution comparison against the training pipeline? A threshold breaker that would shut things down automatically? No.
Third, the human fallback — below a confidence threshold, was there a manual review flow? No. Fully automated. Full black box. Nobody knew anything was wrong until the incident hit. An auto-patch had silently changed the path the model was using to read its own data.
I wrote seven lines of pseudocode. One checkpoint per layer.
The director read it. Then he said one sentence:
"When can you start?"
"A month. Handover."
"What's your notice period?"
"Four weeks."
He picked up his phone, sent a message. Thirty seconds later he put it down.
"We'll buy out your notice period. The offer starts the day you sign. Your salary runs from today."
I stared at him.
"Your time is worth more than the company you're at. I'm not waiting four weeks."
I said: "Deal."
4
Two weeks later, the offer was signed. Sixty percent more than my current salary. No fancy title — "VP" was just a placeholder; I'd start with a team of three.
No need to serve the notice period — the new company bought it out in full. I nodded to HR, signed the handover documents, and that was it.
I sat at my desk, let the last log finish, committed the code, and closed my laptop.
Then I packed. A mug. A few technical books. Sticky notes that hadn't run out. No framed photos, no souvenirs, no "5-year anniversary" plaque — that was at the bottom of a drawer somewhere. I didn't even remember to take it.
I walked to the elevator and pressed B2. The doors closed. Floor 4. Floor 3.
The elevator stopped at 3. The doors opened. Mark was standing there.
He didn't step in. He looked at my backpack.
"You're leaving?"
"Yeah."
He stood there for two seconds, then walked in. The doors closed. He didn't look at me — he watched the floor numbers change.
"That pipeline of yours — the test data and labels — where are they stored?"
In three months, this was the first technical question he'd ever asked me. Not when he was standing in front of the whole engineering team with his audit list. Now. In an elevator. Nobody else.
I didn't answer.
"How do I get access after you're gone?"
"You don't have permissions."
"I can add you as a collaborator — "
"Personal account. One owner. I don't add you, nobody gets in. Call IT, call support — the account is registered under my personal email, and support only talks to me."
He was quiet. Two seconds. Three seconds.
The elevator went from floor 3 to floor 2.
"...How many days do we have?"
"Key rotation every ninety days. You've got eighty-seven."
He didn't say anything else.
The elevator reached B2. I stepped out. He held the door open with one hand — didn't let it close. He watched me walk away and said something that wasn't to me — it was to the elevator wall:
"Eighty-seven days."
The doors closed.
5
I was about ten steps into the B2 corridor when I heard footsteps behind me — not walking, running.
I turned around.
The CEO was coming down the stairwell.
"Wait."
I looked at him.
"Who's poaching you?" His voice was quiet. Not an accusation — he was still catching his breath.
"I signed."
"I know. Who?"
I didn't answer. He stood at the stairwell door for two seconds, caught his breath, and walked toward me.
"I said, who? Give me a name. I'll double it — I'll approve the budget myself. Tell me where you're going right now."
He didn't say "don't leave." He didn't say "we need you." He said "tell me the name of my competitor."
That told me more than any farewell speech ever could.
I looked him in the eye for a moment.
"That AI platform — the one Mark is running — the free trial ends in thirty days. Renewal is $470K a year. You knew that, right?"
He didn't answer.
"When it went live, it was all promises. Now the trial is almost up — has anyone actually verified those dashboard numbers?"
I stepped forward. He stepped back — not because I pushed him, but because he moved.
"Whatever your new company is paying, I'll double it. Report to me directly. No layers."
I stopped and looked at him.
"You signed the pay cut notice. The 30% one."
He froze. "That was company-wide — "
"I know. You didn't stop it."
He had nothing to say.
I said:
"The new company bought out my notice period. The three minutes you've spent talking to me — you just cost them."
He didn't say another word.
I held his gaze for two seconds, then turned and kept walking toward the parking garage exit.
After a few steps, I looked back. He hadn't followed. He was still standing at the stairwell door, tie crooked, one hand on his knee.
The lights were on at B1. He hadn't taken the elevator — he'd run down the stairs.
I didn't look back again.
6
Week four at the new company. My tool passed the full end-to-end stress test.
The engineering director stopped me in the hallway and said exactly one sentence:
"Twelve-week probation — you passed it in four. Want an extra equity grant?"
"The third architecture proposal is still running. Results next week. Let's talk then."
He nodded and walked off.
Before I left, I scrolled past a message from an ex-colleague. The old company's AI platform free trial had expired. They didn't renew. Mark's team had submitted three renewal requests — all three were kicked back. The last one had three words in the approval field: "ROI?"
I opened the AI platform's website. The VP's photo was on the team page. Third screen down.
"72% coverage."
What was left was the 28% that nobody else could do.
I didn't reply to the message. I locked my screen and packed up. The pipeline would break sooner or later. Whether Mark ever got the data — I don't know.
What $500/month couldn't buy, $470K a year couldn't buy either.
The wind on the rooftop is the same everywhere.
Some things don't show up in a budget request. They're not in the slide deck, and they're not in the purchase order. That doesn't mean they don't exist.
So — are you the VP? Are you Mark? Are you the CEO? Or are you me?
If you enjoyed this story, you might also like:
• $660K AI Platform → Replaced
• $8M Vendor Lock-In → Team Fired
• 97.3% Coverage → One Question
• 24h Before Launch → Removed
• Vector DB Demo → SQLite Backup
• $500K Open-Source → Fired
Follow for more stories about AI, engineering, and what happens when code meets corporate reality.
Top comments (0)