Revenue leak scan

A revenue leak is open work with no customer evidence behind it, or a paying account asking for something that never reached the roadmap. Both are invisible while the request lives in a support tool and the revenue lives in billing - nothing joins them, so the backlog gets ranked by who asked loudest rather than by what the request is worth.

It matches the words in each open work item against the words in each customer request, then attaches the MRR of the accounts behind the matching requests. You get three lists: work ranked by the revenue waiting on it, open work nobody asked for, and requests from paying accounts that are not on the board.

No. There is no signup, no card, and no email gate. Paste your rows, get the report. Nothing you paste is stored, logged, or sent anywhere - the join runs in memory and the response is not cached.

It is a keyword join over whatever you paste, so it is a one-shot approximation, not attribution. It will miss a request phrased in completely different words from the ticket, and it cannot see anything you did not paste. It is useful for the same reason a smoke test is useful: if it finds revenue attached to work you had ranked low, that finding is real.