My suggestion to you would be to decide what the business value is of the program and it's future needs. If it's a program that will need to change, be refactored, revamped, etc... then spending...
My suggestion to you would be to decide what the business value is of the program and it's future needs. If it's a program that will need to change, be refactored, revamped, etc... then spending the time to make sure it can do those things is worth the effort. If it's basically just a one and done and you only need it to keep up just long enough, then you obviously spend considerably less effort on it. So basically I would frame it more as how much value is it to the business and make your decision from that.
My suggestion to you would be to decide what the business value is of the program and it's future needs. If it's a program that will need to change, be refactored, revamped, etc... then spending the time to make sure it can do those things is worth the effort. If it's basically just a one and done and you only need it to keep up just long enough, then you obviously spend considerably less effort on it. So basically I would frame it more as how much value is it to the business and make your decision from that.