Earlier quoted context omitted.
The alternative is to build purpose built software, but that would require this municipality to pay SWEs (among other folks) directly. An interesting case study would be if it were actually cheaper in the end to just employ some software engineers and write something catered to themselves.
Yeah, I don't think it would be any cheaper, or any likely to meet success. Succesful software development is hard, whether you hire a consultancy or are a non-software company trying to create an in-house department. Software around workflow (an ERP) is one of the most challenging areas. Because it is hard to shoe-horn it into a universal pattern, or figure out what a given organization actually needs (not always wh…
I think it actually requires the organization to morph into being a tech company first. In order to have good software to run a City Council, it effectively requires the Council to become "a software-making organization that delivers council services". In order to have good software to run a bank, it requires the bank to become "a software-making organization that delivers banking services".
Unfortunately, it's both politically difficult (nobody goes into any type of non-IT activity because they want to work with software) and really challenging: not even IT organizations have figured out the best way to address problems like technical debt, language churn, documentation etc, and non-IT organizations face them just as much.