Define minimal required CRM fields by sales stage

Streamline CRM data entry to ensure data integrity without slowing down sales teams. Establishes the exact required fields needed at every deal milestone.

You getPipeline Data Principles, stage-by-Stage Field Matrix and decommission Candidates

Prompt

Prompt
Act as a revenue operations consultant. Help design a lean CRM field enforcement plan that ensures sales pipeline visibility without overburdening account executives with unnecessary forms.

First, ask me exactly 3 short numbered questions in one message:
1. What CRM platform do you use, and what deal stages exist in your pipeline?
2. What is your typical sales motion (e.g., product-led self-serve, inbound mid-market, enterprise field sales)?
3. What specific data points are mandatory for leadership reporting or downstream handoffs (e.g., billing, onboarding, territory analysis)?

Wait for my answers. Once I respond, create a stage-by-stage requirement matrix showing only the minimum viable data fields required to move a deal forward.

Output format:
- Pipeline Data Principles (3 concise guidelines)
- Stage-by-Stage Field Matrix (Markdown table: Pipeline Stage, Required Fields, Field Format/Type, Why It Matters)
- Decommission Candidates (Common CRM fields to remove or make optional)

Example output

Example for: a B2B SaaS team using HubSpot with a 4-stage inbound sales process

  • Pipeline Data Principles:
  1. Collect data only when it changes downstream action; never capture information no team actively reads.
  2. Use picklists and dropdowns instead of free-text fields whenever reporting is required.
  3. Make fields mandatory only at stage exit, not during initial conversation entry.
  • Stage-by-Stage Field Matrix:
Pipeline StageRequired FieldsField Format/TypeWhy It Matters
Stage 1: Discovery CompletedPrimary Business PainDropdown (4 choices)Ensures clear value proposition before product demonstration
Stage 1: Discovery CompletedEstimated Seat CountNumber (Integer)Qualifies lead tier and routes to correct solutions team
Stage 2: Demo DeliveredEconomic Buyer IdentifiedSingle-line text (Name & Title)Validates decision-maker involvement prior to pricing discussion
Stage 2: Demo DeliveredTarget Close DateDate pickerEstablishes forecasting baseline for current quarterly revenue
Stage 3: Proposal SentContract Value (ARR)CurrencyFeeds finance pipeline forecasting and capacity planning
Stage 3: Proposal SentLegal Contact EmailEmail formatPrevents administrative delays during security and MSA reviews
Stage 4: Closed WonBilling Address & Entity NameText blockRequired for immediate invoice generation by accounting
Stage 4: Closed WonOnboarding Kickoff LeadContact lookupTriggers automated customer success assignment
  • Decommission Candidates:
  • 'Competitor notes' free-text box (Move to closed-lost post-mortem only).
  • 'Annual revenue' of customer (Pull automatically via domain enrichment rather than asking reps).
  • 'Budget status' checkbox (Subjective field that rarely reflects actual buying behavior).
Written by AI from this prompt. Your results will vary.

Paste this prompt into Claude, ChatGPT, or Gemini. Answer the 3 discovery questions with your specific pipeline stages. Follow up by asking the model to write validation rules or tooltips for the most frequently missed fields.

Make it repeatable

Keep using this prompt without pasting it in every time.

Keep exploring

More in Automation & Workflows