How to build a feature comparison from supplied product evidence
A feature matrix helps make differences between products visible under a shared set of criteria. It is useful when the criteria and the supporting sources can be reviewed together.
Start with the right material.
- What you provide
- one competitor feature comparison page.
- The intended result
- Export features by plan and preserve qualifiers, exclusions and unknowns.
How the workflow works.
Define each feature precisely and map the supplied claims to it. Distinguish confirmed support, stated limitations and insufficient information instead of using a yes or no value for every uncertain case.
What to check in the result.
Review ambiguous comparisons against the original wording. Similar feature names may describe different behavior, and the matrix should not imply that undocumented functionality has been tested.
Import the CSV with a consistent delimiter and inspect text identifiers, dates and amounts before using spreadsheet totals. Keep the original file available while checking any automatic type conversion.
Learn from the worked example.
The downloadable CSV example uses these columns: Feature, Free, Pro, Enterprise. Compare a complete record with the source before sorting, combining or importing your own output.
The supplied example is illustrative. It is not a recorded run on your data.
Download the example ↓Use it with your own material.
- Open the source you want to work with and activate WebAct on that tab.
- Copy the task from the hero, add any required fields or preferences, and review the proposed actions.
- Compare the first result with your source. Ask for a specific correction or refinement where needed.