That internal budgeting app isn't a top priority because it isn't
user facing. The company has enough interns in accounting with Excel experience and one of them knows
macros and Access (or PowerApps, or for some horrifying reason, VB6). Of course their math is wrong and they don't know anything about the software they are budgeting across departments and it still just defaults to just bucketing everything as "unclassifiable overhead" rather than revenue departments, but now its in an Excel macro spaghetti ball black box so it is less obvious, and by the time scale up gets out of hand for Excel/Access/PowerApps/VB6 and programmers are actually forced to be assigned to look at the spaghetti ball, because the business might finally collapse at that scale, all of the C-Suite are so used to seeing the reports and the numbers the way they are and programmers aren't as smart as accountants when money is involved and should recreate the system exactly as it
was rather than implement improvements, such as say domain expertise of software projects and their revenue models.
Not that I've bitterly seen multiple versions of that in my career or anything, this is still just purely hypothetical complaints department, eh?
