Problem Statement
The goal is to automate a weekly Revenue Operations briefing that analyzes recent performance data, identifies meaningful changes in key metrics, and provides actionable insights. The workflow compares week‑over‑week dashboard exports, generates a narrative explaining the drivers behind changes, and produces a prioritized action plan with owners and validation methods. This ensures consistent, rigorous visibility into revenue performance without manual analysis.
Steps
Ingest weekly data
INGESTCollect the past 7–14 days of dashboard exports including pipeline changes, bookings, conversion rates, funnel stage velocity, and SLA adherence. Parse files and unify fields across weeks.
Retrieve contextual events
EXECUTEPull in notable events such as product launches, outages, pricing changes, or strategy shifts. These contextual items help interpret metric movements.
Compute deltas and statistical relevance
EXECUTECalculate week‑over‑week changes, apply significance heuristics, and isolate movements that are likely operationally meaningful rather than noise.
Generate narrative and root‑cause hypotheses
EXECUTEDraft a "What changed?" narrative summarizing key movements and propose 3–7 likely root‑cause candidates for each shift, ranked by likelihood.
Validate and structure final briefing
EXECUTEEnsure completeness of sections—Executive Summary, Metrics & Drivers Table, and Actions & Instrumentation Updates—and check for consistency and alignment with business context.
Prompt Configurations
Weekly RevOps briefing generator
You are a Revenue Operations weekly briefing assistant. Analyze the provided weekly metrics dataset and contextual events.\n\nInstructions:\n- Compute week-over-week deltas for all metrics.\n- Flag only statistically or operationally meaningful changes; ignore noise.\n- Create a concise Executive Summary with 10 bullets.\n- Create a Metrics & Drivers Table with: metric, WoW delta, driver ranking, and 3–7 root-cause candidates.\n- Generate an Actions & Instrumentation Updates section listing owners, due dates, expected impact, and how to validate impact.\n- Use a professional but concise tone.\n- Do not invent data; rely only on the provided inputs.\n- If data is missing or unclear, explicitly state assumptions.\n\nOutput exactly three sections: Executive Summary → Metrics & Drivers Table → Actions & Instrumentation Updates.
Example Inputs/Outputs
Pipeline export (Week A vs. Week B): New pipeline down 18%, SQL-to-SQO conversion up 7 points, Bookings flat. Context: minor pricing update, two-day CRM outage. Hypothesis: outage may have slowed early-stage creation.
Executive Summary: 10 bullets summarizing key shifts including −18% new pipeline and improved conversion. Metrics & Drivers Table: includes WoW deltas, significance flags, and root-cause candidates such as CRM outage impact, pricing update effect, rep behavior changes. Actions & Instrumentation Updates: recommends investigating stage-entry delays (Owner: Sales Ops, Due: Friday), validating conversion uplift with cohort analysis, and adding outage-exclusion filters to dashboards.