FWIW, these are exactly the kind of statements that would raise red flags for me as a developer. They practically scream, "I will undervalue your work." If these statements are true, you don't need a technical cofounder, you just need to do some homework to see how many of the pieces you can put in place yourself. If that's too hard, be prepared to admit that the task will be a technical challenge.
I think you make an excellent point - those were the same red flags that caused me to add the edit when I re-read my post earlier.
FWIW I am open to being proved wrong, and I think you've nailed the main issue that arises between 'businessmen' and 'technical' founders ... lack of awareness of the other side. It's clear which camp I'm in!
The sad part about that fact is that lack of awareness affects the business man far more than it affects the developer. They end up shooting themselves in the foot time and time again while they filter themselves out of the pool of prospective clients for the good developers.
No disrespect intended to you, but the onus is on you to understand why developers are so important (if you start thinking of them as your product, the picture becomes clearer) because the good developers don't have the time or the need to help you see the fallacy in your perception of roles.
As for your question, I would have it developed if you don't have a good lead on a tech co-founder. technical personnel get approached with "build my idea" all the time. When they do, they hear "hey do all the work and I'll take half". Which while not entirely a correct position to hold, one has to understand that a good deal of developers have their own ideas, if they are going to work for free they are going to do it on their interest and without cutting someone else in on the deal.
Having invested in a product, no matter the quality of the code, and getting the business off the ground will "put your money where your mouth is" with a technical partner. They will see that you are serious about your idea and that you are willing to put in what is needed to succeed.
If the code is sub par they will still see that you have a very good working prototype that has a lot of learning's rolled up into it. It gives them a head start on writing the next version that incorporated the learning of the "prototype".
"Nothing that hasn't been done before..."
"I imagine an experienced hacker..."
"So there's little technical challenge..."
FWIW, these are exactly the kind of statements that would raise red flags for me as a developer. They practically scream, "I will undervalue your work." If these statements are true, you don't need a technical cofounder, you just need to do some homework to see how many of the pieces you can put in place yourself. If that's too hard, be prepared to admit that the task will be a technical challenge.