Record yourself saying your own price out loud and listen back to it once. Most founders find something they didn't know they were doing: the pace speeds up right before the number, like it's a bandage worth ripping off fast, or a small laugh follows it, or a sentence gets tacked on immediately after that nobody asked for — "but obviously that's flexible depending on what you need." None of that is really about the price. It's about what the founder privately worries the number says about the company, or about them, and the buyer hears every bit of it.
The flinch is a tell, and buyers read tells
A price stated flatly, at normal speaking speed, with a full stop after it, reads as a fact. The same price, said quickly, followed by a laugh or an unprompted qualifier, reads as a negotiable opening position, even if you never meant it that way. You've just told the buyer, without meaning to, that there's room to push, and now the rest of the call is partly about finding out how much room, which is a conversation you didn't intend to have and don't want to be in.
The fix isn't confidence as a mood. It's mechanical: say the number, then stop talking. Let the silence that follows be the buyer's to fill, not yours. If they push back, that's a real negotiation and you can have it deliberately. If they don't, you've just avoided negotiating against yourself for no reason, which is what the unprompted qualifier actually does.
Part of what causes the flinch is doing the arithmetic live, in front of the buyer, for the first time. Founders often haven't decided, before the call, exactly what the annual figure is next to the monthly one, or what a multi-seat deal actually costs once you multiply it out, so the pause before answering isn't nerves about the price itself, it's mental math with an audience. Write the numbers down beforehand — monthly, annual, and whatever the most likely variant of this specific deal will need — so that saying the number is reading rather than calculating.
Discounting before anyone asked is a founder problem, not a buyer problem
Watch for the specific moment: you've stated the price, there's a beat of quiet, and you offer a lower number before the prospect has said a word about cost. That's not a response to an objection. There was no objection yet. It's the founder's own discomfort finding a reason to end early, dressed up as generosity. The buyer, who was possibly about to say yes to the number you started with, now has to recalibrate around a number you volunteered for reasons that had nothing to do with them.
If a discount is ever going to happen, let it happen in response to something real — a longer commitment, a case study you can use, a referral, a specific piece of friction they named. A discount with nothing traded for it teaches the buyer that your price was never really your price, and that lesson is expensive to un-teach on every renewal after this one.
Lead with the number, not the feature recap
There's a common structure that makes the flinch worse: summarize everything the product does, build up to the price as if it's the reveal at the end, then say it in a rush because by then the tension has been building for two full minutes. Reverse the order. State the price early, plainly, then spend the rest of the time on what it includes. A number stated first, with no theater around it, feels like a fact about how the business works. A number saved for last, after a buildup, feels like a moment you were bracing for, and the buyer notices the bracing more than the number.
Practice on a price that isn't yours to be nervous about
If you want to hear what a flinch-free price actually sounds like, say a published price out loud that has nothing to do with your own anxiety about it — a subscription you use, a plan on someone else's pricing page. Notice how flat it sounds, because you have no personal stake in whether the listener thinks it's fair. That flatness is the target. It's not a different set of words. It's the same sentence said by someone who isn't privately negotiating against themselves while they say it.
The apology is doing work you don't want done
"I know it's not cheap, but—" is the single most common sentence said immediately after a price, and it does something specific and unhelpful: it tells the buyer, on your authority, that the price is high, before they've formed their own opinion. Plenty of buyers who would have thought your price was reasonable now have a founder's own words telling them otherwise. Say the number. If they think it's high, let them say so, and then you can actually address what they said instead of the version you pre-emptively apologized for.
What actually earns confidence here
Confidence saying a number out loud is not a personality trait some founders have and others don't. It comes from having done the arithmetic on the number yourself, ahead of time, well enough that you believe it before anyone else has to. If you can't say, in one sentence, why the number is what it is — what it costs to deliver, what it's worth to the buyer, why it's not double or half — the flinch will find its way into the room regardless of how many times you rehearse the delivery. Do the arithmetic first. The steady voice follows the arithmetic; it doesn't precede it.
Where this connects to how we price our own product
We publish our own numbers for exactly this reason — $24.99 a month for the first tier, $79 for the next, $149 above that, a free tier with no card required to see what the market for your product actually looks like before you spend anything. None of those numbers gets said differently depending on who's asking, because there's nothing to flinch about: they're published on a page, checkable by anyone, and we can say why each one is what it is. That's the whole trick, applied to your own price rather than ours. A number you can defend in one sentence is a number you can say without speeding up.