← Field notes
Use case

The salary conversation you've been putting off

The conversation you've prepped the most for and executed the worst. Here's how real-time coaching helps.

Jeff · October 11, 2026

I was thirty-one, sitting in a glass conference room, and I had rehearsed the number for a week.

I knew what I wanted. I knew what the market said I was worth. I had a peer's offer letter screenshotted on my phone for backup. I had three sentences memorized, in order, for the exact moment my manager would push back. And then he pushed back, calmly, and I heard myself say, “well, I mean, I'm flexible, obviously.”

I was not flexible. I had decided, in writing, the night before, that I was not flexible. But the room had a temperature and my mouth had an opinion and the two of them agreed to a smaller number than the one in my head.

I've been on the other side of that conversation too. More times than I want to count. Someone comes in prepared, holds the line for about ninety seconds, and then flinches. I've watched good people leave real money on the table because the silence after their ask felt unbearable.

The pattern

Prep is not performance

Salary conversations are the single most over-prepared, under-executed type of meeting I know. People read books about them. They do mock negotiations with friends. They write scripts. They memorize ranges and anchors and BATNAs.

Then the actual meeting starts and the emotional charge in the room drowns out everything they studied. Your heart rate is up. You are asking another human being, out loud, to value you more. That is a vulnerable thing to do, and vulnerability does not play nicely with recall.

I've seen the same three failure modes, in myself and in people I've managed:

Over-explaining the ask. You state the number, and then you keep talking. You justify. You contextualize. You list every project you shipped last quarter. By the time you stop, the number is buried under a pile of your own anxiety and the other person is responding to the anxiety, not the number.

Under-asking. You walked in thinking $185k. You hear your own voice say “somewhere in the 170s, maybe.” You will spend the next six months pretending that was a strategic choice.

Collapsing under deflection. The other side says “that's not really how our bands work” or “we'd have to go back to finance on that,” and instead of waiting, you fill the space. You offer a smaller number before they've even said no.

What we built

A quiet voice in your corner

I built IntelliPrompter partly because I wanted the version of me from that glass conference room to have had something on the screen that said, in the moment, you already decided. Hold the number. Stop talking.

For salary conversations specifically, the live coaching surface does three concrete things. Not magic. Just the frameworks you already know, delivered at the moment you need them, instead of an hour before or an hour after.

It flags over-explaining. The coaching engine watches for the pattern where you've stated your ask and are still talking thirty seconds later. A small card appears: “You've made the ask. Let them respond.” That's it. No alarm, no interruption. A reminder that the silence is supposed to be there.

It holds the number. Before the meeting, you tell IntelliPrompter what you came in to say. “Base of 195. Signing of 25. No lower than 185 base.” When the other party deflects, the card that surfaces is not a clever comeback. It's your own words, in your own voice, from calmer you thirty minutes ago. “The number is 195. You decided that yesterday.”

It surfaces the framework you prepped. If you loaded a doc on handling the “we don't have budget” objection, that doc is indexed. When the objection shows up in the live transcript, the relevant paragraph lands on your screen inside a second. Grounded in content you wrote or chose, not whatever a model hallucinated.

The ethics of this

Not a trick

I want to be careful here, because this is where tools like ours can go sideways.

IntelliPrompter is not for manipulating the other person. The second guardrail in our published AI ethics is explicit: we will never surface suggestions designed to exploit the vulnerabilities of the person across the table. No neurolinguistic programming. No “this prospect sounds anxious, press harder.” No reading their emotional state and weaponizing it. That line is not a marketing line. It's a line in the prompt and a line in the eval set and a line in our heads.

What this tool is for is much narrower. It helps you say, under pressure, the thing you already decided to say when you were calm. It closes the gap between the version of you who prepared and the version of you who actually has to perform. In a salary conversation, that's the whole game. The other person is a human being with their own interests, and I think they deserve a counterpart who can actually represent themselves clearly. That's better for both of you.

If you walk out of a raise meeting feeling like you tricked someone, we've built the wrong thing. If you walk out feeling like you finally said what you came in to say, we've built the right one.

If you want to try it

The next meeting

If you have one of these conversations on your calendar in the next few weeks, this is a useful one to run with. Load your prep doc. Write out your number and your floor. Let the coaching surface do the boring, hard work of reminding you of your own plan when the room gets warm.

Private beta is open at intelliprompter.com/beta. It's not for everyone yet. We're still rough in places, and if you are not comfortable with a product that ships twice a week and occasionally breaks on a Thursday, wait a cycle. But if you have a conversation coming up where the number in your head and the number that comes out of your mouth need to be the same number, I'd like you to try this.

Hold the number. Let them respond. The silence is supposed to be there.

Jeff

More field notes are on the way. Feature by feature. Pain and gain.

Join the beta waitlist