System BuildIntermediateManufacturingEngineeringSME

ERP System Requirements Analysis Prompt

Helps map operational processes, module scope, and data integration needs before an ERP rollout.

Audience: IT, finance, operations managers · Last updated 2026-07-17
Contents

Scenario

Helps map operational processes, module scope, and data integration needs before an ERP rollout.

Applicable Industry or Company Size

  • Manufacturing
  • Engineering
  • SME

Preparation Before Use

  • A documented review of current processes.
  • A list of existing systems and their data flows.

Variable Reference

VariableDescription
[Company Name]Your company's official name
[Industry]e.g., precision machinery manufacturing, systems integration, engineering consulting
[Number of Employees]e.g., 25, 120, 500+
[Annual Revenue Range]e.g., NT$500M–1B
[Top 3 Pain Points]The top three problems you currently want to solve

Full Prompt

Prompt
You are a senior ERP implementation consultant familiar with finance, production planning, procurement, and inventory processes in manufacturing and engineering companies. Conduct an ERP requirements analysis based on the following background.

[Background]
- Company: [Company Name] / [Industry]
- Number of Employees: [Number of Employees]
- Annual Revenue Range: [Annual Revenue Range]
- Top 3 Pain Points: [Top 3 Pain Points]

[Task]
1. In no more than 200 words, describe your assumed current process (explicitly labeled "the following is an assumption").
2. Recommend module scope priority (finance, general ledger, AR/AP, procurement, inventory, production planning, costing, projects, BI reporting).
3. List 20 user stories (As a / I want / So that).
4. Recommend data integration targets (CRM, MES, e-invoicing, banking, government platforms).
5. Recommend rollout phases and milestones (Wave 1 / 2 / 3).
6. Recommend key risks and mitigations.

[Judgment Criteria] Do not name a specific vendor (SAP / Oracle, etc.) as the only solution; explain the situations each fits.

[Handling uncertain information]
If any of the variables below have not been filled in or the information is insufficient, list the missing fields directly and ask the user — do not assume or fabricate data.

[Prohibited]
- Do not fabricate statistics, regulation numbers, certification names, or client case studies.
- When professional judgment is insufficient, explicitly mark "requires human confirmation" rather than inferring on your own.

[Final self-check]
After producing the output, list a self-check at the end covering: (1) whether any fabricated numbers, regulations, standards, or client names were used; (2) whether any unfilled but important variable was ignored; (3) whether assumptions are clearly labeled.

Usage Steps

  1. Fill in the variables.
  2. Validate assumptions through interviews with finance / production planning teams.
  3. Compile into an RFP for candidate vendors.

Example

For a 100-employee manufacturer, Wave 1 typically focuses on finance, inventory, and procurement.

Common Mistakes

  • Requiring all modules to launch at once.
  • Starting vendor selection before clearly documenting current processes.

Cautions

  • ERP adoption involves organizational change, not just system selection.
Last updated 2026-07-17

Need further customization to fit your company's process and industry?

AEGIS POWER INTEGRATIONS offers AI adoption, process assessment, and systems integration consulting to help you turn prompts into a stable, working internal process.