Carl Dickson

There are so many ingredients that go into winning a proposal that we developed a whole methodology to account for them all. But one stands out. It is an attribute that should be a part of every other ingredient. Understand it and you gain a key to unlocking the secret to winning in writing. The way most people approach proposal writing is not competitive. Or at least not reliably so. See also: Differentiation Most people try to enhance their offering by piling on features. If they are smart, they’ll even describe the benefits to the customer of those features. But that’s not the best strategy for winning a proposal. When the customer evaluates your proposal, they compare it to their other alternatives. A feature that all of your competitors also have is not going to help them select you. There is something that is far more important than your features. The aspects of your proposal that differentiate you from your competitors are what the customer needs to make their decision. No matter how formal the evaluation scoring criteria, the differences will outscore the undifferentiated features. Once you have achieved RFP compliance, differentiators are the most important thing to talk about in your proposal. You can pretty much assume that everyone bidding has experience. At least those who will get seriously considered will have it. You can pretty much assume that their approaches are fully compliant with the RFP. You can pretty much assume that they are all just as committed to the success of the project as you are. Saying that you have experience, that you are compliant, or that you are committed does not help you win. What helps you win is when you show that your experience results in benefits that no one else can deliver. What helps you win is when you offer features that no one else does or when you offer the same features in a way that delivers benefits no one else does. What helps you win is dumping the lame promises about commitment and giving the customer differentiators instead. Sometimes it can be tough to figure out what you can offer that is different. This is especially true when the customer has set up the RFP to tell everyone to bid the exact same thing. But you can always differentiate your offering: Even if you have to bid the same thing, you can offer unique ways of creating it, delivering it, or making sure it is without defects. Even if everyone has the same approach, the reasons why you do things and the way you approach the inevitable trade-offs can show unique insight. You can always be better, faster, stronger, etc. If you can show better alignment with the customer’s goals, then you can show better results, even from the same exact offering. The easiest way to differentiate your proposal is not based on what you offer. It's based on why you chose to offer it that way. If you are a PropLIBRARY Subscriber and want more inspiration, check out "22 Ways to Beat Your Competitors Through Differentiation" in our Win Strategy Recipe Library. Consider: Two proposals for the exact same thing at the same price. One focuses on differentiating how the offering is delivered and how those differentiated approaches better achieve the customer’s goals. The other proposal contains undifferentiated themes that present its offering as fully compliant. Both are in actuality compliant, and it shows in the details. Both deliver the exact same thing. But the two will score differently and the one that focuses on differentiation should score higher because the features will have more merit and appear to deliver more benefit to the customer. Now, take a bunch of non-proposal specialist proposal contributors. Ask half to write about the strengths of your approach. Ask the other half to make sure that all strengths differentiate your approach. Without any special training or coaching, which group is more likely to produce a higher scoring submission? The secret to winning is differentiation and not piling up undifferentiated features. Everything you say in your proposal should be a differentiator. Every. Single. Thing. Differentiation should be the top standard that you measure the quality of your proposal writing against. That is how you outscore the competition. When the customer starts comparing features and strengths, it is the differentiators that enable them to make their selection. A feature that everyone has is not a strength, no matter how positive it sounds. You need to make your features into differentiators for them to count as strengths and give the customer a reason to select you.

One of our customers had asked us to provide them with training so they could do a better job of preparing for an upcoming proposal. Naturally, before the training could get started they received notice that a customer was about to release an RFP, and had released a draft. So we incorporated the draft into the training. But the approach we took surprised me with how effectively it opened their eyes, how well it reached beyond just the proposal specialists, and how it contributed to real organizational change. It shows what you can do to open people’s eyes to what RFP compliance means and what you have to do to achieve a proposal the customer will find easy to evaluate. The training took the form of several sessions, roughly two hours each and about one per week. With an uncertain RFP release date, we anticipated having four sessions, and possibly more. We picked a section from the draft RFP that was big enough but not too big. Then we picked a handful of people to participate, and the rest just observed. The participants represented future proposal specialists and key section leaders/writers. Each of the participants was given a homework assignment to prepare a compliance matrix. The key was that they were all creating what you might think should be the same compliance matrix. They were all working from the same RFP. But we knew from experience that they would all make different judgment calls. We wanted them to make those judgment calls, see how they were all different, and gain experience in how to make them better and reconcile them. The next session was a show and tell session. We looked at each of the compliance matrices. What we saw was that each person took different approaches and worded things differently. This gave me an opportunity to provide some guidance as we compared and contrasted what they came up with. What made this remarkable was that they saw the problems they created for the customer. They saw how the customer would receive wildly different proposals, all based on the same RFP, and what a huge advantage the company whose proposal matched what the customer expected would have. Between that session and the next, I consolidated the compliance matrices and fixed them along the lines we had discussed. That gave us a baseline compliance matrix. Then we discussed Proposal Content Planning, and how to go from the outline generated from the compliance matrix into win strategies and points of emphasis, and account for all the ingredients that need to go into a winning proposal, before it is actually written. That session ended with another homework assignment to create a Proposal Content Plan based on the compliance matrix. The next session started off with a new round of show and tell. But here we were dealing with a lot more material. Still, you could see which ways of presenting instructions would be the most helpful to the proposal writers and how the planning could make the writing go much, much more quickly. You could also see the shift from reviewing and fixing on the back end, to designing proposal quality in from the beginning. But the Proposal Content Plans overlapped extensively and had some conflicts. This was to be expected. However, instead of me consolidating the Proposal Content Plans, I had them do it by having each participant take turns working their Content Plan into what they received, adding in anything new and of value while identifying and resolving any conflicts. This way each of them not only got to see and become aware of how that happens, but had a chance to personally be involved in resolving them. They gained hands-on experience. But the main takeaway was that instead of just hearing it explained, they got to see how important the wording of the instructions in the Content Plan is and how to make theirs better. The end result of the third session was a baseline Proposal Content Plan that was far better than any of them could produce on their own. All before release of the final RFP. Another thing I liked about this approach was that it gave us options for dealing with the uncertainties of the draft RFP. We could continue to enhance the Proposal Content Plan. If the Final RFP introduced changes, they would be much easier to manage in the Content Plan than in a narrative draft. We weren’t sure whether to hold the major review of the Content Plan before RFP release and then do an update review after RFP release, or just wait until release of the final RFP. If we did a round or two of Content Plan enhancement and the final RFP was still not out, then we could face that decision. Either way, we’d be in position for changes, whether small or large, and ready to respond quickly whether the RFP came soon or late. But what I liked the most was the way participants got way more than just procedural training, they got experience. They saw how what they did would impact the customer’s evaluation. And they had to fix it themselves. And since they represented key SMEs as well as future proposal specialists, the improvement in understanding just what it takes to have a compliant proposal that is optimized to win and the importance of not jumping straight into writing was spread across the company. That’s incredibly valuable and hard to achieve. The company went from being undisciplined to being a focused team with everyone on the same page, and achieved it before the RFP was out. It was amazing seeing that happen. And it took less than a dozen hours. The cost was peanuts compared to the impact it made, on that proposal and on future proposals. If you’d like to chat more about how this worked out or may implement something similar at your company to increase your chances of winning an upcoming proposal, just call me at 800-848-1563 or contact me through PropLIBRARY. If you want to learn about our Proposal Content Planning methodology so you can implement something like this on your own, the full documentation for it is available to PropLIBRARY Subscribers.

Instead of being well-oiled intimidating machines, most large companies are a collection of political territories that often don’t know what resources are available to them and don’t cooperate very well anyway. They don’t have an abundance of staff because all those bodies are all already committed and their proposals are just as understaffed as the ones at small companies. And even though they have billions in revenue, they can only spend what’s in their budget on the proposal. But they do have some advantages over small businesses, they just aren’t what you think. See also: Small Business Large companies have more patience. They target bids they know are coming up for recompete years in advance. They may not do much more than track them, but they are patient, and know where most of their future business will come from. If they want to win a big RFP years from now, they'll get into position by winning smaller bids over the next couple of years and get to know the customer. IF they have their act together, they’ll go into it with an advantage in preparation. If they don’t have their act together (which happens far more often than you would think) they may still have at least a little advantage in customer awareness. Large companies use more senior staff and specialists. Large companies usually don’t have an advantage in the number of people they can throw at their bids. The difference is they have more experienced managers and more business development, capture, and proposal specialists. Their proposal manager usually isn't also their administrative assistant. Also, because they're more hierarchical, the people doing the proposals at large companies usually have more authority to get things done. Large companies budget according to metrics and not according to cash flow. If they think they need to spend 2% of award value to win a bid, they spend it. If they think the proposal will require 8 hours a page over 200 pages, they will be prepared to cover the cost of 1,600 hours to write the proposal. It’s not that they have more money to spend. It’s that they can wait to recover it when they win, even after taking their win rate into account (you don’t win them all). A small business might think spending $30,000 is a lot of money to win a $3 million dollar bid, even though it may generate up to ten times that amount in profit, because they’re concerned about cash flow now. A large business will spend that much or more on ten bids in a row, knowing the profit from winning a few will cover that cost several times over. It may take a couple of years just to break even, but they can ride it out. Large companies hire more consultants. See the item above about budgets. If they need outside expertise and they’ve got the budget to cover it, they get it. They don’t hesitate like they’re taking money out of their own pocket. If they don't have the staff they need to work the proposal at the standards needed to achieve a high win probability and the size of the proposal justifies it, they do what it takes. Large companies have more mature processes. They’ve done it before. Many times. So even if they are a bit dysfunctional or have processes that are outdated or otherwise aren’t the most effective (which is usually the case), they’ve got more to work with and are more used to working as a team than a company with limited or no institutional knowledge. The advantages that large companies have come down to experience, patience, and willingness to invest. Small companies that want to beat larger companies need to use smart processes, discipline, and customer awareness to overcome the experience and budget advantages of their larger competitors. It also helps to have the financing needed to take a long-term view of your proposal investments. But even without that, you can submit better bids with fewer people if you are smarter about how you go about it. Large companies waste more effort than small ones. A well thought through process applied with discipline that produces solid, differentiated win strategies while eliminating unnecessary rewriting cycles will improve your win rate while reducing waste. And that's just what you need to take on much larger companies and win.

