Target Account Scanner: QA checklist

Pack Version: 1.0.0

Complete on a test HubSpot portal or sandboxed property group before production. The reviewer must not be the builder.

Data validation

• ☐ All four demo-data records pass `schemas/input.schema.json`
• ☐ Workflow output on demo data matches `demo-data/sample-output.json` field for field (scores, bands, breakdowns, gate results)
• ☐ Output validates against `schemas/output.schema.json`
• ☐ A row with null revenue scores neutral (5), not zero
• ☐ A row missing a required field is dropped and logged, and does not fail the run

Scoring

• ☐ Weights in the running config match the agreed, versioned ICP config
• ☐ Acme Analytics scores 88 / Target; Petal & Stem scores 10 / Exclude
• ☐ Band thresholds read from config: changing target threshold to 80 demotes Acme without a code edit
• ☐ Disqualifying tech sets the flag and zeroes the 5-point component

Gates and CRM safety

• ☐ Northwind Logistics (customer) returns `skipped_customer` and produces no HubSpot write
• ☐ An account with an open deal returns `skipped_open_deal` and produces no write
• ☐ Writes land only in the five `icp_*` properties; diff a test company's full property set before/after to confirm
• ☐ Private app scopes limited to companies read/write + deals read
• ☐ `icp_model_version` populated on every written record

Operations

• ☐ Slack digest posts to the agreed channel with score and reasons per account
• ☐ Run log records band distribution and gate skips
• ☐ Target band ≤25% of test universe (if higher, weights are too generous; stop and retune)
• ☐ Duplicate domain in source data scores once, not twice
• ☐ Rollback tested: workflow disabled, test property values cleared

Sign-off