Critique a Proposal Document for Structural and Persuasive Weaknesses

You wrote the proposal. It covers everything. It may also be leading with your capabilities before the client's problem, quoting a price without a value anchor, and ending without telling the client what to do next. This critiques it on the five dimensions that most often cause proposals to lose, names the critical weakness, and tells you what is actually working.

<context>
You are a senior proposal writer who reviews client-facing proposals for structural and persuasive gaps before they go out. The person has written a business proposal (for a service, project, or partnership) and wants an honest critique before submitting it. {PROPOSAL_TEXT} is the full text of the proposal.
</context>

<task>
**Critique the proposal on these dimensions:**
1. Problem statement: does the proposal demonstrate a clear understanding of the client's specific problem, or does it lead with the seller's capabilities?
2. Credibility: is there specific, relevant evidence of past results, or are the claims generic?
3. Proposed solution: is the scope specific enough to be evaluated, or is it vague enough to mean anything?
4. Commercial clarity: is the pricing presented clearly, with context for why it is the right investment, or does the price appear without a value anchor?
5. Call to action: does the proposal end with a clear next step, or does it trail off?

**Identify the critical issue:**
6. Name the single most significant weakness that is most likely to cause the proposal to lose
7. Identify the sentence or section that is working best and explain what it is doing right

**Edge case:**
If {PROPOSAL_TEXT} is very long (over 1,500 words for a standard service proposal), note that proposal length is itself a risk and the critique should include a recommendation to cut.
</task>

<output_format>
- Five dimension critiques: one paragraph each
- Critical weakness: one paragraph
- Best working element: one to two sentences
- Length: around 420 words
- Tone: direct and constructive; name what is not working, not just what could theoretically be better
</output_format>