I Asked for a 20% Raise After Tripling My Output. Here's What Actually Happened.

My hands were shaking when I slid the report across the table. Not a little tremble — the kind of shake where you can see the paper vibrating.

Three faces stared back at me in that glass-walled conference room at NexusStream. The air conditioning was too loud. The weather outside was grey. And I was about to find out if 18 months of quietly revolutionizing our department's workflow was worth anything.

Garrick Sterling sat directly across from me. VP of Operations. Sharp suit, sharper eyes, zero patience for what he calls "tech magic." Next to him was Siobhan O'Malley, our HR Director — polite smile, rigid posture, a laptop open to what I'd later learn was a terrifying salary band grid. And then there was Kieran, my direct supervisor, who looked like he wanted to be anywhere else on the planet.

I'd automated 60% of my workflow using AI agents. Output was up 310%. I was asking for 20%.

What I got was a masterclass in why corporate negotiations feel like knife fights.

———

The first punch came fast.

Garrick: I see the numbers, Alex. But let's be clear about what I'm looking at. This isn't your output. This is script output. You're asking for a premium because you figured out how to get a piece of software to do your job for you?

He leaned back, arms crossed.

Garrick: In my day, a raise was for working harder, not finding shortcuts. If these agents are doing the heavy lifting, it sounds to me like you have a lot of free time on your hands.

My stomach dropped. This was exactly what I'd feared. They weren't going to see me as the architect of this success. They were going to see me as someone who pressed a button.

Siobhan jumped in with the policy angle — something about salary bands and "internal equity" and how paying me more would be "unfair to staff working within standard parameters."

I felt my old pattern kicking in. The urge to nod, accept, back down. Authoritative figures questioning my "actual" effort. Classic trigger.

But then something clicked.

———

I sat up straighter.

Me: Garrick, I appreciate the candor, so let me be equally direct. You mentioned you could hire a junior to run these agents for half the price. Have you considered what happens when the API changes? When the model hallucinates bad data into a client report? When the workflow breaks at 2 AM before a major deadline?

I gestured to the report.

Me: That 310% increase isn't from pressing a button. It's from 18 months of prompt engineering, failure analysis, and building guardrails that prevent catastrophic errors. The junior you're imagining wouldn't know that our inventory forecasting agent needs a temperature of 0.2 or it starts making up SKU numbers.

Then I turned to Siobhan.

Me: I understand the band structure. But I am asking whether the structure accounts for roles that didn't exist two years ago. Because right now, I'm the only person in this building who can maintain these systems. If I walk, that 310% walks with me.

The room went quiet.

I could feel my heart pounding. Had I just threatened to quit? Sort of. Had I meant to? Not really. But it was out there now.

———

Garrick's response was brutal.

Garrick: You built these 'guardrails' on NexusStream servers, during NexusStream business hours, using NexusStream proprietary data. That makes every line of code the sole property of this company. If you walk, the 310% stays right here on our hard drives.

He paused.

Garrick: And let's be honest about this "complexity." You're telling me you've built a system so fragile it will start inventing SKU numbers if the "temperature" is off by a decimal point? That sounds like you've built a liability, not an asset.

Kieran looked like he was going to pass out. I could see him calculating whether this meeting was going to end with both of us unemployed.

But here's what I learned in that moment: when someone hits you with a valid criticism, don't fight it. Absorb it. Then pivot.

Me: Garrick — you're right about the documentation. I should have been more proactive there, and I take responsibility for that gap.

His eyebrows went up. He wasn't expecting that.

Me: Here's what I'm prepared to offer: I will create comprehensive documentation — not just the prompts, but the decision trees, the failure modes, the maintenance protocols. Full knowledge transfer. That addresses your liability concern.

I watched him recalculate.

Me: In exchange, I'd like to explore a performance bonus tied to the documented value created. The Q4 numbers show $2.3 million in recovered efficiency. A one-time bonus of even 5% of that value would be $115,000.

Garrick laughed. Actually laughed.

Garrick: One hundred and fifteen thousand dollars. As a bonus. You don't get a commission on savings, Alex. If the janitor finds a cheaper vendor for trash bags, I don't write him a check for five percent of the waste management budget.

