Dashboard rot: data sources change schemas, metric definitions drift across departments, organizational attention wanes; custom/embedded builds carry the heaviest ~20-30%/yr maintenance burden

Claim: Dashboards are not build-once assets. Data sources change schemas; metric definitions drift across departments; organizational attention wanes — dashboards spun up for one initiative quietly go unused (the "org attention grave markers" framing). Custom-and-embedded builds carry the heaviest burden: every schema change propagates into the analytics tenancy layer; vendors estimate ~20-30% of original build effort recurs annually as maintenance.

Source: Vendor synthesis; consistent with Fivetran 2026 Enterprise Data Infrastructure Benchmark — data teams spend 53% of engineering time on maintenance; $2.2M/yr/team on pipeline upkeep at enterprise scale (data-pipeline maintenance) and Schema drift is the single largest data-pipeline maintenance category — ~31% of maintenance time per Fivetran 2026 benchmark (schema drift).

Confidence: Industry-consensus.

Why this matters for Candid: Same maintenance-discipline argument as the data-tools brief's R5 — Budget for pipeline maintenance from day one; if the client can't commit to upkeep, rent the managed version instead of building one. Dashboards age out — quarterly audit + archive-30-day-stale discipline is essential.