# AI lead magnet to CRM launch worksheet

Use this worksheet with the accompanying CSV field map. Replace every illustrative property with the exact internal name from the client's CRM.

## 1. Result and follow-up contract

- Lead magnet name and version:
- Visitor input:
- Result promised:
- Result available without CRM success? Yes / No
- Delivery channel:
- Proportional next step:
- What the result does not prove:

## 2. Record model

- Immutable submission ID format:
- Contact match key:
- Ambiguous-match action:
- Where original answers are retained:
- Where the latest result is stored:
- When a company/account is created:
- When a lead is assigned:
- When a deal/opportunity is created:
- What is never created automatically:

## 3. Field map review

For every CSV row, confirm:

- exact source field and version;
- canonical field name;
- destination object and internal property name;
- destination type and allowed values;
- required/optional/null behavior;
- normalization and length rule;
- create, overwrite, append, preserve, or never-write policy;
- owner of the field definition;
- visitor-facing and operator-facing failure behavior.

## 4. Consent and privacy

- Purpose of report delivery:
- Separate purpose of direct marketing:
- Marketing choice shown separately? Yes / No
- Checkbox starts unchecked? Yes / No
- Wording/version stored:
- Collection time stored:
- Collection page stored:
- Withdrawal/suppression route:
- Retention period for raw submission:
- Retention period for CRM fields:
- Client privacy/legal reviewer:

## 5. Transport and secrets

- Pattern: CRM-native form / automation platform / direct server API
- Browser posts to:
- Server or automation posts to:
- Credential owner:
- Credential is absent from browser code and logs? Yes / No
- Timeout:
- Retryable responses:
- Non-retryable responses:
- Maximum attempts:
- Dead-letter or exception queue owner:
- Idempotency or duplicate key:

## 6. Acceptance matrix

| Case | Expected visitor result | Expected CRM result | Evidence | Pass/Fail |
|---|---|---|---|---|
| Valid new email | | | | |
| Existing email | | | | |
| Same submission sent twice | | | | |
| Unicode name | | | | |
| Blank optional company | | | | |
| Invalid email | | | | |
| Unknown enum value | | | | |
| Marketing choice is false | | | | |
| Marketing choice is true | | | | |
| CRM returns validation error | | | | |
| CRM returns rate limit | | | | |
| CRM times out | | | | |
| Notification/routing fails | | | | |
| Screen reader and keyboard flow | | | | |

## 7. Reconciliation and handoff

- Daily count to compare: accepted submissions / synced records / exceptions
- Alert threshold and recipient:
- Dashboard excludes test records? Yes / No
- Sales owner and response target:
- Backup owner:
- Runbook location:
- Field-map owner:
- CRM schema-change owner:
- Shutdown procedure:
- Next review date:

## Release decision

- [ ] The staging form passed the local contract tests.
- [ ] The client CRM sandbox accepted every mapped field.
- [ ] A duplicate submission did not create an unintended duplicate.
- [ ] Empty optional fields did not erase existing values.
- [ ] Report delivery worked while CRM sync was unavailable.
- [ ] Marketing opt-in and report delivery remained separate.
- [ ] A real operator received and understood the routed test lead.
- [ ] Exceptions were visible and recoverable.
- [ ] The client accepted the privacy, retention, and ownership plan.

Decision: Ship / Hold

Owner:

Date:
