Revenue Handoff Diagnostic & Structural Audit
Audit revenue team handoffs to identify systemic process failures and implement concrete, data-driven structural fixes.
Customise & copy
Add the context you have. The prompt updates as you work.
Paste raw notes, logs, or examples of failed handoffs between revenue teams.
Provide current definitions of team stages and official handoff criteria.
Select the specific handoff boundary being analyzed.
Live prompt
3 fieldsYou are an expert Revenue Operations (RevOps) consultant. Analyze the provided revenue team handoff records to diagnose systemic process failures versus isolated execution errors, and specify high-impact structural fixes. Context & Inputs: - Handoff Records & Escalations: {{handoff_notes}} - Stage Definitions & Criteria: {{stage_definitions}} - Team Context: SDR to Account Executive Perform a rigorous operational audit and output a structured diagnostic report using the following format: 1. DIAGNOSTIC SUMMARY - Distinguish clearly between systemic process design flaws and isolated human execution errors found in the data. 2. PRIORITIZED HANDOFF FAILURES - Categorize each failure by type: Information Gap, Ownership Ambiguity, Timing Delay, Qualification Mismatch, or Process Friction. - Back up each category with concrete evidence from the provided records. 3. ACTIONABLE STRUCTURAL RECOMMENDATIONS - Specify exact required fields or data points that must be captured. - Define strict, measurable SLAs for handoff completion and response times. - Clarify precise ownership rules and transition triggers between teams (e.g., Marketing, SDR, AE, Customer Success). Constraints: - Do not propose vague advice like 'improve communication'. Provide concrete rules, fields, and SLAs. - Do not invent metrics or operational data not supported by the input.
Proof before you use it
A real example
Tested on gemini-3.1-flash-lite on 2026-09-06
{
"team_context": "SDR to Account Executive",
"handoff_notes": "Ticket #402: AE rejected 3 leads this week from SDR team stating no budget was established despite form fill. Ticket #415: Prospect attended demo but SDR failed to log the primary pain point in CRM, forcing AE to restart discovery. Average time from SQL qualification to first AE touchpoint is 48 hours.",
"stage_definitions": "SDR Stage: Qualifies inbound leads for BANT (Budget, Authority, Need, Timeline). Handoff criteria: Booked calendar invite with meeting notes populated in CRM custom fields."
}A small ritual that works
How to use it
- 01Paste your raw handoff logs or escalation notes into the handoff_notes field.
- 02Input your current stage definitions and criteria to establish the baseline.
- 03Select the specific team transition boundary you are auditing.
- 04Review the generated diagnostic report to implement the recommended fields and SLAs.
Why it works
The prompt forces a structured operational audit by dividing the analysis into distinct, logical buckets: a diagnostic summary distinguishing design flaws from execution errors, a categorized table of handoff failures with concrete evidence, and prescriptive, granular structural recommendations spanning CRM data schemas, strict SLAs, and definitive ownership rules. By demanding specific required fields, explicit transition triggers, and measurable response times, it prevents vague advice like 'improve communication' and drives teams toward repeatable, inspectable revenue operations.
Where it fails
INSUFFICIENT_EVIDENCE
Customisation tips
Adapt the selected team context dropdown values and ensure your stage definitions accurately reflect your current CRM setup before pasting raw notes. The categories of handoff failures (Information Gap, Ownership Ambiguity, Timing Delay, Qualification Mismatch, Process Friction) can be selectively emphasized depending on whether your bottleneck occurs early in the funnel (Marketing/SDR) or late in the lifecycle (AE/CS).
Watch-outs
- Avoid making unsupported inferences about system capabilities, CRM absence, or high rejection volumes if the raw data only shows a handful of isolated records.
- Do not introduce arbitrary performance metrics, thresholds, or SLA targets without grounding them in an existing operational baseline from your input data.
- Ensure that recommended structural changes—such as shifting stage triggers away from calendar invites—do not conflict with existing stakeholder agreements or core workflow definitions.
- Be careful not to propose complex automations, commission gating, or cross-functional escalations (like Legal/Ops involvement) unless the team context and evidence support that those functions exist.
Works in
Was this useful?
Submit your variation
If your version helps, it may be published with your name and a link back to you.
Related prompts
Want to make AI useful across your team? Explore Atul's training.