Is proposal layout design just the icing on the cake? Does it improve your chances of winning? Is presentation everything? Or is it completely irrelevant to the decision maker? How much do impressions matter? How much effort should you put into the design of your proposal layout? What is the most important priority? I think it is like Maslow's Hierarchy of Needs applied to proposals. At the base, and your first priority, is RFP compliance. If you are not compliant with the requirements in the RFP, you may not even be eligible to win. If you can’t at least follow the instructions and comply with the requirements, you aren’t even in the game. If there is no RFP or the customer will tolerate a certain amount of non-compliance, which may be true in some B2B proposals, you still need to address your approach to the customer’s requirements first. Next comes messaging, and by that I mean articulating what the customer needs to realize to select your proposal from the alternatives available to them, and to articulate it from the customer's perspective instead of your own. Most companies do not do a good job at this level and never really get past it. At this level, layout design can be as simple as possible. It can be plain and ordinary without lowering your chances of winning. A great layout design can't make up for ineffective messaging in a proposal, because it is read differently than a brochure or advertisement. Once you have effective messaging, then you can learn to communicate it visually with graphics. It does not make sense to jump into graphics without being able to articulate your messaging. But once you can do that, graphics can take it to a far more effective level. See also: Production Learning to conceptualize your message and conceptualize graphics can go hand in hand. It depends on whether you are a visual thinker or not. But regardless of whether you conceptualize both at the same time or take them one at a time, you must have solid messaging. Visual messaging is a big improvement, but not an absolute requirement. Once you have messaging communicated visually, then you are ready to consider layout. Proposal layout design is at the tippy-top of the pyramid. That makes it either a finishing touch or the last priority. Proposal layout design, like graphics, supports visual communication, but it is a far more subtle tool. Very few companies ever make it to the level where the highest priority for improving their proposal win rate is to focus on layout design. Actually, none that I have ever known. I'm usually too focused on winning to put time into proposal layout design I started my career in layout design and typography. I love the subject. I almost never bring it up with the customers who engage me to improve their proposals, even when I think their layouts could be greatly improved. This is because there always seem to be higher priorities to focus on that will have a bigger impact on their chances of winning. People are tempted to jump straight into layout design because they want to submit a proposal that looks impressive. But messaging is hard and requires inputs from many people, so an improvement in layout design can look like low-hanging fruit. But in proposals for anything more complicated than a commodity, messaging counts for far more than presentation. That said, if your role in the process is to finalize and produce the document and someone else is responsible for messaging, then it makes sense that you take pride in the layout design, advocate for it, and put all your effort into it. But if you look at proposals holistically, there are definitely other things that have a bigger impact on whether the proposal wins. If you want to play a critical role in the proposal, you need to get out of the back end of the process and use layout and design to drive the parts of the proposal that have a larger impact on whether it wins. The best product development efforts incorporate design at the very beginning. They don’t wait until the product specifications are complete and then think of design as just being about appearance. Apple starts with design and its product development efforts are led by designers. This is because they define design as satisfying the end user and not as appearance. Proposal design, including layout and graphics, can be used to drive the considerations that go into achieving a great proposal that reflects what it will take to win a proposal. If proposal layout design is simply about typography and appearance, most companies will never reach the point where that is the highest priority for increasing their win rate. But if layout is really about proposal design, then it’s about discovering, articulating, and building a proposal around what it takes to win. And that should always be the highest priority in proposal development.

I continue to be fascinated by how similar really bad proposals tend to be. They all make the same mistakes. And even if you follow good processes and do the right things, when the writing is that bad it can prevent you from winning. So I’m going to take a step back from writing about what it takes to submit a great proposal, and just focus on how to make sure your proposal writing is not awful. If you just stop doing these six things you can make a huge improvement in your proposals: See also: Making proposals simple Stop introducing things by defining the world. If you start off by saying “[blank] is critical to the success of this project” or [blank] plays a key role in…” you are saying something that applies equally to all your competitors. It is universally true and does not differentiate you. Instead you should be proposing to do whatever is in the blank. If it’s critical to the project, then it better be something that you are delivering, or better yet, something they can only get from you. That makes it a reason to select you. Stop telling the customer about themselves. Sometimes it’s just flattery as is “[blank] plays a vital role in saving the world.” Sometimes it’s to tell them what their needs are, as in “[blank] needs [blank] in order to save the world.” Sometimes it’s to tell them how to achieve their mission: “To achieve [blank’s] mission of saving the world, you need a…” Stop telling the customer who they are, what they need, what they should do, what their mission is, or how to achieve it. It doesn’t show real understanding, it’s patronizing, it doesn’t differentiate you, and the customer won’t be impressed by your ability to copy and paste from their website. If there is a need, fill it. If there is a problem to be solved, solve it. If it aligns with their mission and goals, they’ll realize that you understand far better than the vendor who submitted all that fluff and they’ll need to select you to get those results. Stop making statements of intent. Never use the words committed, intend, believe, value, seek, is designed to, or any variation. Don’t promise to do things. Do them. Don’t weaken or hedge on what you do. Be the company they need to get things done and not the one that makes a lot of promises, has a lot of concerns, or claims a great many beliefs while proposing to merely do what the RFP requires. Who cares that you have experience, when you were founded, or how fast you’ve grown? If there is a reason to care, then say it. Simply having experience adds no value and does not differentiate your proposal. Everyone will have experience. Yours isn’t any better unless you say why it is. What matters is not where your experience is or what you were doing, what matters is what the current customer will get out of the fact that you have that experience. Will it somehow make you better, faster, or lower in risk? The same is true for when you were founded or how fast you’ve grown. The customer has to get something out of it for it to differentiate your proposal and to become a reason to select you. Make sure your strengths are actually strengths. If you call out your strengths in a proposal, I think that’s great! But if your strength is that you’ll meet the customer’s requirements I think it’s a tragic missed opportunity. To be considered a strength, it must exceed the requirement or achieve the requirement in a way that delivers added value. A real strength becomes a reason to select you. If all you’ve got is what the customer asked for, you’re really easy to beat. Drop everything that’s not a differentiator. People struggle with finding differentiators, especially when the RFP forces everyone to do the same thing. But when you describe the results of what you do, or why you chose to do things that way, then you are saying something different from everyone else. Why you are offering what you are offering can be more important to the customer’s decision making process than what you are offering in the first place. The simplest way to make a radical difference in the quality of your proposal writing is to just stop saying anything that is not a differentiator. If it does not give the customer a reason to select you over other alternatives, it does nothing to help the customer select you. I think most of these habits come about because people are warming up while figuring out what to say and they fall back on making it sound like everything else they see in the business world. Only you shouldn’t want your proposal to sound like everything else. If you simply stop doing these things you will greatly improve your proposals. Pull an old proposal off the shelf, see how many times it does these things, and then look at how much better it will be without them. Perhaps the best part of stopping these really bad habits is that it forces you to say things that matter, things that differentiate your proposal, and those things provide the customer with reasons to select you. There are a ton of things that go into creating a great proposal, but if you just stop doing these awful bad things you’ll see a huge leap in the quality of your proposal writing.

The best way to organize your proposal is around what the customer is looking for. But you have to do it in a very literal sense. The customer is looking for something tangible. They are looking for something in black and white, spelled out, and written down. Different customers look for different things. But if you can anticipate what your customer is looking for, you have a significant advantage. Here are some examples of what your customer might be looking for: See also: Examples Answers to questions Keywords that match the RFP Evidence that you followed instructions Strengths and weaknesses Reasons Solutions Product names, company names, or brands Alternatives or options Something that wasn’t in the RFP Whether they can trust you What they should do What to tell their boss How to complete their evaluation forms Insight Capabilities that could come in handy Things that differentiate you from your competitors Affordability and savings Feasibility Risk mitigation Reliability and quality The path of least resistance Short term or long term gain ROI A better future If you understand what the customer is looking for, then the critical question becomes how will they find it? And what can you do to make that easier? Making it easy for the customer to find what they are looking for impacts: How you develop your outline How you word your headings How you design your layout to draw the reader’s eye What you say, how you say it, and the order you say it in What you emphasize How you incorporate citations and references What you leave in, what you take out, and the level of detail you go into In other words, everything about your proposal. Everything about our proposal should be driven by how to make sure the customer can easily find what they are looking for. It really is that simple. Of course, the hard part is knowing what they are looking for. That is harder than writing the proposal. But instead of worrying about how your proposal should look, or what you should write, or even how to be persuasive, just focus on what they need to find and make it easy. Considering what the customer needs to see is a great place to start your proposal efforts. Once you understand what the customer is looking for, you can build your proposal around making it easy for them to find what they need to see. If you are putting all your effort into the proposal, you might want to reconsider and put more effort into finding out what the customer is looking for. Research it, study it, and ponder it. When you can articulate it, you’ll know what should go into your proposal.

