Choosing an ERP Within a Tight Budget
CountyLine Distributors has 64 employees and runs order entry, inventory, and customer records in 14 shared spreadsheets. Two employees maintain the macros, and both are near retirement. Last year duplicate orders cost about $38,000, and a stock-count error caused a $22,000 expedited shipment. The owner has a $20,000 technology budget and is considering either a $450-per-month cloud ERP for 22 named users with a $12,000 implementation fee, or a $18-per-user-per-month CRM plus keeping spreadsheets for inventory. A custom-built system quote is $55,000. Customer data includes payment card information, and the company must limit access by role. Staff have resisted past software changes.
1. Calculate the first-year cost of the ERP and CRM options. Which fit the $20,000 budget, and what is left out?
Read the worked answer
ERP first-year cost = $12,000 implementation + ($450 x 12) = $12,000 + $5,400 = $17,400. That leaves $2,600 of the $20,000 budget.
CRM first-year cost = $18 x 22 users x 12 months = $4,752. It fits easily, but it does not fix inventory, duplicate orders, or the spreadsheet macro risk.
Custom build = $55,000, which exceeds the budget by $35,000 before maintenance and training.
The ERP is the only integrated option within the stated budget, but the $2,600 remaining is thin. The implementation fee may not include data cleanup, training, role-based security configuration, or temporary staffing. The owner should confirm scope or phase the rollout so the project is not underfunded at go-live.
2. Evaluate the non-cost factors and recommend a course of action.
Read the worked answer
The operational losses are large relative to the software cost: $38,000 in duplicate orders plus $22,000 in expedited freight is $60,000 of annual pain, well above the ERP's first-year price. The two macro maintainers near retirement create key-person risk, and payment card data plus role-based access requirements favor a vendor with auditable permissions rather than 14 shared files.
A CRM alone would leave the inventory and order-entry problems in place. A custom build is not realistic within the budget and would create a long-term support burden for a 64-person distributor.
The owner should choose the ERP, but phase it: clean customer and item data first, implement order entry and inventory before advanced reporting, use role-based access, and reduce card-data scope by tokenizing payments rather than storing card numbers. Staff resistance should be addressed with process owners, a pilot group, and visible quick wins such as fewer duplicate orders.
3. What metrics and change-management steps would show the ERP is working?
Read the worked answer
Useful metrics include duplicate orders per month, inventory accuracy from cycle counts, expedited freight cost, order-entry time, percentage of orders entered directly in the ERP, access-audit exceptions, and days to close the month. A falling duplicate-order count and improving inventory accuracy are the strongest early signs.
Change management should include an executive sponsor, a named process owner for order entry and inventory, super-users in each shift, data-cleanup ownership, training before go-live, and a short period of floor support. The owner should also watch for workarounds, such as staff keeping shadow spreadsheets. If duplicate orders persist or users continue to bypass the ERP, the project is not delivering even if the software is installed.