A consulting proposal checklist, from brief to send

1. Check the proposal against the actual brief

Put the client’s email or discovery notes beside your draft. Highlight the agreed facts: the problem, audience, requested outputs, constraints, budget, and timing. Mark anything you added as a suggestion rather than an agreement.

A useful opening says what you understand and what you propose to do. For example: “Your team wants to understand where new users struggle between signup and their first dashboard. I propose a desktop onboarding audit of the five screens we select together.”

Remove claims that are not supported by your own experience or the client’s evidence. An AI draft should not invent a previous client, revenue gain, certification, or team member to make the proposal sound convincing.

2. Explain how the work leads to a decision

Describe a short sequence of activities and why each is needed. For an audit, the sequence might be to confirm the journey, inspect the screens and existing evidence, prioritize the findings, then review recommendations with the client.

Make the output of each stage clear. A client should be able to tell whether they are buying advice, a design, an implementation, or a combination. Avoid a long method section that never says what will be handed over.

If discovery could change the assignment materially, consider offering discovery as a defined first phase. Do not price an unknown implementation as though its requirements were settled.

3. Read scope, timing, and price as one offer

A scope can look reasonable on its own and still contradict the schedule. A ten-day project with a ten-day client feedback window leaves no room for the revision unless you explain how those periods relate.

• Scope: specify quantities, formats, exclusions, and review checks.
• Client inputs: identify required materials and a person who consolidates feedback.
• Timing: state when the clock starts, the duration, and outstanding scheduling decisions.
• Fee: show currency, price basis, payment milestones, and how extra work is agreed.

For an hourly estimate, confirm whether the stated hours are a forecast, a cap, or a minimum commitment. For a fixed fee, make the boundaries explicit. A number without a price basis is easy to misunderstand.

For more detail on deliverables and boundaries, use the freelance scope of work guide.

4. Compare the brief with a coherent offer

Consider this fictional request: “Please review our onboarding. We have a USD 2,500 budget and want recommendations quickly.” That brief is not yet a complete commitment.

The output is a proposal for discussion. A budget does not automatically become your agreed price, and a desired deadline does not become your delivery promise without a feasibility check.

5. Run this checklist before exporting

CLIENT AND CONTEXT
[ ] Names and project title are correct.
[ ] The problem reflects the client's brief.
[ ] No experience, results, or credentials have been invented.

WORK AND BOUNDARIES
[ ] Every deliverable has a format, limit, and useful review check.
[ ] Adjacent work that is excluded is named.
[ ] Client inputs and the feedback owner are identified.
[ ] Suggested assumptions are marked for confirmation.

TIME AND MONEY
[ ] The start condition and duration are explicit.
[ ] Feedback and revision timing fit the schedule.
[ ] Currency, fee basis, totals, and payment milestones agree.
[ ] Taxes and additional expenses are addressed or left as open questions.
[ ] Additional work requires a new agreement on scope, price, and timing.

FINAL REVIEW
[ ] Open questions are easy to find.
[ ] The client has one clear next step.
[ ] The exported file matches the approved draft.
[ ] Names, amounts, dates, and links have had a human review.

Read the exported document once more. A correct editor view is not enough if the PDF cuts off a fee table, breaks a heading, or omits the open questions.

Common questions