Reason for every flag
Each opportunity should state why it was identified — for example age, status, missing follow-up, billing state or repeat-customer pattern.
Evidence & methodology
Every recovery opportunity should be explainable.
RevenueFound is designed so a customer can see what triggered a flag, how an estimate was formed, what remains uncertain and what happened after action was taken. The analysis should be auditable rather than a black-box score.
Evidence chain
From business record to action.
1Source
Customer-authorised quotes, invoices, customer records and optional jobs/enquiries provide the raw evidence.
2Normalisation
Records are cleaned and structured so stale, duplicated, incomplete or mismatched data can be identified rather than silently ignored.
3Calculation
Value, recovery probability, urgency and actionability are combined into an expected-recovery and priority view.
4QA + outcome
Customer-facing outputs are QA-cleared, then estimated recovery is kept separate from actual recovered value.
Estimate ≠ outcome
Nominal leakage, probability-weighted expected recovery and actual recovered revenue remain separate fields.
Confidence is visible
Confidence reflects evidence quality, completeness, staleness and exceptions. Weak evidence should reduce confidence rather than disappear.
Priority discipline
Not every dollar deserves the same attention.
P1 — Act now
High-value, relatively actionable opportunities with stronger recovery evidence.
P2 — Recover
Worth active follow-up, but with less urgency or lower confidence than P1.
P3 — Automate
Patterns that may be better solved through process improvement than one-off chasing.
P4 — Ignore
Low-value, weak-evidence or uneconomic items that should not consume scarce time.
Important: recovery probabilities are model estimates, not promises. Actual recovered revenue may be higher, lower or zero.
What improves over time
The model should be judged against real outcomes.
RevenueFound is designed to compare expected recovery with what actually happened after action was taken. That evidence can recalibrate future estimates and reveal recurring leakage patterns. We will not publish success claims or recovery-rate benchmarks until real customer outcomes support them.