build-client-reportlisted

# /build-client-report — Monthly Client Report > **Purpose.** Build the monthly client report. The artifact that justifies the retainer + drives renewal. Output is signal-dense, attribution-clean, decision-ready. The client reads it in <10 minutes and walks away with: (1) what shipped, (2) what worked, (3) what we're doing next month, (4) what they need to decide. > > **Bar.** A monthly report that doesn't trigger a "good — keep going" reaction is a renewal-at-risk signal. The client should finish the report wanting to forward it to their team, not file it under "too long". ## When to invoke - **Cron — 1st of each month at 10:00 (per active client).** Per `paperclip.manifest.yaml`. - Manually for mid-month "executive update" requests - Required input to renewal conversations (operator pulls last 3 months of reports before any renewal call) - Triggered by client request (rare — most don't ask, but always available) ## Required inputs 1. `client_slug` declared 2. Reporting period (default: previous calendar month; configurable for biweekly or quarterly) 3. Attribution data for the period (LinkedIn analytics, CRM exports, calendar data, third-party tools — whatever the client uses) 4. Offer deliverables spec from `/onboard-client` Step 8 + offer scope from contract 5. Success metrics list (defined in `/onboard-client` Step 8 — the client agreed these are how the engagement is judged) 6. Last 3 months of monthly reports (for trend continuity) 7. `/voice-drift-detector` audit