Thank you. 100 pct agree. Hands-off was meant to convey respect for Hacker's process and craft of building out a MVP. As far as customer acquisition, feedback, service -- 100 pct hands-on. For some reason (most likely bad writing) my original post didn't convey that.
The idea would solve a personal pain point. And the MVP would test whether that pain point was felt by others. If not, failing fast is okay.
Relationship with Hacker is key to long term success. If Non-technical isn't plugged into the Hacker community, compensating them is a way to demonstrate seriousness. Skin in the game, so to speak.
Also, I'm speaking in broad terms -- Hacker and Non-technical -- for universal discussion. This scenario could apply to me at some point but I also deal with a lot of clients and associates that actively talk about similar scenarios at barbeques, dinner parties and conference rooms.
I don't have a confident road map to advise them on such a course and I'm genuinely interested in what this community thinks would be the best may to make this situation work -- for the sole purpose of launching a MVP -> shipping -> testing -> refining -> scaling.
The idea would solve a personal pain point. And the MVP would test whether that pain point was felt by others. If not, failing fast is okay.
Relationship with Hacker is key to long term success. If Non-technical isn't plugged into the Hacker community, compensating them is a way to demonstrate seriousness. Skin in the game, so to speak.
Also, I'm speaking in broad terms -- Hacker and Non-technical -- for universal discussion. This scenario could apply to me at some point but I also deal with a lot of clients and associates that actively talk about similar scenarios at barbeques, dinner parties and conference rooms.
I don't have a confident road map to advise them on such a course and I'm genuinely interested in what this community thinks would be the best may to make this situation work -- for the sole purpose of launching a MVP -> shipping -> testing -> refining -> scaling.