Three scenarios
Each case below ran through PreDealCheck with synthetic customer data. The engine recomputed claims from source tables and returned one of four states. All data is synthetic.
These three already ran; nothing on this page is interactive. The live check takes any customer table and any claim, and answers in your browser with the rows attached.
Scenario 1: both claims CONTRADICTED
A marketplace seller claims 45 active customers and USD 156,000 annualized recurring revenue. Recomputing both from the source table gives different figures, so both return CONTRADICTED.
| Claim | Stated | Found | Gap | Status |
|---|---|---|---|---|
| Active customers | 45 | 35 | −10 (22%) | CONTRADICTED |
| Annual recurring revenue | USD 156,000 | USD 134,460 | −USD 21,540 (14%) | CONTRADICTED |
The customer table held 40 rows. Rows with status "paused" were excluded as unrecognized. From the 35 customers with explicit live status, the engine summed monthly recurring revenue and annualized it. The arithmetic is transparent: row numbers, source hash, and the rule applied are attached to each finding for verification.
Scenario 2: both claims SUPPORTED
A seller reports 18 active customers and EUR 40,080 annual recurring revenue. Recomputing both from the source table reproduces the claimed figures exactly, so both return SUPPORTED.
| Claim | Stated | Found | Gap | Status |
|---|---|---|---|---|
| Active customers | 18 | 18 | 0 | SUPPORTED |
| Annual recurring revenue | EUR 40,080 | EUR 40,080 | 0 | SUPPORTED |
When table rows reproduce stated claims exactly, both return SUPPORTED on the first pass. The engine distinguished customers with explicit live status, summed fixed recurring monthly rates, and annualized the result. Byte-identical match to the claim.
Scenario 3: DEFINITION_MISMATCH and UNVERIFIED
A marketplace operator states 28 customers and claims 3 churned in Q2 2026. The customer count is valid; the churn claim cannot be verified from source data.
| Claim | Stated | Found | Status |
|---|---|---|---|
| Active customers | 28 | 28 | DEFINITION_MISMATCH |
| Churn in Q2 2026 | 3 customers | — | UNVERIFIED |
The customer count matched. The churn claim returned UNVERIFIED because PreDealCheck does not compute churn from a snapshot. Period churn requires cohort data. The engine reported the limit instead of guessing.
Run one of your own
These three cases are fixed. The live check on the home page takes any customer table and any claim, and shows the rows behind the answer.