The gap is not “which side looks more advanced.” It is whether your exceptions can enter the software. Free goods, splits, borrows, project milestones, a tech waiting on parts — if two of those are routine, packaged software starts pushing the floor around it. The 4×4 below is not a feature list. It is four questions times four ways of working.
Packaged suite Packaged + config Packaged + light custom Custom to the work
The real line: can you change the structure, or only the skin
Packaged software fits companies with few exceptions who will change the floor to fit the product. Config can absorb some of that — if the vendor really opens approval and fields, not just the logo. Force-fit when it misses the floor and you pay a subscription and go back to the sheet. The path is in When SaaS does not match how the floor actually works. Full ERP vs. modules first is in Should a mid-size company buy ERP first, or start with custom modules.
Custom costs less rework, not more menus
What you pay for is turning “who may change price, who may ship, what happens on a stockout” into running rules, and piloting on real documents. Extra menus are not custom. How to estimate cost and cycle is in What a custom business system costs and how long it takes. Sheets look free until volume grows. See Excel inventory breaks once volume grows.
Vendor lock and data export belong on the matrix too
If you stop paying for packaged software, can you export history and move it. That decides rent vs. own. Custom also needs a written owner for source, deploy, and docs. Compare only monthly fees and you discover in year three that you cannot leave. Fields that miss the floor with no way to change structure is the common lock. Growth adds exceptions and tightens it. See Why growth requires an operations system of your own.
Three questions are enough. First: how many exceptions must happen every month, and can you drop them. Second: must the current finance or warehouse software stay. Third: does phase one only need one main chain to run. Answer those and your cell on the matrix is clear. Visible efficiency shows up after the main chain actually enters the system. Extra menus are not done. See The efficiency a business system can make visible. DaXi Technology will not call a reskinned suite “custom.” Simple needs get a configured package. Needs stuck on the state machine get work-shaped software. If sales and finance still keep separate customer files, custom is only a new skin. See Sales and finance looking at the same customers and contracts.
Send current fields and floor actions to the Business systems service page. The comparison is faster than shopping price first. If work-order states are locked in the package, after-sales stays in the group — and the matrix should lean custom.