sounds like 100k is a lot more than you need for a solid version 1 if you cobbled together a tool with no programming skills.
1. write a 1 page summary of the product and feature set, with the requirements above. be detailed enough to cover the requirements; you can still make this document pretty vague if you're worried about disclosure but you're going to have to reveal the product at some point - i wouldn't sweat it too much as you're not going to be posting this around the web.
2. make a list of requirements, one to two sentences for each feature; put requirements into buckets - priority 1,2,3. focus on building the pri 1 features in the first version. _be ruthless about keeping this feature set small_. don't say things like "iphone client" - that's too big - more like "a web client dashboard with my sales funnel, with ability to sort, filter, and query". then describe what type of filtering, querying, etc in separate requirements. then "an iphone view of my sales funnel with a simplified list of fields", "ability to respond to emails via the iphone client", etc.
with this summary and list of high level requirements, you can start soliciting developers and getting feedback on how hard it will be to build; you could try odesk/elance but i'd stay away from those because they're better for finding lone wolves and not cohesive teams. if you do use them, don't pick the cheapest people - there are some other threads on HN about how to do it successfully.
you will learn a LOT by seeing how your potential developers respond to this "RFP" - if they have detailed feedback, ask good clarifying questions, and can point to similar projects and have anecdotes of what made past projects work, then you're on the right track.
i both bid on and subcontract work and i've found that i can tell very quickly by the questions a potential developer asks whether the project will be successful. with this budget you don't want to hire a solo guy but be wary of the teams where the BD/sales guy promises a lot but doesn't seem to be adding a lot of value - it's better to work with teams where all the members are technical and participating in the actual end result.
actually, there are some people i could possibly recommend, email me.
1. write a 1 page summary of the product and feature set, with the requirements above. be detailed enough to cover the requirements; you can still make this document pretty vague if you're worried about disclosure but you're going to have to reveal the product at some point - i wouldn't sweat it too much as you're not going to be posting this around the web.
2. make a list of requirements, one to two sentences for each feature; put requirements into buckets - priority 1,2,3. focus on building the pri 1 features in the first version. _be ruthless about keeping this feature set small_. don't say things like "iphone client" - that's too big - more like "a web client dashboard with my sales funnel, with ability to sort, filter, and query". then describe what type of filtering, querying, etc in separate requirements. then "an iphone view of my sales funnel with a simplified list of fields", "ability to respond to emails via the iphone client", etc.
with this summary and list of high level requirements, you can start soliciting developers and getting feedback on how hard it will be to build; you could try odesk/elance but i'd stay away from those because they're better for finding lone wolves and not cohesive teams. if you do use them, don't pick the cheapest people - there are some other threads on HN about how to do it successfully.
you will learn a LOT by seeing how your potential developers respond to this "RFP" - if they have detailed feedback, ask good clarifying questions, and can point to similar projects and have anecdotes of what made past projects work, then you're on the right track.
i both bid on and subcontract work and i've found that i can tell very quickly by the questions a potential developer asks whether the project will be successful. with this budget you don't want to hire a solo guy but be wary of the teams where the BD/sales guy promises a lot but doesn't seem to be adding a lot of value - it's better to work with teams where all the members are technical and participating in the actual end result.
actually, there are some people i could possibly recommend, email me.