You have access developers who write applications for sale they are prepared to battle with IT to get their product deployed. There is a financial incentive.
You have the altruistic employee who wants to help other employees. If you fall into the second camp life is going to get harder for you. You may want to reconsider and let the organization buy a canned product.
When I worked for one of the Big 4 banks in the UK as an admin person, they asked me to create a small system, just so we could do our admin work more efficiently. Flow leaders were spending an hour each morning working out the allocation of work for us plebs.
I created that DB and my flow leader could not help but show it off to a manager who was opening another site for the same work and reviewing our processes.
Big boss man asked her if she had seen all she needed to see and had everything she wanted.?
She responded 'I want the Payment Allocation Database'. !
Big boss man said 'What on earth is that'?
After a few words, the directive came down, 'Stop using the PA DB immediately'.
The IT department were required to check it, to make sure it was fit for purpose. This was after they had refused to create such a system themselves, and would have certainly created it a lot quicker than I did.
I had left by then, but it was passed for future use, but the IT dept charged my old dept £11K for this, when any of the experts here, could have done it in a few hours. It did not interface with any bank mainframe systems.
In contrast the IT dept created an Access DB that allowed numerics in first and last names and we were constantly sending cheques to Mr firstname SA11 4GH etc.
Now you will say, why would anyone put numerics in a name.? This was due to my colleagues having to copy from one Access DB to another and had to do about 200 a day, so kept making mistakes by pasting into the wrong control.