Salesforce Field Update Checklist
Generate the exact CRM field updates a deal needs — corrected close date, missing amount, firmographic fields HG can fill — as a copy-paste checklist.
The exact CRM fields to fix — backfilled with verified HG firmographic data
Employee count + NAICS + HQ from HG.
Each labeled observed or modeled.
| Field | Current | Proposed |
|---|---|---|
| Employees | blank | ~315,000 (HG observed) |
| NAICS | blank | 446110 Pharmacies |
| Close date | 2026-02-01 (past) | Q3 band - see note |
Overview
For a pasted deal record, produce a precise CRM field-update checklist: which fields are stale or empty, what HG firmographic data can populate them (employee count, industry, HQ), and a realistic corrected close date — so reps fix records in minutes with verified data instead of guesses.
Use cases
Clean records without the busywork
Employee count, industry, HQ — the fields reports break on — get backfilled from HG instead of left blank or guessed. The rep pastes verified values and moves on.
Honest close dates
Instead of a fabricated precise date, the checklist proposes a defensible band with reasoning, so the forecast inherits an honest date the rep can stand behind.
View workflow prompt
# Salesforce Field Update Checklist
## Parameters
- `{{domain}}` *(required)* — The account domain on the record. Example: `walgreens.com`
- `{{current_fields}}` *(required)* — Pasted current field values (close date, amount, employee count, industry, HQ, stage). Example: `Close: 2026-02-01 (past); Amount: blank; Employees: blank; Industry: Retail; Stage: Proposal`
## Purpose
Turn {{current_fields}} for {{domain}} into a precise, copy-paste CRM update checklist — backfilling firmographic fields from HG, flagging stale dates, and labeling each value modeled vs. observed so the rep trusts what they're pasting.
## Process
1. **Diff the record** — read {{current_fields}}; list every field that is empty, stale (past-dated), or obviously wrong.
2. **Backfill from HG** — `company_firmographic` for {{domain}} to source employee count, industry/NAICS, HQ location, and revenue band. Label each as modeled or observed per HG.
3. **Close-date sanity** — if the close date is past and the stage is open, propose a realistic corrected date band (do not invent a precise date; give a defensible range with the reasoning).
4. **In-market note** — `company_intent` one-liner on whether the account is currently active, so the rep knows whether the record is worth the cleanup time.
5. **Emit checklist** — one row per field: field | current | proposed | source.
## Output Format
Markdown with:
- `# CRM Field Update Checklist — {{domain}}`
- `## Field Updates` (table: field | current | proposed value | source [HG observed/modeled or rep judgement])
- `## Close-Date Note` (reasoning for the proposed date band)
- `## In-Market Status` (one line)
- `## Citations`
## Quality Checklist
- Every HG-sourced value labels modeled vs. observed
- No precise close date is invented — only a reasoned band
- Firmographic backfill cites `company_firmographic`
- Fields HG cannot source are marked 'rep judgement', not fabricated