# Which alternatives belong in a product comparison?

By Sean Everett · October 8, 2026

Define the customer’s task and starting environment before choosing competitors. Separate substitutes from complementary components, compare equivalent offers and keep the depth of evidence visible.

Topics: Competitive analysis · Product strategy · Technology selection

## Begin with the customer’s available choices

Describe the customer, the task and the systems already in place. A team adding a capability to an established platform faces a different choice from a team replacing its entire workflow. State which decision the comparison should support before collecting product names.

GOV.UK’s technology guidance emphasizes understanding user needs and the existing systems a service must work with. Build the comparison around that starting point. Include the work people do before and after using the proposed product, especially handoffs that depend on other tools.

The SBA recommends identifying competition by product or service and market segment, including indirect competitors. Ask which alternatives could satisfy the same need: another product, a managed service, an included capability or continuing the current approach.

## Give each comparator a specific role

Distinguish a complete substitute from a component the customer would use alongside the product. A data provider, a workflow application and a service combining both may occupy different positions in the same customer journey. Explain what each option would replace and what would remain.

For example, comparing an add-on with a full suite requires showing the host platform the add-on needs. Compare the complete arrangement the customer would operate. Keep software, service and hybrid offers distinguishable so their different delivery responsibilities remain visible.

Include an adjacent player when it tests a meaningful future possibility, but identify what would have to change for it to become a usable substitute. Hiring announcements and partnerships can suggest a direction; they leave delivery timing and working capability to be established.

## Set comparison rules before scoring the options

NASA’s decision-analysis guidance distinguishes mandatory criteria from desirable characteristics and asks for criteria that differentiate alternatives. Apply that distinction to customer requirements. Identify genuine prerequisites first, then give the remaining criteria importance that reflects the intended use.

Use explicit capability states such as demonstrated, documented, partial, dependent on another component or unresolved. An unavailable answer should remain unknown. Record the product edition, configuration and evidence date so a company-wide claim does not silently become a product-level checkmark.

Show research depth beside the conclusion. A public-information review and a hands-on evaluation provide different coverage. Preserve important gaps and disagreements, then identify the next check that could change the shortlist. A concise comparison is useful when readers can see why each alternative belongs and what supports its assessment.

## Related reading

- [GOV.UK: Defining user needs](https://www.gov.uk/guidance/define-user-needs)
- [GOV.UK: Choosing technology in its operating context](https://www.gov.uk/service-manual/technology/choosing-technology-an-introduction)
- [SBA: Market research and competitive analysis](https://www.sba.gov/counseling/plan-your-business/)
- [NASA: Decision analysis and alternative selection](https://www.nasa.gov/reference/6-8-decision-analysis/)
- [Evaluating complete platform workflows](https://evergences.com/insights/workflow-based-platform-evaluation/)
- [Related owned product: Jetpack Zero — AI-disruption diligence](https://jetpackzero.com/)

Source: https://evergences.com/insights/competitive-comparator-design/