ERP is a motley group of microservices that work independently as well as together—like honey bees—to bring order to chaos. Each microservice owns one task, and together they form the backbone of the organisation.
Enterprise Resource Planning (ERP) systems are the operational backbone of many companies, especially as they scale. The actual job of an ERP is to track every activity and target so that data can inform decisions proactively. This is not a vague aspiration — it is the entire value proposition.
But building an ERP is not about stitching together a monolith. It requires a modular architecture where independent microservices serve individual tasks while collaborating seamlessly. This approach ensures robustness, future-proofing, and scalability.
Understanding who uses ERP and what they need is critical. Every department—from Purchase to Finance, HR to Sales—has distinct pain points and data needs. The ERP must enhance the value each stakeholder contributes, not just automate tasks.
This lesson will take you through the architecture, stakeholder landscape, and discovery process that together define successful ERP product management.
ERP is a suite of microservices, not a single product
ERP systems are often misunderstood as one big software. The reality is closer to a colony of honey bees: many small, independent microservices each responsible for a specific task, working together to bring order to organizational chaos.
Each microservice owns one business capability—purchase order management, inventory tracking, payroll processing, or sales invoicing. These microservices combine into modules aligned with departments—Finance, HR, Sales, and so on. The modules themselves integrate to form the ERP system.
This microservices approach has three core advantages:
- Decoupling: Teams can build, deploy, and maintain each microservice independently, reducing complexity and risk.
- Scalability: As the company grows, the ERP can scale horizontally by adding or upgrading specific microservices.
- Flexibility: New modules or features can be added without disrupting existing workflows, enabling future-proof design.
In practice, this means an ERP is not a single app but a suit of APIs woven together. Modern ERPs increasingly expose APIs, enabling integrations, custom workflows, and interoperability with external systems.
Product discovery kickoff with engineering and design
You (PM): “Our ERP should not be a monolith. Let's design it as independent microservices that can evolve separately but talk to each other via APIs.”
Engineering Lead: “That will help us support future modules without a big rewrite.”
Design Lead: “We can create consistent UX patterns across modules, even if the backend is distributed.”
Aligning on microservices upfront sets the foundation for a scalable, robust ERP system.
Choosing architecture early shapes ERP's future adaptability.
Who uses ERP? Every stakeholder — and they all have different needs
An ERP system is not built for a single user persona. It is used by everyone in the company, from top management to frontline staff.
- Top management uses ERP dashboards to monitor operations, assess performance, and make strategic decisions based on data.
- Purchase teams want predictive demand insights to optimize inventory and negotiate better deals.
- Finance and accounting need accurate transaction records and compliance tracking.
- HR manages payroll, attendance, and employee records.
- Sales teams track orders, customer interactions, and revenue forecasts.
Each department derives distinct value from the ERP, and the system must solve their pain points thoroughly. This requires detailed user research to uncover workflows, frustrations, and data needs.
The vision: data-driven decisions, proactively enabled
The ERP’s guiding vision is to track every activity and target so data can inform decisions proactively. This means shifting from reactive reporting to predictive insights and action triggers.
For example:
- Purchase can get alerts when inventory is predicted to dip below threshold, factoring in supplier lead times.
- Finance can flag anomalies in expenses before month-end closes.
- HR can monitor turnover risk signals and prompt retention actions.
This vision requires not only comprehensive data capture but also analytics layered into the ERP modules. Data pipelines, event processing, and AI/ML models become part of the product.
User research and discovery are non-negotiable before building
Because ERP users are diverse and workflows complex, a detailed user research phase is essential before development.
Interviews, shadowing, and contextual inquiry help uncover:
- The pain points in current processes
- What data users rely on and trust
- How decisions are currently made, and what data would help
- Integration points with legacy systems
This discovery informs the product roadmap and prioritization. Skipping or rushing this phase leads to building modules that users don’t adopt or that fail to solve real problems.
Choose a department in your organization or one you know well (e.g., Finance, Sales, HR). Conduct or imagine interviews with 3-5 users in that department. For each interview, note:
- What are their key tasks and workflows?
- What are their biggest pain points or inefficiencies?
- What data do they use to make decisions?
- What would help them make better, faster decisions?
- What current tools or systems do they use? What do they like/dislike?
Summarize your findings as user stories or problem statements that will guide ERP module design.
ERP modules and their responsibilities
Here are the core modules commonly found in an ERP, each composed of microservices:
| Module | Responsibilities | Indian Context Example |
|---|---|---|
| Purchase | Demand forecasting, supplier management, procurement workflows | Purchase teams in manufacturing companies like Bharat Forge |
| Inventory Management | Stock tracking, warehouse management, reorder alerts | Retail chains managing multiple warehouses like Big Bazaar |
| Sales | Order processing, customer management, invoicing | E-commerce companies like Flipkart tracking B2B orders |
| Finance Management | Expense tracking, budgeting, compliance, audit trails | Startups managing GST compliance and tax filings |
| HR | Payroll, attendance, employee records, performance management | IT services firms managing large, distributed teams |
| Accounting | Ledger maintenance, financial reporting, reconciliations | SMEs using ERP to file statutory reports |
The microservices within these modules must be designed to own their data and APIs clearly, enabling independent evolution and integration.
The interplay between PLM and ERP in enterprise product development
Product Lifecycle Management (PLM) and ERP are closely related but serve different purposes.
- PLM focuses on the entire lifecycle of a product — from ideation, design, development, to manufacturing and support. It manages product data, versions, and engineering workflows.
- ERP manages the operational processes that support the business — procurement, inventory, sales, finance, HR.
In manufacturing and complex enterprises, PLM feeds into ERP. For example, a new product design in PLM triggers procurement of raw materials managed in ERP.
As a PM, understanding how PLM and ERP systems integrate is crucial to ensure data consistency and process alignment.
Integration planning meeting between PLM and ERP teams
PLM PM: “Our BOM (Bill of Materials) changes must flow into procurement automatically.”
ERP PM (You): “We'll expose APIs to receive BOM updates and adjust purchase forecasts accordingly.”
Engineering Lead: “We'll need to version control these integrations to avoid breaking workflows.”
Cross-team alignment on PLM-ERP integration avoids costly disconnects down the line.
Ensuring seamless data flow between PLM and ERP is critical for operational efficiency.
Estimation and planning in ERP product development
ERP products require careful planning and estimation due to their complexity and impact.
- Break down features into microservices and modules.
- Estimate independently to allow parallel development.
- Incorporate buffer for integration testing and change management.
- Plan for incremental delivery with usable modules released early.
This approach reduces risk and allows user feedback to shape subsequent development.
Test yourself: Prioritizing ERP modules for a mid-sized Indian manufacturing company
You are the PM for an ERP product at a mid-sized manufacturing firm based in Pune. The company has urgent needs in Purchase, Inventory, and Finance modules but limited engineering bandwidth. The CEO wants to launch a complete ERP in 12 months.
The call: How do you prioritize module development and set stakeholder expectations? What trade-offs do you communicate?
Your reasoning:
You are the PM for an ERP product at a mid-sized manufacturing firm based in Pune. The company has urgent needs in Purchase, Inventory, and Finance modules but limited engineering bandwidth. The CEO wants to launch a complete ERP in 12 months.
Your task: How do you prioritize module development and set stakeholder expectations? What trade-offs do you communicate?
your reasoning:
From the field: Lessons learned in ERP product management
Where to go next
- Explore how to write effective PRDs for complex products: Product Requirements Documents
- Learn about Agile and Scrum for enterprise software delivery: Agile Product Management
- Understand stakeholder management in large organizations: Stakeholder Management
- Deepen your skills in user research for enterprise products: User Research Methods
PL alumni now work at Flipkart, Razorpay, Swiggy, PhonePe, Amazon, Microsoft, and many other companies.