1
Research the target organization before writing anything
Review their annual report, website, press releases, and any public financial filings to identify a specific operational gap or strategic challenge they face. The quality of your problem statement depends entirely on this research.
π‘ LinkedIn and industry trade publications often surface pain points executives have stated publicly β quote them back to establish credibility.
2
Write the problem statement from the reader's perspective
Frame the problem using the target organization's language and data where possible. Reference specific metrics, costs, or missed opportunities that are observable and verifiable.
π‘ If you cannot cite at least one external source or piece of observable evidence for the problem, your research is incomplete.
3
Define the solution in terms of outcomes, not features
Describe what will be different for the organization after your solution is implemented. Quantify the expected outcome wherever possible β cost saved, time reduced, revenue gained.
π‘ A single quantified outcome ('reduce onboarding time from 14 days to 5 days') is more persuasive than three pages of feature descriptions.
4
Build the scope of work and exclusions list
List every deliverable with a format and delivery date. Then write a separate exclusion list covering at least three things you will not do. This protects both parties.
π‘ Phase your deliverables into logical stages β discovery, design, delivery β so the reader can visualize the engagement before committing.
5
Select and brief the team credentials section
Include only the people who will work on this engagement. For each, lead with the single most relevant past project and its measured result.
π‘ If you are a solo consultant, include one or two client references by industry and outcome β with the client's permission.
6
Frame pricing as a return on investment
State the total fee, the payment schedule, and then immediately follow with the estimated value delivered β savings, revenue lift, or risk reduction. The ratio of value to cost should be obvious.
π‘ Avoid itemized hourly breakdowns in an unsolicited proposal β they shift the reader's focus to cost rather than value.
7
Write the executive summary last
Pull the strongest evidence point from the problem statement, the clearest outcome from the solution section, and the specific next step from the call to action. Keep it to two paragraphs.
π‘ If the executive summary alone does not make the reader want to act, the proposal is not ready to send.
8
Proofread for the reader's name and organization throughout
Search the document for every instance of [TARGET ORGANIZATION] and [CONTACT NAME] before sending. An unsolicited proposal addressed to the wrong name or a competitor's name ends the conversation immediately.
π‘ Send as PDF unless the reader specifically requests an editable format β a polished PDF signals professionalism and prevents accidental edits.