I’ve had some similar thoughts, which I documented here (https://www.alexhudson.com/2017/04/26/articulating-atom-approach/). I advocate using Make as the primary developer UI (so devs on your team know each project is standard: they can clone it, ‘make dep’ and ‘make build’ and they have a working version, for example). But, I don’t advocate going to deep into Make — I think it’s better to wrap up pieces of the build process using other tools. When you’re using things like Docker (for example), Make’s dependency management goes out of the window anyway.
I do think there is a potential opportunity for a simple build co-ordinator; Make isn’t perfect for this role, but it is ubiquitous.