peddletothemetal
Bronze Contributor
Read Rat-Race Escape!
Read Fastlane!
Read Unscripted!
Speedway Pass
User Power
Value/Post Ratio
149%
- Apr 5, 2021
- 110
- 164
(Disclaimer: this is entertainment and I don't know what I'm talking about)
Hit LinkedIn first and try to grow your network out until you connect with people you know who are now programmers and/or are known by people you know. Ask if they'd be interested in consulting and a possible subsequent project.
Once you find someone who will offer consulting, and has a long enough career record on their profile, pay them hourly for discussions. They should be able to tell you what will be hard and what will be easy. However pay attention to how much they use the word "just". Saying it would just take or just need etc several times is an indication they're an idiot or very green in their career (regardless of years of experience), and you should find someone else.
If you don't have money to pay up to this point, your enterprise ends.
They should be able to tell you for instance that scanning in paper won't work cost effectively due to reliability, but what will work too. They should be able to mention some 3rd party services that will do some parts of what you want. If they say 100% should be custom coded from scratch, walk away, unless they explain how the most popular 3rd party services don't cover what you need (which indicates they've actually considered them).
After that you can pay them to write up a plan of how to build the limited MVP you both agree would adequately test the market and most likely be within your budget, how they recommend it be built, and with them adding their quote at the end to build it themselves.
Both the cost of writing the report, and the quote at the end, must be fixed prices. If they use the word "estimate", firmly tell them no, and say you will only agree to a fixed price for a fixed scope of work. If they mutter something about "agile", or won't agree to fixed projects, walk away. But if they agree, don't try to talk their price down. That's the price.
If they present a fixed price to implement what you have discussed would be a good MVP, you will then immediately think the price is "crazy" or the like, and that you will be "clever" by instead having someone in Bangalore you found online build it for you. You will then join the swollen ranks of failed wannabe internetpreneurs who had an idea but got "screwed over".
Alternatively, you aquire funding for that quote, and proceed.
Once that MVP is live, and you've marketed it, and you have confidence that its got interest, it's OK after that point to work out a more flexible development pricing (like hourly or closer to it), and at that point you'll probably want to approach investors.
Hit LinkedIn first and try to grow your network out until you connect with people you know who are now programmers and/or are known by people you know. Ask if they'd be interested in consulting and a possible subsequent project.
Once you find someone who will offer consulting, and has a long enough career record on their profile, pay them hourly for discussions. They should be able to tell you what will be hard and what will be easy. However pay attention to how much they use the word "just". Saying it would just take or just need etc several times is an indication they're an idiot or very green in their career (regardless of years of experience), and you should find someone else.
If you don't have money to pay up to this point, your enterprise ends.
They should be able to tell you for instance that scanning in paper won't work cost effectively due to reliability, but what will work too. They should be able to mention some 3rd party services that will do some parts of what you want. If they say 100% should be custom coded from scratch, walk away, unless they explain how the most popular 3rd party services don't cover what you need (which indicates they've actually considered them).
After that you can pay them to write up a plan of how to build the limited MVP you both agree would adequately test the market and most likely be within your budget, how they recommend it be built, and with them adding their quote at the end to build it themselves.
Both the cost of writing the report, and the quote at the end, must be fixed prices. If they use the word "estimate", firmly tell them no, and say you will only agree to a fixed price for a fixed scope of work. If they mutter something about "agile", or won't agree to fixed projects, walk away. But if they agree, don't try to talk their price down. That's the price.
If they present a fixed price to implement what you have discussed would be a good MVP, you will then immediately think the price is "crazy" or the like, and that you will be "clever" by instead having someone in Bangalore you found online build it for you. You will then join the swollen ranks of failed wannabe internetpreneurs who had an idea but got "screwed over".
Alternatively, you aquire funding for that quote, and proceed.
Once that MVP is live, and you've marketed it, and you have confidence that its got interest, it's OK after that point to work out a more flexible development pricing (like hourly or closer to it), and at that point you'll probably want to approach investors.