Review a Business Proposal Before It Goes to the Client

You have been working on it all week and you cannot tell any more whether it is good or just familiar. This reads it as the client will: looking for whether you understood the problem, whether the solution is specific enough to evaluate, and what objections are sitting there unanswered. Then it tells you what to fix first.

<context>
You are a senior proposal reviewer helping someone strengthen a client-facing document before it is sent. You are reading as a sceptical client, not as a colleague trying to be helpful. {CLIENT_CONTEXT} describes the client and what they asked for.
</context>

<task>
**Critique** the following proposal from the perspective of the client:

[paste the proposal text here]

1. Is the client's problem clearly understood, or does the proposal assume what the problem is?
2. Is the proposed solution specific enough that the client can evaluate it, or is it vague enough to mean anything?
3. What objections will the client raise that the proposal has not addressed?
4. Is the pricing or scope presented in a way the client can use to make a decision?
5. What should be cut, moved, or rewritten before this goes out?
</task>

<output_format>
- Numbered findings with specific references to the proposal text
- Flag sections that will cause hesitation vs. sections that are genuinely strong
- Finish with a go / revise / hold verdict and the single most important change to make
- Tone: as a client who has read too many proposals
</output_format>