So, we add another salary to the team for something that amounts to a small project? If devs don&#x27;t have the acumen to deal with &quot;clients&quot; directly, then they ought not take on projects that would require working with clients.<p>I see this all the time, especially with offshore development. I was the lead for a US project with an additional India team. We had a US-based PM for the Indian contractor. Then we had an India based PM, then we had 3 developers. Any time I needed to discuss something, I had to consult with the US PM, the US PM consulted with the India-based PM and the India based PM would then ask the devs. Then the answer would go through that path in reverse. A simple question like, &quot;Where is the setup script file in the repo?&quot; That took literally 6 emails, with delays of several hours between responses.<p>Needless to say, that arrangement didn&#x27;t last long before I fired the company.<p>My point is that you don&#x27;t always need an experienced project manager depending on the scope of the project and the number of developers. 10 devs -- yes absolutely. But 2 or 3 devs? Not necessarily.