The package cannot see this company
Off-the-shelf software is built for the average workflow. That is why it is cheap, and why it is blind.
It cannot see the Friday exception, the approval that lives in one person’s head, the month-end case the vendor did not model, the unofficial record the team already trusts. Configuration will stretch a field. It will not invent a job the product was not designed to hold.
We already wrote about why context-right beats vibe-coded, and about the unofficial tracker that became the system. That tracker is usually evidence. The package missed something. People filled the hole.
Buy commodity. Build the exception layer.
The 2026 internet is full of custom-versus-off-the-shelf tables. The honest consensus is already hybrid. Keep it.
Buy the functions every company runs the same way. Do not rebuild a calendar, a mailbox, or a ledger because you can generate one.
Build the layer the package cannot see: the exception path, the write rule, the handoff, the unofficial source of record. That is custom software that earns its keep. User research is how you find those exceptions before you commission the layer. Last mile is how you ship it into what you already run.
A workaround is not proof you need to replace the whole suite. It is proof of misfit on one job. Encode that job. Leave the commodity packaged.
When configuration is not enough
Configuration is enough when the vendor’s object model already contains the work, and you are naming fields.
It is not enough when:
- The real process lives in a file, an inbox, or a side tracker
- Two people must agree on a write the package treats as one
- The vendor’s roadmap will not hit your timeline
- Month-end, receiving, or payroll stops if the unofficial path disappears
Then you are not “not using the software hard enough.” You are asking a product built for the average company to see a company it cannot.
A short test
Before you buy another module, or generate another screen, ask:
- Which exceptions does this package have no object for?
- Where is the unofficial system of record today?
- Does the vendor’s timeline match the week you actually have to run?
If the answers are “ours,” “a spreadsheet,” and “no,” you do not need another listicle about custom versus packaged. You need the exception layer.
If the package cannot see the work, talk to us about the layer it is missing, not a second suite.
Questions
What can off-the-shelf actually not see?
This company’s exceptions. Tribal approvals. The unofficial record. The Friday case the vendor did not model. Average workflows, it can see. Yours, only if they are average.
Is a workaround proof of misfit?
Usually. The file, inbox, or side tracker is the job the package would not hold. It is not automatically proof you should rip the suite out.
Should we buy commodity and build the exception layer?
Yes, when the commodity is actually commodity. Build only the path the package cannot model. That is the hybrid the comparison tables already agree on, without saying how to find the path.
When is configuration not enough?
When the object model does not contain the work, the unofficial record is load-bearing, or the vendor’s roadmap is not your week. Then you are past settings. You are in software this company has to own.