Reconcile HubSpot lead-to-revenue attribution with Claude

Write a one-page operating charter for lead-to-revenue attribution classification before exporting any data. State the exact decision this workflow supports: how each opportunity should be classified for sourced, influenced, unattributed, or excluded reporting. Define the in-scope business units, pipelines, regions, date window, record types, and exclusions, then name one analysis owner, one HubSpot data owner, and one final approver. Record the review cadence as monthly and specify where evidence, approvals, and exceptions will be stored. Review the charter with the approver and do not proceed until the scope and decision rights are accepted.

Convert the operating policy into a rule register that can be checked against HubSpot records. Create one row per rule with rule_id, rule_name, business_reason, required_fields, calculation_or_test, pass_condition, exception_code, severity, owner, and policy_version. Start with these minimum checks: every attributed opportunity has at least one associated contact, the qualifying touch occurs before the agreed attribution cutoff, sourced and influenced rules are mutually exclusive where policy requires it, excluded pipeline is coded explicitly, and amount and stage totals reconcile to the approved HubSpot report. Give every rule an example that should pass and an example that should fail so reviewers interpret it consistently. Have the business owner approve the rule register and record any unresolved policy questions before data is scored.