Let others build an MVP without technical skills. How do I break up plans and requirements in bits, so that the chances of success of the contractors rises? How to select contractors? Should I define a stack, or let contractors decoder? Etc. These are obv. the questions OP answers, but as GP points out you need a lot more information to assess the risks in such steps. I wouldn't want to have the next post "How I blew 10K and got nothing in return".

So it's hard. I see people say things like "advertise the product and get a mailing list of people interested, 100k signups mean it's a go", but that has never impressed me that much.

If 1/20 MVPs prove to gain traction, and MVPs cost 10k to outsource, you are looking at spending 200k to find something that sticks.

I think the top thing is to get the scope down. Make it a mVP not a MVP.

Not sure there is a single universal answer. I usually suggest you learn to code so you can do MVP level work for free, but not all people like that answer.

We already got lots of in return, even if there is no revenue yet.