How should I make the decision?

Map what information buyers need before a conversation and publish the parts that can be stated accurately. Record the evidence and remaining uncertainty before committing.

Public pricing vs contact sales

The decision belongs in your wider saas pricing plan. Start with the customer task and operating constraint, then compare the options against that context.

Where each option fits

Public pricing

Public pricing helps buyers self-qualify when packages and charging units can be explained consistently.

Contact-sales pricing

Contact sales can fit genuinely variable scope or complex buying requirements, provided the buyer still receives useful commercial context.

The comparison that matters

Dimension	What changes the decision
Qualification	Buyer-led evaluation versus guided scoping.
Complexity	Standard packages versus variable terms.
Trust	Clarity and honest limits matter in both paths.

The table is a decision framework, not a claim that one option always wins. A useful choice accounts for the work your team can perform, the customer experience it must support and the evidence available today.

Avoid this mistake

Hiding a simple price creates friction; publishing a misleading starting price creates a different problem.

Before comparing results, align the scope. Write down what is included, who does the work and which time period matters. If a comparison uses different definitions on either side, resolve that mismatch before interpreting the numbers.

Run a practical evaluation

Map what information buyers need before a conversation and publish the parts that can be stated accurately.

Choose one representative workflow or customer situation. Avoid a demonstration that removes the difficult part of your actual case.
Define the required outcome and the conditions that would make an option unsuitable. Include operational and customer-experience constraints.
Collect evidence under the same scope for both options. Record implementation effort, dependencies and unresolved questions.
Review the result with the people who will operate the choice. A decision that requires unavailable skills or capacity needs a different plan.
Record the choice and a review trigger. New customer needs, product changes or a different scale can justify revisiting it.

Document the decision

Item	Your evidence
Customer task	What the choice must help someone accomplish
Required capability	The condition that cannot be compromised
Full cost	Money, internal effort and ongoing responsibility
Main risk	What could make the choice fail in your context
Validation	The observation or test supporting the decision
Review trigger	The change that would justify another evaluation

Continue the evaluation

Browse the comparison library and working resources for related decisions.

Apply public pricing vs contact sales in a working review

Choose a representative customer task and compare both options under the same constraints. Keep required capabilities separate from preferences, and document the cost of moving as well as the cost of staying. An attractive feature does not resolve a missing requirement. Leave unknown evidence visible and identify the test that could change the choice.

For this topic, involve the pricing owner with finance, product and customer-facing input and work from offer scope, charging unit and scenario assumptions. The relevant unit is a defined customer segment and comparable commercial offer. State the question the review should resolve before choosing a chart, an asset or a tool. If participants disagree about the unit or scope, resolve that disagreement before combining their evidence.

Evidence to prepare

A price is meaningful only with its package, quantity, terms and serving requirements. Test whether buyers can predict the bill and whether the charging unit supports useful adoption. Keep willingness-to-pay statements separate from observed purchasing behavior.

Review field	What to record
Topic	Public pricing vs contact sales
Decision	The specific action this explanation should help you choose
Working evidence	offer scope, charging unit and scenario assumptions
Unit and scope	a defined customer segment and comparable commercial offer
Responsible people	pricing owner with finance, product and customer-facing input
Remaining uncertainty	The missing fact that could change the decision

Two situations that can change the interpretation

When packaging blocks a new customer’s first useful task

An integration promoted in onboarding should not unexpectedly require a different plan unless that requirement was clearly disclosed.

Use this check: Test the advertised first-use path against actual package permissions and dependencies. Do not hide required conditions in a remote comparison footnote.

The focused diagnostic guide provides the correction process and a working evidence sheet.

When a price-change message omits the available choices

A clear announcement distinguishes a plan migration from a pure rate change and explains where account-specific questions belong.

Use this check: Compare the message with the approved commercial change and support process. Do not imply contractual rights or cancellation terms beyond the customer’s actual agreement.

The focused diagnostic guide provides the correction process and a working evidence sheet.

Record the decision and the limit

An account may object to price because the required integration or implementation support is unclear. Discounting without resolving that concern can create a lower-priced failure. Compare the complete offer and the customer’s actual alternatives before treating every objection as a request for a concession.

Keep the conclusion beside the evidence that supports it. Record what the team will do, who owns the next action and which event or date will trigger a review. If the underlying definition, audience or product behavior changes, revisit the conclusion rather than assuming the old result still applies. A clear limit is useful information; it tells the next reader where additional investigation is required.

Use the complete topic collection for related methods and the category field guides when the product’s buying situation or implementation requirements change how the method should be applied.