{
  "project_id": "AI-02",
  "title": "Collections",
  "source_model": "finance-hours-v1-2026-10-22/model.json",
  "source_category": "Receivables and collections",
  "scope": "One shared-inbox reply-drafting workflow: one entity, one ERP/customer-record source, five payment/invoice inquiry intents, one language, 100 historical test cases and up to five initial users. Staff approve every reply; disputes escalate. No autonomous sending, credit decisions, cash application or payment changes.",
  "basis": "Existing working judgment estimates; case studies do not calibrate these hour ranges.",
  "work": [
    {
      "title": "Define supported inquiries and reply controls",
      "phase": "process",
      "phase_share": 1,
      "hours": [
        16,
        32,
        56
      ],
      "basis": "Define the five intents, identity checks, approved response content, disputes and escalation; agree who authorizes customer communications."
    },
    {
      "title": "Connect the inbox and customer records",
      "phase": "data",
      "phase_share": 1,
      "hours": [
        24,
        48,
        96
      ],
      "basis": "Configure mailbox and read-only account data access, customer/invoice joins and freshness checks; label and separate 100 test cases."
    },
    {
      "title": "Configure reply drafting and escalation",
      "phase": "build",
      "phase_share": 1,
      "hours": [
        32,
        64,
        128
      ],
      "basis": "Configure intent routing, grounded response drafts, citations/account references and manual escalation; preserve customer isolation and an activity record."
    },
    {
      "title": "Test account accuracy and data access",
      "phase": "validation",
      "phase_share": 1,
      "hours": [
        32,
        64,
        128
      ],
      "basis": "Test held-out and misleading requests, disputed balances, missing records and cross-customer disclosure; resolve errors and rehearse reviewer decisions."
    },
    {
      "title": "Train collectors and launch",
      "phase": "rollout",
      "phase_share": 1,
      "hours": [
        16,
        32,
        56
      ],
      "basis": "Train initial users in checking drafts and escalating exceptions; document fallback, monitor a bounded live pilot and approve release."
    }
  ],
  "total_hours": [
    120,
    240,
    464
  ],
  "annual_upkeep_hours": [
    40,
    80,
    160
  ],
  "upkeep_basis": "Judgment: monthly draft/incident sampling and template or source changes at 2/4/8 hours per month, plus quarterly account-isolation, freshness and regression checks at 4/8/16 hours. Routine reply approval remains operating work.",
  "boundary": "Need role-level setup hours for a human-approved inbox workflow, the actual count of supported intents/integrations, and reviewer time per production draft.",
  "organization_assumptions": "Central task-level settings in organization-model.json; reference hours remain unchanged in this file.",
  "difficulty": {
    "label": "Moderate",
    "reasons": [
      "Replies must use the correct customer's current account records.",
      "Access checks must prevent cross-customer disclosures.",
      "Disputed balances need reliable escalation and human approval.",
      "Missing records and misleading requests need repeatable tests."
    ]
  }
}