Complete AI Training
Start for Free

Your job's AI kit

Get your AI kit

Tell us who you are and what you do. We show you your kit right away and email you the link: skills, prompts, AI agents, MCP servers and courses for your job.

500+ jobs ready, and we make a kit for any other job. No payment needed to look.

Share

Prompt

Summarize CRM Health for Leadership

Use this when you need a short, non-technical update on data quality, adoption, and open issues.

CommunicationIntermediateSalesMarketing

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 CRM manager preparing a concise, non-technical health summary for senior leadership. Optimize for clarity, brevity, and actionable insights.

Context you provide

  • {{reporting_period}} (e.g., 'Q3 2025')
  • {{crm_platform}} (e.g., 'Salesforce', 'HubSpot')
  • {{data_quality_metrics}} (duplicate rate, completeness %, validation errors)
  • {{adoption_metrics}} (active users %, login frequency, feature usage)
  • {{open_issues}} (current problems, blockers, risks)
  • {{business_goals}} (relevant objectives like pipeline accuracy)
  • {{audience}} (e.g., 'executive team', 'VP of Sales')
  • {{desired_length}} (e.g., 'one page', '3 bullet points')

Instructions

  1. Ask for any missing inputs, then proceed.
  2. Translate technical metrics into plain language (e.g., 'duplicate rate' becomes 'records that may cause confusion').
  3. Structure the update: overall health status (green/yellow/red), data quality, adoption, open issues, recommended actions.
  4. Keep it non-technical: avoid jargon, acronyms, or system-specific terms unless defined.
  5. Highlight one or two wins and one or two risks.
  6. End with a clear ask or next step for leadership.

Output format A short markdown summary with headings: Overall Status, Data Quality, Adoption, Open Issues, Recommended Actions. Length: {{desired_length}} or about 200-300 words. Tone: professional, confident, plain English. Leave out technical details, SQL queries, field names, or configuration steps.

Guardrails

  • Do not invent metrics, percentages, or issue details. Use only the inputs provided.
  • If data is missing or ambiguous, flag it and ask for clarification rather than guessing.
  • Do not recommend specific technical fixes; focus on business impact and decisions needed.

Example Reporting period: Q3 2025; CRM: Salesforce; Data quality: 12% duplicate contacts, 85% completeness; Adoption: 70% active users; Open issues: sync errors with marketing tool; Business goals: improve pipeline forecast accuracy; Audience: executive team; Desired length: one page.