Lead Enrichment + Grading

Turn a bare address into a fully enriched, correctly graded working lead, with accurate owner names, every phone number captured, equity percent, and interest rate, then sort it into the gold/silver/bronze bucket that decides how hard and how often you chase it. Grading is what keeps a solo operator or a small team from burning equal effort on a high-equity gold lead and a thin, cold one. None of that grading means anything if the import underneath it is sloppy, so the accuracy of the parse is the real foundation of this step.

Daily, right after the morning scrape pass (see sop-kod-scrape-health-check), and any time a re-scrape changes a case's status in a way that should re-trigger grading.

• New addresses already pushed into the enrichment source from the intake/scrape step.
• Enrichment access working (logged in, session valid).
• Familiarity with the fields this step depends on: equity percent and interest rate, and phones, owner names, DNC flags, and litigator flags on the contact side.

• Parse QA was actually run and passed before grading started, every column mapped to the right field and every phone number on the batch was captured.
• Litigator-flagged contacts are fully removed, everywhere. DNC-flagged contacts are kept and clearly labeled, never silently dropped, never fully deleted.
• Every newly imported address has an equity percent and, where available, an interest rate on the record, a lead with neither field populated did not actually enrich and needs a re-check.
• Every enriched lead has exactly one bucket assigned (gold/silver/bronze/ cold), and every gold/silver lead is enrolled in its matching cadence.
• A thin or negative-equity lead with a low interest rate is labeled subto, not miscategorized as cold and dropped.
• Owner names backfilled correctly across the batch, a common failure mode when an export silently goes to email instead of a direct download.

• A batch produced a suspiciously small file, or owner names are missing across it. The export can sometimes go to email instead of offering a direct download. Check the export inbox or downloads page for the real file rather than assuming the pass completed. Re-run and confirm a genuine download before trusting the import.
• Parse QA turns up a column mismatch. Stop before grading. Re-check the mapping against the column-map reference if one exists, fix it, and re-import rather than patching individual records by hand.
• A phone number looks missing that should be on the batch. Re-check whether a contact type was excluded by mistake at export time. This is exactly the failure mode parse QA exists to catch, treat it as a process gap, not a one-off.
• A DNC number got removed instead of labeled. This is a scrub error, not a judgment call. DNC is never a removal reason. Restore the record and relabel it correctly.
• A litigator-flagged number is still showing up somewhere (dialer, route, list). Treat this as a hard stop. It should never happen. Remove it fully and flag how it slipped through.
• A lead looks graded wrong (for example, a clearly high-equity property landed in silver, or a thin-equity property is missing its subto tag). Re-check the raw equity percent and interest rate first, grading is only as good as the export data underneath it.
• A lead you expected to see enriched never got phones or an owner name. Confirm the contact-side export actually ran and imported, not just the property side, the two exports carry different fields and both are required for full enrichment.
• Comps or ARV needed for an offer are missing or feel stale. Enrichment gives you equity and rate, not a fresh valuation, pull area comps separately before making an offer rather than relying solely on the built-in value field.