Off-the-shelf software is the right answer when your process is the one the vendor designed for. It becomes expensive when the real system is a set of spreadsheets around the product you already pay for.
Custom software earns its keep when the operating model is the advantage: inventory rules, booking exceptions, approvals, or a dashboard operators will actually open. The benefit is not uniqueness for its own sake. It is software that matches the work.
A good custom programme is smaller than people fear. The first release should replace one painful workaround, with integrations to the systems that must remain.
Ownership matters. If the build cannot be handed to another team, you have bought a vendor, not a system. Standard stacks, documented APIs, and runbooks are part of the benefit.
We still recommend buying when the score says so. The value of a custom conversation is that the organisation knows why. This is commentary from a fictional delivery practice.
Share a short brief. We work discovery-first, treat security as default, and will say honestly whether we are the right team - then what a first release could look like.