Start with the customer's priorities
A practical guide for sales teams comparing options in customer conversations.
Decision rule: compare only customer-relevant points you can substantiate. If a distinction is not verified, say you will check it rather than presenting it as fact.
Fictional example: Northstar Systems is considering two fictional products, Atlas and Beacon, for a regional service team. The product details below illustrate how to structure a fair comparison; they are not real product or competitor claims.
First, clarify the customer's desired outcome, constraints, and existing workflow. Then connect verified evidence to those needs, state any limits, and agree on what to verify next.
Worked example: compare the relevant distinction
Illustrative only. Validate product-specific details against current, approved evidence before using a comparison with a customer.
- Atlas (fictional):
- A regional team wants a shared view of open service requests.
- Beacon (fictional):
- The team currently reviews requests in separate local reports.
- Atlas (fictional):
- In this fictional scenario, the approved proposal describes a consolidated request view.
- Beacon (fictional):
- In this fictional scenario, the approved proposal describes separate local reports.
- Atlas (fictional):
- Confirm the current proposal scope and the team workflow it covers.
- Beacon (fictional):
- Confirm the current proposal scope and whether local reports can be combined.
- Atlas (fictional):
- “For the shared view you described, our proposal includes a consolidated request view; I can confirm the scope against your workflow.”
- Beacon (fictional):
- “The example describes separate local reports; let's verify whether that matches your current setup.”
Adapt the comparison to the conversation
Use discovery to establish what matters before drawing a conclusion.
- The buyer names a clear priority Ask what outcome they need and how they will judge fit. Compare only the verified points that address that priority, and state the scope or limitation alongside the distinction.
- The buyer has an existing workflow Ask who uses it, what handoffs it involves, and which constraint matters most. Separate what the team has confirmed from what still needs review.
- The buyer's priority is unclear Do not declare a winner. Ask which outcome matters most and what would make a change worthwhile; continue discovery before comparing options.
- A requested distinction is not verified Name the uncertainty, avoid a comparative claim, and take the question to the responsible product or commercial owner for current approved evidence.
Questions that come up
Keep the conversation useful when evidence, scope, or timing is uncertain.
What should I say if I cannot substantiate a claim?
Do not present it as a fact. Say, “I don't want to guess about that distinction. I'll check the current approved information and follow up through our commercial process.” Record the question and seek evidence from the responsible product or commercial owner.
How do I describe a difference without disparaging another option?
Describe the customer's stated need, the verified scope of each option, and any relevant limits. Avoid dismissive labels, broad superiority claims, and statements about another product that are not supported by current evidence.
What if the information may have changed?
Treat it as unverified until checked. Reconfirm against current approved evidence when a product, commercial term, proposal scope, or customer requirement changes.
What if the customer's needs do not match the example?
Use the example only as a comparison method, not as a recommendation. Return to the customer's priorities and verify the relevant distinctions for their situation before drawing a conclusion.
Check the evidence before and after the conversation
In your team's approved commercial workflow, record the specific claim or question, the evidence source checked, and the date checked. Keep the customer requirement that makes the distinction relevant with the note.
- Recheck when products, commercial terms, proposal scope, or customer requirements change.
- If a source does not establish the distinction, leave the claim open and ask the responsible product or commercial owner to verify it.
- Business Operations owns this guide. Review it when comparison practices or approved evidence arrangements change; route corrections through the responsible Business Operations role.