You are under pressure by client to deliver. My ex-colleague totally screwed you up. And now it seems I am going to take over his job with a uphill task of unscrew you up. You didn't realise that before I can unscrew you, I need to reduce the impact of him screwing you up. Refactoring has no business value. So you will not factor in the time for refactoring. Even though you said it will come in later. And your later will never come. Because you fail to release the important of refactoring. Let me tell you a scenerio that will happen for sure. The project will not be complete/reach the schedule time/milestone. You ask why? You wouldn't understand even if I explains. Because if you would, then you wouldn't take this decision path. Don't be surprise I totally understand how your decision path. The cycle will continue. The inevitable which is totally untrue. But the untrue is a myth in the path you have taken. Project milestone not met. Client unhappy. Quick fixes. Client unhappy. Quick fixes. Client unhappy. Quick fixes. Sign off. Project moilestone not met. Client unhappy. Quick fixes. Client unhappy. Quick fixes. Client unhappy. Quick fixes. Client unhappy. Quick fixes. Client unhappy. Quick fixes. Client unhappy. Quick fixes. Sign off... and so on. The effort needed after each phase will just increase. Have you learn about the big O notation?