Test earlier to avoid wasted time, resources and money.
Making a wireframe equivalent in recording is, where i am not looking for final production qualities, but depending on the need, showing rough recordings and asking if anything has to be changed, particularly to:
the melody used
or the chords in the case of arranging
When agreed upon, the next level, questions related to the final sound:
the sound of the instrument
the quality of recording
anything interfering, like reverbs or noises that I missed or any gates etc (in cases where the artist uses one)
This is true about remote working, which is what is going on a lot nowadays, where the internet breaks regional barriers for us to work together.
In a situation where we are physically present in a studio too, sitting with a vocalist or instrumentalist, we don’t have to start the final recording. Give what is to be played or what they have to build based on your needs. Listen to what needs to be changed. Finalize and produce.
The reason is simple: Why waste time on a perfect production before agreeing if the melody or rhythm or tempo or timing is correct or not? Those are areas that dont’t depend on the sound quality.
Sound quality takes money and often time – recording correctly and patiently with as many takes and edits as needed, working the final sound by oneself or in a studio or with a sound engineer.
INstead separate the elements of the recording. Keep final production for the final stage, just like in a wireframe kind of UX design.