Tag Archive for RFP

What Evaluators Want in Your Proposal

Evaluators tell you what they want in the RFP. That’s all they want.

They want a practical, low cost solution as reflected in the RFP technical proposal requirements. More sophisticated solutions are not wanted and may in fact result in a reduced technical score.

They don’t want more than they requested in Section L including:

  • Sales pitch about how great you company is.
  • More corporate experience summaries and resumes than they asked for.
  • Management plan information beyond what they requested in the RFP.
  • Fancy formatting and graphics.
  • They want you to make their job easy and save them time

Evaluators also want clarity and conciseness to make their job easier. Government proposal evaluators do not like evaluating lengthy tomes and demand clarity and conciseness.

  • Use simple declarative sentences and short paragraphs.
  • Explain how your organization will meet each and every requirement in a clear, concise manner.
  • Describe why your organization is unique, but only when you can be convincing and the uniqueness stands up to scrutiny.
  • Use appendices for detailed material.
  • Use simple, easy–to-understand language.
  • Avoid long-winded sentences. Use simple, declarative sentences. Keep paragraphs concise and short.
  • Avoid subjective adjectives that sound boastful.

Avoid letting your CEO throw in self-serving sales pitches without backup and clear evidence relevant to the requirements. An example of this: “ABC Co is a World Class or Best of Breed Company.” Proposal evaluators laugh at such statements; they are the polar opposite of clarity and conciseness. Avoid the “You have got to be kidding pile” – the trash pile – for proposals that start with such language as: “Our firm is a world-class, best-of-breed company that is eminently qualified to serve your organization.”

Complete compliance with every requirement of the RFP is a necessity because any compliance flaw in your proposal can cause an immediate proposal rejection. This makes their job a lot easier if they have 20 plus proposals to review by tomorrow at its already after 11 pm.

Most evaluators want to make the trash pile large and the “read completely” pile as small as possible. The evaluator typically will read just as much as necessary to put a proposal in one of the two piles.

Don’t end up in the wrong pile!

Conclusion: A Compelling and Complaint Proposal Wins

Proposal writing is the Achilles heel of federal proposal writing. Most companies wish there was an easier way and evaluators dream of it going away altogether. The recent trend of “project experience based” Multiple Award Contracts (MACs) is a start on an easier way but are far from the solution. Proving project experience through contract documents and corresponding performance evaluations can complicate RFPs even further than a traditional RFP. But they do solve the technical writing requirements that plague many small businesses.

The art of proposal writing consists of providing a compelling solution that addresses all of the requirements specified in the RFP. And then avoiding the trash pile by being completely compliant with every requirement in the RFP. Don’t try to think for the customer. Give the customer everything asked for in the RFP, down to the minutest of detail. Write to each and every solicitation requirement, even if it appears to be meaningless on the surface. Evaluators love to eliminate proposals to save time and effort or, sometimes, to help their favorite organization,” and not addressing all of the specified requirements can deem a proposal destine for the trash pile.

Give evaluators precisely what they asked for in the simplest, clearest and most compelling way.

The Difference between a Compliant Proposal and a Winning Proposal

OK. Let’s Write! Your boss has tried hard to establish relationships without much luck. And he finally says let’s go for this one because we will perish if we don’t get a contract soon. Ideally, he saw something that could cause your company to stand out from the pack of proposals received by the government.

Writing a Complaint Proposal

A compliant proposal is one that meets every requirement in the RFP and provides evaluators with precisely what they asked for in the RFP. No frills, no extras, no sales puffery.
Your proposal must be compliant to win, but even compliant proposals often lose because they are not good proposals.

Writing a Good Proposal

A good proposal is a compliant proposal that provides all of the information requested in the RFP; namely:

  • A solid technical approach and management plan
  • Pertinent experience summaries
  • Responsive resumes
  • A good price

Good proposals sometimes win but not always.

Writing a Winning Proposal

Winning proposals can come out on top based on superior content.

  • The technical approach differentiates itself from the pack by innovation, creativity, great writing, etc.
  • A management approach that show how you will minimize the government’s risk.
  • Highly tailored and responsive resumes.
  • Highly tailored and pertinent experience summaries.
  • A competitive price.

A proposal may have one or more or all of the above content but still lose for any number of unpredictable reasons.

  • Someone doesn’t like you.
  • They wanted someone else.
  • They wanted the incumbent back to minimize risk even though their performance was a B.
  • The winner low balled the price and the government was so cheap that they let them get away with it.
  • Your benefactor switched jobs.
  • Or ………….

The government has all the cards and they win the game for many reasons.

