Chapter 2

Understanding Different Types of Proposals

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.

Responding to a Request for Proposal (RFP)

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.

remember You normally write a reactive proposal in response to a Request for Proposal (RFP). The RFP identifies the buyer’s current problem and needs in specific terms and requires you to solve the problem in whole or in part. Think of an RFP as a game where the buyer sets all the rules. The buyer may already think you’re the right company to solve its problem, but it may not be able to legally give you the business without you meeting the requirements of an RFP. You have to abide by the buyer’s rules if you’re going to win the business.

tip An RFP is sometimes known as an Invitation to Tender (ITT) or Invitation to Bid (ITB) depending on your location.

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.

Joining the game: The invitation to bid

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.

remember RFPs are not for the faint of heart. In some cases, they can mean future employment of participants or even the long-term viability of a company.

RFPs are the standard way of doing business for many industries for several reasons, including the following:

  • They establish a supportable and repeatable rigor for procurement.
  • They create tangible and comparable views of alternative approaches to solving a business’s problems.
  • They quickly weed out the pretenders from the viable providers.

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.

Understanding requests: RFPs, RFQs, and RFIs

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.

tip We provide some examples to guide you — see the appendix for more information.

Narrowing the field: The infrequent pre-qualification step

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:

  • Information about your company, including its size, location of offices, scope of resources, type of company, and how long you’ve been in business
  • References and evidence of how well you’ve performed on similar jobs in the past
  • Human resources data, such as minority ownership and sustainability programs

tip You need to always be ready to respond to qualification questionnaires, because they’re gatekeeping devices designed to reduce the number of bidders and they tend to pop up at the most inconvenient times. If you respond quickly and thoroughly (and with the least amount of effort), it may offer you a competitive advantage — the less time you spend dealing with these pre-qualification forms, the more time you can spend crafting your solution and responding to the RFP itself. If you receive a lot of qualification questionnaires, consider building a customer-facing website that provides pre-approved, standard questions and answers. While your customer may not use the site, simply publishing the questions and answers will give you a legup on responding.

Following instructions: Compliance and the case for responsiveness

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

  • Meets the customer’s detailed requirements
  • Follows all the customer’s submittal instructions
  • Answers the customer’s questions

tip The most important aspect to responding to an RFP is that you carefully read it from beginning to end, note all statements and even hints of need, and build your proposal to clearly respond to every one of them.

To maximize your chances, you need to

  • Respond to and meet every requirement your customer identifies
  • Structure your proposal exactly as your customer instructs
  • Adhere to all the formatting and packaging guidelines that your customer specifies
  • Stay within the page limit your customer sets
  • Build a compliance matrix to show your customer where in your proposal you respond to a requirement (see Chapter 4 for how)

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.

tip Responsive proposals help customers achieve their business goals, not just their solution needs or procurement objectives. Examples of responsiveness include

  • Understanding and addressing your customer’s stated and implied needs
  • Describing the benefits your customer will gain from your solution
  • Pricing your proposal within your customer’s budget
  • Editing your response so it reads like your customer talks

remember Your goal as a proposal writer is to comply with all your customer’s requirements and express how your company goes beyond those requirements to help meet its business goals. Compliance alone won’t win in an increasingly competitive marketplace. You have to work with your customer before the RFP is released to understand its hot buttons. Hot buttons are singularly important issues or sets of issues that are likely to drive customer buying decisions. They’re emotionally charged, and your customer will repeatedly bring them up because they inhibit success. You can think of hot buttons as benchmark issues — issues that ultimately determine whether the customer selects your solution. You must clearly address them in your proposal — and doing so is what we mean by going beyond compliance and being truly responsive. So while compliance can prevent your proposal from being immediately eliminated, responsiveness edges out your competition in the long run. For more about hot buttons, see Chapter 3.

