Some software projects begin with a blank slate. This one didn't.
We joined the project through a software development company that brought us in as a subcontractor. Their customer was a glass manufacturing company that already relied on Microsoft Dynamics ERP for its everyday operations.
Microsoft Dynamics wasn't going anywhere. It already handled the company's core ERP processes, purchase orders, sales orders, invoices, bills of materials (BOMs), inventory, and other standard business records. The project had a clear goal from the beginning.
The software company wanted a set of custom applications that would work alongside Microsoft Dynamics without replacing it. Our role was to build those custom pieces while keeping the ERP at the center of the business. Instead of changing the ERP itself, we built a wrapper application around it.
The application had its own database and handled custom business logic, while Microsoft Dynamics continued storing the company's core ERP data. The two systems worked together behind the scenes, allowing employees to use custom workflows without losing the structure and reliability of Microsoft Dynamics.
It was a practical approach. The business kept the ERP it already trusted, while gaining functionality that simply didn't exist in the standard platform. One part of the project focused entirely on the sales process.
The manufacturer sold customizable shower doors, and every order looked a little different. Customers could choose different measurements, glass types, materials, finishes, hardware, and several other product options before placing an order. The software company asked us to build a dedicated module for this workflow.
Inside the new application, the sales team could configure a shower door based on a customer's exact requirements instead of trying to piece everything together inside the ERP. As selections were finalized, the application prepared the completed order and synchronized it with Microsoft Dynamics as a sales order. For the sales team, configuring a complex product became much more straightforward.
For Microsoft Dynamics, nothing really changed. It continued receiving complete, structured sales orders exactly as it was designed to. The project also included enhancements to an existing customer portal.
The glass manufacturer already had a portal before we joined, but the software company wanted to expand what customers could do inside it.
We implemented new functionality that gave customers much better visibility into their orders. They could log in to track order progress, review quotes, access packing slips, and stay updated on deliveries without relying on manual updates from the company's team.
We also built features that supported internal logistics operations, including tools for creating and managing delivery driver routes. It brought customer information and delivery planning into a much more connected workflow.
Another requirement was a completely separate portal for suppliers. Vendor communication involved purchase orders, invoices, and supporting documents, but those processes needed a dedicated space outside the ERP interface.
We built a vendor portal where suppliers could securely log in, receive purchase orders, upload required documents, and submit invoices through a centralized workflow. Instead of handling everything through scattered email threads, both the manufacturer and its suppliers had one place to manage ongoing interactions.
Although employees, customers, and suppliers were all using different parts of the solution, Microsoft Dynamics remained the foundation underneath it all.
Core ERP entities stayed inside Microsoft Dynamics, while the wrapper application extended the platform with workflows tailored to the manufacturer's day-to-day operations. That meant the business gained custom functionality without disrupting its existing ERP setup or duplicating critical records across disconnected systems.
Looking back, this project wasn't about building a brand-new ERP system. It was about building everything the ERP needed around it.
The wrapper application, the shower door configurator, the customer portal enhancements, and the vendor portal were all designed to solve specific business requirements while working seamlessly with Microsoft Dynamics rather than competing against it.
This also became part of a longer engineering partnership. For the same end customer, we later contributed to another project that included a pallet tracking and reward management mobile application, extending the digital ecosystem beyond ERP workflows and into daily field operations.
Sometimes the most valuable software isn't the system that replaces everything. It's the software that fits around an existing system and makes it capable of doing a lot more.