The data-model test

The data-model test is a two-week, time-boxed proof run before buying or building quoting software: take your most difficult manufacturer, two product series, one historical price list and one current update — photos, options, and missing values included — and push them through the candidate system's data model. The acceptance test is what comes out: a clean export you can open elsewhere, uncertain and missing values surfaced rather than hidden, and a reversal, with the update undone.

Why it matters

An imposed data model that does not fit the catalog is one of the most reliable ways a quoting-software decision goes wrong — and one of the earliest and most useful indicators of category fit a buyer can get. A model that fits shows it in two weeks. A model that does not shows it in month three of a rollout, at a very different price.

Common confusion

The test is not a demo — a demo runs on the vendor's clean data and always passes. It is also not full due diligence: two weeks will not show scalability, complete integrations, or governance. It tests one thing, the thing that fails most expensively — whether your data fits their model.

Where we use it

Step three of the calculation in Enterprise CPQ vs custom — and it applies unchanged to an ERP's built-in offer module.