Let's say I choose to hack together an interpretation layer for an API that another team controls instead of fixing their API's underlying issues. I'm deliberat

Let's say I choose to hack together an interpretation layer for an API that another team controls instead of fixing their API's underlying issues. I'm deliberately choosing to write worse code for some business purpose (prototyping, legislative deadline, evaluating one API out of many, etc.). We assume that in the future other business purposes (stability, maintainability, other teams using the product, we decided on a direction) will necessitate more work to fix this hack. I need to explain to non-technical people that this will eventually need more work to be fixed. What metaphor should I use to explain taking on temporary business risk now to save time, then spending more time in total to fix it in the future?