Customer intimacy sounds so much cooler than customer awareness. No company is going to say that they’re not interested in achieving customer intimacy. It’s pretty easy to convince the executives that customer intimacy is something you just have to have. But then you have a problem. How do you get it? See also: Information Advantage Customer intimacy is about trust and sharing. You have to earn trust and be willing to share before you are even a candidate for achieving customer intimacy. And some customers are reluctant to trust and do little sharing, let alone anything more… intimate. Do you really think your customer wants to be intimate with you, just because you want it? What is required for customer intimacy? So for starters, don’t expect to get intimate with your customer on a first date. Just because the customer agreed to a meeting, doesn't mean you've got customer intimacy. If you don’t arrive looking for a long-term relationship, you’re probably not going to get past their public persona. Showing up looking for a contract and asking for a chance won't cut it. You have to do more than just say you’re looking for a long-term relationship. You have to walk the talk. You have to invest. You have to earn trust and share, and do it consistently over time, before you can expect the customer to consider you worthy. In some ways it is a courtship. a period where you prove yourself worthy of the customer. So how do you prove that? For starters, it takes more than just claiming to have a compliant, useful, or even beneficial product or service. It requires long-term relevance to be worthy of the commitment. It requires the delivery of value worthy of the investment the customer will make. Proving yourself worthy to the customer requires establishing trust that the risks won't become issues. Above all it requires you to demonstrate that you give value rather than simply take it, and do so during the courtship period. Instead of pleasing talk and promises, it requires trustworthy behavior over enough time for confidence to take root. How NOT to achieve customer intimacy A big part of achieving customer intimacy is avoiding the things that will destroy it and letting time do its magic. If at the first meeting you say "here I am" and "here's what I'm capable of," why would anyone care? If you show up and do nothing but talk about yourself, you’re going to look like a taker and not a giver. If you, and your written collateral, do a lot of bragging and are full of unsubstantiated claims, you’re not going to look credible. If you ask for information from the customer but don’t provide anything of value to them, such as information that could help them pursue their goals, you’re going to sound like just another vendor trying to close a deal and not at all like a potential asset and long-term partner. Once you start forming a relationship with the customer, you need to step up your game and not rest on your laurels. If you do some work with them and your performance is perfectly normal and sufficiently adequate, you can expect to get treated just like everyone else. It doesn’t mean you're worthy just because they didn’t complain about anything. You can expect the customer to keep looking for someone else because, let’s face it, you’re boring—merely okay if they haven't found someone better. And if you do have customer satisfaction problems, you can forget about anything intimate. How to be worthy of customer intimacy Once you make contact, you need to demonstrate how exceptional you are. Note the word “demonstrate.” It is far more noteworthy than all those claims in your brochures and proposals. Demonstrating in this context is synonymous with proof. Exceptional claims require exceptional proof. All relationships start with an introduction. If you have to, you can introduce yourself. But it helps if you are a familiar face and have a good reputation. How you make contact matters as well. There are many ways to stay in front of the customer and prove that you have shared interests: Associations Networking Subcontracting Events Trade shows Webinars Online contacts like email and LinkedIn Capability briefings (better after an introduction than a first contact) When you are familiar, the customer is far more likely to say "yes" when you ask for a meeting so you can get to know each other a little better. That meeting is where you start to form you reputation with the customer. Building your reputation is supported by your: Qualifications Awards Experience Friends in common Association participation and sponsorships Publications Website Social media presence Press Just make sure that you focus on the customer more than you focus on yourself. You should do more listening than talking. Even if you've been invited to a capabilities briefing, consider wrapping all the details about your company with questions about the relevance to the customer. You should be exploring compatibility and not looking for an opportunity to brag. Everything on the lists above helps to lay an important foundation before intimacy even has a chance to occur. Each contact is an opportunity to demonstrate that you’re not the kind of vendor who's only interested in one thing by delivering value to the customer. Remember, it's not about you. It's about the customer. Put everything into a context that matters to them. Try helping them to understand: The issues The alternatives What they need to do to achieve their goals Giving them the information they need to make future decisions is a great way of delivering value. You can provide information by email, website, or in white papers. You can bring in subject matter specialists or executives to demonstrate interest and responsiveness. The key is to be helpful and to demonstrate that you're willing to invest effort into giving attention to the customer. You're not just trying to get their attention. Remember, do not expect intimacy on a first date. Your first meeting with the customer must result in follow-up meetings to get to that stage. If you think you’ve achieved something because you got a meeting, wait until you see if you can get another. If you walk out of your meeting without an agreement to meet again or at least follow up, you may not have made much of an impression. Try showing enthusiasm for what you can accomplish together and see if they return it. Keep in mind that most customers are being courted by multiple companies that seek to influence their decision-making process. It can work against you if you only contact one person at the customer. If you know one person at the customer and never reach out to anyone else, you’re not really showing much interest in the customer as an organization. You're also likely to get that person's perspective instead of a full picture. To have an accurate view of the customer, you need to have relationships at the: Program or operations level Procurement or contracting level Executive level Stakeholder level You should reach out to all stakeholders involved in or impacted by your goals, as well as the decision makers or proposal evaluators themselves once you learn who they might be. Timing matters. If you show up after they’ve written the RFP, then they have already made a commitment and you should not expect to have much influence over it, no matter what you think your relationship with them is. If you show up after they’ve decided their acquisition strategy, don’t expect to be able to get them to change to the contract vehicle you prefer. We all desperately want the kind of customer relationships where they call on us for advice and where we work together to imagine the future and solve challenges as if we were one and the same organization. What a precious but rare thing that is. It doesn’t happen like magic in a storybook. It happens because: You were there for them when they needed it You did things for them they couldn’t do themselves You solved problems they didn’t even know they had before they even realized it You made their jobs easier and never were a burden You were easier to work with than their own staff You were more than just talk You were thorough and reliable Everything you said was credible and they trusted you They came to depend on you And you delivered Maybe it’s so rare because most vendors aspire to be like this but rarely follow through. Doing all the right things is what separates you from all the other vendors. It is what makes customer intimacy bloom. So how do you know whether you've achieved customer intimacy? Does the customer come to you? Or do they wait for you to come to them? Do they ask you for help? Better yet, do they ask you for advice? If you are of real value in their eyes (in spite of whatever you claim) they will seek out that value. They won't wait for it. The other way you can tell is what they share with you. A major part of winning proposals is having an information advantage. If all you have is the same information as everybody else bidding, you do not have an information advantage. When the customer shares their preferences, perspectives, concerns, and things that matter to them in a way that gives you an information advantage, you have a real relationship. You can even quantify the fact of its existence. But they've only shared like that because they want you to do something about it. They want value. Now it's your turn to share.

Are most of your interactions with potential customers these days in writing? Relationship marketing is about providing support and building trust. This is still true when your relationship is conducted by writing. When communicating with potential customers in writing, are you giving them value or just asking for things? What can you give in writing that helps a potential customer? They don’t even have to cost a thing to give, but can still have value to the customer. How about: See also: Influencing the RFP Explanations Comparisons Descriptions Requirements Criteria Processes and procedures Reviews Examples Templates Case studies Terms and conditions Estimates Specifications Summaries Answers Questions to ask References Referrals Instructions Preferences Perspective Guidance Training Facts or data Pictures, illustrations, or graphics Associations Contract clauses or language Schedules Allocations Considerations Amounts Alternatives Durations Deadlines Inspiration Events Trends Contingencies Things to anticipate Confirmation Congratulations Recognition Substantiation Plans Forms Checklists Suggestions Organization Ranges, limits, starting and ending points Best practices A reason to smile Clarification Direction Targets Models Assessments Risk identification Risk avoidance Risk mitigation Research Rules Regulations Loopholes Precedence Exceptions Inclusions Exclusions Compliance Options Background Reminders Improvements Pros Cons Lessons learned Wording Structure Penalties Rewards Incentives Action items Concerns Insight Creativity Testimonials Feedback Opportunities Solutions Sources Destinations Secrets Announcements News Advice Observations Corrections Quantities Objectivity Collaboration I saved my two favorites for last: 100. Things they’ve never thought of before or wouldn’t think about on their own 101. What they need to take the next step or to do their job These can be precious gifts. The kind that earn goodwill. The kind that can start or cement a relationship. The kind that lead to winning business. Providing support and earning trust in writing is about delivering value and establishing credibility. Every email or written interaction is subject to scrutiny. Are you a giver or a taker? Are you a time sink or do you add value? How do you want your potential customer to perceive you? The next time you’re trying to be an asset instead of being a burden, this list should give you some inspiration.

Selling in writing is about influencing the decision process and the decision maker with what you put on paper. When the customer will make their decision based on the proposal you submit, you need to sell in writing to influence the sale. A salesperson has influence in person, but if they don’t carry that over to what gets put in writing they have no influence over closing the actual sale. Influence in person vs influence in writing See also: Information Advantage To sell in writing, the salesperson must discover how to influence both the decision process and the decision maker when the are reading instead of talking in person and then provide instructions that explain how to accomplish this to the proposal writers. This is very different from influencing potential customers through charisma and personal sales technique. Winning in writing means the salesperson can't just "leave the writing to the experts" and stay out of the proposal effort. The salesperson doesn't have to write the proposal or even choose the words, but they must inform the writers of the customer's decision process, preferences, and how to position those words for maximum influence. Winning in writing is actually more like cooking than speaking. When you try to persuade someone in person, they often make their decision on the spot. When you have to persuade someone in writing, they take their time deliberating. They think more about how they should decide and what criteria should guide them. They try to be more logical. They compare, often line by line, in a way that can’t be done with the spoken word. Differentiators matter more than impressions when selling in writing. Proposal evaluators collaborate and share, and sometimes decide by consensus. Winning in writing requires influencing the decision process The customer may have a formal process with an evaluation team to score the proposals they receive. If it’s a government proposal, then winning in writing is all about writing to optimize the scoring process. The salesperson's role becomes communicating how the customer implements their evaluation process, how to interpret the RFP, who is involved and how they make their decisions, and what needs to go into the proposal to achieve the maximum score. To win in writing, you must take how the customer will reach their decision into account, make sure they have the information they need to reach their decision, and if possible guide them through it. Before proposal writers can do that, you have to give them this information. The information a salesperson seeks from the customer must anticipate what you will need to know to write the winning proposal. The salesperson’s success at closing the sale depends on it. When everyone has the same RFP, winning in writing requires achieving an information advantage before you start any actual writing. Salespeople are vital to the proposal process The salesperson is the connection between the people at the customer and the proposal document. Watch a salesperson in action when interacting with a customer: they ask questions, make suggestions, and choose their approach based on the answers. You can’t do that in writing. If someone hasn't done that in person before the writing starts, you will write your proposal with all the charm of an ignorant stranger. If a salesperson talks to the customer, but then doesn’t participate in planning what to say on paper, you lose any insight they may have had and still end up proposing like a stranger. And from the customer’s perspective, you set the relationship back because everything that was discussed has somehow disappeared when they read the proposal. It makes your company look like it is all talk with no follow-through, which happens to be correct. Winning in writing requires more precision Mistakes made in writing are permanent. Never mind typos. If you misinterpret the customer, misunderstand what they want, or fail to write from their perspective, they will be constantly reminded of it every time they look at your proposal. Your salesperson needs to vet what you intend to offer and what you think matters with the customer so that when you present it in the proposal you position it correctly. If you are going to write your proposal from the customer’s perspective, you must be able to relate everything about your offering to what matters to them. It must reflect their preferences and fulfill their needs, goals, and desires. To achieve that, you need someone who can not only talk to the customer and discover those things, but who can anticipate what the writers will be trying to do later and get the input they need to be successful. In a face-to-face meeting, trust is earned through body language, questions and answers, challenges and responses, and interaction. People decide to trust each other based on their reactions. In writing, customers decide whether to trust a vendor based on how accurately the vendor describes the customer’s needs, how thoroughly the offering meets their needs, how accurately their proposal is presented, and how well what they see in writing demonstrates that the vendor listened to them. People only buy from people they trust. To win in writing you must prove you are trustworthy and not merely claim it. If your company depends on selling in writing, then your sales force better play a key role in that writing and not simply hand it off to someone else to produce — at least not if you want to be competitive.

