2026-04-01 API; runs are created and read in the dashboard under Revenue Assurance. See How Alguna Works for the usage and subscription model it relies on.
What it detects
Each finding is an opportunity tracked through open → acknowledged → resolved, so the same gap is not rediscovered on every run.
Quantifying an opportunity
A run only knows what was used. To value it, attach a pricing model to each product in the run; Revenue Assurance then calculates the opportunity cost per customer and in aggregate. Use the price you would actually charge — the same pricing models as the catalogue.Running a scan
1
Create a run
Open Revenue Assurance, click New run, name it, and pick the products and time window to scan.
2
Let it complete
Customers are processed in the background and results stream in as they are found.
3
Attach pricing
Attach a pricing model to each product in the run to see the total opportunity.
4
Export and act
Export the run to CSV and hand opportunities to the team that will close them: a subscription change, a one-off invoice for the overage, or a new subscription.
Who uses it
- RevOps and finance — a defensible figure for uncaptured revenue.
- Billing operators — an audit of subscription coverage that does not depend on spreadsheets.
- CS and account management — every uncovered-usage signal is an expansion conversation with evidence attached.
Permissions
Access is gated by two permissions: one to view runs and opportunities and export CSVs, and one to manage them — create and update runs and configure pricing. Ask a workspace admin to grant them if you do not see the feature.Related
Revenue Recognition
Recognised and deferred revenue from what was billed.
Usage metering quick start
Define a metric and send events.