Winning Proposals Are Based on L and M and Are Easy to Read

Federal RFPs are supposed to show Proposal Writing Instruction in Section L and Proposal Evaluation Criteria in Section M of an RFP. Many do and some don’t. Proposal instructions and requirements can sneak into other parts of an RFP even in RFPs that follow the Federal Section L & M Standards. That’s why filtering the RFP is so critically important.

Proposal evaluators want:

  • Just what they asked for in Section L. Other content that you chose to write beyond the requirements in Section L will not be evaluated
  • Succinctness, clarity, easy to read text, with no frills. Write at a high school level.
  • Quick ways to get through proposals; less is better, clear tables of content, compliance matrices.
  • 100% compliance, any less will result in a rejection.

Evaluators hate:

  • Sales puffery like: ABC Co is a world class service firm with collective experience exceeding 100 person years. Tone down your CEO’s sales pitches. Limit graphics that say nothing, company logos, and fanciness in general. Do not try to impress except in the compelling content you write in response to Section L.
  • Evaluators typically say: “the sales pitch and formatting beauty is clearly done to avoid telling me the low risk solution in simple terms”.

Do not develop your own proposal organization structure because you think that’s its better than the structure shown in Section L.

It can be the kiss of death.

Overview of an Effective Proposal System

An effective proposal system must have procedures for the following three major steps.

Step 1 – Filtering (deconstructing, reverse engineering) an RFP. Filtering has to be performed by an experienced proposal writer because proposal requirements can be buried almost anywhere in a hundred page plus RFP. Miss a requirement and its all over but the shouting and gnashing of the teeth.

Step 2 –  Use the results of filtering to produce a compliance matrix and an outline based on the compliance matrix. The filter will extract precisely what the evaluators want to read in the proposal and what volumes or chapters required, sections/subsections in a required volume, and the evaluation scores associated with each section/subsection. Using the compliance matrix to produce a proposal outline results in proposal that provides exactly what the evaluators want to read; nothing more, nothing less.  When the evaluator starts to read a compliance matrix driven proposal they say: “these people know what they are doing. Maybe I better read on.”

Step 3 – Add to the outline:

  • Instructions for writers
  • Color coded RFP requirements and evaluation criteria to guide the writers
  • Any technical and/or management content from a proposal library of old proposals.

Most small businesses don’t have a proposal library. Start now and build on containing legacy content, up-to-date resumes, and up-to-date experience summaries. An up-to-date library can cut proposal writing costs in half.

The result of using a proposal system is a 100% compliant proposal containing what the evaluators asked for in the RFP.

Proposal Writing for Small Businesses

Learn about the proposal game, the importance of proposal writing experience, and how to write winners by reading Fedmarket’s 10-part installment series on federal proposal writing.

Writing Compliant Proposals: The Way for Small Businesses to Grow in the Federal Market

A majority of small service companies seeking federal contracts lack proposal writing capability.  Proposal writing capability is a necessity for small service contractors because RFPs and RFQs (1) require relatively complex proposals and (2) are usually poorly written and hide the compliance requirements. Small businesses usually do not have the experienced proposal writing personnel to write clear, concise, and compliant proposals.

Fedmarket is offering a complimentary 10-installment primer on Proposal Writing for Small Businesses. The series is comprised of the following installments, watch your email weekly to read the latest installment.

As the titles suggest, the 10-installments in the series tell readers why proposal writing is so crucial to growing a small business.

  1. Non-compliance Is the Way Proposal Evaluators Survive
  2. Overview of an Effective Proposal System
  3. Winning Proposals Are Based on L & M and Are Easy to Read
  4. The Difference between a Compliant Proposal and a Winning Proposal
  5. Proposal Writing Strategies and Mistakes
  6. Win Theme Development
  7. What Evaluators Want in Your Proposal
  8. Proposal Management Considerations
  9. Conducting Proposal Reviews
  10. Conclusion: Compelling and Compliant Wins

1. Non-compliance Is the Way Proposal Evaluators Survive

A typical RFP/RFQ in the federal market will receive 5 – 50 responses; sometimes even more. Evaluators have full-time day jobs and have difficulty wading through the responses; typically, after their child’s soccer game. The first pass through the pile of responses is usually “whoops you missed the page count, we asked for a single key person resume and I don’t see one., etc.; that’s it for you.” Seven more to go and its already midnight. My evaluation scores are due tomorrow; there has to be a better way.

The federal contracting press delights in the stories of a $50 million-dollar contract lost because the proposal exceed the page count requirement in the RFP. Guarding against non-compliance requires an experienced proposal writer supported by an effective proposal system. Non-compliance is the biggest reason why proposals are rejected.

