It all starts with the project proposal. From million-dollar ad campaigns to thousand-dollar one-pagers, so much of your agency’s success depends on sending persuasive proposals. This guide will show you how to create more compelling project proposal outlines.
Of all the documents you’ll create while running a project, few are more important than the project proposal.
This tiny document is the seed that gives birth to million-dollar projects. You’ll use it to win new clients, persuade sponsors to increase funding and convince existing clients to renew their contracts.
A great project proposal is at once informative and persuasive. It may revolve around data, but it doesn’t shy from using marketing copy. It is, at heart, the distillation of several skills - project management, data analysis, copywriting, etc.
Given this expansive brief, writing a convincing project proposal can be a challenge even for agency veterans.
In this guide, I’ll share 7 tips you must follow to create more convincing project proposals.
The project proposal isn't just a project management document. It is also a marketing document.
And as with any marketing document, you have to keep your audience in mind when creating it.
In practical terms, this means using the same language, tone, style, and level of complexity as your audience.
If your audience is a veteran CTO, feel free to pepper in jargon. If it's a small business owner who has never touched a computer before, dumb things down.
Doing this means that you have to research your audience thoroughly. LinkedIn is your best friend here. Dig through their profile and approximate the following:
Publicly shared interests and group memberships show what your target audience is interested in.
Use this information to create a rough sketch of the target, such as this:
A rough profile or persona sketch can help you create a proposal that speaks directly to your target audience.
This will tell you how much detail you should include in a proposal. A veteran CTO, for instance, might want to know the technical details of your proposed solution. A small business owner might be more interested in the impact on his bottom line.
A client might reject your proposal for any number of reasons. Perhaps he isn't sure of your ability to deliver results. Or perhaps he has a better price than a competitor.
But as Francis McNamara points out, most proposals are rejected because of a failure of persuasion, not a failure of process.
It is very seldom that sponsors discard proposals because they don't have enough data. Rather, it is because you failed to make the data compelling enough.
Addressing this root cause of the proposal requires two things:
Within the context of a project proposal, persuasion means two things:
A mistake you can make is to assume that the motivations of the business and the decision-maker are the same. While there is certainly a big overlap, decision-makers also have independent goals and ambitions - to get a promotion, to improve their department's performance, etc.
Your goal should be to highlight the project results that will benefit the decision-makers the most.
For example, your project might have two key benefits - improving website performance by 20% and increasing online sales by 5%.
Persuasion defines what you say in the project proposal. Clarity defines how you say it.
In practical terms, clarity is a function of the proposal's formatting, tone, and copy. Your target shouldn't have to read through two pages before understanding the project's key benefit. Nor should he have to trawl through paragraph after paragraph of jargon.
To be clear, then, is to:
In a 2009 PMI conference paper, Eddie Merla, says that one of the chief causes of project failure is “weak justification”.
He says:
“Sometimes the concept may be properly stated but the justification for the project is weak… the lack of justification indicated a lack of commitment on the part of the team to build a compelling business case.”
This is a frequent problem on technical and creative projects. The technical or creative problem might seem substantial enough on its own. But if you can’t connect it to a business issue, you’ll struggle to justify the project’s existence.
One way to do this is to tie a dollar figure to the problem. Focus on what the business stands to lose if it doesn’t solve the problem. Since people are more likely to avoid a loss than to seek a gain (i.e. loss aversion theory), emphasizing the loss can sell the urgency and impact of the project.
For example, in a project to improve website speed, focus on how slow websites lead to abandoned carts and thus, a loss in revenue.
Try using ROI analysis to figure out the project’s impact on the business. Don’t focus on the exactness of your financial metrics. Rather, focus on their completeness.
At the very least, your proposal should highlight the following:
A project with a “strong” justification would have a large difference between the project impact and project cost. The more “complete” you can be with this data, the easier it will be to justify the project’s existence.
A project proposal is a significantly exhaustive undertaking. You need to research stakeholders, map the relationships between them, identify risks, etc.
How can you make sure that get every detail right and still meet your deadlines?
Easy: treat the project proposal as a mini, self-contained project.
The more complex the proposal, the more you'll want to adopt PM best practices while creating it.
For example, a complex project proposal might go through several stakeholders before it is approved. All these stakeholders will have their own concerns, goals, and preferences.
By creating a stakeholder management plan, you can address all these concerns.
Here are a few things you can do to manage the proposal creation process better:
I don't recommend doing this for every project, but if the project is large and lucrative enough, it is better to be over-prepared than under-prepared.
The best part is that you can use a lot of this data later once you actually win the project.
When it comes to proposal formatting, it’s better to follow traditions than to think outside the box. Sponsors are used to seeing key information structured in a specific way. Tinkering with it will just cause confusion.
So what exactly is this “traditional” proposal format?
Use this image as a reference:
Each section in this project proposal outline serves a specific purpose:
You don’t have to use these exact headings, but I do recommend following the same core structure – summarize the problem, frame the project in context, emphasize the solution, and list the project’s financials and authorization.
The purpose of a proposal is to sell the project. You can’t really expect to do that if your copy reads like it was lifted from an academic journal.
You don’t have to turn it into a sales page, but you should use at least a few persuasive writing tactics, such as:
Don’t be afraid to use superlatives and sales-focused “power” words (“amazing”, “incredible”, etc.) in your copy. Your objective, after all, is to sell the project.
Not every proposal has the same objective. A proposal sent in response to a RFP has a different goal from one sent to renew a contract with an existing client.
In the case of the former, you need to emphasize your value and experience. In the latter’s case, you’re already a known quantity to the client.
Most agencies will send the following six types of proposals:
How much effort you put into each proposal should depend on which category it falls into. Unsolicited proposals require a lot of effort, but you can normally cut that short if you nurture leads upfront.
Similarly, proposals sent in response to an RFP must be comprehensive enough to fight off competitors.
Renewal, continuation, and supplemental proposals, on the other hand, should be shorter since they’ve already been approved in part.
Crafting a compelling project proposal is an art. You have to inform and persuade, all within the confines of a few pages. A strong proposal justifies the existence of the project while also making a case for your agency.
Use these tips to help you create better project proposals.
