A proposal is a summation, not an explanation. It is a summary of the conceptual agreement you’ve reached with an economic buyer and not a negotiating document or an attempt to make a sale.
Therefore, it is formed only after conceptual agreement with the buyer has been completed. We talk more about this later in the chapter, but at the outset it’s important to understand that I’m not talking about the generic or stereotypical proposal in this book. Proposals are a summary of what’s come before, to which the buyer has already agreed, and constitute the connection (the synapse from the introduction of this book) to the launch of the project. Proposals are organic documents, which are used to guide and monitor the project, and are not immediately archaic fossils of the Pleistocene Epoch intended for dusty display cases and re- mote shelves.
Here is what an outstanding proposal can do:
- Summarize and convey formally the conceptual agreements reached in discussions to that point between you and the economic buyer.
- Detail the objectives of the project.
- Provide for the metrics of success.
- Describe the value that will occur once the objectives are met (both personally and professionally).
- Supply options from which the buyer can choose to determine the amount of value sought in return on the investment (ROI) committed.
- Stipulate fees, expense reimbursement, and payment terms.
- Enable immediate acceptance in writing.
My proposals serve as the contract as well as the offer of the contract. They are in plain English, without “third parties shall hold harmless,” because if you include boilerplate legalese, you will ensure that the proposal will wind up in the hands of your prospect’s lawyers, who are so conservative and protective that they’d prefer that the firm not even open the doors every morning in order to prevent any harm from befalling the enterprise.
Here is what proposals cannot and should not do:
- Enable a non buyer (gatekeeper, HR, or training person) to proceed to a buyer on your behalf.
- Establish your credibility.
- Establish a relationship with a buyer.
- Serve as a point of comparison for competitors’ proposals.
Case Study: The Federal Reserve
I had submitted my normal 2.5-page proposal to the Fed in New York, the largest of the Federal Reserve Banks. I had been recommended by some of the banks they supervise, which were clients of mine.
It was mandatory to allow legal to review all proposals, and they took two precious weeks, returning a 32-page monstrosity. Once my buyer and I read it—a painful undertaking—we were shocked to find virtually no difference whatsoever, no changes in my aggressive fees or payment terms, but in- stead an additional 29.5 pages of language worthy of the Rosetta Stone to interpret.
Lawyers are hopeless at two pursuits: running a professional firm based on value, and using the English language to convey meaning.
- Offer vague promises or results and outcomes.
- Include agreements that the buyer has not agreed to prior.
- Serve as a “take it or leave it” alternative.
- Cite legal provisions and covenants.
- Be valid and acceptable without time limits.
- Serve as an agreement for non value relationships, such as pricing by day, participant, materials, labor, and so forth.
What I’m telling you—and what will influence this entire book—is that proposals have traditionally been viewed incorrectly in professional services. They have been a gallimaufry of credibility, research, consultant’s beliefs and mission, pricing, risk management, and competitive submission.
Glossary
Economic buyer: That individual who can produce a check in return for the value expressed in your proposal without any other approvals from anyone else.
Conceptual agreement: Concurrence with that buyer about the objectives for the project, the metrics that will measure progress and/or success, and the value to the organization and the buyer that will accrue as a result of meeting those objectives.
Gatekeeper: Any person who cannot say yes but can say no and sees it as his or her responsibility to keep you distant from the buyer. In most cases this will include the entire human resources, training, and/or learning and development areas.
All of that is wrong. Those issues need to be covered prior to the proposal being created.
I had been consulting with a pharmaceutical consulting firm in New York for a couple of years, right through a lucrative sale to a larger operation. The most important thing I accomplished was to persuade the firm to stop using a metric of “number of proposals issued per week”! Supposedly, this number was an indicator of sales success (e.g., “27 firms asked for our proposals”) but the “hit rate” was dreadful and an entire back office of resources was wasted creating huge, assembly-line proposals.
Proposals are not the point of the arrow, they are the heft behind the arrow. The penetration and aerodynamics are based on other factors, and we turn to those now to put the positioning and creation of proposals in perspective.
Ironically, most people submit proposals far too early and far too often. They are actually at the conclusion of the sales process, just prior to a project’s launch. When a proposal is accepted, you should be able to begin work immediately.

