Library/RevOps, Data & Analytics Support/Data Governance & Enrichment/Design a CRM data standard and field dictionary
TestedRevOps, Data & Analytics SupportSame-Day Use (under 30 min)
About this prompt
This prompt helps RevOps design a concrete CRM data standard and field dictionary to stop inconsistent data from breaking reporting and routing. It produces field definitions, picklists, required-vs-optional rules, normalization logic, an enrichment policy, and enforcement controls. Use it when free-text fields and ten-ways-of-spelling-industry have made your CRM data unreliable.When industries are entered ten ways and titles are all over the place, reporting and routing break and no amount of after-the-fact cleanup keeps up. This prompt designs an implementable standard: a field dictionary defining each key field's meaning, owner, format, and allowed picklist values; required-vs-optional rules by stage so reps aren't forced to fake junk fields; normalization logic for collapsing messy variants into standard buckets; an enrichment policy for which source wins on conflict; and enforcement controls (picklists over free text, validation rules, required-field gates) that prevent bad data at entry. Provide the objects and fields in scope (ACCOUNTS / CONTACTS / OPPS), what the bad data breaks, how data gets entered today (REPS, FORMS, ENRICHMENT, IMPORTS), and THE FIELDS THAT MUST BE CLEAN. The output is meant to hand to whoever configures the CRM, distinct from a one-time merge or enrichment pass. It flags where you'll face a strict-control-vs-rep-flexibility tradeoff, so decide those calls deliberately rather than defaulting to maximum strictness.The prompt
Our CRM data is inconsistent — free-text where there should be picklists, industries entered ten ways, titles all over the place — and it breaks reporting and routing. Help me design a data standard a
The rest of this prompt is Pro.Copying the full text is Pro. Browsing stays free, and 100 prompts are free in full.
Copying the full text is Pro.
Variables to replace
ACCOUNTS / CONTACTS / OPPS — AND THE KEY FIELDS THAT MATTER | REPORTING / ROUTING / SEGMENTATION / FORECASTING | REPS, FORMS, ENRICHMENT, IMPORTS | THE FIELDS THAT MUST BE CLEAN
How to run it
- Copy the prompt and paste it into Claude, ChatGPT, Gemini, or Copilot — it's tuned to run in any of them.
- Replace the variables — swap each bracketed token for your deal's specifics. The variables list above explains every field.
- Make it yours — run it, keep what's strong, and tighten your inputs on the next pass. The prompt improves with your context.
What good output looks like
Make it yours
Promptifi ProFull text of all 2,900+ prompts, every workflow, unlimited saves.Start Pro — $4.99/moor $99 once, lifetime
You're ProFull library open. Copy, save, and chain anything.