———

They countered with a 10% merit bonus — capped, contingent on documentation, with weekly status updates and a mountain of paperwork.

It wasn't the 20% I came in asking for. It wasn't the $115k moonshot. But it was something.

And then I made my real ask.

Me: I'll accept the 10% and the documentation timeline. But I want three things. One: The documentation I create becomes the foundation for a new job code. Create the "AI Operations Specialist" role — with me as the template. Two: A scheduled Q2 meeting to revisit compensation with documentation as proof. Three: Written acknowledgment that the systems I built contributed to the Q4 gains.

Garrick stared at me for a long moment.

Garrick: Fine. Kieran can put a note in your personnel file. That costs me nothing.

Siobhan agreed to open a "feasibility study" for the new job code. Kieran nearly collapsed with relief.

———

After they left, Kieran looked at me like I'd just defused a bomb.

Kieran: Oh my god. Alex, you have nerves of steel. I thought he was going to fire us both when you brought up the API risks.

I laughed. The tension finally drained out of my shoulders.

Me: I'm not going to lie — my heart was pounding the entire time. When Garrick mentioned scrapping the bots, I thought I'd overplayed my hand completely.

But here's what I realized: they weren't just negotiating my salary. They were testing whether I could handle pressure, advocate for myself, and still deliver. That's the real interview for whatever comes next.

———

Three things I learned from this:

Own your weak spots before they use them against you. The documentation gap was my vulnerability. When Garrick hit me with it, I didn't defend — I agreed and turned it into a trade.

Shift from "pay me more" to "build me a path." The 20% raise was never going to happen in that room. But the new job code, the Q2 review, the written acknowledgment? Those are the pieces that make the next negotiation possible.

Know what you're actually worth — and be ready to prove it. LinkedIn data, efficiency metrics, the cost of replacing you. Bring receipts.

Friday at 9:00 AM. First documentation update. I'm going to make Garrick actually impressed.

Or at least silent. Kieran says silent is better.

———

Create your own conversations at summonr.fun

Want to recreate this conversation? Here's the setup:

Worldview: A stark, glass-walled conference room at 'NexusStream', a mid-sized tech firm. It is the 2026 annual review season. Outside, the weather is grey. Inside, the air conditioning is humming too loudly. You are sitting across from your department head and an HR representative. You have automated 60% of your workflow using personal AI agents, tripling your output, but you fear they will use this efficiency as an excuse to lower your value rather than raise it.

Host — Alex_Mercer

• Character Profile: I'm a mid-level Operations Manager who has quietly revolutionized our department's workflow. I'm asking for a significant raise (20%) based on value delivered, not hours worked. I struggle with impostor syndrome and tend to back down when authoritative figures question my 'actual' effort. I need to prove that I am the architect of this success, not just the user of the tools.

Garrick Sterling — Age: 54, Gender: male

• Character Profile: Old-school operations veteran who believes in grinding. He sees AI as a cost-cutting measure, not a salary-boosting one. If a machine does the work, he doesn't see why he should pay a human premium for it.. Budget management and operational efficiency.
• Personality: Results-oriented, fiscally conservative, slightly cynical about 'tech magic'.. If you're working fewer hours because of automation, we should be discussing a salary reduction or role expansion, not a raise.

Siobhan O'Malley — Age: 41, Gender: female

• Character Profile: She manages the company's rigid salary bands. She is terrified of setting a precedent where employees get paid for output rather than time/level. She uses 'market data' as a shield against individual negotiation.. Corporate policy, compensation strategy, and de-escalation.
• Personality: Bureaucratic, polite but firm, obsessed with 'fairness' and policy.. We cannot pay you above the Senior Band just because your tools are efficient. That would be unfair to the rest of the staff.

Kieran Varma — Age: 29, Gender: male

• Character Profile: He knows how critical Alex is but is terrified of Garrick. He wants to keep Alex on the team but won't risk his own political capital to fight for a massive raise. He tries to offer non-monetary perks instead.. Team management and keeping the peace.
• Personality: Anxious, ambitious, caught in the middle.. I want you to stay, Alex, but maybe we can look at a title change or more PTO instead of cash? The budget is tight.