4 Step Formula for Better Business Proposals

One of the secrets to writing successful proposals is to write the proposals backwards. Ok, I don’t mean line by line backwards. What I mean is identify the problems first and then write the proposal to address these problems. I’ve been reading Business Proposals for a client all week (I assess Business Plans and Proposals as part of my consultancy services) and found it very difficult to make a solid recommendation.

Four-Step-Strategy-Business-Proposals

Here’s the problem.

  • The proposals are fine.
  • They’re well-written.
  • They look good.
  • They have (almost) no grammar or typing errors.
  • Even the prices are fine.

So, what’s the problem?

Business Requirements Excel Matrix Business Requirements Excel Matrix

Why Most Proposals Don’t Get Accepted

The problem is that they are offering solutions to problems we don’t actually have.

Maybe someone else does but these documents don’t address our ‘pain points’. My guess is that they read the RFP we sent out and got started pronto. But…

  • Did they read the RFP in detail?
  • Did they read out annual reports?
  • Did they ask to see any feasibility studies we did?

I’m not sure.

How to Write from the Client’s Perspective

One way is to step back and see how you can link your client’s strategic needs – what holds their business together – and what you have on offer. By doing this, you’re putting yourself in their shoes and writing the document so that it answers the issues they have. This actually makes your life simpler. Instead of writing about features, specifications, and other functionality you can dovetail your product offerings to their exact needs.

But…

First you need to identify their strategic needs.

Indeed, the fastest way to lose business is to write business proposals/business plan from your perspective and not that of your clients.

The second is to overlook how the proposed solution actually meets the client’s requirements.

You’d think this would be obvious, right? But many proposals I review miss this point. The proposed solution and the actual business requirements are very far apart.

Identify Strategic Goals
Your business proposal should focus on the client’s needs and how your solution or service solve their problem. This means that before you write the proposal,

You need to read the Request For Proposal, Business Cases, Annual Reports and other collateral that gives you an insight into their business operations. Ask yourself: what it is the client really wants to accomplish.

In other words, does the Request For Proposal, your solution and their Strategic Plan all connect. If not, revise your Proposal and close the gaps between their needs and your offering. Indeed, the more knowledge you have of the client’s strategic goals, and how they impact their business, the more likely your proposal will align with their needs.

How to do this?

Examine their strategic goals from these four different angles:

  • Business Strategy – how can you increase their market share; raise profitability; reduce overhead and marketing the product line.
  • Technical Strategy – how does your product automate labor-intensive processes, enhance quality with automated machining.
  • Social Strategy – in what way can you enhance employee morale, reduce turnover, increase brand recognition, and change consumer attitudes.
  • Personal Strategy – and how can you improve career development opportunities and improve employee issues.

Look at the material you have gathered about the client and

  1. Identify
  2. List
  3. Number and
  4. Rank

the strategic goals.

Revise the Business Proposal so that it addresses each of these strategic goals.

How to Prioritize Strategic Goals

I use an Excel spreadsheet (matrix) to captures the requirements in one column and then cross-references it against our products key features. You can develop something similar that allows you to map your technical solution against their Request For Proposal or other business documents.

In next week’s article, I will look at how to identify the client’s strategic goals. Once you have identified these, you can fine-tune your Proposal to match these goals.

Conclusion

The cardinal mistake that many novice business writers make is to focus on their product – and assume that the reader will have the time, patience and interest to read their material. This is forgivable when someone is charged up and wants to get the message out. And it works  to a degree. The message is sent out but does anyone likes what they read? And will they be so patient the next time?

Over to you.

How can we improve this? Where do you see the connection between Request For Proposals and identifying Strategic Goals? Also, what other points should business writers bear in mind when developing their Business Proposals?

About the Author: Ivan Walsh provides Business Tips for Smart People on Klariti.com. Follow him at http://twitter.com/ivanwalsh

PS: The Business Plan Template is here.

Free and Premium MS Word, Excel and Apple iWork Templates

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