Facing the third degree: The challenge of Q&A-style RFPs

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:

  • A succinct statement of your overall solution and benefits so all contributors think about your strategy as they write their answers.
  • Expressions of your solution’s most important, overarching benefits (these are sometimes called win themes and must contain a need, a pain statement, a feature, a benefit, and a corresponding proof point). You need to echo your win themes at every opportunity within a proposal (see Chapters 6 and 7 for more on writing win themes).
  • Clear descriptions of your customer’s hot buttons (those compelling reasons to buy). Including your customer’s hot buttons in your win strategy ensures that you consistently address your customer’s most pressing and emotionally charged issues. Check out the preceding section for more about hot buttons.
  • A SWOT analysis of your and your competitors’ products and services (SWOT stands for strengths, weaknesses, opportunities, and threats). A SWOT analysis will help you align your solution with your customer’s needs while evaluating how well you stack up against your competition (see Chapter 5 for more on SWOT).
  • Your company’s key discriminators. These are the things that matter to the customer that you can do that your competition can’t, or things you do better than your competition.

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.

warning If you haven’t talked with your customers, you have to do the same strategic preparation during the time you should be honing your response, and you’ll be in what we call reactive mode — you’ll be reacting to new information instead of acting to shape the outcome of the opportunity. Industry research bears this out: You win more when you start early.

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.

Getting the easier questions out of the way

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.

  1. 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).

  2. 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).

    tip 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:

    • Scan through the questions.
    • Highlight those that you can answer easily and directly.
    • Insert bullet points beneath the easy questions to collect ideas for your responses.
    • In your first bullet point, state how you comply with the requirement, echoing the question’s language as much as possible.
    • In the next few bullet points, list the main ideas and themes that you want to express in the order of their importance to the reader.
    • Follow that with a bullet entry identifying your proof points (proof points are facts that prove your claims: statistics, documentation, testimonials, and so on).
    • If appropriate, include a bullet item describing any imagery you want to support your answer.
    • Finish off your answer with a key takeaway or point statement for your reader.

    tip 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.

    tip 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).

  3. Distinguish between the least and most important questions.

    Run through the questions again to decide where your priorities lie:

    • Identify the questions that will have the most influence on the evaluators who assess and score your proposal. Set them aside for now because they will take more thought and effort.
    • Respond to questions of lesser importance by using the bullet point method that you used in Step 2.
    • Classify any question that directly relates to the customer’s hot buttons or to your key discriminators as having high priority (for more on this, refer to the earlier section “Following instructions: Compliance and the case for responsiveness”). Your answers to these questions will usually require more research (or reliance on your subject matter experts) to craft your strongest proof points.

Working with more challenging questions

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

  • Be one you’ve never answered before
  • Require official documentation or other hard-to-find proof
  • Ask you to calculate or analyze some data

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:

  1. 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.

  2. 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.

  3. 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!).

  4. 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.

tip You should spend 80 percent of your time and allocate 80 percent of your proposal’s strategy on the important questions. This may sound obvious, but people tend to go all out on every response, and that approach simply won’t work for Q&A-style RFP responses. It’s why we recommend getting the easy and least important questions out of the way early and quickly. You have limited time and resources, and you must allocate them to the responses that will mean the most for a successful outcome.

Responding to the most important questions

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:

  • Focus on determining levels of compliance. A Q&A-style RFP will (usually) provide a numbered series of questions by categories identified through main and subheadings. Be on the lookout for nested requirements (one or more customer needs buried within the sentences that comprise a numbered question), signified by the verbs will, must, should, and could. Make sure you respond to each of these trigger words. To make sure you respond to them all, search for these terms by using the Find or Search function within your word-processing software.
  • Highlight your key discriminators. What makes your company the best-right choice in this particular matter? What do you offer that no competitor can or will? Highlight these attributes and tailor them to fit the specific question being asked.
  • 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.”

  • Illustrate your responses first, and then write what you see. Sometimes proposal writers find it difficult to understand a highly technical or overly complex response provided by a subject matter expert. In these cases, a picture is not only worth a thousand words but can also launch a thousand words (well, hopefully not a thousand for a single response!). One way to get a clear description of a technical concept is to have a subject matter expert sketch the steps making up a process or draw the components of a solution in relation to one another. Use this effective technique to get highly technical content from subject matter experts and then create a more professional version of the drawing for the proposal to make that content more accessible to less technical evaluators. Discover more about this technique in Chapter 11.
  • Prove your assertions. Demonstrate your capabilities and support your claims with brief, pertinent examples. If you’ve installed a similar solution recently, one having a similar or even greater scope, cite that experience and supply enough detail to ensure that the reader sees the similarities.
  • Remember to be responsive. Think hard about what you’ve learned about your customer through close reading of the RFP and visits with the customer. Echo the customer’s own language to indicate your empathy and understanding.

