My agency has been developing an application that they're hoping will bring in a lot of revenue and they're going about it the wrong way. The agency usually only deals with wordpress and drupal type sites. Our typical client approaches us for 3-6 months of work on a custom theme and then follows up after that with maintenance work.
At the beginning of last year the agency took on a whole new type of client that wanted a web app built, both for desktop and a mobile version for phone. I was hired as a team lead because of my experience with React, React Native, and Node. This job scope is still pretty new to me. So for the past 18 months that web app has kind of been my teams life and we've been sequestered off from other projects.
At the end of last year the other teams started working on a new web app, however, as their main experience is in wordpress, they have attempted to build the entire thing in wordpress. My project is winding down and they've started noticing that the app we built acts much more like an actual app than a website and they want me to apply that to their project. The thing is, for the scale they want this applied to, the project should have never started in wordpress. They're trying to contort a CMS into something it's not. At the very least the only way react is going to play nice with their back end is to change the entire thing into a headless api.
This leaves me with telling them that the months of work they've put into the project were kind of a waste of time as they used the wrong tools from the outset. It's not that they didn't use react but that they didn't use any framework. Almost all of their front end manipulation is done by very hap hazard jQuery. The other issue is that they want to apply some very heavy data analysis to the back end and wordpress was never meant to do things like that so it's causing a massive slow down of the whole thing.
The person who would make the final decision on this has a very profit focused mind though (as a business owner should) and will really focus on 'time to market'. The idea of me saying the concept is great but the whole thing needs to be refurbished will immediately cause him second thoughts on anything I say after that. More so, as many of the original team members are unfamiliar with react, angular, or any other framework it puts them at an immediate loss. I can definitely understand the strength of building in what you know vs learning something new.
For example last week while discussing an npm package we'd used for the mobile version of our previous app the other team noticed we'd solved a big problem they were having and asked us to implement it for them. After looking at their code that's when I realized there was no way to use this npm module without setting up webpack or browserify in the project and they weren't about that at all. After 3 days we were able to write a vanilla js script that did what they needed but I have a feeling this uphill battle is what we'd be in for the entire time.
What is the best way to present all of this to them. I don't want to just say straight up "no we won't work on this as it is" but I also don't want my team taking ownership of the front end of the project only to take blame a few weeks or months from now when it can't perform as they want. Basically I feel like this is going to set us up to fail monumentally.