[ashimema]

Think I agree with the above actually, making the software goals up front and centre would certainly help the case.

I realise there are a bunch of goals there, but having them nearer the top and with a one line description of what they actually mean in the grand scheme would help a corporate sponsor understand more what they are funding.

For instance, what does '(70%) Proper relationship options/conditions' actually mean. Does is make a performance boost, a productivity boost for my developers, a functionality boost (with functions we actual wan't/need), a stability boost.. or all of the above.

This might be clear to developers, but it's likely not developers who hold the purse strings. If one can point and say, this should make my developers more productive, or.. this 'should' (provided I'm making the most of it) increase the performance of my app is a much more tenable thing to put money into.