Fine-tuning your responses into a narrative

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!

    • At the macro level, your customer’s RFP structure supersedes your preferred proposal outline. Follow that structure to the letter unless the customer says otherwise. Still, many RFPs allow leeway in organizing some proposal sections (such as executive summaries, pricing sections, and reference sections), so prepare an overall outline to your response that adheres to the customer’s structure and guides writers through the more flexible sections.
    • Develop your outline within the first 24 to 72 hours, depending on your deadline. Share it immediately with your response team.
    • At the micro level, populate the outline with visuals, bullet points, and notes. (You’ll have accumulated this information as you gathered the relevant materials for your answers — refer to the earlier section, “Getting the easier questions out of the way.”)
    • tip 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.

    tip 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.

    tip 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.

  • Immediately and directly answer every question. The most important rule in Q&A-style responses is to ensure that the first sentence of every response directly answers the question. This rule isn’t always easy to follow, especially if compliance isn’t clear. But with a strong strategy and an understanding of which questions are the most important, you should be able to score well on the critical questions and establish enough separation between your company and others to remain competitive.

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.

tip If you respond often to Q&A-style RFPs, we strongly recommend that you create an easy-access archive of strategy documents, templates, and reusable, pre-approved Q&A-based content that you can use to jump-start responses.

remember Time is either your biggest enemy in RFP responses, or your best competitive advantage. If you have to start from scratch every time, you’ll waste precious hours, even days, and put yourself at a competitive disadvantage. On the other hand, if you can draw from previous work you will have more time to adapt and customize rather than research and compose. Using your head start, you can consistently create more compliant and responsive proposals.

Writing a Proactive Proposal

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.

tip A proactive proposal is best built to a schema or blueprint that you can replicate for every opportunity and every customer. Training your customers to consider your argument in a certain structure is great for not only convincing them to buy from you but also building long-term customer relationships. Repeat readers know exactly where to go to find just what they’re looking for, speeding their assessment process, just as reusing your proven structure speeds your development process.

remember You may hear people refer to proactive proposals as white papers, analytical studies, feasibility reports, and advisories. They’re also known as sales proposals, executive briefings, and letter proposals.

In the following sections, we look at four aspects of proactive proposals:

  • Gauging customer interest in your solution
  • Choosing the right strategy
  • Building themes from your customer’s hot buttons
  • Following a standard, repeatable schema

Getting sponsored: The value of customer concern

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:

  • One or more people who work for your customer, especially decision makers or influencers, have expressed interest in your proposal (these are potential sponsors).
  • You have confirmed your customer’s hot buttons, and your sponsor has confirmed that addressing them in the proposal with your customer’s decision makers and their influencers is appropriate (recall that hot buttons are those emotionally charged, key issues that compel your customers to buy).
  • The value of obtaining a prompt solution outweighs the cost of soliciting solutions from others and the savings that may come from competitive bids.
  • The customer’s purchasing guidelines permit awards without competition. You should already know if this is the case through your preliminary fact-finding discussions with the customer (see Chapter 3), but as a rule, the smaller the company, the more flexible the purchasing guidelines.

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

  • Create opportunities for building relationships with key decision makers
  • Demonstrate your ability to solve your customer’s problems
  • Show that you truly understand the customer’s business, almost as well as an employee

tip The higher up your sponsor, the better chance you have of selling a proactive proposal. An executive sponsor can introduce you to key subject matter experts and ensure through that introduction that you have an ally in the trenches.

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.

Supporting a strategy: The proposal as a means to your long-term goals

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

  • Agree to a subsequent meeting?
  • Issue (or not issue) a bid request?
  • Reconsider its purchasing process?
  • Enter negotiations without further competition?
  • Issue a purchase order?

Your specific objectives determine how you develop your proactive proposal. Here are two of the aforementioned scenarios and strategies for each:

  • If your objective is to persuade your customer to meet so that together you can qualify the opportunity, don’t propose a complete solution. Your proposal should define the problem, create interest in solving it, and define your solution only to the extent that the customer knows it’s feasible.
  • If your objective is to persuade your customer to forgo competitive bidding, focus your proposal on the cost of delayed implementation. Your proposal should clearly illustrate the amount of money the customer is losing each day, week, or month of inactivity, and suggest that delaying the decision may cause further damage and cost.

