Illustrative Example: A Reconciled Lead-to-Pipeline Report
Synthetic demonstration: a B2B team wants to compare accepted inquiries with qualified pipeline. These definitions illustrate a reporting specification; the numbers are invented examples, not customer results.
Submission metric: distinct accepted inquiry IDs created during the month, excluding spam, internal tests and retries. A submission is not yet a qualified lead. Sales acceptance is a separate dated status with a rejection reason.
Pipeline metric: sum the amounts of distinct eligible deals entering the agreed qualified stage during the month. Specify currency, date and exchange-rate rules. Associate inquiries through contact/company records without counting a deal once per contact.
Reconciliation example: ten accepted inquiries link to three unique qualified deals of €10,000, €20,000 and €30,000. The report must show ten inquiries, three deals and €60,000 of pipeline. Two associated contacts must not double a deal amount. Unassociated inquiries remain visible.
Acceptance checks: compare inquiry/deal IDs with the source extract; test month boundaries, exclusions, duplicate associations and a restricted user role. If inquiry records or stage history are unavailable, address that dependency before promising a native report.