Most proposal assignments are a plea for the writers to figure out how to win the proposal on their own. Is that realistic? Is that even possible? It probably depends on how much customer insight the writers have. But instead of hoping for someone to save the day at the tail end of the process, a proposal process designed to win should gather that information and give it to them up front. Instead of assignments or steps in your process, think about setting expectations. What do stakeholders need to know and when? To improve your proposals, you need to make sure that when people sit down to work on them, they have what they need. If they don’t know what they need, you might conclude that you have a training problem. Only instead of looking at it as a training problem, with proposals you’d probably be better off looking at it as a problem with delivering what stakeholders need to know. Part of what they need is information to work with, and part of it is what to do with that information when they get it. A proposal process that gets the most out of people will deliver both. And that’s important, because if you want to escape the problem of people not following your process, the best way is to make following the process easier than skipping it. And the best way to achieve that is to deliver what stakeholders need to know in order to play their parts. See also: Assignments You can see this in practice when proposal assignments are issued. Does the assignment tell the receiver: What the definition of success is? How to achieve that success? Where to get the input they require? If the assignment is to write something to complete an outline item, then it fails all three. If the assignment is to write something demonstrating compliance with the RFP requirements, then it fails two and sets the bar for success below what it will take to win. If the assignment is to write a winning proposal with the RFP as input with an unspecified definition for what a winning proposal would be and some unspecified additional input, then you can expect an uncertain result. In all three cases, the assignment set the receiver up for failure from the beginning. An assignment that is not doomed to failure will: Define proposal quality Provide the criteria required to fulfill proposal quality to the receiver in the context of their assignment Provide the information they will need to fulfill those criteria For example, if a winning proposal requires writing from the customer’s perspective, then the assignment should: Make reflecting the customer’s perspective at least part of what defines a quality proposal. Provide the criteria the reviewers will use to determine whether the proposal reflects the customer’s perspective. For example, one criterion might be: Is the response about what the customer will get out of what we propose, instead of being about us and what we offer? Describe what results the customer is looking for, what their preferences are, and what they hope to achieve as a result of the procurement. If the assignment does not do that, how can they possibly succeed? You can make a huge improvement in your proposals by forgetting about how you currently view your proposal process and just focusing on making better proposal assignments. No amount of proposal reviews or improvement in how you do your reviews can fix things on the back end when poor proposal assignments are made on the front end. No amount of complaining that people missed their deadlines will accomplish anything when you don’t give people what they need to do their tasks. Forget about the steps. Focus on the assignments. And what you need to give better proposal assignments. How assignments are made is an early indicator of the success or failure of the whole effort. Either you have the information you need to give proposal assignments or you’re just hoping for someone to save you from the fact that you’re not prepared. Improving your ability to give better proposal assignments means arriving at the proposal better prepared. Arriving at the proposal prepared to win is often out of the hands of the proposal manager making the writing assignments. Achieving better proposal assignments only happens when you have a solid process in place to make it possible and an organization that delivers what is needed. If your current process isn’t delivering what you need to make better proposal assignments, then maybe it’s time to replace it. And if all parts of the organization aren’t delivering their parts, the right process will make that apparent. Either way, the assignments should define success and not failure.

Great proposal writing isn't based on slick words. Great proposal writing does not require the editing skills of a professional. You really don’t have to be an expert in anything to be a great proposal writer. But there is one thing that is absolutely necessary, and not everyone has it. I’m not even sure that everyone can develop it. That thing is perspective. To write a great proposal, you must be able to conceive which words to use from the customer’s perspective. You must be able to think like the customer, read like the customer, and care about what the customer cares about. Proposal writing requires articulating what the customer needs to hear in order to reach a decision in your favor. But before you look at these things the ways the customer does, you must be able to consider perspectives beyond your own. You must be able to see things from the customer's perspective. If you want to improve your proposal writing skills, start by improving your ability to see the customer's perspective when they receive and evaluate a proposal. Looking through someone else's eyes See also: Great proposals Perspective is a skill that must be developed. Everyone thinks they have perspective, but my experience working with hundreds (thousands?) of proposal contributors has shown me that not everyone does. Some people are only capable of thinking, let alone writing, from their own perspective. This affects not only the way we see things, but how we describe them. If the only perspective someone has is their own, then they interact with the world based solely on their own way of looking at things. When they write, they describe themselves instead of describing the things that matter to the customer. When they propose an offering, they write about what they are providing or will do instead of how it relates to why the customer is trying to procure it. When they consider proposal quality, they do it based on whether they think the proposal is presented the way they think it should be, instead of how the customer will see it. If the proposal says all the good things about them that it should, they think it’s a good proposal. Only they are not the customer and only the customer's opinion matters. They come up blank when you inform them that a good proposal should present what the customer needs to see instead of what they want to say. Because they lack the customer’s perspective, they see getting selected as being completely about them. From that one perspective, how else could it be? The result is that their goal is to be as descriptive as possible and full of details about themselves. They want the customer to know how great they are. So that's what they tell them. From their customer's perspective, however, they just talk about themselves a lot. A proposal that is instead written from the customer's perspective will show considerably more value to the customer than a monologue about how great you are. Only being able to look at the world through your own eyes is a competitive disadvantage. If your proposal is about you, your offering, your approaches, your commitment, your intent to be wonderful, and why the customer should select you, it will be vulnerable to a proposal that is written about what the customer will get, how it will improve things for them, why what you are proposing and your qualifications matter to them, and how it will fulfill their goals. If you can't make that shift, you've got a perspective problem that will keep you from writing great proposals. A proposal may be full of good details, but the proposal won’t be great if it's about you instead of being about what the customer is looking for. Someone else proposing the exact same thing will evaluate much higher by describing it from the customer’s perspective instead of their own. This is because when you write from the customer’s perspective, you demonstrate that what you are proposing aligns with what matters to the customer and will fulfill their goals. Skilled proposal writing requires articulating things from the customer's perspective because it ensures that you provide the information they need to reach a decision in your favor and present it in a way that matters to them. Being really good at describing yourself and talking about yourself in impressive detail will not make you a better proposal writer. How do you write from the customer's perspective? Improving your proposal writing skills starts with doing a little bit of research to understand what matters to the customer. You have to know enough about them to be able to articulate things from their perspective. But that research alone is not enough. You have to consider things from the customer’s perspective and then write what they need to read to see, as opposed to what you think you should say. This is the skill you need to develop and continuously improve. Perspective is an interesting thing. To grow beyond your own perspective and cultivate it as a skill, you have to learn to see things through other people’s eyes. Perspective requires a great deal of empathy. If you can’t imagine what someone else thinks or feels, or if it never occurs to you, then you need to work on your ability to do that effectively if you want to improve your proposal writing skills. How to tell when you are NOT writing from the customer's perspective Here are four warning signs that your proposal writing lacks perspective and is about yourself instead of being about the customer: Everything starts with “we,” “our,” or your company name. Your company or team is the subject of every sentence. Your proposal is about your approaches, what you do, what you sell, the benefits you bring, and why you should be selected. The text of the proposal is all about you describing yourself, your qualifications, your experience, and your strengths. Your proposal is about you and how what you offer is great, instead of being about what the customer will get and how it will fulfill their goals. A great proposal is about the customer and what they get out of everything you do or every qualification you have. You, your offering, and your qualifications only matter if they matter to the customer. The goal of shifting perspective is to be able to articulate your proposal in the ways that matter to the customer. When the customer sits down to read a proposal, they are looking for what they might get out of you, your offering, and your qualifications. You need perspective to be able to articulate in writing what the customer is looking for instead of merely saying how great you are. To cultivate perspective as a skill, you need to think about what would matter to you if you were the customer, reading and evaluating a proposal. You need to understand the customer’s environment, pressures, goals, and aspirations. You need to learn to want the same things they want. You need to think through making a decision the same way that they will. Then you write what they need to hear in order to decide in your favor. Your style of proposal writing, techniques, formatting, capabilities, and experience all matter very little compared to that. Style does not win proposals. Perspective does. It takes a wide range of perspective to do this well The customer is more than one person. The customer has more than one opinion, agenda, or set of goals. If it's an important procurement, there always is more than one person involved in reaching a decision. You not only need to write from the perspective of the decision maker, but you also need to be able to write to the perspective of everyone who influences the decision. In practice, this means considering all the points of view that might exist within the customer's organization and satisfying all of them that your proposal represents their organization's best alternative. Anyone can do it. Except those who can't. Someone with minimal experience and little knowledge but a solid grasp of the potential perspectives of the various readers can write better proposals than highly experienced proposal specialists who lack perspective. Proposal writing skills do not correlate with experience. Some people show up being able to do this naturally. However, even some highly experienced proposal writers write self-descriptive, accurate, but hopelessly ordinary proposals. Experience as a proposal writer matters far less than someone's ability to see the customer's perspective and write a proposal based on it. If you cultivate perspective at an organizational level, it becomes a competitive advantage for your company. This is another reason why effective proposal content planning has such a huge impact on your win probability. The proposal process shouldn't be primarily about steps, procedures, and production. The proposal process should be about how to consistently build every proposal around the customer's perspective. While some research is required, perspective mostly requires empathy. Since we all share the same basic human nature, we all have similar concerns and motivations. This includes the people also known as "the customer." Twisting wording around in our heads to look at them from the outside in requires a lot of effort. And a little skill. It comes easier to some people than it does to others. In my experience, most of the people who struggle to find the words to write in a proposal are really struggling with perspective and not with proposal writing. The challenge is not putting words on paper, it's putting words on paper from someone else's perspective. If you have spent your life only looking through your own eyes, you may not be able to twist your mind around enough to write from someone else’s perspective. It’s easy to think about what’s important to you. It’s a lot harder to think about what’s important to someone else who has different concerns, values, knowledge, experience and priorities. The more you imagine what someone with different concerns, values, knowledge, experience, and priorities cares about, the better you will get at being able to articulate their perspective. The better you get at it, the easier it will be to write from someone else’s perspective. And the better you get at doing that, the better you will be at writing great proposals. Writing good proposals vs. writing great proposals You can write better proposals by learning more about what should go into them. But if you really want to write great proposals, just learn to channel the customer, do a little research, meditate on the Zen of proposal perspective, or simply ponder what it’s like to be the customer conducting a procurement and trying to get your needs met. Then don't try to be a great writer. Just try to write from the customer’s perspective instead of your own and the customer will think you've written a great proposal. And their opinion is the only one that matters.