Building a win theme: Motivators, issues, and hot buttons

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:

  • Main win theme statement: “Our transaction monitoring software will reduce your online revenue losses from fraudulent charges by an average of 34 percent, based on installations similar to yours.”
  • Supporting win theme statement: “Real-time notices integrated with our monitoring software relieve your card holders’ concerns and reinforce your ‘Always on Guard’ brand messaging.”

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:

  • Motivators: These are things that compel your customer to act. They may be corporate (reduced costs or improved customer service) or personal (advancement by demonstrating thought leadership).
  • Issues: These are the things that worry your customer. They stem from the problem you discovered in meetings with your customer, such as potential out-of-service conditions or production delays.
  • Hot buttons: These are a combination of issues and motivators. Hot buttons are the singularly important issues that are likely to motivate your customer to act. (You can find out more about hot buttons in the earlier section “Facing the third degree: The challenges of Q&A-style RFPs” and even more in Chapter 3.)

tip In your proposal, cite the origin of your customer’s hot buttons to provide context for evaluators other than your sponsor and your main contacts. If you found out about a critical need from the head of IT operations, say so. This will not only show unfamiliar readers that you clearly understand the present situation but also validate the theme statements that you sow now and again throughout the proposal.

Here’s how you might set up your discussions of customer hot buttons:

  • In our recent meeting, you mentioned that your key requirements are …
  • In your quality circle, several workers complained of …
  • Acme Vice President Mary Jones recently said …

You want to echo your win theme throughout your proposal but especially in these sections:

  • Transmittal letter: Use here to grab attention!
  • Executive summary: Include here to reinforce the value of your proposal with decision makers.
  • Recommendation: Share here to address the why that supports the what and how of your solution. Win themes add “sticky” reminders of the pain and urgency related to factual descriptions and make the proofs more persuasive.
  • Pricing: Add here to reinforce your solution’s overall benefits when your reader is evaluating the cost.

Organizing your proposal: A repeatable structure

Most proactive proposals are highly structured documents with standard major sections. You may find the following sections in a typical proactive proposal:

  • Transmittal letter: Every proposal needs a cover letter to introduce the proposal and associate it with the opportunity. It’s also a good place to start selling your solution.
  • Executive summary: Aimed at executives with short attention spans, this section reduces the entire proposal to a single page.
  • Current situation: This section shows your reader that you’ve done your homework and that you understand the reader’s business, industry issues, operations, and the needs or problems you’re addressing with your proposal.
  • Recommendation: This section identifies your solution, explains how it works, describes the benefits of implementing it, and shows the future state after the solution is implemented.
  • Pricing: This section summarizes the cost of the solution with a particular focus on value and the rationale for choosing this solution over others.
  • Implementation plan: This section clearly depicts who will do what and when. This is sometimes referred to as the statement of work, or SOW.
  • Qualifications: Sometimes referred to as the “Why Choose Us” section, this provides brief bios or résumés of the people working to design and install the solution and provide support after installation. Use this section to express the advantages of doing business with your company.
  • Next steps: This section launches the project, pushes for a contract if necessary, or expresses follow-up actions for the customer and solution provider.

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.

tip Persuading others to get on board can be difficult, even when they’ve already expressed interest. In the nearby sidebar “Persuading your readers: A lesson from antiquity,” we look at some timeless persuasion tips that help you to sell your proposal. Check out Chapter 10 for more techniques for writing persuasive proposals.

warning If your customer contact requests a particular proposal organization, make sure that you understand the structure and that you comply with the request! Ignoring instructions or requests projects a noncompliant, arrogant tone.

Comparing Small and Large Proposals

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).

Scaling the process: Modifying to meet the opportunity

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.

Starting with your most comprehensive process

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).

Looking at the due date and working backward

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).”

tip Sometimes a customer extends the due date if a bidder or number of bidders request more time to respond, but you can’t count on it, even in the government segments where it’s much more common — and you never want to be the bidder who asks for more time.

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.

