Thanks for asking.
But I have to agree with alt on one thing, we need a budget and control spendings. Just because we have some money it doesn't mean we can spend it on stuff just because they sound like good ideas. We need a budget...
We need a plan. We don't have one.
...
I agree with Akado. This project has a good cause and it needs support from the big stakeholders.
Perhaps by addressing their concerns, it would help gain their support. How about working on the following (if possible and viable) ? :
1) Is there a detailed function/product specification?
Please see OP, the first page.
2) What is the projected number of transactions using the new percent-based transfer function (an estimation based on some figures would do)? From there we can derive a projected revenue.
Sorry I didn't get your point. However, revenue largely depends on sales/marketing/direction of the whole platform, and the over all fee schedule matters a lot. If flat fee is 30 BTS and percentage fee bottom is 1 BTS, more assets will adopt percentage fee; if flat fee is 1 BTS and percentage fee bottom is 1 BTS, few if not zero asset will adopt it. Since there is lack of stable pricing strategy right now, I'm unable to give out a estimation.
3) A cost breakdown would help.
- What are the tasks?
- How many manhours needed for each task?
4) Cost comparison.
- How is the cost of source code development and documentation manpower as compared to the market? Some figures to compare would help.
Sorry, but manhour is nonsense. We're selling products, not labor force.
5) What are the deliverables? What is the roadmap/timeline for the tasks and deliverables?
Please check OP.
6) Warranty for the function/product. How long is the warranty that ensures a working function/product as stated in the specification?
I think one year of warranty is fair.
Maintenance work due to other changes is not included.