> All insourced code is future maintenance expenditure. You need to balance that to the benefits.

I love this perspective. I feel like the pendulum has swung too far back to "it's easy to build, it'll be easy to support". But to be fair, it was probably too far the other way a few years ago: "it was easy to buy, it'll be easy to have them support it".

Other than trial and error, how do you think about pricing out maintenance costs for insourced code vs purchased functionality?