9 Ways To Improve Your Executive Summary

Want to improve your executive summary? Here are nine ways you can improve the style, language, and effectiveness of the executive summary for your next business plan or proposal.

Download Now – Buy Here!

Download Templates Here

[Learn more about these Business Plan templates here]

The Executive Summary creates difficulties for many proposal writers. Is it part of the business proposal or is it a separate document? How long should it be? Should it include costs?

  1. Define the purpose of the Executive Summary

If you’re new to proposal writing, it’s easy to confuse the Executive Summary and the Introduction. After all, both seem to be doing the same thing. And they are, to a degree.

However, the Executive Summary is really the ‘elevator pitch’ for your Business Proposal.

If we see it in these terms, then we need to change the tone, structure and ‘hooks’ to capture the reader’s attention.

  1. Write it as a Separate Document

One way to write the Executive Summary is to think of it as a standalone document.

In other words, if you took it out of the Business Proposal… it would still make sense to the reader.

When you look at it like this, you realize that you don’t need to write it before the proposal is finished. Instead, you can set it aside and develop it after you’ve completed the rest of the bid.

  1. Develop Themes

Themes are an interesting way to develop the Executive Summary. What this means is that you choose a theme, for example, reputation, and then develop the bid around this theme.

Why create themes?

It adds a human element to your proposal. Instead of responding only to the requirements, you go deeper and explore the underlying pain points and needs of the customer.

This makes the document much more interesting to read as it speaks to the reader on an emotional level.

  1. Problem Statement

What you’re doing here is three things:

  1. Identifying the underlying problem or need that exists
  2. Confirming how you’ve recognized this and
  3. Why you’re expertise will address this

In this section, try to connect with the deeper underlying issues.

For example, why does the client need a content management system? Do they feel threatened or risk getting left behind.

These issues may not be identified in the Request For Proposal, but you as a proposal writer need to tease them out – and then weave these into the fabric of the proposal.

  1. Proposed Solution

Remember that you may be writing for more than one reader.

In other words, your Executive Summary may be read by the:

  • CEO
  • Finance Manager
  • IT Manager
  • Quality Manager
  • Procurement Officer

…and so on.

For this reason, keep the text light, focused but not too technical. Avoid using jargon, three letter acronyms, and other buzzwords.

Give a short description of the proposed solution. Identify:

  • How it will be managed
  • Who will benefit from the solution
  • Where it will be implemented
  • How long it will take to develop
  • Who will maintain it
  1. Costs

You don’t need to break down costs by line item; however, the evaluators will expect to see the total cost required for the project.

Don’t try to fudge it and bury the costs in the document. This sends out the wrong message. If you’re confident in your figures, show it in the summary.

If you want, you can also discuss the payment structure. For example, state that the client is expected to pay 15% upfront and the balance at different intervals.

  1. Expertise

You need to demonstrate your expertise – but how?

One way to do this is include an endorsement from a respected industry figure. This works for two reasons:

  • It shows that another person (or company) is willing to vouch for you, which reduces anxiety in the reader.
  • It shows that you have a track record in the industry and aren’t another ‘fly by night’ company.

You can also look for ways to highlight your qualifications, industry recognition, and other prestigious projects you’ve worked on. Social proof is very important.

  1. Length

There are different schools of thought on this.

I prefer to keep it to one page.

In this way, if it’s printed out, the reader doesn’t have to keep the pages together. They can scan it and absorb the key points in one go.

Whereas, when you add a second page, you break the momentum. You don’t want them flicking back and forth checking what you’ve said.

Remember to use a large, easy to read font. Don’t make the decision-maker strain to read your text. The may not have the same excellent eye-sight you possess.

  1. Proofreading

The last step is the hardest – proofreading.

Read: 20 Proofreading Exercises

Try to avoid proofing your own document. Instead, ask a colleague to check it for you. If this is not possible, take a look at these twenty proofreading guidelines.

The key to effective proofreading is to assume there are mistakes. Check facts, dates, figures and numbers. Print it out and read the document from the End to the Start.

Why?

This technique forces you to pay attention; you can’t get into a momentum. Another tactic is to read the Executive Summary aloud and check if the tone sounds right.

Conclusion

Writing an Executive Summary takes dedication. Instead of writing it first to get out of the way – so you can get into the real document – see it as a separate piece of work.

Identify the core messages you want to convey, emotional triggers you want to evoke, and create a sense of urgency.

Over to you.

How do you write Executive Summaries? Do you write them before or after the proposal?

More Executive Summary Writing Tips

  • Aim to summarize the key points of the main document.
  • Write it after finishing the main document.
  • Use words, phrases, and terms that your reader will understand.

  Download Now for only $19.99

Download Template

Learn more about this Proposal Template

Thousands of templates to jump start your project

Acceptance Test Plan

Contingency Plan

Software Development Templates

Acquisition Plan

Conversion Plan

Software Requirements Specification

Action Plan

Cost Benefit Analysis

Software Testing

API Documentation

Database Design

Standard Operating Procedures (SOP)

Audience Analysis

Datasheet

Statement of Work

Availability Plan

Deployment Plan

System Administration Guide

Bill of Materials

Design Document

System Boundary

Business Case

Disaster Recovery Plan

System Design Document

Business Continuity

Disposition Plan

System Specifications

Business Plan

Documentation Plan

Technical Writing Templates

Business Process

Employee Handbook

Test Plan

Business Requirements

Error Message Guide

Training Plan

Business Rules

Expression of Interest

Transition Plan

Capacity Plan

Fact Sheet

Troubleshooting Guide

Case Study

Feasibility Study

Use Case

Change Management Plan

Functional Requirements

User Guide

Communication Plan

Grant Proposal

Verification and Validation Plan

Concept of Operations

Implementation Plan

White Papers

Concept Proposal

Installation Plan

Work Instructions

Configuration Management Plan

Interface Control Document

Software Development Templates

Acceptance Test Plan

Maintenance Plan

Software Requirements Specification

Acquisition Plan

Market Research

Software Testing

Action Plan

Marketing Plan

Standard Operating Procedures (SOP)

API Documentation

Needs Statement

Statement of Work

Audience Analysis

Operations Guide

System Administration Guide

Availability Plan

Policy Manual

System Boundary

Bill of Materials

Project Plan

System Design Document

Business Case

Proposal Manager Templates

System Specifications

Business Continuity

Proposal Template

Technical Writing Templates

Business Plan

Quality Assurance Plan

Test Plan

Business Process

Release Notes

Training Plan

Business Requirements

Request for Proposal

Transition Plan

Business Rules

Risk Management Plan

Troubleshooting Guide

Capacity Plan

Scope of Work

Use Case

Case Study

Security Plan

User Guide

Change Management Plan

Service Level Agreement (SLA)

Verification and Validation Plan

Communication Plan

Setup Guide

White Papers

Concept of Operations

Social Media Policy

Work Instructions

Concept Proposal

Contingency Plan

 

Configuration Management Plan

Conversion Plan