Confirmed gaps per 100
Tax-lead-confirmed unsupported exemptions, separated into known alerts and previously unidentified gaps.
Read the methodA proposed retrospective review of 100 historical exempt sales, their evidence, and your existing vendor coverage. One state. One selected workflow.
Research-stage concept · illustrative product preview
Replace dense grid with “100 sales / one state / one workflow.”
Human review requiredThese numbers define proposed scope, not measured results. Reconciliation testing additionally needs agreed monthly export populations.
| Agreement | What needs to be explicit |
|---|---|
| Permission | Who can grant access; which seller, entity, state, period and files are included. |
| Review | A named tax owner and the source/form assumptions to inspect. |
| Baseline | Current ECM/tax-engine vendor, modules, alerts, review time and known gaps. |
| Data handling | Approved transfer, least-privilege access, retention and deletion terms. |
| Outreach | Separately approved scripts and recipients; not included in sample-review consent. |
| Commercial scope | Selected module, proposed deliverable, budget owner and written pilot decision. |
Tax-lead-confirmed unsupported exemptions, separated into known alerts and previously unidentified gaps.
Read the methodTrack review time, false positives, omissions and the practical work needed to resolve a true gap.
A conversation or click is not a purchase. Record scope, tax-owner sign-off and a signed, funded pilot.
Proceed only with incremental findings beyond current coverage, tax-owner sign-off and a paid audit-prep commitment.
Stop when the incumbent resolves the same issue at lower total review cost. Demo polish is not evidence of demand.
The initial conversation needs business context only. No transaction files, certificates or customer details.