RevOpsRevOps Analystadvanced 120 min saved

Revenue Leakage & Audit Engine

Audit CRM and billing data to identify revenue leakage, quantify financial impact, and implement preventative operational guardrails.

Customise & copy

Add the context you have. The prompt updates as you work.

Dataset Text *

Paste the primary commercial, CRM, or billing dataset.

Renewal and Billing Data *

Paste renewal tracking data, dates, statuses, and invoicing records.

Pipeline and Deal Logs *

Paste opportunity pipeline reports or deal registration logs.

Audit Focus *

Select the primary analytical lens for the audit.

Live prompt

4 fields

You are a Revenue Operations and Financial Audit Expert. Analyze the provided commercial data to uncover revenue leakage, separate confirmed leakage from potential risk, quantify impact strictly based on the provided data, and define preventative operational controls.

Dataset / Source Material:
{{dataset_text}}

Historical Renewal & Billing Records:
{{renewal_billing_data}}

Pipeline & Deal Registration Logs:
{{pipeline_logs}}

Specific Audit Focus or Constraints:
Full Pipeline and Billing Audit

Perform a rigorous revenue audit adhering strictly to this structure:
1. Confirmed Revenue Leakage: List concrete instances where revenue was demonstrably lost, underbilled, or dropped based strictly on the input data. Quantify exact financial impact only where underlying data permits calculation.
2. Potential Revenue Risk: Identify pipeline stagnation, unworked opportunities, or discount anomalies that threaten future revenue without mixing them with confirmed losses.
3. Root-Cause Analysis: Identify systemic patterns leading to the observed leakage or risk.
4. Preventative Operational Controls: Provide specific, implementable system guardrails or operational processes assigned to each finding to prevent recurrence.

Do not invent financial figures, estimate missing data, or use generic best practices. Rely exclusively on the provided text.

Proof before you use it

A real example

Tested on gemini-3.1-flash-lite on 2026-09-06

{
  "audit_focus": "Discount and Pricing Anomalies Only",
  "dataset_text": "SaaS Enterprise Tier: 45 accounts active. Account Omega ownership log shows unassigned status for 60 days following rep departure.",
  "pipeline_logs": "Q3 Expansion Pipeline: 12 enterprise upsell opportunities marked as Closed-Lost due to missed SLA response times.",
  "renewal_billing_data": "Billing record #8842: Tier 2 SKU billed at $500/mo instead of contract rate $1,200/mo over a 6-month billing cycle. Total recorded invoice sum: $3,000."
}

A small ritual that works

How to use it

01Paste your CRM exports, renewal records, and pipeline logs into the designated fields.
02Select the specific audit focus to narrow the analytical scope.
03Execute the prompt to generate a structured report of confirmed leakage and potential risks.
04Review the suggested operational controls to patch systemic process gaps.

Why it works

The prompt enforces structural discipline by requiring a strict separation between confirmed revenue leakage and potential risk, anchored entirely to provided datasets. It prevents hallucinations by prohibiting the invention of financial figures or generic best practices, forcing the model to operate strictly within the supplied data boundaries.

Where it fails

INSUFFICIENT_EVIDENCE

Customisation tips

Modify the 'audit_focus' select options to align with specific organizational audit targets, such as expansion leakage, mid-term co-terming adjustments, or multi-year discount step-downs.

Watch-outs

Ensure input data contains explicit financial figures or SKU records, otherwise the model will lack the necessary baseline to quantify financial impact.
Watch for attempts to invent metrics or arbitrary timelines when analyzing pipeline stagnation or root-cause failures.
Verify that the chosen audit focus matches the supplied dataset variables to prevent out-of-scope analysis.