Sometimes the world is just too big. It’s full of customers, but finding them is like playing the game, “Where’s Waldo?” And just like in the game, you need a strategy for finding your customers. You only have so much time and resources to put into the search. But unlike the game, you have to capture sales from Waldo. And it’s competitive. You may find him, but that doesn’t mean he’ll become a customer. When the game is business development, it’s not just about finding as many Waldos as you can, it’s about converting as many Waldos into customers as you can. When you do business in a complex environment, your ability to convert Waldos into customers will have as much of an impact on your sales as your ability to find leads. Probably more. Finding buyers is easier than turning them into customers. This means that what you do when you find Waldo is more important than finding as many Waldos as possible. Selecting the right targets means both looking in the right places for Waldo, and looking for the right Waldos, the ones who may become customers. It’s almost enough to make you want to wait for Waldo to hold up a sign saying “I’m a customer” and “Download my RFP!” The problem with that approach is that you are a stranger to Waldo. Not only does he not trust you, but you don’t know anything about him to make your proposal matter to him. And if your proposal doesn’t matter, he’s a Waldo with a low probability of becoming a customer. You want a Waldo who you can get to know a little bit before he puts out his RFP, so you can make your proposal reflect the things he cares about. Since the world is so big, you have to make it smaller in order to find that kind of Waldo. How you go about doing that is the key to targeting. You want your smaller world to be full of potential customers, who you can get to know and convert a high percentage into paying customers. Here are five considerations: See also: Strategic planning What does your sales cycle look like? Is it short? Long? Simple? Complex? Seasonal? Event driven? If you have a nice, easy, and short sales cycle, you can reach out to many potential customers. But if you have a long, complex sales cycle, you need to be selective to ensure you pick the right Waldos because it takes time to guide them through the procurement process. Seeking Long Term Relationships. People buy from people they know and trust. So start with people you know. You might not know the buyer, but you might be able to get there through a friend of a friend. Work your network. Grow your relationships into something larger. It’s a quicker payoff than trying to start new relationships from scratch. Especially if you’re going about it randomly. Who buys what you sell? This is a simple data problem, but it’s amazing how many people want to start selling before they know this. Targeting is about figuring out who you want to get to know. The organizations you want to build relationships with are the ones that buy a lot of what you sell. Do your homework and crunch the numbers, then prioritize your efforts. Market segmentation to divide and conquer. There are an infinite number of ways to divide up potential customers to create a group that’s small enough for you to reach, but large enough to fulfill your needs. The most common forms of segmentation are by market, location, size, and demographics. Who’s willing to talk to you? Some customers are better to have than others. Some are easier than others. If you have limited resources, you should focus on the customers who are willing to talk to you, and skip the rest. This means ignoring potential customers who want to keep you at arm’s length or who treat vendors as the enemy. They might be worth pursuing later, when you’ve got the resources and the time. The smaller you make your world by matching potential customers to your sales cycle, segmenting it down to a manageable size, and limiting it to customers you have relationships with or can develop relationships with who frequently buy what you sell, the better your chances are of finding customers. But then there's… The elephant in the room If you make your world too small, it will be full of customers, but even if you win them all there won’t be enough of them. The question becomes whether you can reach enough buyers for what you offer? Sometimes your customers segment easily. For example, they’re all in one location. But sometimes it’s not so easy because they are widely spread out and you can’t reach them all. The elephant in the room is whether you should be offering something else that will appeal to the customers you can reach to better sustain your business. Sometimes finding Waldo isn’t about the hunt. It’s about the bait. Waldo has to want to become your customer. You have to be able to position your offering relative to what Waldo needs and is willing to purchase. And there has to be enough of the right kind of Waldos within your reach. You are far more likely to capture Waldo’s business through strategy than by waiting for him to hold up a sign, ignore all of your competition, and pick you even though he does not know you.

If it’s so obvious that your proposal should describe your strengths and downplay your weaknesses, why do so many proposals do such a poor job of proposal writing? This article was written after spending a day discussing that with a customer who evaluates proposals. I love testing my assumptions and learning everything I can about the customer's perspective from an actual customer. The customer I spent the day talking to worked in the Federal Government. But this topic is one of those that applies equally to commercial proposals. Clearly the Federal proposal evaluation process is strange and mechanical compared to the way companies evaluate proposals. But it’s precisely that level of methodical detail that enables us to see the issue more clearly. Both markets can get something out of it. An RFP issued by the Federal Government has written evaluation criteria. They’ll break down the proposal into sections or volumes and provide the criteria for each one. Here is an example: To get an “Exceptional” rating, the proposed approach must reflect numerous strengths and no weaknesses. To get a “Good” rating, the proposed approach must reflect multiple strengths and only a few minor weaknesses. To get an “Acceptable” rating, the proposed approach must have strengths and may have some weaknesses. To get an “Unacceptable” rating, the proposed approach must have either multiple weaknesses or one or more major weaknesses. See also: Themes Winning with a formal evaluation based on criteria like these becomes a mechanical process of stacking up strengths and weaknesses. You should design your offering so that the evaluator finds those strengths in your proposal. You should anticipate the evaluation forms so that the evaluator can copy and paste your descriptions of your strengths right onto their forms. The only hard part is knowing how to articulate your proposal strengths. If you just do this the way you normally would, you will probably lose to someone who understands the definitions and the way the terms are used in the RFP. For example, if your approach fulfills all of the requirements of the RFP, you might think this is a proposal strength. But you would be wrong. Complying with the RFP is a minimum requirement. It is not a strength. A proposal strength has to represent value to the customer beyond the requirement. Being qualified is also not a strength. But you can turn your qualifications into strengths. All you have to do is show how they differentiate your offering and explain how the customer benefits from it. Simply explaining why you do something can turn it into a strength, if the reason benefits the customer. Every trade-off decision is a potential strength. Every feature of your offering is probably not a strength, if it merely meets the requirement. However, if you do something the customer requires in a way that is innovative or designed to be better, then the reason why it is better makes it a strength. Proposal writing is not about describing things like your approach, or listing all your features in the hopes that the customer will pick some out and call them "strengths." Proposal writing is about describing things in such a way that they fulfill the customer’s definition of being a strength. To win the evaluation, each section of the proposal should be worded to present as many strengths as possible. You can accomplish this simply by calling out your differentiators and explaining why your approach delivers better benefits than what as required. It works best if you design your layout to feature these statements through typography, formatting emphasis, text boxes, etc. So now let’s talk about weaknesses. Weaknesses are not ways in which other proposals are better. Weaknesses are non-compliance. If you are not as good as another provider, the evaluator doesn’t score that as a weakness (your competitor will just have more strengths than you do). But if you fail to meet an RFP requirement, then you have a weakness. While you might think of weaknesses as ways in which your offering is insufficient or fails to meet the customer’s needs, when those needs are defined by the RFP, weaknesses are ways in which your offering fails to meet the RFP requirements. But there’s an even easier way to look at weaknesses. Weaknesses are no-bid indicators and not something you need to write away or hide. If you look at the evaluation criteria above, the winner probably is not going to have any weaknesses. If you are truly non-compliant, your proposal may not get evaluated at all. You can’t explain away the fact that you don’t meet the requirements, or find some clever way to hide it. Weaknesses are a quick way to get an “Unacceptable” rating. So if you are in the game, you won't have any weaknesses. If you are in the game, you will be fully compliant and then it is all about stacking up strengths. This means that if you want to win, you should no-bid everything where you have weaknesses (even if you have already started the proposal and feel invested) and make your proposal process about presenting your strengths. You can even plan what you need to write in a section by listing your strengths in a way that shows how they differentiate you and benefit the customer. Then the rest of the writing becomes much easier. But more importantly, your chances of winning go way up.

monthly_2016_02/ItsNotAboutYou_pdf.747dc5606021860b4c17c70086a4e994

Most people do not follow their company’s proposal process. Most proposal managers blame process failure on the participants not having enough discipline to follow the process. People focus on the burden of following a process. Or the need for training about the process. But those are not the real reasons that people are not following the process. The real reason your process is failing is that it’s not delivering the information that people need. They get an assignment and an RFP that they may or may not understand. Everyone knows that the RFP requirements are only part of what they need to do their assignment, but that’s all they get. Maybe they get a list of “themes.” They ask for templates and re-use libraries because they know they need more information than you are giving them. They just don’t know what to ask for. They have to set out on their own because the process has failed to deliver what they need to complete their assignment. If the goal of the process is to create a proposal that reflects what it will take to win, and the process doesn’t define that, then the process has failed before any proposal writing has even started. If you are trying to write a proposal that reflects the customer’s perspective, and you haven’t anticipated and answered the questions the writers will have about the customer’s preferences, then the process has failed. If you get to the review and the reviewers have to decide for themselves what defines proposal quality, then the process has failed. The key thing to realize is that the process does not matter. The steps do not matter. It’s the information that matters. The process is just a vehicle to organize discovering the information you will need and delivering it to people when they need it in the form they need it in. If your process is all about requirements and assignments, but doesn’t address the information needed to complete those assignments, then it is not providing what the writers need to execute the process. It will fail. But process can also guide people to discover, assess, and transform information into what is needed, while measuring their progress and giving them a way to determine whether they have achieved a quality product. Try this: Drop the process. Completely. Now, just deliver the information people need to write a winning proposal. Start at the end with a winning proposal and work back to the beginning to identify what information is needed to get there. Anticipate the questions people will have and deliver the answers. That is all. Think about each stakeholder. Some stakeholders didn’t participate in the proposal but need to know that it is a quality proposal. Some play a very specialized role, like contracts or pricing. Some make contributions but don’t actually write. Some write, and may or may not have subject matter expertise. Some know the customer and have insight. Some participate in developing the strategies, and may or may not write the narrative. Some plan, track, and oversee. Some have to write the darn thing and struggle to make it reflect the customer’s perspective. Etc. What does each need to know and when? See also: Successful process implementation Don’t think in terms of kickoffs, assignment tracking, and quality assurance. They can support the flow of information, but it’s the information that matters and not the activities. You’ll need some or all of those activities (and more), but you only need them if they contribute the right information and they can only be successful if they receive the right information. You’re going to run into a problem. The need for information stretches back to before the start of the proposal. If the right information isn’t delivered at the start of the proposal, the entire effort is doomed before it begins. And yet, many of you are in that position and can’t use it as an excuse. You’re tasked with making a good show of winning regardless of what you are given to work with. That’s why you need to start with a nice, long list of questions. Ours has 135 questions. The answers to those questions tell you what you’ve got to work with. You can even quantify it by counting up how many answers you've got. And over time you can correlate that with your win rate. But the most important thing is that it gives you a foundation of information that you can move forward with. It gives you something to create bid strategies out of. It gives you something to provide guidance to the proposal writers. It gives you what you need to define what it will take to win and turn it into quality criteria. You will never get answers for all the questions you ask That’s okay. Sometimes the questions you don’t have answers to are the ones that drive your bid strategies. But you can’t figure that out until you know what you’ve got to work with. Your process succeeds or fails based on whether you can deliver the information that people need. If they fail because the process didn’t deliver that information, it had nothing to do with a lack of discipline. If the process delivers the information people need, they’ll follow the process because that’s how they get what they need. If the process doesn’t deliver the information they need, they have to go outside the process in order to fulfill their assignment. That’s why the process is less important than the information. Achieving an information advantage is the single most important thing you can do to position yourself to win But achieving an information advantage is only part discovery. It’s also part what you do with the information you have. If it doesn’t make it into the right black ink on paper, then it’s not part of the proposal. Winning in writing has more to do with getting the right information than it does with the act of writing itself. If people aren’t following your process, ask yourself what they need to complete their assignment that the process isn’t giving them. If your proposals are making it to the review stage and then things go bad, ask yourself what the reviewers know that the writers didn’t. And why. If you are forced to start your proposal without the input you need to write a winning proposal, then figure out what your strategies are going to be in its absence and instruct the writers accordingly. Don’t just push the assignments to the writers and expect them to figure it out. Who wants to be on the receiving end of a process that works like that? One of the advantages of a process that is based on questions that direct the flow of information, instead of a process that is based on steps and assignments, is that you can track where you needed information and didn’t have it. You can even quantify it. But most importantly, you can connect what you didn’t have with what the impact was on the proposal and how it relates to what it takes to win. That is powerful feedback for driving change so that your company can improve its ability to write proposals that do reflect what it will take to win.

