Pricing Support decision map
Pricing support is the explanation layer
The price file says what you want to offer. Pricing support says why that offer is reasonable. If those two layers are disconnected, review gets harder.
A good support package is not necessarily long. It is easy to follow.
Support should match the offer type
Products often need catalog, commercial sales, reseller, manufacturer, or market support. Services often need labor-rate history, market compensation, labor category duties, education and experience assumptions, and discount explanations.
The support should reflect what is actually being sold.
Use file names that help the reviewer
A file called pricing.pdf is less useful than a file named by category, SIN, price family, or support source. The upload package should be navigable by someone who did not build it.
What this looks like in practice
In practiceA services firm writes a reviewer note for every rate family
Instead of uploading invoices and hoping they speak for themselves, the team writes a short note for each labor family: commercial basis, comparable work, discount applied, escalation assumption, and support file location.
The note is not fluff. It is a map that helps the reviewer follow the evidence.
- Commercial basis
- Support file
- Discount
- Escalation
- Reviewer note
Frequently asked questions
Is a commercial pricelist the same as pricing support?
A commercial pricelist can be part of pricing support, but support may also include invoices, market comparisons, labor logic, discounts, and explanatory notes.
How much support is enough?
Enough to let a reviewer understand the price basis, discount, and reasonableness without guessing. Thin support is one of the easiest ways to slow a package down.
Should support be organized by SIN?
Often yes. If pricing varies by SIN, labor family, product family, or service line, organize support around those review lanes.