🚀 Early Access: FREE full access to All Workflows and AI Prompt Systems! No credit card required.
RevOps managers, Sales operations teams, Sales leaders, CRM owners, Operations managers
Prepare the Required Inputs listed in the Workflow Prompt. Use as much detail as necessary.
1. Copy the Workflow Prompt.
2. Paste it into your AI tool.
3. Replace the "Required Inputs"
4. Run the prompt.
Get access to this workflow and 1000+ others designed to save hours and get better results with AI.
You are a CRM operations specialist. Your task is to audit CRM hygiene and produce a practical remediation plan that improves reporting, forecasting, ownership, and sales execution.
### Required Input
- CRM Object or Area: [Example: "Leads, contacts, accounts, opportunities, activities"]
- Business Goal: [Example: "Improve forecast accuracy" or "clean pipeline reporting"]
- Required Fields: [Fields that should be complete. Example: "Close date, stage, owner, source"]
- Sample Data Issues: [Example: "Duplicate accounts, missing industries, stale close dates"]
- Current Reporting Problems: [Example: "Managers do not trust pipeline dashboards"]
- Sales Process Context: [Stage names, ownership rules, handoffs, or lifecycle definitions]
- Team Usage Pattern: [Who updates records and when. Example: "AEs update opportunities weekly"]
- Data Governance Rules: [Existing rules, required fields, naming conventions, or none]
- Known Constraints: [Limited admin support, legacy records, migration issues, etc.]
### Input Validation
Review every required input before producing the final output. If anything is missing, unclear, contradictory, or too vague, ask specific clarification questions. Pause and wait for answers.
### Instructions
Audit CRM hygiene as a revenue operations issue, not a data-entry complaint. Explain how each data problem affects forecasting, routing, reporting, customer handoffs, pipeline inspection, or rep productivity.
Assess completeness, accuracy, consistency, duplication, ownership, freshness, and field usefulness. Do not recommend adding fields unless they support a clear decision or workflow. Too many fields can reduce hygiene.
Evaluate whether required fields match the sales process. Identify fields that are missing, unclear, poorly defined, rarely updated, or used inconsistently across teams. Recommend field definitions and update rules where needed.
Review record ownership and lifecycle logic. Look for orphaned records, duplicate ownership, outdated statuses, unclear handoffs, and records stuck between lifecycle stages.
Prioritise remediation based on business impact. Separate urgent fixes that affect revenue reporting from lower-priority cosmetic clean-up. Include a realistic plan for small teams that may not have dedicated CRM administrators.
Include prevention, not just clean-up. Recommend governance rules, update cadence, validation practices, dashboard checks, and team accountability routines.
### Output
Use this structure:
1. CRM Hygiene Summary
- Overall data health rating
- Most damaging data issue
- Reporting impact
- Recommended first action
2. Data Quality Scorecard
Score completeness, accuracy, consistency, duplication, freshness, ownership, and process alignment.
3. Issue Register
For each issue include:
- Description
- Example or likely source
- Business impact
- Severity
- Recommended fix
- Owner
4. Field and Process Review
Identify fields to keep, clarify, remove, merge, or add.
5. Reporting Impact Analysis
Explain which dashboards, forecasts, handoffs, or workflows are affected.
6. Clean-Up Roadmap
Create a phased plan for immediate fixes, 30-day remediation, and ongoing maintenance.
7. Governance Recommendations
Provide rules for field definitions, ownership, update cadence, validation, and manager review.
Add a simple weekly CRM hygiene checklist for sales managers.
| Data Health Metric | Assigned Rating | Identified Operational Blind Spot |
|---|---|---|
| Completeness | Critical Gap | Core strategic text blocks (e.g., “Quantified Baseline Operational Metric”) are left completely empty in 58% of open opportunities. |
| Accuracy | Needs Improvement | Close dates do not track genuine buyer intent or internal procurement/legal milestones. |
| Consistency | Needs Improvement | Product naming fields fluctuate between “Customs Module,” “Gateway Hub,” and “Cross-Border API” within the same segment. |
| Duplication | Acceptable | Low duplication on cross-sell accounts due to strict parent account locking, but new enterprise logo leads show multi-owner friction. |
| Freshness | Critical Gap | Opportunities remain anchored in “Stage 2: Solution Demonstration” for over 40 days without an active touchpoint or email exchange. |
| Process Alignment | Critical Gap | CRM fields reflect individual rep activity checkboxes (“Demo Sent”) instead of objective, buyer-action milestones. |
Target ERP Environment (This dropdown field is critical for identifying pre-mapped data gateway connectors like SAP, Oracle, or NetSuite).Forecast Category. Move away from subjective definitions. Redefine “Commit” to require two conditions: the delivery of a Cost-of-Delay Ledger and confirmed meeting alignment with the customer’s Lead Systems Architect.Probability (%) Slider. Eliminate the manual percentage field completely. Manual adjustments encourage optimistic guessing; system probabilities should be calculated automatically based on the opportunity stage.Buyer-Verified Next Step. A text field that replaces the standard “Next Steps” log. It mandates entry of a specific, agreed-upon calendar action item locked in by the customer (e.g., “Buyer to submit security SLA to internal IT team on June 15”).The Downstream Dashboard Poisoning Loop:
Bad data….
Get access to all workflows, across every sector, with structured systems built for better results.