If you think the best way to figure out what to write about in your proposal is to start writing, you may be making a colossal mistake. The mistake is that you’re skipping the part where you “figure it out.” You are thinking by writing about it. Look at how inefficient it is to have a conversation in writing. You think of something to say, and then you write it down. Meanwhile, the other person waits. When they get what you wrote, they read it and you wait. They figure out their response and write it down. You wait some more. When you finally get their response, you realize they misinterpreted something and you have to clarify. In writing. This could go on all day. At least with email you can do something else while you wait. When you approach a proposal by writing a draft so you have something to think about you are doing the same thing. When you think after you write, every new thought spawns a re-write cycle. It is incredibly time consuming and inefficient. But what really hurts is that you still don’t know what the proposal should be. It’s like looking for something in the dark. The only way to find it is to trip over it. And if that doesn’t happen, you could be looking for a long, long time. I have seen too many huge, must win proposal efforts embarrassingly fail because of this approach. But usually they blamed it on something else like not starting early enough --- if we start earlier next time, we'll have enough time for all the "inevitable" re-write cycles. And then they take the same approach on the next one. You don’t have forever to wander in the dark looking at draft after draft to try to find the right proposal. You have a deadline. Thinking in writing against a deadline means that you stop when you run out of time. Instead of defining quality and doing what it takes to achieve it, you define quality as being better than the first draft and submit whatever you’ve got when you run out of time. The alternative is to: See also: Content Planning Box Figure out the points you are trying to make before you start writing Identify what needs to be included before you start writing Decide how everything should be positioned before you start writing It's really just a matter of making lists. It helps to do it within the structure provided by the outline. But it's just a series of lists that provide reminders, placeholders, and instructions for the proposal writers. When you have a list of things to address and something that acts like a thesis that all the details should support, you still aren’t ready to write. You need to validate that your points and list of items to address are accurate and complete. Now is the time to think it through. Not after the draft is complete, when improvements become costly. Re-writing a narrative to prove a different point than the one in the draft is a big deal. That’s one reason why many proposals contain unsubstantiated claims. It’s so much easier to make a statement than it is to re-write the narrative to support it. If your approach to identifying what should go in the proposal is to look at the draft and try to see what’s missing, each set of additions will take a re-write cycle, and you’ll never know when you’re complete. It won’t even be your goal. You’ll be looking for a proposal that’s good enough instead of one that is ideal. When the only guidance proposal writers get is the RFP, then compliance is all that you can expect to get back. As important as RFP compliance can be, it’s no way to beat the competition. Proposal writers need to know what points to make and what to include. If you don’t tell them, if you make your assignments at the outline level and leave the details for them to figure out, then all you can expect back is compliance. If that. If the writers are better than average, maybe they’ll tack on some unsubstantiated points and call them “themes.” Never give out an outline as a proposal assignment and expect the writers to figure it out. If they need to figure something out, make that a separate assignment. Ask them what points need to be made. Ask them what needs to be included. Pass it around to collaborate. Review it to be certain. That is the essence of what Proposal Content Planning is an iterative approach we developed to help people figure out what should go in their proposals. It’s part of the MustWin Process that’s in PropLIBRARY. It’s a pretty sophisticated methodology. But at its heart, it’s just a way to avoid thinking in writing. Or, as we like to think about it, a way to beat companies who do their thinking in writing.

Most of the wasted effort that occurs during proposals occurs as a result of poor decisions or the failure to be ready at three critical moments in time during the development of the proposal. A little bit of effort applied at those moments can prevent a ton of waste later. See also: Faster 1. The Bid/No Bid Decision First, the obvious: If you decide to bid something you can’t win, the entire effort is a waste. While true, that’s usually not very helpful. Companies don’t bid things they can’t win when they know they can’t win them, unless they are setting the stage for a future win. Companies bid them because they don’t know they can’t win them. They make their decision based on limited or non-existent information. The problem isn’t how they made the decision. The problem is that they permitted circumstances that force them to make a decision without the right information. Perhaps they should always decline bidding when that’s the case. But that’s not realistic either. The key point is that bad bid/no bid decisions are more often a result of insufficient information than they are of deciding wrongly. The bid/no bid decision is the point in time where the failure to obtain the information needed becomes clear. At that moment of clarity, when you realize that you are having trouble deciding because of what you don’t know, if you decide to bid and continue anyway you guarantee that a higher percentage of your proposal effort will be wasted. The reason you increase the percentage of waste is because if you don’t have the information at the moment of decision, you certainly don’t have it to give to the writers who need it to write a winning proposal. They will be forced to start writing without the right strategies and information, while attempting to learn them as they go. What this really means is that you guarantee they will have extra re-writing cycles to correct the things they didn’t know when they started. And if the information never comes, which is usually the case, it means you will be re-writing until the time of submission without ever getting to a draft that reflects knowledge of what it will take to win. Most of the effort that goes into writing a proposal like that is wasted effort. That’s “most,” as in more than half. That means you doubled the cost of producing the proposal on a pursuit that you knew at the time of the bid decision you were not prepared for and would be a low probability pursuit. This in turn means that by investing in getting the right information, you can cut the proposal effort in half. Or do twice as good of a job of producing it. Where should your company spend its resources? Re-writing to make the most out of a pursuit you were unprepared for, or investing the time it takes to be better informed about the next bid? 2. Proposal Startup When the proposal is starting up is a critical moment. Either you can articulate why the customer should select you, what differentiates your bid, and what the results of selecting you will be for them and do it all from the customer’s perspective, or you can’t. You find this out when you prepare the outline. Either you can take the outline further and give the writers guidance regarding the points you are trying to make, or you can’t. If you leave it up to the writers to figure out what points they should make as part of their writing assignments, you guarantee wasted effort. Either they will choose the wrong points, or more frequently, no points at all beyond RFP compliance. Inevitable and unnecessary re-writes will follow. Each re-write cycle is characterized by the writers taking longer to think about it because they lack the right information. Sometimes they just get stuck. Sometimes they work around the issue without actually solving it, completing their assignment with the hope that the reviewers won’t notice. At best, you make some points. But they are probably not based on any real customer insight. You continue to re-write in search of more and better points until you run out of time and ship what you have instead of what the proposal should have been. Are you connecting the dots yet? Failure to have customer insight at the time of the bid/no bid decision means insufficient guidance to writers and extra re-write cycles result with no hope of creating a proposal that reflects what it will take to win. Your bid strategy amounts to consuming twice as much effort in order to be a little better than your competitors. Where should your company spend its resources? Re-writing until it figures out what the proposal should say, or anticipating the questions that writers will have and that will drive your win strategies so the first draft can reflect them? 3. Proposal Reviews Proposal reviews are when most false starts are discovered. Your writers get to the review, after following the meager instructions they were given, only to be surprised that the reviewers don’t like it and expect them to do it again. The really cruel part of this is that it can happen with a perfectly good proposal. The problem is that the writers and reviewers are working from different instructions. This is a kind way of saying that most reviewers are asked for their opinion and make it up as they go along, creating a moving target for the proposal writers. If you can’t give the writers sufficient guidance regarding the points they should make, how can the reviewers use those same points as quality criteria? If you do not define the quality criteria before the writing starts, you guarantee the worst kind of wasted effort. You guarantee that towards the end of the process, close to your deadline, you’ll trigger re-writes. Where should your company spend its resources? Performing heroic acts after a late stage review that caught everyone by surprise, or putting in the effort to define your review criteria before you start writing? The lack of criteria to bring writing and reviewing onto the same page is an information problem. It is really an extension of the same information problem that showed up during the bid decision and proposal startup. The reason there are no review criteria is that people don’t know what they should be, because they don’t know what it will take to win. 1... 2... 3... If you continued to connect the dots, then you’ve realized what all three key points in time have in common. It’s information. Failure to deliver the right information at those key points in time is what drives the vast majority of proposal waste. And at each of those key moments, you know how it’s going to turn out based on whether you have that information. If you want to eliminate the vast majority of proposal waste, all you have to do is deliver the right information at those three key moments. To deliver it, you have to anticipate what you will need later and ensure that you get it before you start. Companies have difficulty motivating to do this. But when you realize that instead of resorting to win-rate destroying templates or laying off staff you could cut your proposal costs in half, would that help motivate you?

