Not sure if this helps, but if I were you, I’d: * Create a git repo from the code as it exists * If the other team is still doing things live, create a workfl

Not sure if this helps, but if I were you, I’d: * Create a git repo from the code as it exists * If the other team is still doing things live, create a workflow that copies the code from the prod server to git as-is nightly so you have visibility into changes. Here’s an opportunity for you to see maybe what the team gets stuck on or frustrated with, and you can build some lines of communication and most importantly some trust. You can suggest fixed and maybe even develop the leadership role you need. * Get a staging instance up and running. If I had to guess why the team does things live, maybe the project is a huge pain to get sample data for. If that’s the case, figure out the schemas and build a sample data creation tool. Share with the team and demonstrate how they can make changes without having to risk breaking production (and for goodwill - it helps prevent them from having to work evenings, weekends, and vacations because prod goes down!) * PHP isn’t so bad! Wordpress runs a huge chunk of the web with PHP! * tailwind might be a cool way to slowly improve CSS - it can drop into a project better than other css frameworks IMO * Pitch your way of fixing this to management while quoting the cost of a rebuild from different agencies. Throw in the cost of Accenture to rebuild or whatever to scare management a little. You are the most cost effective fix for now and they need to know that.