In short: COTS works best when your policies can bend. In heavily legislated environments, the software usually bends instead, slowly, expensively, and with a spreadsheet quietly doing the real work.
I’ve spent enough time across both COTS and bespoke builds to be confident about one thing: COTS is mostly a series of functional trade-offs. SMEs turn up with real domain knowledge, edge cases, legislative quirks, and the “this only breaks once a year but it really matters” stuff, and then find out pretty quickly that none of it fits neatly inside the platform. So the business bends to suit the software. Sometimes that’s fine. Sometimes it’s just painful.
“It’s configurable” comes with fine print
I still remember a developer trying to build what was described as “simple” functionality in a low-code platform. Watching him slowly question his life choices while Alt-Tabbing between the vendor docs and Seek job ads was… revealing.
Dynamics has its own version of this. A request like “just show related data across multiple parent-child relationships on one screen” sounds harmless, right up until the functional consultant reaches for the how-to guide, the forums, and eventually says, “we may need a workaround.” And even when you finally get it working, you then spend forever making sure it keeps working, so the next release wave doesn’t blow up your neat little bespoke add-on.
Which is why, despite the “it’s configurable” promise, you still end up needing platform specialists. There’s always an asterisk letting you know this only works if you follow the platform’s rules exactly.
Government turns it up to eleven
Legislation doesn’t care about vendor roadmaps, platform constraints, or what was said during the demo. When the law dictates what must be supported, COTS either bends, usually at great cost, or you end up with bolt-ons, custom pages, and a spreadsheet off to the side doing the heavy lifting “temporarily”.
I’ve also seen organisations throw serious money at COTS until it behaved the way they wanted, even when the same thing could have been built by a competent developer in an afternoon.
To be fair, in organisations where policies can move, governance is pragmatic, and change doesn’t take three years and twelve committees, COTS can make a lot of sense. But I keep coming back to the same simple conclusion: legislation is the immovable object. COTS is the thing that has to move.
Choosing a platform matters. Understanding what can’t bend matters more. That’s why we spend time up front understanding the domain reality before we recommend anyone.
Resourcing a platform implementation? See how Talexa supplies experienced contractors.
