Competitive Conversation Guide
A fictional sales comparison guide for connecting a customer’s priorities to verified evidence, careful wording, and clear follow-up when a distinction still needs checking.
Every employee gets a seat — priced per employee in Communications & Intranet, quoted with this template ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
Built for: Business software sales · Technology and IT services · Professional services
Overview
The Competitive Conversation Guide is a fictional worked example for sales teams comparing options in the context of a customer’s priorities. It opens with a decision rule: compare only relevant points that can be substantiated, and say you will check when a distinction is not verified. Its Atlas and Beacon scenario shows how to move from a customer need—a shared view of open service requests—to an illustrative distinction, an evidence check, and careful customer-facing wording. The product details are explicitly fictional, not claims about real products.
Use the page to prepare for or guide a conversation where a buyer has a priority, an existing workflow, or a question about how options differ. Its discovery prompts help establish desired outcomes, constraints, users, and handoffs before making a comparison. The adaptation scenarios cover unclear priorities and unverified claims; the closing section explains what to record, when to recheck, who owns the guide, and where corrections go. Together, these sections support a practical follow-up instead of an unsupported answer.
This page is not an approved product battlecard, a source of current product facts, or a substitute for your organization’s commercial or legal review. Do not reuse the fictional Atlas and Beacon statements as real-world claims. Before a live comparison, verify the current product and proposal scope against approved evidence, preserve relevant limits, and follow the team's commercial workflow. If customer needs do not match the example, return to discovery rather than forcing its conclusion.
Standards & compliance context
- Use current, approved evidence for product comparisons and follow your organization’s applicable commercial and legal review requirements; the page does not establish compliance with a particular law.
- Treat Atlas, Beacon, and all associated product details as fictional sample content, not as evidence or approved claims about real products.
- Keep customer-relevant scope, limitations, and uncertainty alongside any comparison so the wording does not imply more than the evidence supports.
- Maintain a clear heading hierarchy and readable comparison content so sales users can access the guide, including when using assistive technology.
General regulatory context for orientation only — verify current requirements with counsel or the relevant agency before relying on this template for compliance.
What's inside this template
Start with the customer's priorities
Establish the customer’s outcome and constraints before drawing a comparison, and treat the products on this page as fictional examples.
-
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
See how a customer priority, an illustrative difference, an evidence check, and careful wording fit together without turning sample content into a real product claim.
-
Illustrative only. Validate product-specific details against current, approved evidence before using a comparison with a customer. Customer priority A regional team wants a shared view of open service requests. The team currently reviews requests in separate local reports. Illustrative distinction In this fictional scenario, the approved proposal describes a consolidated request view. In this fictional scenario, the approved proposal describes separate local reports. Evidence to check Confirm the current proposal scope and the team workflow it covers. Confirm the current proposal scope and whether local reports can be combined. Careful wording “For the shared view you described, our proposal includes a consolidated request view; I can confirm the scope against your workflow.” “The example describes separate local reports; let's verify whether that matches your current setup.”
Adapt the comparison to the conversation
Choose a response based on what the customer needs and what the available evidence actually establishes.
-
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
Use these answers to handle uncertainty, changed information, and questions about describing another option fairly.
-
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
Record what was checked, when it was checked, and the customer need behind the comparison, then recheck when relevant details change.
-
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.
How to use this template
- Read the fictional scenario and replace its assumptions with the customer's stated outcome, constraints, and existing workflow.
- Identify the specific distinction that matters to the customer and confirm its scope using current, approved evidence.
- If the evidence does not establish the distinction, record the question and customer requirement in the approved commercial workflow without presenting a claim.
- Explain verified differences in neutral language, state relevant limits, and check that the wording reflects the evidence.
- After the conversation, record the evidence source and date checked, then route unresolved questions to the responsible product or commercial owner.
- Recheck the comparison when the product, commercial terms, proposal scope, or customer requirements change, and route guide corrections through the responsible Business Operations role.
Best practices
- Ask what outcome the customer wants and how they will judge fit before comparing product features.
- Tie each comparison point to a stated customer priority rather than listing differences without context.
- Check that approved evidence establishes the exact product and proposal scope you plan to describe.
- Use neutral language that describes scope and limitations instead of dismissive labels or broad superiority claims.
- Say you will verify a distinction when the evidence is missing, unclear, or potentially out of date.
- Record the customer requirement, evidence source, and date checked together in the approved commercial workflow.
- Return to discovery when the customer's needs do not match the fictional example instead of recommending an option by analogy.
What this template typically catches
Issues teams running this template most often surface in practice:
Common use cases
Frequently asked questions
Who should use this guide, and what conversations does it cover?
Sales teams can use it when a customer is weighing options and asks how they differ. It is designed for discovery-led conversations where the team can check product-specific details against current, approved evidence. The Atlas and Beacon scenario is fictional and demonstrates a method, not a real product comparison.
How often should a comparison be checked?
Check the evidence before using a product-specific distinction with a customer. Recheck when products, commercial terms, proposal scope, or customer requirements change. The example does not set a calendar review interval; Business Operations reviews the guide when comparison practices or evidence arrangements change.
Who owns the guide and verifies an open claim?
Business Operations owns the guide and handles corrections through the responsible Business Operations role. For a specific unverified distinction, seek current approved evidence from the responsible product or commercial owner. Keep the customer requirement, the evidence source, and the date checked together in the approved commercial workflow.
Does this guide meet a particular sales or advertising regulation?
The page does not claim compliance with a specific law or regulation. Its practical safeguard is to compare only customer-relevant points that can be substantiated, state limits, and avoid unsupported claims about another option. Follow your organization’s applicable legal, advertising, and commercial review requirements.
What should I do when I cannot verify a distinction?
Do not present it as fact or fill the gap with an assumption. Tell the customer you will check the current approved information, record the question in the commercial workflow, and ask the responsible product or commercial owner to verify it. Leave the claim open if the source does not establish the distinction.
How do I adapt the example when a customer's needs differ?
Start with the customer's desired outcome, constraints, and existing workflow rather than copying the Atlas and Beacon rows. Identify who uses the workflow and what handoffs or limits matter, then connect only verified evidence to those priorities. If the priorities are unclear, continue discovery instead of declaring a winner.
Does the template connect to a CRM or product evidence system?
The page describes recording the claim or question, evidence source, date checked, and relevant customer requirement in your team's approved commercial workflow. It does not specify or configure a CRM, evidence repository, or automatic integration. Use the systems and handoff your organization has approved.
How should a team roll this guide out?
Share the page with sales staff who compare options, and walk through its fictional table as a practice example rather than approved product content. Have users rehearse discovery questions, careful wording, and the handoff for claims that need verification. Confirm the applicable evidence sources and commercial workflow before using real comparisons.
How is this better than an ad-hoc comparison?
The guide provides a repeatable sequence: establish customer priorities, check evidence and scope, use careful wording, and record unresolved questions for follow-up. That makes uncertainty visible instead of turning assumptions into claims. It still depends on current approved evidence and does not replace product, commercial, or legal review.
Related templates
Go deeper on the topic
-
A modern intranet is a specific surface — typically the home-base destination where employees get company news, find policies, and access key apps. A digital...
Ready to use this template?
Every employee gets a seat. Request pricing for Communications & Intranet and we quote into a workspace with Competitive Conversation Guide ready.
Rolled out to every employee at AutoZone (125,000), PetSmart (50,000+), A.S. Watson and Raley's (20,000) — and at larger retailers we are not permitted to name.
