Searching online, I found many different approaches to Project Proposals, all of them presenting different strengths and weakness.
Hereafter, two examples:
The first one, “Sensing neighborhoods”, is a 2014 project that analyse how future technologies can promote stronger relationships among neighbours in Pittsburgh area http://www.slideshare.net/00o000/finalpresentation-30304268?qid=e5dde493-b635-435f-977d-8b3491da8777&v=&b=&from_search=30 (Links to an external site.).
The project is catchy and presents contents in a very clear way, also using info-graphics in order to better clarify all those information that would require a long description. Graphs make all details more clear and easily develop each step in a more simple way.
Objectives, context and outcomes are well defined, but, unfortunately, the path is interrupted, instead of progressing, when the project should concretely explain how to proceed and what kinds of technologies should be used in order to reach its goals.
At this stage, the proposal becomes extremely vague and does not offer indications related to potential budget/funding, timescale and how the project might position itself among all different existing platforms (and how it could “collaborate” with them).
The second one is a 2015 Marketing Proposal related to an Android and iOS app, Made in Ukraine, with the aim to improve “Your business” http://www.slideshare.net/ssuser170f381/commercial-proposal-51621287?qid=e5dde493-b635-435f-977d-8b3491da8777&v=&b=&from_search=29 (Links to an external site.).
Meanwhile the provided services, the costs, the technical background (explained for non users) and the general audience are clear, they only provide, as an example, a small business like a restaurant or a café, without explaining how the same model could be applied to a bigger business’ reality or to a different one.
The presentation is not really catchy and does not give the sense of the diversity of the project itself, that, in this way, looks like any other customer service/fidelity program, not offering something different and/or explaining to such a difficult audience, like small businesses one, why spending money in such a tool and not in another one might be the best solution for them. They don’t even provide some interface examples to make this tool become more interesting to the reader, that, in this way, does not know what to exactly expect (and small businesses owners often want to know in advance what to expect for).
I think both Project Proposals are interesting but incomplete, somehow: probably the best solution could be to join their strengths and create a new presentation out of them. Must be said that, in my opinion, there isn’t an exact formula to write the perfect Project Proposal, all depends on aim, context and situations. Some parts might be missing on purpose, but, in that case, the reader should be enable to understand why they are not included or necessary.
The main point, anyway, is that any presentation or proposal should be catchy and appealing, not only complete in most of its parts, since a Proposal is created when we want to “sell” a concept, an idea: contents are vital, but the packaging is very important, too.