pipeline_coverage_daily feeds a weekly RevOps dashboard and has broken twice, but the team cannot wait for a full enterprise standard. Minimum viable contract: purpose, grain, critical fields, quality rules, owner, SLA, change notice The common trap is writing a schema-only stub because it feels quick. That would not have prevented the recent breaks, which were caused by a coverage_status meaning change and late refresh, not missing columns. Purpose and consumer Purpose: weekly pipeline-coverage dashboard for RevOps planning. Consumer: RevOps Analytics and Sales leadership. Purpose keeps the contract scoped to the decision it protects. Grain and fields Grain: one row per…
Read the full lesson
Sign up free: one personalized lesson every day, matched to your role and goals.
Already have an account? Sign in