R5 — Budget for pipeline maintenance from day one; if the client can't commit to upkeep, rent the managed version instead of building one

Rule: Every recommended data pipeline build must include a maintenance budget and a named owner from day one. If the client cannot commit to upkeep, recommend a managed-vendor version instead of an in-house build.

Why: Maintenance is the dominant lifecycle cost (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); schema drift is the dominant break-cause (Schema drift is the single largest data-pipeline maintenance category — ~31% of maintenance time per Fivetran 2026 benchmark). At enterprise scale that is >50% of engineering time. At SMB scale it can quietly become you, the agency, fixing it forever — or worse, the client's critical workflow silently going stale. The argument generalises to calculators (R4 — Commit to a documented input-refresh schedule before shipping any customer-facing calculator; if you won't, don't ship it).

How to apply:

• Scope-document includes maintenance owner, cadence, escalation path.
• Default to stable, low-drift sources (FRED / Valet / GTFS / public-domain feeds) wherever possible.
• If upkeep is the dealbreaker, recommend the managed-vendor route and accept the lock-in tradeoff explicitly.