SaaS Revenue Leak Starter

The problem

SaaS companies often lose revenue because pricing, usage metering, and contract entitlements drift out of sync. It is difficult to pinpoint where the leak happens without manually auditing messy logs, invoices, and support records.

What it does

• Identifies discrepancies between contract entitlements and actual product usage snapshots.
• Traces commercial signals back to specific evidence to confirm or reject leakage hypotheses.
• Maps ownership and date-range gaps across billing, support, and renewal records.
• Categorizes risks by customer impact and reversibility before any changes are made.
• Generates a structured specialist handoff map for targeted remediation.

Why this beats prompting it yourself

General prompts often hallucinate revenue loss totals or suggest risky billing changes. This skill enforces a strict diagnostic discipline, separating supplied facts from hypotheses and ensuring you never alter customer state or invent financial figures.

Use cases

• Auditing support exceptions that are being delivered without corresponding price increases.
• Identifying legacy discounts and credits that lack clear ownership or expiration dates.
• Reconciling usage definitions against actual invoice events to find metering errors.
• Routing complex billing disputes to the correct internal specialist for resolution.

Known limitations

Does not perform external actions, change billing state, or calculate total dollar losses. Requires sanitized commercial and operational data to be supplied by the user.