R3 — For customer-facing reporting, default to the lightest delivery first: scheduled PDF or shared reporting link; embed only when the four-condition narrow band holds

Rule: For customer-facing reporting, default to a scheduled PDF / email or a shared reporting link. Move to embedded only when ALL of: recurring clients, frequently-updating data, real retention/differentiation case, capacity to maintain (Customer-facing embedded dashboard earns its keep in a NARROW BAND: recurring clients + frequently-updating data-rich results + retention/differentiation lever + support deflection).

Threshold: roughly 20+ client tenants or analytics-as-product → evaluate an embedded-analytics platform (Luzmo / Explo) before a custom build. Reserve custom-and-embedded for when analytics is core differentiation AND you have ≥1-2 engineers to own it permanently (Custom-embedded 3-year TCO converges on $300K-$630K (multiple, mostly vendor sources) with 20-30% annual maintenance; hidden costs are multi-tenancy/RLS, performance at scale, perpetual maintenance).

Why: AgencyAnalytics benchmark — a majority of agencies still send static reports to clients while relying on live dashboards internally; live unfinal numbers invite client misinterpretation — even agencies, the segment most-likely to deliver real-time analytics, still default to static reports. Live, not-yet-final numbers invite client misinterpretation. Custom-embedded TCO ($300K-$630K + 20-30%/yr) only earns its place when analytics IS the product.

How to apply:

• Start with PDF; progress only when the four-condition gate clearly holds.
• For embedded vs custom: default to the platform if engineering capacity is uncertain.
• Mirror calculator brief's R2 — Default to a directional range, ungated, with a loud "this is a ballpark" — not a precise gated quote and portal brief's R1 — Default to BUY, not build, for client portals; recommend a horizontal platform ($19-79/mo) or the bundled vertical-SaaS portal — lightest delivery wins by default.