Evaluate marketing-science software without unverified vendor rankings

A software comparison is useful only when it starts from the decisions the organisation must make. It separates declared capability, capability demonstrated on a comparable case and capability required in the target operating context. This page does not rank vendors.

Define the decision before the tool

Specify the decisions to support, the users, the data perimeter, the required frequency and the error that would be costly. Distinguish collection, modelling, validation, scenarios, governance, export and exit cost. A long feature list cannot replace that scope.

Test the same protocol for every candidate

Use a dated, reproducible case with the same inputs, assumptions and expected outputs. Check data ingestion, transformations, permissions, calculation trace, uncertainty display, scenario controls, export and recovery. Record version, configuration, runtime and failed tests as well as successful ones.

Compare evidence rather than promises

Classify every statement as declared, observed in a controlled demonstration, verified against an artefact, or not verified. A polished interface, a benchmark from another context or an automated recommendation does not prove that the system identifies a causal effect or improves a decision.

Decide with reversibility in view

Assess implementation effort, integration, training, data ownership, portability, auditability, contractual conditions and the cost of leaving. Prefer a limited pilot when critical evidence is missing; do not turn an initial demonstration into a production-wide commitment.

Limits

No generic comparison establishes the value of a tool for every organisation. Results depend on the data, governance, skills, operating process and decision context. Re-run the protocol whenever the version, model, data perimeter or intended decision changes.