See also: Successful process Implementation I tend to focus on winning proposals instead of efficiency. One more win can produce enough revenue to cover the inefficiency of many proposals. If you want more revenue, you are better off focusing on winning than reducing proposal effort. Unfortunately, many organizations treat proposals as a cost instead of as an investment (let alone the core competency of the organization). Proposal costs are covered out of the overhead portion of the budget, and that’s always under pressure for reduction. But the best ways to reduce effort on proposals have very little to do with proposal production. Here are eight ways companies waste a ton of money on proposals: Not being selective in what they bid. Fooling yourself into thinking a bid is an “opportunity” just because you have an RFP and think you can do the work does not mean that you are prepared to win it. Fooling yourself into thinking you can win it, even though you’re not prepared, only makes it worse. Each low probability bid that loses adds the entire cost of the proposal to the efficiency equation. Just one can do more damage than buying magic proposal software can fix. Not being ready to win at RFP release. If you are not ready to win at RFP release, it means you’ll be trying to figure out what it will take to win while writing. This means you’ll have to do re-writes every time you figure out something new. It means you won't be able to write to prove the points you want to make because you'll be figuring out those points as you go. Those points will be less numerous, weaker, and torn up during review without time to fix it. Your win rate will suffer accordingly. To save the cost of losing proposals, try investing a much lower amount in pre-RFP preparation. Changing the outline. Nothing is as disruptive to proposal writing as changing the outline can be. It can burn a huge number of hours. Far more than setting aside a little bit of time to review and approve the outline. Reviewing the outline should be given the same priority as reviewing the content. Never leave it to one person to determine the outline. Discovering their bid strategies by writing about them. If your proposal is going to accomplish your bid strategies, they need to be known before the writing starts. You can’t sprinkle some "themes" on at the end and expect them to win it for you. When you change your bid strategies after proposal writing has started, you’ve changed the thesis or the point you’re trying to make. This can cause a complete do-over because everything in your proposal should be trying to make that point. Change the point and you should have edits everywhere. If you don’t, it literally means your proposal was pointless. An investment in content planning prevents this and saves far more than it costs. Proposal content planning can actually be seen as a profit center, since it will increase your win rate and bring you revenue you would have lost in return for the investment. Not being able to decide their approaches. When people don’t know what to write, it often has more to do with not being able to decide what to offer than it does with the writing. What are you going to offer? How are you going to do it? Why are you going to do it that way? When you can answer those questions, writing it down becomes straightforward. When you can’t answer those questions, you waste time getting started and then every reconsideration spawns a re-write that wastes even more time. Don't waste effort writing in circles if you want to lower your proposal costs. Not being able to answer the writer’s questions. Would the customer prefer this or that? How should we position our offering? What matters to the customer? When the writers don’t have answers to questions like these, they either Let's discuss your challenges with preparing proposals and winning new business Click here to start a conversation by email Or click below to get on my calendar to talk by phone stop and wait, write something lame with the intention of re-writing it later, or simply pull their punches and not bother making the point. This leads to waste when they don’t have the answers before they start writing. Not defining proposal quality until the review. Proposal writers should start with the same criteria the reviewers will follow. If the reviewers make up their criteria at the time of the review, you are guaranteed to introduce unnecessary and costly re-writes. Not reviewing the proposal until all the narrative is in place. Waiting until all the text is in draft form before you start reviewing means the review takes place later than needed and the changes will spawn more extensive re-writes with less time to accomplish them. It’s wasteful. By the time you get to a draft, you should have already reviewed your outline, bid strategies, approaches, positioning, and many other things, leaving only wordsmithing and presentation to be reviewed. Add up all the delays and re-writes and it’s not unusual for companies to waste more than half their proposal effort. How much effort should a company go through to prevent some of that waste? It’s an 80/20 problem. For 20% of the effort, you can reduce 80% of the waste. Why don’t more companies invest in that 20%? Looking back on what I just wrote I find it very interesting that by reducing the waste, you’ll also win more proposals. The things you do to eliminate the waste are some of the same things you should do to increase your win rate. Reducing cost at the same time you increase revenue is a fantastic way to increase your ROI. If you do the math and compare the costs to the benefits of reducing a percentage of that waste while increasing your win rate by a percentage, it’s not hard to see benefits that are orders of magnitude greater than the costs. But what I like best is that instead of having to psych yourself up to invest effort to achieve your gains, by eliminating waste you’ll actually be putting less effort into achieving your gains. Or you could just wastefully muddle through like you are now.

The proposal becomes part of the conversation when it responds to something the customer said, usually in the form of an RFP, and then gives them an opportunity to continue the conversation, usually by accepting your proposal. But there is more to it than that. When making the proposal part of a conversation is part of your strategy, you have to be the company that the customer would most like to continue the conversation with. That means you have to put things on the table to discuss in a way that engages the customer and makes them want to participate and hear more. The conversation that the proposal is usually a part of, is a conversation about what you and the customer can accomplish together and how to make it happen. The customer will want to continue that conversation if it involves great things that are feasible from someone who is credible. Making a proposal part of a conversation is a bid strategy. It is a conscious choice to engage with the customer in a certain way because you think it will make them more likely to accept your proposal. It is a strategy that does not apply to every proposal. It is best suited for: See also: Customer perspective Proposals to provide solutions, things that must be developed, or complex services An RFP that provides goals instead of specifications or one that asks you to tell them what the best approach is When you have questions that the RFP and/or customer can’t answer When both you and the customer will have to puzzle through questions as part of doing the work proposed In other words, when there are a lot of unknowns and the two of you really need to talk instead of exchange documents, turning the documents into a conversation is a way of demonstrating that you are a good pick for the customer to talk through the issues with. To make the proposal part of a conversation you pick up from the last customer communication, possibly the RFP, and provide a framework for continuing the conversation. The project becomes part of the conversation, just like the proposal. But the conversation must involve discussion in both directions. You must both take turns speaking for it to be a conversation. You have to provide opportunities for the customer to have a voice. Everything that goes into making a verbal conversation successful also applies to a written one. The key difference is that it is less interactive. It is similar to a discussion that takes place in email, but even less interactive. But just like there are things you can say in writing that encourage conversation, there are things you can say that discourage conversation. Personality counts as much in a written conversation as it does in a verbal one. When you successfully position your proposal as part of an ongoing conversation, then from the customer’s perspective, they see that you’ve listened to them and responded with something interesting. You’ve shown that something special can be achieved if the two of you work together. You haven’t nailed down all the details, but you’ve shown how the two of you can work them out. You’ve backed up what you’ve said to make it credible. When they look at the other proposals, they see plans and details, but they have no idea what the other vendors will be like to work with. And since the nature of the project involves some uncertainty, that’s a big deal. Who will the customer pick to work through the uncertainty with? You might assume it’s the incumbent, but if the incumbent hasn’t been completely responsive, there’s an opening for someone who is demonstrating their responsiveness, as opposed to simply claiming it. If the incumbent submits a proposal that is not engaging, and you submit one that is engaging, credible, and feasible, you can steal it away from them.

We usually think of a proposal as a tool to close the sale. Does that mean it’s an ending to the conversation you’ve been having with the customer? Or is the start of another conversation? What if you go into the proposal and you haven’t had any conversation with the customer? Can you have a conversation on paper? How does that work? We discover the customer’s needs, we brainstorm solutions that match our capabilities, and we offer them to the customer for consideration. We really want to ask questions that drill down to a deeper understanding of those needs. After we do some brainstorming of our own, we’d like to do some more with the customer. When we offer them things for consideration, we’d really like to hear their feedback. That sounds a lot like a conversation. But too often, we start with an announcement or statement of requirements that we get either by email or on a website. We respond to that in writing. Sometimes, without any discussion beyond some minor negotiation, we find out that we won or lost in writing. Contracts are signed and people start working. Then we actually start having real conversations with the customer. When your conversation is mostly on paper, you can see why having verbal conversation prior to the announcement is so critical. It’s your only chance. And you can see how those who have actually spoken to the customer have a very real competitive advantage. One way to mitigate this is to better understand what a conversation really is, and build your business development practice around it. Conversation is more than just telling. It is more than just describing. Having a conversation with someone who just talks about his or her self is boring. Conversation is interactive. If you are stuck in a procurement process that is turn-based (on my turn I release an RFP, on your turn you submit a proposal), you can still demonstrate your conversational skills. Part of having good conversational skills is recognizing the needs of the other person. It’s adapting what you say and how you say it to what you know about them. See also: Relationship marketing When your conversation is on paper, you need to do the same thing. Part of having good conversational skills is asking questions and listening to what the other person has to say. When your conversation is a proposal, you can offer approaches that will give the customer an opportunity to speak and demonstrate your skills at listening. When the proposal is part of the conversation, it shows that you listened to what they said (even if it’s in writing), provides things for them to consider, invites them to share their thoughts, and then seeks an opportunity to resolve those considerations in person. This is a different style of writing than most people are used to. You may not actually propose doing anything differently, but you must communicate it with a different attitude, desire, and intent to escape the trap of describing yourself and invite the customer to participate in a conversation. Instead of fronting like you’re omniscient and hiding what you don’t know, in a conversation you feature it. Share what you would like to learn more about the customer in the proposal. Don’t patronize them by telling them who they are or what they need. Tell them about what you see and what the possibilities are. Tell them what their options and choices will be if they accept your proposal. Show them that you have an approach for getting to know them and adapting your offering to their preferences. Focus on how you will be able to deliver better results because your approach involves listening to them. If you are bidding against someone who has already had a conversation in person with the customer and earned their trust, the odds are stacked against you and you may not even want to bid. But if the customer found them unresponsive, there’s an opportunity to demonstrate your responsiveness in your proposal. When a customer considers a vendor unresponsive, that means they weren’t available for conversation or didn’t take action in time. Instead of telling the customer your approach and describing your qualifications, try setting up a conversation. If you are the customer and your choice is between: A vendor who says the same-old things, restates the customer’s requirements and says they understand, makes many promises, brags, flatters, and sings their own praises with unsubstantiated claims; or Another vendor who shows they have listened to the things you’ve said, demonstrates that they actually listened with insightful comments and options for you to consider, is up front about what they don't know but has an approach to finding it out, and then invites you to a real conversation so that the things they do will reflect your preferences Who are you tempted to pick? The best thing about the conversational approach is that it doesn’t involve doing anything differently than how you otherwise should be doing them. You need to discover the customer’s needs and preferences. You need their approval for what you intend to do. You want their feedback along the way. Instead of hiding behind meetings, reports, requirements analyses, surveys, and other process instruments of customer interaction, approach it all like one big conversation. Keep all the process instruments, just recognize that a conversation is bi-directional and interactive. Each meeting and each deliverable is just one part of a larger, ongoing conversation. When you remove the conversation, you are just pushing paper. When you make it all part of an ongoing conversation, then you have a relationship. If you go into the bid without an existing customer relationship, you have a critical weakness against someone who does. Your only shot at overcoming that weaknesses is to become a better conversationalist than your competitors. Even if you have to start the conversation in writing.

Customers ask for descriptions, even though that is not what they really want. They are not being sneaky, they just don’t know what to put in their RFPs, so they ask you to describe things they think are relevant to what they are trying to do. If you understand the decision they have to make, then you can address what they really need to know when you respond to what they asked for. When they say: See also: Customer Perspective Describe your company. They mean, “What can you do for me?” They also mean, “Can I trust that your company is able to do what I need?” Describe your qualifications. They mean, “Can I trust that you know what you’re doing and will you be able to deliver on your promises?” What is your transition plan? They mean, “Will you be ready on time and will you meet our deadlines?” They also mean, “Can I trust that there won’t be any disruption and that I won’t be worse off by selecting you?” What is your approach? They mean, “What am I going to get if I select you?” They also want to know if they can trust that you know what you are doing. They also mean, “Why should I pick you? What will I get that’s better than if I pick someone else?” What is your experience? They are thinking, “Maybe if you’ve done it before I can feel confident that you’ll be able to do it again.” But what they really mean is, “Can I trust you to deliver on your promises?” They do not want your experience. They want to know what they will get out of it. Describe your understanding. They are wondering, “Do you know what I mean, as opposed to what I’ve said?” They are concerned about whether you know what they need better than they were able to explain it. They want to know if your interpretation of their requirements reflects what they really want. They want to know if they can trust you to do things the way they would like them done. They also want to be sure that you know what matters to them and have good judgment. Describe your management approach. They want to know if they can trust you to actually deliver the results you’ve promised. They want to know if your experts will stay focused on delivering the right results. They want to know if they’ll have all the support, resources, and processes needed for them to receive the results you’ve promised. Describe your staff approach. Regardless of what you’ve promised, they want to know that the people who will be doing the actual work can be trusted to deliver the results they need. Describe your quality approach. They want to know what you’ll do to prevent mistakes and whether they can trust you to catch them when they occur. Describe your approach to risk mitigation. They know that things go wrong. They want to be able to trust you to deliver anyway. They are not looking for empty promises about some abstract concept of risk or lame examples. They want to know what they can trust you to prevent and what you will do to fix things when they go bad. Provide proof of insurance and a performance bond. They’ve had bad experiences with vendors they thought they could trust. They need more than just empty promises to be convinced. Did you notice that every example of what the customer really means has the word “trust” in it?. Every one. Maybe you should stop loading your proposal up with sales slogans and unsubstantiated claims. Maybe instead you should focus on being trustworthy, and the things you do that impact it. And just maybe, instead of describing yourself you should give them what they really want.

