Monads Furniture
Led the end-to-end Odoo ERP transformation for a furniture manufacturing company with ₹10 Cr+ turnover and 100+ employees, transitioning operations from Excel-driven processes to a centralized ERP ecosystem.
Overview
Monads Furniture & Interiors is a growing furniture manufacturing company that serves large corporate and commercial clients including Olympia IT Park and Brakes India. With an annual turnover of more than ₹10 crore and a workforce of over 100 employees, the scale of the business meant that its processes could no longer be managed efficiently through disconnected spreadsheets and manual coordination. Under the guidance of Dinesh Konidala, Founder of SDK Infinity Technologies, I took a leading role in this engagement — working with a team that included Sanjana, Dilip, and other SDK members — to understand the complete business flow and translate it into an ERP system built around how Monads actually works.
Business Context
Monads Furniture had built its reputation around manufacturing furniture for corporate offices, IT companies, commercial spaces, and large institutional projects. The company operated across multiple interconnected functions — sales, procurement, inventory, manufacturing, production planning, accounts, and project execution. A customer requirement flows through quotation, order confirmation, material procurement, production scheduling, manufacturing, assembly, quality checks, dispatch, and finally into accounting. Every stage depends on the previous one, making the business far more complex than it appears from the outside. I worked closely with two key leaders: Sathish Sir, who leads sales, relationships, and business development; and Ellpan Sir, who leads manufacturing and production operations.
Challenge
Before the ERP implementation, several business processes were handled using Excel sheets and manual coordination. Different teams maintained different versions of information, updates had to be communicated manually, and management had to collect information from multiple people before understanding the status of an order or project. Tracking historical information was difficult. As the number of employees, customers, projects, products, and transactions increased, the coordination overhead grew significantly. The objective was not simply to replace Excel — it was to create a single operational ecosystem where different departments could work on connected information.
My Role
Solution
Instead of forcing the company to change its business process to match standard software workflows, we studied their requirements and designed the ERP around Monads’ actual workflow. The sales process was structured to support lead generation through order confirmation, giving visibility into the entire sales journey. Procurement was connected to operational requirements. Inventory management tracked materials through receiving, storage, transfer, and consumption. Manufacturing operations were given a structured process connecting orders, materials, production activities, and delivery requirements. Accounting was integrated into the overall ecosystem. Several custom modules and workflows were developed specifically for Monads, requiring continuous communication between the business team, functional team, project management, and development team through iterative cycles of understanding, development, testing, and feedback.
Implementation
Modules & Areas
Gallery
Key Learnings
ERP implementation should never begin with “What features does the software have?” — the better question is “How does the business actually work?” Understanding the business first makes the software start making sense.
The first version of a requirement is rarely the final version. Real users interact with the system differently once they start using it, making testing, feedback, iteration, and communication critical.
ERP implementation is partly about technology and largely about business process understanding. The software is the platform; the real work is understanding the business.
Moving from spreadsheet-driven processes to ERP transforms individual knowledge into organizational knowledge — improving visibility, reducing dependency on isolated information sources, and creating a stronger foundation for growth.
Ownership is not about having all the answers. It means making sure the right questions are asked, the right people are involved, the right information reaches the right person, and the project keeps moving forward.
A consultant’s responsibility goes beyond knowing the software — it includes understanding what the customer needs, why they need it, how the requirement affects other departments, and how to manage expectations through to closure.