Companies are almost always better off bringing in one experienced consultant that actually knows how to stand up the project and help hire the team to make it happen.
We used to have a very experienced systems engineer that we'd contract whenever a chief engineer had an idea that gained traction with directors. The systems engineer would help layout the structure and timeline of the project, basically identifying how much money and the types of people we'd need. He'd stick around long enough to get the project to the final design review and then go do something else when we started building stuff. By that point, the PM is deeply involved and the team is cohesive and productive. Maybe it's just a coincidence but every big project we've tried to stand up without his help would struggle tremendously in the early stages.
We used to have a very experienced systems engineer that we'd contract whenever a chief engineer had an idea that gained traction with directors. The systems engineer would help layout the structure and timeline of the project, basically identifying how much money and the types of people we'd need. He'd stick around long enough to get the project to the final design review and then go do something else when we started building stuff. By that point, the PM is deeply involved and the team is cohesive and productive. Maybe it's just a coincidence but every big project we've tried to stand up without his help would struggle tremendously in the early stages.