Many pricing reviews start too late in the system.
The team opens the price sheet, argues about the number, and treats discount pressure as proof that the number is wrong. Sometimes the number is wrong. More often, the market does not understand why the number is justified.
That is a different problem.
Price pressure usually has a cause upstream
Discount pressure usually points to one of four issues: the buyer does not see enough value, the buyer sees value but cannot defend the business case internally, the offer is packaged for the wrong segment, or the sales motion reaches the economic buyer too late.
Changing the number may help. It will not fix those issues.
The first question is what the buyer does instead
The first pricing question should be simple: what does the buyer do if they do not buy from you?
That answer may be a competitor, an internal process, a spreadsheet, a service provider, a maintenance cycle, or a decision to wait another year.
The alternative sets the value context. If the alternative is cheap and tolerable, the pricing story needs to be sharp; if it creates real cost, risk, or delay, the business case should make that visible.
Packaging does more work than teams admit
Pricing power often improves when the package gets clearer.
A single undifferentiated offer forces every buyer into the same value argument. One services business selling a flat-fee engagement saw deal cycles lengthening before anyone looked at the offer structure. The price was not the problem. The package made no distinction between a pilot scope and a full deployment, so every buyer conversation defaulted to justifying the largest possible commitment. Splitting the offer gave the sales team a reason to ask better questions and made the purchase easier to defend internally.
Before changing the price, check whether the package is doing enough work.
The useful question is why the price is under pressure, not what it should be
A pricing snapshot should not ask what the price should be. It should ask why the current price is under pressure.
That leads to a more useful memo: visible alternatives, competitor signals, buyer segments, value claims, packaging gaps, and the questions worth checking before touching the price sheet. It does not replace formal customer research, a QoE review, or a full competitive analysis. It is a faster outside check on whether the pricing story has a real structural problem or whether the issue is somewhere else in the motion.
Not every pricing problem is upstream. Sometimes the number is genuinely wrong. The work is to find out which problem you have before changing the thing that is easiest to change.