Professional services · Work
A disaster-recovery network that could not close in 15 days
A health check found 22 custom scripts, 18 workflows, 21 half-baked integrations, and a month-end that took 15 days. Spreadsheets were holding the company up.
Fleet Response
What was going on
Fleet Response runs a nationwide disaster-recovery network. NetSuite was live in name: a basic setup plus spreadsheets, 1,090 user records, 51 roles, 38 bundles, and more than 80 open tickets. Salora ran a full review, prioritized the ticket pile, upgraded the license, and activated SuiteProjects, Advanced Revenue Management, and OneWorld. Integrations to UKG, Divvy, and Dispatch were stabilized. Job Management Report 2.0 went to Power BI, and nightly data pushed to NetSuite Planning & Budgeting.
The challenge
- A messy inherited instance: 22 custom scripts, 18 workflows, 38 bundles, 21 incomplete integrations
- Month-end close taking 15 days, with heavy manual journal volume
- Project work, percent-complete billing, and revenue recognition that native NetSuite was not actually running
- Workforce, spend, and dispatch systems that did not agree with the ERP
SuiteProjects, ARM, and OneWorld turned on for real. Close moved from 15 days to 5. Manual journals dropped about 75%.
- License upgrade and activation of SuiteProjects, ARM, and OneWorld
- Project WBS, job costing, and percent-complete billing
- ARM tied to the work-breakdown structure, not a side spreadsheet
- Stabilized UKG, Divvy, and Dispatch integrations, including a custom Dispatch-to-project RESTlet
- ODBC feed to Power BI for Job Management Report 2.0, plus nightly NSPB loads
- Multi-subsidiary tax, consolidated financials, and subsidiary-specific advanced PDFs
Dealing with the same friction?
Whether you need a clean implementation, managed support, accounting coverage, or a native automation, Salora will meet you where the work actually is.