tip If you’re the salesperson who discovered the problem and you have to write your own proposals, you can create a reasonable time frame for getting something in writing to your customer. If you’re a proposal writer working on a proactive proposal with an anxious salesperson, you may be more under the gun than with an RFP response.

remember Whatever the situation, the plan is the same: Start at the end and work backward. Consider the following list of development questions to help you decide which ones are relevant to your opportunity and talk them over with your salesperson or proposal team, or, if you’re a salesperson writing the proposal yourself, use them as a mental checklist to ensure that you get the proposal out on time:

  • When is the proposal due?
  • How much time will you need to deliver the proposal?
  • How much time will you need to print and package the proposal and related media?
  • How much time will you need to proof the final copy?
  • How much time will you need to assess comments and revise the content?
  • How complex and time-consuming will your reviews be?
  • How many review cycles will you need?
  • How long will your solution designers need to develop the solution?
  • How long will you need to assemble your team to develop the solution?
  • How long will your team need to assess requirements?
  • How long will management need to assess the opportunity and decide to bid?
  • How long will you need to analyze the RFP and assign work?
  • How long will you need to read the RFP and build your work plan?

tip As with the list of project stages in the preceding section, you won’t have to address all these questions on every engagement (indeed, some are RFP-specific, as you can see). Run through them all on the first few proposals you work on, and they’ll become second nature to you. These questions should be comprehensive enough to get you through any opportunity you face.

Constraining yourself: Overcoming the challenge of limited content

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.

tip Less is definitely more when it comes to content. Evaluators want a direct response to their questions: Full of meat, short on fluff. Consider creating a strict response model for all your content. Base even your proactive proposal content on responses to general and specific questions you know that your customers may have about your solutions.

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:

  1. Start with a clear, short compliance statement.

    “We understand and comply with your requirement for three independent quality checks during the installation period.”

  2. 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.”

  3. 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.”

  4. 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.”

  5. 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.

tip Consider setting limits to the number of characters for each of your responses before you write or assign writers to work on the proposal. You may still have to whittle down your content to meet a strict customer’s specification, but using a tight writing model sets you well on your way to the clearest, most direct depiction of your solution.

Understanding Procurement: The Differences Among Segments

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.

Going global: Developing proposals outside your region

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.

Play by the rules

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.

Understand the subtleties

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.

tip When writing proposals for customers in different countries, pay special attention to proposal instructions, local customs, and audience expectations in terms of language, paper size, binder size, media production and playback capabilities, and actual delivery methods and time frames. Also consider the customs requirements and legalities surrounding information and technology export restrictions.

Be(a)ware of cultural differences

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).

remember Keep in mind that the cultures of readers in other countries shape their communication styles, just as your culture shapes yours. Neither style is inherently wrong or right, but failing to adjust your style to match that of your readers may build a barrier that the best technical solution can’t overcome.

tip Find out as much as you can about your audience’s expectations and culture to prevent miscommunication. Check to see what, if any, style guidelines your employer recommends from a branding perspective. See if your company style guide includes lists of prohibited words and phrases that put vendors at risk. If not, create one as you prepare your first proposals for customers in other countries.

Going green: Electronic versus print

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

  • Converting word-processing files to PDF format
  • Consolidating documents based on platform requirements
  • Pasting individual answers into database fields

For electronic submissions, allow extra time for uploading your content:

  • Avoid waiting until the last minute, because uploading usually takes longer than you anticipate.
  • Remember that your competitors are uploading along with you, and capacity and network issues can affect the system’s performance at crunch time.
  • Upload any documents that you consider final “as is” (for instance, standard policies and certificates) days or even weeks in advance to reduce work as the deadline looms.
  • Get the required signatures on documents early on because you need to scan them, or convert them to PDF files, before submitting them.

remember Electronic proposals can also present a challenge because the system may restrict content precisely. Your responses must be tight, to the point, and with clear, direct proofs. Your ability to use persuasive techniques, even graphic depictions, may be limited or excluded. The goal of most of these systems is to turn your products and services into mere commodities, where price is prince and value a pauper. Use every communicative technique allowed to gain a competitive advantage wherever possible. (Turn to the earlier section “Constraining yourself: Overcoming the challenge of limited content” to find some tips for maximizing your word count.)

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
3.148.102.142