I know it’s fun to complain about the boss, but if you want to get things done, you need to think like the boss. There are reasons why you are encountering friction. It’s not as simple as they are micro-managers or ignoring you. You can use this list to anticipate their concerns and improve the chances that they’ll listen to your concerns. Why your executives won’t list to you: See also: ROI You’re not thinking in terms of Return on Investment (ROI). Executives spend money and allocate resources in order to achieve certain goals. In business and proposal development those goals are usually related to revenue and profit. Companies will spend more to make more. They usually won’t spend more to make people happy. Appealing to ROI only works when it’s quantified. If you say “we should invest effort in following the process because it will boost our win rate and the company will make more revenue,” then what you are saying will be true but unconvincing. But if you show mathematically the difference between raising win rates by 10% vs. increasing the volume of bids by 10%, it’s a lot more compelling. You are not the only stakeholder. You’ve got your needs. So does the subject matter expert who doesn’t want to help with the proposal. So does the CEO. So does everybody who touches or is impacted by the proposal. For executives it can be like having a bunch of noisy kids in the back seat of the car, and they often react accordingly. Budget and incentives distort the picture. Nearly all executives are on some kind of incentive plan. So are many business development and even proposal staff. While having people on incentive plans benefits the company, all incentive plans distort behavior and have negative consequences. It is entirely possible that what you are asking makes complete sense but goes against their personal incentives. If they are aware of it and it really makes sense, they may do what you want anyway. But they may not even be aware of it and are just acting on what they feel are the company’s priorities. They have goals you are not aware of. Your company may be pursuing financing or an acquisition (maybe of itself). There may be legal issues. Or results of an audit. Or informal agreements between teaming partners. Or other reasons that the company doesn’t want to discuss that impact its decisions for better or worse. You’re bringing them problems instead of solutions. If you bring your executive a problem, they have to invest in finding a solution and will probably incur a delay. If they have other fires to fight, yours may not be the highest priority, from their perspective. They’ll get to it when they can. If you bring them a solution, they just have to make a decision (which is painful enough). Bringing them a solution means bringing them the whole cost/benefit analysis and implementation plan so that if they approve it, they can turn their attention elsewhere. You are limiting their freedom to act. When you tell them when they must participate and how, you box them in. If they are in fire-fighting mode, they may just ignore your guidance or attempt at restrictions since from their perspective, they need to juggle competing demands for their attention and act when they have time to do so. You haven’t set expectations. If an executive doesn’t know what to expect in terms of process or results, they may perceive a need to intervene. Or have their attention focused elsewhere when there is a need for their intervention. You’re adding uncertainty instead of clarity. When you speak of issues or risks, you add uncertainty to their considerations. This is true even if you are just the messenger and not the cause of the issues. You are something else that requires attention. If instead you bring clarity to the issues, you focus that attention. Sunk costs. It’s hard to walk away from what you’ve already spent or invested in a pursuit. To avoid seeing it as a loss, it has to be framed as an investment. Fixed costs. Whenever you have fixed costs, you want to maximize their productivity. A salary is a fixed cost. Dumping more pursuits onto someone on salary seems like maximizing productivity. Arguments about opportunity costs, or the fact that if you put effort into a low probability pursuit, it takes effort away from higher probability pursuits are unpersuasive. If, at that particular moment, there are no other higher probability pursuits, they are completely unpersuasive since there appears to be no added cost to pursuing, but there is a slight chance of a payoff. If you think like an executive yourself, you’ll do a better job of providing the right information to achieve the outcome you desire. It’s really the same thing as writing a proposal from the customer’s perspective. You’re just applying it to selling within your company instead of to a customer. The MustWin Process in PropLIBRARY is designed around managing expectations and coordinating the efforts of all the stakeholders, including your executives. It directly addresses most of these considerations, and will help strengthen your position for the rest.

The easy answer is all those regulations. Another good one is whether full compliance is mandatory or not. But the real answer is something different. It’s something that people struggle with. You can look up the regulations. You can learn to comply like a robot. But the most important difference will determine whether your proposal is a success or a failure. How do you get your proposal started? In both government and commercial proposals, the proposal should really start before the RFP is released. But let’s put that aside for a moment, along with other steps like kickoff meetings, etc. Also, I’m going to lump all proposals written against RFPs that are formally evaluated by the customer into the same category as government proposals. Most people start their proposals with an outline. But how do you prepare your outline? In a commercial RFP, you pretty much make it up. Most commercial proposals are evaluated with a great deal of subjectivity and are not formally point scored based on written instructions and evaluation criteria. In fact, most commercial RFPs are more of a wish list, starting point, or framework than a set of specifications that must be followed exactly. When this is the case, and it varies all over the place, the goal is to give the customer the information they need to see you as their best alternative. This information may be in addition to or instead of whatever was in the RFP. What makes government proposals so different and challenging isn’t just that you have to give them exactly what they asked for in the RFP. What makes them so different is that your outline must match what is in the RFP exactly. This must be true even if the RFP is ambiguous, contradictory, out of sequence, outdated, or flawed in some other way. Resolving those issues to come up with the right outline is difficult and stressful. Government proposal specialists use a compliance matrix to match the requirements from different sections of the RFP. When an RFP is well written, everything matches and the sequence is in synch. When the RFP is not well written, things don’t match and you have more than one sequence that you have to somehow resolve and make compatible. I’m coaching a company that is dealing with this right now. I feel bad because she has a really convoluted RFP that she’s trying to make sense of. Instead of being a nice, neat case where you just follow the rules and use the outline provided, it requires judgment calls. Things could go in more than one place and we struggle to determine where the customer expects to find them. What they say they want to be in the proposal, how they say you should organize things, and what they are going to evaluate do not match up. But regardless of whether there is a place specified for everything or if there is more than one place, every requirement must be addressed somewhere. And it has to be where the customer expects to find it. That is what a compliance matrix is designed to resolve. But when the RFP is poorly written, it requires more judgment calls than it should. I’m helping her put things where we think the evaluators expect to find them. In some cases we have to guess. I hate it when customers do this to themselves. The evaluators are going to have a hard time because every vendor will make different judgment calls and each proposal will be organized differently. In a commercial proposal that is not going to be formally evaluated, you might organize things in a logical fashion because the customer is subjectively looking for the best proposal, and not usually trying to point score against the RFP. In the commercial world, you can propose whatever you want and the customer might just go for it if they think it makes sense. But in government proposals, you must propose exactly what they ask for and prepare your proposal exactly the way they asked for it. These different approaches to preparing the outline have major implications. If you try to respond to a government proposal like you would a commercial proposal, your proposal may get thrown out without even being evaluated. And if it does get evaluated it will be at a disadvantage because it will be hard to score if it didn’t follow the RFP exactly or if you didn’t understand how the evaluation process impacts the outline. Learning to prepare an outline for a government proposal is one of the most difficult parts of responding to a government RFP, and if you don’t get it right you won’t win regardless of what’s in your proposal. Getting the outline right is the first step in realizing that your proposal is not about you. It’s not about whether you think it’s well organized or how you would like to present your offering. Getting the outline right for a government proposal is all about putting information where the evaluator expects to find it so they can find the right words to complete their evaluation forms. Your proposal is about them. Commercial companies that want to do business with the government may get past the registration requirements, survive the lengthy sales/RFP process, find a way to meet the past performance requirements, and then blow it just because they didn’t understand how much needs to go into thinking through the outline for a government proposal. So it may not be the first thing you think of when you imagine the difference between writing government and commercial proposals, but the getting the outline right is definitely one of the most important.

Why do so many businesses set themselves up to fail? Just because you are capable of doing the work a customer needs does not mean that you matter. If you don't matter, the only way you can be competitive is on price. The closer you get to a commodity, the more important price is. With a commodity, every vendor is providing the same thing and which vendor you get it from does not matter. The closer you get to a complex solution or services, the more price gives way to credibility and value. If your customers do not care about you as a vendor or do not care about value, then you can: See also: Great Proposals Compete on price alone. Doing this successfully is mostly a game of keeping your overhead low. That makes it really hard to invest in growth. Seek other customers. Is a customer that doesn’t care about you and isn’t going to care about you worth having? For how long? Is a customer that won’t talk to you before RFP release worth having? Every customer relationship is an investment. Invest wisely. Educate the customer regarding how they are impacted by other considerations. If the customer connects with your value proposition, then you matter to them. If the customer is open to a conversation about what impacts them and how you can make a difference, you matter to them. If the customer is not interested in learning how to get better service, see Number 2. If your customers do not care about you as a vendor I would also take that as a sign that you've failed to matter to them. I would want to fix that. To matter to the customer, all you have to offer is: Something that will positively impact them that’s also the best alternative available to them The right value proposition so they can afford it Credibility and trustworthiness so they’ll believe they’ll actually get it from you If it's a customer you already have, the list remains the same, it just gets evaluated with more of a focus on your performance than what you say in the proposal. If you have no credibility, you don’t matter. The smaller the impact the less you matter. The more alternatives they have, the less you matter. If they can’t afford you, you don’t matter. If you don’t matter to your customers and you want to reverse that, you need to offer a substantive positive impact, be the best alternative, be affordable, and for the customer to believe in you. The best way to achieve all of that is not to focus on yourself. Focus on your customer. Ask yourself, from their perspective: What would positively impact them? What alternatives do they have? What can they afford? What represents the best value? What would prove a vendor’s credibility and trustworthiness? Then help the customer discover the answers. Not by telling them about yourself, but by helping them get what they need. It’s not about you. It’s about what matters to them. You can do this in person. And you can do this on paper. It’s just a lot harder to do it on paper, if you haven’t achieved it in person. But it has to be achieved on paper to close the sale with a winning proposal. If you don’t matter, then you can still win. If you don’t matter, then you’re just a price. Price always matters. It’s just not always the most important thing. Now you know what to do about that. And oh, by the way, the entire MustWin Proposal Process is about the steps required to discover what matters to the customer and get it into the proposal so you can go from writing ordinary proposals to writing proposals that are great.