Proposal Writing Blog Series, Day 2: Executive Summary

This is part of a five-day blog series on how to write a winning proposal. It will go discuss actually writing the proposal. If you want to get more in-depth information, examples, and what to do before the proposal, check out my “How to Write a Winning Proposal” handbook.

Yesterday, we discussed how to write the cover letter of a proposal. The Executive Summary should be treated like a miniature version of the proposal. It summarizes the high-level points in the Management Approach and Technical Solution. As I stated when discussing the cover letter, you should write it after you have finished the other pieces being that it is a summary.

As with the cover letter, the Executive Summary is the only other section that could be read by anyone. By knowing this, you have to keep the technical jargon to a minimum. Sum up the main points, even of the Technical Solution section, in a way that anyone can understand.

It also is a good area to start building that rapport with the organization, and setting the tone to make them feel and understand that they are the main focus.

A great way to organize the Executive Summary is first stating the problem. The Executive Summary is also a way to show the organization that you fully understand their problem. By doing this, they know that you have tailored a solution that works for them.

The second paragraph should discuss your solution and promise to ensure that the work is always at its highest quality. Please remember to keep the jargon to a minimum. Anyone, regardless of their knowledge of the intended subject matter, should be able to pick up the Executive Summary and understand what you are trying to say.

The third paragraph should discuss your organization and its management approach. Even though it’s discussing your company and its strategy, you should tailor it so it still makes the client feels that it’s all about them.