I think these platforms just have a ton of features slapped together that barely function and have no thought given to UX, but they check whatever boxes their sales team need.
My city uses a similar platform. The explosion of pickleball required a scheduling system. They were able to implement that system in a few days, although it sucks, it works.
> But adapting the software to the state’s unique regulatory needs proved challenging
A good example that's not taught in CompSci, generic software is an unsolved problem.
In a school environment we contracted someone to write room booking software (A while ago, don't need a list of current solutions)
That's crazy, in an environment that's extremely similar across the worlds schools and also overlaps with non-school environments.
The "unsolved problem" has a lot of elements, bureaucratic, entropy, the value of differences.
But one thing we always see in these $100 million case studies is the government workers won't have specced it properly, so blame will fall back.
The cost is surprising but accurate much as every noob could "write it in a weekend", the fact it doesn't work is tricky.
Switzerland recently made open source mandatory for the public sector. Whether it is mandatory or not in any geography, its use ought to be something to strive for, not only to maximize reuse, but also to achieve a higher quality result in the process.