Problem Statement
Sales and marketing teams need clear visibility into pipeline hygiene issues that reduce conversion rates and forecasting accuracy. The workflow analyzes CRM opportunity and lead data to detect leakage points, SLA breaches, and routing failures. It then recommends rule changes and provides a prioritized cleanup runbook for operations teams.
Steps
Ingest Pipeline Data
INGESTParse the provided CSV export of opportunities and leads, normalizing field names, dates, IDs, and stage labels. Identify required attributes such as owner, lead source, timestamps, and account identifiers.
Retrieve Routing and SLA Rules
EXECUTELoad or parse the provided stage definitions, routing rules, SLA targets, and known failure modes. These definitions will guide leakage detection and rule-gap analysis.
Generate Leakage and Hygiene Analysis
EXECUTEApply logic to detect stalled opportunities, missing mandatory fields, duplicate accounts, invalid or unmapped lead sources, and SLA breaches. Summarize issues into a structured leakage dashboard.
Generate Rule Change Recommendations
EXECUTEUsing the detected leakage patterns, propose routing rule improvements and SLA refinements. Provide rationale, expected impact, and identify which rules have the highest urgency.
Validate and Prioritize Cleanup Plan
EXECUTEDraft a cleanup runbook including filters, ownership, and a definition of done. Validate consistency and ensure remediation items are objective, measurable, and actionable.
Prompt Configurations
Cleanup runbook drafting
Generate a prioritized cleanup runbook. For each remediation item, list: query/filter needed to identify the records, recommended owner (e.g., SDR manager, CRM admin), and definition of done. Make the plan actionable, measurable, and easy for an operations team to execute. Use only issues previously identified; do not fabricate new categories.
Leakage detection and hygiene report
You are an expert RevOps pipeline hygiene analyst. Using the provided dataset and rule definitions, generate a leakage dashboard. Follow this structure: 1) stalled stages (with thresholds), 2) missing fields, 3) duplicate accounts or contacts, 4) broken or unmapped lead sources, and 5) SLA breaches. Provide counts, examples, and severity levels. Do not invent records—only summarize what is present in the input. Tone should be analytical and operations-focused.
Routing and SLA rule recommendations
You are a RevOps routing architect. Based on the leakage dashboard and rule definitions, propose routing rule changes and SLA adjustments. For each proposal, include: rationale, expected lift, and the specific condition/logic change. Write in a concise, professional tone. Do not introduce fictional rules—only modify or extend the provided routing and SLA framework.
Example Inputs/Outputs
CSV excerpt: opp_id, account, stage, owner, lead_source, last_activity_date, created_date ... Routing rules: inbound leads routed by geography, outbound assigned by segment ... SLA: inbound responded to within 2 hours ... Failure modes: missing owner, unmapped lead sources.
Leakage dashboard: 34 stalled opps in 'Qualification' for >14 days; 62 records missing owner; 12 duplicate accounts; 9 leads with unmapped lead_source='FB_ADS_TEST'. Rule change proposals: tighten inbound routing by adding fallback owner; create mapping for new marketing channels; add SLA exception logic for weekends. Cleanup runbook: filters for stalled opps, assign to SDR manager; query for unmapped sources, assign to marketing ops; definition of done = all records updated and rule logic deployed.