Data calls typically occur early in the proposal effort, but can ostensibly happen at any point during the proposal planning or writing processes.
A common problem with proposal teams is that it is so easy for authors to avoid communicating—particularly when one or more author is working virtually.
Successful proposals must be two things: compliant and responsive.
Storyboards have long been a part of our standard proposal best practices. We all know that the proposal giants include storyboarding as an integral part of the proposal development process, but where did this concept of storyboards originate?
There is a common misconception that developing a compliant proposal is relatively easy — you just follow the instructions in Section L of the Request for Proposal (RFP), the way Dorothy and Toto in The Wizard of Oz followed the yellow brick road.
So, you’re about to start proposal writing for the first time. Maybe you’re transitioning careers, or maybe you’re a recent college graduate, stepping into government contracting culture for the very first time.
Tight page limitations are becoming a more frequent challenge as contracting officers continue to look for ways to streamline their acquisition processes.
We know that Evaluators evaluate and score submitted proposals. Therefore, as bidders looking to win work, we should aim to make the evaluators’ jobs as painless as possible.
What do you do when the Request for Proposal (RFP) provides a voluminous Statement of Work (SOW) or Performance Work Statement (PWS) and a minimal page count in which to address it in the proposal?
You have just been tasked with writing the executive summary for a must-win proposal. The stakes are high, the pressure is real, and the scrutiny will be intense. Here are 8 tips for writing a clear, concise, and persuasive document.