This is good advice, and a way to test the feasibility of bringing the work in house. Probably the best way to think about this whole project is not as a proje

This is good advice, and a way to test the feasibility of bringing the work in house. Probably the best way to think about this whole project is not as a project, but as a capability to grow internally. As a big project, you'll get stuck at 80% and never deliver. If you start small and deliver continuously, you'll get stuck at reducing the pain by 80%, which is probably a huge win. Software is grown. Start small and focus on delivering value quickly to build momentum and credibility, but make sure that the team lead knows that your vision is to eventually replace the other systems.