BW-201a · Module 1

Leading with the Problem, Not the Solution

4 min read

The most reliable way to lose a reader in a proposal is to lead with your solution before establishing that you understand their problem. This happens constantly. Proposals open with: "We offer a comprehensive suite of consulting services designed to improve organizational performance." Or: "Our proprietary methodology has helped over 200 companies streamline their operations." These sentences are about the writer. They ask the reader to be interested in the writer before the writer has given them any reason to be.

The alternative — leading with the problem — requires a different kind of discipline. It requires the writer to set aside their natural instinct to demonstrate competence and instead demonstrate understanding. Understanding the problem is more persuasive than any capability statement, because it signals that what follows is relevant to the reader specifically, not to all possible readers generally.

Do This

  • Open with a specific description of the reader's situation and the cost of the problem
  • Use the client's own language and framing from discovery conversations
  • Name the business consequence of the problem, not just the technical symptom
  • Create urgency by naming what happens if the problem is not addressed

Avoid This

  • Open with your firm's history, credentials, or general capability statements
  • Describe the problem in generic terms that could apply to any client
  • Lead with your solution before demonstrating that you understand the problem
  • Use the problem statement as a platform for your methodology

The problem statement should do something specific and somewhat uncomfortable: it should describe the client's pain. Not abstractly — "you are facing challenges in your market" — but specifically. "Your sales team is closing at 23% on qualified leads, against an industry benchmark of 31%. That 8-point gap represents approximately $2.4M in annual revenue that is reaching qualified prospects and not converting. The methodology you are currently using was built for a different buyer profile and has not been updated since your market shifted in 2023."

That is a problem statement. The reader who sees their situation described with that specificity does not ask whether you understand their problem. They ask how quickly you can start.

Problem-first sequencing has a secondary benefit: it forces the writer to do real discovery. You cannot write a specific problem statement without actually understanding the client's situation — which means the proposal writing process is also a quality check on your pre-sales work. If you cannot write a specific problem statement, you did not do enough discovery. Go back and learn more before you write. The proposal is not the place to discover what you should have learned in the meeting.