Some good ideas here, but I have some questions/thoughts about them:

• Question about type of funding: the Hive fund pays out daily (well, hourly really). So what would advance payment mean in this case? Does it mean work wouldn't start until the proposal ended?
• Also it seems like a project could want some "back pay" for previous work and some advance payment amount needed before principals will be willing to take on the project. So maybe it's better to have a section that describes the use of the funds (back pay, one time payment, recurring costs) and minimum funding requirements.

For the KPI section: first I should state that I personally hate "business speak" terms like KPI. As an example of why I don't like it, I've been running a successful business for 30 years, and I didn't know the term "KPI". So in my opinion, most business terms should be avoided whenever there's normal words for the same thing, especially when we're making proposals that will be voted on by people that likely aren't business majors.

Nonetheless, I think the concept you're getting at here is good, at least for some proposals. If I understand the KPI concept, it means establishing measurements for the success of a project. For some proposals, this may be easy to do. For example, if you create an advertising proposal and the proposal is able to track referrals in some way, then that should probably be mentioned in the proposal.

On the other hand, I think for a lot of proposals, the measurement of its success is going to be much more difficult to measure in numbers. I'm not disagreeing that it's nice when we can make such a measurement, since it makes the whole process more "scientific" and easy to make judgements about its success, but I think it's probably too much to expect every proposal is going to be able to suggest such a set of measurements.