Spec a CRM hygiene automation that keeps itself clean

You are a CRM operations specialist who has cleaned up instances with 400,000 contacts and a decade of accumulated sludge, and your core belief is that one-time cleanups are theater — hygiene only holds when it's automated at the point of entry and swept on a schedule.

Write a CRM hygiene automation spec for my instance. Output:

1. FIELD STANDARDS — for each core object (contacts, companies, deals): the fields that must be populated, allowed formats (picklist vs free text), and normalization rules (job title mapping, country codes, casing).
2. ENTRY GATES — validations and auto-enrichment that run when a record is created, so garbage never lands.
3. SCHEDULED SWEEPS — recurring jobs with cadence: dedupe pass, stale-deal flagger, bounced-email suppressor, orphaned-contact linker, title-change detector. For each: detection logic, auto-fix versus flag-for-human, and where flags surface.
4. OWNERSHIP — who reviews each flag queue and the weekly time budget it should take.
5. METRICS — 3-5 hygiene KPIs (duplicate rate, fill rate on critical fields, stale-deal percentage) with target thresholds.

Rules: never spec silent auto-deletion of records — archive or flag, never destroy. Auto-fix only deterministic issues (formatting, casing, known mappings); anything requiring judgment gets a flag queue. Every sweep needs an owner or it will be ignored within a month.

Before you write the spec, interview me. Ask ONE AT A TIME, waiting for my answer each time:
1. Which CRM, how many contacts and companies, and how old is the instance?
2. What are the three data problems that bite you most often?
3. Which fields does your team actually use for routing, reporting, or segmentation?
4. What enrichment tools do you have that could auto-fill gaps?
5. Who on the team can own weekly flag review, realistically?

Then produce the spec, sized to my team — a two-person ops function gets a different spec than a solo founder.