The three critical elements of an effective proposal system from a compliance perspective are:

  1. Carefully filter the RFP for proposal requirements.
  2. Complete a Compliance Matrix based on the results of the filtering process.
  3. Use the Compliance Matrix to develop a draft proposal.

Fedmarket can write proposals for you and assist you in improving your in-house proposal writing capabilities for the 2017 season.  We will provide you with a fixed price quote to write a proposal for you. Send RFP link or the RFP document to sgluck@thefederalmarketplace.com.

We write proposals on a fixed price basis for:

  • Companies with limited proposal writing capabilities
  • Proposal organizations that are overloaded with RFP responses
  • Companies responding to GWACs and IDIQs; using a model proposal coupled with services for building the model into a compliant proposal.

We use the proposal systems and procedures described in this series of installment to write proposals for companies. Many of our customers have us write the first proposal and then use the results to write subsequent proposals.

Fedmarket can also provide you with proposal tools and templates to ease the pain and complexities of completing a compliant federal proposal:

Questions? Call us at 888 661 4094, Ext. 2.

Visit Fedmarket

The Dream Proposal Product Does Not Exist

Federal proposal writing cannot be automated for one simple reason: the proposal preparation instructions in Requests for Proposal (RFPs) are not standardized. The Federal Acquisition Regulations (FAR) defines the basic content of RFPs, but broad section definitions are not enough. To compound the problem, a significant percentage of RFPs do not even follow the section standards specified in FAR. And even worse, proposal instructions can be scattered throughout an RFP, and if you miss a one-sentence requirement, your proposal can be rejected.

All proposals should start with a compliance matrix to make proposal evaluation easier and more efficient. The content and structure of the compliance matrix should dictate the proposal organization structure. Accordingly, a standard RFP template with a standard compliance matrix would clean up the scattered RFP mess and make proposal writing easier and much cheaper for bidders. It would also make proposal evaluation easier and less costly for the government.

Don’t lie awake waiting for a standard RFP template. The irrationality of the federal bureaucracy is legendary. Even the Department of Defense doesn’t follow standards for posting a bidding opportunity at FBO.gov.

Commercial proposal products currently available are all over the map including:

  • Database products assisting in organizing and accessing proposal content
  • Proposal scheduling and management products
  • Products featuring proposal writer collaboration
  • Products telling you how to write win themes and selling points
  • Products that tell you how to organize a proposal
  • Products that claim to automate the proposal writing process (dream products).

All of these products provide some value but are not the answer to the “make it easy” dream. Proposal writing is not easy and never will be. A winning proposal has to be written by experienced proposal writers.
Fedmarket’s “Recipe for Writing a Compliant Federal Proposal” is different than any other available products. The Recipe teaches inexperienced writers how to write a compliant federal proposal using a “clean” RFP. Then the Recipe provides writers with detailed procedures for filtering messy RFPs (the norm) and using the resulting compliance matrix to produce a draft proposal ready for technical input.

Procedurally, the Recipe:

  1. Untangles an RFP into a compliance matrix and then uses the matrix to set up the proposal volumes to meet the government requirements.
  2. The Recipe then supplies pre-written materials and guides writers on how to provide compliant technical materials to complete the proposal.
  3. The Recipe does not provide required technical content in response to a Statement of Work but sets the organization for the technical response (if there is a technical response requirement in the RFP) and provides instructions on where and how to insert technical content in the draft proposal.

In summary, the Recipe is the closest an application can come to automating federal proposal writing. Applying the Recipe to writing a federal proposal is difficult for inexperienced writers, but the Recipe provides a training tool that reduces the learning curve. And, most importantly, the Recipe makes it possible for an inexperienced writer to write a compliant proposal if time is spent using the training tool.
Unfortunately, the dream product that writes technical content for you doesn’t exist. The Recipe gets as close to a complete draft proposal as possible in the unpredictable and messy world of federal contracting.

Read about Fedmarket’s Recipe for Writing a Compliant Federal Proposal at http://www.fedmarket.com/l/proposals/proposal_tools/recipe_for_writing_a_compliant_federal_proposal_/

Questions about proposal writing? Call Richard White at (301) 960 – 5813.

Proposal Writing for Novices

Your boss has just assigned you the job of writing federal proposals. The company is new to the federal market, has lost several proposals, and no one wants the job. You like to write but are a bit apprehensive about entering this strange new world. Your boss sends you a federal Request for Proposal (RFP) and says: “This one is made for us. Let’s go with it.” You try to read the RFP, and your mild apprehension increases to a level of fear. You read the RFP again, and the fear elevates to panic. Where do I start? Maybe Google can help.

