Chapter 2
IN THIS CHAPTER
Delivering on a proposal request
Initiating a proactive proposal
Looking at the difference between small and large proposals
Creating proposals in different environments
Business proposals come in two major flavors: reactive (or solicited) and proactive (or unsolicited). Reactive proposals, also known as RFP responses, are the way most mid- to large-size businesses acquire new products and services; these companies know precisely what they want and have the clout to formally ask suppliers to deliver on these requirements.
Proactive proposals can work for any size of business (some large companies run proactive campaigns for particular industry or solution sets) but are more suitable for midsize and smaller companies. Bidders write them on their own initiative with no guarantees that their efforts will succeed.
In this chapter, you discover the differences between these two major types of proposals and some other considerations that can complicate the primary differences. You also find out how to develop strategies and tactics for writing proposals in each situation.
You write a solicited proposal when a prospective buyer formally requests solutions from you and a number of other bidders. This type of proposal is also known as a reactive proposal because you have to react and respond to the customer’s topics and specifications rather than prescribe a solution in the manner you may prefer (see the section “Writing a Proactive Proposal,” later in this chapter). Your goal with this type of proposal is to get “out in front” of the request — to be collaborating with the customer so you know when a problem is about to reach a breaking point and force the customer to seek a solution — and not be scrambling to pull together a response under duress. To win this type of bid, you need to know as much as possible about the customer as you can and as much about the specific opportunity before your competitors get wind of it.
In the following sections, we take a look at the RFP, some of its sibling request types, and ways for you to stay ahead of the curve and play within the ever-changing rules of the game.
An RFP is an invitation to do business. Some are open invitations, posted publicly so any company can respond. Some are private invitations, sent to a select few providers. And some require that potential bidders prove their mettle by meeting strict requirements in a qualification step before being formally invited to submit a bid.
RFPs can be simple and small — a few pages that identify a need and ask for a solution in relatively broad terms — or they can be complex and large — hundreds of pages of precise requirements, often in the form of nested questions. Bidders must read the RFP carefully and be on the lookout for requirements meant to disqualify careless, would-be suppliers. Bidders must answer each question thoroughly, preferably in a consistent manner, and read between the lines to discover unstated requirements that can mean the difference between winning and losing the business.
RFPs are the standard way of doing business for many industries for several reasons, including the following:
RFPs are a way of business life throughout the world. What was once a staple of doing business with only the largest companies and government entities is now a recognized standard throughout all industries and markets.
Sometimes, the RFP isn’t the first stage of the process. You may need to work through a Request for Information (RFI) or a Request for Quote (RFQ) first. You may even find that you have to undergo a pre-qualification step before you can move forward. In the following sections, we outline these possibilities in more detail.
As you gain experience in business development activities, you may run across some relatives of the RFP. Table 2-1 lists the different types of requests that potential customers may have, listed in the sequence they normally follow, and what they mean to you.
TABLE 2-1 Common Types of Customer Requests
Request Type |
Situation |
Request for Information (RFI) |
A customer has an idea what it needs but seeks potential solutions from qualified suppliers. An RFI may later lead to an RFQ or RFP. |
Request for Quote (RFQ) |
A customer knows what it wants but seeks information about how a supplier would deliver the solution and how much it would cost. |
Request for Proposal (RFP) or Invitation to Tender (ITT) |
A customer doesn’t know how to solve a problem. The RFP (or ITT) supplies detailed information so suppliers can offer viable solutions. The ITT is also referred to as an Invitation to Bid, or ITB. The RFP format may allow a bidder more flexibility in designing a solution. |
Although some RFPs are open to all bidders, some companies whittle down the competition by requiring prospective bidders to fill out a pre-qualification form. These forms are usually questionnaires — some actually call them PQQs, or Pre-Qualification Questionnaires — but they come in a variety of sizes, formats, and structures, and you can count on them requiring the following:
To win with your RFP response, you must comply with your customer’s requirements. If you fudge, hedge, or dodge, you lose. It’s that simple.
A compliant proposal is one that clearly and directly
To maximize your chances, you need to
And then there’s responsiveness. Being responsive does compliance one better. Responsive proposals address overarching goals, underlying concerns, and key issues and values that your customer may not spell out in its RFP.
Most RFPs consist of a series of questions that you must answer thoroughly while wrapping a story line or set of messages around the answers. A question-and-answer (Q&A) style of RFP provides specific directions on how to structure your response: You follow the organization of the RFP to the letter and answer each question one by one as it appears in the text. Deviating from this approach can cost you business.
Q&A-style RFPs often have short deadlines and are notoriously demanding. Procurement organizations and consultants use Q&A-style RFPs to develop line-by-line assessments for comparing each bidder’s capabilities and solutions. Q&A-style RFPs not only ask many direct, compliance-oriented questions but also ask challenging, open-ended questions that you really can’t answer satisfactorily without a consistent win strategy. A win strategy is the collection of tactics you use to help you win a specific opportunity — written and dispersed to everyone on the proposal team. Clearly defining your win strategy and its components ensures that your contributors consistently echo your main messages throughout your proposal.
To devise a consistent win strategy, you must understand the entire scope of the opportunity (which is why you read the RFP cover to cover) and be able to answer every question with an eye to how it relates to all your other answers. A win strategy is something you’ll create early in your process for every opportunity (see Chapter 6 for a full discussion) and includes the following:
Win strategies are easier to create and implement when you know as much as possible about your customers, their needs, and your competitors before an RFP is released. If you’ve had a meaningful dialogue with your customers before they release an RFP, you have time to gather the right people, exchange knowledge about the customer’s hot buttons and how you’ve solved similar problems, craft meaningful win themes by using that shared knowledge, and hit the ground running when the RFP is released.
The nearby sidebar “Getting ahead of the curve” points you in the direction of some useful advice for avoiding reactive mode.
To craft the ideal Q&A-style RFP response, you access all the information you need to answer your questions and then write a dazzling persuasive document around these answers. A customer’s Q&A-style RFP can be daunting because of the sheer number of questions and their varying degrees of complexity. You need an efficient way to make your way through the questions. The following four sections break down this process into stages — from easiest to most complex and strategic — so you can take purposeful steps toward developing a complete, compliant, and responsive proposal.
Answering a customer’s questions properly is hard and tedious work, especially if you have hundreds to answer with a short turnaround. To be successful, you have to allocate to each only the time it warrants. To help you work your way through the questions successfully, use the following strategy to classify the questions by degree of importance and difficulty.
Place the customer’s questions into your proposal template so you’ll have a familiar framework for responding while still adhering to the customer’s prescribed structure.
Number the questions exactly as in the RFP. Create visual distinctions between sections, using descriptive headers, color schemes for contrasting between questions and answers, and theme statements so you can echo and highlight your win themes and your solution’s benefits. Using a standard template will also let your contributors see the proposal take shape as the process unfolds (to access a sample reactive proposal [RFP] response template, see the appendix).
Answer the easy questions first.
Identify the questions that you can address without too much noodle-baking (just worry about getting in the answers at this point; you’ll fine-tune the content later).
If you aren’t responding on your own to the RFP, assign “owners” to each question and a due date (see Chapter 14 for a method to track your assignments). Many questions will require subject matter experts to answer them.
To identify and assemble your answers to the easy questions:
Using this approach to assemble your answers anticipates our recommended four-part response model, which we explain fully in Chapter 9. You can review an annotated template for this response method in Chapter 13.
Make each answer stand on its own merits by stating supporting proofs within the response. As a rule, avoid cross-referencing. For example, instead of responding to a question about your financial stability with “see our attached annual report,” provide the pertinent proof point in the body of your answer: “As proof of our financial stability, Standard & Poor’s verifies that our company has had 20 consecutive profitable quarters. No other bidder can match this record of stability.” This tactic does two important things: It helps you consistently echo win themes (such as financial stability) with specific proofs (20 profitable quarters) while making your response easier for readers to evaluate (no jumping to another part of the bid for proofs).
Distinguish between the least and most important questions.
Run through the questions again to decide where your priorities lie:
Time now to plan content for the difficult and most important questions that you identified in the preceding steps, such as those that directly relate to hot buttons.
A question may challenge you for several reasons. For example, it may
We recommend that you answer the difficult questions in reverse order of importance. Distinguish which of the difficult questions are less important than others, and take the following steps to deal with these questions:
Approach the less important questions by using the bullet point approach outlined earlier in this section.
Refer to Step 2 in the preceding list in this section.
Determine the most minimal response that complies with your customer’s requirements.
Refer to the earlier section “Following instructions: Compliance and the case for responsiveness” for more information on what you can do to maximize compliance.
Figure out how much time you need to get the minimal response.
Your minimal response can be one of only three possibilities: “We comply,” “we do not comply,” or “we partially comply.” You may need to contact someone else for a definitive answer (for example, an engineer, a lawyer, or an executive), so quickly determine what expertise you need to fully answer the question, and either add the expert to your response team or email the expert (so you can get a written response). Send them the actual question from the RFP and a statement describing the context of your response and your win theme strategy. Ask the expert to reply by a specific date and time (“ASAP” is not specific!).
Lock down your sources and finalize the content as early as possible.
No answer is final until you sufficiently explain why and how your solution is better than anyone else’s on this particular requirement. Never simply say, “we comply” and leave it at that. Make the bullet point method from the previous section your mantra: Comply with the requirement, echo your win theme, provide concrete proofs for your claim, illustrate your solution if possible, and plant a key takeaway in your reader’s mind. You can’t do this unless you have sources who will supply the proofs and benefits, so locking down your sources, if they’re not already part of your proposal team, is crucial.
After you’ve handled the less important of your challenging questions, use your win strategy (see the earlier section, “Facing the third degree: The challenge of Q&A-style RFPs”) to build answers for the most important and strategic questions:
Establish how you understand the customer’s needs, goals, and issues. Keep your customer’s hot buttons in mind as you respond. Every word you write should pertain to your customer’s hot buttons and what your solution brings that others’ don’t.
For more on hot-button issues, refer to the earlier section “Following instructions: Compliance and the case for responsiveness.”
Gathering the information for and drafting your answers may seem like the hard part, but turning thorough answers into effective responses and compiling them into a coherent and compelling proposal narrative is just as challenging and even more important.
Consider the following advice when writing your responses:
Outline your content before finalizing it. Before you start writing or ask others to write, build an outline to direct your response. In other words, think before you write!
Make your outline-in-progress available for stakeholders and management to review, amend, and approve. This way you’ll quickly gain consensus on your strategy and raw content plan.
Assign every question to your writers (or yourself) with clear, firm deadlines for all content — answers, images, forms, and attachments.
Establish a systematic way for contributors to deliver content so you can keep track of what’s been done and what hasn’t and what needs to be revised or supplemented.
Use lean and concise content. Evaluators appreciate clear, factual, and concise content, even if they haven’t set page restrictions. Remember that your bid is only one of many, so your most conscientious evaluators will be pressed for time. Also be aware that, based on their evaluation criteria, evaluators may be more interested in “checking the box” than in assessing the technical merits and details for responses to certain questions. So always aim to deliver the briefest yet most evocative content you can. This doesn’t mean leaving out words to save space, cramming processes into jargon that only you can understand, and listing your points in interminable bullet lists. Tell your customer that you can do the work, how you’ll do it, and why you think it matters.
For instance, evaluators may only care that you meet a particular quality standard, while quality processes may be something you think clearly differentiates you from your competitors. If you meet the standard and supply documented proof, you comply and that’s that. Going on and on about your quality team and processes may not help your score.
If you need to make your quality capabilities a discriminator, respond to the question with a visual and a caption that relays your strategic message, but keep the text as short as possible.
Following the advice outlined in this section, as well as using the steps in the preceding section to gather your raw data, will help you to continually improve your responses to Q&A-style RFPs.
We call the unsolicited proposal a proactive proposal because you undertake the work completely on your own initiative, with no guarantees that the buyer will even read it. A proactive proposal normally results from you or your sales representative discussing an unmet need or unsolved problem with a customer during a sales visit or over the phone. In the best cases, your customer contact is interested in your solution and ideally becomes your proposal coach or sponsor, advising you as you prepare your proposal. If you can get a customer executive to sponsor your proposal, your chances for success go up considerably. If you can connect the success of your proposal with the personal success of your sponsor, you have the perfect scenario.
But the best thing about proactive proposals is that they are non-competitive. You jointly discovered the problem with the customer, and you have an early, and likely unopposed, shot at solving it.
In the following sections, we look at four aspects of proactive proposals:
Without a concerned or invested audience, preparing and submitting a proactive proposal has about the same probability of success as a mass or bulk mailing — near zero. However, your success rate for proactive proposals rises far above those for reactive proposals (your response to an RFP) when one or more of the following conditions are met:
Proactive proposals can also be a good, long-term sales strategy. Proactive proposals can improve your win probability on subsequent bids with the same customers because they
The best proactive proposals are those where you have a sponsor — an insider in the company coaching you toward success. Gaining a sponsor — preferably a highly regarded voice in your customer’s company — is like being on a date and having your date’s best friend in your corner, pointing out your good traits, rationalizing your mistakes, and downplaying your inability to choose the right fork at a restaurant.
The overarching objective of a proactive proposal is to advance a sale. But to develop the most effective proactive proposal possible, you must define your objectives more precisely. Do you want to persuade your customer to
Your specific objectives determine how you develop your proactive proposal. Here are two of the aforementioned scenarios and strategies for each:
After your meeting with the customer, you’ll know who will read and evaluate your proposal. With this knowledge, you create a win theme that matches the priorities of those key decision makers (for more on win themes, check out the earlier section “Facing the third degree: The challenge of Q&A-style RFPs”).
A good win theme statement contains need, a pain statement, a feature, a benefit, and a corresponding proof point. While a good proposal has a single, overarching win theme, it can also have supporting win themes that reinforce other key messages and address multiple hot buttons. Here is an example of an overall win theme statement — a single sentence that summarizes the main message — and a supporting win theme:
Win themes may be even more important in proactive proposals than in reactive ones, because proactive proposals are essentially narratives. A proactive proposal is a story: a story of how you (the hero) will save your customer (the person in peril) from the villain (the problem or need the customer faces). Narratives of all types — novels, screenplays, and, yes, proposals — need theme statements to consistently deliver key messages across multiple structural elements (chapters, scenes, and proposal sections). Creating win themes and corresponding theme statements is crucial to your proposal’s coherence and its success.
You derive your win themes from three elements:
Here’s how you might set up your discussions of customer hot buttons:
You want to echo your win theme throughout your proposal but especially in these sections:
Most proactive proposals are highly structured documents with standard major sections. You may find the following sections in a typical proactive proposal:
You don’t have to follow this structure, but you should aim to establish a repeatable model, or schema, for all your proactive proposals, so a customer who receives a second, third, and fourth proposal — even if they’re for different solutions and months apart — knows what to expect and where to find what they seek. This way you’re subtly training readers to conform their way of thinking about proposals with yours.
As you work through this book, you find that the proposal techniques we recommend work on all types and sizes of proposals — responding to small or large opportunities is simply a matter of scale. But all our recommendations hinge on one key principle: If you initiate business through proposals, you need a repeatable, end-to-end process for developing business opportunities — from identifying and selecting appropriate opportunities to developing solutions and the proposals that describe and sell those solutions.
Your business development process should be in place long before you write the opening words to either a proactive or reactive proposal, and your proposal development process should be a distinct stage of the business development process. But not every step in your proposal process is needed or even feasible in every instance, based on the size, scope, and value of the opportunity.
With this in mind, we review some of the unique situations that can influence how you adjust your standard business development and proposal processes to meet the needs of your opportunity (depending on the industry you work in and the markets you target).
The key to scaling the process you use for a given opportunity is knowing your audience’s expectations. Every industry has its traditions and special requirements. All governments have their own set of rules. For example, United States procurements are governed by FAR, or Federal Acquisition Regulations. Even commercial opportunities may take on complex and rigid requirements, especially those managed by consultants.
You need a flexible proposal process — you may call it an accordion process — that expands like the bellows to encompass every possible preparation step and contracts to fit within the tightest of deadline time frames. Otherwise, you can’t hope to create a proposal capable of winning every time. Here’s how you can create such a process to accommodate opportunities of different sizes and degrees of complexity.
The best approach is to start big and work down. For your largest, most complex opportunities, you need a master process with each step broken into stages and each resource mapped to the required deliverable or outcome. If you build a comprehensive process for your largest opportunity, you’ll have every possible step available for every less complex, smaller opportunity you encounter — then you merely pick and choose what’s right for each project. Chapter 6 goes into much more detail if you need it, and if your process must be even more rigorous, you can always check out the techniques in Project Management For Dummies, 4th Edition, by Stanley E. Portny (Wiley).
A deadline for an RFP response is just what it says: You cross the line, and you’re dead (well, your opportunity is, and you may be out of a job). Your timeline is always at the mercy of the customer’s deadline. An RFP states a firm deadline — for example, “Your proposal is due on (date) at (time, usually including the time zone, such as GMT) at (address).”
A proactive proposal also has a deadline — it’s the time within which your customer expects you to offer a solution to the problem it may not have known it had until you brought it up. If it’s an urgent problem, you may have a shorter deadline.
Having more steps in your process to consider than you have time for is just one of the challenges you face as a proposal writer. Along with time constraints, customers often set limits to the amount of content allowed in an RFP response. For instance, they may set specific page limits for executive summaries and past performance entries, and total page limits for volumes and entire responses. Automated response platforms may even set character limits by answer or section to eliminate long-winded sales pitches. And as for proactive proposals, this is the age of limited attention spans, so being long-winded is not a prescription for success. Your best strategy in all circumstances is to limit your content on your own.
Constrain the answers to these general and specific questions on a tight authoring model. You can use the following steps and the accompanying examples as a guide:
Start with a clear, short compliance statement.
“We understand and comply with your requirement for three independent quality checks during the installation period.”
Offer a brief answer to the question.
“Our installation process already includes two internal quality checks — one at the midpoint and the second at the end of the process — so adding a third and opening them up to an independent assessor will be easy, although we will need to add a new interval to our timeline to comply.”
Provide a description of method or example of proof.
“As you see in the flow diagram, we can easily insert a third checkpoint either at equipment drop date or during offline testing. Again, the degree of testing you require will dictate the increase in overall implementation time.”
Confirm the key takeaway message.
“Our flexible implementation process helps ensure your complete satisfaction with our solution. This flexibility extends beyond installation to system support.”
Use graphics instead of words.
For example, you may be able to customize the standard process flow diagram to show callouts at the optional checkpoints proposed by the bidder.
Every industry has unique requirements for proposals, both reactive and proactive (and some outright refuse to accept proactive proposals). Depending on the size of your customer’s business, you may be dealing with procurement departments that govern what and how that company buys products and services. Depending on the segment, you may have strict published rules and regulations to follow. For instance, before you consider bidding on a government procurement, be sure you understand acquisition rules and regulations. Most government proposals must follow a strict organization and response methodology, wherever you are in the world. You must adhere to the rules or you’ll find yourself eliminated from the contest. Or you may just be dealing with the preferences of individuals in key positions. The following sections provide a brief guide to some of the more prominent segments you may encounter.
Global procurements teams, including public sector and large commercial organizations that frequently make large purchases, also follow a rules-driven process. All buyers want to make the evaluation process easier. Forcing standardized responses helps achieve this goal, whichever region you’re looking toward.
Bid requests issued as part of a formal, rules-driven purchasing process normally advise and guide bidders on the structure they should follow. Some rules are industry-specific. In the United Kingdom and Europe, for example, PAS 75 provides detailed lists of headings for pre-qualification questions for bidders in the construction industry. Although rules are not standardized across legislatures, you can expect procurements to be transparent and fair, with some type of bidder instructions provided. Some U.K. government agencies now offer detailed guidance that makes forming a content plan easy but meeting page counts difficult.
Depending on current political trends, bidding and partnering with companies based in multiple countries can be perceived either positively or negatively by international audiences. If you’re responsible for assembling a multinational response team, you need to keep up with current political scenarios and understand how they relate to your company, your home country, and the opportunity at hand.
Cultural awareness is especially critical when doing business in different countries, so be sure to research your customer’s traditions before you make an unintentional faux pas that may undermine a bid.
Closely consider your customer’s use of color, imagery, metaphors, and tone to avoid miscommunication or a worse offense. For example, when submitting a proposal to a South African company, know that red can be associated with mourning. When proposing a solution to any country’s military, avoid photographs of another government’s soldiers (unless they are obviously relevant to the proposed solution).
In recent years, commercial and government buyers have inclined toward running greener procurements, requiring that bidders submit proposals and follow-up documentation and discussions electronically. Procuring organizations use a variety of platforms and methods.
Examine the areas on the submission platform carefully and ask questions if you’re unsure about where to place documents and proposal artifacts. Leave plenty of time in your schedule for
For electronic submissions, allow extra time for uploading your content:
3.148.102.142