It was a Tuesday. Four people on the Zoom. Our biggest customer on the other side, with their head of product doing the talking and two of their engineers quietly watching me sweat.
They wanted a date. A real one. The kind you put in a slide and show your board.
I could feel the shape of the answer forming in my mouth before I had checked it against anything. “End of Q1,” I was about to say. It felt reasonable. It felt confident. It would end the awkward pause.
And then a card slid up in the corner of my screen.
What it actually said
Four short sections. I read it in about two seconds, because that is all a coaching card gets.
Watch for: you just said “end of Q1.” Two engineers on this team are on parental leave Jan–Mar.
Frameworks: commit to scope OR date, not both. Pick one axis to be firm on.
Questions to ask: which parts of this do you need in Q1 vs. which parts can slip to mid-Q2?
What to avoid: giving a confident date you'll walk back in three weeks.
I closed my mouth. I took the pause I had been trying to avoid. Then I said something like: “Before I give you a date, I want to split this into what you actually need in Q1 and what can land in mid-Q2. Walk me through which of these pieces is blocking you.”
The head of product nodded. He had been expecting a date he could poke holes in. Instead we spent fifteen minutes scoping. Two of the four items turned out to be nice-to-haves. The real Q1 deliverable got smaller. The mid-Q2 commitment got cleaner. Nobody left angry.
The quarter of pain I didn't have
I know exactly what the other version of that meeting looks like, because I have lived it before. You commit to the aggressive date in the room. You walk out feeling like you held the line. Three weeks later you are the person on a Slack thread explaining that two of your engineers are out and the thing you promised is not going to happen on time. Trust takes a chip. Then another. Then you are rebuilding.
The coaching card did not do anything clever. It did not read the customer's mind. It noticed a specific phrase I had just said, matched it against something I already knew (my own team's calendar), and handed me the single most useful sentence I could ask in that moment.
It was the thing a great chief of staff would lean over and whisper to me, if I had one in the room.
Boring on purpose
The coaching engine runs locally. It listens to the live transcript, pulls relevant context from your own notes and prior meetings, and every twenty seconds or so decides whether there is something worth putting on screen. Most of the time there isn't. The best coaching card is the one that doesn't fire.
When a topic shows up that benefits from more structure (a commitment, a tough objection, a hiring decision, a scope negotiation) it switches from a one-line nudge to the four-section card you just read. Watch for. Frameworks. Questions to ask. What to avoid. Same shape every time, so your eyes know where to land.
I think a lot about how fast a human can read something while also talking. The answer is: not very fast. Which is why the card is four bullets and not a paragraph. If it takes more than two seconds to absorb, it has already failed.
What it won't do
It won't save you from a bad deal. It won't make an unprepared person sound prepared. If I had not already known my team's leave schedule and put it in my notes, the card would not have had anything to warn me about. The intelligence is yours. The card is the delivery mechanism.
It also fires wrong sometimes. In the early builds it would offer structured guidance for small talk, which is annoying. We tuned the confidence threshold up and capped offers at three per meeting, which helped a lot. It is still not perfect. If you accept one and it wasn't useful, there is a thumbs-down that trains it to shut up about that pattern. I use that button more than I would like to admit.
The deal you don't lose
Most of the time I can't point to a specific meeting the product saved. The wins are invisible. You just notice, over a quarter, that you are walking out of rooms feeling slightly less wrecked. Fewer “why did I say that” moments on the drive home.
But every once in a while there is a moment like the Tuesday card, where I can draw a straight line from a sentence on my screen to a quarter of pain I did not have. That is what we're building IntelliPrompter to do.
If that sounds like a tool you want in your next hard meeting, the beta is at intelliprompter.com/beta.
Jeff