You luckily found this White Paper in the sea of proposal writing advice, books, and assist products.

An inexperienced proposal writer’s greatest fears should be:

  1. Missing a one-sentence requirement buried in the RFP and being rejected for missing the requirement.
  2. Being blamed for a loss resulting from your company’s lack of experience, personnel, or technical capability; all of which have nothing to do with your work in developing the proposal.

Federal proposal writing is inherently messy and fraught with difficulties. Proposal preparation instructions in Requests for Proposal (RFPs) are not standardized. The Federal Acquisition Regulations (FAR) define the basic content of RFPs, but broad section definitions are not enough. To compound the problem, a significant percentage of RFPs do not even follow the section standards specified in FAR. And even worse, proposal instructions can be scattered throughout an RFP, and if you miss a one-sentence requirement, your proposal can be rejected.

All proposals should start with a compliance matrix to make proposal evaluation easier for the writer and, more importantly, for the federal evaluator. The content and structure of the compliance matrix should dictate the proposal organization structure. The matrix forces you to write exactly what evaluators want to score and gives them a roadmap to where they can find what they asked for in the RFP. Evaluators can’t score extra information beyond what is requested in the RFP so the “world class puffery” and extra content designed to make your company look big and powerful can actually reduce your evaluation score.

Fedmarket’s Recipe for Writing a Compliant Federal Proposal is different than any other available proposal writing products. The Recipe teaches inexperienced writers how to write a compliant federal proposal using a “clean” RFP. Inexperienced proposal writers should repeat the clean RFP procedure as many times as necessary to understand the basics of filtering an RFP to produce a compliance matrix.

Part 2 of the Recipe provides writers with detailed procedures for filtering messy RFPs (the norm) and using the resulting compliance matrix to produce a draft proposal ready for technical input.

Procedurally, the Recipe:

  1. Untangles an RFP into a compliance matrix and then uses the matrix to set up the proposal volumes to meet the government requirements.
  2. Supplies pre-written materials and guides writers on how to provide compliant technical materials to complete the proposal.
  3. Sets the organization for the technical response (if there is a technical response requirement in the RFP) and provides instructions on where and how to insert the technical content in the draft proposal.

In summary, the dream product that writes technical content for you doesn’t exist. The Recipe gets as close to a complete draft proposal as possible in the unpredictable and messy world of federal contracting. Applying the Recipe to writing a federal proposal may, at first, seem difficult for inexperienced writers, but the Recipe is a training tool which will reduce your RFP learning curve. And, most importantly, the Recipe makes it possible for an inexperienced writer to write a compliant proposal.

Proposal Writing Tips

Federal proposal writing is misunderstood, frustrating, expensive, and demoralizing. You must have an experienced federal proposal writer (commercial experience doesn’t count), hire someone with experience, or use an outside service.

Most federal insiders consider proposal writing the Achilles heel of the business but know how to play the game and keep their proposal costs within reason.

Secret 1 for newcomers: Don’t write proposals for customers to whom you haven’t sold, or at a minimum, who at least know who you are. Bidding opportunities galore may appear wide-open to all, but invariably they have already been pre-sold by one or more companies well before the opportunity becomes publicly announced.

Secret 2: Some federal contracting officials may imply to newcomers that pre-selling is “naughty” when in fact it is encouraged by federal regulation. How could they buy things without knowing what they are buying? Do you buy software without knowing what you are buying and its value way before you spend the money?

Secret 3: Requests for Proposal (RFPs) are made purposely complex to justify contract awards to aggrieved losers, federal auditors, or the public and press, if they ask.

Provide a Solution, Not a Sales Pitch

The process of arranging meetings with federal procurement officials (end users) is not an easy one. End users are busy and vendors from countries all around the world are trying to sell the end users their wares. On the other hand, end users are expected to be open to meeting with all vendors and are not supposed to show favoritism. Getting through the door of an end user’s office requires people and sales skills.

The most important thing to remember is that end users are people trying to do their job. They are naturally more eager to meet with those who appear to understand their problems and offer solutions. They will figure out a way to avoid meeting with vendors who appear to be on a fishing expedition.

An obvious question is, “How can I know an end user’s problems without meeting with them first?” Identifying problems is not easy but it can be done. Use the Internet and phone calls to conduct research on the targeted agency’s programs, the structure of the organization, and each individual’s job responsibilities. Talk to other vendors, use your networking contacts, and deduce what their problems may be.