Client Reporting Autopilot
Reduce reporting time while increasing insight quality
Client reporting is often slowed by pulling data from too many platforms, reformatting, and writing commentary from scratch. This recipe produces a reporting pipeline plan: KPI definitions, dashboard layout, insight prompts, and a repeatable narrative template.
INGREDIENTS
PROMPT
Design a client reporting autopilot (SOP + templates). Output: - KPI dictionary (definition, formula, source per metric) - Dashboard outline (pages + charts + filters) - Commentary template ("what happened / why / what's next") - Weekly workflow checklist (who does what, when) - Reusable insight library (common patterns + pre-written explanations) Inputs: - Client type: - Platforms: - KPIs promised: - Reporting frequency: - Biggest reporting bottleneck:
How It Works
This recipe standardizes and automates the parts of reporting that shouldn't be reinvented weekly.
Triggers
- Reporting feels too manual
- Multiple clients/platforms cause copy-paste errors and delays
- You need consistent "what happened / why / next" storytelling
Inputs
- Platforms per client (ads, analytics, email, SEO)
- KPI expectations and definitions
- Client-specific targets and constraints
Outputs
- Reporting SOP (week/month)
- Dashboard spec (pages, filters, performance constraints)
- Commentary template + reusable insight library
Actions / Steps
- Define a KPI dictionary (one definition per metric).
- Choose a minimal dashboard layout (avoid overload).
- Build an insight workflow: anomalies → hypotheses → actions.
- Create a "client-ready narrative" that avoids jargon and explains uncertainty.
Parameters
- Reporting frequency
- KPI set per client tier
- Time budget per report