Tag Archive for Proposal

Win Theme Development

Use an Executive Summary as a tool for win theme development. Write the Executive Summary first using customer insights, your experience with similar work, and contract performance and management insights. Then refine and rewrite it as the proposal progresses.

Again, start the Executive Summary on Day 1 of the proposal project. Many of Fedmarket’s customers say; “we can’t do this.” But you can; it depends on who is writing it; ideally a project person, a unit manager, someone who knows the technology required or the customer. And if you can’t then maybe take a pass on the opportunity.

Break the Executive Summary up, when you think its complete insert all of its content in scored Section L responses if an Executive Summary is not asked for in the RFP (has no evaluation points assigned to it). Move:

  • Technical content into the technical approach
  • Experience points into the experience volume
  • Personnel points into the personnel volume
  • Management points into the management volume

You may have to change the context a bit to make it fit each win theme in the right place.

Try it, it works.

 

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.

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.

Essential Elements Federal Proposal Writing

The five C’s required to write a winning proposal are: customer knowledge, creativity, compliance, clarity and conciseness. All five C’s are needed to maximize proposal evaluation scores.

Newcomers to the federal market underestimate the importance of the five C’s and typically think that slapping together a quick proposal is enough. Proposal evaluators love quick and dirty proposals because they can reject them within minutes and cut down on the work of proposal evaluation; they can get on with evaluating the others in the huge pile of responses. Evaluators hope that many proposals in the pile will lack the five C’s.

Customer Knowledge: The federal buyer must know you and what you can do to solve their problem. You probably should not waste valuable resources writing a proposal without customer knowledge beyond the Request for Proposal (RFP). Advanced sales and customer contact provides (1) the federal buyer with the comfort of reduced risk in selecting you for an award, and (2) you learn what the buyer really wants in order to create a tailored and creative solution to the buyer’s problem (the most critical part of the proposal).
This is what the insiders do (companies with direct federal contracts). They live with the customer and can’t help but understand their needs.

Compliance: Complete compliance with every requirement of the RFP is a necessity because any compliance flaw in your proposal can cause an immediate proposal rejection. Any missed compliance requirement, however small, can relegate you to the reject pile.

Creativity: Once you know the customer, you must creatively present your solution to their problem. A creative technical approach seals the deal. A winning technical approach emanates from (1) customer knowledge and (2) a highly structured proposal writing system. A structured system can take various forms, but the essential element is that the system should produce a detailed proposal outline containing legacy content and instructions before any writing begins.

Most technical writers (the people on the firing line) need structure and guidance to write a clear and concise technical content. Without a system, chaos usually results, particularly if there are several technical writers involved.

Clarity and Conciseness: Your English teachers probably taught you that clear and concise writing begins with a tight outline (organization structure). Government proposal evaluators do not like evaluating lengthy tomes and demand clarity and conciseness. Your proposal evaluation scores will suffer without it. A structured proposal writing system enhances clarity and conciseness.

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.

NASA SWEP V Due Day Extended to November 1

Interested parties in the Solutions for Enterprise-Wide Procurement – SEWP V Procurement are hereby notified that NASA/GSFC received a significant number of questions to the subject solicitation. Amendment #5 to the solicitation has been released to extend the proposal submission date to November 1, 2013.

All Questions and Answers will be posted for Industry’s review and updates to the final Request for Proposal shall be incorporated in the next release. The next amendment is anticipated to be released on or about October 22, 2013.

This announcement was published on October 17th, 2 minutes after the announcement that the date has been extended to November 1, 2013. Note the statement about the number of questions received and the timing of the posting would indicate that the questions were received within 2 minutes of the extension announcement. To us this would indicate that another extension could be forthcoming on October 22.

Small businesses have by far the best chances of an award by responding to Category B/Group B & Category B/Group C. You have the least technical requirements in these two groups (complimentary IT products) and it is set aside for small businesses. You would be competing with only your peers.

Fedmarket is offering SWEP proposal writing services.

Call sales at 888 661 4094, Ext. 2.

Why Proposals Lose

Fedmarket uses a structured RFP-driven proposal process that ensures proposal compliance. We win a majority of the proposals we write and almost all of the multiple award (IDIQ) bids. Yet some of the single award proposals we write proposals lose. Why, because the customer:

  • Was stretching its capabilities and experience and corporate egos hate to admit it.
  • Did not write the critical technical content required to win (a proposal service company usually cannot write complex technical solution content. This has to come from the customers technical staff or proposal library.
  • Won technically but lost on price.
  • Did not understand what the customer asked for in the RFP, e.g., they wanted experience in building barracks and the fact that you built huge shopping centers did not score points.

And sometimes the customer just wanted to work with the company they know and love.