{"id":1302,"slug":"rule-budget-for-pipeline-maintenance-from-day-one","title":"R5 — Budget for pipeline maintenance from day one; if the client can't commit to upkeep, rent the managed version instead of building one","kind":"rule","scope":"business","status":"current","audiences":["kevin","smb-owner","candid-team"],"topics":["agency-methodology","data-infrastructure","data-pipeline-maintenance"],"reference_body":"**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.\n\n**Why:** Maintenance is the dominant lifecycle cost ([[fivetran-2026-benchmark-53pct-maintenance]]); schema drift is the dominant break-cause ([[schema-drift-31pct-maintenance-fivetran-2026]]). 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 ([[rule-commit-to-input-refresh-or-dont-ship]]).\n\n**How to apply:**\n- Scope-document includes maintenance owner, cadence, escalation path.\n- Default to stable, low-drift sources (FRED / Valet / GTFS / public-domain feeds) wherever possible.\n- If upkeep is the dealbreaker, recommend the managed-vendor route and accept the lock-in tradeoff explicitly.","rationale_body":null,"metadata":null,"links":{"outgoing":[{"slug":"rule-commit-to-input-refresh-or-dont-ship","title":"R4 — Commit to a documented input-refresh schedule before shipping any customer-facing calculator; if you won't, don't ship it","kind":"rule","scope":"business","link_type":"relates-to"},{"slug":"fivetran-2026-benchmark-53pct-maintenance","title":"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","kind":"reference","scope":"business","link_type":"depends-on"},{"slug":"schema-drift-31pct-maintenance-fivetran-2026","title":"Schema drift is the single largest data-pipeline maintenance category — ~31% of maintenance time per Fivetran 2026 benchmark","kind":"reference","scope":"business","link_type":"depends-on"}],"incoming":[{"slug":"research-brief-data-driven-tools-smb-june-2026","title":"Research brief: live data and data-driven tools for SMBs — when it's an edge, when it's overkill (June 2026)","kind":"reference","scope":"business","link_type":"relates-to"},{"slug":"article-data-tools-for-smbs-edge-or-overkill","title":"Article (draft): Before you buy that data tool, ask one question — would your competitor's version look exactly like yours?","kind":"reference","scope":"business","link_type":"relates-to"},{"slug":"rule-treat-data-custody-as-line-item","title":"R4 — Treat data custody as a project line item, not a footnote: PIPEDA consent + MFA + encryption + breach response plan + 24-month breach records all live in scope before launch","kind":"rule","scope":"business","link_type":"relates-to"},{"slug":"rule-budget-20-30pct-annual-maintenance-from-day-one","title":"R4 — Budget 20-30% of build effort annually for maintenance from day one; assign a metric-definitions owner; audit quarterly and archive any dashboard unopened in 30+ days","kind":"rule","scope":"business","link_type":"relates-to"}]},"created_at":"2026-06-20T16:57:38.999Z","updated_at":"2026-06-20T16:57:38.999Z"}