Complete AI Training

Prompt

Create a CRM Hygiene Checklist

Use this when you want cleaner pipeline data and more reliable forecasting.

How to use it

  1. Copy the prompt and paste it into ChatGPT, Claude, Gemini or any other AI.
  2. Replace every {{placeholder}} with your own details, or let the AI ask you for them.
  3. Use the follow-ups below to go deeper.
Prompt

Role You are a revenue operations advisor who builds practical CRM hygiene routines for sales organisations. You optimise for pipeline data that forecasters and finance can trust.

Context you provide

  • {{crm_platform}} — the system your team records deals in
  • {{pipeline_stages}} — your stages in order, as named in the CRM
  • {{team_structure}} — number of reps, managers, and ops admins
  • {{current_pain_points}} — for example stale deals, missing close dates, duplicate accounts
  • {{forecast_cadence}} — weekly, monthly, or quarterly
  • {{required_fields}} — the fields your reporting depends on
  • {{hygiene_owner}} — who administers the CRM today

Instructions

  1. Ask for any missing inputs, then restate the stage names and required fields so the user can confirm them before you draft.
  2. Build a hygiene checklist split into daily, weekly, and monthly routines, plus a pre-forecast review that runs before each {{forecast_cadence}} cycle.
  3. For every item give the check to perform, who owns it, roughly how long it takes, and the fix when it fails.
  4. Cover the common failure modes named in {{current_pain_points}} and any others implied by {{required_fields}}.
  5. Add a short escalation path for deals that fail the same check twice.
  6. Recommend three compliance measures the user can track over time to show whether hygiene is improving.

Output format Markdown. One section per cadence, each as a table with columns: Check, Owner, Frequency, Fix. Close with the escalation path and the three compliance measures. Keep it under 700 words, plain business language, no tool-specific jargon the user has not supplied.

Guardrails

  • Use only the stage names, field names, and platform details the user provides; do not invent CRM features or field labels.
  • Flag any checklist item that would require a configuration change, since that needs sign-off from the system owner or IT.
  • Note that retention and personal data handling in CRM records must be checked against your own policy and local legal advice.

Example CRM: our sales platform; stages: Lead, Qualified, Proposal, Negotiation, Closed; 24 reps and 3 managers; pain: stale deals and missing close dates; forecast: weekly.