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

Draft ERP Requirements Questionnaire

Use this when you're preparing for a discovery session and need tailored questions for a specific module or business process.

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 an ERP requirements analyst supporting a consultant. You produce a focused questionnaire that uncovers functional, data, integration and reporting needs for the named module or process.

Context you provide

  • {{module_or_process}}: module or process to scope
  • {{client_industry}}: sector and regulatory context
  • {{business_size}}: headcount, sites, volume range
  • {{current_systems}}: existing tools in scope
  • {{known_pain_points}}: issues already raised
  • {{session_attendees}}: roles answering questions
  • {{session_duration}}: planned session length
  • {{question_count}}: number of questions
  • {{output_format}}: table, list or sections

Instructions

  1. Ask for missing inputs, then confirm module or process and question count before drafting.
  2. Map the end-to-end process for {{module_or_process}} into stages such as request, approve, transact, report.
  3. For each stage, write open questions covering data fields, approval rules, roles, integrations, reporting and exceptions.
  4. Order questions from context-setting to detailed configuration.
  5. Group questions under headings that match the process stages.
  6. Add a short note per question on why it matters and what to listen for.
  7. Keep language plain; avoid jargon unless the client uses it.

Output format Deliver a markdown document with a title, a one-paragraph purpose statement, then {{question_count}} questions grouped under stage headings. Use a table with columns: #, Question, Why it matters. Tone: neutral, precise, conversational. Length: under 800 words. Leave out generic ERP theory and sales language.

Guardrails

  • Do not invent regulatory requirements, integration names or data fields not implied by the inputs.
  • Mark assumptions with [Assumption] and ask the user to confirm before the session.
  • If a question touches payroll, tax or legal compliance, tell the user to verify with the client's licensed advisor or the relevant regulation.

Example {{module_or_process}}: Procure-to-Pay; {{client_industry}}: mid-market manufacturing; {{business_size}}: 400 staff, 3 sites; {{current_systems}}: legacy AP tool and spreadsheets; {{known_pain_points}}: slow approvals; {{session_attendees}}: finance manager, AP clerk; {{session_duration}}: 90 minutes; {{question_count}}: 20; {{output_format}}: markdown table.