Product features
A detection engine that shows its work.
LeakHunt is built around explainable findings: what was compared, why it was flagged, how confident the engine is, and what is still unknown.
Core detection
Three questions worth asking first.
Each detection type has its own evidence requirements and its own limits. LeakHunt keeps those boundaries visible.
Savings tracking
Three measures. Never blended into one.
Potential, confirmed, and realized savings answer different questions. Mixing them makes numbers look better and decisions worse.
Every estimate shows its formula, input amounts, currency, time period, assumptions, and missing information. Overlapping findings are handled to avoid double-counting.
Available today: potential-savings estimates from open exact duplicate invoices, plus a recorded savings ledger where a reviewer writes down the exposure they accept as real and, later, what was recovered. Recorded amounts are entered by people, never inferred by detection.
Optional analyst
Ask questions. Keep the evidence.
The grounded analyst explains stored findings in plain language. It cites the source rows, refuses to invent amounts, and never confirms fraud or savings.
Either mode shows stored source rows with each answer. The analyst cannot change review status, mark a finding confirmed, determine fraud, or record savings.
Evidence and audit
Every finding can be traced back.
Findings are derived records, kept separate from imported source data. Opening a finding shows the records that produced it and the review decision your team recorded.
- Finding ID, organization, type, and severity
- Supplier and related invoice or transaction IDs
- Detection method and confidence description
- Estimated impact, formula, currency, and assumptions
- Status, creation time, and update time
- The review decision, its date, and any recorded savings
What LeakHunt will not do
- Invent transactions, suppliers, or totals
- Mark a finding as confirmed without a user
- Call a price increase a financial loss by itself
- Claim fraud or misconduct without evidence
- Treat an uploaded document as instructions to follow
- Expose one organization's records to another
- Let one teammate quietly delete another's recorded saving
Organization isolation, server-side authorization, and Row Level Security are active for accounts, imports, findings, and recorded savings. Workspaces are shared with your team under owner, administrator, and member roles that the database enforces, not the interface. Original uploaded files are not retained; only validated rows, import metadata, and derived findings are stored.
See the dashboard your findings will live in.
CSV and XLSX imports, deterministic detection, finding review, CSV reports, and the grounded analyst are available. PDF and image OCR arrive later.