NetSuite case study
A Connecticut-based heavy equipment manufacturer had run NetSuite for years alongside Salesforce and Tableau, but years of accumulated customization had started working against them — slowdowns during peak hours, unreliable IoT data sync, and staff falling back on spreadsheets. ERP Peers stepped in as their ongoing NetSuite support partner.
Client context
The client is a heavy equipment manufacturer based in Connecticut, in business for over two decades, designing and building construction machinery including excavators, drilling rigs and loaders for contractors and construction firms who depend on them for both equipment and ongoing service support.
NetSuite had been their ERP for several years, working alongside Salesforce for customer relationships and Tableau for BI and reporting. All three tools mattered to the business — but system slowdowns, data inconsistencies and user inefficiencies were increasingly getting in the way of daily operations.
The challenge
System slowdowns, data inconsistencies and user inefficiencies were increasingly getting in the way of daily operations across NetSuite, Salesforce and Tableau.
Years of workflow and script customization had begun conflicting with each other. The clearest symptom was in the spare-parts inventory system spanning multiple warehouses — during high-demand periods, it would freeze, delaying shipments.
Production machines carried IoT sensors tracking performance and maintenance schedules, meant to sync with NetSuite — but sync inconsistencies meant maintenance teams weren’t always alerted to upcoming service needs, leading to unexpected breakdowns.
Heavy customization made even routine tasks difficult for experienced staff, and some employees had started falling back on spreadsheets for reporting — introducing errors and duplicated work.
The solution delivered
ERP Peers took on ongoing NetSuite support to work through these problems systematically, rather than proposing a system replacement.
A full review of every customization and integration found the inventory system was making far more unnecessary data calls than it needed, overloading the system — optimizing those calls alone improved processing time by 35%.
Removed the internal conflicts between years of accumulated customization that were causing slowdowns and crashes.
Reconnected the sync between NetSuite and the IoT-based production-tracking system, so maintenance data became accurate in real time.
Measurable impact
Optimizing the existing setup, rather than replacing it, was what actually moved the needle here.
Faster system performance — no more peak-hour slowdowns
Faster inventory-system processing after call optimization
Less manual work, with spreadsheet workarounds no longer needed
NetSuite, Salesforce and Tableau working together cleanly
Managers now have accurate, real-time data they can actually rely on for decisions.
Takeaway
Ongoing NetSuite support turned a system that had been fighting the business — slowdowns, unreliable data, adoption friction — into one that supports it. For a business running a mature, heavily customized NetSuite environment alongside other core systems, a full replatform is rarely the first answer: finding out which customizations are actually in conflict, and fixing those, is often what actually moves the needle.
Facing a similar challenge?
We can assess your current setup, the systems involved and where things are actually getting stuck before recommending an integration, workflow change or another route.
Our customer support team is available for help.
